Ok so the reach keeps on turning on bluetooth by itself, and is running real slow
I have to continually force refresh my browser to stay connected / drops connection
It popped up an Emlid privacy page I clicked ok, but now i can not reload at all after
I can still ping its ip through command prompt, but no browser page, very odd.
blue tooth just keeps flashing then turning blue like it is connecting then disconnecting. though it should not be on at all
The heat sink is very hot, It has not run like this before I maybe have 48hrs on this unit.
I have generated a full system report, where do i send it @tatiana.andreeva.
will try a pm.
But also in the web browser the blue tooth was always green. But now i see that may have been because of the unit freezing. Both wifi and hotspot the interface would freeze.
I just wanted to note that the LED status of the Reach RS2 doesn’t show the behavior of the Bluetooth. The connection LED shows the state of the RTK solution:
when it turns blue, it indicates that the unit transmits corrections;
when it’s blinking white, it shows that the unit calculates either Single or Float;
when it becomes solid white, it means that the unit obtained Fix.
All of these statuses are described in our LED status docs.
We’re currently checking what could be the cause of such behavior. I’ll give an update once there’s news.
I tried as scientifically as possible to make the RS2 lock up again. Turning on each function then waiting 15min taking a temp then turning on another function.
It took many hours, but the hottest I could get it even with charging was 43C and everything enabled. I have found it is slightly warmer in kinematic vs static mode. But no problems with interface or connection at that temperature.
The night it locked up the reach surpassed this temperature within minutes of it turning on.
It is possible i fixed something then by re flashing but it took time for the component to cool back down.
How is it going? I just wanted to tell you that we have released the 26.1 update that should resolve the disconnection issues with ReachView 3 app. Please update your receivers to check if the update works for you.