![]() |
"VxWorks6x_10.32.42.2 (Registry localhost)"
Here is the error report from trying to connect to the cRIO:
Quote:
Quote:
This occurs on a physical machine without admin privilages and on a virtual machine with admin privilages. Has not been tested on the netbook supplied by FIRST. |
Re: "VxWorks6x_10.32.42.2 (Registry localhost)"
Quote:
Is the cRio powered up, running, and properly connected (via router or not) to the PC? Can you ping the cRio from the PC on which you're running Workbench? |
Re: "VxWorks6x_10.32.42.2 (Registry localhost)"
Have you followed the "Getting Started with C++" Manual here:
http://first.wpi.edu/Images/CMS/Firs...artedWithC.pdf I received similar errors until realized i had not selected the Kernel image as discussed on page 6. Good Luck! |
Re: "VxWorks6x_10.32.42.2 (Registry localhost)"
I have read and followed it to the letter.
I still get the same results. I'll try again though... Edit: I tried pinging the device via the usb chord and it timed out. What could this mean? |
Re: "VxWorks6x_10.32.42.2 (Registry localhost)"
I'm just giving my two cents here, but could it be possible that the network setup on your virtual machine leaves something to be desired? If it pings without response, there is only one thing that does that: it is not connected. Lack of admin rights on a physical computer can do this too, since you need to change network settings.
|
Re: "VxWorks6x_10.32.42.2 (Registry localhost)"
I just tried it on the FIRST netbook, and I get similar results even though I have admin rights and the firewall is turned off.
Is there anything else I have to do to set it up that's independent of windriver? If so, I haven't done it. Edit: I think I have the wrong thing. The cRIO is the little microcontroller right? Or is it the thing that goes on the actual robot? |
Re: "VxWorks6x_10.32.42.2 (Registry localhost)"
The cRIO is the long, heavy rectangular box that the 'cards' slot into. Has a lower section that has some dip switches, a serial port and two ethernet ports.
I would suggest going back to the beginning and making sure you didn't miss anything. Work through this, and then this. Start a new workspace to do this, rather than try persevere with what you have. When you have got everything working successfully, and if time permits, then go back to your current workspace and try to figure out what was different. |
Re: "VxWorks6x_10.32.42.2 (Registry localhost)"
Quote:
Quote:
|
Re: "VxWorks6x_10.32.42.2 (Registry localhost)"
Thank you, we have it figured out now. It was just confusion on how the system worked that was our problem.
|
| All times are GMT -5. The time now is 10:04 AM. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi