Break Problem
6 years 10 months ago #29532196
by robotian
Break Problem was created by robotian
I bought 3 of FBL2360 and I'm using 2 of FBL2360 for mecanum based robot.
I connect D_SUB I/O refer to manual and it's operation is good.
But one of driver has something wrong.
This driver operate front left and right motor.
If motor rotation is started, break is released.
If motor is stopped, and then the break is on.
The problem is that when left motor is stopped and break is on, right motor is break is on concurrently, even it is on rotation.
If right wheel is stopped, the left wheel is run normally.
So, I change to another driver, the problem is solved.
Could you tell me how can I fix this driver?
I connect D_SUB I/O refer to manual and it's operation is good.
But one of driver has something wrong.
This driver operate front left and right motor.
If motor rotation is started, break is released.
If motor is stopped, and then the break is on.
The problem is that when left motor is stopped and break is on, right motor is break is on concurrently, even it is on rotation.
If right wheel is stopped, the left wheel is run normally.
So, I change to another driver, the problem is solved.
Could you tell me how can I fix this driver?
Please Log in or Create an account to join the conversation.
6 years 10 months ago #29532200
by blake
Replied by blake on topic Break Problem
Do both controllers have the same firmware? Please tell me the version/date of firmware that is on the controllers, this can be seen in roborun in the bottom right corner.
Do both controllers have the same configuration? Please send copy of the configuration files of your two controllers, clearly label which one is from the misbehaving controller.
Which pins are your brakes connected to on the 25-pin dsub?
Do both controllers have the same configuration? Please send copy of the configuration files of your two controllers, clearly label which one is from the misbehaving controller.
Which pins are your brakes connected to on the 25-pin dsub?
Please Log in or Create an account to join the conversation.
6 years 10 months ago #29532206
by robotian
Replied by robotian on topic Break Problem
Do both controllers have the same firmware?
-> Yes, it's same.
Please tell me the version/date of firmware that is on the controllers, this can be seen in roborun in the bottom right corner.
-> Roboteq v1.5 FBL2XXXX 10/01/2015
Do both controllers have the same configuration?
-> Absolutely Yes.
Please send copy of the configuration files of your two controllers, clearly label which one is from the misbehaving controller.
-> OK. look attathment
Which pins are your brakes connected to on the 25-pin dsub?
-> Pin18 for ch1, Pin6 for ch2.
Let explane again.
I had 3 of FBL2360(FBL1, FBL2, FBL3).
I installed FBL1, FBL2 on my mecanum vehicle.
The FBL1 had braking problem(which I told you). But FBL2 was working well.
It is defferent between them only CANOpen node ID.
I load profile from FBL1 and save to FBL3.
I installed FBL3 and it's working well.
-> Yes, it's same.
Please tell me the version/date of firmware that is on the controllers, this can be seen in roborun in the bottom right corner.
-> Roboteq v1.5 FBL2XXXX 10/01/2015
Do both controllers have the same configuration?
-> Absolutely Yes.
Please send copy of the configuration files of your two controllers, clearly label which one is from the misbehaving controller.
-> OK. look attathment
Which pins are your brakes connected to on the 25-pin dsub?
-> Pin18 for ch1, Pin6 for ch2.
Let explane again.
I had 3 of FBL2360(FBL1, FBL2, FBL3).
I installed FBL1, FBL2 on my mecanum vehicle.
The FBL1 had braking problem(which I told you). But FBL2 was working well.
It is defferent between them only CANOpen node ID.
I load profile from FBL1 and save to FBL3.
I installed FBL3 and it's working well.
Please Log in or Create an account to join the conversation.
6 years 10 months ago #29532208
by blake
Replied by blake on topic Break Problem
Thank you for your reply. The attachment for your configuration file did not work, when loading attachments to this forum they must be in .zip format. Or you can just send it to me directly at This email address is being protected from spambots. You need JavaScript enabled to view it.
Regardless of that you do have an outdated firmware on your controllers. Please contact me at the above email address so that I can send you an updated firmware.
Regardless of that you do have an outdated firmware on your controllers. Please contact me at the above email address so that I can send you an updated firmware.
Please Log in or Create an account to join the conversation.
6 years 9 months ago #29532210
by robotian
Replied by robotian on topic Break Problem
I would send you a E-mail.
I wish my e-mail find you.
Thank you.
I wish my e-mail find you.
Thank you.
Please Log in or Create an account to join the conversation.
6 years 9 months ago #29532211
by robotian
Replied by robotian on topic Break Problem
I update new firmware and FBL1 is working well and brake problem is solved.
So I update all driver. But FBL2 has problem. there is fault message "UnderVolt" and "DefConfig"
FBL2 doesn't work. Then I check the system and there is no hardware problem.
What's wrong with that?
So I update all driver. But FBL2 has problem. there is fault message "UnderVolt" and "DefConfig"
FBL2 doesn't work. Then I check the system and there is no hardware problem.
What's wrong with that?
Please Log in or Create an account to join the conversation.
6 years 9 months ago #29532213
by blake
Replied by blake on topic Break Problem
The DefConfig LED is okay, that shouldn't cause a problem. The UnderVolt LED is usually shown red when there is only power being applied to PWRCTRL and not VMOT. Do you have power applied to VMOT? If so what voltage? If you do have power on VMOT and above a reasonable voltage (>12V) then try resetting the controller default configuration and that Undervolt should go away. Then you can reload your configuration file to the controller.
Please Log in or Create an account to join the conversation.
Moderators: tonysantoni
Time to create page: 0.101 seconds