By fernlop - Sat Jan 11, 2020 3:59 pm
- Sat Jan 11, 2020 3:59 pm
#18951
I did some more research today with more equipment.
Im sure now that the battery doesn't has any role in this locking / unlocking mechanism. I recorded the traffic between the ESC and BMS. Don't know what "language" they are talking but doesn't look like UART or CAN. When disconnecting the cable that is sending from the ESC to the BMS, nothing happens and everything still works. The other way round it generated an error, of cause, because the ESC can't read the battery level.
So now im pretty sure the ESC really need the code send on every 20th tick. If it doesn't receive it, it will turn off at about 2:06 minutes.
This are the options to solve this problem:
Im sure now that the battery doesn't has any role in this locking / unlocking mechanism. I recorded the traffic between the ESC and BMS. Don't know what "language" they are talking but doesn't look like UART or CAN. When disconnecting the cable that is sending from the ESC to the BMS, nothing happens and everything still works. The other way round it generated an error, of cause, because the ESC can't read the battery level.
So now im pretty sure the ESC really need the code send on every 20th tick. If it doesn't receive it, it will turn off at about 2:06 minutes.
This are the options to solve this problem:
- Decode the code that is sent every 20th and be able to regenerate it
- Reprogram the ESC (Found out its a STM32F103C8T6 Chip and will try this)
- Buy a new ESC and be able to connect it to the original components like Display, SpeedControl, Brake, Motor
- Dirty solution: "Reboot" the ESC just before the 2:06 Minutes and use relays on the 3 motor cables to block the wheelblocking just while rebooting. ( Will test this)