Driver station malfunctions after upgrade

[dtischle]

See attached file for the same story with pictures.

We assembled the Driver station and the control system to a minimum configuration and tested it. Joystick controlled the motors..

We disassembled the whole kit and reassembled it on a new table. 

We than updated the Driver station firmware per instructions at:

http://usfirst.org/community/frc/content.aspx?id=10934

Upgrade went fine (After several unsuccessful attempts but this is another story)

Now, when we turn everything on, the driver station hangs and will not react to buttons.

For diagnostics, this is what we have:

The driver station is disconnected from the cRIO controller and connected to the 2 joysticks.

Everything works fine.

We now connect it to the cRIO via the Ethernet cable Driver station ETH1 to cRIO link 1

Now the Driver station switch everything to “Invalid” and hangs

Even disconnecting the digital board and starting all over again doesn’t help

Regards, Dan Tischler Team 3087

[Philbot]

After updating the driver station, you must also re-image the cRIO. (they work together as a matched pair)

Use the cRIO imaging tool that was installed on your PC when you updated your PC software.

Go here and read the section about updaing your software.  Don't skip any steps between tests.

http://usfirst.org/frccontrolsystem

After updayting the cRIO, you also have to setup the Driver Station with the correct team number....

Once again... do the updates step by step as shown in the manual.

[Now_With_Underscores]

If you're having trouble updating the image on the cRIO after updating to version 2, unplug the cRIO's power supply and plug the cRIO's Ethernet straight into your computer with a crossover cable.  Set the computer's ip address to obtain automatically (DHCP).  Turn on the IP Reset and Safe Mode switches on crio and then plug in the cRIO.  Open Measurement and Automation (Start»Programs»National Instruments»Measurement and Automation).  Once open, look in the bottom of the configuration tab (on the left) and find your cRIO (default name is 'test').  Right click on the cRIO and select 'Format Disk'.  Once reformatted, change the computer's IP address to 10.0.0.6 and the subnet to 255.0.0.0, turn off IP Reset and Safe Mode and then reset the cRIO.  Now run the imaging utility.

[MarkO_]

We had a similar problem with the cRIO after a Bad Reprogram. We could no longer communicate with the cRIO.

We had updated the LabView to the “Second Mandatory Update” http://joule.ni.com/nidu/cds/view/p/lang/en/id/1180, and were trying to upload some Test Code to the cRIO, and things went Very Bad.

First, setting the Computer to use a DHCP server did not work with a Direct Connection between the Computer and the cRIO.

But the “Open Measurement and Automation” application (Start»Programs»National Instruments»Measurement and Automation), does not need TCP/IP to operate.

After opening “Open Measurement and Automation Explorer, Ver 4.5”, click on “Tools-->NI-Serial-->Ethernet Device Configuration”. After scanning the Ethernet Bus, a single Device (cRIO-FRC) was located with an Unknown TCP/IP address. Clicking on the “cRIO-FRC” device and then clicking the “Properties” Button, I could force the IP Address and Subnet Information to what was the correct values. Then the “FRC cRIO Imaging Tool” (Start»Programs»National Instruments»LabVIEW 8.5» FRC cRIO Imaging Tool) worked correctly.

MarkO

FRC Team 957 (Professional Mentor)

[dtischle]

We have upgraded the cRIO as instructed and now it works find.

Thanks much!!!