ReachView v2.18.1

News
#7

@agrimgalina

Hope this stable release helps you with some of your prior difficulties. ; ) (you can be the official Emlid designated Guinea pig!) : )

1 Like
#8

Ha sorry !!!

1 Like
#9

Emlid rocks! I second @timd1971 your hard work is truly appreciated! I will start updating my units (two reach rs+ and two reach m+ :grin:) They do not have names yet…

2 Likes
#10

Name suggestions? These Jack "A"s?

Joe, Sal, Q & MURR? :stuck_out_tongue_closed_eyes:

https://www.trutv.com/shows/impractical-jokers/index.html

2 Likes
#12

I’ll report back after the updates… :joy:

#13

8 posts were split to a new topic: Can’t connect to Wi-Fi

#14

9 posts were split to a new topic: Not getting fix with the latest v2.18.0

#15

@andrew.yushkevich @tatiana.andreeva @egor.fedorov
Congratulations EMLID the application is incredible, in NTRIP in 10 seconds fixed without problem, I see that now in ANDROID devices when deploying the keyboard the function to record is up and you do not have to close the keyboard.
congratulations and more congratulations
Luis

6 Likes
#16

I have done a dozen comparative tests 2.16.2 and 2.18.0 and I confirm that the problem that I reported in versions 2.17.x DEV was resolved.
The test was carried out by two receivers, thanks to which the results can be compared under the same external conditions in different locations.

IMG_20190601_204400
IMG_20190601_204400.jpg3120×4160 2.1 MB

9 Likes
#17

A post was split to a new topic: RV 2.18 with 3DR radios

#19

A post was split to a new topic: Rndis RV v2.18

#22

3 posts were split to a new topic: Incorrect password after update to v2.18.1

#26

A post was split to a new topic: Can disable Base mode tab on v2.18.1

#29

I have a (bvery old) ReachRS which is not updating to v2.18.1, but stays at v2.18.0
Is this the expected behavior?

And more generally: what’s the future plan on different version for RS and RS2? Will RS only be updated as soon as new features relevant to both devices are added?

1 Like
#30

Hi Johannes,

Could you please post the screenshot demonstrating the behavior and the Simple System Report from the unit?

All Reach devices will have the same firmware version. The future firmware updates should be released for all Reach models.

2 Likes
#31
Simple system report 
app version: 2.18.0-r0
'wifi_status, interface: wlan0':
- wifi_mode: wpa_supplicant
- ip: 192.168.178.23
  is_connected: true
  mac_address: 90:b6:86:05:77:2d
  ssid: WannaBeImpact2
base mode:
  base coordinates:
    accumulation: '0.3'
    antenna offset:
      east: '0'
      north: '0'
      up: '0.5'
    coordinates:
    - '52.3641923783'
    - '4.87147226459'
    - '51.4'
    format: llh
    mode: manual
  output:
    enabled: true
    format: rtcm3
    path: ntrips://:BETATEST@rtk2go.com:2101/villagename#rtcm3
    type: ntrips
  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: '0.1'
    '1020':
      enabled: false
      frequency: '0.1'
    '1097':
      enabled: true
      frequency: '0.1'
    '1107':
      enabled: false
      frequency: '5'
    '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: jeberenz:***@euref-ip.net:2101/IJMU00NLD0
    send position to base: 'off'
    type: ntripcli
  input3:
    enabled: false
    format: rtcm3
    path: :9028
    type: tcpsvr
logging:
  base:
    format: RTCM3
    started: false
    version: null
  correction:
    format: RTCM3
    started: false
    version: null
  interval: 24
  overwrite: true
  raw:
    format: RINEX
    started: false
    version: '3.03'
  solution:
    format: LLH
    started: false
    version: null
lora:
  air rate: '9.11'
  frequency: 868000
  output power: '20'
position output:
  output1:
    enabled: true
    format: nmea
    path: :7050
    type: tcpsvr
  output2:
    enabled: false
    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: '15'
  glonass ar mode: 'on'
  gps ar mode: fix-and-hold
  max horizontal acceleration: '0.8'
  max vertical acceleration: '0.8'
  positioning mode: kinematic
  positioning systems:
    compass: false
    galileo: true
    glonass: true
    gps: true
    qzs: true
    qzss: true
    sbas: true
  snr mask: '30'
  update rate: '5'

0
Screenshot firmaware 2.18.0.png396×680 15.4 KB

#32

Hi Johannes,

Sorry for the delayed reply.

Have you already tried using another Wi-Fi network (for example, you phone hotspot) to update the device?

May I ask you to send me the Full System report in PM so I can check if your unit is connected to the Internet?

#33

Dear Tatiana, no I did not.
I just used our office wifi. The RS2 did update through the same network at that time though.
I’m traveling now (showcasing our system + RS2 in Westafrica :slight_smile: ), so I will send a report when I’m back.

1 Like
#34

Hi Johannes,

Keep us posted. :slightly_smiling_face:

#35