An Electric Scooter Community on a Mission to Stamp out Transportation Mediocrity.
I'm pretty sure it's 05e, although it does look like a 06e from that pick. for good measure does anyone know what a 05 & 06 errors mean? or any recommendations for how I could find out? cuz I can't find sh*t online
Leon Kolaric wrote: ↑Fri Jul 08, 2022 8:49 amI sent you PM
How do you explain this:Bug_meh wrote: ↑Tue May 25, 2021 10:21 amM20001 wrote: ↑Sun May 23, 2021 6:23 pmI dont think you have a chance to be succesful with this, as far as I know, the conversion between greenbox and ESC is secured over challenge - response, google for it if you dont know what it is. the only way would be to reflash the combox with a firmware from a older one, but I dont know how to dump and then flash the firmware of the combox.
Ok, to recap (for people to follow) :
1. The unclocked firmware works only if the scooter has a combox with the version V184.108.40.206 not with version V220.127.116.11
2. We can't downgrade the combox version from V18.104.22.168 to V22.214.171.124 because we don't know how to dump/flash the combox.
3. We can't subsititue the combox V126.96.36.199 with something that will emulate the combox V188.8.131.52 (like an arduino) because cannot analyze the the communication between the combox and the controller, due to some Challenge-response authentication security measures.
4. The MCU is still flashable on newer version of the GEN 3(just add header pins yourself)
Ok, now here is another idea which might be more feasible...
What if we use the Blue Pill development board which seems to have the exact same MCU (STM32F103C8T6) as on the Lime Gen 3 Controller's board, to write a completely new firmware ?
I know that we don't have the schematics of the controller but, we can still reverse the PCB itself.
Here is how I see the thing :
1. We take a Breadboard, we put the Blue Pill in the middle.
2. We identify the circuits on the board that handle the motor, we replicate this circuit on the breadboard (using the exact same components). Making sure that we use the same pins one the dev-board's MCU as on the original MCU.
3. We implement this circuit on a brand new firmware. Once we are able to control the motor with the MCU. we can then skip to the next feature.
4. We then add the throttle support, again making sure that we use the same pins on the MCU.
At some point, we will probably also need to have more infos about the motor like the datasheet to make it spin trough software. Maybe not, I don't know if the motor is standard or not.
The goal here is to tackle to problem in a incremental manner, piece by piece, step by step, feature by feature.
We clone piece of the hardware, implement the logic in the firmware, then we move on to the next piece. Until we've replicated the hole controller.
We can then inject this new firmware into the original controller and if all goes well.... it should work ?
This way we can even get ride of the combox, and it will be a cross version working solution. no matter which version of the scooter is. Since all GEN 3 are flashable.
Do you think that could work ? Or should I stop dreaming ?
Connect with cmsis dap And use arterytek isp. […]
Hello!if i want to upgrade by ST-Link V2 STM8 ST[…]
Hello anyone know something about this DRV? Tha[…]
anyone know what the pinnout is on the BMS f[…]