@tahawaru just to confirm you have turned off figure 8 offboard mode in voxl-vision-hub? Also does the drone arm when stating "drone arming" - lastly, do you have the dds agent running on the voxl2? There is a part of me that is nervous since you are running this on the rb5 and not a voxl2 that the px4 instance on there is quite stale and doesnt have the dds CLIENT sitting in the executable script. take a look at /usr/bin/voxl-px4-start and check if there is reference to the dds client.
Zach
@vicky-s-karthik mind posting the exact commands that you ran?
ROS melodic is fully deprecated - so my recommendation is to move over to ros2 foxy which is what we support on the voxl2 as of right now. I will try and recreate your issue in the meantime. Please try installing ros melodic base as the cv2 instance on there conflicts with opencv on voxl-sdk.
@Kiazoa-Joao so first you should be leveraging: https://gitlab.com/voxl-public/voxl-docker-images/voxl-docker-mavsdk
Voxl-docker-mavsdk-python is quite stale - the voxl-docker-mavsdk directory above is maintained and meant to run mavsdk python and c++ implementation.
What this will do is build the docker image on the parent computer and then push the docker tarball onto the voxl2 to be loaded. Then the user can run it from the voxl2.
Just follow the instructions in this repository and paste if you get any errors.
Zach
@Ansel-Misfeldt said in SBUS not detected:
Let me know if you need us to test the specific version it breaks on.
Reply
@Ansel-Misfeldt will flash a flight core and let you know what we find.
Zach
Hi @Karl-pan no I cannot say we have come accross this error before but will have a solution soon - just to confirm, can you paste you conf file in /etc/modalai/voxl-tflite-server.conf as well as run voxl-inspect-cam -a to ensure the camera is outputting the frames. It sounds more like an issue with camera server than tflite if you are trying to access a nullptr that is the frame.
Will look into this.
Zach
Looks like I misspoke - you are connecting to the DSP - SO due to that we need to keep voxl-mavlink-server on there to allow the packets to be forwarded from the DSP to the system. I will say there MIGHT be a way to forward the ports from the mavlink-server instance into the microdds agent so the topics are exposed.
We will look into this!
Zach
@Gary-Holmgren you will have to either edit or disable the ROS2 DDS on the voxl2 and create a new one that uses the serial link - aka ttyHSX. So in the microdds agent service file in /etc/systemd/system you will have to edit the file to change from listening to the UDP port and then listen the serial link. However, by doing this you will then conflict with the mavlink-server instance running on the voxl2 as well.
LMK if this helps.
Zach
@Darshit-Desai are your ROS_ID's the same between the docker and disk? If not how are you sharing the interfaces into the ros docker instance?
If it is easier you can just share the /opt/ros/foxy/mpa_to_ros2 directory as a volume as well as the /run/mpa directory as a volume and run the ros2 node in the docker instance. The other thing to note is I am unsure if there is compatibility between foxy and humble in terms of the nodes or if there are some internal conflicts happening behind the scenes.
Zach
@Gary-Holmgren said in ROS2 errors on VOXL2:
-source /opt/ros/foxy/setup.bash
Hey @Gary-Holmgren! So this is an issue with a conflict in the emPY library - it should have been updated in the most recent SDK release - however the solution programmatically is the following:
python3 -m pip uninstall -y empy
python3 -m pip install empy==3.3.4
Cheers!
Zach
@Jeremy-Frederick said in External MAVLink Connection using VOXL 2 through ttyHS1:
I'm looking to establish an external MAVLink connection to the voxl-px4 service on VOXL 2 through the ttyHS1 of the USB3 expansion board. I'm looking to integrate a third party RemoteID module, and am not implementing an external flight controller.
@Jeremy-Frederick voxl-mavlink-server is meant to act similar to mavlink-router where it can route traffic (two way comms) between a specific port or hardline. How are you connecting to your remoteID module? Over the UART I would presume as that is the only way to send those packets. If you are using the USB3.0 port instead then you will need to either edit voxl-mavlink-server or create a mavlink-router to route the traffic to that port.
A bit more information on your setup would be great!
Zach
@valvarez said in PWM Servo IO Board:
@valvarez that is correct you should power your servo from another power source capable if giving off 5V - if the servo has an operational range though of 3.3-5 then you can power it from the IO board.
Thanks
Zach
I will take a gander at this today @Mohammad-Goli and get abck with an answer - I will say the ros1 is deprecated and we tend to support or push for ros2 - does the same issue persist with ros2?
@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
@navin_kaviyarasu said in Starling2: Flight mode falls to AltitudeHold when switched to PositionHold:
Also, I don't see odometry data on mavlink console, I doubt the issue more than with the parameters!
Reply
@navin_kaviyarasu if the drone starts in position hold and then switches to altitude during the flight, it means it is losing its position during flight and falls back to the flight control that doesnt require the camera.
As for what you can do to resolve this - if you already changed the EKF2 parameters to not take into account the GPS - please proceed to calibrate the following:
LMK how this works!
Zach
@Shivam-Sehgal unsure what you mean by calibration files? As in files for the camera calibration? PX4 Calibration? IMU Calibration? If you specify we can further help. Also most of these parameters for the originals live on the drone under /usr/share/modalai
Zach
@henrytrinh yes this is possible with external storage - you can leverage a USB2.0 or 3.0 and connect a microsd adapter and then mount the drive.
Zach
No - tflite server runs only tflite on the GPU - you can try leveraging the Qualcomm Nueral SDK to get onnx working on the Adreno GPU, but that is a very large lift.
How far away is the gps from the 5g hat? Also have you leveraged faraday tape around the fuselage of your drone so the signal for the gps doesnt get interfered. Odds are the issue isnt from the 5g hat but from the USB3.0 port if you are leveraging. Multiple studies show there is quite a lot of interference from usb3.0 that can disrupt GPS - the solution for this is taking faraday tape and wrapping it around the right spots to cut the signal:
@Jetson-Nano if you plan on using object detection in tflite server, then you can use yolov5 or yolov8 - I am unsure if you can pipe in that data into tflite with it working as that code base is meant to ingest generic raw and nv frames (RAW8/16 or NV12/21) so streaming in a different frame format might cause issue - if this doesnt fail and it works with the pipe, then it is up to you to train your own model based on the thermal camera feed.
Why do you have it set to trajectory? If you are commanding the drone via strictly offboard commands programmatically - vision-hub should have offboard set to "off" so it isnt conflicting offboard commands with what you are feeding in.
Please do this and retest and post the results.