by raez » July 21st, 2016, 7:42 am
Thanks for the quick response vic!
Yeah, now I've tried just scheduling for today instead of all week. My mistake about the clock, I'm based in europe so I'm familiar with the 24 hour clock - however, not that familiar with the 12 hour clock it seems!
My roomba wouldn't wake up, the following was sent through roomba status (while roomba was in full-mode):
7: Got a response
128: Got a beep
168,4,12,15
167,16,12,20,12,20,12,20,12,20,12,20,12,20,12,20
- "disconnect"
Then i plugged out my cable from my roomba, after approximatly 3 min it entered standby-mode where the LED:s was turned off. 10 min later - no response.
I tried another variant that looked like this:
128
168,4,12,15
167,16,0,0,0,0,0,0,0,0,12,17,0,0,0,0
The two minute difference was to try if the roomba would start cleaning on schedule if the roomba didn't enter standby mode. But with no success. I tried again after reseting the roomba with "7".
Do I need to have the roomba in the charging dock after entering schedule so it doesn't enter standby mode?
Is there anyting in the roomba status program that needs to be turned on before sending the codes? I'm in full control in the "Full mode" which I'm entering through the "Start" button in roomba status interface. After pressing that button I'm currently sending the codes.
I've tried sending spot/clean/dock start codes, which all function as expected.
What else can i try? I'll try realterm now to see if I have any luck there.