I/O Configuration – Port Configuration

Use these settings to set up the receiver inputs and outputs.

Select I/O Configuration / Port Configuration.

 

Port Selection

  • Port – The first drop-down list displays which type of port is available for configuration.
  • Output Type – The second drop-down list displays which output type is sent out of each port.

One of the following output groups appears with configuration settings, depending on the option that you select in the drop-down list at the top of the page:

Select one of the following options:

TCP/IP 5017 and TCP/IP 5018

By default, these ports are available. However, these can be changed to add or remove other ports.

Client – Select this check box to enter a Remote IP and port. This enables the receiver to initiate a connection to the remote server. This can be used when the receiver is behind a network firewall or has a dynamic IP address.

Output Only/ Allow Multiple TCP/IP Connections – Select this check box to configure the receiver so that it can broadcast to multiple simultaneous remotes. The remotes are unable to send data back to the receiver. Trimble strongly recommends this setting for all ports without a two-way data requirement. If this is not enabled, remotes can reconfigure the receiver.

UDP Mode – Select this check box to use UDP (User Datagram Protocol) instead of TCP. You can edit a UDP timeout. By default, it is set to 60 seconds.

  • UDP Broadcast Transmit – Selecting this option will allow the broadcast of data (e.g., CMRx) to any devices on the same local network by using the IP broadcast address of 255.255.255.255.
  • UDP Broadcast Receive – Selecting this option will allow the receipt of data (e.g., CMRx) from a UDP Broadcast Transmit device on the same local network.

Authenticate, set password – Select this check box so that all incoming connections are required to enter a password to authenticate the connection. This is not NTRIP authentication.

Add TCP/IP or UDP Port

Select this option to add a new TCP/IP port to the receiver.

UDP Mode – Select this check box to use UDP (User Datagram Protocol) instead of TCP.

Local Port# – Select the port number that is to be used and then click Add to create the configuration.

Depending on the option that you select in the drop-down list at the top of the page, the options for configuration changes:

IBSS/NTRIP Client

This option allows correction data to be received securely from an NTRIP Caster. The NTRIP source may be:

  • A Trimble VRS Network
  • A Trimble NTRIP Caster
  • The Trimble Internet Base Station Service (IBSS) 
  • Another NTRIP compliant correction source

NTRIP version 2 is supported in firmware version 4.14 and later.

Status – Indicates the current status of the NTRIP connection:

Status Meaning
Init NTRIP Client disabled.
Up and Connected NTRIP Client is connected to a source of corrections and receiving data.
Invalid Mountpoint NTRIP error 404 returned from NTRIP Caster.
Invalid Username or Password NTRIP error 401 returned from NTRIP Caster.
Failed to connect to remote NTRIP Caster Connection failed due to an Internet-related issue.
No GNSS data from Caster NTRIP error 503 returned from NTRIP Caster. No data available from the NTRIP Caster.
Unexpected internal error NTRIP Caster internal error.
Incorrect NTRIP Caster response NTRIP error 602 returned from NTRIP Caster.
No output stream is configured NTRIP error 604 returned from NTRIP Caster.
Connection in progress The NTRIP Client is in the process of connecting to the NTRIP Caster.
Unknown Ntrip Status The status is not one of those listed above.

Enable – Select to enable NTRIP Client.

IBSS Mode – Checking this mode provides a simplified interface for IBSS:

  • TCC Organization – Enter the TCC Organization name.
  • TCC Device ID – The Device ID is generated by the receiver.
  • TCC Password – Enter the TCC password provided by your Organization's TCC administrator.
  • Base Name – Enter the name of the base station preferred as the source of your corrections if known, or select from the list using the Get Base Name list button.
  • Get Base Name List – Use this button to obtain a list of available IBSS base stations for selection. The list is ordered with the closest at the top of the list and includes the distance from your current location in km.

NTRIP Caster HTTP:// – The address and port of the NTRIP Caster that the receiver will connect to in order to receive correction data.

