Advanced Search

New test build - 82c3a77 . I decided to go back to 6659b95, apply non-timing changes, and make one minor change to data handling. As far as I can tell this build behaves just like 6659b95. Please let me know how it is for you. The only problem I see is retries when loading parameters, with more retries at slower packet rates.

I would've preferred 2.4G but it's not in stock at the places I usually buy from. I just ordered one from a place I've never heard of - we'll see how that goes. Good excuse to build a new quad.

6659b95 on 250Hz bad/good is 0/251 and on 500Hz it's 0/501. The 6659b95 seems to run smoother yet superfast while flying but that could be imaginative cause I have had no issues with it and love it.

You should buy a 2.4Ghz module. Superfast and crazy range.

On 1610498 the menu shows on all packet rates except 500Hz.

Testing without model match is fine for now. Need to get the other issues worked out.

One concern is that bad/good is 0/340 at 500Hz. The good needs to be at 500, otherwise packets are being lost. Can you please check what it shows on 6659b95 when the packet rate is 500Hz? Set the rate to 500Hz, then exit the menu, wait a couple seconds, then go back into the menu to check. I'll also look at adding the "good" value to telemetry so we can see what it is during normal operation. It may only be dropping packets while transferring the parameter data so it may not be a flight issue.

I'm very puzzled why 1610498 wouldn't work as the only changes were removing the debug beep and always running the serial port at 1.87Mbps. You said the CRSF menu doesn't show - does the build work other than that? Does the menu show up at lower packet rates?

Thanks for the offer but unfortunately I'm not in The Netherlands . I'm in the US. I did look into running my module at 500Hz and I think I'll try that. The serial packet rate is tied directly to the air packet rate so not sure what it'll do to the TX. It may not run and if it does I doubt it will connect to the receiver.

I'm hopeful we can get everything working at 500Hz. I've got a couple optimizations in mind but they're not quick to implement.

I am not testing model match now because the connection is not stable yet. Is that ok?

Do you think this is going to work? Maybe I can send you a 2.4Gz ELRS module to develop 500Hz on? Do you perhaps live in The Netherlands?

Ah bad/good I didn't look at because it was always showing the same. On 7d14d15 shows good/bad 0/±250 on 250Hz and 0/±340 on 500Hz.

When 250Hz shows in the menu while 500Hz was actually selected I see good/bad 0/±340. When I try to switch to 500Hz the menu keeps showing 250Hz. When I switch to 150Hz the menu actually switches to 150 and good/bad shows 0/±150.

On 1610498 the CRSF menu doesn't show

Failsafes and telemetry not working are not good. Was there any strange behavior on the T8 screen or with the buttons after these incidents?

The flashing when you go on the device page happens because the screen is repainted as the parameters are received from the TX (or other CRSF device). These packets are received at the same rate as the packet rate, so lower rates take longer. For the TX it's a little over 1K of data.

The issue with the 250/500 packet rate display apparently wrong is puzzling. I can think of a couple of possibilities though neither seems likely. First a question though - when you say " packet rate shows 250 while 500 is selected" do you mean the bad/good ratio shows 0/250 while the packet rate is 500? or that the packet rate config box shows 250 when you know the last time you left the menu it was 500?

If it's the first case it's because the bad/good ratio is not updated while on the device page. If you enter the page at 250, change to 500, then look at the bad/good ratio it will still show 250.

The other way I could see this happening is if the setting is changed while the parameters are still loading. This should be almost impossible in practice, but be sure the screen stops flashing and the LOADING tag on the top line disappears before navigating the menu. I'll look into disabling the buttons until all parameters are loaded.

For the issue of starting up with throttle warning the info about 250 and 500 behavior suggests something to try. My mention of opentx was just to note that the hardware it runs on has a different power-up behavior than Jumper hardware in that with Jumper the TX powers up immediately even if no serial data is being sent from the T8. Maybe that interacts with the TX baudrate detection in some way that causes a problem. Also the baud rate change that Deviation does may be involved. I'd like to be able to just set the baudrate in Deviation instead of trying to detect when the module is ELRS, but since the protocol options are taken over by the CRSF pages there's no good place to put a baudrate selection.

From what I can see in the code ELRS keeps trying different baud rates forever, but maybe there's a timeout somewhere that depends on packet rate. Easy enough to test. Please try test build 1610498 . This build has the baudrate fixed at 1.87Mbps, instead of elevating to that rate only when ELRS module is detected.

When I tested this build there was a strange behavior with model match. I had model match on with the previous version of Deviation, installed the build above, and powered on the T8. The RX LED started flashing the model mismatch code. I went to the 900TX device page, turned model match off and the RX connected, then I turned model match back on. Next I changed Deviation back to the previous build, which bumps the datarate from 400K to 1.87M when ELRS is detected. Again the model ID setting was lost! Finally I changed back to the test version above, but this time model ID was not lost! Still puzzled about this behavior.

I asked about voice because when I have voice enabled I never hear any beeps. I assume the beeper is disabled.

The high throttle on boot issue only occurs on 250 and 500Hz. On 50 and 150Hz it behaves normally.

I have RGB on the TX that behaves the same as yours. When I keep high throttle it will go into wifi mode and the led turns green. When I boot with low throttle WiFi mode doesn't enable.

I have looked at OpenTX once and I think it sucks so any OpenTX remark doesn't mean a thing to me.

