Hi, guys...
I have a problem.
There is an error at KRC2 controller. RTWLoadVxD( LPVXWRT (#0x1) - Device Driver could not be initialized (not found or wrong path)
Can anybody help me?
Cross3 Error: Device Driver could not be initialized
-
lomaxe -
July 24, 2017 at 10:48 AM -
Thread is marked as Resolved.
-
-
Check MFC and DSE correctly plugged in ISA or PCI port. If you have chance try functional MFC from another robot.
-
also check if MFC is in correct slot...
-
Read the attached discussion on this topic,
this will be helpful. -
Hi, guys...
I have a problem.
There is an error at KRC2 controller. RTWLoadVxD( LPVXWRT (#0x1) - Device Driver could not be initialized (not found or wrong path)
Can anybody help me?What is the history of this controller? Are you just powering it up for the first time after years in storage? Or was it working correctly until this happened? Have there been any changes made to the robot recently?
-
Thank you very much for your help. The problem was in MFC or DSE cards. I just unpluged it and then pluged in again.
QuoteWhat is the history of this controller? Are you just powering it up for the first time after years in storage? Or was it working correctly until this happened? Have there been any changes made to the robot recently?
The robot and the controller was moved from one country to another. They both were in working state before moving.
-
re-seat cards (MFC for example) and connectors
-
Quote
re-seat cards (MFC for example) and connectors
Thank u very much. I have done it and the conroller works normally.
Thanks to all who tried to help me at this topic.