I've been tinkering with the auto start features available to hopefully reduce my downtime and I have a question. My Chili miners require two starts, they error out spectacularly the first time then they'll hash just fine on the second start.
Is there any way to schedule a run once task to start them as automated devices a second time? I was able to have them auto start with the client, then start 20 seconds later, but then it tries to send them a start command every 20 second which seems less than ideal. Any help would be appreciated!
It doesn't actually send any commands to the devices if they are already running. But it does print "Executing scheduled action: Start automated devices" every time in the log which is annoying.
I have attempted to fix the problem with having to start Chili devices twice in the beta. Could you try that and see if it has worked? The beta is available under the "tools" menu on the website.
I tried the beta this morning. On starting Chili 1 I got
2014.03.18 [8:05] Device detected on COM29: BitFORCE SC 1.0
Then this, repeated probably 30 times
2014.03.18 [8:05] BitFORCE (COM29) ERROR: Unexpected response to stage 1 or 2- stage command: ERROR: UNKNOWN
Then it ended on
2014.03.18 [8:05] BitFORCE (COM29) ERROR: BFL-incompatible Chili firmware? Retrying without ZWX command
2014.03.18 [8:05] BitFORCE (COM29) ERROR: Unexpected response to queue job pack command: INPROCESS:0
Text is the same for Chili 2 (COM31) but they did both start hashing. However for some reason it seems like the server stopped giving me work very quickly and eventually both ended on
2014.03.18 [8:05] BitFORCE (COMXX) ERROR: BitFORCE (COMXX) ran out of work. Idling…
I tried it again a bit later and this time it seems to be working. Only running for about 3 minutes but it didn’t stall out immediately either. I still get hit with the above mess in the log but they do start hashing without any additional clicking from me. I tried to set COM29 and COM31 as automated, and set the client to auto start them and while it hits both it only manages to actually start one of them when I try it that way. I may tinker with the scheduled tasks to see about getting around that.