Posts made by Eric Katzfey

@Jetson-Nano Which build, specifically, are you looking for? Something from the ModalAI fork of PX4 or from mainline? Are you not able to build firmware yourself?

@voxltester The primary and secondary ip / port configurations are for destinations. voxl-mavlink-server will initiate connections to those. For incoming connections just send to port 14550. voxl-mavlink-server is listening on that port. When an incoming message from a new ip / port combo comes in it will store that and consider that a new connection. If you use drone.connect it is waiting for voxl-mavlink-server to connect to it rather than attempting to connect to voxl-mavlink-server on it's own.

@Jetson-Nano Can you open the question about UAVCAN in a separate post? It has nothing to do with the initial question and we like each separate issue to have it's own posting / title. Thanks!

@Mustafa_Cayci You can run PX4 directly on VOXL2. Do you still need the external Pixhawk? When you say USB-C is that the connector that is already on VOXL3 for adb?

@PatkirkMartin No, as I said a UART mapped to the applications processor would also work. PX4 has a split architecture on VOXL2 with all flight critical operations happening on the DSP and support functions such as Mavlink, logging, and data manager are on the applications processor. But there is flexibility to move functions between them as needed. So, to match the ELRS receiver with the Mavlink module you could run it on the applications processor instead of the DSP. However, you would need an expansion board that exposes such a connector.

@PatkirkMartin The ELRS is connected to a DSP UART via J19, correct? That is the link that you want to send Mavlink data on?

@Mustafa_Cayci You would need an accessory board that exposes a USB port for you to connect. Yes, VOXL2 has Ubuntu / Docker capability.

@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?