Skip to content

InternalGPS has a conflict with S-port telemetry #7435

Description

@Billy60

Is there an existing issue for this problem?

  • I have searched the existing issues

What part of EdgeTX is the focus of this bug?

Transmitter firmware

Current Behavior

I have been trying to have InternalGPS work and also have a model GPS position be used after received by telemetry via S-port. InternalGPS is to be connected to UART2. When this is done, all telemetry data are not fournd anymore and it is not possible to have both Model GPS position and internal transmistter position properly received and used. I presume there is a conflict in names: ahead of the 'sensor renaming' feature, both GPS signals kill each other.
FW is 2.12.1

Expected Behavior

The telemetric sensors should be found and made available even if InternalGPS has a signal. I would expect to have both signals appear and be used.
I would also expect UART1 to be used, and also other UARTs showed on the main PCB (UART3 etc)
Also, I would expect the Baud rate for the incoming GPS positions to ba also received at a higher rate than 9600. A automatic feature would adapt the TX software so it accepts a Buad rate speed up to at least 32600.

Steps To Reproduce

When no telemetry is sent / received: 'GPS' sensor shows and is available for use in widgets. All sensors are found and made available.
If a Telemetry GPS fix is received, both sensors are not displayed in the sensor list, 'GPS' stays at --, all other sensors are not found anymore. No 'internalGPS' sensor is found.
Renaming the GPS sensor does not help.

Version

2.12.1

Transmitter

RadioMaster TX16S / TX16SMK2

Operating System (OS)

No response

OS Version

No response

Anything else?

HOw come nobody can axplain what is UART1 for ? it seems to be unavailable. Please document the use and limits of all UARTso on the PCB.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions