Fix OSD summary screen not displayed after long flight

[shellixyz]

Possible fix for #2973 and #2638

Issue might be that the resumeRefreshAt variable controlling the OSD refresh / arming screen display time / summary display time is only 32 bits and 2^32/1000000/60 ~= 71 minutes.

[digitalentity]

Good catch. We missed this one when converting time to 64-bit.

[JDFPV]

I'm also having the same problem ( OSD summary screen not displayed after long flight ). But in my case on 2 different flights using the omnibus f4 pro board, using 1.8 firmware. I flew for 56 minutes total and traveled over 60km. When i landed, i disarmed and no summary screen. This only happens when i travel over 60km. Is there a fix for this as well as the flight time issue mentioned above?? Please Help

[shellixyz]

@JDFPV I don't think the distance plays a role. You only flew for 56 minutes but what is important is the time from power up not the fly time. The summary screens fails to be displayed if disarming after 71 minutes and 35 seconds from power up.

Please try this binary: inav_1.9.0_OMNIBUSF4PRO.hex.zip

[JDFPV]

@shellixyz ok i just looked back at the dvr footage. And the plane was powered up for 2 minutes and 25 seconds prior the launch. So that's a total of 58 minutes and 35 seconds.... No where near 71 minutes of being powered up.

[shellixyz]

@JDFPV Did you have throttle low and pitch centered when you disarmed ? It will be fixed by #2980 but if you disarm with throttle or pitch > max_check setting the summary screen is not displayed.

[JDFPV]

@shellixyz yes. Throttle at its lowest position and pitch, roll and yaw was centered before i disarmed sir.

[JDFPV]

Ok i have the hex file uploaded. Will test it out and report to you guys this weekend after i fly. Thanks for your help.

[JDFPV]

Ok, i flew over the weekend and the summary problem is fixed. But now, when im 6+ miles out and switch to rth the plane just banks hard to the left and losing altitude. This happened to me twice on 2 different flights. Using rth less than 6 miles out it works normal. Any suggestions on why this is happening? Using 1.8 i never had any trouble with rth at all. This just started with the 1.9 hex file.

[JDFPV]

Do i need to open a new issuse for the rth problem im having?

[digitalentity]

@JDFPV yes please. And if possible, include a blackbox recording of the issue.