Hi Clark/Troy (:eyebrow:)

Thanks for responding. It turns out the problem was on my end, I had mixed up two pins and not wired the power output from the Arduino correctly. Once I fixed this so the display actually got 5V, it starts up and displays text fine. Sorry for bothering.

cheers,

/Patrik

Thanks for the tip. Figured it out first, though. It was ups.exe that was doing it, disabling that service made the problem go away (and interestingly enough had no effect on the ups monitoring which still works fine....)

Hey all,
A new issue just started appearing for me using my MX212. Currently, something is hijacking the USB COM port when the computer boots. LCDC says it can't open communications, and something is sending a repeating character sequence consisting of "<spc><weird char><spc><spc>" to the display ...

If we can get back to MY problem, thread hijacker! ( :wink: )

I just realized that I have a PCI USB card lying around, so I decided to connect the display to that instead of to the nforce4 onboard USB, and it appears this has also fixed the problem! :D It does appear to be an issue with the nforce ...

So the new display works fine, it displays ( ) none of the peculiar behaviors of the old one. Thanks!

If you could let me know the results of swapping them, I would be able to get a good indication of wether the display is faulty, or wether there is a compatiblity issue related to your motherboard.
I tried the display on the other machine (while that display is on RMA) and it works fine. I did ...

lutorm, do you think this was related to the driver problems you had? Is there anyway you can try your display with another motherboard to see if it's just your display in particular that has the problem? (or maybe it's just with your specific motherboard)

Well, this is a little difficult since ...

Hmm. I don't have any power management options for those devices...

I should add that the system suspends to S3. I don't know if the problem persists with suspend to S1.

Ok again (sorry to be updating this so often...)

I hacked the FTDI inf files to include PID FA01, which allows the driver to install and it even works with LCDC. However, the usb subsystem still locks up when coming out of standby.

I verified that this is caused by the MX, as either a) unplugging ...

You may want to try updating your driver with the ones on the FTDI web site:

http://www.ftdichip.com/Drivers/VCP.htm


Ok, so I uninstalled the MO drivers, and when I plugged the MX in and the found new hardware wizard came up, I selected the CDM2.00.00 drivers. However, it just says "hardware ...

I just noticed that when the usb subsystem hangs, the matrix orbital driver under USB controllers says "no drivers are installed for this device" for device status.

And it looks like this driver is the one from FTDI, so I'll try those newer drivers.

Sorry for the delay in responding. Are you using the internal, or external USB cable to connect to the display? The internal cable tends to be more sensitive to static, and can cause the display to apear to have 'locked up'. The solution to this is to either use the external usb cable (and route it ...

You may want to try updating your driver with the ones on the FTDI web site:

http://www.ftdichip.com/Drivers/VCP.htm

Let me know if this helps you at all.


Ok, I'll try this, but what is this driver for? Is this the Matrix Orbital driver or a USB chip driver? I tried "update driver" for the MO ...

Paradigm wrote:One quick question I have: Which OS are you running, 2000, XP, Vista or other?

XP SP2

sorry for the delay, been traveling.

Is there no MO guy here that can tell me if this is normal or not?

An additional piece of info: before the usb is initialized (like in memtest86+), the fans connected to the GPO outputs seem to change speeds in an apparently random way. Every now and then (on something like 5 minute timescales ...