Enable SSL/TLS – Select this check box to enable the SSL or TLS protocol. This check box is for either IBSS or regular NTRIP connections.

Authenticate NTRIP Caster – This check box appears if the Enable SSL/TLS check box is selected. It uses a hard-coded CA certificate. (Not present for non-IBSS NTRIP.)

User Name – Enter the username required to log on to the server.

Password – Enter the password required to log on to the server.

Verify Password – Re-enter the password required to log on to the server.

Mount Point – Enter name of the correction stream to which you are connecting on the NTRIP Caster if known, or select from the list using the Get Mount Points button.

Get Mount Points – Use this button to obtain a list of available IBSS base stations for selection. The list is ordered with the closest at the top of the list and includes the distance from the receiver's current position in km.

Glossary of terms

IBSS/NTRIP Server

This option enables the receiver to connect to IBSS or an NTRIP Caster to send correction data securely across the internet.

Status – Indicates the current status of the NTRIP connection:

Status Meaning
Init NTRIP Server disabled.
Up and Connected NTRIP Server is connected to an NTRIP Caster and sending correction data.
Invalid Mountpoint NTRIP error 404 returned from NTRIP Caster.
Invalid Username or Password NTRIP error 401 returned from NTRIP Caster.
Failed to connect to remote NTRIP Caster Connection failed due to an Internet-related issue.
No GNSS data from Caster NTRIP error 503 returned from NTRIP Caster. No data available from the NTRIP Caster.
Unexpected internal error NTRIP Caster internal error.
Incorrect NTRIP Caster response NTRIP error 602 returned from NTRIP Caster.
Rejected by remote Caster due to mount point in use NTRIP error 603 returned from NTRIP Caster.
No output stream is configured NTRIP error 604 returned from NTRIP Caster.
Connection in progress The NTRIP Server is in the process of connecting to the NTRIP Caster.
Unknown Ntrip Status The status is not one of those listed above.

Enable – Select this check box to enable NTRIP Server.

NTRIP Version – NTRIP Server supports either NTRIP version 1 or 2.

NTRIP Caster http:// – The address and port of the NTRIP Caster that the receiver will connect to in order to send or receive data.

Enable SSL/TLS – Select this check box to enable the SSL or TLS protocol. This check box is for either IBSS or regular NTRIP connections.

Mount Point – The name of the correction stream the receiver is supplying to the NTRIP Caster.

Username – Enter the username required to log on to the server.

Password – Enter the password required to log on to the server.

Verify Password – Re-enter the password required to log on to the server.

Identifier – The unique identifier for the receiver (NTRIP Server) supplying the correction stream.

Country – An optional identifier to help distinguish which country the NTRIP Server is in.

Network – An optional identifier to help distinguish which network the NTRIP Server is a part of.

Select the correction type to output:

Glossary of terms

NTRIP Caster

There are three NTRIP Caster ports available. For each port, a maximum of 10 users can request data, which means that a total of 30 users can simultaneously request data.

Enable – Select this check box to enable this NTRIP Caster port.

Port – Source Port number of the caster host.

Enable SSL/TLS – Select this check box to enable the SSL or TLS protocol.

Identifier – The unique identifier for the NTRIP Caster.

Country – Enter the character country code, for example USA, DE.

Mount Point – Enter the name of the output stream, such as its type. Users must enter this name to connect to the port.

Authentication – This is set to Basic so you will require a login username and password.

Generator – Set to Trimble.

Fee – Set to no fee per connection. There is no billing model in this receiver.

NMEA Required – Set to No as this is a single base solution.

Mount Point – Enter the name of the receiver, such as its location. This name is required by the users.

Select one source of corrections:

When the factory defaults are applied the three NTRIP Caster ports will be automatically configured to output CMRx on port 2101, CMR on port 2102 and RTCMv2.1 on port 2103.

Glossary of terms

Serial 1-4

Serial Port Setup – Set the appropriate baud rate, parity, and flow control for the port.

