Hi, I'm working on April Tag setup for the tracking camera (SDK 1.1.1, M0149 Camera). I've run through the voxl-configure-tag-detector wizard, set to factory default, and enabled. I haven't changed anything with the other configuration files. My issue arises when I'm trying to check output, but voxl-inspect-tags is producing the following, without proceeding (tried waiting for +5 minutes, power cycled and waited again):

I'm able to see the live tracking camera output via Voxl Portal, but it's not giving me anything indicating that it's picking up on the tag.

@Moderator Ah, yep. That fixed it. Thanks for the help!

@Eric-Katzfey date gives me 3/2/23. I'm using SoftAP, so I guess it makes sense that files that I've pushed while on WiFi have the correct date, but the videos are using the default date.

I tried the above suggested by @Moderator and it worked, adding the new video to the folder.

Pulling the direct file name ./adb pull /data/video/video_2023-03-02_13:16:02.h265 gives me an error; pulling just /data/video gives me the same error. Could it be a corrupted file?

Updated ls -la /data/video output

I'm working on recording videos and taking snapshots (VOXL SDK 1.1.1. ). I'm following the steps outlined in the MAVCam Manager Doc, and using QGC to take the photos and videos. The snapshots are automatically transferred directly onto my laptop in the photos folder within the QGC folder by just clicking the shutter button (no pulling required).

However, I'm having issues accessing the videos. The doc says that videos are saved locally to the VOXL disc. ls -la /data/videos and ls -la /data/snapshots returns that old files exist, but the new recordings/photos aren't there (recorded 4/29/24). Also, pulling returns two empty folders.

Here's the output of ls -la /data and voxl-inspect-services, in case it's helpful.

@Alex-Kushleyev I changed the resolution to be correct, and we finally have feed! Live output in voxl portal and voxl-inspect-cam.

I've confirmed that M0036 cable is bad, the tracking camera isn't able to connect when routed through the cable.

However, we have a major issue with the feed we are receiving. We think it's a combination of bad focus + a possibly scratched lens... maybe you can help us diagnose. This the tracking output in Voxl Portal using the 9x6 checkerboard. We're using other forum threads to try and test out focus but I'd love to hear your preliminary thoughts.

@Alex-Kushleyev I'm trying to run voxl-camera-server and I'm getting error messages for both cameras; The hires camera makes sense, but I'm not sure about the tracking cam...

I've swapped the M0149 back to the JL port where it was originally. Also, I personally haven't gotten the hires camera working, but I agree that it's more likely the cable.

Starting Camera: tracking
Using gain limits min: 54 max: 863
ERROR:   Camera 0 failed to find supported preview config: 640x480
ERROR:   Failed to start camera: tracking
Starting Camera: hires
ERROR:   failed to call HAL3 get_camera_info for cam 1
ERROR:   Failed to start camera: hires

------ voxl-camera-server: Camera server is now running 

I'm not getting any output. Also, voxl-inspect-services lists voxl-camera-server | Enabled | Not Running | (I'm assuming it's because it has no cameras to run). Voxl Portal and voxl-inspect-cam show no camera streams.

@Vinny I think you may be mistaken... One end of the M0036 is connected to the M0135, and the other end is connected to the M0107 Camera (that's inside the purple case). We're only using one M0135.

I'm receiving a new M0036 cable tomorrow. I'll test that.

@Alex-Kushleyev Ran through the troubleshooting steps (swapping both connections), still only getting one camera (same ID, just on the other slot). I think I'll just replace the cable.

Can I work on the setup on only one sensor, with a simple way to add another one? Or will I have to redo the whole setup when I have both?

voxl2-mini:/$ voxl-camera-server -l
existing instance of voxl-camera-server found, attempting to stop it
DEBUG:   Attempting to open the hal module
DEBUG:   SUCCESS: Camera module opened on attempt 0
DEBUG:   ----------- Number of cameras: 1

DEBUG:   Cam idx: 0, Cam slot: 3, Slave Address: 0x0030, Sensor Id: 0x0356
DEBUG:   Note: This list comes from the HAL module and may not be indicative
DEBUG:          of configurations that have full pipelines

DEBUG:   Number of cameras: 1

@Alex-Kushleyev ok, the imx412_3 bin file is in /usr/lib/camera/, but I'm still only sensing 1 camera.

Also, I'll be on spring break, so I apologize for a potential lack of response.

@Alex-Kushleyev Is there somewhere I can download the imx412_3.bin file? It's not in the output of ./adb shell ls -la /usr/lib/camera

The flex connector comes straight away from the camera.

I've pushed the server config file.