LCDC Error, hardware or software?
-
- LCD!
- Posts: 10
- Joined: Wed Mar 03, 2004 8:12 pm
- Location: Vancouver, BC
I have 6 external and 2 internal m/b USB ports and the only thing plugged in currently (not that it seems to have made a difference in the past) is I have a USB IR Receiver/Transmitter plugged into one of my external USB ports. Also I have ran the module off the internal USB connection of the m/b and a normal external USB connection with seemingly no effect either way on my problem.Miles wrote:Do you currently have any other USB devices connected?
There very well might be a problem with the FTDI component on how it receives and transmits data. To do a further analysis I would have to perform some tests on our test bench. Can you contact me at myero@matrixorbital.ca to discuss some RMA options?
Miles Y.
Head of Technical Support
Product Manager
Matrix Orbital
Head of Technical Support
Product Manager
Matrix Orbital
Miles wrote:There very well might be a problem with the FTDI component on how it receives and transmits data. To do a further analysis I would have to perform some tests on our test bench. Can you contact me at myero@matrixorbital.ca to discuss some RMA options?
Is there any update on a possible resolution to this problem? I'm having the exact same issues with my MO display, and I can't seem to make it run stable on my system regardless of what I do.
-
- LCD!
- Posts: 10
- Joined: Wed Mar 03, 2004 8:12 pm
- Location: Vancouver, BC
Phish,
I RMA'd my module - Miles tested it for two days without error. I received it back from RMA and it errored out again within 5 minutes. To make a long story short I changed my USB port that I was plugged into and it has been working for over 2 days now without a problem. So I am starting to think that there is a problem with one (or several) of my USB ports. I would try your module on another machine if you can. Try to eliminate the USB as source of the problem...
Cheers!
Wino
I RMA'd my module - Miles tested it for two days without error. I received it back from RMA and it errored out again within 5 minutes. To make a long story short I changed my USB port that I was plugged into and it has been working for over 2 days now without a problem. So I am starting to think that there is a problem with one (or several) of my USB ports. I would try your module on another machine if you can. Try to eliminate the USB as source of the problem...
Cheers!
Wino
Phish wrote:Miles wrote:There very well might be a problem with the FTDI component on how it receives and transmits data. To do a further analysis I would have to perform some tests on our test bench. Can you contact me at myero@matrixorbital.ca to discuss some RMA options?
Is there any update on a possible resolution to this problem? I'm having the exact same issues with my MO display, and I can't seem to make it run stable on my system regardless of what I do.
Wino,WinoOutWest wrote:Phish,
I RMA'd my module - Miles tested it for two days without error. I received it back from RMA and it errored out again within 5 minutes. To make a long story short I changed my USB port that I was plugged into and it has been working for over 2 days now without a problem. So I am starting to think that there is a problem with one (or several) of my USB ports. I would try your module on another machine if you can. Try to eliminate the USB as source of the problem...
Cheers!
Wino
What motherboard are you using? I have a MSI 865PE Neo2-PFIS2R, and I'm pretty sure the board is the problem, since I have 2 of these displays, both exibit the same behaviour, regardless of USB port used. I've also installed a bare-bones instance of XP and removed every item in my system other than CPU, Vid card, RAM and PS2 keyboard/mouse. I'm going to try another motherboard tonight to see if that solves the problem, and if so I'll RMA the MB back to MSI
-
- LCD!
- Posts: 10
- Joined: Wed Mar 03, 2004 8:12 pm
- Location: Vancouver, BC
Phish,
My board is an Asus P4P800-VM. I didn't think to try it in another board yet. But after months of problems its been stable for 3 days now. I might even begin to get excited at the prospect of this thing working now!
:-)
The only thing different since it "started" working was the USB port that its plugged into.
My board is an Asus P4P800-VM. I didn't think to try it in another board yet. But after months of problems its been stable for 3 days now. I might even begin to get excited at the prospect of this thing working now!
:-)
The only thing different since it "started" working was the USB port that its plugged into.