Topics created by jacob yaacubov

Hi there, I would highly recommend upgrading to the latest SDK 1.6.2.

Q1: For voxl-vision-hub, openvins is just another [abstracted] VIO client, using the same MPA interface as QVIO. Thus, should work the same as QVIO.
Q2: There are no outstanding buffer conflicts between the 2 inputs in that SDK version. Though best to update to 1.6.2 as there have been numerous MPA improvements.

Q3: MAYBE ON GROUND, POSITION LOCK? is reporting that the barometer is reporting <1m and OVINS > 1m (-1 in NED space). It appears OVINS had a blow up, has recovered with a new origin in the local frame. Your output says it must have reseted in the ai/flying and hence the new local origin is above your landing point (fixed frame). Depending how you have PX4's EKF setup could lead to issues like the landing detector not working, or position error when running missions, hence why it's reported as a warning. Your output says it's at 0,0,-15 indicating OVINS restarted at ~15m up, but the PX4 baro says it's at 0. If outdoors, I recommend setting EKF2_HGT_REF = baro, if indoors, you'll need to reconcile a origin offset if VIO resets midair (qvio would require this as well) if using vio data directly waypoint manager (i.e. offboard waypoint mode or custom nav code)

Going forward if staying with 1.4.x,

edit /etc/modalai/voxl-open-vins-server.conf and change:
"en_vio_always_on": true, ssh into the drone and run voxl-vision-hub --debug_fixed_frame --debug_tag_cam --debug_odometry to compare values and see if there is a error in calculation possibly causing vision-hub to restart. move the drone around by hand, point it at a tag as needed and monitor the output from vision-hub. Should tell you where a possible conflict arises.

@jacob-yaacubov We have some add-on boards that would allow connection of 2 USB cameras. For example: https://www.modalai.com/collections/voxl-2-add-ons/products/voxl-microhard-modem-usb-hub and https://www.modalai.com/collections/voxl-2-add-ons/products/voxl-lte?variant=32449203601459

@jacob-yaacubov said in px4 params flow to autopilot:

sometimes at bootup the QGC says all parameters lost

Hi Jacob - Unsure if I am fully following but this is the explanation for how parameters work on the voxl2:

Every boot of the voxl2 kick off the px4 instance if you have that service enabled - it will then grab the parameters from /data/px4/param (if a parameter file already exists) - if you save a file from QGC of edit a parameter, from their, it will update in this file as well. As for why the parameters are lost - I am assuming what you mean is the parameter file isnt fully loaded (AKA the green bar at the top of qgc never finishes because of a timeout) - if that is the case I would recommend trying another qgc instance on a different device like a phone or different os (mac vs linux vs windows) - and see if the problem persists.

Zach

@jacob-yaacubov said in Mavlink server configuration of ports wont work:

branches

@jacob-yaacubov said in Mavlink server configuration of ports wont work:

both ros master run on 127.0.01 so its local ros communication looks more like mavlink issue not sure though

Reply

@jacob-yaacubov yes you need to change the mav sys id for both otherwise they will overlap and create the problem you stated before when connecting to qgc and having overlapping px4 instances. As for ROS you need to change the ROS_DOMAIN_ID (an external terminal environment variable) otherwise all the ros topics will also overlap and create multiple publishers and subscribers on the same drone when you have multiple on.

Zach

@Alex-Kushleyev yes seems like it, thank you!

@jacob-yaacubov ,

I am not sure why this is happening. However, you maybe able to debug this yourself using gdb and starting the ros node manually:

gdb /opt/ros/melodic/lib/voxl_mpa_to_ros/voxl_mpa_to_ros_node r __name:=voxl_mpa_to_ros_node __log:=/opt/ros/foxy/log/my_new_ros_log/voxl_mpa_to_ros_node-1.log (wait for crash) bt (this will print stack backtrace, at least will tell you in which function the crash occurred)

Please try..

Great @jacob-yaacubov. Sorry for the issue overall, but glad we made it right.

@Jeremy-Frederick I'm guessing that the black 4 wire cable between the VOXL 2 and the APM may have some issues making an occasional problem for the i2c bus. Do you have another one of those cables to swap with?

Yes you can look at it that way. Pose is just the generic positional data inclusive of the quaternion and imu wrt vio/camera - odometry is that as well as things like the twist or better known as velocity wrt to the vio instance/camera and the angular velocity wrt to the vio/camera.

Let me know if this better helps you understand - all the code is open sourced btw so feel free to take a gander for a programatic understanding:

https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-mpa-to-ros2/-/blob/master/colcon_ws/src/voxl_mpa_to_ros2/src/interfaces/qvio_interface.cpp?ref_type=heads#L113

Regarding enabling additional cameras, it is is not trivial and it would require a special kernel (because it would break the existing stereo camera support). Additionally, it would require a special interposer / cable in order to use a stereo pair with another camera on a single connector (this hardware does not exist now). At this time, we do not have plans to enable this functionality. As an option, you could potentially hook up a USB camera (will require an usb expansion adapter) to supplement existing cameras (using UVC interface), but we don't provide as much support for that option since that is 3rd party hardware and software.

@Jeffrey-Mao voxl-mpa-ros2 is on the dev branch and not yet on stable. We expect more comprehensive testing and promotion to stable in the next few weeks. In the meantime, you can experiment with the latest code in the dev repository at your own risk