@teddy-zaremba Temporary fix by just installing missing package:

apt-get install -y libwayland-server0:arm64 libwayland-dev:arm64

Also have to install this for voxl-portal

apt-get install -y libglib2.0-0:arm64

@Rowan-Dempster No problem! Kind of primitive but effective 🙂

@Jskim
Finally, I tried a test.
I tried changing the video player and the Streamer died immediately.
The conclusion is that the Streamer died even when it was in the foreground.
플레이어 변경하면 바로 죽음.jpg

Thanks,

JS, Kim

@KnightHawk06 That is the source, yes.

@James-Strawson

hmmm, by any chance are you failing to link against symbols from libgmb.so? That is a new library dependency of libmodal_pipe. Most of our packages use the following linker flags to avoid recursive linking, I think this would be a better solution than specifying the libmodal_pipe version in install_build_deps.sh

set(CMAKE_C_FLAGS "-Wl,--unresolved-symbols=ignore-in-shared-libs ${CMAKE_C_FLAGS}")
set(CMAKE_CXX_FLAGS "-Wl,--unresolved-symbols=ignore-in-shared-libs ${CMAKE_CXX_FLAGS}")

Hi again,

From investigating the voxl-vision-hub code with added prints for debug, I see that the setpoint SETPOINT_POSITION_MAGIC_NUMBER is sent to mavlink-server from two functions -

(1) _send_current_position()
sending the current position, and type-mask ignoring vx,vy,vz,ax,ay,az,yaw_rate

// fetch latest position and attitude from px4 itself so the setpoint // we are about to send is a close as possible to where we currently are

(2) execute_setpoint_position_command()
sending the setpoint as recieved from voxl-planner

The implemented behaviour of (1) suits the situation of position+yaw command. However for vx+vy+z+yaw_rate command I think something is missing.

Any help will be appreciated.
Thank you, Meytal

@taiwohazeez The build flow should be like this:

cd voxl-mpa-to-ros2 git checkout dev git submodule update --init --recursive voxl-docker -i qrb5165-emulator ./install_build_deps.sh qrb5165 dev ./build.sh qrb5165 dev ./make_package.sh deb

@Judoor-0
You can use QGroundControl v5 and later. Then once your drone coots and connected to the QGC, mouse click on the desirable position and select Set Estimator Origin option. This will be your [0,0,0] in local frame and [lat, lon, alt] in global
24ef863e-534d-4894-b99d-d1cacd609954-Untitled.jpg

@JackHammer no problem.

This should be the esc param file for the Starling 2 Max motor : https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-esc/-/blob/dev/voxl-esc-params/D0012_Starling_MAX/esc_params_m0129_f2203_5_1500kv_7x3.7x3.xml

The param file should also be present in /usr/share/modalai/voxl-esc-params

Do you know how to update the esc parameters?

systemctl stop voxl-px4 cd /usr/share/modalai/voxl-esc-tools ./voxl-esc-updload-params.py -p <full path to params file>

After updating the params, you can run a "power ramp test", as shown here : https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-esc/-/blob/dev/voxl-esc-tools/doc/low_kv_motor_tuning.md?ref_type=heads#power-ramp-test . Use id=255 to spin all motors (and you can limit power to 80%)

./voxl-esc-spin.py --id 255 --power 80 --ramp-time 3.0 --timeout 3.5 --enable-plot 1 --cmd-rate 250

Since you can't display the plot on voxl2, a plot will be saved as html, which you get download from voxl2 and view in a browser.

You can do it without propellers (for safety). If all the motors are working properly, the four rpms will be very close to the same as the power ramps (within 100-200 rpm). Otherwise, you may have a bad motor that was damaged during the crash.

https://www.modalai.com/products/starling-2-max-replacement-parts?variant=49704826896688

Alex

After some additional investigation I was able to resolve this by replacing the include:

#include <c_library_v2/common/mavlink.h>

with:

#include <c_library_v2/development/mavlink.h>

in actuator_test.cpp

Solved using SDK 1.4

@Ege-Yüceel Wow, this is a very ambitious plan! Keep in mind that VIO needs not only camera images but also IMU input. Camera images are normally supplied by the voxl-camera-server on MPA pipes. So, you would need to stop voxl-camera-server and start your own application that takes the images from Gazebo and places them into correctly named MPA pipes. The images would have to be formatted properly, etc. Likewise for IMU samples that normally come from voxl-imu-server. I think this will be quite difficult to get working properly but theoretically possible.

@tom Thank you so much. It is working now with your suggestion. I think the README file of voxl-tflite-server need to be updated.

Hello @itzikwds,

Sorry for the delay. We can extend pympa to support the ai_detection class.

Here is as example of an application that receives the detection data : https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-mpa-tools/-/blob/dev/tools/voxl-inspect-detections.c

However, since you need this in python, pympa would need to be extended to support the detection data.

Can you please confirm that you still need this functionality or did you find another solution?

Alex

@ashwin I'm not really understanding the issue. Mavlink has no limitation to send packets to a localhost address. On VOXL 2 we configure voxl-px4 to send to localhost but that is because voxl-mavlink-server is the application that actually sends the data to the GCS. At the GCS you will see each connection with a unique IP address.

@Eric-Katzfey Thanks for the reply. You’ve correctly identified my problem.
Due to time constraints, I need to deploy my system soon. I hope to have a solution that works on your hardware or to wait for the Ubuntu 20 update.

Choose Option 1 if you DO NOT have the camera board attached
d9a9defd-3783-452a-a735-7cb2c38d7065-image.png

Choose Option 2 if you are using the camera board
3a551368-4c35-4edd-8f0d-09b2f6cd47da-image.png