MRPM not recognized by SDC2130

device: SDC2130
firmware: v1.2 12/04/2012 note: I noticed that the link to the firmware on this page says that the date should be 01/31/13, however the link downloads firmware from 12/04/2012.

If I send the command \"~MRPM 1\" the response is \"-\"

In the scripting tab of Roborun+, the line \"MS1=GetConfig(_MRPM,1)\" gives the error \"\'_MRPM\' is not a valid named constant\". The \"_MRPM\" in the line of script is not in purple lettering as it should be.

How can I fix this?

These configuration parameters are working fine: MAC, MDEC, EPPR, EHL, ELL, EHOME.

Another note for Roboteq: In your Advanced Digital Motor Controllers User Manual v1.2 May 10, 2012, you refer to the configuration command \"MACC\" several times (for example, in the description of the Set Acceleration Command on page 165) however the actual command is \"MAC\" with only one C. It is correctly listed as MAC on page 217.

egarms wrote:

device: SDC2130
firmware: v1.2 12/04/2012 note: I noticed that the link to the firmware on this page says that the date should be 01/31/13, however the link downloads firmware from 12/04/2012.

If I send the command \"~MRPM 1\" the response is \"-\"

In the scripting tab of Roborun+, the line \"MS1=GetConfig(_MRPM,1)\" gives the error \"\'_MRPM\' is not a valid named constant\". The \"_MRPM\" in the line of script is not in purple lettering as it should be.

How can I fix this?

These configuration parameters are working fine: MAC, MDEC, EPPR, EHL, ELL, EHOME.

Another note for Roboteq: In your Advanced Digital Motor Controllers User Manual v1.2 May 10, 2012, you refer to the configuration command \"MACC\" several times (for example, in the description of the Set Acceleration Command on page 165) however the actual command is \"MAC\" with only one C. It is correctly listed as MAC on page 217.

The date that the firmware was uploaded to the site is the one you see, but the date that the firmware is labeled is the version that was last validated.

If the return value is \"-\" then the command is not accepted. In Microbasic, if the command is correct syntax, the colors will change over the command; if it doesn\'t, then the syntax is incorrect.

In your case, I believe it would be either
MS1=getconfig(_mxrpm,1)
MS1=getvalue(_mxrpm,1)

I pulled this from page 214 from users manual.

We sincerely apologize for the discrepancy and will update the errata for this error.

You can see what the correct syntax for a command change is by changing a parameter in the configuration tab and the going to console, as it will display the command that it used.