Matrix Orbital Corp

Hi, this one has driven me nuts for awhile. I have an MX421 and the backlight randomly shuts down by itself. Sometimes it runs for days, sometimes shuts down every five minutes.

I believe it has something to do with the drivers (V1.4) but not sure.

I have installed the display on two different motherboards, same results. I have reinstalled the LCDC software many times, uninstalled and reinstalled the device, and the drivers. I have tried 1.06.33 LCDC version and the original 1.05 version several times.
If I do not run the LCDC software, the display remains on forever, works perfect. Since I get the same results with different motherboards, I do not believe it is hardware related. Since the display works fine with the system on (and LCDC not running) I do not believe it is an interference issue, a grounding issue, etc.

I have even reinstalled the operating system from scratch, reformatted, removed all registry entries, everything I can think of, and I still get the same results. I have two different Matrix Orbital displays, the MX421 and a new MX212 and they both exhibit this random backlight shutdown.

I have tried every type of USB connection and many different cables, direct connect to a board USB port, through a hub, and even directly to the motherboard header. Same result.

I cant think of what else to try. I can only assume the driivers or the LCDC software needs a fix.

Anyone else have this problem? If so, I would appreciate hearing about it or possible solutions. I love the unit, but the backlight issue takes most of the fun out of it. Thanks.

hi harley7892,

Just to to confirm, the unit backlight works fine without running LCDC?

Yes, the unit seems to stay on day and night when LCDC is not running. When I activate the software, the backlight will randomly turn off (although the display is still running, darkly)

harley7892,

I will test a unit at our facility for 24 hours to try to duplicate your problem, and I will get back to you tommorow.

Best Regards,

harley7892,

So far, I have not been able to recreated the problem yet. I will leave the unit running over the weekend, and I will let you know the results.

Best Regards,

Thank you for your efforts. I will await your reply. In the meantime I am going to remove the unit from the pc and try to set it up somewhere away from it. Perhaps there is some coincidental anomoly that affects the USB connection, when the unit is in proximity. and the LCDC software is running. I have had strange USB incidents before, especially with USB modems. I do have a USB keyboard and I will try switching to a PS2.

I do love the unit. These intermittant problems generate great sympathy in me for the Space Shuttle.

If all else fails, there are serial and parallel MO units I can try. And perhaps another software driver.

Hi harley7892,

I have ran the unit over the weekend using LCDC, and I still haven't been able to recreate your problem.

Would you like to send any of your units back to us for testing?

First, I want to thank you for your efforts. It is clear you have great dedication to your products.

I left both units on over the weekend (two different ASUS boards, one with an MX2 and the other with the MX4) I moved the one on the MX2 three feet outside of the case, away from any EMI, and I routed the cables away from any other electronics. That unit did not shut off (and it had before). The second unit on a new Pw5d2 I mounted as far away from the motherboard and fans as I could, and still stay within the case.) That unit only shut down once (although it did display scrambled characters every now and then.)
It seems the farther the unit is from the fans and motherboard, the less the shutdown effect)

One thing new I am going to try, to put the unit in a non-ASUS board (actually going to use an ABIT) and see if I still get the effect.

All of my ASUS boards have from time to time had a few USB incidents, modem lockups, board freezes, etc. If I have anything hooked up to the COM1 serial port, it will occasionally send dash patterns to the MO unit. (Actually I guess they are really both serial ports, one actual, one virtual)

Perhaps there is something peculiar about the ASUS USB architecture, or 955X drivers, or something that causes intermittant conflicts.

In any case, if the unit displays the same behavior on the ABIT board, I will RMA them back to the two retailers I purchased them from, and they will send them back under warrranty I would guess.

But I do thank you for your offer and efforts again. (Incidentally I ordered another unit, an MX414 just to try). Hope springs eternal!

harley7892,

Another thing you can keep in mind that cheap fans and cold cathode fluorescent lights emit a lot of electrical noise. If you have any extra optional fans or ccfls, try testing the display with the fans and ccfls unplugged.

Let me know your test results.

Best Regards,

Well still having a few problems. I have no less than four different MO displays (mx414, 411, 412, 212)I have tried on two ASUS motherboards. (I use all Delta fans, great quality, and no other lighting, like CCFl).
It is more stable now, but even after a fresh o/s install, removing all other usb devices, isolating the unit, trying every usb port on the motherboard, and every port on an external powered usb hub, I get occasional random backlight shut downs, and sometimes the display(s) halts with a little blinking "" in the upper right corner. I have installed and uninstalled the device, drivers, and LCDC software many times. I have tried many different usb cables. I have tried to make sure there are no irq or sharing conflicts in the system.
I dont know what else to try at this point. I have to assume it is an issue with the drivers, the software, or possibly some inherent problem with asus usb controllers.
Since it happens with all of the displays, I do not believe there is any defect in them. All other usb devices work fine on both motherboards. (p5ad2-e premium and p5wd2 premium)

I dont give up easily, love a challenge, but I have run out of ideas. Anything I haven't tried?

Ray

Hi Ray,

Out of all the usb cables you tried, were they all internal, external, or did you try both?

Hi Tom.

Tried both, internal and external, long and short ones.

Did you see any difference between the internal and external usb cables?

The internal cable definitely generated more errors. Probably closer to interference generating electronics that the outside routed cable. I use an open box tower Lubic case, so I just route the cables anywhere I want.

Dont think its a cable issue however. I have the unit grounded to the PSU ground, the cable shielded and routed away from anything electric.

My guess is still the drivers or usb bus conflict. I think I'll test that theory with what I found over at the LCDC website. I can run two or three units off of separate copies of LCDC. Think I'll hook three of them up and see if they interfere with each other. If so, maybe I can reassign an irq, or select a higher virtual com port beyond com 4, the default. This is new ground for me, but what the heck, it can't hurt.

What if I set up an event in LCDC to turn the backlight on after, say, each time a certain screen displays? Might not work if the unit has actually stalled, but if its still running, it might relight? Just a thought.