"VxWorks6x_10.32.42.2 (Registry localhost)"

[z.s.tar.gz]

Here is the error report from trying to connect to the cRIO:

Error connecting to 'VxWorks6x_10.32.42.2' (Registry localhost). Failed to launch target serverPossibly caused by: Back-end not connected.
Removed dead entry from Registry!

com.windriver.ide.target.exceptions.TargetServiceE xception: Error connecting to 'VxWorks6x_10.32.42.2' (Registry localhost). Failed to launch target server
Possibly caused by: Back-end not connected.
Removed dead entry from Registry!
Caused by: com.windriver.ide.target.exceptions.TargetServerDi edException: Back-end not connected
at com.windriver.ide.target.wizard.connectstrategies. tgtsvr.TargetServerLauncher.threadLaunchTargetServ er(TargetServerLauncher.java:497)
at com.windriver.ide.target.wizard.connectstrategies. tgtsvr.TargetServerLauncher.launch(TargetServerLau ncher.java:562)
at com.windriver.ide.target.processes.ProcessLauncher .run(ProcessLauncher.java:133)
at java.lang.Thread.run(Thread.java:595)

I'm new to WindRiver and cRIO, so I don't know what to do at this point.

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.

[gvarndell]

Originally Posted by z.s.tar.gz

Here is the error report from trying to connect to the cRIO:

I'm new to WindRiver and cRIO, so I don't know what to do at this point.

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.

Not much to go on here in terms of relevant detail.
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?

[Tom Schindler]

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!

[z.s.tar.gz]

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?

[1951-44U]

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.

[z.s.tar.gz]

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?

[SteveGarward]

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.

[byteit101]

Originally Posted by z.s.tar.gz

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?

Originally Posted by z.s.tar.gz

Edit: I tried pinging the device via the usb chord and it timed out. What could this mean?

the usb device that connects to the DS that you are refering to sounds like the cypress IO board. if you can see electronics on a blueish circuit board that has stuff on it (and connects to a 9 volt batten) it is the IO board. this is non-essential (unless you are using it)

[z.s.tar.gz]

Thank you, we have it figured out now. It was just confusion on how the system worked that was our problem.