PX4 / PX4-windows-toolchain

Repo containing all scripts to install and use the PX4 Toolchain for Windows.
BSD 3-Clause "New" or "Revised" License
31 stars 100 forks source link

Failed sending mavlink message: Address family not supported by protocol #8

Open MikaelFerland opened 5 years ago

MikaelFerland commented 5 years ago

Hi guys, I install the PX4 Toolchain on my Windows 10 laptop and I get this warning Failed sending mavlink message: Address family not supported by protocol here is my console output : `BUILD SUCCESSFUL Total time: 4 seconds Options parsed, starting Sim. Starting GUI... 3D [dev] 1.6.0-pre12-daily-experimental daily

INFO [simulator] Simulator connected on TCP port 4560. WARN WARN [simulator] [simulator] Failed sending mavlink message: Address family not supported by protocolFailed sending mavlink message: Address family not supported by protocol

INFO [init] Mixer: etc/mixers/quad_w.main.mix on /dev/pwm_output0 INFO [mavlink] mode: Normal, data rate: 4000000 B/s on udp port 14570 remote port 14550 INFO [mavlink] mode: Onboard, data rate: 4000000 B/s on udp port 14580 remote port 14540 INFO [logger] logger started (mode=all) INFO [logger] Start file log (type: full) INFO [logger] Opened full log file: ./log/2019-01-19/03_19_22.ulg INFO [mavlink] MAVLink only on localhost (set param MAV_BROADCAST = 1 to enable network) INFO [px4] Startup script returned successfully pxh>`

After some research I found that his cause by the TCP connect on 0.0.0.0 from here https://github.com/PX4/Firmware/blob/master/src/modules/simulator/simulator_mavlink.cpp#L663 I find post that mentioned it works on Linux because they redirect it to 127.0.0.1 and I can be confirm by pinging the 0.0.0.0, but it doesn't work on a Windows machine.

For some reason, I tried on an other Windows 10 computer and I did get this warning. I compare my route on both and seems similar between each other.

But the computer with the warning has the Windows 10 October update (1809) and the one working has not.

As you know jMAVSim depends on the first heartbeat to initialize MAVLink. So it never happen because of the warning.

I hope we will find the problem together, Regards,

MikaelFerland commented 5 years ago

They fix it here https://github.com/PX4/Firmware/pull/11101/commits/30ccb784a62c2bcee98cdd14d6114fb29d20e94e