No satellites on bluetooth

alexander.gehrig · February 8, 2023, 9:05pm

Hoping there’s something easy that I’ve overlooked, thanks in advance for any pointers.

Set up - Locating known survey markers in the field I connect to Reach RS2 with iPhone 13 pro max over bluetooth and utilize NTRIP over bluetooth for corrections. Wifi is turned off. Cell signal on iPhone is 2 bars or better.

Issue - the app connects to RS2 (I can flash the RS2 LEDs) via BT but there are no satellites displayed. This has happened in several different locations with open sky conditions. If I connect to the RS2 via its wifi hotspot, there are satellites. Sometimes restarting the RS2 helps, sometimes it just doesn’t find anything.

Using Emlid Flow version 8.1. iOS 16.3. Firmware 30 Beta 3.

System report:

app version:30.0.beta.3-dev-r1
current_network:
ip:192.168.42.1
security:wpa
ssid:Preston_reach:0E:C5
enabled:true
mode:hotspot
base_mode:
base_coordinates:
accumulation:120
antenna_offset:0
coordinates:
height:0
latitude:0
longitude:0
mode:single-and-hold
output:
io_type:‘off’
settings:
lora:
air_rate:9.11
frequency:902000
output_power:20
ntripcaster:
mount_point:REACH
password:‘’
port:2101
username:reach
ntripsvr:
address:‘’
mount_point:‘’
password:'’
port:-1
serial:
baud_rate:38400
device:ttyEXTS0
tcpcli:
address:localhost
port:9001
tcpsvr:
port:9000
rtcm3_messages:
message_1004:
enabled:false
frequency:1
message_1006:
enabled:true
frequency:0.1
message_1008:
enabled:false
frequency:0.1
message_1012:
enabled:false
frequency:1
message_1033:
enabled:false
frequency:0.1
message_1074:
enabled:true
frequency:0.5
message_1084:
enabled:true
frequency:0.5
message_1094:
enabled:true
frequency:0.5
message_1124:
enabled:true
frequency:0.5
message_1230:
enabled:true
frequency:0.1
bluetooth:
enabled:true
pairing:
discoverable:true
no_input_no_output:true
pin:‘’
correction_input:
base_corrections:
io_type:ble
settings:
bluetooth:
send_position_to_base:false
lora:
air_rate:9.11
frequency:902000
output_power:20
send_position_to_base:false
ntripcli:
address:151.111.143.7
mount_point:AGRTCM31
password:'’
port:9000
send_position_to_base:true
username:DNR/AlexanderG
serial:
baud_rate:38400
device:ttyEXTS0
send_position_to_base:false
tcpcli:
address:localhost
port:10001
send_position_to_base:false
tcpsvr:
port:10000
send_position_to_base:false
device:
power_on_bottom_connector:false
privacy_policy_accepted:true
role:null
rv3_banner_shown:false
usage_analysis_accepted:true
logging:
logs:
autostart:true
base:
enabled:true
format:RTCM3
raw:
enabled:true
format:RINEX
rinex_options:
logging_interval:0
marker_name:null
pole_height:null
preset:default
satellite_systems:
beidou:true
galileo:true
glonass:true
gps:true
qzss:true
sbas:false
time_adjustments_enabled:true
version:‘3.03’
solution:
enabled:true
format:LLH
started:true
settings:
interval:24
overwrite:true
simultaneous_logging:false
network:
tcp_over_modem:false
position_output:
output1:
io_type:bluetooth
nmea_settings:
bluetooth:
ebp:
enabled:true
update_rate:1
gga:
enabled:true
update_rate:1
gsa:
enabled:true
update_rate:1
gst:
enabled:true
update_rate:1
gsv:
enabled:true
update_rate:1
main_talker_id:gn
rmc:
enabled:true
update_rate:1
vtg:
enabled:true
update_rate:1
zda:
enabled:true
update_rate:1
serial:
ebp:
enabled:true
update_rate:1
gga:
enabled:true
update_rate:1
gsa:
enabled:true
update_rate:1
gst:
enabled:true
update_rate:1
gsv:
enabled:true
update_rate:1
main_talker_id:gn
rmc:
enabled:true
update_rate:1
vtg:
enabled:true
update_rate:1
zda:
enabled:true
update_rate:1
tcpcli:
ebp:
enabled:true
update_rate:1
gga:
enabled:true
update_rate:1
gsa:
enabled:true
update_rate:1
gst:
enabled:true
update_rate:1
gsv:
enabled:true
update_rate:1
main_talker_id:gn
rmc:
enabled:true
update_rate:1
vtg:
enabled:true
update_rate:1
zda:
enabled:true
update_rate:1
tcpsvr:
ebp:
enabled:true
update_rate:1
gga:
enabled:true
update_rate:1
gsa:
enabled:true
update_rate:1
gst:
enabled:true
update_rate:1
gsv:
enabled:true
update_rate:1
main_talker_id:gn
rmc:
enabled:true
update_rate:1
vtg:
enabled:true
update_rate:1
zda:
enabled:true
update_rate:1
settings:
bluetooth:
format:NMEA
serial:
baud_rate:38400
device:ttyEXTS0
format:ERB
tcpcli:
address:localhost
format:ERB
port:9000
tcpsvr:
format:LLH
port:9001
output2:
io_type:‘off’
nmea_settings:
bluetooth:
ebp:
enabled:true
update_rate:1
gga:
enabled:true
update_rate:1
gsa:
enabled:true
update_rate:1
gst:
enabled:true
update_rate:1
gsv:
enabled:true
update_rate:1
main_talker_id:gn
rmc:
enabled:true
update_rate:1
vtg:
enabled:true
update_rate:1
zda:
enabled:true
update_rate:1
serial:
ebp:
enabled:true
update_rate:1
gga:
enabled:true
update_rate:1
gsa:
enabled:true
update_rate:1
gst:
enabled:true
update_rate:1
gsv:
enabled:true
update_rate:1
main_talker_id:gn
rmc:
enabled:true
update_rate:1
vtg:
enabled:true
update_rate:1
zda:
enabled:true
update_rate:1
tcpcli:
ebp:
enabled:true
update_rate:1
gga:
enabled:true
update_rate:1
gsa:
enabled:true
update_rate:1
gst:
enabled:true
update_rate:1
gsv:
enabled:true
update_rate:1
main_talker_id:gn
rmc:
enabled:true
update_rate:1
vtg:
enabled:true
update_rate:1
zda:
enabled:true
update_rate:1
tcpsvr:
ebp:
enabled:true
update_rate:1
gga:
enabled:true
update_rate:1
gsa:
enabled:true
update_rate:1
gst:
enabled:true
update_rate:1
gsv:
enabled:true
update_rate:1
main_talker_id:gn
rmc:
enabled:true
update_rate:1
vtg:
enabled:true
update_rate:1
zda:
enabled:true
update_rate:1
settings:
bluetooth:
format:NMEA
serial:
baud_rate:38400
device:ttyEXTS0
format:ERB
tcpcli:
address:localhost
format:ERB
port:9000
tcpsvr:
format:LLH
port:9001
positioning_settings:
elevation_mask_angle:15
glonass_ar_mode:false
gnss_settings:
positioning_systems:
beidou:false
galileo:true
glonass:true
gps:true
qzss:true
update_rate:5
gps_ar_mode:fix-and-hold
max_horizontal_acceleration:1
max_vertical_acceleration:1
positioning_mode:kinematic
snr_mask:35
sound:
mute:false
volume:100

