18 channels for DSM2 / DSMX ?

vlad_vy wrote:

These extra options will not fit in Devo7e RAM:

rbe2012 wrote: I think you can force the right values to be shown directly, not only after revisiting the page. I'll have a look later.

I was on the wrong track. The values are changed outside the protocol option page - no need to force something.

Vlad, is there a direct dependancy of the values? Esp. is the resolution a changeable option or given by the DSM2/DSMx-protocol and the number of channels used? If so I would not show this as an option.

And what about Devo10? There are enough user inputs to control additional channels...
We should introduce a "#define HAS_DSM_XCHANNELS" or similar in the target_defs.h files and add the X-channel code conditionally.

Hi. How about the Devo8? It has 18 inputs excluding trims.
Regards, David.

...and Devo10.

I see no reason why we should add more differences between the deviation implementations than what is necessary from a technical /ressource view. If such a feature is usable shall the user decide. It will cost more to maintain the differences.

I can imagine a config where X-channels are used, but not all regular channels (X-channels are for switching lights and gears, was writetn somewhere). So the number of inputs needed may be less than the highest used channel number.

I would like Devo8S if you can do it. Happy to test too. May I ask how you have implemented X1 and X2? Are they 9bit copies of Ch11 and Ch12?
Thanks, David.

Thanks. I've seen reference to 20 channels so I assume you've implemented this as 1-12 normal + X1-X8. It is my understanding that Spektrum only send data for 18 channels with X1/X2 the same as Ch11/12 but with different resolution. I don't think this is a problem; just seeking clarification.
Regards, David.

Vlad i do have a Devo10. I think there are not enough inputs to need x-channels, but i can test it should it be necessary.


In the "final version", what do i have to do to get xchannels enabled?

As I have written here or in my repo: if you choose values which start with a number and change the values, they are changed in steps (of 1 if both values < 200, 10 above) so you will have a very long way from 1024 to 2048.
But you are right, should be shorter. BTW: leading blanks do not help...

I think this is because something is changed when the channel number field is calculated (maybe in numchanselect_cb()?).In this case there can be a difference in Devo8 where the channel number field is visible and Devo10 where it is not.
If you send me the code I can have a look.

Didn't you make any changes outside of dsm2.c?