- Forum
- Roboteq Motor Controllers
- Controller Configuration & Operation
- Issues after upgrading firmware
Issues after upgrading firmware
6 years 9 months ago #29532594
by pugwng
Issues after upgrading firmware was created by pugwng
Hi. I have a FBL2360 and it was working fine with version 1.6 for some months.
Yesterday I upgraded the controller firmware to version 1.7 (onboard of the machine). After that, started to configure motor options in Configurations Tab, once clicked to save to controller, the motors suddenly started to move/spin for less than a sec, and the circuit breaker from batteries opened. When I turned it on again, the Roborun's Run Tab flaged "Undervolt" (as expected since I kept the switch/contactor opened at VMOT). I removed the controller from machine, and powered it by a much smaller (12v Lifepo4) battery. If I just power it through GND and Pwr Ctrl, it works, and I can see it on PC. But if I also connect the two VMOTs, the controller drains the battery and shuts-off. What could be happening? Could a simple "saving to controller" cause such issues at power stage?
Yesterday I upgraded the controller firmware to version 1.7 (onboard of the machine). After that, started to configure motor options in Configurations Tab, once clicked to save to controller, the motors suddenly started to move/spin for less than a sec, and the circuit breaker from batteries opened. When I turned it on again, the Roborun's Run Tab flaged "Undervolt" (as expected since I kept the switch/contactor opened at VMOT). I removed the controller from machine, and powered it by a much smaller (12v Lifepo4) battery. If I just power it through GND and Pwr Ctrl, it works, and I can see it on PC. But if I also connect the two VMOTs, the controller drains the battery and shuts-off. What could be happening? Could a simple "saving to controller" cause such issues at power stage?
Please Log in or Create an account to join the conversation.
6 years 9 months ago #29532595
by blake
Replied by blake on topic Issues after upgrading firmware
In short, updating to the latest firmware would not cause such a thing to happen. Please attach your configuration file along with microbasic script if using one. If you'd prefer you can send these files to me at This email address is being protected from spambots. You need JavaScript enabled to view it..
Please Log in or Create an account to join the conversation.
Moderators: tonysantoni
- Forum
- Roboteq Motor Controllers
- Controller Configuration & Operation
- Issues after upgrading firmware
Time to create page: 0.052 seconds