Close

Command Structure Testing

A project log for ES-200 Electric Scooter Unlocker

Our streets are becoming litter with high technology joy. These forgotten scooter must be reverse engineer and given the love they deserve.

Mr. SpriggsMr. Spriggs 12/20/2019 at 13:530 Comments

Today I got the code working to send test commands to the scooter motor controller. This is some of the rules the command system seem to follow.

- It looks like the commands need to be sent twice for them to take effect.

- The keep alive command/ Kill will over write all other commands. 

- The commands you want to keep working need to be sent repeatedly to keep working, every 10 sec is OK. 

None of this has been tested on a running scooter. (i.e. don't want to kill my ride) So I can't  tell you if the motor is operational.

As for the commands Ive gotten something to happen
0x02 Causes headlight to flash and a loss of the LCD
0x03 Causes headlight to flash and LCD is still working
0x04 None
0x05 Turns on Scooter 
0x06 Causes headlight to flash and a loss of the LCD
0x07 Causes headlight to flash, LCD is still working, MPH is lit.
0x08 None
0x09 Causes headlight to turn off, LCD is still working, MPH is lit.
0x0A Causes headlight to flash and a loss of the LCD
0x0B Causes headlight to flash and a loss of the LCD
0x0C None
0x0D Causes headlight to turn off, LCD is still working, MPH is lit.
0x0E Causes headlight to flash and a loss of the LCD
0x0F Causes headlight to flash, LCD is still working, MPH is lit.

Discussions