I cannot change any settings under 2.23.8.
Help!
Even simply turning off corrections input is “not applied “
I get “new settings we’re not applied “
I cannot change any settings under 2.23.8.
Help!
Even simply turning off corrections input is “not applied “
I get “new settings we’re not applied “
Hi @bwolv,
Just to check, could you please specify if rebooting the device helps with that? Do I understand correctly that this issue happens on both devices? Do you use LoRa as a way of correction input/output?
Hi Polina, yes, I have rebooted the RS2 several times. It began after the update to 2.23.8; I did not update the second unit after the trouble with the first. I had been using NTRIP, and Lora, after the update it is “stuck” on “Serial” and connected to /dev/ttyMFD2. I cannot even turn off correction input, as any attempts to change setting (in any page) result in a red banner saying “New Settings Were not applied”…
Thanks!
Hi @bwolv,
May I ask you to generate the Full System Report on your Reach RS2 and send it to me in PM or to support@emlid.com? This will help us check what might the cause of such behavior.
Ok sure, here goes!
[2019-08-30 22:44:41,921] [ INFO] — Discoverable: 1 (bluetool.py:173)
[2019-08-30 22:47:11,796] [ INFO] — RequestConfirmation: /org/bluez/hci0/dev_DC_66_72_D1_D2_86, 569602
(agent.py:170)
[2019-08-30 22:47:11,902] [ INFO] — RequestConfirmation: /org/bluez/hci0/dev_DC_66_72_D1_D2_86: False
(agent.py:184)
[2019-08-30 22:47:11,911] [ ERROR] — org.bluez.Error.AuthenticationFailed: Authentication Failed
(bluetool.py:207)
[2019-08-30 22:47:19,904] [ ERROR] — org.bluez.Error.ConnectionAttemptFailed: Page Timeout
(bluetool.py:207)
[2019-08-30 22:47:25,325] [ ERROR] — org.bluez.Error.ConnectionAttemptFailed: Page Timeout
(bluetool.py:207)
[2019-08-30 22:47:34,123] [ INFO] — RequestConfirmation: /org/bluez/hci0/dev_DC_66_72_D1_D2_86, 593522
(agent.py:170)
[2019-08-30 22:47:34,249] [ INFO] — RequestConfirmation: /org/bluez/hci0/dev_DC_66_72_D1_D2_86: False
(agent.py:184)
[2019-08-30 22:47:34,264] [ ERROR] — org.bluez.Error.AuthenticationFailed: Authentication Failed
(bluetool.py:207)
[2019-08-30 22:47:46,624] [ INFO] — RequestConfirmation: /org/bluez/hci0/dev_DC_66_72_D1_D2_86, 767192
(agent.py:170)
[2019-08-30 22:47:46,717] [ INFO] — RequestConfirmation: /org/bluez/hci0/dev_DC_66_72_D1_D2_86: False
(agent.py:184)
[2019-08-30 22:47:46,731] [ ERROR] — org.bluez.Error.AuthenticationFailed: Authentication Failed
(bluetool.py:207)
[2019-08-30 22:47:48,811] [ INFO] — RequestConfirmation: /org/bluez/hci0/dev_DC_66_72_D1_D2_86, 482941
(agent.py:170)
[2019-08-30 22:47:48,934] [ INFO] — RequestConfirmation: /org/bluez/hci0/dev_DC_66_72_D1_D2_86: False
(agent.py:184)
[2019-08-30 22:47:48,940] [ ERROR] — org.bluez.Error.AuthenticationFailed: Authentication Failed
(bluetool.py:207)
[2019-08-30 22:47:50,224] [ INFO] — RequestConfirmation: /org/bluez/hci0/dev_DC_66_72_D1_D2_86, 674361
(agent.py:170)
[2019-08-30 22:47:50,325] [ INFO] — RequestConfirmation: /org/bluez/hci0/dev_DC_66_72_D1_D2_86: False
(agent.py:184)
[2019-08-30 22:47:50,331] [ ERROR] — org.bluez.Error.AuthenticationFailed: Authentication Failed
(bluetool.py:207)
[2019-08-30 22:47:50,476] [ ERROR] — org.bluez.Error.AuthenticationCanceled: Authentication Canceled
(bluetool.py:207)
[2019-08-30 22:48:01,588] [ INFO] — RequestConfirmation: /org/bluez/hci0/dev_DC_66_72_D1_D2_86, 425936
(agent.py:170)
[2019-08-30 22:48:01,698] [ INFO] — RequestConfirmation: /org/bluez/hci0/dev_DC_66_72_D1_D2_86: False
(agent.py:184)
[2019-08-30 22:48:01,705] [ ERROR] — org.bluez.Error.AuthenticationFailed: Authentication Failed
(bluetool.py:207)
[2019-08-30 22:48:01,878] [ ERROR] — org.bluez.Error.AuthenticationCanceled: Authentication Canceled
(bluetool.py:207)
[2019-08-30 22:51:17,029] [ INFO] — RequestConfirmation: /org/bluez/hci0/dev_DC_66_72_D1_D2_86, 638224
(agent.py:170)
[2019-08-30 22:51:17,164] [ INFO] — RequestConfirmation: /org/bluez/hci0/dev_DC_66_72_D1_D2_86: False
(agent.py:184)
[2019-08-30 22:51:22,562] [ INFO] — RequestConfirmation: /org/bluez/hci0/dev_DC_66_72_D1_D2_86, 220761
(agent.py:170)
[2019-08-30 22:51:22,681] [ INFO] — RequestConfirmation: /org/bluez/hci0/dev_DC_66_72_D1_D2_86: False
(agent.py:184)
[2019-08-30 22:51:22,689] [ ERROR] — org.bluez.Error.AuthenticationFailed: Authentication Failed
(bluetool.py:207)
[2019-08-30 22:51:25,539] [ ERROR] — org.bluez.Error.AuthenticationFailed: Authentication Failed
(bluetool.py:207)
[2019-08-30 22:51:32,857] [ INFO] — RequestConfirmation: /org/bluez/hci0/dev_DC_66_72_D1_D2_86, 426878
(agent.py:170)
[2019-08-30 22:51:32,976] [ INFO] — RequestConfirmation: /org/bluez/hci0/dev_DC_66_72_D1_D2_86: False
(agent.py:184)
[2019-08-30 22:51:32,983] [ ERROR] — org.bluez.Error.AuthenticationFailed: Authentication Failed
(bluetool.py:207)
[2019-08-30 22:51:40,475] [ ERROR] — org.bluez.Error.AuthenticationFailed: Authentication Failed
(bluetool.py:207)
[2019-08-30 22:51:41,004] [ INFO] — RequestConfirmation: /org/bluez/hci0/dev_DC_66_72_D1_D2_86, 159955
(agent.py:170)
[2019-08-30 22:51:41,165] [ INFO] — RequestConfirmation: /org/bluez/hci0/dev_DC_66_72_D1_D2_86: False
(agent.py:184)
[2019-08-30 22:51:52,856] [ ERROR] — org.bluez.Error.AuthenticationTimeout: Authentication Timeout
(bluetool.py:207)
[2019-08-30 22:52:06,075] [ INFO] — RequestConfirmation: /org/bluez/hci0/dev_DC_66_72_D1_D2_86, 465113
(agent.py:170)
[2019-08-30 22:52:06,212] [ INFO] — RequestConfirmation: /org/bluez/hci0/dev_DC_66_72_D1_D2_86: False
(agent.py:184)
[2019-08-30 22:52:06,219] [ ERROR] — org.bluez.Error.AuthenticationFailed: Authentication Failed
(bluetool.py:207)
[2019-08-30 22:52:18,637] [ INFO] — Discoverable: 1 (bluetool.py:173)
[2019-08-30 22:52:26,339] [ INFO] — RequestConfirmation: /org/bluez/hci0/dev_DC_66_72_D1_D2_86, 781887
(agent.py:170)
[2019-08-30 22:52:26,467] [ INFO] — RequestConfirmation: /org/bluez/hci0/dev_DC_66_72_D1_D2_86: False
(agent.py:184)
[2019-08-30 23:02:59,321] [ INFO] — RequestConfirmation: /org/bluez/hci0/dev_DC_66_72_D1_D2_86, 737536
(agent.py:170)
[2019-08-30 23:02:59,390] [ INFO] — RequestConfirmation: /org/bluez/hci0/dev_DC_66_72_D1_D2_86: False
The Simple report…
[[quote=“bwolv, post:1, topic:20762, full:true”]
I cannot change any settings under 2.23.8.
Help!
Even simply turning off corrections input is “not applied “
I get “new settings we’re not applied “
details=“Simple system report”]
app version: 2.23.8-dev-r0
'wifi_status, interface: wlan0':
- wifi_mode: infrastructure
- ip: 192.168.1.22
is_added: true
is_connected: true
is_visible: false
mac_address: 6C:21:A2:92:8D:7A
security: wpa-psk
ssid: Northern Lights
uuid: 0163e540-eda4-40b5-bae6-f75e3bfe3cda
base mode:
base coordinates:
accumulation: 2.0
antenna offset:
east: '0'
north: '0'
up: '0'
coordinates:
- 0
- 0
- 0
format: llh
mode: single-and-hold
output:
enabled: true
io_type: tcpsvr
port: 9000
rtcm3 messages:
'1006':
enabled: true
frequency: 0.10000000000000001
'1074':
enabled: true
frequency: 1.0
'1084':
enabled: true
frequency: 1.0
'1094':
enabled: false
frequency: 1.0
'1124':
enabled: false
frequency: 1.0
bluetooth:
discoverable: true
enabled: false
pin: '***'
constraints:
lora:
frequency:
- - 902000
- 928000
correction input:
input2:
baud_rate: 38400
device: UART
enabled: true
io_type: serial
send_position_to_base: false
device:
emit_telemetry: false
night_mode: false
power_on_bottom_connector: false
logging:
base:
format: RTCM3
started: false
correction:
format: RTCM3
started: true
debug: false
interval: 24
overwrite: true
raw:
format: UBX
started: false
solution:
format: LLH
started: false
lora:
air rate: 2.6000000000000001
frequency: 868000
output power: 20.0
network:
tcp_over_modem: false
position output:
output1:
baud_rate: 38400
device: UART
enabled: false
format: ERB
io_type: serial
output2:
baud_rate: 38400
device: UART
enabled: false
format: ERB
io_type: serial
rtk settings:
elevation mask angle: 15
glonass ar mode: 'off'
gps ar mode: fix-and-hold
max horizontal acceleration: 1.0
max vertical acceleration: 1.0
positioning mode: kinematic
positioning systems:
compass: true
galileo: true
glonass: true
gps: true
qzss: true
snr mask: 35
update rate: 10
sound:
mute: false
volume: 20
[/details]
The Simple report…
app version: 2.23.8-dev-r0
'wifi_status, interface: wlan0':
- wifi_mode: infrastructure
- ip: 192.168.1.22
is_added: true
is_connected: true
is_visible: false
mac_address: 6C:21:A2:92:8D:7A
security: wpa-psk
ssid: Northern Lights
uuid: 0163e540-eda4-40b5-bae6-f75e3bfe3cda
base mode:
base coordinates:
accumulation: 2.0
antenna offset:
east: '0'
north: '0'
up: '0'
coordinates:
- 0
- 0
- 0
format: llh
mode: single-and-hold
output:
enabled: true
io_type: tcpsvr
port: 9000
rtcm3 messages:
'1006':
enabled: true
frequency: 0.10000000000000001
'1074':
enabled: true
frequency: 1.0
'1084':
enabled: true
frequency: 1.0
'1094':
enabled: false
frequency: 1.0
'1124':
enabled: false
frequency: 1.0
bluetooth:
discoverable: true
enabled: false
pin: '***'
constraints:
lora:
frequency:
- - 902000
- 928000
correction input:
input2:
baud_rate: 38400
device: UART
enabled: true
io_type: serial
send_position_to_base: false
device:
emit_telemetry: false
night_mode: false
power_on_bottom_connector: false
logging:
base:
format: RTCM3
started: false
correction:
format: RTCM3
started: true
debug: false
interval: 24
overwrite: true
raw:
format: UBX
started: false
solution:
format: LLH
started: false
lora:
air rate: 2.6000000000000001
frequency: 868000
output power: 20.0
network:
tcp_over_modem: false
position output:
output1:
baud_rate: 38400
device: UART
enabled: false
format: ERB
io_type: serial
output2:
baud_rate: 38400
device: UART
enabled: false
format: ERB
io_type: serial
rtk settings:
elevation mask angle: 15
glonass ar mode: 'off'
gps ar mode: fix-and-hold
max horizontal acceleration: 1.0
max vertical acceleration: 1.0
positioning mode: kinematic
positioning systems:
compass: true
galileo: true
glonass: true
gps: true
qzss: true
snr mask: 35
update rate: 10
sound:
mute: false
volume: 20
I I had that problem a week ago and I reset the equipment which changed the frequency to around 864, I reset it to 902 and the problem was corrected.
Check the frecuency for your location, I hope this can help you.
Hi @bwolv,
Thanks for the reports! We’ll look into them.
I’ve deleted your Full System Report as it might contain some sensitive information.
Meanwhile, would it be possible to check if changing the Correction Input method prior to trying to switch it off completely makes any difference?
Thanks Polina,
I tried to change corrections input before shut down, but again, “changes are not applied”… I also tried to change Lora frequency. And got the same result.
I have tried to " Reset settings to default"… No luck. still “New settings were not applied”…
SOLVED!!!
As Jofemo60 suggested, after the firmware update, it seems the Lora frequency was set “out of bounds”… it would not even allow the corrections input to be turned off. But as Jofemo60 suggested, by returning the frequency to (between 902 to 928 in my region) that was a change that was finally “applied”! And that allowed changes to be applied in the other pages as well!
Thanks Jofemo60!,
@bwolv, thanks for the update on this! Great to know that now it’s possible to work with your device!
Jesus @jofemo60, thanks for sharing the tip!
Hey guys,
Just wanted to tell you that this is fixed in the latest dev v2.23.9 update. You should not face the issue with applying settings after you update to it.
You can check the full list of fixes and improvements in this community forum thread.
This topic was automatically closed 100 days after the last reply. New replies are no longer allowed.