the range on my ESP8266 was horrible so I have set up an ESP32 board to try. After much effort to learn and set up arduino IDE for ESP32, I finally have the firmware uploaded and working. I first tested with serial connection to ensure everything was working. However, the only way I could get it to connect reliably with USB/serial was to disable "reset controller on connect".
I then tried bluetooth which worked as well.
After serial was now working perfectly, I setup the firmware for wifi with a static address. The board shows up on wifi scanner at the correct ip static address as confirmed by mac address and I can ping it.
however when I try to connect by the windows myfp2esp software at the assigned ip with port 2020, I get a socket exception error then a pop up - cannot connect to controller. I set the socket timeout to 3000, but this all happens very quickly - within 1-2 sec so I am not sure if this is a time out.
I tried access point mode. There I can connect to the access point wifi with my computer without error. but when I try to connect with the myFP2esp, there is a delay as it tries to connect then I get a message of "not connected, is controller running"
the only thing I can think of is maybe the connection tries to reset the controller ?? which from my troubleshooting the serial connection with my ESP board screws up the connection? I have set the board to PRO2ESP32R3WEMOS, but also tried the PRO2ESP32DRV8825 with same effect
I tried to access the managment server at port 6060 and I reached a page that says "url not found" but it had a button for "homepage" which didn't work
any advice ?
thanks and happy holidays and happy new year.
Al
Last edit: Al ros 2020-12-25
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
One thing at a time. We cannot hope to resolve everything at once. That is like trying to find a needle in a very very large haystack.
If we break things down a bit, and first test something that we should be able to resolve first, then it pave the wave to helping address other issues too.
Let us focus first on ACCESSPOINT MODE.
Itriedaccesspointmode. ThereIcanconnecttotheaccesspointwifiwithmycomputerwithouterror. butwhenItrytoconnectwiththemyFP2esp, thereisadelayasittriestoconnectthenIgetamessageof"not connected, is controller running"
So you will need to provide, as outlined in the early pages of the pdf some information. Because I am not looking over your shoulder, I cannot see what is happening. Let alone what firmware version or config you have. And I do not know what version of the windows app you have, let alone a log file from myFP2ESP.
So I am pretty much blindfolded trying to guess what might be happening. The more information I have the better I can help you.
If you are not running the latest firmware and the latest windows tcpip app, then update to those now. It is best to uninstall the windows app first using control panel, then install the latest version/
So I am looking for your focuserconfig.h file as a starter. I assume you connect successfully to the AccessPoint, but when you run the myFP2ESP TCPIP program it does not connect/ So you will need to enable logging in that application, then try to connect, and after an unsuccess connection close the app and also send me the errorlog file produced by the windows app.
But for starters, ignoring all else, let us start with accesspoint and using the myFP2ESP TCPIP windows app and sort out that connection problem before addressing any other issues.
I am happy for you to email me at gmail or yahoo. Address is in the firmware file or PDF.
regards
Robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks very much Robert. I do apologize for the long post, I was hoping the more information I gave might help narrow the possibilities as the firmware was working with Serial connection But not wifi.Sorry for making it seem overwhelming. I am on latest firmware and latest windows apps. I also tried stepping back to v34. I am on latest updated windows 10. You are correct in both accesspoin I am able to connect My computer, but the app doesn't connect to controller. In stationmode. I can see the controller has successfully connected to my router, but again the app doesn't connect.
I overlooked updating the data file - I will read up on how to do that. If it doesn't solve things, I will take you up on the offer to email you my logs.
Thanks and happy holidays and happy new year
Al
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Update
apologies, I had overlooked the step of needing to upload the data after flashing firmware. with that completed in access mode, I am able to reach the management console and adjust settings. I am also able to start the webserver and control the focuser using the move commands.
however, I still can't connect using the latest version of the myFP2esp at the default 192.168.4.1:2020 (same for the ascom driver).
I am using the "myFP2ESP32 R3 WEMOS ESP32 CH340G SOLDERLESS SOLUTION" with my generic ESP32. with out any additional attachments such as temperature. Just the ESP32, driver board and stepper motor.
Hi Al
happy to assist.
Focus on one issue.
In Ap mode, you can connect your computer to the 192.168.4.1 controller AP
Then you run the Windows TCP/IP using 192.168.4.1 and port 2020
But the windows app does not connect.
So lets focus on this specific issue. Forget about ASCOm and trying other things.
So in the windows app,start the windows app, enable error logging on the loggging tab
Then goto connection tab, check ip and port number is correct then click Connect
If it times out etc, then exit the windows app.
Then send me the errorlog and the focuserconfig.h file
Regards
Robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi
the range on my ESP8266 was horrible so I have set up an ESP32 board to try. After much effort to learn and set up arduino IDE for ESP32, I finally have the firmware uploaded and working. I first tested with serial connection to ensure everything was working. However, the only way I could get it to connect reliably with USB/serial was to disable "reset controller on connect".
I then tried bluetooth which worked as well.
After serial was now working perfectly, I setup the firmware for wifi with a static address. The board shows up on wifi scanner at the correct ip static address as confirmed by mac address and I can ping it.
however when I try to connect by the windows myfp2esp software at the assigned ip with port 2020, I get a socket exception error then a pop up - cannot connect to controller. I set the socket timeout to 3000, but this all happens very quickly - within 1-2 sec so I am not sure if this is a time out.
I tried access point mode. There I can connect to the access point wifi with my computer without error. but when I try to connect with the myFP2esp, there is a delay as it tries to connect then I get a message of "not connected, is controller running"
the only thing I can think of is maybe the connection tries to reset the controller ?? which from my troubleshooting the serial connection with my ESP board screws up the connection? I have set the board to PRO2ESP32R3WEMOS, but also tried the PRO2ESP32DRV8825 with same effect
I tried to access the managment server at port 6060 and I reached a page that says "url not found" but it had a button for "homepage" which didn't work
any advice ?
thanks and happy holidays and happy new year.
Al
Last edit: Al ros 2020-12-25
One thing at a time. We cannot hope to resolve everything at once. That is like trying to find a needle in a very very large haystack.
If we break things down a bit, and first test something that we should be able to resolve first, then it pave the wave to helping address other issues too.
Let us focus first on ACCESSPOINT MODE.
So you will need to provide, as outlined in the early pages of the pdf some information. Because I am not looking over your shoulder, I cannot see what is happening. Let alone what firmware version or config you have. And I do not know what version of the windows app you have, let alone a log file from myFP2ESP.
So I am pretty much blindfolded trying to guess what might be happening. The more information I have the better I can help you.
If you are not running the latest firmware and the latest windows tcpip app, then update to those now. It is best to uninstall the windows app first using control panel, then install the latest version/
So I am looking for your focuserconfig.h file as a starter. I assume you connect successfully to the AccessPoint, but when you run the myFP2ESP TCPIP program it does not connect/ So you will need to enable logging in that application, then try to connect, and after an unsuccess connection close the app and also send me the errorlog file produced by the windows app.
I also assume you have watched the wifi videos for the controller at
https://www.youtube.com/channel/UCPd7bXRv2QGeMAKHZvG1PsA
which demonstrates connection to accesspoint as well as staionmode.
But for starters, ignoring all else, let us start with accesspoint and using the myFP2ESP TCPIP windows app and sort out that connection problem before addressing any other issues.
I am happy for you to email me at gmail or yahoo. Address is in the firmware file or PDF.
regards
Robert
And remember, after uploading the firmware, you must also update the data files as shown in the pdf. Eachand every time.
Thanks very much Robert. I do apologize for the long post, I was hoping the more information I gave might help narrow the possibilities as the firmware was working with Serial connection But not wifi.Sorry for making it seem overwhelming. I am on latest firmware and latest windows apps. I also tried stepping back to v34. I am on latest updated windows 10. You are correct in both accesspoin I am able to connect My computer, but the app doesn't connect to controller. In stationmode. I can see the controller has successfully connected to my router, but again the app doesn't connect.
I overlooked updating the data file - I will read up on how to do that. If it doesn't solve things, I will take you up on the offer to email you my logs.
Thanks and happy holidays and happy new year
Al
Update
apologies, I had overlooked the step of needing to upload the data after flashing firmware. with that completed in access mode, I am able to reach the management console and adjust settings. I am also able to start the webserver and control the focuser using the move commands.
however, I still can't connect using the latest version of the myFP2esp at the default 192.168.4.1:2020 (same for the ascom driver).
I am using the "myFP2ESP32 R3 WEMOS ESP32 CH340G SOLDERLESS SOLUTION" with my generic ESP32. with out any additional attachments such as temperature. Just the ESP32, driver board and stepper motor.
the actual ESP is this one: https://www.amazon.ca/SeeKool-Development-Microcontroller-Integrated-Compatible/dp/B07NPJJ8ZC/ref=sr_1_1_sspa?dchild=1&keywords=esp32&qid=1608905000&sr=8-1-spons&psc=1&spLa=ZW5jcnlwdGVkUXVhbGlmaWVyPUEySE1CVzBaRldaQ0w5JmVuY3J5cHRlZElkPUExMDE1MjE1Mzk2QVZFTU1SQU02RCZlbmNyeXB0ZWRBZElkPUEwNTE4NTQ4MTIzSzlHOUc1TEVSWiZ3aWRnZXROYW1lPXNwX2F0ZiZhY3Rpb249Y2xpY2tSZWRpcmVjdCZkb05vdExvZ0NsaWNrPXRydWU=
will definitely be making another contribution to the cause.
thanks for your assistance
Al
Hi Al
happy to assist.
Focus on one issue.
In Ap mode, you can connect your computer to the 192.168.4.1 controller AP
Then you run the Windows TCP/IP using 192.168.4.1 and port 2020
But the windows app does not connect.
So lets focus on this specific issue. Forget about ASCOm and trying other things.
So in the windows app,start the windows app, enable error logging on the loggging tab
Then goto connection tab, check ip and port number is correct then click Connect
If it times out etc, then exit the windows app.
Then send me the errorlog and the focuserconfig.h file
Regards
Robert
Thanks - All sent to your email. Also please keep in mind that I have an ESP8266 that works fine with the same windows app.
best regards
Al
Thanks for your help. the updated windows app has solved the issue.
Al