Problem with the comunication - camera and cRio

[NoahLitle]

Hello,

We are team 3089.

We have a problem with the comunication between the camera and the cRio.
The camera works well when we plugged it to the computer, but when we plugged it to the cRio on the robot - it didn't work.

The error we get is:

ERROR <Code> -44003 occurred at Camera.lvlib:Issue HTTP Request with Authentication.vi>>Camera.lvlib:Issue Get.vi>>Camera.lvlib:Set Image Appearance Property.vi>>Camera.lvlib:Set Enum Appearance Property.vi>>Camera.lvlib:Set Image Size.vi>>Begin.vi>>Robot Main.vi

We need any possible help,

Thanks,
Team 3089.

[Mark McLeod]

It's probably something simple.

Does everything work except the camera display on the dashboard?

Is the cRIO reimaged with v19 and did you download, "Run as startup", the default robot project?

One problem with the Driver Station Update installer is the Dashboard can get messed up so that the camera image doesn't display. The camera is working, just the Dashboard isn't.
The solution for this is to run the Driver Station Update twice more.
Once to Uninstall (select "FRC Driver Station" & "Remove this feature").
Again to Install.

There could be other causes too. Any more symptoms, such as how do you know the camera isn't working?

[NoahLitle]

Thank you for your fast reply.

We have reinstalled what you have told us and still there are no communication between the camera and the cRio.

The error we get is:

ERROR <Code> -44003 occurred at Camera.lvlib:Issue HTTP Request with Authentication.vi>>Camera.lvlib:Issue Get.vi>>Camera.lvlib:Set Image Appearance Property.vi>>Camera.lvlib:Set Enum Appearance Property.vi>>Camera.lvlib:Set Image Size.vi>>Begin.vi>>Robot Main.vi
<time>09:11:17 01/16/2010

Please help us with our problem,
Thanks for your help,
Team 3089

[Mark McLeod]

That error message is what you get with the wrong Dashboard, but it could be the wrong code running on the cRIO too.

Here are how the two versions of the Dashboard look.
Compare yours to make sure which one you have running.

The first one is what the correct Dashboard should look like.
The second one is what came pre-installed on the Classmate and does not work with the camera.

[NoahLitle]

Hi again,

We are having a problem while trying to set the code in the Crio,
We will appreciate if you can show us how to change the Dashboard so it will be like you have showed us in the first picture.

Thanks again,
Team 3089.

[Mark McLeod]

Since uninstall/reinstall the DS update didn't work for you it's a little more involved, but you can create your own Dashboard that will work. I assume you installed the latest LabVIEW Update.

How to Create Your Own Dashboard:

1. Exit the Driver account to close everything (Setup tab -> Exit)
2. Login to the Developer Account
3. Use LabVIEW and create a new Dashboard project.
4. You'll then need to create an exe
   1. Right click on Build Specifications -> New -> Application (EXE)
   2. In the Popup:
      1. "target filename" - give it something meaningful, e.g., MyDashboard.exe
      2. Note the Destination Directory. That's where you're going to find your new dashboard
   3. Tell it where to begin:
      1. In the left list click on "Source Files"
      2. Click on "Dashboard Main.vi"
      3. Click on the right pointing arrow that will highlight
      4. You should see Dashboard Main appear on the right hand side under "Startup VIs"
   4. Click on "Build" at the bottom to create your exe
5. When it's done building:
   1. Go to the Destination Directory you remember from above. It'll be something like: My Documents\LabVIEW Data\builds\2010 Game Dashboard Project\My Application
   2. You'll see three files: MyDashboard.aliases, .exe, .ini
   3. Copy all three files to the directory: C:\Program Files\FRC Dashboard
   4. Go to C:\Documents and Settings\All Users\Shared Documents
   5. Make a backup copy of the file: FRC DS Data Storage.ini
   6. Edit the file: FRC DS Data Storage.ini
   7. You'll see a line: DashboardCmdLine=""C:\\Program Files\\FRC Dashboard\\Dashboard.exe""
   8. Change the name of the Dashboard.exe to MyDashboard.exe
   9. Save and exit the file
6. Login to the Driver account to start up the new dashboard and see if it works.

Now of course, you can go back and edit the project to customize the Dashboard for yourselves.

[Dark_Vizior]

Hey,

We (team 3257) are getting the same -44003 error when connecting the camera to the cRIO. We can access the camera with a web browser on the other side of the wireless bridge, however, we cannot access it when it is connected to the cRIO.

We added a hub between the wireless bridge and the RIO and we are monitoring the traffic with a packet sniffer. When the camera is attached to port 2 of the cRIO, the only traffic we see are SYN packets being sent from the cRIO address to the camera address. The camera never sends back ACK packets.

Any help? That'd be great.

[Mark McLeod]

Promise me you're running the correct Dashboard as in picture 1 above.
That's got to be the #1 trap people are falling into.

The cRIO doesn't act as a router, so you won't be able to sniff the camera response back to the cRIO from a hub attached to port 1, just the cRIO's messages to the camera. You'd probably see them if you were attached to port 2.
Since the cRIO isn't a router you can't communicate through the cRIO to the camera as it's on a different net (192.).
So what you are getting seems normal and what I'd expect to see.

A secondary issue is not having the camera username/password accounts the cRIO is using (FRC/FRC).

Originally Posted by Dark_Vizior

We (team 3257) are getting the same -44003 error when connecting the camera to the cRIO. We can access the camera with a web browser on the other side of the wireless bridge, however, we cannot access it when it is connected to the cRIO.

We added a hub between the wireless bridge and the RIO and we are monitoring the traffic with a packet sniffer. When the camera is attached to port 2 of the cRIO, the only traffic we see are SYN packets being sent from the cRIO address to the camera address. The camera never sends back ACK packets.