DSM2 Reports

magic_marty wrote: here is what the model file looks like...


name=Model7
type=plane
[radio]
protocol=DSM2
num_channels=6
fixed_id=654321
tx_power=100mW

[channel1]
template=simple
[mixer]
src=THR
dest=Ch1

[channel2]
template=expo_dr
[mixer]
src=AIL
dest=Ch2
[mixer]
src=AIL
dest=Ch2
switch=AIL DR
scalar=60

[channel3]
template=expo_dr
[mixer]
src=ELE
dest=Ch3
[mixer]
src=ELE
dest=Ch3
switch=ELE DR
scalar=60

[channel4]
template=expo_dr
[mixer]
src=RUD
dest=Ch4
[mixer]
src=RUD
dest=Ch4
switch=RUD DR
scalar=60

[channel5]
template=expo_dr
[mixer]
src=GEAR
dest=Ch5

[trim1]
src=LEFT_V
pos=TRIMLV+
neg=TRIMLV-
[trim2]
src=RIGHT_V
pos=TRIMRV+
neg=TRIMRV-
[trim3]
src=LEFT_H
pos=TRIMLH+
neg=TRIMLH-
[trim4]
src=RIGHT_H
pos=TRIMRH+
neg=TRIMRH-
[timer2]
type=countdown
time=10
[safety]
Ch3=min - replace with Auto=min
[gui-qvga]
trim=4in
barsize=half
box1=Ch3
box2=timer1
box3=timer2
bar1=Ch1
bar2=Ch2
bar3=Ch3
bar4=Ch4
toggle1=ELE DR
tglico1=1
toggle2=AIL DR
toggle3=RUD DR
tglico3=2
toggle4=GEAR
tglico4=4

There IS a safety section in there.
Replace "Ch3=min" with "Auto=min"

magic_marty wrote: here is what the model file looks like...

name=Model7
type=plane
[radio]
protocol=DSM2
num_channels=6
fixed_id=654321
tx_power=100mW

[channel1]
template=simple
[mixer]
src=THR
dest=Ch1

[channel2]
template=expo_dr
[mixer]
src=AIL
dest=Ch2
[mixer]
src=AIL
dest=Ch2
switch=AIL DR
scalar=60

[channel3]
template=expo_dr
[mixer]
src=ELE
dest=Ch3
[mixer]
src=ELE
dest=Ch3
switch=ELE DR
scalar=60

[channel4]
template=expo_dr
[mixer]
src=RUD
dest=Ch4
[mixer]
src=RUD
dest=Ch4
switch=RUD DR
scalar=60

[channel5]
template=expo_dr
[mixer]
src=GEAR
dest=Ch5

[trim1]
src=LEFT_V
pos=TRIMLV+
neg=TRIMLV-
[trim2]
src=RIGHT_V
pos=TRIMRV+
neg=TRIMRV-
[trim3]
src=LEFT_H
pos=TRIMLH+
neg=TRIMLH-
[trim4]
src=RIGHT_H
pos=TRIMRH+
neg=TRIMRH-
[timer2]
type=countdown
time=10
[safety]
Ch3=min
[gui-qvga]
trim=4in
barsize=half
box1=Ch3
box2=timer1
box3=timer2
bar1=Ch1
bar2=Ch2
bar3=Ch3
bar4=Ch4
toggle1=ELE DR
tglico1=1
toggle2=AIL DR
toggle3=RUD DR
tglico3=2
toggle4=GEAR
tglico4=4

Here is a new release that should fix the brownout issue and support > 7 channels. It is only very lightly tested due to my lack of DSM2 hardware at the moment.
www.deviationtx.com/forum/5-news-announc...-dsm2-telemetry#2445

