The AXIS 206 camera is not giving us any video. Our Driver Station is fully updated (compass in the lower right corner), we made no alterations to the basic camera code, but we are not receiving any video from it.
The other thing to check is that your camera has been setup with the correct account and password. Also be sure to check the Diagnostics tab on the DS as it will display errors thrown by the robot and may help with debugging.
Greg McKaskle
Please refer to http://www.chiefdelphi.com/forums/showthread.php?t=79935 post #68. Hope this helps.
- Bryce
Is there a solution for LabVIEW? We’ve updated the Driver Station with the mandatory update, the dashboard has the compass, but we get no link lights or video with 3 different crossover cables plugged into port 2(at different times of course :)) We have also tried several different methods to run camera code, but it just doesn’t work. :mad: Help please!
Can you describe the colored light around the camera lens?
It should be steady green. If it looks different, it could help determine what is going on.
Greg McKaskle
Have you referred to my previous post? Do you get any other functions of the code to work (like driving any motors)? Also, by link lights do you mean the green and orange ethernet lights? Even if you have no code that accesses the camera, I believe the lights should still come on solid. If not, maybe there was an issue reflashing your cRio? It should say something like v19 at the bottom of the dashboard when it’s connected.
- Bryce
Thanks for the reply, we got a link today with another crossover cable(we must have been making them wrong 
) but we still aren’t getting an image. We got the motors and some servos working. I don’t think it was a reflashing image because we tried with v19 a few times. Yes, the link lights are the two orange and green lights on the back and the ring on front takes a while to change from orange to green when we run last year’s Servo Camera Example, Otherwise on the default framework, it stays orange. On the default code we get a -44003 occurred at Camera.lvlib: Issue HTTP request with Authentication.vi >>Camera.lvlib:Read JPG.vi>>Camea.lvlib: Aquire Image.vi:1 error. Any ideas?
:edit: The ring just turned green on the camera.
these are simple solutions but they worked for us, make sure the at least one account on the camera has the username FRC and password FRC. make sure the camera is plugged into cRIO port 2. and if all else fails run the update on the DS again and flash the cRIO with the base code. i know im a rookie this year but just thought i’d try and help. 
oh! and also check your IP address on the camera it works if you set it up with the example 192.168.0.90.
Bet your Dashboard isn’t the correct one.
Take a look at these pictures to see if you have the wrong Dashboard.
Thanks, my team is a rookie team this year too!(except for me :D) You really got yours working Andrew? We’ve tried and tried again with everything you just listed. I think we might just enlist one of the other local teams to help. (Even though the next closest team is an hour away sigh:rolleyes: ) Thanks, please keep thinking.
It’s the correct one…
og! one more thing to try haha. unpower the camera then hold the button and while holding the button down turn it on, wait for the orange or yellow light to come up then re-IP the camera. this resets all the settings on the camera so just in case a wrong number or setting was set. let me know how it goes!
-44003 occurred at Camera.lvlib: Issue HTTP request with Authentication.vi
This error indicates that there HTTP request is getting errors trying to send TCP packets to the camera. -44001 indicates an error with the FRC/FRC account. Verify the IP on the camera and verify the cable. Finally, with all of this configuration, it may be worthwhile verifying that the second enet port on the cRIO is still 192…
Finally, make sure that the camera doesn’t have its reset button pressed against the robot frame or anything else that will cause it to continually reboot/reset.
Greg McKaskle
yes i agree, but the -44003 error i wouldn’t worry about. We have our camera up and we still get that error sometimes but there is no issue with the camera or the camera finding the targets.
Thanks for the help everyone!
We finally got the camera working :] . Turns out both of the X-overs we had were bad, including the one from FIRST :eek:. Also we had to install/reinstall the updates THREE times.
Thanks Again!
Torgeir
Team 3189 Captain