Ok Guys,
Last night we were able to get it working! It appears our major problem was that the camera did not have an ADMINISTRATIVE user with the username "FRC" and password "FRC". When I add this it works, and when I use "root" and "admin" it does not. This seems definitive to me. Also, I don't think it was necessary, but as we were grasping at straws, we installed the FRC LabView update on the Classmate PC (FRCLabVIEWUpdate2.0for2010.zip). If any teams still can't get this to work, this might be the problem. Can anyone who got it to work verify that they didn't have to install this? Also, you shouldn't have to uninstall and reinstall WindRiver because we didn't.
Here are the updated steps below with what we did:
1. cRio must be reflashed with v19 image.
2. WindRiver should be intstalled with the WPI Lib update (WorkbenchUpdate20100107.exe).
**AN UNINSTALL APPEARS UNNECESSARY AS WE DID NOT UNINSTALL.**
3. The camera should be set up with IP address 192.168.0.90 (which is the default) and a username and password of **FRC** and **FRC**, respectively. I understand there **MAY BE** other valid usernames and password combinations as well.
** I PREVIOUSLY STATED THE USERNAME AND PASSWORD AS root AND admin. THIS IS INCORRECT. I KNOW AT LEAST ONE VALID COMBINATION IS "FRC" and "FRC". root AND admin DO NOT WORK!**
4. The camera should be connected via CROSSOVER cable to Ethernet port 2 on the cRio and adequate power supplied. When you plug in the camera, the orange and green lights should stay on (when not sending data) and may blink a couple times, but no rapid blinks (again, when idle).These two lights signify that there is at least a connection between the cRio and camera. They must be on, or you either have a bad cable, or non CROSSOVER cable (the orange one is a crossover cable).
5. The driver’s station update should be installed (DSUpdate1.0for2010.zip). This requires installing BOTH components, uninstalling BOTH components and then reinstalling BOTH components again. Apparently the NI installer has issues.
**IT MAY NOT BE NECESSARY TO UNINSTALL BOTH COMPONENTS. THE OTHER IS FOR THE CYPRESS I/O AND SHOULD NOT BE RELATED TO THE CAMERA. IT MIGHT HOWEVER, AFFECT THE I/O MODULE.**
6. Add the “2010 Vision Demonstration Program” to the current workspace and compile. (In WindRiver click File -> New -> Example… -> VxWorks Downloadable Kernel Module Sample Project -> FRC 2010 Vision Demonstration Program -> Finish.) Be sure to use the correct compiled cRio image path located in the FIRST Downloader Preferences section of “Preferences” (Located under Window).
7. Deploy the code. And watch it work!
I'll try to give a description of what happens after rebooting the cRio using the unmodified 2010 Vision Demo example:
With the dashboard up and running, reprogram the cRio and then reboot. When the dashboard shows that you have three green lights (communications and two others I don't remember), you should be disabled and Ethernet port 2 on the cRio (to which the camera is connected) should have steady lights, orange and green (the orange may blink every now and then). After enabling, not much happens for at least 10 seconds. Referring to the code, there is a wait statement that will wait for 10 seconds to allow the camera to boot. During this time THE WATCHDOG IS NOT FED. So just after enabling and for about 10 seconds afterwards, the watchdog will not be fed. There will be a message that says "Watchdog not fed". After about 12-15 seconds the orange light at Ethernet Port 2 will start flashing rapidly and an image will be displayed. Also, the "Watchdog not fed" message will go away. The green lights at the front of the camera should come on as well to let you know it has an active connection. Also, when you pull the trigger, the camera will track a target. It seems to do a reasonable job, but the frame rate of the image displayed using the unmodified code is pretty horrible.
My hope is that this will help a lot of teams overcome their frustrations. I'll try to answer any questions people might have about this process.
- Bryce
P.S. The caps locked words are not me screaming, but rather trying to point out important information.
