Posts made by MikeD

@Eric-Katzfey We think that Gazebo is transmitting over the serial link based on the following observation. While running Gazebo,
if we power off the VOXL2 FlightDeck Gazebo reports the following:
Exception sending a multicast message:Network is unreachable
If we unplug the FTDI cable from the host Gazebo reports the following:
Tx queue overflow
By the way, the FTDI cable we are using is the MODAL AI MCBL-00091 - we tried two different cables with the same results.
The hardware configuration is a VOXL2 FlightDeck. Could there be anything special we need to do to configure the FlightDeck?

@Eric-Katzfey We finally determined that the heart beat messages were going over an ethernet port and not from the FTDI cable. If I unplug the ethernet connection then we don't get heartbeats any longer. Is there a way to configure the VOXL2 to always use the FTDI connection via J18 on the board or should it just work?

@Eric-Katzfey
The only difference I see is that I'm getting these status messages and you do not:
libcurl: (28) Failed to connect to fuel.ignitionrobotics.org port 443: Connection timed out
libcurl: (28) Failed to connect to fuel.gazebosim.org port 443: Connection timed out

Could this be a problem? Those websites do not appear to exist any longer. Also, if the serial cable was bad how would Wireshark be able to pick up heartbeats from HITL on VOXL2?

Hi -
I'm having issues getting HITL running with ModalAI's Gazebo Docker container while following the instructions below:
https://docs.modalai.com/voxl2-PX4-hitl/#gazebo-setup

1. FTDI cable is connected to J18 and linux host (Ubuntu 22.04)
2. Starting the Docker Gazebo instance reports the following:
   Opened serial device /dev/ttyUSB0
   libcurl: (28) Failed to connect to fuel.ignitionrobotics.org port 443: Connection timed out
   libcurl: (28) Failed to connect to fuel.gazebosim.org port 443: Connection timed out
   ** Gazebo appears to start successfully.
3. In adb shell I run: voxl-px4-hitl
4. Here is an excerpt from that output:

INFO [mavlink] mode: Normal, data rate: 100000 B/s on udp port 14558 remote port 14559
INFO [muorb] SLPI: Marking DeviceNode(telemetry_status) as advertised in process_remote_topic
INFO [muorb] SLPI: Too many arming check events (1, 14 > 14). Not reporting all
INFO [muorb] SLPI: Preflight Fail: No valid data from Accel 0
INFO [muorb] SLPI: Preflight Fail: barometer 0 missing
INFO [muorb] SLPI: Preflight Fail: ekf2 missing data
INFO [muorb] SLPI: Preflight Fail: No valid data from Gyro 0
INFO [muorb] SLPI: Preflight Fail: Compass Sensor 0 missing
INFO [mavlink] MAVLink only on localhost (set param MAV_{i}_BROADCAST = 1 to enable network)
INFO [px4] Startup script returned successfully

==> Note that there are many Preflight check failures.

5. Running dsp_hitl status returns this:
   INFO [muorb] SLPI: Running: yes
   INFO [muorb] SLPI: Status of IMU_Data counter: 0
   INFO [muorb] SLPI: Value of current accel x, y, z data: 0.000000, 0.000000, 0.000000
   INFO [muorb] SLPI: Value of current gyro x, y, z data: 0.000000, 0.000000, 0.000000
   INFO [muorb] SLPI: Value of HIL_Sensor counter: 0
   INFO [muorb] SLPI: Value of Heartbeat counter: 15
   INFO [muorb] SLPI: Value of Vision data counter: 0
   INFO [muorb] SLPI: Value of odometry counter: 0
   INFO [muorb] SLPI: Value of GPS Data counter: 0
   INFO [muorb] SLPI: Ok executing command: dsp_hitl status

==> Note that accel & gyro data are always zero AND only the heartbeat counter is incrementing.

6. Inspection via Wireshark reveals that only heartbeat messages are flowing.

Any help would be greatly appreciated