CRio Connection: Buggy

[ChaosX73]

We got the most recent LabView update today, and after reimaging the CRio (which was successful by the way), I opened the driver's station. My computer is tethered to the bot and we have not had communications problems before now. Now, even though I can ping the robot successfully, the communications only like to come on for one second, turn off, wait a minute, and then repeat. On the CRio, the Status LED blinks 4 times in a row and repeats that. I have power-cycled the bot many times and, yes, I have restarted my computer. Nothing is working.

What happened? Does the Labview update contain evil?

[Joe Ross]

After imaging the cRIO, there is no code installed on the robot. Does that explain your problem?

[ChaosX73]

It's not the fact that there is no code, it's the fact that for some reason, the CRio doesn't want to admit that it's connected to my computer. My mentor said something about the CRio being "Bricked" but I have no idea what that means.

[mswalker]

We are having the same issue. After re-imaging the cRio (three times successfully) and updating labview, we cannot run code on the cRio. We can ping it but when we try to "run at startup" we get a message that Labview cannot communicate with the real time target. The status light on the cRio repeats a series of 4 flashes as reported above.

[Greg McKaskle]

Four flashes means a double crash. The manual mentions it could be due to running out of memory.

You may want to watch the deployment dialog closely to see if that indicates a memory issue.

Greg McKaskle

[Mark McLeod]

Just got the same thing at one of the teams here.

Re-imaged the cRIO with v27 and we start getting the 4 blinks repeated.
Cannot download code but can reimage it to our hearts content.

I can reimage with v25 and everything works fine again.

[Joe Ross]

Originally Posted by Mark McLeod

Re-imaged the cRIO with v27 and we start getting the 4 blinks repeated.
Cannot download code but can reimage it to our hearts content.

Does the serial console show anything interesting?

[Mark McLeod]

I have console dumps, but haven't been able to look at them.
I did get it working, but I'll have to wait on posting an update.
I'm in transit between teams.

[mswalker]

We managed to get code to deploy/run a few times but mostly we get the four flashes in Status. On one of the times it worked, I checked the memory usage and there was still 16K or so free.

The four flashes in status start even after a reboot with no attempt to deploy. I tried disconnecting everything - removing all sidecar adapters, ethernet connections etc. And rebooted. And still the cRIO showed four flashes.

From a laptop I can ping the cRio before trying to run. When I try to run I get "can't connect to real time target" but after cancelling, I can still ping the cRio.

I have not tried to go back to v25. I'll check that out.

[Greg McKaskle]

16K is not much. Can you verify that number and clarify when you are at 16K?

Greg McKaskle

[Chris Hibner]

I just want to jump in to say that we've seen similar issues since the update.

Since the update we haven't been able to deploy code wirelessly. When we try to deploy wired, we haven't been successful when hooked to the Dlink. If we connect directly to the cRIO, we are successful deploying about 25% of the time (i.e. it takes about 4 tries before it works).

After deploying new software and rebooting, we are able to get the robot to run wirelessly through the driver station. No issues.

We have not yet been able to run software via the Run button since the update. It starts to run and then it promply loses connection.

That's all I have for now. I won't see the cRIO until Wednesday night, so if I notice anything new then I'll try and post it.

[thE_iyE]

Just to cover some bases for ChaosX73:

Originally Posted by ChaosX73

It's not the fact that there is no code, it's the fact that for some reason, the CRio doesn't want to admit that it's connected to my computer. My mentor said something about the CRio being "Bricked" but I have no idea what that means.

I can't seem to image the cRio from my personal laptop, so I have to use the classmate. I 'bricked' (which means to turn it into an expensive paper-weight) our cRio by using the imaging tool on my laptop, so the way you have to fix it is format the cRio. You format it by putting the cRio in safe-mode. Once its in safe mode, try to deploy code using the imaging tool. It will recognize it in safe-mode and ask if you want to format it, do so. This will return it to its normal state so you can put new code on.

Its likely not bricked, so try and just deploy v28, but if your computer doesn't recognize it and the IP address doesn't seem to be recognized by your computer, its likely bricked.

Again, this is just to cover some bases for ChaosX73. Hope it helps!