> For the complete documentation index, see [llms.txt](https://survey.fmpx.docs.frox-it.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://survey.fmpx.docs.frox-it.de/gnss-antennen-einrichten/leica-zeno-connect-antennen-gg04-flx100/verbindung-uber-gnss-nmea.md).

# Verbindung über GNSS NMEA

Modul **M-FX GNSS NMEA**

Das Modul M-FX GNSS NMEA läuft ohne Kivid Feld Treiber.

Für alle Antennen, die über den NMEA Treiber angebunden werden, muss in FX Survey im Menü Programmeinstellungen / GNSS unter Receiver die Option NMEA ausgewählt werden.

<figure><img src="https://415365806-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FavDnAykoA7C7prWiDq6h%2Fuploads%2FGoREyPyGbAM1daQtS5ci%2Fgrafik.png?alt=media&amp;token=e9838bf1-0895-4627-9dc2-9a12445e6a13" alt=""><figcaption></figcaption></figure>

Die Verbindung der Antenne zu FX Survey erfolgt über einen COM Port. Die GNSS Antenne muss NMEA Daten per Bluetooth senden.&#x20;

Zunächst wird die Antenne per Bluetooth in Windows gekoppelt. Dabei wird ein COM Port vergeben. Den COM Port in den Programmeinstellungen unter dem Reiter GNSS FX Survey eintragen.

Der Korrekturdatendienst wird über die Antenne definiert.

&#x20;


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://survey.fmpx.docs.frox-it.de/gnss-antennen-einrichten/leica-zeno-connect-antennen-gg04-flx100/verbindung-uber-gnss-nmea.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
