Posts made by Eric Katzfey

@nickanick Also, you can run voxl-mavlink-server with some of the debug options which will show you which packets are coming in and going out.

@nickanick What is the IP of the computer running QGC? Can you ping the VOXL2 from that computer? Can you see the Mavlink heartbeat packets on that computer with tcpdump or other protocol analyzer when you setup the QGC connection?

@Mustafa_Cayci Yes, you can run ROS2 and OpenCV on a VOXL2. Can you give more details about the RFID reader? What type of I/O does it use? What type of software interfaces with the reader?

@PatkirkMartin Mavlink over a DSP mapped UART won't work. However, if you have an accessory board with an apps processor UART available then you should be able to configure that to work with Mavlink.

@Hector-Gutierrez Well, I'm happy that worked, but you shouldn't have to disable voxl-vision-hub like that. I only suggested that as a debug step. We'll take a look and see if we can reproduce the error and come up with a better solution.

@Hector-Gutierrez What calibration step is not working? Are you running any custom software, like ROS or MAVSDK based applications? If you disable voxl-vision-hub does the error go away?

@bschulzhf PX4 will only correct incoming messages. Something external will have to also run TIMESYNC with PX4 to estimate the offset and correct and incoming PX4 message timestamps that it wants to align. voxl-mavlink-server does this for a few messages.

@nickanick That was what I responded with previously. Did that documentation not address your question?

@nickanick It's best if you ask each question in a separate post. For QGC over the ADB USB: https://docs.modalai.com/qgc-via-adb/

@jon You can use a J19 UART from the apps processor. Take a look at the code in voxl-elrs (https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-elrs/-/tree/dev?ref_type=heads), specifically the file src/elrs_slpi.c. This project accesses SLPI UARTs from an AP userspace process through voxl_io, not through POSIX termios. You cannot have a flight controller running at the same time though so PX4 / ArduPilot / etc. would need to be stopped first.

@jon When running that way make sure you wait a few seconds before restarting. If you ctrl-c out of voxl-px4 and immediately restart voxl-px4 you will see that error condition.

@Michael-Hatton Yes, you need to have a separate battery charger. I'll see if I can get a recommendation from the team on a good charger to use. I use a Hota D6 Pro, personally.

@jon You may want to update to the latest release. There have been some updates to voxl-reset-slpi. How do you normally restart voxl-px4? Are you running from the command line or as a service?

@bschulzhf Sort of. The timestamp from voxl-vision-hub and voxl-mavlink-server is just the Linux processor monotonic time. But because voxl-mavlink-server has been responding to the time sync protocol messages from PX4 it allows PX4 itself to update the timestamp to PX4 time when it comes in.

@wilkinsaf You can disable compass with SYS_HAS_MAG = 0 and EKF2_MAG_TYPE = 5. But if you enable it and it isn't healthy you won't be able to arm. Power compensation may work, it depends on your particular drone model and use case.

@jon That looks like the DSP portion of PX4 didn't exit completely / cleanly from the previous run. What version of the SDK are you running?

@JB1 Our voxl-remote-id software with WiFi dongle is intended only for reference and is not meant to be a commercially ready system for our customers who need a remote id solution for their VOXL2 based drone products. Integration, testing, validation, and FAA registration with desired hardware is up to the end user. At a minimum the manufacturer id would need to be changed from ModalAI's id to your companies issued manufacturer id.

@JB1 I'll look into your questions. There is no RTC on VOXL2.

@jon And you can find a lot of detailed information about the agent, including the start options, here: https://docs.px4.io/main/en/middleware/uxrce_dds

@Michael-Hatton When you arm the drone it is in flight mode and the motors start to spin. It's that spinning of the motors that you don't want while plugged into a power supply. Only use your battery to actually spin the motors and fly.