MGL Avionics User Forum

The SL-30 data output from the Razor has a bug. The VOR CDI data is reverse sense. The localizer and glide slope seem to be OK.
I've made several support requests and have not received a response. I can provide data, if needed.

Regards,

Well, I guess I'm the only one flying with an N16 and a Razor display.
I will start a new post to request a bug fix.

Is anyone using the Razor with N16 to monitor VOR? Does it work for you? The Razor CDI is confusing because the deflection appears to be backwards from a standard CDI. I had assumed that this was because the display was an airplane instead of a needle. But, this is really confusing after having flow...

I'm having problems driving the CDI display on a GRT EFIS from the Razor and N16. The CDI display seems reasonable on the Razor, but jumps around and comes and goes on the EFIS. I've placed a serial monitor on the output of the Razor and have verified that the Razor is outputting bad SL30 CDI messag...

I did just get a call from Hiram at the USA repair. He did try cooling the control head in refrigerator and then a freezer and could not duplicate. I appreciated the call back and I understand how difficult CNDs can be. He did get one failure after placing the unit in the freezer, but there was also...

The problem with random touches keeps occurring anytime the temperature is below 50F, until the unit warms up. I've returned the unit to MGL USA for warranty repair. They have had it for 3 weeks now and cannot duplicate (probably because they didn't test at low temp.) and just updated firmware and w...

It happened again. I checked the panel mount screws, they were very loose. I snugged them up a little and the touch screen still had random presses. I cycled power and everything was OK. It seems that when the temp is below 50F this happens.

I had the same issue this morning.
I attributed it to cold weather (37F). This is the coldest I've operated the system so far. Power cycling didn't help, but once the unit was on for about 5 minutes the problem went away.
If it happens again I'll try loosening the screws.

Update: Michigan Avionics suggested running a virtual comm port program in between the physical USB comm port and the updater app. That did work.

I have gotten the Razor firmware updated now and it solves the problem with LSBs. WIth Windows10 and and a USB to serial adapter I had to use some virtual Comm port software in between the Razor fimrware update program and the actual comm port in order to get the updater to work. I suspect Windows 1...