Driver Interface

[whytheheckme]

Originally Posted by BradAMiller

I believe that connecting another device to the 2nd ethernet port on the cRIO is legal provided that you can come up with a switch that runs off robot power. You should check the rules yourself to be sure.

Given that, I'd expect that the cRIO might have trouble doing image processing from two cameras at the same time depending on what operations your're performing. The problem with doing that is that the AxisCamera class is currently a singleton, meaning that it assumes that there is only a single camera connected.

It might be that this can be changed in an update so that multiple cameras can be supported or it might be something that you can look at.

As for the question of modifying the dashbaord program... the source code is available as a LabVIEW application. You can modify it as needed. You have to be careful to keep the data in sync between the robot and dashboards ends. You can look at both samples to see how this works.

Might it be more viable to simply write code to pass the packets from the camera directly through to the DS/dashboard? Or would this utilized too much bandwidth?

[drakesword]

The cmd line in the ini file was blank. I tried setting it to "C:\Program Files\FRC Dashboard\Dashboard.exe" But it still wont come up OR it may be comming up minimized. the update disables alt-tab so i cannot bring it up

EDIT

Scratch the disabled alt tab it does work its just not launching the software

EDIT

Figured it out . . . gotta double backslash the commands
"C:\\Program Files\\FRC Dashboard\\Dashboard.exe"

[James Dempsey]

Originally Posted by whytheheckme

Might it be more viable to simply write code to pass the packets from the camera directly through to the DS/dashboard? Or would this utilized too much bandwidth?

I haven't calculated it but I would think that passing the data stream directly to the dashboard would be a feasible option that doesn't eat up the bandwidth. However, I may be wrong since the camera feed is a direct stream of jpgs(if I am not mistaken). This may result in a large consumption of bandwidth due to the quantity and quality of the jpgs but I would assume that FIRST designed this to not eat up your bandwidth.

-
James D

[jhersh]

Originally Posted by whytheheckme

Might it be more viable to simply write code to pass the packets from the camera directly through to the DS/dashboard? Or would this utilized too much bandwidth?

This is essentially what the video to dashboard server on the cRIO does. The JPEGs from the camera are not recompressed... they are simply forwarded on.