PPM issues (Was: It's time for a 2.1 release?)

More
11 Dec 2012 11:55 - 11 Dec 2012 11:56 #3872 by vlad_vy
Replied by vlad_vy on topic It's time for a 2.1 release?
Maybe more safe will be to have 2 subset of PPM, standard 8 channel PPM-OUT (for outer modules) and PPM-SIM? Without PPM config options.
Last edit: 11 Dec 2012 11:56 by vlad_vy.

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

More
11 Dec 2012 13:29 #3873 by PhracturedBlue
Replied by PhracturedBlue on topic It's time for a 2.1 release?
Nah. The defaults should be fine for everyone using a Sim (especially since you need to calibrate in a sim anyway). Only in the case you need an external module may you need to tweak the values.

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

More
11 Dec 2012 13:50 #3874 by domcars0
Replied by domcars0 on topic It's time for a 2.1 release?

PhracturedBlue wrote: Only in the case you need an external module may you need to tweak the values.

Or if you use your deviation Tx as trainer on another radio :cheer:
I've just tested my Devo 10/Deviation (release of last saturday #a8d0315) as trainer on my WK2801 (as master) ...It works, I've just to trims the zero of all channels which are away from the good value.

Devo 10 (+7e) owner. It's mine, please don't touch it with your big fingers :angry:

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

More
12 Dec 2012 15:29 #3922 by vlad_vy
Replied by vlad_vy on topic It's time for a 2.1 release?
Data pulses for different radios
github.com/blutack/paparazzi/tree/v3.9/conf/radios

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

More
13 Dec 2012 02:12 #3966 by suvsuv
Replied by suvsuv on topic It's time for a 2.1 release?

PhracturedBlue wrote: I implemented a config option in the code.
the default is set to match the devo10's normal output.
I also added support for more than 10 channels, though I'm notsure it will actually work.

Let me know if you have further issues. It works fine in Phoenix

Now PPM output can be tweaked for different PPM-FM module, below is test result to generate PPM complied with walkera's TX



As different TX vendors use different setting for PPM output, e.g. Futaba's PPM settings are notch=300us and center+notch=1.5ms, there is no actual PPM standard. I might let the Frame pulse width be configurable between 20000 and 22500m
Attachments:

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

More
13 Dec 2012 04:25 #3971 by PhracturedBlue
Replied by PhracturedBlue on topic It's time for a 2.1 release?
I thought about that, but so far everything has worked fine with the 22.5ms frame rate. should we need to change it in the future it is easy to add.

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

More
16 Dec 2012 07:49 #4027 by vlad_vy
Replied by vlad_vy on topic It's time for a 2.1 release?
PPM frames may be fully specified by:
- Max Frame-Rate: 25Hz - 100Hz (typical 50Hz) => Min-Frame-Width: 40ms-10ms (typical 20ms)
- Min Frame-Sync: 2.0ms - 5.0ms (typical 2.5ms)
- Channel-Separator: 200us - 500us (typical 400ms)
- Channel-Polarity: +/- (typical +)

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

More
16 Dec 2012 13:37 #4038 by PhracturedBlue
Replied by PhracturedBlue on topic It's time for a 2.1 release?
I think I'll wait until after 2.1 to modify this. I've fronzen all string changes for the release, and I don't think this is worth waiting for all strings to get synced again.

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

Time to create page: 0.058 seconds
Powered by Kunena Forum