Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Handle loss of access to the camera. #1

Closed
jack-oquin opened this issue Oct 12, 2012 · 1 comment
Closed

Handle loss of access to the camera. #1

jack-oquin opened this issue Oct 12, 2012 · 1 comment

Comments

@jack-oquin
Copy link
Member

If the camera is unavailable on the network when the driver starts, it should initiate a slow poll waiting for it to respond.

Similarly, if the device stops sending images, the driver should wait in a slow poll loop until access is recovered and the camera reconnected.
@paulmilliken paulmilliken mentioned this issue May 13, 2013
Merged
@awesomebytes
Copy link
Member

This was implemented and merged already :)

I even tried:

[WARN] [WallTime: 1430926296.123376] Error opening URL http://10.68.0.6/mjpg/video.mjpg?fps=0&resolution=640x480Possible timeout.  Looping until camera appears

And it loops waiting.

clalancette added a commit to TRI-jaguar4x4/axis_camera that referenced this issue Sep 6, 2018
@clalancette
Make the axis publishers best effort. (ros-drivers#1)
c17c50d 
This makes sense for a camera.

Signed-off-by: Chris Lalancette <clalancette@openrobotics.org>
civerachb-cpr pushed a commit that referenced this issue May 12, 2020
@peci1
Merge pull request #1 from tradr-project/version_bump
ea7c4b5 
Bumped the version to 0.3.0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jack-oquin @awesomebytes