GPS client mode

Since some time, a lot of peplink products already allow to act as a GPS server, using & serving NMEA messages collected from the internal GPS chip.

In our usecase however, the Pepwave unit is inside a moving ship, with our own equipment being mounted outdoors (which also has the ability to act as a GPS server using TCP)

In this case, it would be very nice to configure the Pepwave device to not get it’s GPS input from the on-board receiver, but from another TCP source.


  • Today, the only GPS source is the unit’s internal GPS chip
  • Allow to specifiy another source to fetch GPS NMEA data. (TCP, specifying IP + Port)
  • Still allow to locally acts as a GPS server by forwarding/converting the received sentences

Kind Regards,



Are you looking for GPS Forwarding? If so, below is the tips and tricks.

1 Like


The request is for the pepwave unit itself to get GPS data from another

Thus, NOT using the internal GPS chip as primary source.


1 Like

There is another case for this feature:

We now use a Balancer 210, which is installed on a ship.
Currently, it is only possible to set a fixed position for this model as it does not contain GPS hardware.
When the ship is sailing out … the position is not correct anymore.

It would be very very nice if this unit would have the option to fetch NMEA sentences from a remote device

Some basic menu structure that would be compatible for all peplink products:

  • Set GPS coordinates fixed (default for products lacking GPS hardware internally)
  • Use internal GPS hardware to fetch current location (Default for most products)
  • Fetch GPS coordinates (NMEA sentences) from following server (TCP):
    –> IP:Port

When the device makes a TCP connection, the server starts sending NMEA sentences over the socket, which the device decodes and uses.
When the Pepwave device closes the socket, the server is notified automatically and stops sending.


This is similar to the case pointed out by our Rural Fire Services in New South Wales customer.
HD4 is installed in a helicopter and used to stream video back to the base 380 via speedfusion tunnel.
This project is working really fine.
HD4 is just using the existing LTE antenna setup on this vehicle.
and because it’s a very difficult process and expensive exercise to setup new antenna system for the GPS, i.e. making holes in the helicopter, the builtin GPS modem of HD4 was not used.

However, there’s already a GPSD server running on the Computer connected to the HD4 in the helicopter. It has all the NEMA GPS data it is receiving from the aircraft GPS system. Instead of installing another antenna for the Peplink is there a way that the Peplink can connect to and received GPS data from a GPSD server via the LAN.

1 Like

any updates on this?


Please and update on this would be much appreciated?

1 Like

Hello @TK_Liew, do you have any updates on this please?

or is there some API’s we could call or is there a SDK we could use?

1 Like

Bringing this back up…

Our onboard navigation software can repeat NMEA data sentences across the network. If the Pepwave router could accept this (highly accurate) data, it would eliminate the need to run an additional GPS antenna or at least provide redundancy. Maybe it could even support vessel heading data (HDT)? Also, we would like to display knots instead of mph on the tracking map, if possible.

1 Like

Any update on this from the peplink team?
Even when it’s a nack.


@Koen_Vandeputte @rocknolds @markwiggs ,

Engineering team is considering the request. The most challenge part is that there are too many GPS source devices running in the market that we have no ways to restrict the methods & format.

As for now , Engineering team is considering to accepting “Raw NMEA 0183 Network Steam UDP/TCP” as the GPS source input . In-order words, if your GPS receiver device able to forward GPS stream using the mentioned method then it can be work as the GPS input for the device. Tentatively this have been scheduled for firmware 8.2.0 or above.

1 Like