MX1 Failure (firmware/OS related?)

[LaneRM]

Today I went out with three new files on the SD card. The newest Navidata.ewd, and MX1FW.BIN and MX1OPSFW.BIN from http://www.mglavionics.co.za/mx1upd.html
.

Seemed like it went ok? The first file updated, and then it told me that it required another file, so I shut it down and initiated the update in the same manner.

All seemed well until I took off and the screen froze. I turned it off and back on, but the MX1 would reboot during startup, try to start again, and then freeze. After landing the issue persisted.

Holding down the left most button and powering on the device brings me to the update menu.

I'm wondering if there's a repository of older firmware/OS files somewhere and if reverting would help?

Is there a way to hard reset the device? I can't do anything via the GUI.

In the morning I'll go out and check my wiring and ensure that it's not wiring issue. All other devices are powering up normally.

[LaneRM]

Update:

I formatted an SD card and loaded it with the iEFIS MX1 Application Software version 10 and FlightOps System MX1 version 0001006 located at https://support.michiganavionics.com/po ... x1-updates on the Michigan Avionics portal.

Reverting back to these versions solved the problem completely.

I read through several posts from people who are experiencing boot loops - maybe loading these versions could help you too?

[Allegro 4205]

I had similar issues with Frozen Display on take off and then cycling on boot up. Resolved with reload Operational Software and firmware.
Followed the guide per the micro kit wifi gateway instructions………seems ok now but gateway is not fully functional

[brs]

It's refreshing to know that I'm not insane thinking only my (two) MX1's did that sort of thing. It's common for it to freakout in flight and either freeze or boot-loop. I've come so very close to removing it, but it's a really nice unit (if it would only behave).

The quick fix for continuous boot-looping and or frozen is to restart it while holding the Bottom-Right(portrait) or Top-Right(Landscape) knob to present a menu. Select the first item to reset non-volital-memory. If the Altitude is wildly wrong (after it reboots) then just reboot normally and it will reset to 29.92.

I've had to perform the above many times in flight to get back my airspeed so to make a safe landing.

When I first discovered this issue, It happened when hitting "Action - Start New Flight". Seems the data recording is partially at fault for this happening. It does this if the auto-detect new flight is turned on.

Yesterday while checking for erroneous settings that might be a contributing factor I noticed something odd. In the "Analog Input Setup" that under "Analog Input 2" Where it said 'No Name' clicking on that to change the name indicated that (1-11) characters were valid. But I found out that the name entered there was something like "No Name No Name No Name No Name" obviously more than 11 characters. I wonder if anyone else has this feature present. Go to that field and scroll to the right and see how many "No Name"'s you have in a row. I've not yet flown since I changed that.

I'm still on the latest V16 firmware. Didn't find Ver10 on the michiganavionics site. Seems they updated to V16.

[brs]

If you need the older firmware you can copy the links from the firmware update page and change the version number...

For example....

mglavionics.co.za/ MX1upd16L /MX1FW.BIN
becomes....
mglavionics.co.za/ MX1upd10L /MX1FW.BIN

Seems to work with all the other FW files and simulator.

[brs]

I formatted an SD card and loaded it with the iEFIS MX1 Application Software version 10 and FlightOps System MX1 version 0001006... maybe loading these versions could help you too?

Lane,
I loaded V10 FW files today. It fixes the data recording (Action/StartNewFlight) issue and hopefully further reboot/boot-loop.
However, now the Altimeter reads 145,000+ at 29.92 Hg. I've tried several things and am once again stuck. I guess tomorrow I'll try V16 again and see if that fixes the Altimeter (but breaks the rebooting again).

Rainier any chance you can chime in about these MX1 issues?

[brs]

Tried Several Versions this morning and found one that seems to work.

V16 through V13: These all cause the same crash/boot-loop issues when Flight Data begins to record.

V12: Yea! This version works.

V11: Didn't try

V10: Though some have reported it to work, on my MX1, the Altitude shows ~145,000' higher than field elevation
=====

It seems that V12 is the latest MX1 (landscape anyway) firmware that does not crash when Flight Data Logging turns on.

[LaneRM]

Just getting back to the forum. Good info there BRS, glad you got it settled. On to the next thing!

[rainier]

It seems that V12 is the latest MX1 (landscape anyway) firmware that does not crash when Flight Data Logging turns on.

I am trying hard to emulate this here - I am using version 16. It works perfectly.
Can you tell me how you have setup your system ? Size of recording file ? Can you see the recording file if using the internal file manager ?
Can you tell me what external items you have connected - in case it is data recording of one of these that is causing your issue.

[brs]

Rainier,

Recording file is 10mb, I can zip it and send it to you (will check it via internal file mgr later today).
I've tried various combinations of disconnecting items - haven't seen any indication of external items that might be causing this.
I'll make up a diagram for how things are connected. Will post here when I have that.

Would it help if I cloned the internal SD card and sent you an image?

-brs