How to create static points

Reach RS / RS+ Getting started
1

how to create static points, I am from chile greetings, this has been a chaos

2

Place the rover rod over your point, ensure you have static rtk settings enabled, wait for fix, read your value or start a survey and get an average value over time.

3

what are the static rtk settings

6

It always helps to read the fine manual :wink:

https://docs.emlid.com/reach/common/reachview/rtk-settings/

1 Like
7

Static - an assumption is made that Reach is static. Constraining the system helps to resolve ambiguities faster as well as produce measurements with higher precision.

from a reference station which of these two would serve me?

Fix-and-hold: after first ambiguity fix hold them constrained. Fix is more stable, but in case first initialization was not correct it will take longer to recover and initialize correctly. You can think of it as if Fix had inertia.

Continuous: ambiguities are resolved epoch by epoch. Less stable, but no risk of holding a false fix.
In real-life conditions on moving platform Fix-and-hold provides better overall performance.

8

Hi @jeraldoproyectos,

Do you want to collect a point in RTK or post-process raw data from Reach to get point coordinates?

9

to carry out a post process later

10

@jeraldoproyectos

May I ask you to share your Reach Simple system report? I can check it to make sure your configurations are appropriate.

11

details=“Simple system report”]

app version: 2.16.1-r0
'wifi_status, interface: wlan0':
- wifi_mode: ap
- access_point:
    band: bg
    channel: 1
    password: null
  ip: 192.168.42.1
  is_added: true
  is_connected: true
  mac_address: 8C:F7:10:18:32:E0
  security: wpa-psk
  ssid: Base_:D3:3A
  uuid: e535f3e0-c489-4dad-be79-369b02ee2b69
base mode:
  base coordinates:
    accumulation: '5'
    antenna offset:
      east: '0'
      north: '0'
      up: '1.11'
    coordinates:
    - '-19.9944838494'
    - '-69.7715816429'
    - '1145.208'
    format: llh
    mode: manual
  output:
    enabled: true
    format: rtcm3
    path: lora
    type: lora
  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: true
      frequency: '1'
    '1107':
      enabled: false
      frequency: '1'
    '1117':
      enabled: false
      frequency: '1'
    '1127':
      enabled: false
      frequency: '1'
    gps:
      enabled: false
      frequency: '1'
    qzss:
      enabled: false
      frequency: '1'
bluetooth:
  discoverable: true
  enabled: true
  pin: '***'
correction input:
  input2:
    enabled: true
    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: false
    version: null
  correction:
    format: RTCM3
    started: true
    version: null
  interval: 24
  overwrite: true
  raw:
    format: RINEX
    started: false
    version: '3.03'
  solution:
    format: XYZ
    started: false
    version: null
lora:
  air rate: '9.11'
  frequency: 900000
  output power: '12'
position output:
  output1:
    enabled: false
    format: nmea
    path: bluetooth
    type: bluetooth
  output2:
    enabled: false
    format: llh
    path: :9001
    type: tcpsvr
  output3:
    enabled: true
    format: xyz
    path: :2014
    type: tcpsvr
  output4:
    enabled: true
    format: llh_ext
    path: :2015
    type: tcpsvr
rtk settings:
  elevation mask angle: '15'
  glonass ar mode: 'on'
  gps ar mode: fix-and-hold
  max horizontal acceleration: '1'
  max vertical acceleration: '1'
  positioning mode: static
  positioning systems:
    compass: false
    galileo: true
    glonass: true
    gps: true
    qzs: true
    qzss: true
    sbas: true
  snr mask: '35'
  update rate: '5'

[/details]

12

Hi @jeraldoproyectos,

Thanks! It looks fine.
I’ve noticed that you didn’t enable raw data logging. Don’t forget to turn it on before you start to collect the point.

So you need:

  1. Set up the unit on the point you want to collect;
  2. Enable raw data logging;
  3. Record log on this point;
  4. Export log from Reach on your laptop/PC;
  5. Get the log from the reference station;
  6. Post-process logs.
13

Thank you very much Tatiana.
the raw data of emlid can be transformed to rinex that can be used in another post-process program

14

@jeraldoproyectos,

Sure, you can convert raw data to RINEX using RTKConv and then use it in any software for post-processing.
You also can start raw data logging in RINEX format in ReachView.

1 Like