Is there anyway to tell from the logs why my MX1 is rebooting? If not, how do I go about finding the culprit.
I had thought it was a power spike or something like that but then my last flight I departed with the alternator off. About 7 minutes into the flight the MX1 reboot. It happens often and not on a regular basis.
Thank You.
MX1: diagnosing random reboot
Forum rules
Please keep your posts friendly and on topic. No politics or discussions of a controversial nature not related to our favorite subject of flying and avionics. Offending posts may be removed or moderated.
Please keep your posts friendly and on topic. No politics or discussions of a controversial nature not related to our favorite subject of flying and avionics. Offending posts may be removed or moderated.
Re: MX1: diagnosing random reboot
Took the Sonex up today, MX1 freaked out just after rotation. Went into a boot-loop. Managed to get the volatile memory cleared while still climbing. It was nice to have airspeed indication to get back on ground though everything was out the window until I shut down later restarted. Still working every idea I have to try to get the panel so it is helpful and not the other way around.
Re: MX1: diagnosing random reboot
Has anyone had reboots because of airframe static discharge? I'm starting to look outside of the box for solutions.
One outside the box idea that is gaining steam is to remove the MX1 and put in some steam-gauges. Ok perhaps not real mechanical gages but 'singles'.
One outside the box idea that is gaining steam is to remove the MX1 and put in some steam-gauges. Ok perhaps not real mechanical gages but 'singles'.
SOLVED!: MX1: diagnosing random reboot
The MX1's (two separate units so far) rebooting/locking-up has been isolated!
A few weeks ago it was discovered that pressing ACTION/START-NEW-FLIGHT caused the unit to either go into a boot-loop else freeze. To fix this the NON-volital-memory had to be cleared. As a result I changed Flight-Recording to start automatically, yet the MX1 would still fail on takeoff and in flight. This made sense as Flight-Recording was still being started - Automatically.
I found that by disabling Flight-Recording altogether seems to have fixed the problem. By setting the Flight-Recording to start on "digital input" (something like that), but not having an input configured, kept Flight-Recording from running and the MX1 no longer failed.
Please fix this! Flight-Recording is very important to me as this is a new engine.
Edit: This is a Land Scape configured MX1.
A few weeks ago it was discovered that pressing ACTION/START-NEW-FLIGHT caused the unit to either go into a boot-loop else freeze. To fix this the NON-volital-memory had to be cleared. As a result I changed Flight-Recording to start automatically, yet the MX1 would still fail on takeoff and in flight. This made sense as Flight-Recording was still being started - Automatically.
I found that by disabling Flight-Recording altogether seems to have fixed the problem. By setting the Flight-Recording to start on "digital input" (something like that), but not having an input configured, kept Flight-Recording from running and the MX1 no longer failed.
Please fix this! Flight-Recording is very important to me as this is a new engine.
Edit: This is a Land Scape configured MX1.
Re: MX1: diagnosing random reboot
Thanks for the info.
Is your system setup to record to the external SD card ?
Is your system setup to record to the external SD card ?