Waiting for cRIO to reboot

[nikRbokRz]

Hi,

I've gone through the recent required updates for the FRC Squawk.

However, I now have an unusual problem. When I upload code, the message "Waiting for cRIO to reboot (XXXs)" appears. It never goes away (and the time keeps increasing). As a result, I can no longer view any System.out.println()'s.

It's interesting, because another programming team member has also updated the FRC Squawk stuff, but he is only getting to "Waiting for cRIO to reboot (10s)" - which is what I used get - and then is able to view the print statements.

Any ideas on why this is happening, and how I could fix this?

[Patrick Chiang]

Does restarting the Driver Station/Dashboard when it's waiting help?

[nikRbokRz]

How exactly would I restart my Dashboard/DS? I have my ClassmatePC on at all times.

[Patrick Chiang]

What's your driver station / developing setup? Are you uploading code from another computer?

[nikRbokRz]

Yeah, we're all programming from our own laptops, and then uploading code wirelessly, using the bridge.

It used to work before the update, but since then it's not working (and only for me, it works fine for my teammate).

[Patrick Chiang]

Try running the driver station and dashboard on your laptops. We used to have a problem where we got a similar problem. We fixed it by closing the dashboard and opening it while the code deploys.

[nikRbokRz]

But it's not really "laptops". It's just my laptop that doesn't work correctly. It deploys code, it's just that I can't get print statements.

[ygd]

Make sure the subnet/netmask is set to 255.0.0.0. We had this problem too until we changed it.

[ericarseneau]

One test that you should try is to run the "echo" target on the build.xml of your project in NetBeans. Then reboot the cRIO. If you get output after a while that is the console out of the cRIO then you know you are getting good communication from the cRIO. If not, then you may have the mask issue pointed out.

[michael714]

I've got one for you. The other day, after installing every imaginable update, we were getting "Waiting for cRio to reboot" scrolling indefinitely on the console. After some experimentation, I realized that code was loading on the robot and the reboot was occurring, but we just weren't getting the appropriate console output. So, I checked the IP settings for the network card on my PC and discovered that we were using DHCP. So, I changed it by manually setting the IP to 10.22.72.6 (team 2272) and the console update correctly and I no longer received indefinite waiting to reboot. FYI.

[Phoenix.14]

We're having this same problem when we try to load code onto our cRIO. We have the laptop hooked into the wireless bridge, although we've also tried a direct cable into the cRIO. We use java with netbeans, and we're trying to load a new project onto the cRIO; unfortunately, whenever we select Run Main Project, the output scrolls indefinitely on "Waiting for cRIO to reboot (<x> s)". After 15 or 16 seconds, the Classmate driver's station regains comms with the robot, but continues to read "No Robot Code". When we reset the robot, it still has no code. Does anybody have any other tips on how to solve this problem?