Replies to This Discussion

DeveloperPermalink Reply by Olivier ADLER on February 2, 2013 at 4:56am

Yes it is compatible with other receivers.

Futur shipments should have a version based on this firmware, with some modifications for a better code portability though different boards (APM 1.x, APM 2.x...)

Changes at this level must be done very carefully and with serious testing, this explain that new versions do not fit production boards without serious team discussions and testing. This take some time.

Olivier

• ▶ Reply

Permalink Reply by avionics on February 2, 2013 at 4:58am

after updating i tested and it works fine no more twitch. well done.

• ▶ Reply

Permalink Reply by Daryl on February 2, 2013 at 11:47am

I have a question for the group and this may be unrelated to this latest upgrade, but since I flashed the AdruPM v2.3.13 fw, I cannot seem to get channel 6 to tune my PID terms.  The APM recognizes channel 6 with a range from 1101 to 1941, but when I set up CH6 to a P term with min=0 to max=3, I note while refreshing the config screen for each turning of the radio dial it remains at the min value until CH6 reaches somewhere between 1353 and 1381 where it then jumps to the max value.  I am not getting a linear setting in between the min and max.

 

Has anyone else experienced this problem or tried the CH6 tuning options since they flashed in the new fw?

• ▶ Reply

DeveloperPermalink Reply by jasonshort on February 2, 2013 at 11:57am

Are you setting your range value in the CLI? Internally these values are stored x1000.

They are converted to floats later in the code. 

Try the CLI setup::range and test::range to do what your doing.

Jason

• ▶ Reply

Permalink Reply by Daryl on February 2, 2013 at 1:08pm

Jason, I couldn't find any documentation on the range command.  When I ran the setup::show I noticed RC6 range was 1379 (min) and 1381 (max).  How those numbers got there, I don't know.  I sometimes get that on PID terms changing too for no reason.  Anyway, went back into PM and ran another radio calibration, then back to CLI setup:show and RC6 had the proper min/max numbers and the channel 6 options are now working.

 

Thanks.

• ▶ Reply

DeveloperPermalink Reply by John Arne Birkeland on March 10, 2013 at 6:39am

To check if you need the latest PPM encoder there is a new RC Jitter test in the source repository.

https://github.com/diydrones/ardupilot/tree/master/libraries/AP_HAL...

Either compile and upload it yourself using Arduino 1.0.3 (Autopilot version) or use on of the pre-compiled files that I have included here, and upload using the "Load custom firmware" option in the Mission Planner.

The jitter test is a APM application, not a PPM encoder firmware. Do NOT try and upload it to the PPM encoder chip using the DFU bootloader.

After a successful upload, connect to the APM board using the Mission Planner Terminal window (CLI) and let the test run for about 30min. Make sure you do not touch the R/C radio while doing the test.

After a while your test should look something like this.

< 00:08:24> -------------------------------------------
ch1: center:1520 min:1516 max:1522 delta:4
ch2: center:1542 min:1539 max:1545 delta:3
ch3: center:1934 min:1930 max:1936 delta:4
ch4: center:1520 min:1516 max:1522 delta:4
ch5: center:1851 min:1849 max:1854 delta:3
ch6: center:1520 min:1517 max:1522 delta:3
ch7: center:1521 min:1519 max:1523 delta:2
ch8: center:2074 min:2069 max:2076 delta:5

If no channel show delta changes above 10, you do not need to upgrade the PPM encoder. If they are much higher (and you are sure you did not touch any of the sticks during the test), you definitively need to update to the latest version (V2.3.16).

Also, you have problems with jitter delta greater then 10, please send me a PM with some details about your radio setup.

Attachments:

• RCJitterTest_APM2.x.hex, 53 KB
• RCJitterTest_APM1.x.hex, 53 KB

• ▶ Reply

• ‹ Previous
• 1
• …
• 8
• 9
• 10
• Next ›
• Page