Ask your questions right here!

• 

  VOXL ADB or Wi-Fi no longer communicating!?!
  • Chad Sweet  

  1
  0
  Votes
  1
  Posts
  139
  Views

  No one has replied

• 

  sysimg 4.0.0 voxl-camera-server crashing tracking
  • Steve Turner  

  4
  0
  Votes
  4
  Posts
  28
  Views

  

  These are usually hardware issues. Some possibilities crimped flex cable exposed copper on the flex cable loose or damaged connector
• B

  VOXL PWM AUX servo operate
  • bensusana  

  2
  0
  Votes
  2
  Posts
  14
  Views

  

  I don't think we have used a Flight Core PWM to control a servo at ModalAI Have you reviewed the PX4 docs? The Flight Core is a pretty standard PX4 flight controller, like a pixhawk https://docs.px4.io/main/en/peripherals/pwm_escs_and_servo.html#pwm-servos-and-escs-motor-controllers
• 

  HITL with VOXL 2 Serial Port Closed
  • Taylor Presley  

  7
  0
  Votes
  7
  Posts
  45
  Views

  

  Hm thats super strange but I am glad you got it working! Keep us posted on how the project turns out
• 

  I accidentaly created a new file in my s500 drone drone
  • José Quintanilla  

  3
  0
  Votes
  3
  Posts
  12
  Views

  

  It worked, thank you
• R

  Flashlight attachment on VOXL/VOXL2
  • rohitpillai  

  3
  2
  Votes
  3
  Posts
  31
  Views

  

  It was a custom PCB that we do not have available as a product
• 

  VOXL is rebooting PX4
  • m4v3r  

  3
  0
  Votes
  3
  Posts
  14
  Views

  

  @tom Hi. This is on a VOXL Flight (VOXL 1 plus Flight core) and usually only happens when I'm on the PX4 main branch (I really don't think it ever happened on a stable version). From what I gathered it results from a "Yaw estimate error". For now I'm disabling the service via SSH, connect to PX4 over USB and use a long cable for calibration. After both my mags are calibrated in this way I can actually repeat this calibration over wifi (because they're not reporting deviating values anymore it seems). best regards
• 

  VOXL2 calibrate ESCs
  • Daniel Ryu  

  8
  0
  Votes
  8
  Posts
  64
  Views

  

  In the calibration.md file, you will find the following statement: set voltage to nominal battery voltage (7.5V for 2S, 11.3V for 3S, 15V for 4S) make sure the power supply can handle the maximum motor current. If not, you will see the voltage drop towards the end of the test (power supply limiting) and the calibration will be invalid You should be able to determine the maximum motor current based on the motor specifications provided by the manufacturer. For 4S, you would set the power supply to about 15V (would need 16.8V if you wanted to see absolute maximum RPM achievable with a 4S battery) Using a power supply is a suggestion, but you could just use a battery as well. You can monitor the current drawn by the ESC (the calibration script should print it on screen) and abort the test if you see or hear anything unusual. Alex
• 

  Safety Setup parameters missing from firmware
  • Dylan Lau  

  7
  0
  Votes
  7
  Posts
  45
  Views

  

  @Dylan-Lau said in Safety Setup parameters missing from firmware: @Adrian-Hidalgo Here is the px4 parameter file: link text Hi @Adrian-Hidalgo, may I know if there is an update? We thought of some workarounds but since it deals with safety, it is better to implement something with the support team's expertise. We found https://gitlab.com/voxl-public/flight-core-px4/px4-parameters/-/blob/master/platforms/master/temp1.params and https://gitlab.com/voxl-public/flight-core-px4/px4-parameters/-/tree/master/platforms/v1.13/M500 and so should we use this instead of the default one we have from the system image? Cheers Dylan
• 

  VOXL2 camera cal looks wierd
  • Patrick Hinchey  

  13
  0
  Votes
  13
  Posts
  16
  Views

  

  yessss 6x9 and a white background both improved detection rate, not just latency. Thanks for your help!
