@Eric-Katzfey So you probably just need to do the magnetometer calibration procedure to be ready for flight.
Posts made by Eric Katzfey
-
RE: Calibration for VOXL SDK 1.1.3
-
RE: Calibration for VOXL SDK 1.1.3
@Phi-Nguyen The magnetometer rotation is specified directly with the magnetometer driver so you don't need to set it with that parameter. The
/usr/bin/voxl-px4-start
startup script will attempt to launch the magnetometer driver with the-R 10
option to specify the rotation. -
RE: Operational range of the VOXL 2 mini
@Bilal-Hussain No, there is no integrated radio / modem on either VOXL 2 or VOXL 2 mini. It has to be add on boards.
-
RE: Operational range of the VOXL 2 mini
@Bilal-Hussain Are you asking how far away you can be from a 5G base station and still have enough bandwidth to transmit video? That's not an easy question to answer. Certainly part of it depends on the base station itself. Things like base station antenna design, things like how many other users are using that base station, obstructions in the way between the drone and the base station, etc. etc. It also depends on the video feed itself. Best to choose a video stream with low bandwidth requirements and tolerance to packet loss. Of course the drone transmit chain including PA design, antenna type and placement also play a role. But the VOXL 2 mini has no 5G modem on it's own. A 5G radio is an accessory. I'm curious what the context of the question is. Are you planning to use 5G but know that you will be far away from the nearest base station? What about 4G or 3G in that case? Or maybe don't use cellular at all. There are other options.
-
RE: QGC keeps crashing when sentinel drone is reconnected
@Dawid-Mościcki Perhaps you can ask the QGC development team for some help in narrowing down what is causing QGC to crash. If you think there is a missing parameter then in your
/usr/bin/voxl-px4-start
script add a new line totouch
the parameter so that QGC will see it. (e.g.param touch SDLOG_MODE
) -
RE: ODOMETRY MESSAGE
@leonardo-Andrade-0 The startup script
/usr/bin/voxl-px4-start
controls the startup of the mavlink instances. The mavlink instance that sends messages to QGC enablesnormal
mode which does not include the odometry message. But you can see in that script how you can add extra streams. So, you can add odometry with something like this:mavlink start -x -u 14558 -o 14559 -r 100000 -n lo mavlink stream -u 14558 -s ODOMETRY -r 30
-
RE: VOXL ESC with Cube running PX4
@Chase-Riley Yes, as Alex said, most standard builds do not include the voxl_esc driver. Only the ModalAI products include it as a standard part of the build. So you will need to add that to you build configuration.
-
RE: VOXL ESC with Cube running PX4
@Chase-Riley We load and test our forked version of PX4 on our flight core products but the mainline PX4 should work with our ESC. Having said that it's not something we have been testing. We are planning to move away from our fork to mainline PX4 in the near future for all of our products.
-
RE: VOXL 2 issue connecting with RC
@Alexander-Saunders said in VOXL 2 issue connecting with RC:
Spektrum AR6210
We use the SPM9745 receiver and have never tried the model that you are trying. Others have had issues with various Spektrum transmitters. Here is a link to a different forum post about that: https://forum.modalai.com/topic/2703/voxl2-spektrum-receiver-error. The transmitter we use is https://www.horizonhobby.com/product/dx6e-6-channel-dsmx-transmitter-only/SPMR6655.html. The connection with RC and with QGC are two completely separate things. Are you also not able to connect to QGC?
-
RE: voxl-px4 not logging in VIO only flight modes
@Aaky Logs are started when the vehicle arms and stopped when the vehicle disarms in the default configuration. In the configuration where you are not seeing logs generated can you delete everything in /data/px4/log then arm the drone, wait a couple of seconds, and then disarm and verify that there is nothing written in that directory? If there is nothing can you arm the drone, ssh into the drone, enter the command
px4-logger on
, wait a few seconds, then issue the commandpx4-logger off
, then disarm the drone. Do you get anything then? The output fromjournalctl -b -u voxl-px4
will be helpful in debugging what is going on. -
RE: Record video with from two OV9782 cameras in stereo
@restore The way to view multiple cameras on QGC is to use multiple instances of voxl-streamer, each streaming one camera to a dedicated port. Then use voxl-mavcam-manager to advertise each of those cameras using the Mavlink camera protocol. Then, in QGC you can choose which camera you want to see and start recording, take snapshots, etc. But voxl-mavcam-manager is still under development so not the easiest to work with right now.
-
RE: Connecting i2c device on voxl2
@Aaky The Microhard board does not expose an apps processor UART but you could use a USB to UART adapter to connect to the Gimbal via one of the USB ports.
-
RE: Connecting i2c device on voxl2
@Aaky Yes, you could use the UART exposed on that M0125 expansion board.
-
RE: Connecting i2c device on voxl2
@Aaky That is not a standard configuration that we test with so likely will not work out of the box. But it shouldn't be too hard to adapt voxl-mavlink-server to your use case. And if you make changes that you think would benefit other users we would gladly accept a Pull Request with the updates.
-
RE: voxl-px4 service pipeline uORB failure
@jacob-yaacubov You should definitely upgrade to SDK 1.1.3.
-
RE: Connecting i2c device on voxl2
@Aaky Correct. VOXL2 uses UDP for it's Mavlink telemetry, not UART TELEM ports like on a microcontroller based autopilot. But, voxl-mavlink-server should be able to route Mavlink messages over an apps processor based UART such that it would be similar to a TELEM port. Which add-on board is it? Is it something custom or one of our boards?
-
RE: SPI port for VOXL2 SLPI DSP
@Aaky Unfortunately, we have not done any integration between PX4 and SPI devices on the apps processor. I would get an oscilloscope and see what is happening on the bus.