Streaming Stereo Camera
-
@tom Thank you.
I tried it again without manually running voxl-streamer.
First I made sure it was on by inspecting my services.
When I confirmed that it was on, I tried to input the rtsp:// in the Open Network Stream in VLC, but it failed.
Here is the error message in VLCConnection failed: VLC could not connect to "192.168.110.152:8900". Your input can't be opened: VLC is unable to open the MRL 'rtsp://192.168.110.152:8900/live'. Check the log for details. Connection failed: VLC could not connect to "127.0.0.1:8900". Your input can't be opened: VLC is unable to open the MRL 'rtsp://127.0.0.1:8900/live'. Check the log for details. Connection failed: VLC could not connect to "192.168.110.159:8900". Your input can't be opened: VLC is unable to open the MRL 'rtsp://192.168.110.159:8900/live'. Check the log for details.Can you confirm that I should be using the rtsp://192.168.110.152:8900/live for the VLC network stream?
Or should it be rtsp://127.0.0.1:8900/live ?voxl:~$ voxl-streamer -i tracking Waiting for pipe tracking to appear Found Pipe detected following stats from pipe: w: 640 h: 480 fps: 30 format: RAW8 Stream available at rtsp://127.0.0.1:8900/liveHere is my settings in voxl-mavcam-manager
{ "snapshot_pipe_name": "tracking", "video_record_pipe_name": "tracking", "default_uri": "rtsp://192.168.110.152:8900/live", "enable_auto_ip": true }I am not able to view any video when executing the voxl-mavcam-manager either.
voxl:~$ voxl-mavcam-manager ================================================================= Parameters as loaded from config file: snapshot_pipe_name: tracking video_record_pipe_name: tracking default_uri: rtsp://192.168.110.152:8900/live enable_auto_ip: 1 ================================================================= Camera name for qgc: Camera 0 Mavlink server Connected Got camera information request auto-detected RTSP URI: rtsp://192.168.110.152:8900/live Got camera information request auto-detected RTSP URI: rtsp://192.168.110.152:8900/live Got camera information request auto-detected RTSP URI: rtsp://192.168.110.152:8900/live -
I am not able to view any video when executing the voxl-mavcam-manager either.
voxl:~$ voxl-mavcam-manager ================================================================= Parameters as loaded from config file: snapshot_pipe_name: tracking video_record_pipe_name: tracking default_uri: rtsp://192.168.110.152:8900/live enable_auto_ip: 1 ================================================================= Camera name for qgc: Camera 0 Mavlink server Connected Got camera information request auto-detected RTSP URI: rtsp://192.168.110.152:8900/live Got camera information request auto-detected RTSP URI: rtsp://192.168.110.152:8900/live Got camera information request auto-detected RTSP URI: rtsp://192.168.110.152:8900/live -
@Kris Again, you've ran through
voxl-configure-skuandvoxl-configure-mpathere is no reason to start a service manually. In your first post you could see thatvoxl-mavcam-managerwas already running as a service.What do your video stream settings look like in QGC? Do you have it setup correctly to expect an rtsp stream?
-
@Kris Again, you've ran through
voxl-configure-skuandvoxl-configure-mpathere is no reason to start a service manually. In your first post you could see thatvoxl-mavcam-managerwas already running as a service.What do your video stream settings look like in QGC? Do you have it setup correctly to expect an rtsp stream?
-
@tom
Yes, I have ran through thevoxl-configure-skuand thevoxl-configure-mpa.
This is what my video stream seetings look like in QGC, if its the correct location.
-
@tom This is what I see.
voxl:~$ systemctl status voxl-streamer ● voxl-streamer.service - voxl-streamer Loaded: loaded (/usr/bin/voxl-streamer; enabled; vendor preset: enabled) Active: active (running) since Tue 2024-03-05 01:18:42 UTC; 13min ago Process: 17793 ExecStartPre=/bin/sleep 5 (code=exited, status=0/SUCCESS) Main PID: 17800 (voxl-streamer) CGroup: /system.slice/voxl-streamer.service └─17800 /usr/bin/voxl-streamer Mar 05 01:31:34 apq8096 voxl-streamer[17800]: A new client rtsp://192.168.11...1 Mar 05 01:31:34 apq8096 voxl-streamer[17800]: Camera server Connected Mar 05 01:31:34 apq8096 voxl-streamer[17800]: rtsp client disconnected, tota...0 Mar 05 01:31:34 apq8096 voxl-streamer[17800]: no more rtsp clients, closing ...y Mar 05 01:31:34 apq8096 voxl-streamer[17800]: A new client rtsp://192.168.11...1 Mar 05 01:31:34 apq8096 voxl-streamer[17800]: Camera server Connected Mar 05 01:31:34 apq8096 voxl-streamer[17800]: rtsp client disconnected, tota...0 Mar 05 01:31:34 apq8096 voxl-streamer[17800]: no more rtsp clients, closing ...y Mar 05 01:31:34 apq8096 voxl-streamer[17800]: A new client rtsp://192.168.11...1 Mar 05 01:31:34 apq8096 voxl-streamer[17800]: Camera server Connected Hint: Some lines were ellipsized, use -l to show in full.voxl:~$ systemctl status voxl-streamer -l ● voxl-streamer.service - voxl-streamer Loaded: loaded (/usr/bin/voxl-streamer; enabled; vendor preset: enabled) Active: active (running) since Tue 2024-03-05 01:18:42 UTC; 14min ago Process: 17793 ExecStartPre=/bin/sleep 5 (code=exited, status=0/SUCCESS) Main PID: 17800 (voxl-streamer) CGroup: /system.slice/voxl-streamer.service └─17800 /usr/bin/voxl-streamer Mar 05 01:33:33 apq8096 voxl-streamer[17800]: no more rtsp clients, closing source pipe intentionally Mar 05 01:33:33 apq8096 voxl-streamer[17800]: A new client rtsp://192.168.110.159:48596(null) has connected, total clients: 1 Mar 05 01:33:33 apq8096 voxl-streamer[17800]: Camera server Connected Mar 05 01:33:33 apq8096 voxl-streamer[17800]: rtsp client disconnected, total clients: 0 Mar 05 01:33:33 apq8096 voxl-streamer[17800]: no more rtsp clients, closing source pipe intentionally Mar 05 01:33:33 apq8096 voxl-streamer[17800]: A new client rtsp://192.168.110.159:48604(null) has connected, total clients: 1 Mar 05 01:33:33 apq8096 voxl-streamer[17800]: Camera server Connected Mar 05 01:33:33 apq8096 voxl-streamer[17800]: rtsp client disconnected, total clients: 0 Mar 05 01:33:33 apq8096 voxl-streamer[17800]: no more rtsp clients, closing source pipe intentionally Mar 05 01:33:33 apq8096 voxl-streamer[17800]: A new client rtsp://192.168.110.159:48606(null) has connected, total clients: 1 -
voxl:~$ systemctl status voxl-mavcam-manager -l ● voxl-mavcam-manager.service - voxl-mavcam-manager Loaded: loaded (/usr/bin/voxl-mavcam-manager; enabled; vendor preset: enabled) Active: failed (Result: signal) since Tue 2024-03-05 01:18:39 UTC; 20min ago Process: 17657 ExecStart=/bin/bash -c /usr/bin/voxl-mavcam-manager (code=killed, signal=ABRT) Main PID: 17657 (code=killed, signal=ABRT) Mar 05 01:18:39 apq8096 bash[17657]: snapshot_pipe_name: tracking Mar 05 01:18:39 apq8096 bash[17657]: video_record_pipe_name: tracking Mar 05 01:18:39 apq8096 bash[17657]: default_uri: rtsp://192.168.110.152:8900/live Mar 05 01:18:39 apq8096 bash[17657]: enable_auto_ip: 0 Mar 05 01:18:39 apq8096 bash[17657]: ================================================================= Mar 05 01:18:39 apq8096 bash[17657]: Camera name for qgc: Camera 0 Mar 05 01:18:39 apq8096 bash[17657]: Mavlink server Connected Mar 05 01:18:39 apq8096 systemd[1]: voxl-mavcam-manager.service: Main process exited, code=killed, status=6/ABRT Mar 05 01:18:39 apq8096 systemd[1]: voxl-mavcam-manager.service: Unit entered failed state. Mar 05 01:18:39 apq8096 systemd[1]: voxl-mavcam-manager.service: Failed with result 'signal'. -
voxl-inspect-mavlink mavlink_sys_status| ID | Mavlink MSG Name |Counter| Hz | |-------|-----------------------------|-------|------| | 1 | sys_status | 92 | 5.0 |@Kris , please try the following:
- verify the ip address of voxl2
- when you adb into voxl2, the ip address is printed
- you can use
ifconfigto check the ip address
- make sure
voxl-streameris running (it looks like it is based on output ofsystemctl status voxl-streamer - ping your voxl2 ip from your host machine (just to make sure it can reach voxl2)
- download ffmpeg / ffplay to your host machine
- perhaps something in VLC is not working, but ffmpeg / ffplay usually works
- on linux OS should be able to do it using
apt-get ffmpeg - for other OS you can find direct download : https://www.ffmpeg.org/download.html
play the video on the host machine (replace
voxl2-ipwith actual ip address)ffplay rtsp://<voxl2-ip>:8900/live - verify the ip address of voxl2
-
@Kris , please try the following:
- verify the ip address of voxl2
- when you adb into voxl2, the ip address is printed
- you can use
ifconfigto check the ip address
- make sure
voxl-streameris running (it looks like it is based on output ofsystemctl status voxl-streamer - ping your voxl2 ip from your host machine (just to make sure it can reach voxl2)
- download ffmpeg / ffplay to your host machine
- perhaps something in VLC is not working, but ffmpeg / ffplay usually works
- on linux OS should be able to do it using
apt-get ffmpeg - for other OS you can find direct download : https://www.ffmpeg.org/download.html
play the video on the host machine (replace
voxl2-ipwith actual ip address)ffplay rtsp://<voxl2-ip>:8900/liveTypically hires is the only pipe with encoding enabled by default, but in this case tracking is being used. Can you make sure encoding is enabled for the tracking camera in voxl-camera-server.conf ?
Or, can you just see if hires_enc is working in QGC first? That's what we ship by default on a fresh install hires_enc to QGC should by enabled by default.
- verify the ip address of voxl2
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login