Frsky D8 Telemtry

Hello,
To Day im converting some of my Sailplanes from Taranis to Deviation.
Im using most Time Alt and Vspeed from the High prez. Vario ( the original Frsky Version )
Now i found some Things:

8 Channels only
Alt shows High over Sea Level
Vspeed is not implemented


Can some one please insert the same Telemetry Code like the FrskyX Protocol ?

Alt is going to Zero at Power up
VSP is the Vario Climb Rate
DIS is discharge with Amp Sensor
12 Chanel SBUS
....

If some one needs Testing, i can do it.
I have Amp Sensor, Vario,D8r,D4r,SBUS to PWM, Senso Hub with normal Altimeter ,AD2 Divider.

greetings Alex

SBUS is receiver-sided, that can't be added on the transmitter. Same with the channel count.. with 8 channels, the PPM signal is "full". A receiver modification would be needed to add more.

Oh, yes there i was wrong with the SBUS.
D Series do not have the SBUS Port.

Alex, are you testing with the FrskyX test build? The telemetry changes there should be in Frsky protocol as well - they share the decoding code now. I did not change the AD2GAIN in Frsky though.

Oh, nice.
I was using a spare Tx and do not have seen it, time to flash it with your Frskyx Build

Thank You

I'm interested in your findings Alexandro, I want to convert my fleet to Frsky and waiting for a DR4 and vario from Hobbyking for testing (Singapore post sucks big time )

@blackmoon

i used the FrskyX Build to get the Telemetry for Frsky D8, but it does not work.
All new Telemetry Numbers do have a Black Background on Main Screen and showing 0.
I write some o.t Infos for hexfed at the FrskyX Post.
Maybe he can make some Changes to get it to work.
I use many D8R and D4R with Altimeter Vario on my Sailplanes and try to Change most of them to DeviatonTX.

greetings Alex

Alex, which tx are you using for the D8 testing? As with D16 the 7e only supports the rx telemetry, not hub. Are the RSSI and Volt1 values shown correctly?

The D8 telemetry seems to work fine in the emulator, so might need to make some debug versions for testing.

Hello,
i was using the Devo 10 with ver 070

RSSI and Volt1 is ok, but the other things do only show 0 and black Background.

Same on Devo 8S

greetings Alex

Found an error in the D8 telemetry state machine - hope it's the problem.

The FrskyX test build is updated - 8e0 1bb.

Edit: test build updated with new 320x240 (color screen) telemetry test page.

Hello,
Test Ver. 1bb on DEVO 8s

Nice Telemetry Test Screen !

Alt is most Time Jumping around , 52, 24, 42 and so one ( some error at getting the right conversion ? )
Amp is most tim ok (0.5, 0.6 <- is it doing double the original ? same at FrskyX -> 250 is around 600 at Display) but some times it jumps up to 700,1200, 72

Dis is ticking and looking good ( with the to high Amp it is not showing the right Number, but i looks it does the calc. good )
Vsi is the same as Amp

greetings Alex

-> should we do the debug here or want You have it on the FrskyX Post ? hexfed

Test build frskyx3 is updated - 278.
- Hub telemetry reworked based on opentx

The code in opentx was different than the documentation I've found online which was different from the old frsky code. Let's see how this looks before looking at the VOLTA difference. This may even fix that depending on what sensor IDs are being received. Would you mind listing the sensors you have hooked up?

If the values are jumping around it's likely a different issue than if they just have the wrong value.

Two new hub telemetry items are added - VARIO (VSI), and VFAS (VOLT3). Not sure if VFAS is different than the "amp sensor" but it has a different ID.

Probably best to continue the discussion here so it's clear this is about D8 and hub telemetry.

Hello,
Test Ver. 278 on Devo 8s, D8R
Volt1 and RSSI looks good

all other Data are some times good and then jumping again.

i am using for testing:
FAS-100
Vari-H ( High prez. Altimeter ) as Hub for FAS-100
1/10 Divider for Volt2 ,for Testing Volt2 without the Vario ( it uses Volt2 for sending the Climb rate )

can get a FAS-40 for testing

greetings Alex

Thanks Alex. Answers to these questions may help narrow it down.
1) Can you confirm you're only seeing values for the sensors you're using - all the other boxes are red with unchanging values, even when the sensor values jump around?
2) When the jumping occurs, does it happen to all the values at the same time or different sensors at different times?
3) When the jumping occurs, do the values stay close to the correct number, or does it seem random?
4) Does the Volt2 value stay steady, or does it jump around?

Also would you try FrskyX and check the VoltA and Amp readings there? Those values will be coming through the same decoding code.

One thing I haven't brought in from the opentx code yet is to only accept split sensor values (bp.ap) if they're received consecutively in sequence. Can add that tonight, but it's probably just there for the case of dropped packets. The opentx code also applies averaging to some of the sensors.

The Volt2 value comes from the same place in the packet as Volt1 so I'd expect the same behavior. If not that can rule out some possibilities.

Hello,
Test Ver. 278 , Devo 8s, D8R, Vario High Prez.,FVAS-100.

i have a Video where You can see it, it is hard to describe whats going on.

www.dropbox.com/s/s03noblkqpzt40l/d8r.mov?dl=0

the jumping is coming like Waves, You see it at Video


Test on FrskyX:
VoltA shows exact the input Voltage from the FVAS-100 and stay without any jumping
the AMP is showing 0.5 / 0.6 and no jumping, it is the same as on all working FrskyX Builds

Thanks! Video is very helpful.
Frskyx3 test build is updated - 209.
- Fixed error in indexing that caused last two bytes of telemetry packets to be skipped
- Only update baro altitude and amp sensor voltage if bp.ap parts received in order

The first item may fix the jumping around. Or it could be something else From the video seems like the same few erroneous values were being displayed.

The best info I found on D8 over-the-air packet format was this post . Anyone know of more detailed info, or SPI captures?

Hello,
Test VER.209, Devo 8s, D8r

it is doing the same Dance
VoltA is showing 11 Volt ( this is the right Number) and the it jumps to 499 at some Time and later back to 11
Alt 2.4 , then 22.4 and then to an other wrong Number
the other Numbers doing same Things.

it looks like the Data Stream does not match the Data Fields some Time and blead into the wrong
neighbor Field, where it gets then wrong calculated

all other are red like same as on video

greetings Alex

Thanks Alex - appreciate your patience

I think you're right about data being written to the wrong place, but have not spotted the bug yet. Still looking but want to try something else at the same time.

I've put a special test version here for the devo 8s. It should save received telemetry packets into the datalog.bin file. It will start recording when telemetry is received, and can save about 20 seconds of data. No need to make any datalog settings on the tx. I've included an empty datalog.bin file in the zip for you to copy to the filesystem so it's a known starting point. So the test procedure is:
1) install the test dfu, then boot to usb mode and copy the datalog.bin file to the 8s
2) connect to the receiver (no need to rebind if already bound)
3) check that telemetry is being received
4) after 30 seconds power off the tx, boot to usb mode, and copy the datalog.bin file and post here

I doubt the data is the problem but want to be sure and it will be good to have some real test data.

This test dfu is not for flying! I tested it with another protocol on my devo10 and the datalogging worked, but it might cause issues...

Hello,

the Datalog.bin, i renamed to Datalog.txt to upload it here





greetings Alex

Great, it worked mostly Thanks

Did the jumping around symptom occur during the recording?