Skip to content

Ports Menu

Torch: Feature Partially Supported / EVK: Feature Partially Supported

Setting the baud rate of the ports

Setting the baud rates of the two available external ports

Baud rate configuration of Radio and Data ports

Baud rate configuration of Radio and Data ports

Output GNSS Data over USB

Set output to GNSS data over USB Serial

Set output to GNSS data over USB Serial

Enabling Output GNSS data to USB serial will pipe all GNSS output (generally NMEA but also RTCM) to the USB serial connection. This permits a wired connection to be made on devices, such as the RTK Torch, that have only one external port (USB). Note: To exit this mode, press +++ to open the configuration menu.

Additionally, correction may be sent to the device over USB. RTCM corrections received over USB will follow the Corrections Priority table.

Example NMEA output over USB

Example NMEA output over USB

Radio Port

Available on devices that have an external RADIO port.

By default, the Radio port is set to 57600bps to match the Serial Telemetry Radios that are recommended to be used with the RTK Facet (it is a plug-and-play solution). This can be set from 4800bps to 921600bps.

Mux Channel

Available on devices that have a built-in multiplexer on the DATA port.

The Data port on the RTK Facet, Express, and Express Plus is very flexible. Internally the Data connector is connected to a digital mux allowing one of four software-selectable setups. By default, the Data port will be connected to the UART1 of the ZED-F9P and output any messages via serial.

  • NMEA - The TX pin outputs any enabled messages (NMEA, UBX, and RTCM) at a default of 460,800bps (configurable 9600 to 921600bps). The RX pin can receive RTCM for RTK and can also receive UBX configuration commands if desired.
  • PPS/Trigger - The TX pin outputs the pulse-per-second signal that is accurate to 30ns RMS. This pin can be configured as an extremely accurate time base. The pulse length and time between pulses are configurable down to 1us. The RX pin is connected to the EXTINT pin on the ZED-F9P allowing for events to be measured with incredibly accurate nano-second resolution. Useful for things like audio triangulation. See the External Event Logging section below and the Timemark section of the ZED-F9P Integration Manual for more information.
  • I2C - (On Express, Facet, and Facet L-Band) The TX pin operates as SCL, RX pin as SDA on the I2C bus. This allows additional sensors to be connected to the I2C bus.
  • Wheel/Dir Encoder - (On Express Plus) Connect the DATA port to the wheel tick inputs on the ZED-F9R. This aids the Sensor Fusion engine for IMU based location fixes when installed in an automobile. Signals must be limited to 3.3V.
  • GPIO - The TX pin operates as a DAC-capable GPIO on the ESP32. The RX pin operates as an ADC-capable input on the ESP32. This is useful for custom applications.

Data Port

By default, the Data port is set to 460800bps and can be configured from 4800bps to 921600bps. The 460800bps baud rate was chosen to support applications where a large number of messages are enabled and a large amount of data is sent. If you need to decrease the baud rate to 115200bps or other, be sure to monitor the MON-COMM message within u-center for buffer overruns. A baud rate of 115200bps and the NMEA+RXM default configuration at 4Hz will cause buffer overruns.

Monitoring the COM ports on the ZED-F9P

Monitoring the COM ports on the ZED-F9P

If you must run the data port at lower than 460800bps, and you need to enable a large number of messages and/or increase the fix frequency beyond 4Hz, be sure to verify that UART1 usage stays below 99%. The image above shows the UART1 becoming overwhelmed because the ZED cannot transmit at 115200bps fast enough.

Most applications do not need to plug anything into the Data port. Most users will get their NMEA position data over Bluetooth. However, this port can be useful for sending position data to an embedded microcontroller or single-board computer. The pinout is 3.3V / TX / RX / GND. 3.3V is provided by this connector to power a remote device if needed. While the port is capable of sourcing up to 600mA, we do not recommend more than 300mA. This port should not be connected to a power source.

Pulse Per Second

Configuring the External Pulse and External Events

Configuring the External Pulse and External Events over WiFi

RTK Mux Menu

Port menu showing mux data port connections

When PPS/Event Trigger is selected, the Pulse-Per-Second output from the ZED-F9x is sent out of the TX pin of the DATA port. Once the RTK device has GNSS reception, this can be used as a very accurate time base.

The time between pulses can be configured down to 100ns (10MHz) with an accuracy of 30ns RMS and 60ns 99%. The pulse width and polarity are also configurable.

Wires connected to a SparkFun USB C to Serial adapter

For PPS, only the Black and Green wires are needed. If you need to provide 3.3V to your system, the red wire can supply up to 600mA but we do not recommend sourcing more than 300mA.

  • Red - 3.3V
  • Green - TX (output from the RTK device)
  • Orange - RX (input into the RTK device)
  • Black - GND

Similarly, the RX pin of the DATA port can be used for event logging. See External Event Logging for more information.