That's good news! Guess it makes sense that 500Hz is more sensitive to timing. Though the timing correction values coming from the TX are larger now than before the change, though now positive instead of negative.

Voice support is not required for the beeps.

When the throttle warning is active at power-up Deviation doesn't start the protocol code until the warning is cleared. I'm not sure why that would affect the TX connecting to the RX. Unfortunately I cannot replicate this behavior with my ES900 modules. As long as I drop the throttle to zero before the devices go into wifi mode, the TX and RX connect and RX shows solid green. Maybe there's some difference between 2.4 and 900 here.

Can you see the RGB LED on the TX? What is it's behavior? On mine it's flashing orange until I drop the throttle, then turns solid blue at the same time the RX LED goes solid.

There is a difference between opentx/edgetx handsets and Deviation handsets here. The opentx/edgetx devices have control over the power to the external module, and do not apply power until all power-on safety warnings have been cleared. With the Jumper handsets the firmware can't control the power and the module is powered up when the radio is turned on. Not clear how that might play a part.

When switching between packet rates I get RSSI telemetry warnings. So it seems that connection is gone/weak for a moment but not seconds I guess. The RX led stays solid.

I have flashing menu buildup. When I enter the ELRS menu the menu flashes a few times. The lower the packet rate the more often the menu flashes.

I flew 4 lipos on quads this afternoon with 7d14d15. During the third flight the connection dropped twice (failsafe) and rebooting T8 reestablished the connection.

Sometimes when I reboot the T8 and go into the ELRS menu package rate shows 250 while 500 is selected. After reboot 500Hz usually shows again and sometimes after reboot shows 250Hz.

I installed 7d14d15 and it seems to work perfectly on 500Hz and all other packet rates. I have voice audio so I'm not sure I would hear chirping?

One issue I noticed is that the TX doesn't reconnect to the RX when booted with throttle high.

1. install 7d14d15.
2. Throttle low.
3. Boot T8
4. TX connects to RX, RX led solid.
5. All works well.

1. install 7d14d15.
2. Throttle mid-high..
3. Boot T8. RX led blinking slow.
4. Ch3 is high warning pops up. RX led blinking slow.
5. Lower throttle, popup disappears. RX led blinking slow.
6. ELRS menu gone.
5. Need reboot T8 with throttle low to connect.

Another issue I noticed that in 1 scenario the telemetry didn't work but RX was connected. No RSSI nothing. I can try to reproduce that again later.

Test build available - 7d14d15 . This has some test code to compensate for a small packet timing change. That's the main suspect I found by comparing 2ef012c and 6659b95, although it's so small I don't think it could be the problem but we'll see. One other piece of debug code in the build is a beep on serial data errors. If the T8 starts chirping that's what it is.

As you noticed when you change a parameter the new value is only sent to the TX when navigating away from the selector. When I change the packet rate more than half the time the receiver disconnects, sometimes taking several seconds before reconnecting. Do you see that same behavior if switching between working lower packet rates, like 25 to 250? Wondering if both radios behave the same.

The same rithm as when I turn off the transmitter and RX loses connection. Slow steady.

Thanks, this is all great information.

When the RX LED is blinking it is green? What is the flash pattern? Slow steady, fast steady, some number of flashes then a pause, etc?

On 500Hz the 2ef012c doesn't work.

1. Set 500Hz with previous version.
2. Flash 2ef012c
3. Reboot T8
4. Sometimes it connects to the RX and then after a few seconds disconnects again. RX led is sometimes solid for a few seconds but then blinking.
5. Checking ELRS menu, ELRS menu is gone.
6. ELRS not working anymore and only fix is to flash previous version.

On 500Hz the 2ef012c doesn't work.

1. Set 250Hz with previous version.
2. Flash 2ef012c
3. Reboot T8
4. Connect RX, all working, RX led solid green.
5. Cursor to packet rate. all working, RX led solid green.
6. Use left and right keys to move around on values, 50-500Hz, keep 500Hz. All working, RX led solid green.
7. Use up down keys to move cursor away from packet rate. RX led NOT solid green but blinking.
8. Move around ELRS menu seems to work.
9. Cursor to packet rate. RX led NOT solid green but blinking.
10. Use left light keys to move around on values, 50-500Hz, keep 250Hz. RX led NOT solid green but blinking.
11. Use up down keys to move cursor away from packet rate. RX led NOT solid green but blinking.
12. Move around ELRS menu seems to work. RX led NOT solid green but blinking.
13. Leaving ELRS menu, ELRS menu is gone. RX led NOT solid green but blinking.
14. Reboot T8. Sometimes it connects to the RX and then after a few seconds disconnects again. RX led is sometimes solid for a few seconds but then blinking.
15. Checking ELRS menu, ELRS menu is gone.
16. ELRS not working anymore and only fix is to flash previous version.

Yes, it's fine to keep using that local build. No changes were needed in the RX.

Seems there's a problem at 500Hz, the one thing I can't test with my 900MHz module. Maybe I can enable 500Hz in a local build for testing.

To be sure I understand the issue, with 2ef012c the connection is lost immediately after changing to 500Hz in the CRSF device page in the T8? If you use 6659b95 to change the packet rate to 500Hz then upgrade to 2ef012c, does it work as long as you don't go into the CRSF config page or just not work even right after power up?

In 2ef012c the Bind button doesn't do anything.

I'm still using my ELRS local build of the #1372 pull request for the TX but not RX. Is that ok?
I see it has been merged into master.

For modelmismatch a popup would do I guess.