Hello! I have an RS 2 RECEIVER and a getac ps 336 with Surv CE. More than several times, the bluetooth/internet connection between RS2 and getac is interrupted and i don t know what to do. Can someone please help me, thanks!
Hi Sam, what update rate you have in RTK Settings in ReachView?
Could you please try 1 Hz? Does the issue persist?
I will try at 1hz, and get you updated. Thanks!
With 1hz it s the same. It shows me bluetooth error: 0. OS returns 10057. Verify the bluetooth settings. Surv Ce runs on windows CE 6.05. I deleted the existing bluetooth connection and added it again and it connects ok.
Another problem i have now is that surv ce shows me an erorr -
no rtk corrections are obtained from the base. When i use ntrip leberfur it shows me that i obtain corrections.
Hi @SAM88,
May I ask you to share a simple system report from your Reach RS2?
Another problem i have now is that surv ce shows me an erorr - no rtk corrections are obtained from the base. When i use ntrip leberfur it shows me that i obtain corrections
I just want to clarify whether you configured Corrections input over NTRIP in the ReachView app?
I configured it but i have bluetooth problems. The bluetooth between the rs2 and getac dosen t work constantly. It fixes good, but I have to reconnect manually, because in SURV CE 6.05 it shows me after several minutes RTK fixed with no corrections. I will attach 2 reports from different periods.
from 25.02 : [details=“Simple system report”]
app version: 2.22.2-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: B0:F1:EC:02:07:E6
security: wpa-psk
ssid: reach:68:96
uuid: 843fea05-632e-4abf-9269-60c2258991d2
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:
'1006':
enabled: true
frequency: 0.10000000000000001
'1074':
enabled: true
frequency: 1
'1084':
enabled: true
frequency: 1
'1094':
enabled: false
frequency: 1
'1124':
enabled: false
frequency: 1
bluetooth:
discoverable: true
enabled: true
pin: '***'
constraints:
lora:
frequency:
- - 863000
- 870000
correction input:
input2:
enabled: true
format: rtcm3
path: bluetooth
send position to base: 'off'
type: bluetooth
input3:
enabled: false
format: RTCM3
io_type: tcpsvr
path: :9028
device: null
logging:
base:
format: RTCM3
started: true
correction:
format: null
started: null
debug: false
interval: 24
overwrite: false
raw:
format: UBX
started: true
solution:
format: LLH
started: true
lora:
air rate: 2.6000000000000001
frequency: 868000
mode: null
output power: 20
position output:
output1:
enabled: true
format: nmea
path: bluetooth
type: bluetooth
output2:
enabled: false
format: llh
path: :9001
type: tcpsvr
rtk settings:
elevation mask angle: 13
glonass ar mode: 'off'
gps ar mode: fix-and-hold
max horizontal acceleration: 1
max vertical acceleration: 1
positioning mode: kinematic
positioning systems:
compass: true
galileo: true
glonass: true
gps: true
qzss: true
snr mask: 36
update rate: 5
sound: null
[/details]
from today 02.03 : [details=“Simple system report”]
app version: 2.22.2-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: B0:F1:EC:02:07:E6
security: wpa-psk
ssid: reach:68:96
uuid: 843fea05-632e-4abf-9269-60c2258991d2
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:
'1006':
enabled: true
frequency: 0.10000000000000001
'1074':
enabled: true
frequency: 1
'1084':
enabled: true
frequency: 1
'1094':
enabled: false
frequency: 1
'1124':
enabled: false
frequency: 1
bluetooth:
discoverable: true
enabled: true
pin: '***'
constraints:
lora:
frequency:
- - 863000
- 870000
correction input:
input2:
enabled: true
format: rtcm3
path: bluetooth
send position to base: 'off'
type: bluetooth
input3:
enabled: false
format: RTCM3
io_type: tcpsvr
path: :9028
device: null
logging:
base:
format: RTCM3
started: true
correction:
format: null
started: null
debug: false
interval: 15
overwrite: false
raw:
format: UBX
started: true
solution:
format: LLH
started: true
lora:
air rate: 2.6000000000000001
frequency: 868000
mode: null
output power: 20
position output:
output1:
enabled: true
format: nmea
path: bluetooth
type: bluetooth
output2:
enabled: false
format: llh
path: :9001
type: tcpsvr
rtk settings:
elevation mask angle: 13
glonass ar mode: 'off'
gps ar mode: fix-and-hold
max horizontal acceleration: 1
max vertical acceleration: 1
positioning mode: kinematic
positioning systems:
compass: true
galileo: true
glonass: true
gps: true
qzss: true
snr mask: 36
update rate: 1
sound: null
[/details]
Sam,
I’ll try to reproduce the issue and get back to you with the results.
Hi Sam,
Based on your system report, you receive corrections via Bluetooth, and also you mentioned that you connect to the NTRIP caster. May I ask you to describe your setup in more detail?
The problem is the bluetooth connection. The controller, in survce stops receiveing data after several minutes… The setup details are in the report… Can someone who uses survce give me some solutions? Thanks in advance!
I sent more setup details. My ticket number is 27365.
Hi @SAM88,
I received your email, thank you! May I also ask you to share the Correction input tab screenshot?
Since you noticed that you get corrections via Bluetooth and I would like to reproduce the behavior with the same settings.
Hi @SAM88,
How is it going?
I tried to reproduce the issue, however, I’m not sure that I have the same settings. Please, could you elaborate on how you receive the corrections?
