Advanced Search

Sounds like progress. One thing I've had trouble with calibrating my t8sg is that the left stick down position is a little uncertain. If I pull down too hard during calibration, I never get the stick down that far in normal operation. Not sure if that might relate to the pulsing. I re-routed the cables behind the gimbal which did help.

So I connected with someone on the Betaflight discord and he got me through the throttle channel issue. Now on BF all looks good, but it still won't arm. Then I noticed that the throttle channel seems to be pulsing and going over the threshold so I don't know what is going on. Going to try a different battery in my tx and see if it still acts that way. He had me calibrate and that is when the throttle channel started pulsing.

I think it needs to be below the stick low threshold on the receiver page. Haven't messed with my bf settings recently. Should be info online.
Be sure you've calibrated your transmitter.

It says throttle channel is too high.

Yes, the mod is still needed. That can't be solved with just firmware..

You're welcome.

On the BF setup page there's an Info box on the right. The first line lists the things that are currently keeping the quad from arming. Everything in the box has hover help.

Hi, I just built the recent firmware for my carbon fiber t8sg v2 and I was wondering if I still need to do the pin mod to get elrs to work. Thanks!

I really appreciate the input -

Checked the mixer page for arm switch and it makes the expected change when toggled. Checked the channel monitor and it also makes the expected change when toggled.

And confirmed switch still works with another quad that is bound to the tx.

Going to look further in bf settings but not sure what to look for. I read something about having the modes set up correctly or it won't arm too. But I think the mode channel was properly set up - but again I am new to this.

Check the mixer page for the arm switch and verify the display makes the expected change when toggling the switch. Maybe it's a bad switch.
Check the channel monitor to make sure the expected channel change happens when toggling the switch.
If that works then don't know why it wouldn't show up in bf. Try using a different channel for arming.

When connected to bf all switches (and sticks) respond to input from tx EXCEPT the arm switch that I set up as a simple switch. Thoughts?

Great, thanks for reporting back.

I've merged the pending PR and the fixed id change so the Deviation master branch is the latest (and same as the latest test build). I put a "nightly build" in the Test Build section on deviationtx.com. Still working on the CI build changes.

hexfet wrote: New test build is available - 5889e07 . This build sends a model id of 0 to ELRS if the Deviation Fixed ID is greater than 63. I'll probably make a change to the UI so it's only possible to set a CRSF fixed id in the range 0-63 but UI changes take more time.

From looking at the ELRS code I learned the situation is a little different than what I thought. The fixed id of 255 meaning model match is off only applies to the RX. When sending a model id to the TX it should always be in the range 0-63.

Now I get the normal 500Hz default for my models, which is what I would expect when not using Model Match. Thanks.

New test build is available - 5889e07 . This build sends a model id of 0 to ELRS if the Deviation Fixed ID is greater than 63. I'll probably make a change to the UI so it's only possible to set a CRSF fixed id in the range 0-63 but UI changes take more time.

From looking at the ELRS code I learned the situation is a little different than what I thought. The fixed id of 255 meaning model match is off only applies to the RX. When sending a model id to the TX it should always be in the range 0-63.

That seems reasonable and is easier than making warning dialog. I am curious why ELRS has the feature of not storing settings if model id is 255 (or maybe anything over 63). I'll look at that code's history.

Thanks, confused as to why model ID was in play, thought it was left as default... Guess default is not 0 like I expected.

hexfet wrote:

LAM_FPV wrote: Hi i have tested the last version everything works good. The only problem i have is that the module restart all my settings when i reboot the transmitter. Rate. Telemetry power etc... any idea ?

I have betafpv 1w tx betafpv rx elrs 2.2.0
Thanks !

Interesting! I had not noticed this behavior before but I think it's consistent with the description on the ELRS Model Matching page . If your model's Fixed ID is outside the range 0(None)-63 then this explains the behavior you're seeing. I can duplicate the behavior on my HappyModel ES2400TX.

For Fixed IDs from 0-63 (Deviation displays 0 as None) the ELRS Model Matching feature is in effect. The doc at the link above says that even if the Model Match setting is Off, ELRS stores some parameters based on Fixed ID, with up to 64 sets of parameters. For Fixed IDs outside that range ELRS boots up with the default parameter settings.

Try changing the Fixed ID to something in the range None-63 for each of your ELRS models. It's fine to use the same Fixed ID in multiple models if you don't use Model Match and do want the models to use the same ELRS parameter settings.

Also want to mention there is a fix in ELRS master branch that may also be needed, though if the Fixed ID change works then the ELRS fix will only help the menus load faster. The ELRS change will be included in the 2.3 version.

When you say it responds to stick movements do you mean you see channels changing on the receiver page in Betaflight? If so then that probably means it's bound.

What's required for arming in your Betaflight configuration? If it's a particular channel and you can get that channel to the right value on the receiver page then it should arm.

Maybe just lower the value to 63 when elrs is selected? Is not ideal but works and is less confusing.

belrik wrote: Testing on 2.4g with eLRS 2.2. latest deviationTX build linked above.

Connection defaults to 150hz which is not correct for 2.4g systems, every time I put in a new pack the connection is set to 150hz.
Anytime the RX restarts the TX is defaulting to 150hz, I believe the prior packet rate should be retained (as on EdgeTX).

Sounds like the same thing as described in my previous post. Change your model's Fixed ID to 63 or less. ELRS saves some TX settings even when not using Model Match, but only for model id's 0-63. For CRSF Deviation treats any Fixed ID over 63 as 255. ELRS treats this as "no model id defined" and doesn't store settings in that condition.

I see that EdgeTX only allows the model id (Receiver) to be set 0-63, so it's never the "off" value. That's probably a good UI choice. There may be some users that want to change settings but not have them saved past the current power cycle. But judging by these two questions it seems mainly to cause confusion. I'll think about a change.

Testing on 2.4g with eLRS 2.2. latest deviationTX build linked above.

Connection defaults to 150hz which is not correct for 2.4g systems, every time I put in a new pack the connection is set to 150hz.
Anytime the RX restarts the TX is defaulting to 150hz, I believe the prior packet rate should be retained (as on EdgeTX).

WOW ! proud to say that now everything works perfectly ! My problem was an fixed ID problem. I put 1 on fixed ID and now everything is OK ! Thank you so much !

It seems like 400k and 1.87M bitrate work well, wich one do you advice to use ?

Ok for the 2.3 i will flash it as soon as it will be released !