wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 2312
inet 169.254.233.208 netmask 255.255.0.0 broadcast 169.254.255.255
inet6 fe80::ddc:47bd:f5ec:71dd prefixlen 64 scopeid 0x20<link>
ether 10:5a:95:c7:9e:69 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 30 overruns 0 carrier 0 collisions 0
S
Posts made by SKA
-
RE: Station Mode Issue with Voxl Suite 1.6.3posted in Ask your questions right here!
-
RE: Station Mode Issue with Voxl Suite 1.6.3posted in Ask your questions right here!
@Alex-Kushleyev Here's what I see! I wonder if this is the problem:
/etc/network/interfaces: No such file or directoryvoxl2-mini (M0104):/$ journalctl -u dhcpcd -- Logs begin at Thu 2023-03-02 12:58:02 UTC, end at Fri 2026-04-03 16:11:48 UTC. -- Mar 02 12:58:04 m0104 systemd[1]: Starting LSB: IPv4 DHCP client with IPv4LL support... Mar 02 12:58:04 m0104 dhcpcd[1250]: grep: /etc/network/interfaces: No such file or directory Mar 02 12:58:05 m0104 dhcpcd[1309]: no interfaces have a carrier Mar 02 12:58:05 m0104 dhcpcd[1309]: forked to background, child pid 1503 Mar 02 12:58:05 m0104 systemd[1]: Started LSB: IPv4 DHCP client with IPv4LL support. Mar 02 12:58:06 m0104 dhcpcd[1503]: bond0: waiting for carrier Mar 02 12:58:06 m0104 dhcpcd[1503]: dummy0: waiting for carrier Mar 02 12:58:06 m0104 dhcpcd[1503]: wlan0: waiting for carrier Mar 02 12:58:06 m0104 dhcpcd[1503]: dummy0: carrier acquired Mar 02 12:58:06 m0104 dhcpcd[1503]: DUID 00:01:00:01:2b:93:59:de:b6:a9:9d:64:6d:02 Mar 02 12:58:06 m0104 dhcpcd[1503]: dummy0: IAID 9d:64:6d:02 Mar 02 12:58:06 m0104 dhcpcd[1503]: dummy0: adding address fe80::54fe:595c:4ff6:b95c Mar 02 12:58:06 m0104 dhcpcd[1503]: dummy0: soliciting a DHCP lease Mar 02 12:58:07 m0104 dhcpcd[1503]: dummy0: soliciting an IPv6 router Mar 02 12:58:10 m0104 dhcpcd[1503]: wlan0: carrier acquired Mar 02 12:58:10 m0104 dhcpcd[1503]: wlan0: IAID ca:b3:a6:89 Mar 02 12:58:10 m0104 dhcpcd[1503]: wlan0: adding address fe80::bc34:9301:bd06:6b68 Mar 02 12:58:11 m0104 dhcpcd[1503]: wlan0: soliciting a DHCP lease Mar 02 12:58:11 m0104 dhcpcd[1503]: wlan0: soliciting an IPv6 router Mar 02 12:58:12 m0104 dhcpcd[1503]: wlan0: offered 10.10.10.116 from 10.10.10.1 Mar 02 12:58:12 m0104 dhcpcd[1503]: wlan0: probing address 10.10.10.116/24 Mar 02 12:58:17 m0104 dhcpcd[1503]: wlan0: leased 10.10.10.116 for 86400 seconds Mar 02 12:58:17 m0104 dhcpcd[1503]: wlan0: adding route to 10.10.10.0/24 Mar 02 12:58:17 m0104 dhcpcd[1503]: wlan0: adding default route via 10.10.10.1 Mar 02 12:58:19 m0104 dhcpcd[1503]: dummy0: no IPv6 Routers available Mar 02 12:58:24 m0104 dhcpcd[1503]: wlan0: no IPv6 Routers available -- Reboot -- Apr 03 15:39:02 m0104 systemd[1]: Starting LSB: IPv4 DHCP client with IPv4LL support... Apr 03 15:39:02 m0104 dhcpcd[1899]: grep: /etc/network/interfaces: No such file or directory Apr 03 15:39:03 m0104 dhcpcd[2026]: no interfaces have a carrier Apr 03 15:39:03 m0104 dhcpcd[2262]: bond0: waiting for carrier Apr 03 15:39:03 m0104 dhcpcd[2262]: dummy0: waiting for carrier Apr 03 15:39:03 m0104 dhcpcd[2262]: wlan0: waiting for carrier Apr 03 15:39:03 m0104 dhcpcd[2262]: dummy0: carrier acquired Apr 03 15:39:03 m0104 dhcpcd[2026]: forked to background, child pid 2262 Apr 03 15:39:03 m0104 systemd[1]: Started LSB: IPv4 DHCP client with IPv4LL support. Apr 03 15:39:03 m0104 dhcpcd[2262]: DUID 00:01:00:01:2b:93:59:de:b6:a9:9d:64:6d:02 Apr 03 15:39:03 m0104 dhcpcd[2262]: dummy0: IAID 7e:3c:18:e8 Apr 03 15:39:03 m0104 dhcpcd[2262]: dummy0: adding address fe80::e48d:a57d:cf5f:95ce Apr 03 15:39:03 m0104 dhcpcd[2262]: dummy0: soliciting an IPv6 router Apr 03 15:39:04 m0104 dhcpcd[2262]: dummy0: soliciting a DHCP lease Apr 03 15:39:12 m0104 dhcpcd[2262]: wlan0: carrier acquired Apr 03 15:39:12 m0104 dhcpcd[2262]: wlan0: IAID ca:b3:a6:89 Apr 03 15:39:12 m0104 dhcpcd[2262]: wlan0: adding address fe80::bc34:9301:bd06:6b68 Apr 03 15:39:12 m0104 dhcpcd[2262]: wlan0: soliciting a DHCP lease Apr 03 15:39:12 m0104 dhcpcd[2262]: wlan0: offered 10.10.10.116 from 10.10.10.1 Apr 03 15:39:12 m0104 dhcpcd[2262]: wlan0: probing address 10.10.10.116/24 Apr 03 15:39:13 m0104 dhcpcd[2262]: wlan0: soliciting an IPv6 router Apr 03 15:39:15 m0104 dhcpcd[2262]: dummy0: no IPv6 Routers available Apr 03 15:39:17 m0104 dhcpcd[2262]: wlan0: leased 10.10.10.116 for 86400 seconds Apr 03 15:39:17 m0104 dhcpcd[2262]: wlan0: adding route to 10.10.10.0/24 Apr 03 15:39:17 m0104 dhcpcd[2262]: wlan0: adding default route via 10.10.10.1 Apr 03 15:39:26 m0104 dhcpcd[2262]: wlan0: no IPv6 Routers available -- Reboot -- Apr 03 15:39:54 m0104 systemd[1]: Starting LSB: IPv4 DHCP client with IPv4LL support... -- Reboot -- Apr 03 15:39:54 m0104 systemd[1]: Starting LSB: IPv4 DHCP client with IPv4LL support... -- Reboot -- Apr 03 15:39:54 m0104 systemd[1]: Starting LSB: IPv4 DHCP client with IPv4LL support... -- Reboot -- Apr 03 15:39:54 m0104 systemd[1]: Starting LSB: IPv4 DHCP client with IPv4LL support... -- Reboot -- Apr 03 15:39:54 m0104 systemd[1]: Starting LSB: IPv4 DHCP client with IPv4LL support... -- Reboot -- Apr 03 15:39:54 m0104 systemd[1]: Starting LSB: IPv4 DHCP client with IPv4LL support... -- Reboot -- Apr 03 15:39:54 m0104 systemd[1]: Starting LSB: IPv4 DHCP client with IPv4LL support... -- Reboot -- --More-- -
RE: Station Mode Issue with Voxl Suite 1.6.3posted in Ask your questions right here!
@Alex-Kushleyev When I run
tail -n 100 /var/log/syslog, I don't see any messages coming fromm0104 dhcpcdorm0104 wpa_supplicantedit: I turned the USB VBUS off and on, and saw this pop up on syslog:
Apr 3 16:07:44 m0104 dhcpcd[2276]: wlan0: probing for an IPv4LL address -
RE: Station Mode Issue with Voxl Suite 1.6.3posted in Ask your questions right here!
@Alex-Kushleyev After turning it off and on, this was the dmesg output:
[ 1075.483890] usb 1-1: USB disconnect, device number 2 [ 1081.832158] usb 1-1: new high-speed USB device number 3 using xhci-hcd [ 1081.969792] usb 1-1: New USB device found, idVendor=2357, idProduct=011e, bcdDevice= 2.00 [ 1081.969808] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 1081.969819] usb 1-1: Product: 802.11ac WLAN Adapter [ 1081.969827] usb 1-1: Manufacturer: Realtek [ 1081.969836] usb 1-1: SerialNumber: 00e04c000001 [ 1082.194843] usb 1-1: 88XXau 10:5a:95:c7:9e:69 hw_info[107] [ 1082.911593] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 1082.911656] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready -
RE: Station Mode Issue with Voxl Suite 1.6.3posted in Ask your questions right here!
@Alex-Kushleyev I didn't add the station_band file, and this is a freshly flashed voxl. Removing/changing it to 2.4ghz didn't help unfortunately.
voxl2-mini (M0104):/$ iwconfig wlan0 wlan0 unassociated ESSID:"" Nickname:"<WIFI@REALTEK>" Mode:Managed Frequency=2.412 GHz Access Point: Not-Associated Sensitivity:0/0 Retry:off RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality=0/100 Signal level=0 dBm Noise level=0 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 -
RE: Station Mode Issue with Voxl Suite 1.6.3posted in Ask your questions right here!
@Alex-Kushleyev Hi!
I'm facing the same issue using station mode on sdk v1.6.3.
I've tried using the ALFA AWU2036 as well as the TP-LINK AC600.
Changing back to sdk 1.6.0, it works as expected.voxl2-mini (M0104):/$ voxl-my-ip 169.254.233.208 (wlan0) voxl2-mini (M0104):/$ ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8): 56 data bytes 92 bytes from 169.254.233.208: Destination Host Unreachable 92 bytes from 169.254.233.208: Destination Host Unreachable 92 bytes from 169.254.233.208: Destination Host Unreachable 92 bytes from 169.254.233.208: Destination Host Unreachable 92 bytes from 169.254.233.208: Destination Host Unreachable ^C92 bytes from 169.254.233.208: Destination Host Unreachable --- 8.8.8.8 ping statistics --- 7 packets transmitted, 0 packets received, 100% packet loss voxl2-mini (M0104):/$ cat /data/misc/wifi/wpa_supplicant.conf # Only WPA-PSK is used. Any valid cipher combination is accepted. ctrl_interface=/var/run/wpa_supplicant update_config=1 network={ #Open # ssid="example open network" # key_mgmt=NONE #WPA-PSK ssid="xxxxxxx" #proto=WPA key_mgmt=WPA-PSK pairwise=TKIP CCMP group=TKIP CCMP psk="yyyyyyy" #WEP # ssid="example wep network" # key_mgmt=NONE # wep_key0="abcde" # wep_key1=0102030405 # wep_tx_keyidx=0 } wowlan_triggers=magic_pkt voxl2-mini (M0104):/$ cd data/misc/wifi/ voxl2-mini (M0104):/data/misc/wifi$ ls hostapd.conf station_band station_interface station_ssid wlan_mode wpa_supplicant.conf voxl2-mini (M0104):/data/misc/wifi$ cat station_band 2ghz -
Camera status when voxl-camera-server is not runningposted in Video and Image Sensors
Hi!
I was wondering if the cameras and interposer board remain powered on but on standby or if they are entirely powered off when the
voxl-camera-serveris not running.Thanks!
-
EIS cam-server crashposted in Video and Image Sensors
Hi! @Alex-Kushleyev
When I run
voxl-camera-serverv2.2.17 following all the instructions for the EIS tech docs, I'm seeing the server crash. All the camera pipes are initialized, and the camera server starts with no problems, but when I either try to open the stream or attemptvoxl-inspect-cam-ascii hires_misp_greythe camera server aborts. I'm using an imx412 sensor. Here are the error messages I see when I run the server in debug mode and then attempt to open the stream in voxl-portal:VERBOSE: setting hal3 exposure for hires 5259763 800 VERBOSE: setting hal3 exposure for hires 5259763 800 VERBOSE: setting hal3 exposure for hires 5259763 800 VERBOSE: setting hal3 exposure for hires 5259763 800 VERBOSE: setting hal3 exposure for hires 5259763 800 VERBOSE: setting hal3 exposure for hires 5259763 800 VERBOSE: setting hal3 exposure for hires 5259763 800 VERBOSE: setting hal3 exposure for hires 5259763 800 VERBOSE: added request for small video stream VERBOSE: Sending request for frame 0 for camera hires for 1 streams VERBOSE: Received result from HAl3 for frame number 0 VERBOSE: Received 0 buffers from camera hires, partial result:1 VERBOSE: finished sending request for frame 0 for camera hires VERBOSE: returning from SendOneCaptureRequest for frame 1 for camera hires VERBOSE: setting hal3 exposure for hires 5259763 800 VERBOSE: added request for small video stream VERBOSE: Sending request for frame 1 for camera hires for 1 streams VERBOSE: finished sending request for frame 1 for camera hires VERBOSE: returning from SendOneCaptureRequest for frame 2 for camera hires VERBOSE: setting hal3 exposure for hires 5259763 800 VERBOSE: added request for small video stream VERBOSE: Sending request for frame 2 for camera hires for 1 streams VERBOSE: finished sending request for frame 2 for camera hires VERBOSE: returning from SendOneCaptureRequest for frame 3 for camera hires VERBOSE: setting hal3 exposure for hires 5259763 800 VERBOSE: added request for small video stream VERBOSE: Sending request for frame 3 for camera hires for 1 streams VERBOSE: finished sending request for frame 3 for camera hires VERBOSE: returning from SendOneCaptureRequest for frame 4 for camera hires VERBOSE: setting hal3 exposure for hires 5259763 800 VERBOSE: added request for small video stream VERBOSE: Sending request for frame 4 for camera hires for 1 streams VERBOSE: finished sending request for frame 4 for camera hires VERBOSE: returning from SendOneCaptureRequest for frame 5 for camera hires VERBOSE: setting hal3 exposure for hires 5259763 800 VERBOSE: added request for small video stream VERBOSE: Sending request for frame 5 for camera hires for 1 streams VERBOSE: Received result from HAl3 for frame number 1 VERBOSE: Received 0 buffers from camera hires, partial result:1 VERBOSE: Received result from HAl3 for frame number 2 VERBOSE: Received 0 buffers from camera hires, partial result:1 DEBUG: Value of pitmode_active is: 1 DEBUG: Value of pitmode_active is: 1 DEBUG: Value of pitmode_active is: 1 DEBUG: Value of pitmode_active is: 1 DEBUG: Value of pitmode_active is: 1 VERBOSE: finished sending request for frame 5 for camera hires VERBOSE: returning from SendOneCaptureRequest for frame 6 for camera hires VERBOSE: setting hal3 exposure for hires 5259763 800 ERROR: Received "Result" error from camera: hires, frame number 0 ERROR: Received "Buffer" error from camera: hires, frame number 0 VERBOSE: added request for small video stream VERBOSE: Sending request for frame 6 for camera hires for 1 streams WARNING: Pushed buffers back to pools for frame: 0 VERBOSE: Received result from HAl3 for frame number 0 VERBOSE: Received 1 buffers from camera hires, partial result:0 VERBOSE: Received output buffer 0 from camera hires VERBOSE: Buffer arrive before meta frame 0 ERROR: Received "Result" error from camera: hires, frame number 1 ERROR: Received "Buffer" error from camera: hires, frame number 1 WARNING: Pushed buffers back to pools for frame: 1 VERBOSE: Received result from HAl3 for frame number 1 VERBOSE: Received 1 buffers from camera hires, partial result:0 VERBOSE: Received output buffer 1 from camera hires VERBOSE: Buffer arrive before meta frame 1 ERROR: Received "Result" error from camera: hires, frame number 2 ERROR: Received "Buffer" error from camera: hires, frame number 2 WARNING: Pushed buffers back to pools for frame: 2 VERBOSE: Received result from HAl3 for frame number 2 VERBOSE: Received 1 buffers from camera hires, partial result:0 VERBOSE: Received output buffer 2 from camera hires VERBOSE: Buffer arrive before meta frame 2 ERROR: Received "Request" error from camera: hires, frame number 3 WARNING: Pushed buffers back to pools for frame: 3 VERBOSE: Received result from HAl3 for frame number 3 VERBOSE: Received 1 buffers from camera hires, partial result:0 VERBOSE: Received output buffer 3 from camera hires VERBOSE: Buffer arrive before meta frame 3 ERROR: Received "Request" error from camera: hires, frame number 4 WARNING: Pushed buffers back to pools for frame: 4 VERBOSE: Received result from HAl3 for frame number 4 VERBOSE: Received 1 buffers from camera hires, partial result:0 VERBOSE: Received output buffer 4 from camera hires VERBOSE: Buffer arrive before meta frame 4 ERROR: Received "Request" error from camera: hires, frame number 5 WARNING: Pushed buffers back to pools for frame: 5 VERBOSE: Received result from HAl3 for frame number 5 VERBOSE: Received 1 buffers from camera hires, partial result:0 VERBOSE: Received output buffer 5 from camera hires VERBOSE: Buffer arrive before meta frame 5 DEBUG: Value of pitmode_active is: 1 DEBUG: Value of pitmode_active is: 1 DEBUG: Value of pitmode_active is: 1 DEBUG: Value of pitmode_active is: 1 DEBUG: Value of pitmode_active is: 1 DEBUG: Value of pitmode_active is: 1 DEBUG: Value of pitmode_active is: 1Let me know if you have any advice on how to resolve this, thanks!
-
voxl-cross error when building voxl-open-vins-serverposted in VOXL SDK
Hi!
When I try to build voxl-open-vins-server using voxl-cross:V4.4, first I run:./install_build_deps.sh qrb5165 devAfter which I build and face this error:
voxl-cross(4.4):~(voxl-open-vins-server)(0.5.6)$ ./build.sh qrb5165 Found voxl-cross version: 4.4 -- --------------------------------------------------------- -- Using voxl-cross 64-bit toolchain for QRB5165 ubun1 18.04 -- C Compiler : /usr/bin/aarch64-linux-gnu-gcc-7 -- C++ Compiler: /usr/bin/aarch64-linux-gnu-g++-7 -- Sysroot : /opt/sysroots/qrb5165_1 -- C flags : -isystem=/usr/lib/gcc/aarch64-linux-gnu/7/include -isystem=/usr/local/include -isystem=/usr/lib/gcc/aarch64-linux-gnu/7/include-fixed -isystem=/usr/include/aarch64-linux-gnu -isystem=/usr/include -idirafter /usr/include -march=armv8.2-a -- CXX flags : -isystem=/usr/include/c++/7 -isystem=/usr/include/aarch64-linux-gnu/c++/7 -isystem=/usr/include/c++/7/backward -isystem=/usr/lib/gcc/aarch64-linux-gnu/7/include -isystem=/usr/local/include -isystem=/usr/lib/gcc/aarch64-linux-gnu/7/include-fixed -isystem=/usr/include/aarch64-linux-gnu -isystem=/usr/include -idirafter /usr/include -march=armv8.2-a -- Link Flags : -B/opt/sysroots/qrb5165_1/usr/lib/ -L/opt/sysroots/qrb5165_1/usr/lib/gcc/aarch64-linux-gnu/7 -L/opt/sysroots/qrb5165_1/usr/lib/aarch64-linux-gnu -L/opt/sysroots/qrb5165_1/usr/lib -L/opt/sysroots/qrb5165_1/lib/aarch64-linux-gnu -L/opt/sysroots/qrb5165_1/usr/lib/aarch64-linux-gnu -L/opt/sysroots/qrb5165_1/lib -L/usr/lib64 -L/usr/lib DEBUG BUILD -- EN_ION_BUF enabled CMake Warning (dev) at CMakeLists.txt:35 (find_package): Policy CMP0167 is not set: The FindBoost module is removed. Run "cmake --help-policy CMP0167" for policy details. Use the cmake_policy command to set the policy and suppress this warning. This warning is for project developers. Use -Wno-dev to suppress it. CMake Error at /usr/share/cmake-3.31/Modules/FindBoost.cmake:1858 (file): file STRINGS file "/usr/include/boost/version.hpp" cannot be read. Call Stack (most recent call first): CMakeLists.txt:35 (find_package) CMake Warning at /usr/share/cmake-3.31/Modules/FindBoost.cmake:1031 (message): Imported targets and dependency information not available for Boost version 0.0.0 (all versions older than 1.33) Call Stack (most recent call first): /usr/share/cmake-3.31/Modules/FindBoost.cmake:1539 (_Boost_COMPONENT_DEPENDENCIES) /usr/share/cmake-3.31/Modules/FindBoost.cmake:2151 (_Boost_MISSING_DEPENDENCIES) CMakeLists.txt:35 (find_package) CMake Error at /usr/share/cmake-3.31/Modules/FindPackageHandleStandardArgs.cmake:233 (message): Could NOT find Boost: Found unsuitable version "0.0.0", but required is at least "1.63.0" (found /usr/include, ) Call Stack (most recent call first): /usr/share/cmake-3.31/Modules/FindPackageHandleStandardArgs.cmake:601 (_FPHSA_FAILURE_MESSAGE) /usr/share/cmake-3.31/Modules/FindBoost.cmake:2409 (find_package_handle_standard_args) CMakeLists.txt:35 (find_package) -- Configuring incomplete, errors occurred! make: /usr/local/bin/cmake: No such file or directory make: *** [Makefile:257: cmake_check_build_system] Error 127Let me know how I can get past this, thanks!
-
RE: Calibration for EISposted in Video and Image Sensors
@Alex-Kushleyev Thanks!
This is what I'm seeing with voxl-camera-server set to the following:
"en_misp": true, "preview_width": 4040, "preview_height": 3040, "misp_width": 2020, "misp_height": 1520, "misp_awb": "auto", "misp_zoom": 1., "en_eis": false, "eis_mode": "full-follow", "eis_view": "eis-only", "eis_follow_rate": 0.01, "en_large_video": false, "en_small_video": true,I'll keep debugging why this is happening. Will EIS accept an intrinsics file calibrated from hires_small_grey setting the width and height to 2020x1520?
-
RE: Calibration for EISposted in Video and Image Sensors
@Alex-Kushleyev I'm looking at hires_misp_grey. I know I've been looking at the misp streams all along because they haven't been fisheye, like the hires_small_grey stream.
Also, just checked out the zoom slider in voxl-portal, it doesn't seem to work -
RE: Calibration for EISposted in Video and Image Sensors
@Alex-Kushleyev No, it doesn't change. Let me try adjusting in voxl-portal.
-
RE: Calibration for EISposted in Video and Image Sensors
@Alex-Kushleyev I tried 1.0 as well, it didn't make a difference.
-
Calibration for EISposted in Video and Image Sensors
Hi! When I follow the instructions on here to calibrate at half resolution for EIS, I'm noticing that the output video is zoomed in. Even setting misp_zoom to 0, and resolution to 4040x3040 for an imx412 camera is not giving me the full camera view.
I'm using voxl-camera-server_2.2.4
Here is my voxl-camera-server.conf file:{ "type": "imx412", "name": "hires", "enabled": true, "camera_id": 1, "fps": 10, "en_preview": true, "en_raw_preview": true, "en_misp": true, "preview_width": 4040, "preview_height": 3040, "misp_width": 2020, "misp_height": 1520, "misp_awb": "auto", "misp_zoom": 0, "en_eis": false, "eis_mode": "full-follow", "eis_view": "eis-only", "eis_follow_rate": 0.01, "en_large_video": false, "en_small_video": true, "en_snapshot": false, "ae_mode": "lme_msv", "en_rotate": false, "misp_venc_enable": true, "misp_venc_mode": "h264", "misp_venc_br_ctrl": "cbr", "misp_venc_Qfixed": 30, "misp_venc_Qmin": 15, "misp_venc_Qmax": 51, "misp_venc_nPframes": 29, "misp_venc_mbps": 3, "ae_desired_msv": 100, "exposure_min_us": 25, "exposure_max_us": 5000, "gain_min": 100, "gain_max": 32000, "exposure_soft_min_us": 5000, "snapshot_jpeg_quality": 75, "small_video_width": 1024, "small_video_height": 768, "small_venc_mode": "h264", "small_venc_br_ctrl": "cqp", "small_venc_Qfixed": 30, "small_venc_Qmin": 15, "small_venc_Qmax": 40, "small_venc_nPframes": 9, "small_venc_mbps": 2, "small_venc_osd": false, "large_video_width": 4056, "large_video_height": 3040, "large_venc_mode": "h264", "large_venc_br_ctrl": "cqp", "large_venc_Qfixed": 40, "large_venc_Qmin": 15, "large_venc_Qmax": 50, "large_venc_nPframes": 29, "large_venc_mbps": 40, "large_venc_osd": false, "en_snapshot_width": 4056, "en_snapshot_height": 3040, "exif_focal_length": 3.0999999046325684, "exif_focal_length_in_35mm_format": 17, "exif_fnumber": 1.2400000095367432, "misp_venc_osd": false, "misp_gamma": 1.6, "ae_filter_alpha": 0.600000023841858, "ae_ignore_fraction": 0.20000000298023224, "ae_slope": 0.05000000074505806, "ae_exposure_period": 1, "ae_gain_period": 1 } -
RE: RTSP streaming issuesposted in VOXL 2 Mini
Hey @Alex-Kushleyev! To answer your questions:
-
Yes, with the latest SDK, RTSP streaming works in VLC as long as the cache is not set to 0 ms. I’ve seen stable playback once the cache is increased (around ~300 ms).
-
I’m using VLC to test playback, but I also tested using ffmpeg and was able to successfully record video from the RTSP stream even with 0ms cache. This led me to think that frames are being transmitted correctly, but there’s likely a timing / timestamp issue in the RTSP stream that ffmpeg is tolerant of, but causes VLC to freeze. I don't remember the exact command I used but it was similar to:
ffmpeg \ -rtsp_transport tcp \ -fflags nobuffer \ -flags low_delay \ -an \ -i rtsp://<voxl-ip>:8900/live \ -t 10 \ -c copy \ out.mp4- Yes, '''hires_misp_color''' has been available when I've tested this. When I set VLC to 0ms cache, I always only receive one frame before the stream freezes.
-
-
RE: RTSP streaming issuesposted in VOXL 2 Mini
Following up on this, @Alex-Kushleyev do you have any initial leads that might help me - thanks!
-
RTSP streaming issuesposted in VOXL 2 Mini
Hi! I need to be able to network stream to VLC with caching set to 0ms. It seems like older SDKs stream just fine with 0ms cache, but SDK 1.6.0 does not.
Using SDK 1.4.0, I'm able to stream with no problems. The voxl-streamer version is 0.7.5, and I also switched over to voxl-streamer 0.8.0 (from SDK1.6) to narrow down the root cause of the problem, but noticed that streaming worked in this configuration too.
Then, I flashed the voxl to SDK 1.6.0, and tried both versions of voxl-streamer (0.7.5 and 0.8.0) and neither of them were able to stream with 0ms cache.
Where should I look to solve this problem? Thanks!
For reference, here's my voxl-streamer.conf:
voxl2-mini-test-fixture (TF-M0104):/$ cat etc/modalai/voxl-streamer.conf { "input-pipe": "hires_misp_color", "bitrate": 3000000, "rotation": 0, "decimator": 1, "encoder": "h264", "port": 8900 } -
RE: EIS functionalityposted in Video and Image Sensors
@Alex-Kushleyev I verified that I used the correct drivers and had already updated
maxRAWSizeson/vendor/etc/camera/camxoverridesettings.txt. I just went through the updated EIS docs and I am still seeing the same errors. Let me know if there's anything else I can check!