Ping Sonar Altimeter udp port overlap in blue os

Hello, my name is Seunghyun Kim. I have a question because I had a problem in the process of assembling and testing the blue rov.
I installed one altimeter facing forward and the other facing the floor. However, when I checked in blue os, it uses the same udp.
(One is connected by USB and the other is connected to the Navigator Flight Controller.)
Q1. May I know how to change the port??
Q2. Is it possible to check the data of 2 Altimeters in QGC through Mavlink?
Thank you

Hi @drone_begginer,

This is a previously reported bug, but we haven’t yet had enough information to track it down and fix it. It would be helpful if you could provide a log file for the ping service, from http://blueos.local:7777/file-browser/files/system_logs/ping/ :slight_smile:

The port is determined automatically when the device is detected, and it’s not currently possible to manually override it.

It should technically be possible to manually set up bridges in the Serial Bridges page, although that then means the MAVLink distances won’t be usable, and I’m not sure if there’ll be a conflict between the manual bridges and the automatic ones from the pings service.

If you turn on MAVLink Distances for both devices then measurements from both should show up in QGC, but it likely won’t be possible to tell which measurement is from which device, because the ping service MAVLink driver currently sends all distances as pointing downwards, and I don’t believe the QGC telemetry widget allows filtering by the device ID.

Hi Eliot
thanks for the reply.
here are logfiles
logfile_06-13-2023_05_52_27.2023-06-13_09-23-07_079639.log (89.1 KB)
logfile_06-13-2023_05_52_27.log (4 KB)
logfile_06-19-2023_09_40_09.log (89.8 KB)

Please confirm

ping1D is the new one and the other ping1D is using the old one.
I also attach the sensor details