GS and drone are not connected #409

fumimatsu · 2025-02-19T11:11:02Z

fumimatsu
Feb 19, 2025

Thanks for the great product.

I am looking to create a standard setup using rpi 3B+ and Zero 2W.
Flashed 25.01-rc2 from release and some necessary services seem to be working!

However, the drone and GS do not seem to be connected.

What should I check in order to display the video

gs side

message.txt

drone side

Answered by svpcom

Feb 20, 2025

Try to set stbc = 0 and ldpc = 0

View full answer

fumimatsu · 2025-02-19T14:37:59Z

fumimatsu
Feb 19, 2025
Author

I thought this was a common KeyPair problem, so I created a key and saved it, but no luck!

I can't get a ping through to each IP in the first place.
ping 10.5.0.1 or 2
If everything is normal, can I connect to this IP first by ping or ssh?

19 replies

fumimatsu Feb 19, 2025
Author

i use WI-U2-433DMS This product also has 2.4Ghz.
same adapter both, air is rpi zero 2 w with wfb-ng 25.01-rc2

Below are the logs i checked after changing to 5Ghz

at gs
■journalctl -xu wifibroadcast@gs

Feb 19 14:39:29 raspberrypi systemd[1]: Started [email protected] - WFB-ng standalone server, profile gs.
aa Subject: A start job for unit [email protected] has finished successfully
aa Defined-By: systemd
aa Support: https://www.debian.org/support
aa
aa A start job for unit [email protected] has finished successfully.
aa
aa The job identifier is 624.
Feb 19 14:39:32 raspberrypi bash[799]: [server.main #info] WFB-ng version 25.2.12.74062-1d14a1a3
Feb 19 14:39:32 raspberrypi bash[799]: [server.main #info] Run on armv7l/6.1.21-v7+ @raspberrypi, profile(s): ['gs'], using: ['wlan0']
Feb 19 14:39:32 raspberrypi bash[799]: [server.main #info] Using config files:
Feb 19 14:39:32 raspberrypi bash[799]: /usr/lib/python3/dist-packages/wfb_ng/conf/master.cfg
Feb 19 14:39:32 raspberrypi bash[799]: /usr/lib/python3/dist-packages/wfb_ng/conf/site.cfg
Feb 19 14:39:32 raspberrypi bash[799]: /etc/wifibroadcast.cfg
Feb 19 14:39:32 raspberrypi bash[799]: [defer.Deferred._runCallbacks #info] # iw reg set BO
Feb 19 14:39:32 raspberrypi bash[799]: [defer.Deferred._runCallbacks #info] # nmcli device show wlan0
Feb 19 14:39:32 raspberrypi bash[799]: [server.init_wlans #info] Switch wlan0 to unmanaged state
Feb 19 14:39:32 raspberrypi bash[799]: [defer.Deferred._runCallbacks #info] # nmcli device set wlan0 managed no
Feb 19 14:39:33 raspberrypi bash[799]: [defer.Deferred._runCallbacks #info] # ip link set wlan0 down
Feb 19 14:39:33 raspberrypi bash[799]: [defer.Deferred._runCallbacks #info] # iw dev wlan0 set monitor otherbss
Feb 19 14:39:33 raspberrypi bash[799]: [defer.Deferred._runCallbacks #info] # ip link set wlan0 up
Feb 19 14:39:33 raspberrypi bash[799]: [defer.Deferred._runCallbacks #info] # iw dev wlan0 set channel 100 HT20
Feb 19 14:39:33 raspberrypi bash[799]: [defer.Deferred._runCallbacks #info] # iw dev wlan0 set txpower fixed -1500
Feb 19 14:39:33 raspberrypi bash[799]: [tcp.Port.startListening #info] MsgPackAPIFactory starting on 8003
Feb 19 14:39:33 raspberrypi bash[799]: [tcp.Port.startListening #info] JSONAPIFactory starting on 8103
Feb 19 14:39:33 raspberrypi bash[799]: [server.init #info] Starting gs/video@default
Feb 19 14:39:33 raspberrypi bash[799]: [services.init_udp_direct_rx #info] Send video stream 0 to 127.0.0.1:5600
Feb 19 14:39:33 raspberrypi bash[799]: [protocols.RXProtocol.connectionMade #info] Started video rx
Feb 19 14:39:33 raspberrypi bash[799]: [services.init_udp_direct_rx #info] video: /usr/bin/wfb_rx -p 0 -c 127.0.0.1 -u 5600 -K /etc/gs.key -R 2097152 -l 1000 -i>
Feb 19 14:39:33 raspberrypi bash[799]: [server.init #info] Starting gs/mavlink@default
Feb 19 14:39:33 raspberrypi bash[799]: [services.init_mavlink #info] Connect mavlink stream 16(RX), 144(TX) to 127.0.0.1:14550
Feb 19 14:39:33 raspberrypi bash[799]: [services.init_mavlink #info] Mirror mavlink stream to OSD at 127.0.0.1:14551
Feb 19 14:39:33 raspberrypi bash[799]: [udp.Port._bindSocket #info] UDPProxyProtocol starting on 60450
Feb 19 14:39:33 raspberrypi bash[799]: [services.init_mavlink #info] mavlink RX: /usr/bin/wfb_rx -p 16 -u 60450 -K /etc/gs.key -R 2097152 -l 1000 -i 7669206 wla>
Feb 19 14:39:33 raspberrypi bash[799]: [services.init_mavlink #info] mavlink TX: /usr/bin/wfb_tx -f data -p 144 -u 0 -K /etc/gs.key -B 20 -G long -S 1 -L 1 -M 1>
Feb 19 14:39:33 raspberrypi bash[799]: [protocols.TXProtocol.connectionMade #info] Started mavlink tx
Feb 19 14:39:33 raspberrypi bash[799]: [server.init #info] Starting gs/tunnel@default
Feb 19 14:39:33 raspberrypi bash[799]: [udp.Port._bindSocket #info] UDPProxyProtocol starting on 54249
Feb 19 14:39:33 raspberrypi bash[799]: [services.init_tunnel #info] tunnel RX: /usr/bin/wfb_rx -p 32 -u 54249 -K /etc/gs.key -R 2097152 -l 1000 -i 7669206 wlan0
Feb 19 14:39:33 raspberrypi bash[799]: [services.init_tunnel #info] tunnel TX: /usr/bin/wfb_tx -f data -p 160 -u 0 -K /etc/gs.key -B 20 -G long -S 1 -L 1 -M 1 ->
Feb 19 14:39:33 raspberrypi bash[799]: [protocols.TXProtocol.connectionMade #info] Started tunnel tx
Feb 19 14:39:33 raspberrypi bash[799]: [protocols.DbgProtocol.lineReceived #info] mavlink tx: Using data frames
Feb 19 14:39:33 raspberrypi bash[799]: [protocols.DbgProtocol.lineReceived #info] mavlink tx: Listen on 52381 for wlan0
Feb 19 14:39:33 raspberrypi bash[799]: [protocols.DbgProtocol.lineReceived #info] mavlink tx: Listen on 48049 for management commands
Feb 19 14:39:33 raspberrypi bash[799]: [services.init_mavlink #info] mavlink use wfb_tx ports {0: 52381}, control_port 48049
Feb 19 14:39:33 raspberrypi bash[799]: [udp.Port._bindSocket #info] MavlinkUDPProxyProtocol starting on 56139
Feb 19 14:39:33 raspberrypi bash[799]: [udp.Port._bindSocket #info] UDPProxyProtocol starting on 42143
Feb 19 14:39:33 raspberrypi bash[799]: [protocols.RXProtocol.connectionMade #info] Started mavlink rx
Feb 19 14:39:33 raspberrypi bash[799]: [protocols.DbgProtocol.lineReceived #info] tunnel tx: Using data frames
Feb 19 14:39:33 raspberrypi bash[799]: [protocols.DbgProtocol.lineReceived #info] tunnel tx: Listen on 34614 for wlan0
Feb 19 14:39:33 raspberrypi bash[799]: [protocols.DbgProtocol.lineReceived #info] tunnel tx: Listen on 42065 for management commands
Feb 19 14:39:33 raspberrypi bash[799]: [services.init_tunnel #info] tunnel use wfb_tx ports {0: 34614}, control_port 42065
Feb 19 14:39:33 raspberrypi bash[799]: [udp.Port._bindSocket #info] UDPProxyProtocol starting on 36061
Feb 19 14:39:33 raspberrypi bash[799]: [protocols.RXProtocol.connectionMade #info] Started tunnel rx

■lsusb
pi@raspberrypi:~ $ lsusb
Bus 001 Device 004: ID 0411:0242 BUFFALO INC. (formerly MelCo., Inc.) 802.11ac WLAN Adapter
Bus 001 Device 003: ID 0424:ec00 Microchip Technology, Inc. (formerly SMSC) SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Microchip Technology, Inc. (formerly SMSC) SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

■ethtool
pi@raspberrypi:~ $ ethtool -i wlan0
driver: rtl88xxau_wfb
version: 6.1.21-v7+
firmware-version:
expansion-rom-version:
bus-info: 1-1.2:1.0
supports-statistics: no
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no

at drone sorry picture
■journalctl -xu wifibroadcast@drone

■lsusb

■ethtool

svpcom Feb 19, 2025
Maintainer

Please also upload /etc/wifibroadcast.cfg both from drone and gs

fumimatsu Feb 20, 2025
Author

thanks

■ this is at gs

See /usr/lib/python3/dist-packages/wfb_ng/conf/master.cfg

for all available options. You can override any of the in this file

Section inheritance order:

drone video: 'base', 'drone_base', 'video', 'drone_video'

drone mavlink: 'base', 'drone_base', 'mavlink', 'drone_mavlink'

drone tunnel: 'base', 'drone_base', 'tunnel', 'drone_tunnel'

gs video: 'base', 'gs_base', 'video', 'gs_video'

gs mavlink: 'base', 'gs_base', 'mavlink', 'gs_mavlink'

gs tunnel: 'base', 'gs_base', 'tunnel', 'gs_tunnel'

During wfb-ng startup master.cfg will be merged with wifibroadcast.cfg and

then for each service all sections will be merged in order of inheritance (see above).

For advanced config usage (adding new profile, etc) see master.cfg for reference

[common]
wifi_channel = 100 # default channel for 5.8 GHz

log_file = None # Set to "wifibroadcast.log" to disable logging via systemd

link_id = "default" # It will be hashed and mapped to three bytes of MAC
# You can use different link ids for multi-vehicle setup without stream remapping.
# For that case need to have several instances of wifibroadcast.cfg on GS - one for each link (GS <-> droneX)
# Redefine peer addresses, tunnel interfaces and tunnel addresses to not overlap
# Copy and rename [email protected] service and set path to custom wfb config.

wifi_txpower = -1500 # Leave None to use default power settings from driver.
# For 8812au set to -dBm * 100. I.e for 30dBm set to -3000
# For 8812eu set to dBm * 100. I.e for 30dBm set to 3000
# All driver default settings are in /etc/modprobe.d/wfb.conf

[base]
bandwidth = 20 # bandwidth 10 (8812eu only), 20, 40 or 80 MHz
force_vht = False # Force VHT headers instead of HT for 10/20/40 MHz bandwidth modes
short_gi = False # use short GI or not
stbc = 1 # stbc streams: 1, 2, 3 or 0 if unused
ldpc = 1 # 8812au only
mcs_index = 1 # mcs index

###############################

DRONE PART

###############################

[drone_mavlink]

Uncoment if you need to forward mavlink stream from the drone uart

#peer = 'serial:/dev/ttyS0:1500000' # Serial port for autopilot

###############################

GS PART

###############################

[gs_video]
peer = 'connect://127.0.0.1:5600' # outgoing connection for RTP video sink (RTSP server (default), local video pipeline or QGC), use 224.0.0.1 for multicast streaming

[gs_mavlink]
#peer = 'connect://192.168.1.1:14550' # QGC address
osd = 'connect://127.0.0.1:14551' # Builtin wfb-ng-osd

■ this is for drone

See /usr/lib/python3/dist-packages/wfb_ng/conf/master.cfg

for all available options. You can override any of the in this file

Section inheritance order:

drone video: 'base', 'drone_base', 'video', 'drone_video'

drone mavlink: 'base', 'drone_base', 'mavlink', 'drone_mavlink'

drone tunnel: 'base', 'drone_base', 'tunnel', 'drone_tunnel'

gs video: 'base', 'gs_base', 'video', 'gs_video'

gs mavlink: 'base', 'gs_base', 'mavlink', 'gs_mavlink'

gs tunnel: 'base', 'gs_base', 'tunnel', 'gs_tunnel'

During wfb-ng startup master.cfg will be merged with wifibroadcast.cfg and

then for each service all sections will be merged in order of inheritance (see above).

For advanced config usage (adding new profile, etc) see master.cfg for reference

[common]
wifi_channel = 100 # default channel for 5.8 GHz

log_file = None # Set to "wifibroadcast.log" to disable logging via systemd

link_id = "default" # It will be hashed and mapped to three bytes of MAC
# You can use different link ids for multi-vehicle setup without stream remapping.
# For that case need to have several instances of wifibroadcast.cfg on GS - one for each link (GS <-> droneX)
# Redefine peer addresses, tunnel interfaces and tunnel addresses to not overlap
# Copy and rename [email protected] service and set path to custom wfb config.

wifi_txpower = -1500 # Leave None to use default power settings from driver.
# For 8812au set to -dBm * 100. I.e for 30dBm set to -3000
# For 8812eu set to dBm * 100. I.e for 30dBm set to 3000
# All driver default settings are in /etc/modprobe.d/wfb.conf

[base]
bandwidth = 20 # bandwidth 10 (8812eu only), 20, 40 or 80 MHz
force_vht = False # Force VHT headers instead of HT for 10/20/40 MHz bandwidth modes
short_gi = False # use short GI or not
stbc = 1 # stbc streams: 1, 2, 3 or 0 if unused
ldpc = 1 # 8812au only
mcs_index = 1 # mcs index

###############################

DRONE PART

###############################

[drone_mavlink]

Uncoment if you need to forward mavlink stream from the drone uart

#peer = 'serial:/dev/ttyS0:1500000' # Serial port for autopilot

###############################

GS PART

###############################

[gs_video]
peer = 'connect://127.0.0.1:5600' # outgoing connection for RTP video sink (RTSP server (default), local video pipeline or QGC), use 224.0.0.1 for multicast streaming

[gs_mavlink]
#peer = 'connect://192.168.1.1:14550' # QGC address
osd = 'connect://127.0.0.1:14551' # Builtin wfb-ng-osd

svpcom Feb 20, 2025
Maintainer

Try to set stbc = 0 and ldpc = 0

Answer selected by fumimatsu

fumimatsu Feb 20, 2025
Author

thanks! connection is comming!
but no video image...

I guess I haven't finished setting up my camera correctly yet.
But I was able to make the connection. Thanks.

fumimatsu Feb 20, 2025
Author

Video is comming !
thank you for your support!

480029133_28879903014990826_759251783266606806_n.mp4

svpcom Feb 20, 2025
Maintainer

Try to set stbc = 0 and ldpc = 0

This means that your cards are not 8812au, because 8812au must have stbc and ldpc support.

svpcom Feb 20, 2025
Maintainer

They may be *bu or *cu chip variants. Could you look inside?

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

GS and drone are not connected #409

{{title}}

Replies: 1 comment 19 replies

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

GS and drone are not connected #409

fumimatsu Feb 19, 2025

Replies: 1 comment · 19 replies

fumimatsu Feb 19, 2025 Author

fumimatsu Feb 19, 2025 Author

svpcom Feb 19, 2025 Maintainer

fumimatsu Feb 20, 2025 Author

See /usr/lib/python3/dist-packages/wfb_ng/conf/master.cfg

for all available options. You can override any of the in this file

Section inheritance order:

drone video: 'base', 'drone_base', 'video', 'drone_video'

drone mavlink: 'base', 'drone_base', 'mavlink', 'drone_mavlink'

drone tunnel: 'base', 'drone_base', 'tunnel', 'drone_tunnel'

gs video: 'base', 'gs_base', 'video', 'gs_video'

gs mavlink: 'base', 'gs_base', 'mavlink', 'gs_mavlink'

gs tunnel: 'base', 'gs_base', 'tunnel', 'gs_tunnel'

During wfb-ng startup master.cfg will be merged with wifibroadcast.cfg and

then for each service all sections will be merged in order of inheritance (see above).

For advanced config usage (adding new profile, etc) see master.cfg for reference

DRONE PART

Uncoment if you need to forward mavlink stream from the drone uart

GS PART

See /usr/lib/python3/dist-packages/wfb_ng/conf/master.cfg

for all available options. You can override any of the in this file

Section inheritance order:

drone video: 'base', 'drone_base', 'video', 'drone_video'

drone mavlink: 'base', 'drone_base', 'mavlink', 'drone_mavlink'

drone tunnel: 'base', 'drone_base', 'tunnel', 'drone_tunnel'

gs video: 'base', 'gs_base', 'video', 'gs_video'

gs mavlink: 'base', 'gs_base', 'mavlink', 'gs_mavlink'

gs tunnel: 'base', 'gs_base', 'tunnel', 'gs_tunnel'

During wfb-ng startup master.cfg will be merged with wifibroadcast.cfg and

then for each service all sections will be merged in order of inheritance (see above).

For advanced config usage (adding new profile, etc) see master.cfg for reference

DRONE PART

Uncoment if you need to forward mavlink stream from the drone uart

GS PART

svpcom Feb 20, 2025 Maintainer

fumimatsu Feb 20, 2025 Author

fumimatsu Feb 20, 2025 Author

svpcom Feb 20, 2025 Maintainer

svpcom Feb 20, 2025 Maintainer

fumimatsu
Feb 19, 2025

Replies: 1 comment 19 replies

fumimatsu
Feb 19, 2025
Author

fumimatsu Feb 19, 2025
Author

svpcom Feb 19, 2025
Maintainer

fumimatsu Feb 20, 2025
Author

svpcom Feb 20, 2025
Maintainer

fumimatsu Feb 20, 2025
Author

fumimatsu Feb 20, 2025
Author

svpcom Feb 20, 2025
Maintainer

svpcom Feb 20, 2025
Maintainer