Hello.
I'm having trouble connecting to the hotspot on my MELE overclock (windows 11 pro). I have no problems connecting to the router on my home network.
I have tried several times to change the SSID and password on the hotspot and in stationmode_defines.h.
Does anyone know why I can't connect to the hotspot?
I'm using myfp2esp32firmware-304, as I haven't been able to get myfp2esp32-firmware-306-07 to work
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have tested with the hotspot set up with 2.4GHz / 5GHz and only 2.4GHz. I haven't tried with a static IP, because I don't know if I can decide which IP range the hotspot should use. I use the Windows app Hotspot and resilientHotspot.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I note that 306 is available on SF in the files area. You indicate that you could not get it to work. If you have an issue, that is why I am here, all you need to do is ask either by email to gmail or by a post here.
However, v309 firmware is available for testing: send me an email (not on SF) and I will arrange access, then we can go from there. The list of fixes from 304 to 309 are listed at the end of this reply.
Hotspots have never been tested by me. They introduce another layer that differs so much from vendor to vendor. A hotspot is not the same as a router connection and does not pretend to be a "router" connection. Each vendor creates things their own way so there is a lot of difference in functionality between vendor apps.
The fact that the controller can connect to the wireless router indicates the problem does not rely with the firmware, but with the Hotspot. It is probable that there is some hotspot config setting that may be needed for the ESP32, that the router allows, but Hotspot on Windows does not.
Having delved into the Wifi side of ESP32 a little, there is a lot going on, monitoring beacons etc, channel switching etc. ESP32 uses beacons to start-up the WiFi before sending, as well as detecting Beacons from the router that it uses to prepare for an incoming message.
I doubt that the hotspot actually functions as a proper router. Phones are much less fussy than the ESP32, hence phones can connect and the ESP32 does not.
I presume that you want the controller to connect to an observator pc, rather than connect directly to the router. This assumption might be wrong. There should be little or no difference in response times using a router connection vs a hotspot connection. So I am not sure why you want to use a Hotspot.
Static IP's (the range in use) is part of the router config (a decent router).
Many (most) Wireless routers only let you assign a Static IP to the router itself, where the IP is determined by the Internet Service Provider.
If the router can allow you to set the Lease time, then the lease time is set to the maximum which should allow the controller to use the same IP address over and over again. If the lease time is too short < 24 hours, and the controller is only used like a couple of times a week, then the IP address will definately change.
I attach a PDF page from a DLINK DIR-1210 WiFi router, which can assign Static IP's to WiFi clients. Not all routers can do this. You would need to "login" to the router or read the pdf to ascertain if the router you are using can support client static IP's.
Regards
Robert
---------------------------------------------------------------------30913-Oct-2023---------------------------------------------------------------------ForTMCboardssetinitialvalueofstepmodeto1/4Improvehpswcode,moveupdatefromloop()tomyBoards.cppFixforSSIDindisplaystoalsoshowACCESSPOINTSSIDFixforDisplayGraphic/TextnotshowingFahrenheittemperature---------------------------------------------------------------------308-0008-Oct-2023---------------------------------------------------------------------Sketchuses1042777bytes(79%)ofprogramstoragespace.Maximumis1310720bytes.Globalvariablesuse46376bytes(14%)ofdynamicmemoryAddSendMyHeader()toManagementServer(reducecodespace)Addalpacasrvr_statusAddcheckforboardpinwhenstartingtemperatureprobeAddtemp_comp_enableandtemp_comp_availabeto.inoandaddhelpersAddtempcomponloadtoControllerDatasotempcompcanbeenabledwhentempprobestartedAddtempcomponloadto/admin8management_serverpageAddxhtmltowebserverandmanagement_serverforHEAPAlignpagesona16bitboundaryCacheboardpinsintolocalisedvarsdriver_board.cppChangepagelayoutfor/admin4,/admin5,admin7,admin8,admin9DeletetempcompavailableandtempcompenablefromControllerDataasthesearenotpersistentDeleteunreferenced/orphaneddefinesandvariablesDeprecateHPSWMessages(nowhandledbyDebugServer)FixAlpacaServerstop()FixAlpacaServercheckclientsFixDebugserverportinitialisationFixDuckDNSstartnotsettingDuckDNSrefreshtimeFixpotentialcrashindriver_board.cppwhenmovingfocuserandusingManagement/WebServerFixpotentialcrashiftempprobenotstartedcorrectlyFixset_tempcomp_state()andset_tempcomp_available()FixforWebServerMovenotmovingmotorMovetempcompavailableandtempcompstatetoruntimeanddeletedfromControllerDataMoveishexdigit()intomainfile(referencedinmanagement_server.cppandweb_server.cpp)RenameASCOMALPACAvarsandnamestoALPACAReplace'$'occurrenceswith_RTOKENtcpip_server.cpp---------------------------------------------------------------------307---------------------------------------------------------------------AddWifireconnectController_configchangesforENABLE_TEXTDISPLAYandENABLE_GRAPHICDISPLAYChangestocontroller_data.cpparoundsavingconfigurationsettingsFixget?hpsw=(missingclosingjsonbrace)Fixget/cntlr_config.jsnintcpip_server.cpp---------------------------------------------------------------------306-0615-Aug-2023---------------------------------------------------------------------Adddebugserver---------------------------------------------------------------------306-0514-Aug-2023---------------------------------------------------------------------AddLinkspagetoManagementServerAddMovepagetoManagementServerAdd[Links][Move][Save]tobottomof/admin1pageFixfornotfoundissuesinweb_server.cpp-relatedto.icoFixforcompilationerrorforTMC2225Use#defines to limit inclusion of unnecessary driver code (driver_board.cpp)
The reason I want to connect via Hotspot is that I have a mobile setup that I take with me to places where I don't have access to a router. I have no desire to take a router with me when I go to the mountains to take pictures. My setup loses flexibility if I depend on a router to be able to use autofocus. Hotspot is used for remote desktop via tablet out in the field, for polar alignment and N.I.N.A.
When I'm at home, I control N.I.N.A from my laptop after I've finished polar alignment.
I will investigate further into the problem of connecting via hotspot, I assume that the problem is that it does not have its own DHCP server. There are also relatively few opportunities to make changes that you can make on a router. I haven't had time to familiarize myself with the hotspot setup in Windows, so it may be that there are more options than I think. I have some experience from setting up networks, but it has been many years since I knew how (openWRT).
When it comes to 306.07 I have no idea why it doesn't work. Serial output from ESP32 makes no sense. It only shows status on pins, and there all show 255... I have considered adding some serial print in the code to see where it stops. After looking through the code, I see that it is quite a lot more complex than the programs I have created myself. (I only program when I have a project for myself)
I'd like to look at 309, but I'm not familiar enough with the code to be able to give any good feedback as of today.
I haven't had time to familiarize myself with the PDF, but I can't find anything in the code that makes it possible to use USB/serial with ASCOM. Don't see the choice in controller_config, but hopefully I won't have to go that route.
Thank you so much for an amazing job you have done!!!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
For the esp32, the serial port is used for debugging and controlled by the debug server.
You could run the controller in ACCESSPOINT, and devices could log into it. And if the ALPACA server is running, then you can connect using an ascom remote client - this is easy to setup, and works with NINA https://www.youtube.com/watch?v=KklTVEl25hs
If you have already solved the issue, please let me know what was done to oversome it,
Many thanks
Robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am precisely in the same situation as my colleague. I have put it elsewhere in the forum because I am in exactly the same situation (Mele minipc). Because of this, I have also asked about the bluetooth connection
All the best
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello.
I'm having trouble connecting to the hotspot on my MELE overclock (windows 11 pro). I have no problems connecting to the router on my home network.
I have tried several times to change the SSID and password on the hotspot and in stationmode_defines.h.
Does anyone know why I can't connect to the hotspot?
I'm using myfp2esp32firmware-304, as I haven't been able to get myfp2esp32-firmware-306-07 to work
I have tested with the hotspot set up with 2.4GHz / 5GHz and only 2.4GHz. I haven't tried with a static IP, because I don't know if I can decide which IP range the hotspot should use. I use the Windows app Hotspot and resilientHotspot.
Hi
I cannot help re firmware 304.
I note that 306 is available on SF in the files area. You indicate that you could not get it to work. If you have an issue, that is why I am here, all you need to do is ask either by email to gmail or by a post here.
However, v309 firmware is available for testing: send me an email (not on SF) and I will arrange access, then we can go from there. The list of fixes from 304 to 309 are listed at the end of this reply.
Hotspots have never been tested by me. They introduce another layer that differs so much from vendor to vendor. A hotspot is not the same as a router connection and does not pretend to be a "router" connection. Each vendor creates things their own way so there is a lot of difference in functionality between vendor apps.
The fact that the controller can connect to the wireless router indicates the problem does not rely with the firmware, but with the Hotspot. It is probable that there is some hotspot config setting that may be needed for the ESP32, that the router allows, but Hotspot on Windows does not.
Having delved into the Wifi side of ESP32 a little, there is a lot going on, monitoring beacons etc, channel switching etc. ESP32 uses beacons to start-up the WiFi before sending, as well as detecting Beacons from the router that it uses to prepare for an incoming message.
I doubt that the hotspot actually functions as a proper router. Phones are much less fussy than the ESP32, hence phones can connect and the ESP32 does not.
I presume that you want the controller to connect to an observator pc, rather than connect directly to the router. This assumption might be wrong. There should be little or no difference in response times using a router connection vs a hotspot connection. So I am not sure why you want to use a Hotspot.
Static IP's (the range in use) is part of the router config (a decent router).
Many (most) Wireless routers only let you assign a Static IP to the router itself, where the IP is determined by the Internet Service Provider.
If the router can allow you to set the Lease time, then the lease time is set to the maximum which should allow the controller to use the same IP address over and over again. If the lease time is too short < 24 hours, and the controller is only used like a couple of times a week, then the IP address will definately change.
I attach a PDF page from a DLINK DIR-1210 WiFi router, which can assign Static IP's to WiFi clients. Not all routers can do this. You would need to "login" to the router or read the pdf to ascertain if the router you are using can support client static IP's.
Regards
Robert
Last edit: brownrb 2023-11-09
Thanks for the detailed answer.
The reason I want to connect via Hotspot is that I have a mobile setup that I take with me to places where I don't have access to a router. I have no desire to take a router with me when I go to the mountains to take pictures. My setup loses flexibility if I depend on a router to be able to use autofocus. Hotspot is used for remote desktop via tablet out in the field, for polar alignment and N.I.N.A.
When I'm at home, I control N.I.N.A from my laptop after I've finished polar alignment.
I will investigate further into the problem of connecting via hotspot, I assume that the problem is that it does not have its own DHCP server. There are also relatively few opportunities to make changes that you can make on a router. I haven't had time to familiarize myself with the hotspot setup in Windows, so it may be that there are more options than I think. I have some experience from setting up networks, but it has been many years since I knew how (openWRT).
When it comes to 306.07 I have no idea why it doesn't work. Serial output from ESP32 makes no sense. It only shows status on pins, and there all show 255... I have considered adding some serial print in the code to see where it stops. After looking through the code, I see that it is quite a lot more complex than the programs I have created myself. (I only program when I have a project for myself)
I'd like to look at 309, but I'm not familiar enough with the code to be able to give any good feedback as of today.
I haven't had time to familiarize myself with the PDF, but I can't find anything in the code that makes it possible to use USB/serial with ASCOM. Don't see the choice in controller_config, but hopefully I won't have to go that route.
Thank you so much for an amazing job you have done!!!
Hi
Serial support was dropped some time ago.
Please note that the myfp2esp8266 wifi project does support serial connections
https://sourceforge.net/projects/myfp2esp8266-focus-controller/
For the esp32, the serial port is used for debugging and controlled by the debug server.
You could run the controller in ACCESSPOINT, and devices could log into it. And if the ALPACA server is running, then you can connect using an ascom remote client - this is easy to setup, and works with NINA
https://www.youtube.com/watch?v=KklTVEl25hs
If you have already solved the issue, please let me know what was done to oversome it,
Many thanks
Robert
I am precisely in the same situation as my colleague. I have put it elsewhere in the forum because I am in exactly the same situation (Mele minipc). Because of this, I have also asked about the bluetooth connection
All the best