RC control: Roboteq not translating pulse input correctly

6 years 10 months ago #29528571 by allen
Hi all,

I have a HDC2450 controller, controlling a motor on each channel for my robot. I have for the past month been able to use RC/pulsewidth control to move the robot.

This past week, however, roboteq for some reason is not outputting commands correctly, for one direction on one channel.
For example,
1) pulse input 1 is mapped to motor command 1.
2) pulse input 2 is mapped to motor command 2.
3) In roboteq, moving the joysticks on my RC controller gives the correct signal ranges under the "Pulse In" fields, for both inputs (the range is about [1100, 1900], centered at 1500)
4) 1100 on pulse input 1 maps to -1000 for motor command 1; 1900 on pulse input 1 maps to 1000 for motor command 1.
5) 1100 on pulse input 1 maps to -1000 for motor command 2; 1900 on pulse input 2 maps to a maximum of 70 for motor command 2.

I've switched and checked the wiring for the pulse inputs, but the same problem persists: no matter what the wiring configuration is, pulse input 2 always maps to a very asymmetric motor command range. This seems to me to be a roboteq driver problem translating pulse input 2 to motor command (my configuration for pulse inp1 is identical to pulse inp2). I have also updated the firmware, but the problem persists.

Any help please?

Thanks,
Allen

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

6 years 10 months ago #29528572 by Griffin Baker
Did you try resetting your controller to defaults? Check your range values set for your RC inputs. By default they are set to 1000, 1500, 2000. May be possible it may have been set to 1100, 1500, 1900.

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

6 years 10 months ago #29528573 by allen
Hi Griffin,

Could you tell me how to do the resetting? I haven't configured the RC input range before, and it's always been around 1100, 1500, 1900 (back when it worked).

Thanks,
Allen

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

6 years 10 months ago #29528574 by Griffin Baker
Connect controller to the Roborun+ PC utility. Then in the configuration tab, click on reset to defaults on the right side of browser.

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

6 years 10 months ago #29528575 by allen
Hi Griffin,

Resetting it to defaults have indeed solved the problem. So you're saying my problem happened because either I accidentally changed the RC input range values, or it got corrupted somehow?

Thanks,
Allen

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

6 years 10 months ago #29528576 by Griffin Baker
Appears so. What is the firmware version date you are using? In console tab, ?fid in one of the data fields. The in data will tell you the firmware ID and date.

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

Moderators: tonysantoni
Time to create page: 0.738 seconds