@AndriiHlyvko, I just ran into the same issue while testing Boson (in my case I was testing the 16-bit Boson streaming mode). The libuvc issue caused a crash, since i did not use a fixed version of libuvc. However, what actually caused the buffer overflow was the fact that Boson was reporting smaller buffer requirements for RAW16 during query (it was reporting width * height * 1.5 , just like for YUV, but actual frame size was width * height * 2, so uvc pipeline allocated smaller buffer and overflow happened with the full frame came in. Was this the same issue with your Boson tests or did you experience something else? Thanks! Alex

Hi @tom , here is my /etc/modalai/voxl-px4.conf: #!/bin/bash # # voxl-px4 Configuration File # # GPS: # Tell PX4 which GPS to use. If there is no GPS unit use NONE. Otherwise # choose AUTODETECT and the startup script will attempt to automatically # configure the GPS, magnetometer, and status LED # Options include: [NONE, AUTODETECT] # # RC: # Tell PX4 which RC transmitter to use. # Use EXTERNAL when getting RC control from external Mavlink messages (e.g Via QGC) # Options include: [SPEKTRUM, CRSF_MAV, CRSF_RAW, M0065_SBUS, EXTERNAL, FAKE_RC_INPUT] # # ESC: # Tell PX4 which type of ESC to use. # Options include: [VOXL_ESC, VOXL2_IO_PWM_ESC] # # POWER_MANAGER: # Tell PX4 which power manager to use. # Use NONE for ModalAI Mini-ESC since the ESC driver handles PM. # Use EXTERNAL when not using the ModalAI APM power manager to power the board # This also just disables the voxlpm driver, same as the NONE option # Options include: [VOXLPM, EXTERNAL, NONE] # # DISTANCE_SENSOR: # Tell PX4 which distance sensor peripheral to use. # Note: The sensor will be started on the RC port so it is only # really possible to use it when using external RC. # Options include: [NONE, LIGHTWARE_SF000] # # OSD: # Tell PX4 whether to enable OSD (on-screen display). # Options include: [ENABLE, DISABLE] # # DAEMON_MODE: # Tell PX4 whether to enable daemon mode. # Options include: [ENABLE, DISABLE] # # SENSOR_CAL: # Tell PX4 where to source sensor calibration information. # Options include: [ACTUAL, FAKE] # # ARTIFACT_MODE: # Do not allow artifacts to be saved to disk. Will not start the logging # module, will delete any current log files, and will delete the data manager file. # Options include: [ENABLE, DISABLE] # # EXTRA_STEPS: # Optional field that allows a user to define custom commands to be run by PX4 on boot. # Must be a valid bash array as seen below # Example: EXTRA_STEPS=( "qshell gps start" "qshell commander mode manual" ) # # GPS=AUTODETECT RC=GHST ESC=VOXL_ESC POWER_MANAGER=VOXLPM DISTANCE_SENSOR=NONE OSD=DISABLE DAEMON_MODE=ENABLE SENSOR_CAL=ACTUAL ARTIFACT_MODE=DISABLE EXTRA_STEPS=()

@Jainik-Mehta , Due to the high resolution of the hires camera (4056x3040), the voxl-portal has a hard time encoding these images to jpegs (using a software jpeg encoder turbojpeg), so that they can be sent out to your browser. This is expected behavior. In order to avoid this, please choose a lower resolution stream, something closer to 1280x720, or what you already have as an option 1024x768 hires_small_color (instead of hires_large_color). Voxl-portal is a tool that should be used for debugging / testing and is not optimized for efficient video transmission. For most efficient video transmission, you should use the encoded stream and you could make it available via rtsp protocol using voxl-streamer tool. Then camera server will use hw video encoder to generate the video, send it to voxl-streamer and the streamer can forward the video to you rtsp player (vlc, ffmpeg, mplayer, etc, etc) If you need more guidance, please let us know what you are trying to achieve. Alex

@nuallaino , we are continuing to investigate the GPS signal issues and found that sometimes the wifi module (Alpha networks), located right under the GPS receiver, can create interference with the GPS unit. Please try a workaround by disconnecting the wifi dongle from the M0141 usb adapter board and use a usb extension cable to move the wifi dongle from under the gps receiver. You don't have to mount the cable to the drone just for this test. Also, you can do a quick test by disabling USB power (which will turn off the wifi dongle) using the following command on VOXL2. You will need an ADB connection to check the GPS status if wifi is disabled. pin GPIO_157 controls VBUS, which is USB power on VOXL2 to disable, run voxl-gpio write 157 0 to enable, run voxl-gpio write 157 1 Please let us know if these tests show positive results. Alex

@Kessie D0012 is Starling 2 Max, voxl-esc setup_D0012 will load the correct firmware for your board as well as the correct params for your drone

Thank you for your help guys. I eventually reflashed the VOXL2 and it is working fine!

@Paul-Carff I believe the way to add channels is via the controller itself - the receiver on the VOXL2 should not require any update in config to take in more channels - from this point its configuring the controller to allow it to use more channels Zach

@jefersonsilva If you let it sit for a long time does it eventually find satellites and get a fix?

@tom Sounds good. Thanks for making me familiar with your platform. I will get a quote soon and purchase one starling 2 max.

edit: use mavutil.mavlink.MAVLINK_MSG_ID_LOCAL_POSITION_NED* instead of magic number 32 for message ID

@admin @Moderator Any suggestions on how to prevent this altitude divergence? This happens somewhat regularly and requires reversion to manual control.

@soraminds , VOXL2 supports SoftAP mode (access point), so you can set up your drone(s) to be access points and that should allow your ground sensors to connect to the drone. See https://docs.modalai.com/sentinel-user-guide-connect-network/ , specifically see usage for voxl-wifi: voxl-wifi softap Usage -- voxl-wifi Description: Configure the Wi-Fi mode. Usage: voxl-wifi getmode Print the current Wi-Fi mode (softap or station) voxl-wifi softap <ssid> [password] Set Wi-Fi to 2.4ghz access point mode (ch6). Default password is '1234567890' voxl-wifi softap5 <ssid> [password] Set Wi-Fi to 5ghz access point mode (ch149). Default password is '1234567890' voxl-wifi station <ssid> [password] Set Wi-Fi to station mode and connect to the access point with the given SSID and password (if provided). voxl-wifi factory Set Wi-Fi configuration to factory defaults. This will set the Wi-Fi to 5ghz access point mode, with SSID 'VOXL-[MAC address]' and password '1234567890'.

@Eric-Katzfey Worked! Thanks a lot

@Jeremy-Schmidt Hi, It's resolved now, in the mean time I had a response from the support. Have a good day Julien