skylooker

Just to say, thank you to everyone who helped. In the end I fixed the problem by buying a Skywatcher Wi-Fi adapter as the built-in chip's Wi-Fi was corrupt and so that was the only way to get a valid SSID. Once I had a way to connect, I could load the new firmware and it all worked perfectly. I went for the new EQ firmware as my scope is mounted on the right so now I have AZ working I might be looking into a wedge in the near future...this hobby never ends ha ha!

Thanks for the advice everyone. It seems we're leaning towards a firmware update being the solution but is that possible if I can't wirelessly connect to the SynScan_xxxx SSID using a PC (which is the case)? I had read https://stargazerslounge.com/topic/305296-sw-az-gti-mount-firmware-update/?do=findComment&comment=3338343 and thought I had to connect using the standard SynScan_xxxx SSID. What was your experience @banjaxed ? Did you have to connect to the SynScan_xxxx SSID using your PC and then run the update, or would connecting to the ESP_xxxxxx work? I just don't want to risk bricking the mount. I think based on what @stash_old mentioned in https://stargazerslounge.com/topic/323320-skywatcher-az-gti-mount-wifi-not-working/?do=findComment&comment=3525347 that the ESP_xxxxxx is an Access Point (AP) address which should then trigger the main WiFi SSID (SynScan_xxxx SSID) we can connect to. Are there cases where the ESP chip in the mount doesn't fully load or gets stuck at the AP stage? Or am I barking up the wrong tree? Thanks for the replies, it's nice to be part of a helpful community.

Hi I'm hoping someone on here can help with some problems I am having with my recently acquired (second hand) Skywatcher AZ GTi. When I originally switched the mount on I got the single flashing red LED indicating the internal Wi-Fi was on. I then looked for the SSID in the format SynScan_xxxx under the Wi-Fi listings on my Android phone but all I saw was an SSID in the format ESP_xxxxxx that never changed to anything else. Having read a few threads on here I thought it might be interference from my home Wi-Fi (or neighbour’s Wi-Fi) so I took myself off to the middle of a field and used the Android Net Analyzer to ensure there were no Wi-Fi signals detected and switched the mount on again and all that was listed was the ESP_xxxxxx SSID on my Android phone. Not to be defeated I then reset the Wi-Fi configuration to factory default by powering it on for 4 hours using a 12V 1A mains adaptor without anything connected (physicaly or using Wi-Fi). Off to the field to check again (no other external Wi-Fi networks etc) still just the ESP_xxxxxx SSID. A little disheartened by this I then attempted to detect the mount using an iPhone, and iPad and a PC, all of which detect it as having the ESP_xxxxxx SSID. So I am now at the stage of asking for help in the hope someone can shed some light on this. Now I know in normal operation the ESP_xxxxxx will always come up for a few seconds and then be replaced by the SynScan_xxxx SSID but this is not happening and as a result I cannot connect to it, and (correct me if I am wrong) this means I cannot update the firmware, which is a solution I have seen suggested when it comes to the ESP_xxxxxx problem. Hopefully I’m just missing something and it’s not kaput. Any ideas are very welcome!