Skip to content
  • OpenVINS

    GPS-denied Navigation (VIO)
    2
    1
    0 Votes
    2 Posts
    14 Views
    zauberflote1Z
    Please update your VINS to our master branch here: https://gitlab.com/voxl-public/voxl-sdk/services/voxl-open-vins-server
  • Using VOXL IO Expander with VOXL 2 Mini?

    Ask your questions right here!
    2
    0 Votes
    2 Posts
    20 Views
    Eric KatzfeyE
    Yes, you can connect to one of the UARTs on J19. However, there are only 3 UARTs so you'll have to choose which one to use. The PWM outputs on the IO expander are mainly intended to be used when you have PWM ESCs instead of a ModalAI UART based ESC. In that case you would connect to the ESC UART. If you want to use the IO expander in addition to a ModalAI UART based ESC then you will have to choose between the RC UART or the GNSS UART.
  • Re-configure VOXL2 1.4 for GHOST Receiver/Transmitter?

    Sentinel
    2
    0 Votes
    2 Posts
    40 Views
    Eric KatzfeyE
    First of all I would update the SDK to something newer. That's probably not going to solve this issue but it makes it easier for us to support you when you are on the current SDK. To help troubleshoot can you show the output of px4-qshell ghst_rc status. Run that status command a few times.
  • 0 Votes
    1 Posts
    9 Views
    No one has replied
  • 0 Votes
    1 Posts
    8 Views
    No one has replied
  • QDL - 'received non-successful result'

    Sentinel
    2
    0 Votes
    2 Posts
    463 Views
    P
    RMA'd the VOXL2 board, it was found to be unrepairable.
  • 0 Votes
    2 Posts
    78 Views
    D
    Hi @masa-chau, It seems you are on the right track. A few pointers from my side: First, what are you actually trying to achieve? If you can avoid tracking in 3D and perform the task in 2D, I would strongly recommend doing that. Recovering 3D position from 2D observations is quite hard and can be very finicky/unreliable. For many tracking tasks, you can get away with tracking entirely in image space. If you really need to track in 3D: Use the PX4 estimator output. VIO is fused into EKF2 in PX4, so I would probably use the PX4 estimated poses/velocities as the state of the drone rather than trying to fuse the raw VIO yourself. I believe these should be available in ROS 2 through voxl-microdds-agent, although someone from ModalAI should confirm the exact topics/data being exposed. Your 2D observations from the object detector are fine, but pay close attention to latency. Also, I would not expect reliable detection at very long distances with the Starling 2 Max fisheye camera; in practice, the useful detection range may be significantly below what you might initially expect. I would not rely on the ToF camera for this. For the actual tracking algorithm, I would look at an EKF or MAP estimator that fuses the 2D observations (e.g. bearing and potentially bounding-box size) with the drone's 3D pose/velocity. The important point is that a single 2D observation does not give you reliable depth. To estimate the object's distance over time, you need additional constraints, typically through a motion model or assumptions about how the tracked object moves. Whether the object is flying or driving, you will probably need to make some approximation about its motion. I would look into the existing literature on monocular 3D object tracking / bearing-only tracking for this part. Good luck!
  • voxl-mavcam-manager in differnt versions

    VOXL SDK
    5
    0 Votes
    5 Posts
    306 Views
    A
    Hi,Apoorv Thapliyal, Thanks for the suggestions made. We have tried 1.4.5 SDK on Voxl2 board and we are able to get snapshot in both QGC and also in /data/snapshots folder in the board .If we try to change resolution of snapshot in voxl-camera-server ,it is applied to resolution of snapshot saved in /data/snapshot folder in voxl2 board.
  • Bots Unlimited Wifi Crash

    Ask your questions right here!
    7
    0 Votes
    7 Posts
    279 Views
    L
    Hi John, Thanks for the data dumps. Could you run this wifi_capture.sh on your board and send us the data when you reproduce the crash along with the dump file again? It should be here along with a simple readme https://drive.google.com/drive/folders/14nMhkvOMeHJ6zLJYMW4scAglTfkRYY8N?usp=sharing Could you also briefly describe how you are connecting/what devices you are connecting? Also does this happen under any specific workloads or is it sporadic? It seems like a firmware crash so any additional information would be very useful if we end up needing to report it. Thanks! Luke
  • 0 Votes
    1 Posts
    31 Views
    No one has replied
  • 0 Votes
    9 Posts
    323 Views
    VinnyV
    Hi @jetson-nano I'm not sure I am following. The ADB Debug port is still available on VOXL 2 when you use an M0062 Debug Board with USB Hub. Our plug-in boards that connect to J3 and J5 do not consume the primary USB. See here for guidance: https://docs.modalai.com/expansion-design-guide/#usb-expansion-over-j3--j5
  • 0 Votes
    3 Posts
    100 Views
    M
    ok thanks, I have emailed, please let me know if you have not received it
  • 7-port USB 2.0 hub design review

    PCB Design Reviews
    1
    0 Votes
    1 Posts
    50 Views
    No one has replied
  • 0 Votes
    1 Posts
    40 Views
    No one has replied
  • VOXL ESC FPV 4-in-1 with Built-in Power Module (MDK-M0138) Issues

    ESCs
    12
    0 Votes
    12 Posts
    331 Views
    Alex KushleyevA
    Hi @jbiscan21 , The main issue was that the max_rpm_delta was set to zero. Even with PI gains (and max errors) set to zero, you could have had it working with non-zero max_rpm_delta. Let me explain. max_rpm_delta term is used to cap the target rpm relative to the current rpm. This is done to prevent very aggressive motor behavior, especially if motor is spinning very slowly because it is tangled in grass, etc, allowing unlimited max_rpm_delta could cause motor to burn out or de-sync. The RPM controller has a feed-forward term and feedback terms. feedback terms are Proportional and Integral with corresponding gains and error terms (k * e). feed-forward term comes from the calibration : for desired RPM, the calibration tells the ESC what PWM (duty cycle) to apply there is also battery voltage compensation, so that even if voltage is changing, the feed-forward curve will still be accurate. The rpm error is computed like so : rpm_error = rpm_desired - rpm_current, which standard. But then it is capped with the max_rpm_delta, so if that is equal to zero, then rpm_error will be zero. One subtle detail is that the rpm_error is also used to look up the desired rpm feed_forward : rpm_for_feed_forward_term = rpm_current + rpm_error (roughly speaking), so having the max_rpm_delta set to zero, caused the motor to be always stuck at minimum rpm. So you could still have zero P and I terms and the motor would use a feed forward term with voltage compensation and it would provide a nice and soft response (similar to traditional ESC). Adding P and I will make the response better than a traditional ESC. In fact when using a new motor + prop, you should start off with P and I gains zero, just use a feed forward term to test at first and then you can increase the ESC's responsiveness by giving it more max_rpm_delta and also P and I terms. However, that is more advanced tuning should be done using voxl-esc tools first in order ensure ESC response stability (we could discuss that in another thread). To answer your earlier questions: You could use pwm (power) control, but i have never used it with PX4. Perhaps @eric-katzfey can comment about that the ESC calibration for modalai ESCs calibrates the feed-forward term (as described above), and has to be done with a propeller. Yes, in flight, the air dynamics will change due to many factors such as air pressure, temperature, air speed, etc, etc, but the job of RPM controller is to keep a desired rpm. A higher level controller could potentially estimate the thrust vs rpm is changing due to air temperature or pressure difference from the calibrated response (outside of the scope of ESC's rpm controller). Alex
  • 0 Votes
    8 Posts
    275 Views
    Alex KushleyevA
    @dan-jennings , I would be happy to help you with the Hadron Issues on newer SDKs. There were no changes to the Hadron (Boson + OV64B) functionaliy recently. Please make a new post for this issue and provide the following details: which SDK is working and which SDK(s) are not working for Hadron detailed description of the issue, any useful info from camera server or dmesg? how is Hadron connected to VOXL2? which interposers and which VOXL2 camera port (J6, J7, or J8) please provide voxl-camera-server.conf that you are using please provide a list of sensormodule.bin and *so files in /usr/lib/camera Thank you Alex
  • 0 Votes
    4 Posts
    99 Views
    Eric KatzfeyE
    Can you plug the cable from the working drone into the other one? That could tell you if it's the cable.
  • stinger + TOF

    Stinger Vision FPV
    1
    0 Votes
    1 Posts
    68 Views
    No one has replied
  • 0 Votes
    1 Posts
    84 Views
    No one has replied
  • 0 Votes
    3 Posts
    140 Views
    Eric KatzfeyE
    Also, there are many good simulators out there.