Thread: Why can't we specify an IP Address to search for in the cRio Imaging Tool?
View Single Post
  #9   Spotlight this post!  
Unread 31-07-2013, 17:58
magnets's Avatar
magnets magnets is offline
Registered User
no team
  
Join Date: Jun 2013
Rookie Year: 2012
Location: United States
Posts: 748
magnets has a reputation beyond reputemagnets has a reputation beyond reputemagnets has a reputation beyond reputemagnets has a reputation beyond reputemagnets has a reputation beyond reputemagnets has a reputation beyond reputemagnets has a reputation beyond reputemagnets has a reputation beyond reputemagnets has a reputation beyond reputemagnets has a reputation beyond reputemagnets has a reputation beyond repute
Re: Why can't we specify an IP Address to search for in the cRio Imaging Tool?
That's weird. I've used virtualbox with ubuntu to run windows 7, and I've successfully reimaged the cRIO multiple times. I don't remember exactly what settings I used for the network adapter, but I remember that it wasn't the default. Make sure that the network adapter you're using to connect the robot under ubuntu has an ip of 10.0.0.xyz, and read online about the different modes that virtualbox supports for network adapters. Also, it probably wouldn't hurt to reset the IP of the cRIO first.

You won't get the dashboard, imaging tool, or netconsole to connect to the cRIO unless you have the network set up right, so just shrink the Ubuntu partition, and install windows 7 along side it.

The reason why this isn't supported is because this situation would never occur while you are just running windows 7, which is what the software is designed to work with. There just aren't enough people working with the control system to have such a large amount of compatibility. If you do run windows 7 in a VM, you'll notice that Java's debugger doesn't work, and unless you install specific USB drivers, all the joysticks will have massive lag after 2 minutes of being enabled.