View Single Post
  #2   Spotlight this post!  
Unread 16-11-2009, 19:17
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
 
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,753
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: Axis Camera Communications Error

The communications error could be caused by a number of things. I'll list out some issues to inspect, but to help isolate the issue, it may be useful to connect the camera to a PC. Set the PC to IP 192.168.1.6, see if you can ping the camera which is at 192.168.1.90 I believe. You can also connect to the camera using a web browser -- type http://192.168.1.90 into the URL field of the browser, and it should bring up a login screen. If the camera is configured correctly a login of FRC with a password of FRC should work. Once logged in, you can view images, change settings, etc.

If the camera works in this mode, you may want to make sure that the camera is being plugged into enet slot 2 on the cRIO. The are silk-screen labeled, but it seems sort of backwards to me which is which. And make sure that you are using a crossover cable as neither the camera or the cRIO has an autosense capability. The crossover cable in the kit last year was orange. Note that since most PCs built in recent history have auto-sense, it is not necessary to fret with the cable when connecting to a PC.

If this doesn't allow you to get things working, please indicate which of these steps succeeded so that I can give better advice.

Greg McKaskle