View Single Post
  #10   Spotlight this post!  
Unread 21-03-2011, 21:33
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,748
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 206 camera not streaming

The cRIO does not have a DHCP server on it, but once the camera times out waiting for a DHCP server, it will self-assign to 192.168.0.90.

If you had the camera statically set to 0.90 and the cRIO port two also set to 0.90, that would cause a problem with camera communications.

I believe that both ports on the cRIO have link LEDs. Use them to determine if the cRIO may have a loose enet connector. Also test a different crossover cable and wiggle the connector at the camera.

Swapping cRIO and seeing a temporary improvement doesn't really convince me of what the problem is.

As for the lag, TCP buffers don't wait in line. The lag would be per port. If you have large images and lots of them, you could put a bigger CPU load on the cRIO, but other than that, the UDP packets from the DS and the TCP packets to and from the camera and DS have little to do with one another.

Greg McKaskle