Cannot get FIX on Reach RS

Hi all,

We’re using a regular Reach as a base and a Reach RS as a rover in an open field within an urban environment, and can’t seem to get a consistent AR validation ratio above 3.

Playing with all of the RTK parameters seems like it would jump into FIX more often than it has before, but it still usually hangs around 1.5.

Satellite signal doesn’t seem to be an issue, as we’re consistently getting above 5 green bars on both the base and the rover. This is with the base on a tripod with a ground plane; our goal is to have this work in a rural environment in Turkey. Here are pictures of the setup.

We don’t have the resources to do post-processing while in the field, and need to ensure we can get fixed solutions before we leave this summer.

Here are the log files from our last attempt.
Raw UBX
Solution ERB
Base RTCM3

We don’t know what else to try. Any ideas?
Thank you!

Just looking quickly through your logs and photo i have couple things.

  1. by looking at the logs i can see alot of noise and rover is missing radiolink with base most of the time.
    The first part is to noisy to be used, which leaves us with the last 10-12min where you could get fix.
  2. I see powerlines above your rover, that means trouble and obstructions around at low angle. By adjusting mask angle to around 25 degree and using gps/glonass/galileo you should get fix. But use continuous and survey several times with some time apart to rule out bad fix.
    3.Watch your logs after a job if you had trouble, it tells you alot you can learn from and use next time around.
3 Likes

Something wrong with the correction link. Seems like it barely appeared during the log. Please provide two system reports and describe the way they are connected.

Here are my two system reports for the base and rover.

Base system report
app version: 2.11.0-r0
'wifi_status, interface: wlan0':
- Client state
- IP address: 192.168.43.221
  mac address: 90:b6:86:09:ce:17
  ssid: Roberts
base mode:
  base coordinates:
    accumulation: '3'
    antenna offset:
      east: '0'
      north: '0'
      up: '0'
    coordinates:
    - '0'
    - '0'
    - '0'
    format: llh
    mode: single-and-hold
  output:
    enabled: true
    format: rtcm3
    path: tcpsvr://:9000#rtcm3
    type: tcpsvr
  rtcm3 messages:
    '1002':
      enabled: true
      frequency: '1'
    '1006':
      enabled: true
      frequency: '0.1'
    '1008':
      enabled: true
      frequency: '1'
    '1010':
      enabled: true
      frequency: '1'
    '1019':
      enabled: true
      frequency: '1'
    '1020':
      enabled: true
      frequency: '1'
    '1097':
      enabled: true
      frequency: '1'
    '1107':
      enabled: true
      frequency: '1'
    '1117':
      enabled: true
      frequency: '1'
    '1127':
      enabled: true
      frequency: '1'
bluetooth:
  discoverable: true
  enabled: true
  pin: '***'
camera:
  duty cycle: 20
  enable: false
  period: 2
  polarity: true
correction input:
  input2:
    enabled: false
    format: rtcm3
    path: ttyMFD2:38400:8:n:1:off
    send position to base: 'off'
    type: serial
  input3:
    enabled: false
    format: rtcm3
    path: :9028
    type: tcpsvr
logging:
  base:
    format: RTCM3
    started: true
    version: null
  correction:
    format: RTCM3
    started: true
    version: null
  interval: 86400
  overwrite: true
  raw:
    format: UBX
    started: true
    version: null
  solution:
    format: ERB
    started: true
    version: null
position output:
  output1:
    enabled: true
    format: erb
    path: :9001
    type: tcpsvr
  output2:
    enabled: true
    format: llh
    path: :2013
    type: tcpsvr
  output3:
    enabled: true
    format: llh
    path: :2014
    type: tcpsvr
  output4:
    enabled: true
    format: llh
    path: :2015
    type: tcpsvr
rtk settings:
  elevation mask angle: '30'
  glonass ar mode: 'on'
  gps ar mode: continuous
  max horizontal acceleration: '1'
  max vertical acceleration: '1'
  positioning mode: single
  positioning systems:
    compass: false
    galileo: true
    glonass: true
    gps: true
    qzs: true
    qzss: true
    sbas: true
  snr mask: '40'
  update rate: '5'
Rover system report
app version: 2.11.0-r0
'wifi_status, interface: wlan0':
- Client state
- IP address: 192.168.43.162
  mac address: 90:b6:86:00:96:40
  ssid: Roberts
base mode:
  base coordinates:
    accumulation: '2'
    antenna offset:
      east: '0'
      north: '0'
      up: '0'
    coordinates:
    - '0'
    - '0'
    - '0'
    format: llh
    mode: single-and-hold
  output:
    enabled: false
    format: rtcm3
    path: tcpsvr://:9000#rtcm3
    type: tcpsvr
  rtcm3 messages:
    '1002':
      enabled: true
      frequency: '1'
    '1006':
      enabled: true
      frequency: '0.1'
    '1008':
      enabled: false
      frequency: '1'
    '1010':
      enabled: true
      frequency: '1'
    '1019':
      enabled: false
      frequency: '1'
    '1020':
      enabled: false
      frequency: '1'
    '1097':
      enabled: false
      frequency: '1'
    '1107':
      enabled: false
      frequency: '1'
    '1117':
      enabled: false
      frequency: '1'
    '1127':
      enabled: false
      frequency: '1'
bluetooth:
  discoverable: true
  enabled: true
  pin: '***'
correction input:
  input2:
    enabled: true
    format: rtcm3
    path: 192.168.43.221:9000
    send position to base: 'off'
    type: tcpcli
  input3:
    enabled: false
    format: rtcm3
    path: :9028
    type: tcpsvr
logging:
  base:
    format: RTCM3
    started: true
    version: null
  correction:
    format: RTCM3
    started: true
    version: null
  interval: 86400
  overwrite: true
  raw:
    format: UBX
    started: true
    version: null
  solution:
    format: ERB
    started: true
    version: null
lora:
  air rate: 2.6000000000000001
  frequency: 868000
  output power: 20
position output:
  output1:
    enabled: true
    format: llh
    path: :9001
    type: tcpsvr
  output2:
    enabled: true
    format: llh
    path: :2013
    type: tcpsvr
  output3:
    enabled: true
    format: llh
    path: :2014
    type: tcpsvr
  output4:
    enabled: true
    format: llh
    path: :2015
    type: tcpsvr
rtk settings:
  elevation mask angle: '30'
  glonass ar mode: 'on'
  gps ar mode: continuous
  max horizontal acceleration: '1'
  max vertical acceleration: '1'
  positioning mode: kinematic
  positioning systems:
    compass: false
    galileo: true
    glonass: true
    gps: true
    qzs: true
    qzss: true
    sbas: true
  snr mask: '40'
  update rate: '5'

We use a mobile hotspot on a phone and connect both the rover and the base to the hotspot. For the base we output corrections using TCP on port 9000, and then for the rover we listen on the same port with the base’s local IP address.

We’ve also used the same setup on different wifi networks from different devices with the same results, usually the AR validation ratio hangs at ~1.5.

From the settings I can only see that the elevation mask is a little too high. In general, more information is better, even if it’s “low quality”. I would suggest trying in a better environment first. First times setting RTK up are often hit and miss. Once you find your workflow, you can start experimenting with worse conditions.

1 Like

This topic was automatically closed 100 days after the last reply. New replies are no longer allowed.