@tom SOLVED, thanks Tom, that command line prompt showed me that I needed to voxl-configure-extrinsics. Thank you!

@tom We're running v1.0.1 SDK. However, we were actually just able to get the RTSP stream working over Herelink with virtually no latency. Using the SiYiQgroundControl application on the Herelink, the RTSP works completely fine. I believe the issue is in the QGC firmware that ships stock with the Herelink controller. For now you can consider this thread solved. Thanks again!

@Jeremy-Frederick Just tried a separate carrier board and modem and it seems to be working just fine now

@tom

Hello, for form factor reasons, and to get the maximum db output of the microhard module, I want to try and integrate the Microhard USB Carrier Board with the VOXL 2 instead of the standard Add on Board. I'm attempting to set it up identical to how the doodle labs radios integrate, through the USB 2 fastboot board on the VOXL 2. I have been unsuccessful in creating a network connection to the radio.

Is there any reason why this integration wouldn't work? Is there anything that can be done to get this integration to work?

@Viktor-Gal No, not yet, I have the service running but no overlay available.

Hello, I've begun playing around with the new open-vins implementation on VOXL 2 and I was curious when your team expects the documentation to be posted up on the website.

@Alex-Kushleyev

{
"version": 0.1,
"fsync_en": false,
"fsync_gpio": 109,
"cameras": [{
"type": "ar0144",
"name": "tracking",
"enabled": true,
"camera_id": 0,
"fps": 30,
"en_rotate": false,
"en_preview": true,
"preview_width": 1280,
"preview_height": 800,
"en_raw_preview": true,
"ae_mode": "lme_msv",
"ae_desired_msv": 60,
"exposure_min_us": 20,
"exposure_max_us": 33000,
"gain_min": 54,
"gain_max": 8000,
"exposure_soft_min_us": 5000,
"ae_filter_alpha": 0.600000023841858,
"ae_ignore_fraction": 0.20000000298023224,
"ae_slope": 0.05000000074505806,
"ae_exposure_period": 1,
"ae_gain_period": 1
}, {
"type": "imx214",
"name": "hires",
"enabled": true,
"camera_id": 1,
"fps": 30,
"en_preview": false,
"preview_width": 640,
"preview_height": 480,
"en_raw_preview": false,
"en_small_video": true,
"small_video_width": 1024,
"small_video_height": 768,
"small_venc_mode": "h265",
"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,
"en_large_video": true,
"large_video_width": 4208,
"large_video_height": 3120,
"large_venc_mode": "h265",
"large_venc_br_ctrl": "cqp",
"large_venc_Qfixed": 38,
"large_venc_Qmin": 15,
"large_venc_Qmax": 50,
"large_venc_nPframes": 29,
"large_venc_mbps": 30,
"en_snapshot": true,
"en_snapshot_width": 4208,
"en_snapshot_height": 3120,
"exif_focal_length": 0,
"exif_focal_length_in_35mm_format": 0,
"exif_fnumber": 0,
"ae_mode": "isp"
}]
}

@Alex-Kushleyev We have IMX214 connected to J7 Upper through the m0084 cable. Alongside it is a ARR0144 Tracking Camera connected to J7 Lower.

I've been using the IMX214 4k High-Resolution sensor for the past few days and I've noticed some fairly severe horizontal lines crowding the frame in dark environments. Any thoughts as to why this is? Is there anything I can do in the camera settings to limit this?

VOXL 2 , SDK 1.3

https://vimeo.com/1021115190

Hello. I've got an Add-on Ethernet hat for the VOXL 2 that I'm using on a bench top and the ETH0 RJ45 full ethernet port is not properly establishing a connection to my network. I'm running a VOXL 2 with SDK 1.3, when connected via a USB - ETH converter in the USB-A port, a connection is easily established. When I change out the component with another ethernet hat, the connection is automatically established as expected.

No lights on the network switch port light up, when inspecting with $ ethtool eth0, no network connection is read, I've attempted to force set an IP address which is successful but still leads to no network connection.

Thoughts?

We had a camera cable fail on us, flown on a VOXL 2 using an imx412 and OV7251 tracking camera. System was working fine until a minor crash, then video signal was lost. Trying to assess the reason why the cable would fail like this, could this be caused by the cable becoming partially unplugged while the aircraft was still powered? Let me know your thoughts. There definitely was not a screw or any other penetrative object that could have punctured the cable causing a short.