Reimaging the cRIO - Help!

[kelsey.m]

Hi,
We're having issues reimaging the cRIO. Thanks in advance for any input and help!

We're a rookie team from the UAE and trying to get a jumpstart on the upcoming season. Our mentoring team, LiveWire FRC 3562, was gracious enough to provide us with a copy of LabVIEW and we've been able to install it. We have the sample code ready for download.

-Initially (a few months past) we were able to image the cRIO.
- All the updates are installed, we've checked that repeatedly, and reinstalled all of them, in the correct sequence, just in case.
- The Driver Station confirms we have communication with the cRIO! This is exciting! There were cheers.
- But, the robot does not respond to joystick movement at all.
- A series of error messages appear in the Driver Station and searching them on various threads suggests we need to reimage the cRIO.
- However, when we attempt to use the FRC cRIO Imaging Tool, an error message pops up stating "No cRIO images found. Expected here: long path ending in /FRC Images"
- The path exists, the FRC Images folder exists and it has a couple of folders in it...

Questions, anyone have this same problem last season? Can anyone point us in the right direction? If anyone has recently imaged their cRIO, can you look at the content of your FRC Images folder and tell us the contents? Or maybe zip and email the contents if that would even work? Any other thoughts/approaches ? We don't have the LabVIEW disk so we can't reinstall LabVIEW but I don't think thats the problem...

[kelsey.m]

Wow! We changed nothing and at startup today it now recognizes the current image which is new. Still no movement/response to joysticks. So I would still love feedback...

These images are the error messages in driver station and our cRIO imaging tool...

[kelsey.m]

Here are the error messages via the driver station... Warning

[Greg McKaskle]

The driver station LEDs to the left of the messages show that the laptop is able to ping the robot. Further to the left are Communications and Code LEDs, what are the state of those?

The warnings shown in the window are lower level details. If they aren't errors, you don't really need to worry about them.

Greg McKaskle

[Mark McLeod]

At first glance the cRIO image seems to be fine. It's operating and talking back to the Driver station. I've attached three screenshots of the Driver Station app tabs for Operation, Diagnostics, and Setup, so you can compare them with your own. You can see that the warning/info messages on the second image of the Diagnostics tab are similar to your photo. These have the Driver station PC connected directly to the cRIO, so no bridge.

In additional to answering Greg's question, about the status shown on the left of all three screenshots (communications/Robot Code/Joysticks and Teleoperated Enabled),

A couple of things to check:

• Have you Enabled the Driver Station? (see the first image below, Operation tab)
• On the Driver Station Setup tab (third image below), the right side has a list of the joysticks you have connected. Check to see that yours is there, in the correct USB slot, and turns blue when you push a joystick button. It will be green if it's recognized as being plugged in.
• Are you running a default robot project? How did you download it to the robot?

[kelsey.m]

Thanks so much for the help. Our river station appears to match yours' and the communication, joystick and robot code lights are all green. However, it's never turned blue. We are using default code. We downloaded it via the project explorer window...

[Mark McLeod]

If the joystick entry won't turn blue when you push a button, that means no commands will be sent to the robot.

Try hitting the F1 key to see if the button presses get recognized after that. That forces the Driver Station to check the USB joysticks again.

What kind of joystick are you using?

Would you take a snapshot of the Setup tab for us?

[Mark McLeod]

P.S.
Laptop USB is notorious for cutting power to USB ports while the laptop is on battery.

1. Make sure your laptop battery is fully charged and preferably plugged in.
2. Check your power saver settings to avoid power cutbacks when the battery is low.
   • Open the Device Manager. Win 8, hold the Windows key and press the 'x' key to open a menu in the lower-left and select "Device Manager." Using Win 7, open the Start Menu, type "Device Manager" in the search field, and click it.
   • Expand "Universal Serial Bus controllers"
   • Right-click each entry titled "USB Root Hub" and select "Properties"
   • Change to the "Power Management" tab
   • Uncheck the check box next to "Allow the computer to turn off this device to save power"
   • Press "OK"
   • Repeat this for each "USB Root Hub" entry
   • Reboot the computer
3. If using more than one USB device, i.e., multiple joysticks, distribute the USB load across all the laptop USB ports that you have. Keep critical joysticks on their own USB port.
4. Avoid ganging multiple USB devices up on a single USB hub. Bigger hubs are worse. If used, small hubs are best.
5. Avoid fancy joysticks that draw an excess of USB power. Power hungry fancy sticks or ones with glittery LEDs won't fare as well as plain vanilla generic joysticks.

[kelsey.m]

Here is the image of our setup...

We're currently attempting to find the original default code to download, just in case we changed something by accident.

As far as the joysticks, this is probably a stupid question, but other than battery usage, does the model matter?
Meaning, do we have to select it somewhere within the code? We used V-Max 2013 flight joysticks for ps3/PC, nothing fancy, just generic joysticks...

[Greg McKaskle]

From your screen, it seems that you have joysticks, code, and communication to your robot. It is disabled, and it isn't possible to know how the code was programmed.

My suggestion would be to enable the robot in teleop mode and carefully test it. Perhaps you should put the robot on blocks as you test. You should also be ready to disable or estop it by hitting the spacebar on the driver station if you need to.

Another approach is to go to the dashboard and put the robot into test mode. This lets you read sensors and it lets you enable and test outputs just one at a time.

Greg McKaskle

[Alan Anderson]

Originally Posted by kelsey.m

We're currently attempting to find the original default code to download, just in case we changed something by accident.

If you reimaged the cRIO, any user code was erased from it in the process. You must load your code onto the robot again before it will do anything.

[kelsey.m]

Update...

We have code on the robot (downloaded default to cRIO via project explorer and right clicking run on robot main), and the driver station shows that it has code.

We have observed the joystick names going blue when we click buttons but not moving the joystick (changing the axis position).

We have observed the axis values changing as we move the joysticks in the test phase.

We still have not gotten motors to respond to joystick movement....

thanks for any advice!

[Mark McLeod]

..and you Enabled the Driver Station?

Sounds like the cRIO and code are doing fine.

How about the electrical side of things?
Lets discuss the wiring.
cRIO modules seem to be in the correct places.

• Do you have power wired separately to the Digital Sidecar from the Power Distribution Panel (PDP)?
• Are all three power LEDs on the Digital Sidecar bright green?
• Do you have PWM outputs 1 & 2 wired to speed controllers?
• What are the status lights on the speed controllers doing?
• Are the speed controllers separately wired for 12v from the PDP?

[rsisk]

Originally Posted by Mark McLeod

...[*]Are the speed controllers separately wired for 12v from the PDP?[/list]

There is a PDP on board? There's your problem

On a more serious note, Mark meant the PDB, Power Distribution Board

[Greg McKaskle]

Page three of this tutorial -- https://decibel.ni.com/content/docs/DOC-26314 -- may help out.

The short answer is that if you open a resource in your code and register it by name, it will show up. If you select an actuator value in the table, a control will display allowing you to modify the value. Motors are somewhat dangerous, so they utilize a momentary enable button. This means, you select, then set the desired speed, then click and hold the enable button for as long as you want the motor controller to be sent that value. Other actuators don't require the enable button.

If this doesn't work, please describe what it does do to the LEDs, etc. And don't forget to enable the robot on the driver station.

Greg McKaskle