@teng Not with QVIO, but voxl-open-vins-server uses front/down VIO by default starting in SDK 1.4.0
Group Details
Private
Dev Team
Member List
-
RE: Running multiple qvio instancesposted in GPS-denied Navigation (VIO)
-
RE: How to enable Turtle Modeposted in Ask your questions right here!
@Jetson-Nano Instead of listening to the input_rc topic with the listener function you can now monitor the RC_CHANNELS Mavlink message from the FC v2.
-
RE: RC connection/MH carrier directly to VOXL2, while using Flight core V2posted in Microhard Modems
@Jetson-Nano Which connector would you use for this on VOXL 2? In order to send RC values to PX4 running on an external FC v2 you need to send the RC values in an RC_CHANNELS_OVERRIDE Mavlink message. (https://mavlink.io/en/messages/common.html#RC_CHANNELS_OVERRIDE) So, you would need a custom program on the VOXL 2 to read the input from the RC receiver, create the Mavlink message, and send it to the external FC over the UART.
-
RE: Motor Replacement Instructions Starling 2 Maxposted in Starling & Starling 2
@griffin Were you able to get your motors replaced? It sounds like you had ordered the proper spec replacement motors
-
RE: Creating image of current stateposted in Ask your questions right here!
@Kessie Not exactly, but the important data to retain lives in
/data/or/data/modalaiThe SDK flash will attempt to retain this partition, but in certain cases it requires a wipe.
I would take note of
/data/modalai/sku.txtas well as pull off any calibration files in
/data/modalai, you can see if you have any onboard currently by runningvoxl-check-calibrationIf you have this data saved you'll have no issue getting back to your previous state, I can help guide you through it if you run into any issues.
-
RE: Instruction to set a Static IP for wlan0 voxl2posted in Software Development
@Judoor-0 Thanks for the contribution, this is very helpful!
-
RE: Unbricking a VOXL 2 - Pass but no ADB?posted in Ask your questions right here!
@czarsimon When you run through the QDL process how long does it take for the flash to finish? seconds? minutes?
Also, are you able to ADB onto functional devices on this machine? Want to rule it weird permission issues
-
RE: Microhard module integration with VOXL2posted in VOXL Accessories
Hi @Jetson-Nano
No difference in data rate on any MH board. They are all USB2 rates.Hope that helped!
-
RE: Microhard module integration with VOXL2posted in VOXL Accessories
Hi @Jetson-Nano
Let me try to clarify to help:
The "-3" Plug in board variant https://www.modalai.com/collections/expansion-board/products/voxl-microhard-modem-usb-hub does this:- Power to MH Modem, USB Interface, USB Power to Downstream Peripherals, and interfaces all through the J3 interface to VOXL 2
However, the "-2" Standalone Module https://www.modalai.com/collections/modems/products/mdk-m0048-2
- brings only USB over the J7 4-pin USB Interface
. - There is not enough power over that VBUS to power the MH Module and downstream peripherals. That is where the red 2-pin JST J8 comes in...
That connector provides power to the MH radio AND power to Downstream USB devices.
So, if you originally had a -1 variant that you plugged into VOXL 2's J3, and you want to remove that interface, you will need to switch over to the -3 hardware variant product.
I think that was the info you were looking for and I hope I clarified that for you.
-
RE: Microhard module integration with VOXL2posted in VOXL Accessories
Hi @Jetson-Nano
If you do not use the J3 from VOXL 2 to power your Microhard that is the "-1" variant, you cannot power peripherals. You'll need to use the -2 variant with the red connector: https://www.modalai.com/collections/modems/products/mdk-m0048-2VBUS in to the MH is not used for powering downstream USB VBUS ports.
