Hi @irw Can you please post High Res and clear photos of both sides of the VOXL 2?

@Myles-Levine , the VOXL2 SoC is not designed to run at full power for a long time without cooling. The maximum operating temperature is around 95 deg C, at which point, the CPU will being automatically throttling (reducing) operating frequency. It is common to rely on air flow from propellers when the drone is flying, however some implementations may have a small fan as well. Since you mentioned bench testing, installing a small fan next to VOXL2 to get airflow over the board should help. No specific recommendations, you can start with a standard 12V fan used in PC power supplies. It can be relatively easy to overheat VOXL2 without cooling, because it has quite a powerful processor and the heat is concentrated in such a small package. You can spend more time optimizing the code (if possible) or add passive and / or active cooling. Alex

@Michael-Soul , it is EAR99

Hello @adam , please see the following post regarding GPS signal quality on Starling 2 and Starling 2 Max : https://forum.modalai.com/topic/5116/gnss-emi-mitigation-guidelines There is no voxl-gps service - voxl-px4 handles the GPS functionality, so as long as that is running, the GPS module should be active. Please go through the documentation linked above, there are some mitigation steps that are relatively easy to implement. We apologize for the inconvenience, but enabling usable GPS on Starling 2 will require some tweaks. Alex

@Nikos-Mavr I have an extra ac1300 to use that lsusb recognizes but I don't think the driver is implemented. Ac600 Antenna might be malfunctioning after all because even if it lights up on other pcs and identifies WiFis it cannot connect. Is there a way to implement a driver for ac1300?

@MikeR Does your commando 8 have an orq ghost transmitter module connected to it? If it doesn't then it is likely using ELRS which is not compatible with a ghost receiver. You'd need a orqa transmitter like this one: https://shop.orqafpv.com/products/orqa-orqa-fpv-ctrl-radio-controller Maybe your other drone had an ELRS receiver on it?

@Nikos-Mavr You're welcome! And can you please start a new forum post for this new issue? Thanks!

@Piyush-Singh , can you please provide more details how exactly all cameras are connected to VOXL2 mini (including interposers, flexes), etc. A diagram would help a lot which kernel variant are you running on your voxl2 mini (2.0.0 or 2.0.2). Are all the other cameras working if you disable the TOF sensor in the camera server config? Alex

@Shantanu-Gupta please check documentation and video for VOXL2: https://docs.modalai.com/voxl2-voxl2-mini-system-image/#force-voxl-2-into-fastboot https://docs.modalai.com/voxl2-connectors/#buttons https://www.youtube.com/watch?v=IM3PnW7cipQ Alex

we just posted an update on this topic, please see https://forum.modalai.com/topic/5116/gnss-emi-mitigation-guidelines

@shawn_ricardo A couple of quick points. First of all, PX4 just queries the Linux system time so there's no mechanism to set a separate notion of system time in PX4. If the VOXL 2 is connected to the internet then, yes, it will update the Linux system time with NTP. But VOXL 2 has no battery backed RTC so if it cannot get system time from NTP then it uses the last saved time which is typically the last time there was a connection to an NTP server. Also, in newer versions of our PX4 we get rid of the -t option when starting the logger module so it will not use the system time. Instead it will just create session directories and log files within them in increasing numerical order. So, highest numbered log file in highest numbered session directory is the latest log.

@ndwe Whether you use a VOXL or Jetson as a companion computer shouldn't make any difference unless you want to use the VOXL SDK. The version you run is totally up to you. If our v1.14.0 based version works for you then use it. We do plan to transition to v1.17.x in the near future. I don't think the issues you are seeing are related to something specific in the flight core v2 hardware setup. I would think that if you swapped it out for some other brand you would see the same issue. I would ask on the PX4 forums to see if others have experienced the same issues.

Hi @jon , do you always see the following warning right before the seg fault? (and never see it when there is no seg fault?) @jon said in voxl-logger seg fault on shutdown: WARNING, _stop_helper_and_remove_pipe timed out joining read thread The way one would normally debug this is using gdb, but that would be tricky if you are spawning the logger from another (python) process and don't have a terminal to type in gdb (after crash) to investigate.. You could potentially attach gdb to an already running (spawned) logger. Alex

@Alex-Kushleyev said in Configuration for VOXL 4in1 mini 6S ESC and Newbee Drone Flow 2808 1300KV motors: ESC M0138 FPV ESC : Thank you very much for your reply Alex. I appreciate the references and support documentation you provided as well.

@Alex-Kushleyev Thanks Alex, very helpful!

@Myles-Levine , if you are masking out 90% of down-facing camera, then it is probably useless any movement of the features will get it out of the unmasked region very easily and feature will be dropped.. It may hurt VIO as there may be features going in and out, only trackable for a few frames (just adds to the complexity). You should try to move the down-facing camera to free up it's FOV or even have it facing slightly angled to the back of the drone.. Alex

Hello @Catalystmachine , Sorry for the confusion. We have updated the page to be more clear that Boson is not included, see below: "(No Boson)" was added to the kit description. The title of the product already states "VOXL 2 MIPI Boson+ Adapters for Thermal IR FPV" as well as the Kit description used to say (Before we added (No Boson)) : "PCB Adapters Only..." The price of the Boson cameras varies significantly, depending on the specifications. You can contact a distributor to get more details. For example : https://www.oemcameras.com/product-category/thermal-imaging-cameras/thermal-imaging-cores/flir-boson-series-htm/boson-plus/ (you can find more at https://oem.flir.com/contact/find-a-dealer/) Please note that Boson+ series of the Boson sensor is required for compatibility with VOXL2. Regarding the pricing of the adapter kit, we do offer discounts in higher volumes, if you are interested, please send us a request: https://www.modalai.com/pages/contact-us [image: 1773106957515-ebff1907-0495-4a65-8f27-2138562022d3-image.png]

Hey @voxltester It seems there is an issue with how MicroXRCE and the microhard modem interfaces are starting up, I had to edit the service files to get the topics on the VOXL2. Edit /etc/systemd/system/voxl-microdds-agent.service: [Unit] Description=voxl-microdds-agent SourcePath=/usr/bin/MicroXRCEAgent After=network.target After=multi-user.target [Service] User=root Type=simple ExecStart=/usr/bin/MicroXRCEAgent udp4 -p 8888 [Install] WantedBy=multi-user.target Edit /etc/systemd/system/voxl-modem.service: [Unit] Description=Modem Initialization After=sdsprpcd.service [Service] User=root Type=oneshot ExecStartPre=/bin/sleep 2 ExecStart=/usr/bin/voxl-modem-start RemainAfterExit=yes [Install] WantedBy=multi-user.target Add export ROS_DOMAIN_ID=0 to your .bashrc Reboot the VOXL2, and the topics should come up Thanks