Menu

Topic-icon Firmware update issue fbl2360

More
3 years 2 months ago #29532282 by Erik
I updated my fbl2360 firmware yesterday, after that the DOUT-1 was called LED in the controller.

My robot worked fine but after an hour one wheel got serious issues and started making strange noises/stalling.

I reset the controller to factory settings, changed all cables and finally it worked properly again.

Now i updated the firmware again but i guess i have another version since DOUT-1 is not called LED anymore.

What is happening or what do i do wrong?

On the Roborun console page i read : Rev 1.6. 7-19-16

Do i have the latest firmware installed now? And if so why is the Dout-1 not called LED anymore?

Please Log in or Create an account to join the conversation.

More
3 years 2 months ago #29532284 by Erik
Replied by Erik on topic Firmware update issue fbl2360
I also have a Dell laptop, see the topic from Scott. And i also have my touchpad going crazy, that happens when the laptop has been used on battery and is charging..when i pull the adaptercable out it works again.

But how can i fix the problem? And is my roborun working properly now?? I don't have another laptop here, yes another Dell.

I almost bought me a new laptop this week because of that adapterproblem, now i know its Roborun which is the problem.

Please Log in or Create an account to join the conversation.

More
3 years 2 months ago #29532296 by blake
Replied by blake on topic Firmware update issue fbl2360

Erik wrote: I updated my fbl2360 firmware yesterday, after that the DOUT-1 was called LED in the controller.


Does this mean that the actual label in Roborun+ showed LED? If this is the case then this must have been a label you changed within Roborun. This has nothing to do with the firmware, these are local label that are saved to the trees of the Roborun Utility.

I am unclear as to if you are still experiencing problems with your motor outputs or not. If you are, please tell me which version of firmware you are using. Are you operating in open loop or closed loop? Are any faults triggering? Any details are helpful.

Regarding the problems you are experiencing with your touchpad, there have been no other reports of this problem happening except for the two reports from you and Scott. It is difficult to determine what is causing this to happen but we suspect it is a laptop or adapter issue.

Please Log in or Create an account to join the conversation.

More
3 years 2 months ago #29532299 by Erik
Replied by Erik on topic Firmware update issue fbl2360
Thanks Blake, in that case i must have renamed the Dout-1 into LED myself. The heat must have gotten me, i 'll turn on the aircon from now on.

I do have a repaired hall cable which might have caused the motor-issue. After swapping the motors the other motor had the same issue...after checking my cable (which was good) all worked fine again but i also had reset the software in the meantime.

I'm still not sure if my notebookadapter is fine or not, it's 5 years old now though and yup it's hot here. When the notebookbattery is 100% charged i never had that issue with the touchpad.

I use the latest version of all roboteq software/firmware from the download section. It does give an error though before upgrading since it can't read my type of controller (over usb-cable) and check if the firmware is good for it...it does install well.

I haven't tried closed loop again, i tried "torque mode" some days ago which made my robot going full speed through the livingroom with my notebook connected by cable...since then i'm scared to try things out and need a good stand to lift the wheels first.
Why does torque mode run without me giving any run command? I still have to study about those modes first before using it.

Please Log in or Create an account to join the conversation.

Moderators: tonysantoni
Time to create page: 0.104 seconds
Go to top