NTRIP trb142 issue

Networking Solutions Issue
1

Hi all,

I’m trying to get a serial rs232 NTRIP rtcm stream between Trimble AG372 and TRB142 . When I’m setting up the stream the status shows up but nothing happens. I started debugging by checking the wiring they are okey. Second I triple checked the receiver settings they are correct. Now I’m kind a lost. If I’m reading the link below this person is having the same issues. TRB 142 Ntrip geht nicht

So stream is up but does not make a serial connection. I have also checked all the baud rates possible. Link to receiver manual :

Hope it’s a software issue

3

Greetings, @Nldatn ,

Welcome to Teltonika Community!

Thank you for reaching out and for the detailed description. We can see you’re experiencing a situation where the NTRIP stream appears active, but no data is being forwarded to the Trimble AG372 over RS232 - this is a known symptom with a few likely causes. Please work through the steps below in order.

  1. Check for RS232 port conflicts

Only one service can use the RS232 port at a time. Go to Services → Serial Utilities and make sure no other instances (Over IP, Console, or Modem Control) are enabled. If any are active on RS232, they will silently block the NTRIP client.

  1. Verify cable type

The TRB142 RS232 port is DCE (female). To connect a DTE device like the Trimble AG372, you need a straight-through Female/Male cable - not a null-modem/crossover cable. Using the wrong cable type is a common cause of this exact symptom.

  1. Match serial parameters

Baud rate alone isn’t enough - all five parameters must match the AG372 spec exactly:
• Data bits (typically 8)
• Stop bits (typically 1)
• Parity (typically None)
• Flow control - check whether the AG372 requires RTS/CTS hardware handshaking, as the TRB142 defaults to None

  1. Run the NTRIP debug log (CLI)

This is the most direct diagnostic step. Access the CLI via SSH or WebUI (System → CLI) and run:

/etc/init.d/ntrip stop
ntrip_client -s 2 -D 9

If there’s no output, also try with -s 0. Please share the full output with us - it will show clearly whether the problem is on the caster side or the serial output side.

  1. Confirm firmware and NTRIP package

NTRIP is an optional package - confirm it’s installed and up to date via System → Package Manager. Also check your firmware version under System → Firmware. Several NTRIP-related bugs have been resolved in recent TRB1 firmware releases, so we recommend updating to the latest stable version if you haven’t already.

Once you’ve gone through these steps, please reply with the CLI debug output from Step 4 and let us know the outcome of the cable/port checks. That will allow us to investigate further.

Best regards,
V.

4

Hello

Since it still isn’t working for me either, I wanted to post my settings here again.

Point 1:

It worked with the old software using the RS232 adapters and the John Deere Starfire 6000.

Point 2:

The cable and RS232 adapter haven’t changed.

Point 3:

It’s configured correctly.

Point 4:

Device: TRB142

Kernel: 5.4.302

Firmware: TRB1_R_00.07.21.3

Build: 40729a45af5

Build date: 2026-03-20 11:48:48

--------------------------------------------------------

            \~ INTERNAL API USAGE \~

/sbin/api GET /system/device/status

/sbin/api POST /interfaces/config {…}

Docs: [https://developers.teltonika-networks.com](https://developers.teltonika-networks.com/)

--------------------------------------------------------

root@TRB142:~# /etc/init.d/ntrip stop

-ash: /etc/init.d/ntrip: not found

root@TRB142:~#

root@TRB142:~# ntrip_client -s 2 -D 9

NTRIP client starting

Using config section=2

Debug level set to 9

Getting uci configuration

Enabled:[0]

ntrip_port:[0]

close_on_no_data period:[0]

nmea_source:[-1]

lattitude:[0.000000]

longitude:[0.000000]

ltermios_read_settings failed: Failed to lookup ‘2’ uci section

Stop the service

root@TRB142:~# /etc/init.d/ntrip stop

-ash: /etc/init.d/ntrip: not found

root@TRB142:~#

root@TRB142:~# ntrip_client -s 0 -D 9

NTRIP client starting

Using config section=0

Debug level set to 9

Getting uci configuration

Enabled:[0]

ntrip_port:[0]

close_on_no_data period:[0]

nmea_source:[-1]

lattitude:[0.000000]

longitude:[0.000000]

ltermios_read_settings failed: Failed to lookup ‘0’ uci section

Stop the service

root@TRB142:~#

Point 5:

Firmware TRB1_R_00.07.21.3

Best Regards

5

Hey,

not sure if this is helpful to you, but im using the RUT956 modem.

it requires the AG-372 to send a GGA string.

with the RDI or Ag Remote, set the port you are using for the RS232 (Pins 6 & 8 RHS are Port C)

Set the 372, if connected to a CNH display, Toolbox > GPS Modem = other, scroll to the bottom and select manual port config or the display will reset the port used.

I RTCM 38400

O 8N1 NMEA 38400

NMEA out at 01 sec

Modem would need baud rate set the same, 38400