GPS @ 10hz only outputting @ 1Hz

Reach Module / M+ / M2 Getting started
1

Question, I’ve set the Reach M+ to 10hz GPS only (Rover) in the Reach View software, however the NMEA sentences output are only arrving at 1 Hz through the serial port?

I’ve used loads of expensive RTK systems in the past and never had an issue.

Can anyone tell me how to get 10Hz positional information out of the Reach M+ in Rover Mode?

1 Like
3

Hi @carl,

Could you please share the Simple System report from your Reach device?

4
Simple system report 
app version: 2.16.2-r0
'wifi_status, interface: wlan0':
- wifi_mode: infrastructure
- ip: 192.168.0.42
  is_added: true
  is_connected: true
  is_visible: false
  mac_address: CC:B8:A8:F4:EF:38
  security: wpa-psk
  ssid: SKYA58EB
  uuid: d325c979-38fe-40d4-9fd0-a9bc14391fdf
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: true
    format: rtcm3
    path: tcpsvr://:9000#rtcm3
    type: tcpsvr
  rtcm3 messages:
    '1002':
      enabled: true
      frequency: '1'
    '1006':
      enabled: true
      frequency: '0.1'
    '1010':
      enabled: true
      frequency: '1'
    '1097':
      enabled: false
      frequency: '1'
    '1107':
      enabled: false
      frequency: '1'
    '1117':
      enabled: false
      frequency: '1'
    '1127':
      enabled: false
      frequency: '1'
bluetooth:
  discoverable: false
  enabled: false
  pin: '***'
camera:
  duty cycle: 20
  enable: false
  period: 2
  polarity: true
correction input:
  input2:
    enabled: true
    format: rtcm3
    path: ttyMFD2:38400:8:n:1:off
    send position to base: single
    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: 24
  overwrite: true
  raw:
    format: UBX
    started: true
    version: null
  solution:
    format: LLH
    started: true
    version: null
lora:
  air rate: 2.6000000000000001
  frequency: 868000
  output power: 20
position output:
  output1:
    enabled: true
    format: nmea
    path: ttyGS0:115200:8:n:1:off
    type: serial
  output2:
    enabled: true
    format: nmea
    path: ttyMFD2:115200:8:n:1:off
    type: serial
  output3:
    enabled: true
    format: llh
    path: :2014
    type: tcpsvr
  output4:
    enabled: true
    format: llh_ext
    path: :2015
    type: tcpsvr
rtk settings:
  elevation mask angle: '15'
  glonass ar mode: 'off'
  gps ar mode: fix-and-hold
  max horizontal acceleration: '10'
  max vertical acceleration: '10'
  positioning mode: kinematic
  positioning systems:
    compass: false
    galileo: false
    glonass: false
    gps: true
    qzss: false
    sbas: false
  snr mask: '35'
  update rate: '10'
5

@carl,

What was the solution status when you’ve tested NMEA output?

6

There wasn’t one as we were just testing the setup indoors.

Usually you still get the NMEA sentenses at the reqired frequency (10hz) from the ublox M8.

We were getting these at 1 Hz:

$GPGSA,A,1,*1E
$GPGSV,1,1,0,*49
$GNGST,*65
$GNVTG,*60

Thanks

Carl…

1 Like
7

Hi @carl,

Reach should get at least Single solution to output NMEA with a higher update rate.

8

These are from the Reach but at 1Hz only?

$GPGSA,A,1,*1E
$GPGSV,1,1,0,*49
$GNGST,*65
$GNVTG,*60

9

Maybe test it outdoors to see what you get?

Let us know how it goes!

1 Like
10

@carl,

Please test it outdoors as @timd1971 suggested.
If Reach has no solution status, it outputs the NMEA string with 1 Hz frequency independently of which update rate you specified in ReachView.

1 Like
11

ok thanks…

1 Like
13

Did it report higher Hz after doing so? Thanks!

14

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