• 

  Garbage attitude control
  • Patrick Hinchey  

  26
  0
  Votes
  26
  Posts
  241
  Views

  

  OK thanks for the info, we are still looking at the main issue at hand in this thread still.... it's slow progress right now, but we will update here when I have positive movement to share.
• M

  Hires images are not showing correctly when using 3000 x 4000 resolution
  • mark  

  4
  0
  Votes
  4
  Posts
  31
  Views

  

  It looks like configuration 28 is what you're looking for with the standard 3840x2160. That's the resolution I've tested the 214/377 sensors with.
• S

  Building a custom docker image with VOXL libs
  • ShauliXtend  

  7
  0
  Votes
  7
  Posts
  33
  Views

  

  @ShauliXtend said in Building a custom docker image with VOXL libs: on the VOXL itself you use 32bit libraries while the system is 64bit Yes, unfortunately the QVIO algorithm is proprietary to qualcomm, we don't even have the source, just the 32 bit binaries that they've provided. maybe there is a way to still use the 32bit file You'll need to compile a 32-bit program to use a 32-bit library, there's unfortunately no way around this without some sort of inter-process communication (hence our standalone qvio-server)
• 

  I'm not able to change frame-rate on tracking and stereo cameras...
  • Ed Sutter  

  5
  0
  Votes
  5
  Posts
  27
  Views

  

  @Alex-Gardner So I guess I can't really do much to debug this (without knowing more about the proprietary implementation), true? Point being... if there is documentation you can share, I'll gladly dig into this.
• C

  Non standard camera configuration on VOXL running 4.0.0-0.9.4
  • czarsimon  

  6
  0
  Votes
  6
  Posts
  40
  Views

  C

  Thanks for the hint @Alex-Gardner, I tried two separate modules on 3.3.0, 3.6.0, and 3.8.0 and they worked just fine, it is only with system image 4.0.0 and voxl-sdk 0.9 that neither one works which makes me conclude that it's not the sensor but something with the software. Also both modules works just fine when run by themselves, it is only in conjunction with other sensors like stereo/tof that the hires is causing issues.
• 

  Erroneous data in VOA distance bin/linescan
  • Kavin Kailash  

  3
  0
  Votes
  3
  Posts
  29
  Views

  

  @Chad-Sweet Thanks for your response. I apologise for the late response. As you correctly pointed out, we resolved the issue after a re-calibration of the front stereo pair in natural lighting and by further tuning the 'blur_size' and 'post_median_size' parameters in the DFS server config file. Now the data reflects actual physical obstacles quite reliably.
• 

  VOXL2 has two network interfaces for microhard modem
  • Daniel Ryu  

  7
  0
  Votes
  7
  Posts
  41
  Views

  

  General QOL update: I automated a script using cron to ifconfig usb0 down and change the eth0 ip address to what I wanted using ifconfig eth0 <ip>. This only works if the script is run using sudo
• 

  Serial port for HITL and building gazebo target
  • Youngjoo Kim  

  6
  0
  Votes
  6
  Posts
  24
  Views

  

  @Youngjoo-Kim J18 is the port normally used for the UART based ESC. It is connected to the DSP, not the Linux processor. You cannot directly access it from Linux. Why do you need to run Mavlink over a serial port? We support and recommend using UDP.
• 

  VOXL2 - Tracking Sensor M0014 and cameras data capturing
  • Alon Michaeli  

  2
  0
  Votes
  2
  Posts
  12
  Views

  

  You should be using docs.modalai.com , the beta-docs are only published for specific, pre-release components. You cannot plug image sensors in where ever you like. You need to follow a supported configuration here: https://docs.modalai.com/voxl2-camera-configs/
• D

  Could we enable VOXL 2 to support HiRes Camera OV64B by install driver without system image re-generated?
  • DanChang  

  5
  0
  Votes
  5
  Posts
  38
  Views

  D

  Hi Chad, Thanks. One more question: Once new features are necessary during development or feasibility check, how to get ModalAI direct support? by contract or only through ModalAI forum? Best Regards, Dan