One of the following groups appears, depending on the option that you select in the drop-down list at the top of the page:

Bluetooth Port

You can stream any available data over a Bluetooth connection.

Maintain configuration when connection dropped – Select this for the receiver to maintain the output configuration on the selected Bluetooth port when the wireless link is dropped. The output resumes when the wireless link is re-established.

One of the following groups appears, depending on the option that you select in the drop-down list at the top of the page:

USB

USB Port – Data can be streamed over an available USB connection.

Depending on the option selected in the drop-down list at the top of the page, the options for configuration changes:

CMR

The following fields appear when CMR is selected from the list at the top of the page.

CMR – Select which CMR corrections will be output on this port. If transmitting CMRx messages, ensure that all rovers and machines have firmware that will accept CMRx. CMRx was introduced in receiver firmware version 4.0.

Delay – Select the time delay for the CMR output. This is used in multi-base applications.

REPEAT-RTCM

This feature allows an external source of RTCM corrections to be repeated to another port. The external source can be OmniSTAR VBS (if installed).

The following fields appear when you select REPEAT-RTCM from the list at the top of the page.

Use VBS as source – Select this check box to use the decoded OmniSTAR VBS service to populate an RTCM DGPS correction stream. The RTCM DGPS correction stream can be output on Ethernet, Serial, or USB ports. This output is available when the receiver is in any operating mode and can also be selected from the front panel Port menu. Only available when a valid OmniSTAR VBS subscription is loaded in receiver that supports OmniSTAR.

RTCM

The following fields appear when you select RTCM from the list at the top of the page.

Enable/Disable – Select if RTCM output is to be enabled on this port.

Version – Select which version of RTCM message will be output on this port. (Use version 2.X to transmit a version of RTCM that is compatible when multiple rovers are being used and they are not all compatible with the same version of RTCM message. That is, one rover might only support version 2.1 and the other requires version 2.3.)

RTCM version 3 is available when the base station is used by a mixed fleet of RTK receivers from a number of manufacturers. RTCM version 3 is more efficient, handles GLONASS, and is more suitable for networked RTK than version 2.x. If the GLONASS option is installed in the base station (receiver firmware version 4.13 and later), then both GPS and GLONASS measurements are output.

 

<<For SPS receivers, does this also apply to Alloy? >>

RTCM 3.2 introduces RTCM Multiple Signal Message (MSM) correction messages. RTCM 3.2 MSM format is available when a base station mode is loaded in an SPS GNSS receiver. It is shown as RTCM 3.2 in the SPS GNSS receiver web interface. Until now the RTCM v3.x messages had the following issues:

  • They are not compact like the Trimble CMRx message structure
  • They were variable in message size, which caused challenges with data radios
  • They did not include the QZS, BeiDou, or Galileo constellations

RTCM 3.2 MSM is more compact, more uniform in message size, and allows for the newer constellations when compared to the RTCM v3.x messages.

Note that the Trimble proprietary CMRx messages still use 30% less bandwidth than RTCM MSM.

If your receiver has the Advanced RTCM option code loaded, this extra web menu is visible when the RTCMv3.2 (MSM) transmit option is selected:

Bandwidth limit – This option is available once RTCM version 3 is selected. If the radio link used has a known maximum data throughput rate, then enter that value into this field in bytes per second. The receiver will then logically reduce the number of satellite messages so that maximum rate is not exceeded.

Type – Select which type of RTCM message will be output on this port.

NMEA

The following fields appear when NMEA is selected from the list at the top of the page.

NMEA Messages – Select which NMEA messages will be output on this port.

Standard – Select which standard to use for the compliant messages.

  • NMEA – Output messages comply the National Marine Electronics Association (NMEA) 0183 Standard for Interfacing Marine Electronic Devices, Version 4.0, November 1, 2008. This is the default selection.
  • IEC61162-1:2010/NMEA 0183 V4.10 – Output messages will comply with the International Electrotechnical Commission (IEC) 61162-1, Edition 4 2010-11.

