I flashed my reach using the v2.1 beta file. The update completed successfully and I see the new reachview app when restarting and connecting to the reach via its self generated wifi link. I enter the connection info for my wifi router and hit save. The screen shows the router info, but everything below if greyed out. If I reboot, it goes back into self generate hotspot mode and I can not get the reach to connect to my router.
@TB_RTK How do you tell which version of the beta you are running? Is there a version file in the ReachImage_v2.1_beta zip? Do all links point to a central file? I’ve been trying to update (four days) and get reach to connect to my wifi without success.
At the bottom of Emlid menu (where you save wifi credentials) you can see current and new version to update)
To verify a successful flash? Im acctually not sure what i was thinking. I guess if everything works, its successfully
I wasn’t able to try it a second time. It tried to connect the first time, reach flashed Blue a couple of times and then turned green and was not creating it’s own hot spot. So I couldn’t get to the app a second time.
I have to try my testing again. I received false negatives I believe. When I did connect to my android mobile hotspot it worked fantastic BUT, the LED was Green. I thought Green meant it created it’s own hotspot so it is possible I missed it connecting to my local network. I was looking for a Blue LEDs to indicate it was connected to wifi.
I still believe there is an issue connecting to my in home wifi. (Belkin 1750AC) Either there is an incompatibility with my wifi or Reach is not providing what my network needs for it to connect. I would see it in the router logs but when scanned with Fing and Zenmap it was listed but no ports were open. It was also never listed in my networks connected devices.
In the beta version the led statuses are much simpler as we didn’t get the chance to address them properly yet. The green in the end simply means the app started with no problems. If, for some reason, it fails, the light will turn red.
The network status can be read by checking the led during boot. During Linux boot it’s magenta. Then it turns off for a second and we start our self tests and preparations. Yellow blinking means Reach is looking for a network to join. Right after that, the led blinks either blue or green, meaning it has connected to a network or created a hotspot correspondingly. Then, the time sync begins and magenta is added to either blue or green for a short period of time. As soon as the time sync is finished, the app launches with a solid green.
It seems, that in your case Reach actually connected to your network.
Could be that I have the same problem. I had no success getting the Reach up and running at work (corporate WiFi, Windows 7, Internet Explorer) or at home with a Belkin N300, Windows 10, Firefox setup. I finally got it after updating to the Beta 2.1.5, using my iPhone as a hotspot and opening the app in Safari. Now the Reach works fine on its own hotspot, but no luck on my Belkin network. It seems to connect OK, shows up with an address in Fing, but I can’t connect or ping it. Anything else on the Belkin network pings fine.
Yes. I can concur with your findings. We are not able to connect to a WiFi router. I replaced my Belkin router yesterday with a new router (Netgear,Nighthawk AC1900) thinking it was a problem with the router. It is not a problem with the router. Reach connects and can be seen on the router but when doing an intense scan plus all TCP ports with Zenmap and there are not any ports open. There is nothing to connect to on the Reach. When doing the same scan when using Reach’s hot spot ports for Http and SSH are available. .
Both networks I tried (at work and at home) use WPA2 personal security. In another week or so I’ll be getting a new setup (changing from ADSL to the new Fibre-optic National broadband), maybe that will make a difference.
It doesn’t make sense the ISP would be an issue. The router it is connecting to though might. I to have primarily used wpa2-personal and although the router says connected when scanned with zenmap and fing, both reports show there are not any ports available to talk. Port 80 (and maybe 22 for SSH) should be available. I have tried all of the security settings without success. I can consistently connect to my mobile hot spot but cannot connect to a Wifi Router.
Here is where it connects and is up in router attached devices.
I agree it’s not an ISP thing per se, but having a new modem/router and new setup configuration might make it work without ever finding what exactly in my current router configuration is causing the problem.
I’ve tried forgetting the network and starting again a few times with the same result. The procedure is a bit painful, because the Reach ‘thinks’ it has found a known network and locks on, so to get to the app I have to shut the network off first.
Is there a way that the network connection can be tested with a wired connection to the laptop? I have Linux on another computer but I’m certainly no expert.
@egor.fedorov , Could this be a problem with Region settings for the Wifi router? My region settings are fixed in the Wifi Router for North America. Reach does connect to my Wifi router but there are not any ports open to connect to from other computers.
Could it be the web server and SSH on the reach do not get started?
Is anybody in North America connecting to reach via Wifi Router? Not mobile hot spot but Wifi router.