You do not have a programming issue but a connectivity issue. Setup the laptop to be on the same subnet as the robot, connect it to the router on the robot and try to ping the robot (x.y.z.2). If you can ping it, you should be able to deploy.
Nope, it was working earlier today with different code untill i tried to update the code. I’m pretty sure the problem has to do with the different laptop rather than with the robot itself
ok, heres a way to test if you are connected to the CRIO and the router.
go to the start menu search bar and find the cmd prompt
ping your router’s IP by typing in ping 10.xx.yy.zz where xx and yy are your team numbers and zz is any number between 0-255*
ping your CRIO’s IP by typing in ping 10.xx.yy.zz where xx and yy are your team numbers and zz is any number between 0-255*
*if you have not set these up yet, then the ping will fail
If these do not return received, then you need to reconfigure your IP settings to match. Type in ipconfig in the cmd prompt to see your current IP address. To find out what to configure your IP settings to, go to the FIRST website and search for setting up your wireless router and configuring the IP address.
Well, it has something to do with the laptop I was using. Not sure what, but we have a solution: wait for the mentor with the good computer or buy a brand-new 500 dollar comp for use NOW?
Is the laptop you are using running Windows 7 64bit? If so, there are known issues that we too experienced; the only way to fix these is to either set up a dual-boot on the laptop or use a virtual machine and run Windows XP on it
We found that the “Deploy” feature of Workbench was FUBAR. We used “Filezilla” to do the transfer and everything worked. Also, make sure that you have a console (or netconsole) running and watch the boot cycle. Also, make sure you’re not getting the dreaded “24-bit relocation” error. I just answered another thread where they were getting that error. It’s easy enough to fix if you know where to go in the build properties.