Same issues again today as 2 weeks ago:
Went out to a job… client wanted a georeferenced ortho of a future construction site. Had an incredibly hard time collecting my GCPs again. What happens a lot is that while waiting for a fix… everything just freezes and the bars disappear… with NTRIP correction data still on by the way. I get the notification that I have to make sure the RS has an unobstructed sky view, but I was on a bare terrain without any trees or buildings in a 200m radius. Only remedy is rebooting the RS… had to do that like 5 times or so, before I just gave up and went home. Last time, I kept going anyway and it took me an hour and a half and at least 15 reboots to collect just 8 GCPs… with one euro per minute in CORS costs. Completely unworkable like this and it costs me a lot of money. Anyone else seeing this?
Hello,
Thanks for the report. There is indeed something wrong. Could you start by submitting a system report(the simple one will suffice)?
Of course. How do I do that?
app version: 2.10.0-r0
’wifi_status, interface: wlan0’:
- Client state
- IP address: 192.168.43.41
mac address: fc:db:b3:98:9c:4d
ssid: AndroidAP
base mode:
base coordinates:
accumulation: '2’
antenna offset:
east: '0’
north: '0’
up: '0’
coordinates:- ‘0’
- ‘0’
- '0’
format: llh
mode: fix-and-hold
output:
enabled: false
format: rtcm3
path: tcpsvr://:9000#rtcm3
type: tcpsvr
rtcm3 messages:
‘1002’:
enabled: false
frequency: ‘1’
‘1006’:
enabled: false
frequency: ‘0.1’
‘1008’:
enabled: false
frequency: ‘1’
‘1010’:
enabled: false
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’
gps:
enabled: false
frequency: '1’
qzss:
enabled: false
frequency: '1’
bluetooth:
discoverable: false
enabled: false
pin: '***'
correction input:
input2:
enabled: false
format: rtcm3
path: eagledrone01:***@ntrip.06-gps.nl:2101/06GPSVRSGLO30
send position to base: single
type: ntripcli
input3:
enabled: false
format: rtcm3
path: :9028
type: tcpsvr
logging:
base:
format: RTCM3
started: true
version: null
correction:
format: RTCM3
started: false
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: false
format: nmea
path: bluetooth
type: bluetooth
output2:
enabled: true
format: llh
path: :2013
type: tcpsvr
rtk settings:
elevation mask angle: '20’
glonass ar mode: 'off’
gps ar mode: continuous
max horizontal acceleration: '1’
max vertical acceleration: '1’
positioning mode: kinematic
positioning systems:
compass: false
galileo: false
glonass: true
gps: true
qzs: true
qzss: false
sbas: false
snr mask: '35’
update rate: ‘5’
And… do I need to select RTCM 3.0 or 3.1 format in my CORS mountpoint settings?
AND… also… and this drives me crazy too… when I toggle the on/off switch for base correction in the “correction input” menu; nothing happens. Stream will stay off. It will only go active if you mess around with some setting and then hit apply… and then changing them back again and hitting apply again. Why? Or am I doing something wrong?
Check out issues with bars just dropping when surveying outside and with clear sky view. Reachview 2.10.0
@emlid.
Not “also” mate… that’s the whole issue here 
Maybe @egor.fedorov or @igor.vereninov can help…
Hi @jantjj,
This certainly does not look right. Could you please submit raw data and solution log files where the issue with disappearing bars could be seen? Also the full system report. We need to determine if it is a hardware issue or a weird software glitch.
You can send the logs to our support email.
Thanks. You have mail
This topic was automatically closed 100 days after the last reply. New replies are no longer allowed.