axis camera - problem
 

My team has been struggling to get the camera to work. The program does work - we've tried both default and just about everything else possible. We also know that Ethernet port 2 on the cRio and the camera itself does work ( we've plugged it directly into the computer, and also into a router. It worked both times).

When its plugged into the crio, the light showing a connection never lights up (we've tested the light, and it works), and the code (the start/open camera subvi) returns a 'failure to communicate' error message (# -44003). The only cause of this problem that i can think of is the firmware on either the camera or the cRio, since the hardware and software should work.

Note: we have installed the updated firmware on the driver station and cRio. We're using labview. We've also messed around with the ips, setting the cam to 10.27.33.XX, and sticking with the default 192.168.0.90. We've also tried with the Ethernet cable supplied, and another one given to us by a science teacher. However, it is possible we don't have a crossover, but if not would it be possible for it to communicate with a pc?

One last question: do we need to do something additional to set the cRio port 2 to 192.168.0.3? Or is there some way to check what the actual ip address of it is?


Thanks for any help,
Jmak

Re: axis camera - problem
 

The orange cable that came in the KOP is a crossover cable.
The cRIO does not have autosense, so it must be connected to the camera via the crossover cable. Your PC may have autosense, if so it would work with either type of cable.

Re: axis camera - problem
 

Ok. I think what we used was blue... :ahh:


Actually, I'm not sure if we have an orange one.

Re: axis camera - problem
 

You don't need to do anything to set the cRIO port 2's IP address. It's hardcoded to be 192.168.0.3

You can check the address if you like (see control system manual section 5.4.1)
-- using a null modem serial cable connected between a PC and the cRIO serial port.
-- The "console out" dip switch on the cRIO must be on (opposite all the other ones).
-- Use Hyperterminal on your PC with settigs of 9600 BAUD, 8 data bits, No parity, 1 stop bit, No flow control

When the cRIO is reset or booted you'll get startup messages, one of which tells the ethernet port IP addresses.

P.S.
But it sounds as if you didn't know the orange cable was special...

Re: axis camera - problem
 

The very first thing your team should have done with the control system was to do a complete inventory to see if anything was missing.

Re: axis camera - problem
 

We knew we needed a specific cable, but the instructions didn't say which specific one we needed; I guess we just grabbed one that could plug into the camera :o .

we did do an inventory, but I wasn't the one doing it. I think we have the orange one, and I'll try to check today. Snow day, so no school :D.

Re: axis camera - problem
 

I despise you...:P

Re: axis camera - problem
 

Both section 5.5 of the Control system manual and section 3 of the "LabVIEW
Robotics Programming Guide for the FIRST Robotics Competition" say to use a crossover cable.

Re: axis camera - problem
 

I know, but what differentiates a crossover from a regular ethernet cable?

Re: axis camera - problem
 

The provided cross-over cable is orange.

Unfortunately, it can sometimes be a pain to figure out if an unknown cable is straight thru or cross over. Hopefully, they are obviously marked so that you can assume a cable is straight unless it is obviously not.

If it isn't well marked, you have to look at the colors of the wires on both ends. On a straight thru, the color order will match on both sides. On a cross over, two of the pairs are swapped with each other.

You can also buy devices that check for you.

Does anyone have any better suggestions? This has always been frustrating to me. I usually just put a piece of orange electrical tape on all my cross overs when I buy/make them.

Re: axis camera - problem
 

This was noted on the KOP checklist, for those that missed it.

Re: axis camera - problem
 

OK... I wasn't able to make sure it was only the cable causing the problems, since our wga600 inexplicably stopped working while we were transferring the control system to a robot. When we plug the power cable in it shows no sign of receiving power, and simply doesn't work. Someone's gonna go get a new one in the next few day - we have a friendly local competition at the end of the week.