- Posts: 85
expressLRS
- mooiweertje
- Offline
It got it working. Making the change in the source tree and build it using the local tab. I now have a full menu in Deviation. Thanks guys!
Please Log in or Create an account to join the conversation.
- mooiweertje
- Offline
- Posts: 85
Please Log in or Create an account to join the conversation.
- mooiweertje
- Offline
- Posts: 85
Please Log in or Create an account to join the conversation.
- belrik
- Offline
- Posts: 94
Please Log in or Create an account to join the conversation.
- mooiweertje
- Offline
- Posts: 85
Please Log in or Create an account to join the conversation.
- belrik
- Offline
- Posts: 94
mooiweertje wrote: The display shows 12V but voice says 1.2 Volt. I fly FPV so what the display says is less important than what the voice says. Why can I only setup a warning 10V and below? For 4S I need something in the 14V range.
Most FPV pilots would use an OSD warning, which is more flexible and can be configured to alert on a per-cell voltage instead of the overall voltage, so works if you fly 3S, 4S or 6S.
What you have sounds like a general deviation issue, as the telemetry screen is showing the correct information. You might have more luck with a dedicated post in the general section instead of the eLRS thread?
Please Log in or Create an account to join the conversation.
- mooiweertje
- Offline
- Posts: 85
Please Log in or Create an account to join the conversation.
- hexfet
- Offline
- Posts: 1891
Please Log in or Create an account to join the conversation.
- mooiweertje
- Offline
- Posts: 85
Please Log in or Create an account to join the conversation.
- hexfet
- Offline
- Posts: 1891
The test build also has a change that should fix the problem with long names, though a tester on github reported the fix does not work. If you have a chance to test that it would be helpful.
Please Log in or Create an account to join the conversation.
- mooiweertje
- Offline
- Posts: 85
Please Log in or Create an account to join the conversation.
- belrik
- Offline
- Posts: 94
hexfet wrote: Good to hear, thanks for testing. I'll get the changes merged.
The test build also has a change that should fix the problem with long names, though a tester on github reported the fix does not work. If you have a chance to test that it would be helpful.
Yeah, that was me. I am asking if there is some debug I can gather but long names still seem to throw errors. OpenTX processes the names ok.
Please Log in or Create an account to join the conversation.
- hexfet
- Offline
- Posts: 1891
Please Log in or Create an account to join the conversation.
- belrik
- Offline
- Posts: 94
Edit - looks like d0ca763 is the latest commit on your crsf_name branch, I'll test that.
Please Log in or Create an account to join the conversation.
- mooiweertje
- Offline
- Posts: 85
I used ExpressLRS configurator 1.3.3 today and yesterday 1.3.2. The only reason I can think of why today works and yesterday not.
hexfet wrote: Sometimes Here's a test build that addresses the issues you mentioned. Please give it a try.
Please Log in or Create an account to join the conversation.
- mooiweertje
- Offline
- Posts: 85
hexfet wrote: Please try the test build here . Not sure it will work but might have spotted the problem.
Please Log in or Create an account to join the conversation.
- belrik
- Offline
- Posts: 94
mooiweertje wrote: The one I tested yesterday and didn't work, works fine today..... Strange but true... deviation-t8sg_v2_plus-v5.0.0-99811b4 works! I can see all 13 characters in the menu "HM ES24TX Pro". Also Betaflight 4.3 shows up in the menu now.
I used ExpressLRS configurator 1.3.3 today and yesterday 1.3.2. The only reason I can think of why today works and yesterday not.
hexfet wrote: Sometimes Here's a test build that addresses the issues you mentioned. Please give it a try.
Hmm. I believe that the HM modules actually already had their names shortened from "HappyModel ES24TX" in the eLRS project to work around this problem. I was one of the people asking for the change. Now the problem is that many manufacturers have created modules we need >14 characters and there seems to be an error at 14 or longer still.
I've tested the d0ca763 build and that still seems to cause issues, but I cannot see deviation-t8sg_v2_plus-v5.0.0-99811b4 to test that. it's not listed under deviationtx.com/downloads-new/category/2838-hexfet-crsf-test , was that posted to github?
BTW My module name is "BETAFPV 2G4MICRO".
Please Log in or Create an account to join the conversation.
- mooiweertje
- Offline
- Posts: 85
Please Log in or Create an account to join the conversation.
- belrik
- Offline
- Posts: 94
mooiweertje wrote: The 99811b4 is attached to my previous message. Do you use ExpressLRS configurator 1.3.3?
I am using the latest configurator. I am building from local source and I need to edit the TX DEVICE_NAME in the source for the radio to list my TX in the devices page.
Thanks for pointing me to 99811b4, I tried that but the problem persists. It's not a deal-breaker to shorten the device name for me cos I'm happy messing around with Git on the CLI, but for some this will be a show-stopper.
BTW not sure if everyone is aware but there is also a parallel discussion on Github: github.com/DeviationTX/deviation/pull/1020
Please Log in or Create an account to join the conversation.
- mooiweertje
- Offline
- Posts: 85
Suggesting the problem with the BETAFPV 2G4MICRO is not the name length or you are not using the 1.3.3 ExpressLRS configurator which is only 4 days old.
Please Log in or Create an account to join the conversation.
- Home
- Forum
- Development
- Protocol Development
- expressLRS