Revision history [back]

We've seen this sort of thing before, e.g. #ros-pkg4481. Usually it's because of too many dropped packets between the camera and computer. Can you please post the diagnostics - before starting the Prosilica, do:

rosrun runtime_monitor monitor

Then start the Prosilica driver with streaming.launch (prosilica.launch starts the camera in polled mode, so it won't automatically stream images). Look at the Packet Statistics component in the runtime monitor. On a properly configured GigE network there shouldn't be any dropped packets. On Fast Ethernet some (warning level) lost packets are expected, but things should still work.

If the error always happens on the very first diagnostics collection, we'll have to try something else. But hopefully that's not the case.

We've seen this sort of thing before, e.g. #ros-pkg4481. Usually it's because of too many dropped packets between the camera and computer. Can you please post the diagnostics - before starting the Prosilica, do:

rosrun runtime_monitor monitor

Then start the Prosilica driver with streaming.launch (prosilica.launch starts the camera in polled mode, so it won't automatically stream images). Look at the Packet Statistics component in the runtime monitor. On a properly configured GigE network there shouldn't be any dropped packets. On Fast Ethernet some (warning level) lost packets are expected, but things should still work.

If the error always happens on the very first diagnostics collection, we'll have to try something else. But hopefully that's not the case.