expressLRS

That's good news. Yes 458a87e is fine for testing.

How is the CRSF menu with other devices? My crossfire nano rx sometimes doesn't show on the CRSF config page until I scroll down. Looking at the serial data it just seems slow to respond.

Ah yes. Often the device names don't show until the cursor hits the menu element.

I haven't seen anything else disturbing. I'm going to fly tomorrow.

The GPS telemetry shows some numbers but they are not close to the same as what I see in iNav and goggle OSD and are not the location.

I'll need to set up some GPS telemetry to look into that, unless maybe you can make a data capture? Is this a new behavior or GPS telemetry was always like that?

Test build 051dab03 is available. This has a fix for the issue where a newly discovered device did not appear on the CRSF config page until an up/down press. Now the name will show up when the device info message is received. My nano rx responds a lot faster after changing the packet rate from Dynamic to 150Hz.

Today was my first flight with ELRS on a wing with GPS. I only have ELRS for a week. I never used a module before just the internal 4 in 1. GPS telemetry from an frsky type receiver worked well.

I don't know how to set dynamic packet rate. I only see an option for dynamic power in the menu.

There might be an error in the conversion of the CRSF gps telemetry. I'll look at it in the coming days.

The data rate setting is on a Crossfire receiver.

New devices now show in the menu. Just very rarely it does not.

Thanks. Sounds like maybe a race condition to chase down. I went ahead and merged the current PR as it's much better than it was.

Test build 3663db7 is available. Fixes the GPS latitude and longitude display.

I don't get a GPS lock inside and the weather is crap. In the weekend the weather will be better and I will test the GPS telemetry in the field.

Test build is updated - cd4e656 . PR #1023 has the changes. GPS fix is also included in the build.

Received my ELRS module and learned a few things. Noticeable is a fix to scrolling the device menu.

ELRS has a special message to update the bad/good packet status and connection status (in opentx shown in upper right corner by the lua script). Not sure how best to use it, if at all. The bad/good is also in the main menu list - could have a button press update that value. Exposing it as telemetry data is another possibility. Maybe put it on the top line while in the device menu, though it may overwrite part of the device name. Suggestions?

If you are able to expose the good/bad ratio it would be helpful. Unfortunately OpenTX has somewhat set the standard for UI so suggest we follow their lead to avoid confusing new users who will see OpenTX and expect Deviation to work the same way.
Thanks for getting the eLRS module, really appreciate the time you are putting into this!

hexfet wrote: Test build is updated - cd4e656 . PR #1023 has the changes. GPS fix is also included in the build.

Received my ELRS module and learned a few things. Noticeable is a fix to scrolling the device menu.

ELRS has a special message to update the bad/good packet status and connection status (in opentx shown in upper right corner by the lua script). Not sure how best to use it, if at all. The bad/good is also in the main menu list - could have a button press update that value. Exposing it as telemetry data is another possibility. Maybe put it on the top line while in the device menu, though it may overwrite part of the device name. Suggestions?

I've got something in the Menu now bad/good 0/501. I don't know what it is. In the telemetry I have a lot of telemetry fields showing values that say something about connection quality. I don't know which one to use.
If it's possible to put a telemetry alarm on good/bad it may be useful to add it to the telemetry data.

I'm flying tomorrow and will check the GPS telemetry.

Oooh, megabauds?

github.com/DeviationTX/deviation/pull/10...9de11a2d5d558c54a92d

1.87Mb/s?

GPS telemetry works. I fly fpv so I don't know how to test good/bad. I have rssi in osd.

The bad/good numbers are basically the number of bad and good packets received in a second. Should be 0/configured packet rate. It refers to the link between Deviation and the tx module. The radio telemetry is the correct thing to monitor for the air link.

I've merged the gps fix. Thanks for the testing.

New test build is available 835b547 . As belrik noticed the serial data rate is bumped to 1.87Mbps if the module is detected to be ELRS. This rate works well on my t8sg. Please let me know how it works for you.

Model match is enabled. Set the fixed id in the model to a number 0-63. Click on Re-Init after this change, or power cycle the t8sg. Follow the ELRS procedure for setting the receiver. I'm not sure I've worked out all the details, but it's basically having the receiver connected, the tx module Model Match parameter set On, and then set the fixed id. When I mess up and can't connect to the receiver then turning the module parameter Off restores the connection after cycling power.

I think I have time again Wednesday to try the new build.

I read somewhere ELRS packet rate can go up to 1KHz. Is this the goal of the new baud rate?

mooiweertje wrote: I think I have time again Wednesday to try the new build.

I read somewhere ELRS packet rate can go up to 1KHz. Is this the goal of the new baud rate?

It would help enable higher packet rates but the goal of higher baud rates was to spend less time transmitting each packet from the radio to the module. Think of each stick update like a download, a higher transfer rate allows the stick data to reach the module quicker each time. The savings amount to a latency reduction, I think 0.5ms latency saving was given as an example.
Search "megabauds" for more information.

Problems sleeping so I flashed the 835b547 and it seems to work perfectly.

Tested Model match and it is working but it's behavior doesn't make much sense. I set the id to 11 and the next time I check the id in the RX it's 0. I've also lost connection between Deviation and the TX.
I would be afraid to use it how it works now.