It will be released on 1.6.3. If you need the feature now, you can always build it from source and deploy to your voxl.

https://gitlab.com/voxl-public/voxl-sdk/services/voxl-portal/-/tree/dev?ref_type=heads

@kgn-mdlai Unfortunately, the April Tag code is quite outdated and hasn't been tested on any of our latest hardware. As it is now it is provided as reference code and if you are able to get things working correctly on your own we are happy to accept PRs to the repo. We do plan an update of this in a future revision of the SDK but there is no scheduled date that we can provide right now.

@Nitin-Varma-Vegesna

Hello, please provide your platform specs and sdk version.

Hello @ApoorvThapliyal,

Is there anything that looks wrong or off about the configuration? Should I look at any other file in particular?

@tejasram The source code is here: https://gitlab.com/voxl-public/voxl-sdk/services/voxl-tag-detector. Perhaps try changing #define MAX_TAG_LOCATIONS 64 in locations.h.

@Alex-Kushleyev
We are designing our custom adapter board which will have mating connector DF56C-26S-0.3V(51) on board to connect MSU-M0186-1-09 camera module.

And we are planning to test synchronicity with other camera. So just wanted to confirm master or slave mode is configured from firmware or is there any dependency on hardware is well for this configuration.
let me know if more details are needed.

Regards,
Richa

@Alex-Kushleyev This was what I got when opening the file in SolidWorks:
a3f8d672-9ddc-465e-85c5-f40e6203ce29-image.png

I found a symlink mismatch in the file tree... pushing M073 PCB board with M0172 connector.

Anyway, it is solved now:

8f13ae56-bfcd-4829-8bd1-e238097e9bb0-image.png

Thank you.

Regards,
Jacob

@Alex-Kushleyev Found the reason why it was skipping. In /px4-firmware/src/lib/parameters/CMakeLists.txt there is a line that skips all modules that match 'pwm_out'. I was able to disable that for PCA9685. Once I disabled the module.yaml file being skipped it worked. No need for the .c file (which makes sense, that is just the old way to do the .yaml)

Hi @Rowan-Dempster ,

We just merged the changes to dev : https://gitlab.com/voxl-public/voxl-sdk/core-libs/libmodal-pipe/-/merge_requests/39.

A new build of the libmodal-pipe library will be added after tonight's nightly build here : http://voxl-packages.modalai.com/dists/qrb5165/dev/binary-arm64/ .

Any SDK releases after this will include this support.

Alex

@taiwohazeez This is what most people use: https://qgroundcontrol.com/

@Sarika-Sharma ,

If you have multiple active network interfaces, then you need to set up routing rules using standard linux network tools (ip route ..). You can check the current routes using ip route list on voxl2.

voxl-my-ip script probably just returns the first available ip address. you can use ifconfig to check all the interfaces.

As an example... assuming your wifi ip range is 192.168.10.x (192.168.10.1 is the wifi router's ip address) and usb0 is 192.168.7.x

# route to the Linux host (192.168.7. subnet) via usb0 sudo ip route add 192.168.7.0/24 via 192.168.7.1 dev usb0 # default route for all other traffic via wlan0 sudo ip route add default via 192.168.10.1 dev wlan0

If you want to make these routes persistent you will have to edit /etc/network/interfaces.. Please check Linux networking documentation.

Alex

@lhermosillo It was 15 with/without the GPS.

@ggangmi What was the flight mode on takeoff and what did it unexpectedly change to? There should be logs in /data/px4/log. They may be incomplete or maybe even corrupted if the drone lost power in the crash but there should be something there. The logging starts when the drone is armed.

@Nitin-Varma-Vegesna If you re-install or update your SDK to the latest it will properly set all of the parameters.

@alan123 Hi, sorry for the late reply. Unfortunatly, we have not finished it yet. We're switching from ntrip to ros2

@Sarika-Sharma ,

Since you are testing different configurations, i would suggest to reduce the number of cameras first to find working cases and see if you may have a bad camera or a bad flex cable.

So, try both tracking camera one at a time, then hires camera by itself, then two tracking cameras, then two tracking + hires, etc..

Alex

@Jetson-Nano ,

We have not tried QVIO with Boson, it may work (but we can't really support that). The boson output is usually a bit fuzzy, so i am not sure how the feature detection will work, but it may be ok. Disabling FFC will definitely resolve the gaps in the frame feed, but disabling the FFC will also affect the Boson image quality, which may degrade over time.

If you wanted to use any USB (thermal) camera with VIO, you would just have to use voxl-uvc-server to publish the images to mpa, so that voxl-qvio-server can subscribe to them. The only issue is that the uvc interface does not provide accurate timestamp of the camera, but it may be ok just to use the time of arrival of the frame. QVIO does estimate the time offset between the IMU and camera, so as long as the timestamp is consistently captured, it should be ok..

Alex