TCP/IP based setup having issues

Reach Module / M+ / M2 RTK / PPK configuration
1

I have begin to play with reachRTK kit, current setup as following (RFD900+ radios are off-the-shelf but will use them after finishing with network tests) but having problems as detailed below :

  • Modem/AP IP : 192.168.1.1
  • Rover : 192.168.1.211
  • Base : 192.168.1.176
  • Reach Image : v1.2
  • ReachView : v0.4.9

I setup Base with the following parameters :

output path for corrections : tcpsvr
port : 9000
output format : rtcm3
rtcm3 messages for output : 1002,1006,1010,1019
base latitude : 0 (wanted to give zero for tests because exact coordinates are unknown)
base longitude : 0 (wanted to give zero for tests because exact coordinates are unknown)
base height : 10 (wanted to give ten for tests because exact height is unknown)
option : GPS_1Hz.cmd

saved and started, there is nothing appearing on status screen, mode says base and status says started, nothing else.

and Rover configured as following :

positioning mode : kinematic
used positioning systems : gps,sbas,glo,gal
dynamics model of the rover (kinematic and dgps only) : off
u-blox configuration file : GPS_1Hz
input source for base corrections : tcpcli
ip : 192.168.1.176
port : 9000
input format for base corrections : rtcm3
solution 1 output path : tcpsvr
port : 9001
solution 1 output format : nmea
solution 2 output path : bluetooth
solution 2 output format : nmea
raw data log for onboard receiver : off
raw data log for base corrections : off
base antenna coordinates : rtcm

the rest of settings are defaults (never changed anything in advanced menu), saved and started, the idea is to have nmea data both on tcp and bluetooth to test with different connections. on status screen i see mode : kinematic, status : single, lat and lon and height gives coordinates and height but they are not fixed with some value. also notice yellow, red and green bars with grey bars close to them, which i understand that they are from base station. waited for a long time to get fix but nothing changes.

my question is whether above settings are correct for communicating between a LAN ? And do i need to expect some coordinates on status screen of base station ?

2

use gps coordinatis (lat long height) from gmaps more or less precise (you’re not gonna get anything that makes sence otherwise)
your input source of base corrections should be
IP:192.168.1.211
also use gps and glonass on rover and base for better results;

3

Input source of base corrections should be 192.168.1.211 ? Can you please explain, my base IP is 192.168.1.176, i am having NMEA output from rover which IP is 192.168.1.211

Untitled.png1351×683 29.7 KB

And there is not setting for setting GPS and GLONASS for base setup :frowning:

4

recheck your first post for base and rover IP’s;
do you see your base’s grey bars on your rover?

5

sorry i corrected it right now, do not have a good reception (used some metal plates instead of ground plane), but as attached :

Untitled.png1361×373 12.3 KB

6

ground plane needs to be directly under your antenna…best way is to attach your antenna in the center of a ground plane (10x10cm), make a hole for the cable; reflections occur if you place ground plate too low under your antenna;
what gps antenna(s) do you use? (your signal is not optimal - related to your antenna and ground plane)
ground plane has to be rf-refleflective - no matter how thick (aluminium, copper, …)
edit: also use gps configuration file gps and glonass 5hz - for base and rover !

1 Like