Variations from standard

Report max DQI=2 NMEA GGA string – When enabled, the Quality Indicator field in the GGA output message will never be greater than 2 (Differential GPS). Use this only with legacy systems that do not fully support the NMEA standard.

Report max correction age 9 sec in NMEA GGA string – When enabled, the Age of differential data field in the GGA message will never be greater than 9 sec. Use this only with legacy systems that do not fully support the NMEA standard.

Report extended information in NMEA GGA and RMC strings – By default, this check box is enabled to provide high precision position data in the NMEA messages. Clear this check box to conform to the NMEA standard message length of 82 characters.

Report GST message always as GPGST – When enabled, the NMEA talker ID will always be $GP for the GST message no matter what constellation is being tracked. This is required for some legacy systems using this NMEA output which have not yet been updated to follow the NMEA standard. By default this will be disabled.

Report legacy talker ID – When enabled, this forces the following sentences to always use “GP” as the talker ID: GGA, MSS, DTM, GLL, HDT, RMC, ROT, VTG, and ZDA.

RT17/RT27

The RT17/RT27 option is only available when the Binary Outputs option is installed in the receiver.

The following fields appear when RT17/RT27 is selected from the list at the top of the page.

Epoch Interval – This defines the rate at which the RT17/RT27 messages are output. Check boxes are provided to enable the output of measurements and/or positions.

Measurements – Select this check box to output raw observables.

Positions – Select this check box to output position measurements.

Concise – Select this check box to output a more compact message containing the raw observables. This should always be enabled.

R-T Flag – Select this check box to output IODE values and cycle-slip counts.

Ephemeris – Select this check box to output the satellite ephemeris when received.

Send Raw GPS Data – Select this check box to output the raw data extracted from the satellites.

Multi-System Support – Select this check box to output the GPS L5 and GLONASS observables.

Smooth Pseudorange – Enable Pseudorange smoothing.

Smooth Phase – Enable Phase smoothing.

Send Raw WAAS Data – Select this box to output the raw data extracted from the SBAS satellites.

BINEX

The following fields appear when you select BINEX from the list at the top of the page.

Observable Rate – Select the output rate for the raw observables.

Smooth Pseudorange – Enable Pseudorange smoothing.

Smooth Phase – Enable Phase smoothing.

GSOF

The following fields appear when you select GSOF (General Survey Output Format) message from the list at the top of the page.

GSOF Messages – Select which GSOF messages will be output on this port.

OmniSTAR

Only available when a valid OmniSTAR subscription is loaded in a receiver that supports OmniSTAR.

DATA for OmniSTAR – Enables the demodulated OmniSTAR data output on this port. This output can then be used as an External OmniSTAR input on a non-Trimble OmniSTAR-capable receiver that has a valid and appropriate OmniSTAR subscription.

DATA for Trimble – Enables the demodulated OmniSTAR data output on this port. This output is the same raw data as above with a TRIMCOMM wrapper (0xC4) to support use as an External OmniSTAR input on a Trimble receiver. The receiver must have a valid and appropriate OmniSTAR subscription.

DEBUG – Enables/Disables DEBUG OmniSTAR output on this port.

1PPS Time Tag

The following fields appear when you select 1PPS Time Tag from the list at the top of the page.

1PPS Time Tag – Enables the ASCII Time tags. The time tag provides the UTC time of the 1PPS pulse and is output approximately 800 milliseconds before the pulse.

To enable the 1PPS pulse, see Receiver Configuration - General.

Met-Tilt

This setting is used to support meteorological and tilt sensors. This option is available only with serial ports. It allows up to six different fields that allow serial poll type commands to be sent to MET or TILT sensors. The responses are recorded in the receiver's internal memory. If a RINEX file is generated from the associated T02 file, the appropriate and associated *.met and/or *.05m files will be generated.

Serial port 2, when set to MET-TILT, has a power output option that can supply up to 3.6 W @12 V DC from pin 9 of serial port 2.

They are not used in Construction applications.