After testing (with Spektrum AR6210, JR RD921):
1) Binding and brownout detection working normally.
2) Any channel not working at all.
3) Reboot for exit from USB page (russian interface) solved.
4) Telemetry info now updated at main page.
5) Font for Telemetry page (Volt1,2,3, Temp1,2,3,4, RPM1,2) will be better make black. White color difficult to see.
6) Mixer page (with Russian interface): if displayed small font (assigned switches), I can see numbers only. Next channel also display buttons with small font (I cann't see this font with russian interface). If channel have not assigned switches, next channel will display buttons with normal font.

Example:
[1-THR] THR [Expo&DR] FMODE1 FMODE2
[2-AIL] AIL [Expo&DR] MIX1 MIX2
[3-ELE] ELE [Expo&DR] MIX1 MIX2
[4-RUD] RUD [Simple]
[5-GEAR] GEAR [Simple]

With Russian interface:
[1-THR] THR [Expo&DR] 1 2
[2- ] AIL [ & ] 1 2
[3- ] ELE [ & ] 1 2
[4- ] RUD [ ]
[5-GEAR] GEAR [Simple]

With test build b5b5461b2ff7 I havn't problem with small font for buttons, only with small font for assigned switches.

I've updated build so that DSM2 channels work. Try to grab the new version.
It isn't surprising that you can't see the small-font. It does not contain the cyrillic characters. I'll need to think about how to handle that.

The telemetry stuff is not yet complete.

I understand issue with small font and russian language, but why small font appears on buttons?

I've tested new build (fc31fd71caa8), only 4-RUD channel working properly, others 1-7 channels working incorrectly - vibrate, respond after long delays and so on, 8-9 channels don't working.

I'm not clear on what you mean.

Did you test #channels =6, 7, 8, 9?(make sure to rebind each time)
is it the same in all cases?
what Rx are you testing with? Sorry, my reading comprehension isn't very good.

I've had reports that it is at least basically functional. Until I have replacement DSM2 hardware, I'm quite limited in what I can test myself.

Edit: I've fixed the issue with the fonts on buttons. It'll be in the next release

Spektrum AR6210
At 6 and 7 channels mode, all working fine. At 8 and 9 channels mode, any channel not working at all.

JR RD921
At 6 and 7 channels mode, all working fine. At 8 channel mode, 1-7 channels working incorrectly - interrupted movement, 8 channel don't working. At 9 channel mode only 4-RUD channel working properly, others 1-7 channels working incorrectly - vibrate, respond after long delays and so on, 8-9 channels don't working.

I see at DSM.txt:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
A packet consists of a Tx ID + upto 7 channels of data
each 16bit data value is defined as:
10bit:
a 0 bbbb cccccccccc
11bit:
a bbbb ccccccccccc

a: 0 for 1st data packet, 1 for 2nd data packet
bbbb: the channel number of this packet
cc..: 10 or 11bit channel data (MSB 1st)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

At other source I see:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Data from a tranmitter with 10 bit resolution has the form:
[F 0 C3 C2 C1 C0 D9 D8 D7 D6 D5 D4 D3 D2 D1 D0]

Data from a tranmitter with 11 bit resolution has the form
[F C3 C2 C1 C0 D10 D9 D8 D7 D6 D5 D4 D3 D2 D1 D0]
where :
0 means a '0' bit
F: Normally 0 but set to 1 for the first channel of the 2nd frame if a second frame is transmitted.
C3 to C0 is the channel number, 4 bit, matching the numbers allocated in the transmitter.
D9 to D0 is the channel data (10 bit) 0xaa..0x200..0x356 for 100% transmitter-travel
D10 to D0 is the channel data (11 bit) 0x154..0x400..0x6AC for 100% transmitter-travel
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Good catch. The docs you mention are correct. I improperly documented DSM.txt (and then subsequently implemented it incorrectly). This likely explains the 8/9 ch issue.

For some reason 11bit mode also didn't work reliably, so at the moment, I'm only using 10-bit mode. I probably won't dig into that until my DSM2/X hardware arrives.

I've updated the dfu and filesystem again at the above link:
www.deviationtx.com/forum/5-news-announc...2-telemetry-update-2

Make sure to grab both the fs and the dfu, and update the config.ini file (in the media dir)

This release is my attempt to work with >7 channels. Of course, I can't actually test it myself.

I cann't find in DSM.txt what data used at unused channels.

"14 bytes - up to 7 channels (16 bit word per channel) with encoded channel number, channel value, the "2nd frame in a sequence" flag. Unused channels have FF FF instead of data bytes."

true, I didn't document it, but that is already coded in the protocol. I'll make sure I add it to the documentation

Test with 87729ce290cb build

Spektrum AR6210
At 6 and 7 channels mode, all working fine. At 8 and 9 channels mode, 1-6 channels working incorrectly - vibrate, interrupted movement, respond after long delays and so on. But now, at 8 and 9 channel mode, Rx respond.

JR RD921
At 6 and 7 channels mode, all working fine. At 8 channel mode, 1-7 channels working incorrectly - interrupted movement, 8 channel don't working. At 9 channel mode only 4-RUD channel working properly, others 1-7 channels working incorrectly - vibrate, respond after long delays and so on, 8 channel don't working, but 9 channel now working with interrupted movement.

It's not related to DSM2, but I found at dsm2.c - build_bind_packet()

#if DSMX
packet[12] = num_channels < 8 ? 0xa2 : 0xb3; ??? 0xb2 ???