Its bent... more bent than a roundabout. Someone probably stacked it into a curb and is still recovering in hospital.
It looks like the mudguard hits the deck. Definitely not right!
I WOULD NOT ride that.
An Electric Scooter Community on a Mission to Stamp out Transportation Mediocrity.
yeswhat478 wrote: ↑Fri Jun 14, 2019 5:15 amIts bent... more bent than a roundabout. Someone probably stacked it into a curb and is still recovering in hospital.
It looks like the mudguard hits the deck. Definitely not right!
I WOULD NOT ride that.
fieldc0llapse wrote: ↑Mon Apr 29, 2019 5:47 pmHere's a little contribution by me aswell. Scooter is SZ2.5. Voltages appear on dashboard, after you short the blue wire from the green gps cable, to 36v, and led on controller starts blinking, and a momentary tick can be heard from the front wheel motor. The logic is the following: Green box receives the server signal to start the scooter after transaction is complete etc etc, it shorts the blue wire to 36V to enable the controller. After the controller is enabled, the TX2 pin which can be seen in the pictures is going from 4.3V to ~5V and down to 0V, and is trying to speak to the green box. I think the green box is only replying with an "ok" type signal like 0xFF or something similar, and not with a special "code" which is bound to the specific scooter. I think the scooter identification is solely done on the green box side, since it's the one that communicates with the servers and therefore with the user application. The STM32 on the controller has the same program on every scooter, and expects a simple talkback from the green box saying "start". Honestly, i think @orac12 has done an excellent job finding that "ok" reply that the greenbox will send to the controller and is not lying at all. Props, will try to find that ok code aswell