Promise me you're running the correct Dashboard as in picture 1 above.
That's got to be the #1 trap people are falling into.
The cRIO doesn't act as a router, so you won't be able to sniff the camera response back to the cRIO from a hub attached to port 1, just the cRIO's messages to the camera. You'd probably see them if you were attached to port 2.
Since the cRIO isn't a router you can't communicate through the cRIO to the camera as it's on a different net (192.).
So what you are getting seems normal and what I'd expect to see.
A secondary issue is not having the camera username/password accounts the cRIO is using (FRC/FRC).
Quote:
Originally Posted by Dark_Vizior
We (team 3257) are getting the same -44003 error when connecting the camera to the cRIO. We can access the camera with a web browser on the other side of the wireless bridge, however, we cannot access it when it is connected to the cRIO.
We added a hub between the wireless bridge and the RIO and we are monitoring the traffic with a packet sniffer. When the camera is attached to port 2 of the cRIO, the only traffic we see are SYN packets being sent from the cRIO address to the camera address. The camera never sends back ACK packets.
|