I have aquired a new scope with a myFocuserPro2 powered focuser.
I have installed the ASCOM driver (v269) and the Windows application (v2.4.3.9) on my Windows10 observatory PC.
I can connect the Windows app to the focuser hardware with no problems, but can not connect any other software to the focuser.
I am imaging with Voyager, but can not connect to focuser.
To keep things simple, I used POTH to debug the connectiopn issue. I can't connect with POTH, even when replicating the setup parameters that the myFocuserPro2 application uses. COM8, 9600, and all other common between the app and the ASCOM driver setup dialog.
I disconnected the app before trying to connect from POTH, but the ASCOM driver reports
"Error connecting to focuser. 80131500 - ASCOM.myFocuser2ASCOM.Focuser Cannot connect to controller".
Have re-booted, re-installed the myFocuserPro2 ASCOM driver, ...
Appreciate any help available.
Tom
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Then run it. Enable logging (Settings, Logfile, Enable). Choose the ASCOM driver - in the setup enable Trace logging (checkbox Trace lOn).
Set all the parameters correctly (comport, speed=9600)
Then connect to the focuser.
If it connects or timesouts, either way, send me the ascom app logfile (myASCOMAPPLog-xx102019.txt) and the ascom trace files (found in Documents\ASCOM\Logs xxxx\ and is something like ASCOM.myFocuserPro2xxxxxxxx.txt
regards
Robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Then run it. Enable logging (Settings, Logfile, Enable). Choose the ASCOM
driver - in the setup enable Trace logging (checkbox Trace lOn).
Set all the parameters correctly (comport, speed=9600)
Then connect to the focuser.
If it connects or timesouts, either way, send me the ascom app logfile
(myASCOMAPPLog-xx102019.txt) and the ascom trace files (found in
Documents\ASCOM\Logs xxxx\ and is something like
ASCOM.myFocuserPro2xxxxxxxx.txt
Hi Robert, and all.
Has this issue been resolved? I noticed that it is over a year old now but no mention of the MyFocuserPro2 working in Voyager. The reason I ask is because I am now using Voyager to control my Observatory and Image acquisition but cannot use my MyfocuserPro2-M (The one you built for me Robert). The focuser works fine through the windows application, which is Version 2.4.4.3, but I cannot use it with the Ascom driver through Voyager. I will also be sending info to the Voyager Team, hoping for a fix.
Anyway, sorry for hacking into this thread but it seemed relevant or at least the same problem.
Andrew.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Andrew
You need to enable TRACE ON in the ASCOM setup driver -
This creates a logfile in Documents\ASCOM\logs\xxxx
Then try and connect with voyager and send me the trace file.
Please install the latest ascom driver before doing this as I can only fix the "latest" driver.
That way we find out what is happening.
Its strange because everything else, as far as I know can connect to the ascom driver without issue.
regards
Robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I have aquired a new scope with a myFocuserPro2 powered focuser.
I have installed the ASCOM driver (v269) and the Windows application (v2.4.3.9) on my Windows10 observatory PC.
I can connect the Windows app to the focuser hardware with no problems, but can not connect any other software to the focuser.
I am imaging with Voyager, but can not connect to focuser.
To keep things simple, I used POTH to debug the connectiopn issue. I can't connect with POTH, even when replicating the setup parameters that the myFocuserPro2 application uses. COM8, 9600, and all other common between the app and the ASCOM driver setup dialog.
I disconnected the app before trying to connect from POTH, but the ASCOM driver reports
"Error connecting to focuser. 80131500 - ASCOM.myFocuser2ASCOM.Focuser Cannot connect to controller".
Have re-booted, re-installed the myFocuserPro2 ASCOM driver, ...
Appreciate any help available.
Tom
Hi Tom
My email address is in the firmware file.
Download this ASCOM APP tester
https://sourceforge.net/projects/arduinoascomfocuserpro2diy/files/ASCOM%20DRIVER%20TESTER/myFocuserProASCOMApp_1_3_1_6.zip/download
Install it.
Then run it. Enable logging (Settings, Logfile, Enable). Choose the ASCOM driver - in the setup enable Trace logging (checkbox Trace lOn).
Set all the parameters correctly (comport, speed=9600)
Then connect to the focuser.
If it connects or timesouts, either way, send me the ascom app logfile (myASCOMAPPLog-xx102019.txt) and the ascom trace files (found in Documents\ASCOM\Logs xxxx\ and is something like ASCOM.myFocuserPro2xxxxxxxx.txt
regards
Robert
Tom Fowler fowler.tw@gmail.com
[image: Attachments]19:59 (1 minute ago)
to [arduinoascomfocuserpro2diy:discussion]
Hi Robert,
Please find the logs attached.
As I mentioned in my forum post, the myFocuserPro2 Windows app does connect
without problem using apparently identical driver options.
Thank you for the support.
Tom
Tom Fowler
M: +61 411 776 346
On Tue, 15 Oct 2019 at 10:45, brownrb brownrb@users.sourceforge.net wrote:
upgrade the Windows app to Wndows application (v2.4.3.10)
Hi Tom
The controller firmware has been modified and is invalid.
Can you please post some photos of the controller?
Where did you get it from?
Do you have the controller firmware file?
Regards
Robert
Last edit: brownrb 2019-10-15
Hi Robert, and all.
Has this issue been resolved? I noticed that it is over a year old now but no mention of the MyFocuserPro2 working in Voyager. The reason I ask is because I am now using Voyager to control my Observatory and Image acquisition but cannot use my MyfocuserPro2-M (The one you built for me Robert). The focuser works fine through the windows application, which is Version 2.4.4.3, but I cannot use it with the Ascom driver through Voyager. I will also be sending info to the Voyager Team, hoping for a fix.
Anyway, sorry for hacking into this thread but it seemed relevant or at least the same problem.
Andrew.
I note that I was using ASCOM driver 270, I have installed v276 to give that a try. Still using the original Firmware that came with the controller.
Hi Andrew
You need to enable TRACE ON in the ASCOM setup driver -
This creates a logfile in Documents\ASCOM\logs\xxxx
Then try and connect with voyager and send me the trace file.
Please install the latest ascom driver before doing this as I can only fix the "latest" driver.
That way we find out what is happening.
Its strange because everything else, as far as I know can connect to the ascom driver without issue.
regards
Robert