MSPOSD osd message blocks Adaptive Link osd message

[i998]

Configuration: Runcam WiFi Link OpenIPC camera and Pixel Pilot Android App. Adaptive link installed and turned on. WFB-NG connection.

Issue: Adaptive Link osd message is not visible unless a telemetry link from a flight controller is properly connected and functional. Otherwise the MSPOSD shows red "Waiting for data..." message and does not allow process Adaptive-Link osd info.

How to reproduce:

1. Connect a Flight Controller to Runcam WiFi Link camera, run Pixel Pilot Android App and see the adaptive link message from https://github.com/OpenIPC/adaptive-link/blob/3a831a75cb25df403374fa5104ea494c140695da/alink_drone.c#L1419

This is the expected behavior.

2. Run the Runcam WiFi Link camera and run Pixel Pilot Android App without a Flight Controller connected. See the red MSPOSD message from

   msposd/osd.c

   Line 2855 in 060e019

   sprintf(msgbuff, "&F48 &L23 Waiting for data on %s ...", _port_name);

This is an issue - MSPOSD osd message blocks Adaptive Link osd message, cannot see Adaptive Link osd message without a running Flight Controller.

Appreciate your help with this issue.

[tipoman9]

Although the idea of msposd is to render FlightController's MSP Display Port messages over the display, I think I've added an option to enable this some time ago.
Can you try to add -x 99 or --matrix 99 to the command line arguments?

[i998]

Thank you, tipoman9, for your attention to this issue.
Could you please clarify which command line (i.e. msposd or adaptive link or else) I need to add the arguments to and where can I find that command line? I have WinSCP access to the Runcam camera file system but need further directions where to find the correct command.

P.S. Just to clarify, the problem is to stop relying on the telemetry traffic from a Flight Controller. I would like to use the RunCam as-is, with no Flight Controller but still see the telemetry from Adaptive Link.

[tipoman9]

I don't know where exactly the msposd is initialized in the firmware you use.
you may check the /usr/bin/wifibroadcast file
It may look like

If you find it there, simply add -x 99 at the end of the arguments line

[i998]

I checked the /usr/bin/wifibroadcast file. For Runcam WifiLink it has the following function:

start_telemetry() {
chipset=$(ipcinfo -c)
[ "$chipset" = "ssc33x" ] && devmem 0x1F207890 16 0x8

port_rx=14550
port_tx=14551

echo_log "Starting $router"
load_wfb 144 16 "$port_rx" "$port_tx"

if [ "$router" = "mavfwd" ]; then
	mavfwd -b 115200 -c 8 -p 100 -a 15 -t -m /dev/"$serial" \
		-o 127.0.0.1:"$port_tx" -i 127.0.0.1:"$port_rx" > /dev/null &
else
	if [ "$router" = "msposd" ]; then
		size=$(curl -s localhost/api/v1/config.json | jsonfilter -qe "@.video0.size")
	fi
	msposd -b 115200 -c 8 -r "$osd_fps" -m /dev/"$serial" \
		-o 127.0.0.1:"$port_tx" -z "$size" > /dev/null &
	sleep 5
	echo "&L70&F28&G8CPU:&C TEMP:&T\n&B" >/tmp/MSPOSD.msg
fi

}

Added the -x 99 as below,

	msposd -b 115200 -c 8 -r "$osd_fps" -m /dev/"$serial" \
		-o 127.0.0.1:"$port_tx" -z "$size" -x 99 > /dev/null &

restarted the camera and got the green telemetry message without the flight controller - as expected.

Thank you a lot for helping with this!
Regards, i988