-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
MATEK H743 freeze after couple of minutes with INAV8 + JETI #10646
Comments
Can you please include a settings DIFF, not a DUMP. When you said it freezes after a couple of minutes. Is that after the same elapsed time in each test ? |
Diff: https://pastebin.com/Nm0Syd10 It freeze with Battery only It freeze without sd card and enabled bblog |
I see you are using Jeti, which you have reported elsewhere is locking up again. Don't you think that could also be the problem here? |
i dont know. |
Have you tried setting serial RX to something like CRSF and physically removing the Jeti receiver? |
I will try it and set rx to sbus i noticed something strange right now, but i cant say exactly if it was before the freeze or after. |
Seems like no freeze with SBUS |
So it seems like another Jeti related issue to me. |
can u compile me inav 8 with inav 7 compiler? lets see if this fix the issue like in inav 4 |
Try to test with the artifacts from #10653 No guarantees, so test in the bench first. |
Thanks, test is running... What i also noticed some time ago, i have 16 channels but inav shows 24 channels on reciver tab. Here is a video with 16 channel mode |
It freeze around 7 min |
This will likely be a tough one to crack without hardware. |
Jea i think so.. i have a suspicion what it could be, but unfortunately i don't have the programming skills to implement it. in the beginning with jeti, between rx and tx, i think it was a 2,4k resistor was needed. then marv-t in betafligh implemented it in the code so that no resistor is needed anymore. maybe go back with the code so that the resistor is needed and test it? if i can remember correctly from testing in the past, if i disable telemetry feature it dont freeze |
I reached out to JETI to see if they are willing to provide a test system on loan, or if they have some sort of simulator we can use. Otherwise, we may have to depend on someone in the community donating a radio + rx for testing. (It does not need to be the latest model, so if you anyone has an older JETI system that is compatible with EXBUS and is willing to donate to the INAV team, reach out!) |
Great, thank you. I'm curious what answers now, don't think they'll go into it. I might have a transmitter and rx available on loan, if jeti dosent respond. May I contact you on discord? |
Sure, but I would wait for Jeti to reply. I have no idea how long I would need the radio for, so I would rather know I am not preventing anyone from flying in the mean time :) |
Meanwhile as I also have some JETI planes with INAV (using Jeti's exbus protocol) I could test out Inav 8 on some FCs. So what do I exactly need to do to cross check with you guys? |
I have right now flashd inav 8 on ma matekf722 wing. lets see what happens. @jaroszmm maybe its a combination of jeti protocol an the other connected hardware |
@jaroszmm |
ok, freeze too with f722 with only rx connected after around 20 min From my testing some time ago i noticed that the freez maybe takes longer if i use 50Hz transmitter rate. |
Hello, I have the exact same issue with h743 and jeti on fixed wing, exactly the same as we had before somewhere in 6 or version 7. |
@JWC1304 Can you pls try to disable the telemetry option in INAV configurator and look if it freeze? |
if you use a matek controller and inav8 it will freeze after a few minutes of flying. the last time it was something with exbus jeti with made it freeze, basiccally losing signal. |
i would like toi but than i will have to sacrifice another plane or bird, i can only repeat it while actually flying. Or can you tell me how to test this on the bench |
No, it freeze on bench too with usb. pls confirm first the freeze with telemetry enabled and usb. |
okay give me an hour (dinner in between )and i will report back asap |
It's probably worth adding Jeti causes freezes in the known issues of the release notes. |
Okay, mine just froze on freshly flashed 8.0 |
with the gcc9 version? |
No, with "official" 8.0 |
And another freeze, this time quickly, not even 10 min operation |
now with gcc9? or the official version testing official version has the freeze. |
Still official. I wanted to check if this happens at least twice. |
I am testing INAV 8.0 GCC 9.3.1 and it works with no problem. It took me some time to figure how to install it. I did not do it since 6.0 |
I see CH 17 jumping up and down randomly. It is strange |
Diff All command does not work for me. |
after 43 mins it is still working (INAV 8.0 GCC 9.3.1) but Diff All doesn't work and INAV configurator freezes when Diff All performed |
F722 runs with no freeze on GCC9 and there are only 16 channels in configurator |
Where did you enable 24 CH mode in your transmitter, I cannot find it? I have DC-24. |
Does the Diff All command work in your configurator? |
I found it. When I enabled 24 CH mode, all control surfaces stopped working |
yes you have to restart fc |
I tried to configure the FC from the scratch and it seems to be working Ok and CH 17 stands still no random moving. |
O.K. I believe INAV 8.0 compiled on GCC 9.3.1 will work. I am back on INAV 6.1 now. I don't see any reason to upgrade anytime soon. Anyway, thank you very much for the file. |
Iam done, i think iam not able to find the issue in this way. f722 looks fine no freeze. i think the compile broke something.... the whole story begun with gcc change from gcc9 to gcc10.... |
For Information, cant observe an freeze on H743 and F722 with GCC9 and telemetry enabled |
I had no freeze at all while testing it but I wanted to fly today and ended up waiting for satellites. It stopped on 5 and never increased, so I flashed the INAV back to 6.1 and had 11 sats almost immediately. |
i woiuld love to test it but i have an imac system, or did you guys already fixed the issue, i do not quite understand where we are at right now. Did yoy guys also play with the throttle that is how i made it freeze everytime, @RoadyFPV can you enlighten me what is the status now? Will there be a new compiled version soon? |
Hi, I am on mac too. Where is your problem? INAV configurator also works on mac platform. Latest version of INAV 8.0 compiled on GCC 9.3.1 works. Official version doesn't (I mean for JETI users). |
there wasa new file sent to test with that was for test purposes only and that was not a mac file but for windows, no idea how i compile 8.0 with occ9.3.1, I know the offical relases work with mac, duuh, although i had to start it up in a terminal with some attr command, and yes a jeti user that suffers from the freezing. |
You got it wrong. There is no such a file for windows or mac. There is a one file for all platforms only configurators are platform orientated. Here is the file INAV.8.with.gcc.9.3.1.zip |
my bad thank you
my bad thank you |
This are no official Version of INAV, Fly it at your own risk. |
I sent them an e-mail, but not sure if they will be able to provide a unit on loan. I don't have any special contacts there, so it may not even get past customer support. |
Got a reply today. Sounds like Jeti will send a loaner with the next elefun order. It should arrive in a few weeks. So there may be a light on the end of the tunnel. |
I flashd INAV 8 to my MATEK H743
after a couple of minutes the FC frezze no Servo and configurator reaction, only a usb reconnect or disconnect the battery will help.
With INAV 7 no issues at all.
Steps to Reproduce
1.Flash INAV 8
2.apply the modified diff / or set it up new
3.The FC freeze after a couple of minutes
Expected behavior
It should not freeze like in INAV 7Suggested solution(s)
Find with me a way to clear the issue, maybe u can give me instructions how to find itAdditional context
https://pastebin.com/HxEp59E6
version
INAV/MATEKH743 8.0.0 Jan 21 2025 / 16:13:24 (ec2106a)
GCC-13.2.1 20231009
The text was updated successfully, but these errors were encountered: