-
Notifications
You must be signed in to change notification settings - Fork 74
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.
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
"Error opening URL...Looping until camera appears" when viewing image in image_view #43
Comments
Hello, You should most probably launch the node using a launch file as the But modifying to your IP. You may be missing some param the node needs. Also check that Also, there is a PR here: #42 And finally, if you only want to see the camera stream, you can also try Hope it helps. 2016-02-24 0:51 GMT+01:00 mtsakaguchi [email protected]:
|
Sorry for being two years late to the subject, but I had this same issue and resolved it by setting my Axis camera to allow for anonymous access (no username/pass authentication) and left off the _user:= and _password:= from the arguments in running the ROS node, worked just fine |
I can confirm that allowing anonymous login fixes this issue. |
Setting to anonymous login works for me too. |
yep setting to anonymous fixed the issue. |
Hello,
I am running into an issue where I cannot view the published Axis camera images using the image_view package. I run
rosrun axis_camera axis.py
where the default host name is192.168.0.90
and I get the warning that thepublisher should be created with an explicit keyword argument 'queue_size'
. When I run image_view to view the raw image stream, the axis camera node prints out the warning[WARN] [WallTime: 1456299554.224392] Error opening URL http://192.168.0.90/mjpg/video.mjpg?fps=0&resolution=640x480Possible timeout. Looping until camera appears
which doesn't make sense because I can go to my web browser and type in
192.168.0.90
and I'm able to view the live stream and command the PTZ.I've even tried removing the axis_camera package and using the latest tagged release version and I still get the same error.
Any help would be appreciated!
The text was updated successfully, but these errors were encountered: