Why can't you set the RC_SPEED you want?

Posted by Paxmax on July 4, 2013 at 12:39pm

I've been posting my problems before, regarding what FW to use.

One reason I was thought I need newer FW was because I couldn't write my RC_SPEED parameter, so I thought I must have downloaded a too old or incompatible FW.

But lo and behold when I get exact same behaviour with new 2.9.1b FW.

I wanted 400Hz cuz that's what plushes can do, but no, saveing parameters fail.

...but this time I started testing several options and some numbers I can save some I can't save -I get "set RC_SPEED failed"

For instance 380, 381, 382, 383, 384 are ok. If I click "arrow up" from 384 it should increase it to "385" but it won't, it will still read "384" but the save will fail!

Add another click and it will read 385, and still save will fail.

The next at all working/saveable number is 402 + one click, and the "real visual" 403 works too.

It would help with some kind of explanation? is it some weird internal MCU frequency division that screws it up?

It would be handy if the GUI/instructions supported same idea then.

Also clicking the arrow up and arrow down in GUI makes it jump a different amount of steps per click.

What sayeth the experts?

You need to be a member of diydrones to add comments!

Join diydrones

Email me when people reply –
Follow

Replies

  • Developer
    Randy July 4, 2013 at 1:35pm

    Paxmax,

         Looks like a mission planner issue.  It's possible to update the RCSPEED to whatever you want via the advanced parameters list (the full list with every parameter on it).  Could you raise an issue in the mission planner's issues list so Michael O can have a look at it?

This reply was deleted.