New FrSkyX protocol

Hello,
Test Ver.255

System lock up at boot and Beeps

greetings Alex

My bad - built with the wrong compiler. New test version here . I also removed the static qualifier so this should be equivalent to the 739 build. I verified this build is the same as produced by building with the docker image and will continue to do so until I get this merged to github.

Thanks for the testing!

Hello,
Test Ver. 187

Bind works on Channel Number set greater 8
PWM out 1-8 does not work , only working on Channel Number set to 8 or lower

greetings Alex

Test report : version '187'. With x4r-sb , sp-r-f3 , devo 7e .

I've got bind, solid green light, tested 12 channels first, nothing moves in cleanflight,
then changed to 8 channels - works but pitch and roll are changed.
when adding more channels e.g.9 - ch 1 stops working. 10-ch2 , 11-ch3 , 12-ch4

Waiting for the next version to test

ouch...let's tack downwind a little bit. I've moved to github and building with PB's docker image.

The frskyx bitbucket 739 changes are build dfcf1e0 in github. The frskyx code is the same as the bitbucket 739 build, but also the latest nightly changes are included. Fingers crossed this works on the 7e - not making any more predictions :/ Test version here .

If that works I've also made a second test version with some additional changes that should not affect the 7e. Version 8e903ef .

Thanks for the testing and patience!

Hello,
Test Ver. dfc

Bind : ok
-> green light on RX does Flicker, no Servo moving
-> Channel Number 8 and 12 , all same. No Movement and Green Light Flicker

Test Ver. 8a9

No Boot, only Beep and Clear Screen with Backlight on.

greetings Alex

TEST. For me both versions : 'dfc' and '8e9'

After the flash Devo keeps restarting, there is no logo on the screen, just sound and blinking. There is a bootloop.

Reverted back to 739 and works fine. @hexfet , can you tell me if I can fly with 739 firmware now ? I just finished my new build and wanted to use x4r receiver.
What is missing in the firmware ?

Thanks for your work!

I am definitely not understanding something about the 7e build. Compared assembly listings for both dfc and 8e9 and the generated code is identical except for the version number. That's consistent with darker44's report but Alex got different behavior.

Let's do a sanity check. I've created a protocol_frskyx3 test build 8e9 with versions for 10, 6, 8, and 12. Please test if you can to make sure the move to github/docker was successful.

darker44 wrote: Reverted back to 739 and works fine. @hexfet , can you tell me if I can fly with 739 firmware now ?

It's not missing any features. Using Deviation is always subject to the warning on the front page of www.devationtx.com . That said, if everything looks fine in cleanflight, if it was me, and my build was a CF quad that won't get damaged much, I'd be comfortable hover testing at a few feet - over soft grass I'd do a full-power range check before any flying.

I haven't kept up with these new versions, but I can tell you that the old one I am still using worked great at range, doing acrobatics, etc.. zero issues, RSSI also working. So my guess is that if you have a working version (for the main protocol) now, it'll be fine for actual flight.

Arakon wrote: I haven't kept up with these new versions, but I can tell you that the old one I am still using worked great at range, doing acrobatics, etc.. zero issues, RSSI also working. So my guess is that if you have a working version (for the main protocol) now, it'll be fine for actual flight.

Hey Arakon, can you tell me what version are you using ?

Thanks hexfet anyway, so I'm waiting for people to test other DEVO receivers now, and I'm always happy to help with 7e testing.
I will test flying with working version also.

I'm using 15e8960, that was one of the releases just before work on the telemetry stuff began, I think. I unfortunately don't have the file anymore, which is why I am reluctant right now to test any other versions.
I'm using it with an X4R-SB and an XSR receiver, btw.

Edit: Actually found the dfu file and put together the file system stuff needed I think.. I've attached it if you want to try.
This is from early march, though.. keep that in mind.

I just tested frskyx3 with devo 10 and devo 8s.
all 12 channels work fine. i got rssi and voltage to rx. Also used a lipo sensor (smart port) gives total voltage and voltage of 2 cells, Plus an extra box with unknown voltage witch gives strange readings. (i guess a small glitch)

Tom

i also tested the dfc and 8e9 on the 7e.
with both versions: white screen beeeeeep and power of. (by it self)

Tom

TomPeer wrote: I just tested frskyx3 with devo 10 and devo 8s.
all 12 channels work fine. i got rssi and voltage to rx. Also used a lipo sensor (smart port) gives total voltage and voltage of 2 cells, Plus an extra box with unknown voltage witch gives strange readings. (i guess a small glitch)

Tom

Thanks for testing. Glad it's working

Can you describe the location of the extra box, or post a screenshot?

the box with the numbers in the black. Although this time it stays with this number but it also had the number 0.77.

That is the minimum cell voltage. The black background means no lower value has been reported in the previous five seconds.

If you saw a value of 0.77 it implies a spurious low value might be reported, maybe as things are powering up. Might need to update the code to reject values less than 2V or so.

thanks, good to know. Than all seems to work fine.
Good work.

Hello,
Test Ver. 8e9 on Devo 8s

Rssi ok
Volt1 ok
PWM 1-8 ok

looks good
doing deep Test later

greetings Alex

The protocol_frskyx3 test build is updated with version 61e, including a build for the 7e. Might have found the 7e issue...

The min cell is now updated by scanning all the cell values whenever cell telemetry is received. Might see 0 flash up until all cells have been reported at least once through telemetry.

Hello,
Test Ver. 61e on Devo 7e

Beeps and does not Boot


greetings Alex