Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: T-Echo Critical Fault #7 after changing Positions settings #3699

Closed
muchomustacho opened this issue Apr 22, 2024 · 3 comments
Closed
Labels
bug Something isn't working

Comments

@muchomustacho
Copy link

Category

Other

Hardware

T-Echo

Firmware Version

2.3.4.ea61808 Beta

Description

I'm on the latest iOS app and the latest stable firmware (2.3.4.ea61808 Beta). When I import my channels and I go to change their position settings (make them Precise Location or change the Approximate Location) I get a Critical Fault #7 error on the screen.

I'm able to send and receive after I get this setting but when I restart the device, the error goes away but I'm unable to send any messages. They all time out. I can go and make a change on one of the channels and it gives the error again but then I'm able to send messages.

Only workaround I've come up for the error to go away and then keep the settings is set it up just the way I need it, then test I can send and receive and then do a reflash of the firmware, that seems to take care of it.

thumbnail_Image

Relevant log output

No response

@muchomustacho muchomustacho added the bug Something isn't working label Apr 22, 2024
@caveman99
Copy link
Member

caveman99 commented Apr 22, 2024

"The channel tried to set a radio setting which is not supported by this chipset, radio comms settings are now undefined" - Please make sure the T-Echo actually fits the frequency range you wanna use and don't tinker with the radio settings too much. e.g. don't change frequency slot or offset if you don't know what you are doing.

Closing this, if problem persists even on default settings please provide debug serial logs and reopen.

@muchomustacho
Copy link
Author

The only change to the radio I made was the frequency slot so it matches the US; 20. I run my Long Fast channel as channel 1 instead of 0. Is that not supported by the T-Echo?

@muchomustacho
Copy link
Author

I've put it back to only Primary Channel and Frequency Slot to 0 and when I change the Position to Approximate Location 0.2 it gives the error again.

How do I get you guys a log for that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants