Strange rpm behaviour HBL2350

8 years 8 months ago #29527065 by GreenTeamTwente
Hi all,

After testing with the HBL2350 for a while I have encountered a strange issue:

When I set the Max RPM in closed loop modus to 1000, the power level sets the exact RPM as expected.

When I set the Max RPM to a lower value, for example 600, the power level does not set the RPM correctly, as a power level of 500 does not give an rpm of (500/1000)*600=300 but does instead translate to about 175.

Attached are some screenshots of the issue:





Can anyone tell me whats the cause of this issue, as 1000 max rpm does work as expected, or can anyone tell me a workaround that does not involve random guessing of a conversion factor between actual RPM and intended RPM.

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

8 years 8 months ago #29527069 by roboteq
Replied by roboteq on topic Re:Strange rpm behaviour HBL2350
if you set the max rpm to 500 and give a 500 command, then the speed should be 250.

There is a known issue with the roborun chart for some controller models. The speed RPM and speed % channels are swapped. So it may be that you are monitoring the speed% times 10.

Try downloading and installing the latest version.

If the problem is indeed with the firmware, we\'ll need to investigate and fix.

In the meantime, you can keep the maxrpm at 1000 and change your commands to reach the desired speed.

For example, if you need to go between 0 and 500 RPM, limit you commands between 0 and 500.

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

8 years 8 months ago #29527079 by GreenTeamTwente
Indeed setting 500 max rpm and 500 power should result in 250 rpm.

But it does not give the 250 rpm back to the roboteq utility and it does not rotate the motor at 250 rpm: the rpm the roboteq utility reports seems to match the speed of the motor.

This has not been measured scientifically, but has instead been determined by counting the rotations within one minute at said max rpm/power settings.

As setting the max rpm to 1000 does work correctly, i think its an issue with the firmware. Might it be a division in which a float is expected but instead an int is returned? (using 23 pole pairs)

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

Moderators: tonysantoni
Time to create page: 0.154 seconds