I was having intermittent issues with WiFi an decided to move my controller to a Serial.
I reprogrammed with the latest firmware Release 230-1. Configured with MYFP2ESP_PROTOCOL.
I updated the ASCOM deriver, but honestly not sure which file to install from the SourceFoge repo as it has two :
myFP2ESPASCOMv208.exe
myFP2ESPASCOM1v208.exe
Nina connects first time and all seems good.
The issue however is if I hit the disconnect button on Nina, then I am not able to reconnect again. Looks like the port is not being released properly in the ASCOM. The behavior is the Same if I use the ASCOM testing tools.
The MyFocuser Windows app is perfectly connects and disconnects wit no issue.
Hi Clifford
myFP2ESPASCOMv208.exe
is the main one.
myFP2ESPASCOM1v208.exe
is used for a second focuser if you have one.
Like the main one I would use on my imaging scope and the send one for my guide scope running phd2
Just a word about the next release, Serial mode and Blue tooth mode will be dropped.
I am not aware of any outstanding issue, however, what I would require is to enable the trace log in the ascom driver - it is a checkbox, then logs will go to users documents/ascom/logs folder
In Nina it is possible to get some helpful info
Options, General, Log level, Trace
Set the device polling interval to 2
Next to the log level is a text search icon, click this to find out where the nina logs are stored.
After that, connect to the focuser - and this will start the log files, then do your test like disconnect and then attempt to reconnect. Then send me the ascom log files and the nina logs
Thanks will do a test with the otter driver and let you know.
Just out of interest does the WiFi diver reconnect if it gets disconnected. I don't have a log file but I noticed that every now and again the focusers woudl disconnect and remain so. When in this state the myfocuser web page was available and the if I hit connect in NINA it would connect again.
It might be nice to reconnect automatically, for those imaging secessions that last hours.
Cliff
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Cliff
Any device like a focuser etc, cannot initiate any connection. They are response devices onyl, and have no awareness of anything else on the network.
if the web page is responding, the controller is still running WiFi and has a connection to the network, else if the controller had lost its wifi connection then you could not access the webserver, because the webserver service depends on wifi to run.
If the focuser lost its wifi connection then nothing would respond. a reboot would have to occur in order to reload the wifi - there really is no way to turn wifi on and off.
There maybe something on the network etc that is causing the disconnect,
There is nothing in the ASCOM protocol about a "keep alive" - this is common in TCPIP but alpaca and ascom do not have it. A keep alive is where an application can send a query at timed intervals basically saying :you there? still connected? and the controller replies. I have that in some of the drivers that use tcpip.
There are a number of areas to look about this disconnect
1. look at the NINA logs, around the time of the disconnect, there maybe something in the log file.
2. check network routers etc, for any other activity at the time
3. If you are using the ASCOM driver, enable tracing and then you can see from the trace log what happened.
To look at an issue like that, you need the logs from ASCOM driver and NINA, as well as look at the configuration of the controller.
I am assuming that you are running NINA, the ASCOM driver (configured to TCP/IP) and have not changed any of the port values.
regards
Robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
HI Robert
I was having intermittent issues with WiFi an decided to move my controller to a Serial.
I reprogrammed with the latest firmware Release 230-1. Configured with MYFP2ESP_PROTOCOL.
I updated the ASCOM deriver, but honestly not sure which file to install from the SourceFoge repo as it has two :
Nina connects first time and all seems good.
The issue however is if I hit the disconnect button on Nina, then I am not able to reconnect again. Looks like the port is not being released properly in the ASCOM. The behavior is the Same if I use the ASCOM testing tools.
The MyFocuser Windows app is perfectly connects and disconnects wit no issue.
Let me know if yo have any ideas ?
Cliff
Last edit: Clifford de Wit 2022-03-30
Hi Clifford
myFP2ESPASCOMv208.exe
is the main one.
myFP2ESPASCOM1v208.exe
is used for a second focuser if you have one.
Like the main one I would use on my imaging scope and the send one for my guide scope running phd2
Just a word about the next release, Serial mode and Blue tooth mode will be dropped.
I am not aware of any outstanding issue, however, what I would require is to enable the trace log in the ascom driver - it is a checkbox, then logs will go to users documents/ascom/logs folder
In Nina it is possible to get some helpful info
Options, General, Log level, Trace
Set the device polling interval to 2
Next to the log level is a text search icon, click this to find out where the nina logs are stored.
After that, connect to the focuser - and this will start the log files, then do your test like disconnect and then attempt to reconnect. Then send me the ascom log files and the nina logs
Regards
Robert
If the controller is in serial mode, you can load up the ascom driver for myFocuserPro2 and use that,
here is a link to the file
https://sourceforge.net/projects/arduinoascomfocuserpro2diy/files/ASCOM%20DRIVERS/myFP2ASCOM_Setup284.exe/download
It would be interesting to see if the problem occurs with that driver also?
Not able to run the test myself at present, long story, and you can email me direct at yahoo or gmail is that helps (in the pdf and firmware).
Cheers
Robert
HI Robert
Thanks will do a test with the otter driver and let you know.
Just out of interest does the WiFi diver reconnect if it gets disconnected. I don't have a log file but I noticed that every now and again the focusers woudl disconnect and remain so. When in this state the myfocuser web page was available and the if I hit connect in NINA it would connect again.
It might be nice to reconnect automatically, for those imaging secessions that last hours.
Cliff
Hi Cliff
Any device like a focuser etc, cannot initiate any connection. They are response devices onyl, and have no awareness of anything else on the network.
if the web page is responding, the controller is still running WiFi and has a connection to the network, else if the controller had lost its wifi connection then you could not access the webserver, because the webserver service depends on wifi to run.
If the focuser lost its wifi connection then nothing would respond. a reboot would have to occur in order to reload the wifi - there really is no way to turn wifi on and off.
There maybe something on the network etc that is causing the disconnect,
There is nothing in the ASCOM protocol about a "keep alive" - this is common in TCPIP but alpaca and ascom do not have it. A keep alive is where an application can send a query at timed intervals basically saying :you there? still connected? and the controller replies. I have that in some of the drivers that use tcpip.
There are a number of areas to look about this disconnect
1. look at the NINA logs, around the time of the disconnect, there maybe something in the log file.
2. check network routers etc, for any other activity at the time
3. If you are using the ASCOM driver, enable tracing and then you can see from the trace log what happened.
To look at an issue like that, you need the logs from ASCOM driver and NINA, as well as look at the configuration of the controller.
I am assuming that you are running NINA, the ASCOM driver (configured to TCP/IP) and have not changed any of the port values.
regards
Robert