- Posts: 18
Devo-10: 12 Channel Barrier
- lasakro
- Topic Author
- Offline
Please Log in or Create an account to join the conversation.
- Thomas.Heiss
- Offline
- Posts: 698
The internal CYRF module probably is max 12CH??
Please Log in or Create an account to join the conversation.
- HappyHarry
- Offline
- Posts: 1136
Please Log in or Create an account to join the conversation.
- lasakro
- Topic Author
- Offline
- Posts: 18
10.6. Protocol: DSMX
The DSMX protocol is used to control many Spektrum™ and JR™, as well as other models using this protocol. While the DSMX protocol can support up to 14 channels, Deviation is currently limited to a maximum of 12.
Please Log in or Create an account to join the conversation.
- Thomas.Heiss
- Offline
- Posts: 698
Please Log in or Create an account to join the conversation.
- Fernandez
- Offline
- Posts: 983
I also thought that somehow deviation was limited to 12, so is that true?
Please Log in or Create an account to join the conversation.
- HappyHarry
- Offline
- Posts: 1136
Please Log in or Create an account to join the conversation.
- victzh
- Offline
- Posts: 1386
See deviation/src/target/devo10/target_defs.h NUM_OUT_CHANNELS. It is set to 12 now, it should be just a matter of changing it.
Please Log in or Create an account to join the conversation.
- mwm
- Offline
Which actually brings up a third issue. The protocol code may need to be changed to copy values for the extra channels into the outgoing packets.
If someone is interested in actually testing such, I'd be happy to provide a build for a Tx with a specific protocol tweaked.
Do not ask me questions via PM. Ask in the forums, where I'll answer if I can.
My remotely piloted vehicle ("drone") is a yacht.
Please Log in or Create an account to join the conversation.
- lasakro
- Topic Author
- Offline
- Posts: 18
I'd be happy to test such a build.
Please Log in or Create an account to join the conversation.
- hexfet
- Away
- Posts: 1892
I think for FrskyX you'd just need to change the value returned by the PROTOCMD_NUMCHAN case. Probably should be 16 anyway, but never checked if values greater than NUM_OUT_CHANNELS would cause problems.mwm wrote: Which actually brings up a third issue. The protocol code may need to be changed to copy values for the extra channels into the outgoing packets.
Please Log in or Create an account to join the conversation.
- mwm
- Offline
lasakro wrote: @mwm,
I'd be happy to test such a build.
What transmitter and what protocol? I don't have anything an Rx to test with, I'm just offering to build one for someone who can but can't do the build.
Do not ask me questions via PM. Ask in the forums, where I'll answer if I can.
My remotely piloted vehicle ("drone") is a yacht.
Please Log in or Create an account to join the conversation.
- lasakro
- Topic Author
- Offline
- Posts: 18
Devo 10, DSMX please sir. Thanks.
I'll check back more frequently, I promise.
Please Log in or Create an account to join the conversation.
- mwm
- Offline
This is a Devo10 build based on the 5.0 release. If you're running that, you can just install the dfu. If not, use the 5.0 release file system with this. Nightly build file systems might work, but I'd rather not introduce extra variables. Which is also why I used 5.0 release.
I've bumped the overall max channels to 16, because that's where we are heading. However, the DSMX code only had obvious places for 2 extra channels, so you get 14 channels for it. This was done blind, so I had to guess about where they would go, and Spektrum may have taken things in a completely different direction, so don't be surprised if it doesn't work at all.
After making sure your original 12 channels still work, try them both at once. I may have cross-connected them.
And I did learn something: there's more that has to change than just the NUM_OUT_CHANNELS define for the Tx. The datalog stuff has to change a bit as well. PBR set things up so that changing the datalog format breaks the build, so the version number gets updated.
Do not ask me questions via PM. Ask in the forums, where I'll answer if I can.
My remotely piloted vehicle ("drone") is a yacht.
Please Log in or Create an account to join the conversation.
- lasakro
- Topic Author
- Offline
- Posts: 18
1) I was running 5.0
2) Installed dfu from above.
3) Now in Mixer only channels 1 and 2 configured. 3-12 are all set to none.
4) Reloaded current model file, no change.
5) Loaded different file, no change. Not reading model files.
6) Configured manually in mixer ch's 3 and 4 as Thr & Rud.
7) Configured manually in mixer ch's 5-14 all Simple and Src=Aux4.
Eight) All 14 channels on Devo 10 Mixer Page, as a group, responded as programmed. Didn't check 1 for 1.
9) In Mission Planner ch's 1-8 responded as programmed.
10) Scope on ch's 9-14: 9-11 responded as programmed, 12-14 were dead (Flat line, no PWM).
Let me know when you have another one to try.
Please Log in or Create an account to join the conversation.
- lasakro
- Topic Author
- Offline
- Posts: 18
Please Log in or Create an account to join the conversation.
- hexfet
- Away
- Posts: 1892
I haven't updated the datalog code yet so please don't use that feature. Tested with t8sg and XSR receiver SBUS output. All 16 channels worked fine. Channel monitor screen worked as expected. Haven't tested other features.
Please Log in or Create an account to join the conversation.
- Hined1
- Offline
- Posts: 1
Please Log in or Create an account to join the conversation.
- hexfet
- Away
- Posts: 1892
Test builds are updated (3880781). Updated the datalog version, and the conversion utility to support 16 channels. Tested the datalog with 16 channels. Recording and conversion both worked fine.
Please Log in or Create an account to join the conversation.
- hexfet
- Away
- Posts: 1892
Please Log in or Create an account to join the conversation.
- Home
- Forum
- General
- General Discussions
- Devo-10: 12 Channel Barrier