Station Mode cannot connect to AP of the mount.

[lewdmeat]

Hi,
first of all, thank you very much Robert for this amazing tool.

I finally got the controller to work, now i'm at the point of setting things up properly for the rig.
In AP mode this works flawlessly. In Station mode, connecting to my home network, that works fine also.
The problem I have now is that I cannot get to to connect to my mount's AP (AZ-GTi). When I set it up for the mount's AP, the controller keeps rebooting.
I decoded the ESP32 exception and it seems to just be rebooting after timeout of retries to connect to the network.
Is it a limitation of the mount's AP for some reason? I know too little about Wi-Fi networking to troubleshoot any further.

I have another EPS32 board lying around and I'm testing that with a simple wifi-connect code to see if that ESP32 can connect to the mount's AP or not, so far I'm still struggling to even upload the sketch, maybe it was a faulty board that I dont remember.

Any directions for me how to troubleshoot or test further would be much appreciated!
Thanks!

[brownrb]

Apologies for not getting to this sooner.
I am a bit like a bear in a cave, when I get absorbed into a new release. hence myFP2 (done today), mySQM+ (in a week) and then myFP2ESP32 after that.

If the WiFi is low then its a problem, because the controller will attempt to reconnect the WiFi over and over again.

There are some things in beta 313 which are addressed specifically to WiFim and the WiFi signal strength appears on footer pages of Management Server

Troubleshoot.
It is probably easier to enable the Debug Server and set it to ouput debug messages to port 9090.
In controller_config.h enable boot print

#define BOOT_PRINT 1

I then run a logger to capture all debug messages to a file.

I think the position() error has been addressed
Send me an email to my gmail. com account (look in PDF) and you can try the latest beta 313 if interested.

Regards
Robert

[lewdmeat]

PC: 0x40180bbb: DRIVER_BOARD::getposition() at C:\Users\xxxx\Documents\Arduino\MyFocuserPro2-ESP\myfp2esp32_311-02/driver_board.cpp line 984
EXCVADDR: 0x00000004

Decoding stack results
0x40180bb8: DRIVER_BOARD::getposition() at C:\Users\xxxx\Documents\Arduino\MyFocuserPro2-ESP\myfp2esp32_311-02/driver_board.cpp line 983
0x400ed3f7: reboot_esp32(int) at C:\Users\xxxx\Documents\Arduino\MyFocuserPro2-ESP\myfp2esp32_311-02/myfp2esp32_311-02.ino line 976
0x400ee67d: setup() at C:\Users\xxxx\Documents\Arduino\MyFocuserPro2-ESP\myfp2esp32_311-02/myfp2esp32_311-02.ino line 1304
0x400ff316: loopTask(void*) at C:\Users\xxxx\AppData\Local\Arduino15\packages\esp32\hardware\esp32\2.0.11\cores\esp32\main.cpp line 42

Here's the decoded exception I keep getting when setting the station up to connect to the mount's AP.

[lewdmeat]

I have tested further with different networks and hotspots. Even with simple SSIDs as well (no spaces, no special characters). So far I have noticed the controller can only connect successfully to networks that are Wi-Fi 6 (802.11ax) and Wi-Fi 4 (802.11n) and cannot connect to the mount's AP which is 802.11g

[lewdmeat]

nvm I solved it. Turns out the combination of weak AP Signal from the mount and the built-in antenna on the PCB means I have to practically put the controller onto the mount itself to have a connection. even just 1m away is too far.