Hello everybody,
i have a problem with my base correction connection in NTRIP.
In Correction Input it connects to the base but after a few seconds there is a “timeout” error. A few seconds later it sems to be connected but then there is the “timeout” error again. This goes on and on.
Reachview 2.16.2
Thank you for your help!
Hi @johannes ,
Could you please share your Reach Simple System Report ?
Hello Tatiana, thank you for your help!
here is the system report.
Simple system report
app version: 2.16.2-r0
'wifi_status, interface: wlan0':
- wifi_mode: wpa_supplicant
- ip: 192.168.23.105
is_connected: true
mac_address: fc:db:b3:8c:11:c5
ssid: ASUS-Access Point
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: '***'
camera:
duty cycle: 20
enable: false
period: 2
polarity: true
correction input:
input2:
enabled: true
format: rtcm3
path: hofstaetter:***@5.9.114.59:2101/MOUNT
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: UBX
started: false
version: null
solution:
format: LLH
started: false
version: null
position output:
output1:
enabled: true
format: nmea
path: ttyGS0:115200:8:n:1:off
type: serial
output2:
enabled: true
format: erb
path: ttyMFD2:4800: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: '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: '35'
update rate: '1'
Hi @johannes ,
What’s the network you connect your Reach device? Please make sure it provides the Internet connection.
Could you try to connect Reach to another network as well?
Hi @tatiana.andreeva ,
it’s my home network. I also tried it with the wifi hotspot of my smartphone but there was the same problem. The network Provider of my smartphone is t-mobile AT.
When i try the same settings on my second emelid reach it works.
Hi @johannes ,
Are you trying to connect both Reach devices to the same NTRIP station simultaneously?
Could you share the screenshot of Correction Input tab and the Simple System Report from this unit as well?
i don’t try it simultnaeously.
here is the screenshot of correction input tab.
and the system report as well:+[details=“Simple system report”]
app version: 2.16.2-r0
'wifi_status, interface: wlan0':
- wifi_mode: wpa_supplicant
- ip: 192.168.23.104
is_connected: true
mac_address: fc:db:b3:92:43:52
ssid: OpenWrt
base mode:
base coordinates:
accumulation: '30'
antenna offset:
east: '0'
north: '0'
up: '0'
coordinates:
- '48.2450714'
- '13.06251236'
- '426.82'
format: llh
mode: manual
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: 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: true
frequency: '1'
'1117':
enabled: true
frequency: '1'
'1127':
enabled: true
frequency: '1'
gps:
enabled: false
frequency: '1'
qzss:
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: hofstaetter:***@5.9.114.59:2101/LOMR2
send position to base: single
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: UBX
started: false
version: null
solution:
format: LLH
started: false
version: null
position output:
output1:
enabled: false
format: nmea
path: host-hostgeo.ddns.net:8080
type: tcpcli
output2:
enabled: false
format: llh
path: :2013
type: tcpsvr
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: '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: '35'
update rate: '1'
[/details]
@johannes ,
Thanks!
Please reset settings to default and try to connect once more.
system
(system)
Closed
June 6, 2019, 11:55am
11
This topic was automatically closed 100 days after the last reply. New replies are no longer allowed.