Hi @joseph-vale , i tested the python script from FLIR help site (Radiometry.py). I just had to modify it to use the correct USB and Video devices. The script ran find, but since my Boson does not support radiometric output, the reported temperature was like 70 degrees colder than it should be (reporting -50C at room temperature). Are you able to get correct temperatures with your device using this script? As i mentioned before, there is a way of getting the image data from voxl-camera-server into python. I think it would be interesting to try running the same exact conversion and annotation code from the FLIR example. This would allow you to first check the temperatures using a USB connection and then check them using the VOXL2 pipeline. I am going to set up an example that that uses pympa (python wrapper for MPA) to get the 16bit data from Boson and plot + convert it to temperature using the reference code. Alex

@voxltester Only if it is connected to a GCS that sends the Mavlink SYSTEM_TIME message.

@Zachary-Lowell-0 and @smiley , I just updated the docs to include more info on this https://docs.modalai.com/M0153/#misc-connector-pinout Also verified that i could ping a i2c device connected to M0201 J4 and M0201 itself is connected to VOXL2 J7 via M0181 (there are other options how to connect M0201 to VOXL). IMU -> [JST GH cable] -> (M0201 J4) .... (M0201 J2) -> [MIPI COAX cable] -> (M0181 J1) .... (M0181) -> (VOXL2 J7) voxl2:/$ i2cdetect -r -y 4 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- 68 -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- (able to ping an i2c IMU board connected to /dev/i2c-4). Please let me know if you have any additional questions. Alex

@alan123 , yes, the 12-pin connector on VOXL2 (J19) was designed such that the first 6 pins are compatible with a lot of existing GPS recevier modules. Please double check the pins and you should use a 12-pin connector to plug into VOXL2 (may need to re-pin your cable). Alex

@tom Thank you. I will submit an RMA request.

@clange Yes, definitely. All the support to build a Debian package for installation is in https://github.com/ArduPilot/ardupilot/tree/master/libraries/AP_HAL_QURT/packaging

@cbay , We support any camera that is compatible with UVC (plugged into a usb port). Please look into voxl-uvc-server. https://docs.modalai.com/voxl-uvc-server/ Regarding NIR, have you considered using a regular camera (most cameras are sensitive to NIR) and install a lens with a NIR pass filter (if you dont want to see visible light)? Then you could use one of our hi-res cameras like IMX412 or IMX664. I can get you spectral response plot of those sensors if you need. Alex

@Seungjae-Baek [image: 1763679737134-image.png] [image: 1763679737747-img_0429-resized.jpg] One more question: Should we use 5G antenna, not LTE? As I know when we buy the 5g modem the default antenna is the one with LTE.

@Cliff-Wong Thanks! I will try this as soon as possible and report how it works out.

@aspen The landing detector in PX4 isn't perfect (obviously) so in this case it didn't detect the landing. I would map one of the switches to toggle between arm and disarm so that when the drone lands you can disarm via switch. Did you try the v1.16 package?

@Peter-Milani , I see. this looks like a generic implementation of OpenCL for ARM from 3rd party (not Qualcomm), and i think it also overwrites the proprietary opencl libraries, disabling the GPU opencl support. However, you could make two separate docker images, one for each use case (cpu and gpu) Alex

@N-Chen To anyone reading this, maybe encountering the same issue in the future. I've tested the board with a guy that has a lot of experience with the voxl2 board, According to him, the board was faulty, probably some electrical issue, the amperage did not cross 0.1, and the board usually runs on something like 0.5. I've replaced my board as well as my power-supply cables (which were also under par).

Hi @dylangresham Stinger is intended to be a complete drone package for developers, integrators, and system providers who do not require additional customization. We believe it includes all the necessary functionality for the FPV use case. Starling 2, Starling 2 Max, and the PX4 Developer Editions, on the other hand, are designed to be customizable platforms that developers and integrators can modify to suit their specific products and use cases. By design, these are not fully Blue List–certified turnkey drones, since any additions, removals, or changes made by the end developer would require recertification. That said, because most (if not all) of the subcomponents used in these platforms are already listed on the Blue UAS components list, the end-user certification process should be straightforward. ModalAI parts will pass screening easily thanks to their existing certifications. I hope that clarifies the rationale.

@Eric-Katzfey Thank you for reverting back. I am trying to proceed with the same approach. I am facing some errors while going with this approach , I am trying to debug them. Another approach :- I am also thinking to hardcode the joystick based turtle mode to the voxl_esc.cpp. The manual control values will be monitored and once the value of the assigned button is clicked, the turtle mode will be enabled. Do you think it is a good approach?

You will need the SKU supporting the TOF to accurately run current versions of voxl-mapper and VOA. Zach