Ethernet
The Ethernet interface offers a 100 MBit port for connection to a network, router or laptop/computer. The interface offers a Web UI, as well as 4 (four) configurable data ports. Each Data Port
- can be configured as a TCP Server, TCP Client or a UDP Client as detailed in Ethernet Modes
- can be configured with an Input and/or Output for a number of protocols as detailed in Ethernet Data Port Functions.
- should only be used to establish a connection with a single remote computer/device at any one time.
Ethernet Modes
| Ethernet Mode | Description | Required Configuration |
|---|---|---|
| TCP Server | Certus will establish a TCP Server listening on the defined port. A connected client is able to receive Output data and send Input data based on the defined Input and Output functions. |
Port |
| TCP Client | Certus will continuously attempt to establish a TCP connection to the defined Destination IP and Port. Once established, a connected client is able to receive Output data and send Input data based on the defined Input and Output functions. |
Client Destination IP address Port |
| UDP Client | Certus will send UDP Output data to the defined Destination IP and Port. A client can also send UDP Input data to Certus this same Port. |
Client Destination IP address Port |
Ethernet Data Port Modes
Ethernet Functions
NMEA Input
| Description: |
This function accepts external data in the NMEA 0183 format. Advanced Navigation recommends against using NMEA 0183 input wherever possible due to the inefficiency, low accuracy and precision and weak error checking of the format. All NMEA messages received must have a valid checksum. Supported messages are listed below. The recommended combination of messages are GPGGA, GPVTG and GPZDA with optional messages GPGSV and GPGSA.
Supported NMEA messages |
Novatel GNSS Input
| Description: |
This function is designed for interfacing Certus with a Novatel GNSS receiver. It accepts data in the Novatel binary format and requires messages BESTPOS and BESTVEL at rates higher than 1 Hz (20Hz recommended). The message BESTSATS is optional to display detailed satellite information. The message HEADING is also supported for ALIGN capable receivers. |
Topcon GNSS Input
| Description: |
This function is designed for interfacing Certus with a Topcon GNSS receiver. It accepts data in the GRIL TPS binary format and expects messages PG and VG at rates higher than 1 Hz. |
ANPP Input
| Description: |
This function accepts data in the ANPP format as specified in Advanced Navigation Packet Protocol. |
RTCM Differential GNSS Corrections Input
| Description: |
This function accepts RTCM v3 GNSS corrections messages. This allows for Differential GNSS or RTK with the Certus internal GNSS receiver. |
Trimble GNSS Input
| Description: |
This function is designed for interfacing Certus with an external Trimble GNSS receiver. It accepts data in the Trimble binary format GSOF and expects packet 0x40 with records 1, 2, 8, and 12 at rates higher than 1Hz (20Hz recommended) and optional records 9 and 34 at 1 to 2Hz. |
u-blox GNSS Input
| Description: |
This function is designed for interfacing Certus with an external u-blox GNSS receiver. It accepts data in the u-blox binary format and expects message NAV-PVT at rates higher than 1Hz. |
Hemisphere GNSS Input
| Description: |
This function is designed for interfacing Certus with an external Hemisphere GNSS receiver. It accepts data in the Hemisphere binary format and expects message Bin1 at rates higher than 1Hz. For Hemisphere receivers that provide heading using two antennas, NMEA should be used instead as the binary format does not allow for transmission of heading information. |
Teledyne DVL Input
| Description: |
This function accepts DVL data from a Teledyne DVL. For assistance with configuration, contact Support. |
Tritech USBL Input
| Description: |
This function accepts USBL data from a Tritech USBL. For assistance with configuration, contact Support. |
Linkquest DVL Input
| Description: |
This function accepts DVL data from a Linkquest DVL. The DVL should be configured to output in NQ1 format. For assistance with configuration, contact Support. |
Nortek DVL Input
| Description: |
This function accepts DVL data in the Nortek DVL binary format. It accepts the packets 0x1B (DVL Bottom Track) and 0x1D (DVL Water Track). The recommended update rate is 8Hz. |
NMEA Output
| Description: |
This function outputs a configurable combination of the NMEA messages GPZDA, GPGGA, GPVTG, GPRMC, GPHDT, PASHR, GPROT, GPHEV, GPGSV, PFECGPAtt, and PFECGPHve at up to 50 Hz. The messages output and the output rate can be configured using the web UI or Certus Manager. An example output is shown below. $GPZDA,031644.460,07,05,2013,00,00*52 $GPGGA,031644.460,3352.3501851,S,15112.2355488,E,6,00,1.4,150.0,M,0.0,M,,*7E $GPVTG,089.19,T,089.19,M,000.00,N,000.00,K,E*27 $GPRMC,031644.460,A,3352.3501851,S,15112.2355488,E,0.0,89.2,070513,12.5,W,E*02 $GPHDT,89.2,T*06 $PASHR,031644.460,089.19,T,-00.01,-00.47,-00.00,,,,0,0*2E |
ANPP Output
| Description: |
This function outputs data in the ANPP format as specified in Advanced Navigation Packet Protocol. This function is for ANPP peripheral devices only. |
TSS1 Output
| Description: |
This function outputs the TSS1 format at a user configurable rate of up to 50 Hz. The output rate can be configured using the page in the web UI. |
Simrad 1000 Output
|
Description: |
This function outputs the Simrad 1000 format at a user configurable rate of up to 50 Hz. The output rate can be configured using the Data Ports page in the Using the Web User Interface. |
Simrad 3000 Output
|
Description: |
This function outputs the Simrad 3000 format at a user configurable rate up to 50 Hz. The output rate can be configured using the Data Ports page in the Using the Web User Interface. |
Serial Port Passthrough
| Description: |
This function allows passthrough communication through either GPIO 1 and 2 or the Auxiliary port. To transmit data use the Serial Port Passthrough Packet. When data is received it will be sent back using the same Serial Port Passthrough Packet. |