stancecoke
Minor legend
Have you tried to do a factory reset (calibrate torquesensor)?
-
Hello ES! We could use some help to get us past the finish line on building the new knowledgebase for the forum.
Can you donate? Please see our fundraising page. Thank you!
FOC Open Source Firmware for Bafang CAN bus controllers with GD32F303 processor
- Thread starter stancecoke
- Start date
Avatarkhorn
Established
Yes, I’ve tried it. Most parameters get reset, but not 3203. The values I tried to write appear there, but they aren’t actually stored in the controller. I also tried loading the original firmware header into the controller and setting the rest of the values to FF (to overwrite the existing data). After loading a normal EBiCS firmware, the problem is still there. BESST and BESST Pro can’t read this data either when using the EBiCS firmware. With the original firmware, this parameter block reads and writes normally.
stancecoke
Minor legend
Hm, I have to check this, but I can't test it with a M560, as I don't have one any longer.
Avatarkhorn
Established
Most likely, there’s no need for further testing. My controller is indeed behaving strangely. For example, it keeps supplying voltage to the display (any display, any firmware) even after being turned off — the display then shows error 30 due to a lack of data.
In the end, I managed to write the “3203” parameters using the original firmware and then flashed the rest with Ebics. So, I’ll be able to use the motor until I replace the controller.
P.S: This response (and everything above) refers to the M510 FC 3.0 motor and controller.
After comparing the M560 and M510 motors, I like the M510 better. It’s quieter, legally compliant, noticeably lighter, and powerful enough for my needs.
Last edited:
stancecoke
Minor legend
Hm, this has no effect on the values, that EBiCS is using for the 3203 parameters. EBiCS is using the default parameters from the config.h on the very first install. After that it reads the values from the virtual EEPROM.
I'll check it later!
stancecoke
Minor legend
I tried it on the M215, as it is on my workbench at the moment and the CAN communication is identical to the M510/M560 branch. For me it works as expected. The values can be read and written and the last setting is present after a restart of the controller.
But I recommend to reload the Canable GUI in your webbrowser (use the reload button of your webbrowser) after writing and then read the parameters again, to make sure, that you read the latest data really.
Last edited:
