Issue with RTACC Shared Memory Network and VXWindows KRC1

    Hello all, I recently purchased a bulk of KRC1 controlled KR150 and KR200 robots. They are GM robots. I have been running through them getting them started back up and testing them and have ran into a couple that have this issue. When the controller is booting and starting Windows before a desktop is even displayed I get the error message below:

    Your network adapter RTACC VxWorks Shared Memory Network (0000) is not working properly. You may need to set it up again.
    Which if you go to the Windows Device Manager under network adapters there is a yellow flag next to it

    After hitting ok on that error it tries to start Cross 3 to which this error pops up:
    Uploader DLL version 2.00
    Device driver interface DLL lprtw32.dll version 3.10
    Driver LPVXWRT.vxd/sys version 3.42
    Shared memory network version 4
    RTW Setup (#0x2) No RTwin-Hardware found

    It them errors our"Cross 3 has encountered a fatal error and will now shut down, leaving you at the Windows desktop.

    What I have done so far:
    Removed the Shared Memory Network adapter from Windows and then reinstalled it using SMS Setup from the Internat/Tools... folder.
    Checked the settings for the adapter ( IP: 192.168.1.2 Subnet: 255.255.255.0 no DNS settings.)
    Reinstalled KSS software
    Took a hard drive from a working KRC1 KR200 (same robot) and installed it, no change. (This one really blows my mind as my understanding is the VXworks and Shared Memory Network have no hardware to my knowledge. How can changing the hard drive not have an effect on this issue when there is no hardware to the network? Using the Windows and settings from a good working robot directly.)

    Any helps from the Kuka masters would be greatly appreciated as I have run into this on two robots now and suspect more.

    I have had this problem in the past...

    First was when I tried to use a domestic motherboard with many differents specifications...

    Other case was when the MFC board had a problem.

    If you motherboard is original board, I suggest you change the MFC, because the system VxWorks despite of a "software" expect get on communication between both parts.

    See the image.

    Hello all, I just wanted to revisit this in case someone else has this issue in the future and finds this thread by searching.

    The problem was with the MFC card. The card itself wasn't bad but had jiggled loose just a touch probably during shipping. That MFC card is very long and barely supported in the normal sized PCI slot of the motherboard. I went to pull it out and noticed it was a touch loose. Pushed it in and the issue is gone. Thanks again!

Advertising from our partners