Flashing red Sats icon.....

Darren Clemons

Well-Known Member
IMG_1331.JPG
I was in the field today and the LS seemed to pause and at first I thought lock up, but then I was able to get to the home screen and saw this....a flashing red icon on the sats button. When I clicked on it, instead of how it usually shows all the satellite data, it asked something like what type of receiver internal or external (wish I'd took a picture). I had no solution at all in the collect screen, not even STN or CDF, just blank dashes..
I immediately did a hard reset on the LS and thankfully she took right off and I didn't see it again.
Anyone have any idea why it did this and what may have caused it?
 

Adam

Well-Known Member
5PLS
Don't know what caused it but it happens if an OAF is no longer valid.
 

Darren Clemons

Well-Known Member
Don't know what caused it but it happens if an OAF is no longer valid.
That's what Sibole told me when I texted him. Said I was lucky it went back to working. Hopefully it won't happen again. I checked my OAF when I got to the office and it seemed fine.
 

Michael Stazhkov

Developer
JAVAD GNSS
View attachment 6061 I was in the field today and the LS seemed to pause and at first I thought lock up, but then I was able to get to the home screen and saw this....a flashing red icon on the sats button. When I clicked on it, instead of how it usually shows all the satellite data, it asked something like what type of receiver internal or external (wish I'd took a picture). I had no solution at all in the collect screen, not even STN or CDF, just blank dashes..
I immediately did a hard reset on the LS and thankfully she took right off and I didn't see it again.
Anyone have any idea why it did this and what may have caused it?
When OAF is expired it should show 0 satellites and blink yellow.
When it blinks red it means that there are no communication between application and GNSS board. It can happen by 2 reasons: the communication port stops working or GNSS firmware exception. Usually when it happens we see a problem with port. But it happens very rarely. Reboot should help.
 
Top