[/details]

svetlana.nikolenko · February 9, 2023, 3:08pm

Hi Alexander,

It seems you do everything right. But I see you work on the 30 Beta version, and we already have a stable one. Please connect your device to Wi-Fi and update your device to 30 stable version. So that we’ll be sure it’s not related to Beta.

alexander.gehrig · February 9, 2023, 4:50pm

Thanks for the reply. I updated firmware to the 30 stable version. After restart results are the same as above. I also tried connecting to RS2 via bluetooth with an android device - it would pair according to the mobile device and it would show up in the list of devices on the app but would not even open the receiver to display status, connection input etc.

As an added note, it had been working as recently as last week. I could get satellites and corrections connecting via bluetooth on both iOS and android.

alexander.gehrig · February 13, 2023, 4:28pm

Tried another test this morning. Satellites over the RS2 wifi hot spot, nothing over bluetooth. Report included if its useful. Really hoping to find something that I’ve missed, I currently own a very expensive brick.
Report.pdf (105.7 KB)

svetlana.nikolenko · February 13, 2023, 8:07pm

Hi Alexander,

I’m pretty sure we’ll be able to fix this cause it looks like a software issue. But I need a little bit more info to investigate that:

The Full system report
Your Android model and version

I’d suggest sending the report to support@emlid.com cause it contains sensitive info.

alexander.gehrig · February 13, 2023, 9:31pm

Thanks, I emailed the report and received notice that it is logged as ticket 69032. I am using iOS 16.3 on iPhone 13 Pro Max. I have also used an android device but iOS is the system I need this to work on.

svetlana.nikolenko · February 14, 2023, 2:17pm

I got your email. I’ll check the report and get back to you.

kseniia.suzdaltseva · February 24, 2023, 3:32pm

Hi Alexander,

We haven’t found any specific issues from the Reach side but have noticed that the iPhone was paired with Reach at some point. Let’s dig a bit deeper into the issue. Please do the following:

Remove Reach from the list of known devices on the iPhone
If the issue persists, please create an FSR right after this behavior is spotted and share it with us via email.

alexander.gehrig · February 27, 2023, 8:51pm

Thanks, just sent another report.

svetlana.nikolenko · February 28, 2023, 2:40pm

I received it, thanks! I’ll get back to you once we examine it.

svetlana.nikolenko · March 27, 2023, 2:23pm

Just want to mention it works fine now. In the report we examined, everything was fine as well. So, most likely, it was something phone-related.

If anyone faces similar behavior, please create a new thread or contact us via support@emlid.com. We’ll investigate that.