Camera other than Axis 206?

[Greg Marra]

Originally Posted by whatabouteve

i got it set up exactly like it says in the manual, set comp ip to 192.168.0.6 go to web browser and got to 192.168.0.90 then set password and configure to 340 x 280 or whatever that size was..

I am not particularly versant with the IP configurations of the new controls system, but I know most things are 192.xx.yy.1, rather than 192.168.0.1. Are you sure the middle of the IP doesn't need to be your team number?

[Pausert]

The camera does not follow the typical FRC naming convention, which 10.xx.yy.z where xxyy is the team number and z is the identifier for the router, bridge, cRIO, Classmate etc. The default IP is correct on the older camera, but I don't know about the new, square one.

[whatabouteve]

It says it is the same ip address. My question is involving how the actual camera functions and the code works with the data because my big theory is,

The camera sends more information to the cRio than the cRio actually dumps out of its system. That is why after 6 seconds of being turned on and operating fine, the cRio has overflow errors because it is trying to hold onto too much data.

I need a way to change the subroutine called upon by
AxisCamera &camera = AxisCamera::GetInstance();
Since it is the only thing that seems wrong with the entire setup because
i recieve the proper image i ask for and it runs on the cRio.

[Greg McKaskle]

The cRIO and camera both have 100Mbit ethernet. The new and old camera both compress images using the same algorithm. The new one is or seems to be largely compatible with the old one. Provided you put an account on the camera, it should respond with images, just like the 206 did.

The GetInstance() function opens the TCP session with the camera. It is hanging, returning an error, or what?

Greg McKaskle

[Alan Anderson]

Originally Posted by Greg Marra

I am not particularly versant with the IP configurations of the new controls system, but I know most things are 192.xx.yy.1, rather than 192.168.0.1. Are you sure the middle of the IP doesn't need to be your team number?

The camera is on the second network port of the cRIO. It is indeed supposed to be at the 192.168.0.90 IP address.

[whatabouteve]

Here is an exact description of what happens:
we power up the cRio
the netbook connects to the cRio
the camera turns green
we enable the cRio
the robot begins sending an image once teleoperated starts
(This is because we have the single line of code just before the teleoperated loop)
watchdog might flicker on the screen for a moment
after between 6 to 7 seconds, Watchdog appears, stays, and the robot loses connection. It remains that way until we physically turn off the robot.

that is all that happens every time.

[thetallmage]

Question. Are there any hardware differences to the newer model that makes it mount to the "pan and tilt assembly" differently or is this not a concern?

[Dale]

We don't use the Pan and tilt system but here are some pictures of the two cameras.