URGENT can't deploy in WindRiver

[kws4000]

It compiles, we have reformattted, all updates are done, we have com....

FIRST->Deploy
Problem Occored
IO ERROR while downloading program to robot

Previously we we had programmed with Windows 7, now this laptop is on XP.

HELP!!!!!!!

oh yeah we are tethered right now

[davidthefat]

Did you change the IP to 10.24.05.6 and sunet mask to 255.0.0.0 and the wifi is turned off?

[kws4000]

No dice. No wifi included anyhow.

[davidthefat]

Oh, I know the problem, you guys divided by zero... But seriously I have no idea.

[wireties]

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.

HTH

[kws4000]

Originally Posted by wireties

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.

HTH

Not sure what you mean by "ping"
we have comm via straight port #1 or through the router

[davidthefat]

Did you recently go to a scrimmage? You probably have to reconfigure the bridge on the robot

[kws4000]

Originally Posted by davidthefat

Did you recently go to a scrimmage? You probably have to reconfigure the bridge on the robot

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

[Matthew Blake]

ok, heres a way to test if you are connected to the CRIO and the router.

1. go to the start menu search bar and find the cmd prompt
2. 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*
3. 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.

Hope this helps!

[kws4000]

Nope, it worked
Our mentor just got here so we'll find out together

[kws4000]

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?

You can imagine the expletives flying now.

[Matthew Blake]

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

[kws4000]

Don't think you understood.
The laptop with te problem was XP
The laptop that would work was 7, likely 64 bit

Anyhow, doesn't matter now.

[taichichuan]

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.

HTH,

Mike