New Ctrl Sys Early Ship - Benchtop Test

[rrossbach]

Hi -
We received our early shipment of the new control system today....just like Christmas a month early for the team!

We ran through the benchtop test procedure this afternoon, and all worked fine except for Auton mode - following the steps in the benchtop test doc, nothing happened when we enabled Auton mode. This is with the out-of-the-box firmware, image, etc on the cRIO and DS.

Has anyone else run into a similar problem? Trying to determine if this indicates a hardware defect (and we have to get a replacement from FIRST) or simply a problem with the default code that ships on the controller....

Thanks,
Ron

Team 2607 - Programming Mentor

[Mark McLeod]

Ours didn't follow the bench test expected outputs in all cases either.
I don't yet know if that's a real problem or an OTB version issue though.
We saw two discrepancies. One joystick didn't behave during teleop, and the first time we tried Auto nothing happened, but it did run for two seconds when we retried it.

We haven't dropped our own test program in yet to run a full verifiable test.
That's tomorrow for us.

[willson.thomas]

If everything worked up to that point and you're feeling lucky, I would just move on to flashing the DS and cRIO, then trying your own autonomous code. If that works, you should be just fine.

[Jon236]

Originally Posted by Mark McLeod

Ours didn't follow the bench test expected outputs in all cases either.
I don't yet know if that's a real problem or an OTB version issue though.
We saw two discrepancies. One joystick didn't behave during teleop, and the first time we tried Auto nothing happened, but it did run for two seconds when we retried it.

We haven't dropped our own test program in yet to run a full verifiable test.
That's tomorrow for us.

Mark,

Our system behaved just as yours did out of the box. Once the software updates are downloaded to both cRio and DS, everything seemed to work well.

[rees2001]

Quick question.

Did auton run once & then not again?

[rrossbach]

No, the OTB auton didn't even run once. Tried it multiple times (rebooting both DS and cRIO) and even hooked up two Jaguars instead of Victors in case it was an "operable range" issue, to no avail.

The Jaguars are nice, btw. Control seems to be much smoother and a much wider operable range.

Thanks,
Ron

Team 2607 - Programming Mentor

[Greg McKaskle]

I don't believe that the autonomous code uses the motors at all. It simply strobes the solenoid module outputs something like a certain black car on TV.

Greg McKaskle

[rfrank]

Originally Posted by Jon236

Mark,

Our system behaved just as yours did out of the box. Once the software updates are downloaded to both cRio and DS, everything seemed to work well.

Is there a software update for the cRio? If so, where is it located?

Thanks!

[Mark McLeod]

2009 Control System page at http://www.usfirst.org/community/frc....aspx?id=10934
Under Software Updates

[Alan Anderson]

http://www.usfirst.org/frccontrolsystem is easier to remember.

[rfrank]

I see an update for the Driver Station, for LabView, and for WPILib. I do not see one for the cRio. Is it included in the LabView update?

My team has this exact problem:
http://www.chiefdelphi.com/forums/sh...ad.php?t=70175
But none of the posts on the above thread (nor the one that it links to on the beta forums) are any help.

[stevenlu]

I think the cRIO update is found on the NI website:
http://joule.ni.com/nidu/cds/view/p/id/1162/lang/en

[Abrakadabra]

Yes - the whole update process is a little confusing. If you piece together the various instructions found in various places all in the right order, you might get it right...

Here's what I figured out by reading everything very carefully before doing anything, and my system is working now, so I think I got it right...

Before updating the cRIO firmware, you need to do the LabView update (this fact is only mentioned on the WPI site where you get the C++ update... go figure)

After you have done the LabView update, you will have an icon on your Windows Desktop that says "FRC cRIO Imaging Tool". Once you have that, you can start the cRIO updating process that is documented in section 5.1.2 (the Configuration chapter, not the Software Installation chapter, and not section 5.2.2 as mentioned in section 1.6.5 (5.2.2 doesn't exist!))

When you do the cRIO imaging, I found it easiest to connect the PC directly to the cRIO using the orange crossover cable provided in the kit (although you can also follow the directions and use the Driver Station as a LAN switch). If this is the first time you are updating the cRIO, make sure you set the IP on your computer to the static address 10.0.0.6, with a subnet of 255.0.0.0. (For subsequent updates, you will use the IP address with the team number embedded).

Then instead of following the menu path detailed in section 5.1.2.4.1, I just clicked on the above mentioned Desktop icon, and everything went smoothly from there.

Also - Please note that for the latest C++ software update found on the WPI site (Beta update 5), they say that you must reimage the cRIO before you install it, which directly contradicts the steps outlined in sections 1.6.4 and 1.6.5.

YMMV, but good luck anyway

[Tom Line]

Is anyone currently doing this with 2 nics in a computer so you don't lose net connectivity when you connect to the Crio?

Is there an option to select which network adapter Labview should be using, if you do have 2 nics in a computer?

[Mark McLeod]

Originally Posted by Greg McKaskle

I don't believe that the autonomous code uses the motors at all. It simply strobes the solenoid module outputs something like a certain black car on TV.

P.S. Is it possible that you're thinking of the new software patch in FRCLabVIEWUpdate1.0, rather than the OTB?
That does cause a chase light sequence on the solenoid LEDs in autonomous.
-----

Then I think it's possible that at least two versions of the OTB shipped.
1) Autonomously strobe the solenoid lights
2) Autonomously work somewhat in accordance with the bench test description

We evidently got version 2, because there was no indicator light strobing, but autonomous did drive the pwm outputs several different ways.
With our version when the DS was booted into autonomous we saw one of these three different autonomous behaviors occur randomly intermixed.

1. pwm 2 goes full forward effectively forever all by it's lonesome self
2. Nothing happens and joystick 1 still controls the motors as in arcade teleop
3. pwm1-4 go full forward for 2 seconds

I'm just trying to figure out what to tell people at the local workshops.