I am experiencing something similar. I am on beta 0.20 from buba's Google Drive. I was running it for about 2000km without any problems.Minatauro wrote: ↑Dec 14 2019 1:21pmHi,
I just swapped out a broken torque sensor for a brand new one, however, there is no assistance from the motor now when peddling. The vlcd5 is fine and has no error codes. I tried the walk assist to test the motor and that is not working. If the display is working does that mean the controller is ok? The torque sensor is new and the wires seem to be ok on it. I can't figure out why it's not giving assistance. Had anyone experienced this before?
Since two days, the display starts up correctly, but sometimes the lights do not come on (I have the setting that the lights should be on after start). When this is the case, also the motor does not start at all. Voltage, cadence and speed readings are working. I can change the assist levels. But when I switch the lights, only the display light switches, and no motor assist whatsoever, also no walk-assist.
I do not have e-brakes, but today I saw once that the e-brake sign was shortly on. Could that be the reason?
In other cases, the e-brake sign was not on at all, and the motor had the same behaviour.
Sometimes, after a while the lights come on and then the motor also works as expected for the whole trip until I shut it down again.
A couple of questions:
If, for some reason the e-brake pin is giving the wrong reading during bootup, could this lead to the described behaviour?
Could we add a function to disable the ebrakes completely in the software?
Is there any other thing which could prevent the motor to give assistance?
Another theory is that there is something in the code, i.e. could it be that there is a buffer overflow or similar? I will re-flash the bike this weekend to check if that is the case.