Topics created by voxltester

@voxltester As I tried to explain before, don't wait for voxl-mavlink-server to connect to your application. You need to have it initiate the connection to voxl-mavlink-server.

Hey @voxltester
It seems there is an issue with how MicroXRCE and the microhard modem interfaces are starting up, I had to edit the service files to get the topics on the VOXL2.
Edit /etc/systemd/system/voxl-microdds-agent.service:

[Unit] Description=voxl-microdds-agent SourcePath=/usr/bin/MicroXRCEAgent After=network.target After=multi-user.target [Service] User=root Type=simple ExecStart=/usr/bin/MicroXRCEAgent udp4 -p 8888 [Install] WantedBy=multi-user.target

Edit /etc/systemd/system/voxl-modem.service:

[Unit] Description=Modem Initialization After=sdsprpcd.service [Service] User=root Type=oneshot ExecStartPre=/bin/sleep 2 ExecStart=/usr/bin/voxl-modem-start RemainAfterExit=yes [Install] WantedBy=multi-user.target

Add export ROS_DOMAIN_ID=0 to your .bashrc
Reboot the VOXL2, and the topics should come up
Thanks

@voxltester Great! Glad you got it working.

@voxltester Only if it is connected to a GCS that sends the Mavlink SYSTEM_TIME message.

Hi @voxltester
Are you able to post a high res photo of the USB breakout board, both top and bottom?
Could save you the time and hassle of an RMA with a good high quality photo I can inspect.

The board was tested and passed before shipping, but these boards do have some small parts on that that are susceptible to damage if the board is dropped or if a tool or other item hits into it.

Thanks!