Hi everyone. Thank you very much for this great project.
When I want to test myfocuser with myfocuserproAscom.app;
Ascom focuser chooser says;
Incompatible driver
Can not find the driver executable:
"file:///C:/Program Files (x86)/Common Files/ASCOM/Focuser/ASCOM.myfocuser2ASCOM.focuser.DLL"
Actually the file location is correct (checked) and I've already installed the driver(myFocuser2ASCOMSetup250.exe) .
I am using Ascom Platform 6.3 and the newest drivers in files section.
What am i missing?
Thank you very much.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi
I recommend using the latest versions.
Uninstall the ASCOM driver
Restart the computer
Reinstall the latest ASCOM driver v253
If you have antivirus software installed I highly recommend you disable it before installing the driver. After installing the driver you may need to check your antivirus software to ensure the program/driver can run properly - Bitdefender has known issues in this area and will prevent it starting if Safe Files is enabled for your Documents folder.
The driver runs on both 32/64bit machines. I assume you are running Win10 64bit?
When you run ASCOMApp, do you get to see the chooser?
Can you then select the driver in ASCOMApp?
Can you bring up the setupdialog main screen of the focuser driver which shows the properties?
If you can then turn on Tracing
Is the message appears when you try to "Connect" - clicking Connect in the ASCOMApp or does it happen before this?
If it happens at Connect, look in the Documents\ASCOM\Logs xxxxx folder and send me the latest ASCOM trace log file.
Regards
Robert
Last edit: brownrb 2018-04-03
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Robert,
I followed your instructions but still having the same problem.
I am running Win7, 64 bit. Is this the problem?
When I run ASCOMApp, I see the chooser.
With the ASCOM Focuser Chooser, I can see the "myFocuserPro2ASCOM" in the scroll down menu BUT;
once I choose it, it gives the error "Incompatible Driver" error.
I can not click the "properties or OK" and can not see the setup dialog. So the story ends for me :(
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You can try the ASCOM Diagnostics program that is installed whrn u installed ASCOM to verify your installation. Please send me the trace file.
You can also try the ASCOM Focus Simulator to see if that is working also.
If you have a client app like Nebulosity, APT, BackyardEOS, Maxim, SGP etc you could try using that to see if it will connect to the focuser driver. My preliminary suspicion is that there is something wrong with your ASCOM installation.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I can see from the logfile that the ASCOMdriver is recognized and accessible.
"Simulator" works but "Ascom Simulator Focuser Driver" gives the same error.
It would appear that your ASCOM installation has an issue. You need to goto the yahoo group ASCOM-Talk and perhaps they will have an answer. This is not specific to my ASCOM driver, if, as you have indicated, it is also appearing with the Simulator, then its indicitive of a much bigger underlying problem.
09:44:59.906 FileDetails C:\Program Files (x86)\Common Files\ASCOM\Focuser\ASCOM.myFocuser2ASCOM.Focuser.dll
09:44:59.906 FileDetails Assembly Version: ASCOM.myFocuser2ASCOM.Focuser, Version=6.0.6667.31181, Culture=neutral, PublicKeyToken=5a596dde3293c610
09:44:59.906 FileDetails Assembly Framework: v4.0.30319
09:44:59.906 FileDetails File Version: 6.0.0.0
09:44:59.906 FileDetails Product Version: 6.0.0.0
09:44:59.906 FileDetails Description: ASCOM.myFocuser2ASCOM.Focuser
09:44:59.906 FileDetails Company Name: RBB
09:44:59.906 FileDetails Last Write Time: 03.04.2018 16:19:22
09:44:59.906 FileDetails Creation Time: 03.04.2018 09:31:44
09:44:59.906 FileDetails File Length: 418,304
09:44:59.906 FileDetails Attributes: Archive
09:44:59.906 PEReader Running within CLR version: v4.0.30319
09:44:59.906 PEReader Filename to check: C:\Program Files (x86)\Common Files\ASCOM\Focuser\ASCOM.myFocuser2ASCOM.Focuser.dll
09:44:59.906 PEReader Determining whether this is an assembly
09:44:59.906 PEReader.IsAssembly Found an assembly because it loaded Ok to the reflection context: True
09:44:59.906 PEReader Determining PE Machine type
09:44:59.906 PEReader.MachineType Machine - found "Intel 32bit" executable. Characteristics: 00002102, OS32BitCompatible: True
09:44:59.906 PEReader.MachineType Reading optional 32bit header
09:44:59.906 PEReader This is an assembly, determining Bitness through the CLR header
09:44:59.906 PEReader.Bitness This is a 32 bit assembly, reading the CLR Header
09:44:59.906 PEReader.Bitness Checking 16 headers
09:44:59.906 PEReader.Bitness Found "MSIL" assembly
09:44:59.906 PEReader Assembly required Runtime version: 2.5
09:44:59.906 PE.IsDotNetAssembly Returning: True
09:44:59.906 FileDetails .NET Assembly: True
09:44:59.906 PE.BitNess Returning: 2
09:44:59.906 FileDetails Bitness: BitsMSIL
09:44:59.906 PE.SubSystem Returning 32bit value: WINDOWS_CUI
09:44:59.906 FileDetails Subsystem: WINDOWS_CUI**
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello Robert,
As we expected, the problem was related with ASCOM platform not with your driver. But still wanted to put the solution here. Because it may also effect your project.
In windows; Regional Date Seperator format for Turkey is "dot." I think it causes a problem. Because, if I change the format to English everything work flawlessly.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes I saw the response in the ASCOM group. Great thinking!
What I can confirm is that the myfocuserpro2 driver creates a thread, and changes the threads culture to "eng-us". only affects the display of temp offset and temp values, nothing else. Not the internal processing. This This does not change the OS or other applications, just the focuser thread. So should have zero impact.
Noting that you have exactly the same issue with the ASCOM Focuser Simulator indicates that the issue lies somehow in ASCOM as it is happening with more than one driver, so will be interesting to see what they find.
Regards
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi everyone. Thank you very much for this great project.
When I want to test myfocuser with myfocuserproAscom.app;
Ascom focuser chooser says;
Incompatible driver
Can not find the driver executable:
"file:///C:/Program Files (x86)/Common Files/ASCOM/Focuser/ASCOM.myfocuser2ASCOM.focuser.DLL"
Actually the file location is correct (checked) and I've already installed the driver(myFocuser2ASCOMSetup250.exe) .
I am using Ascom Platform 6.3 and the newest drivers in files section.
What am i missing?
Thank you very much.
Hi
I recommend using the latest versions.
Uninstall the ASCOM driver
Restart the computer
Reinstall the latest ASCOM driver v253
If you have antivirus software installed I highly recommend you disable it before installing the driver. After installing the driver you may need to check your antivirus software to ensure the program/driver can run properly - Bitdefender has known issues in this area and will prevent it starting if Safe Files is enabled for your Documents folder.
The driver runs on both 32/64bit machines. I assume you are running Win10 64bit?
When you run ASCOMApp, do you get to see the chooser?
Can you then select the driver in ASCOMApp?
Can you bring up the setupdialog main screen of the focuser driver which shows the properties?
If you can then turn on Tracing
Is the message appears when you try to "Connect" - clicking Connect in the ASCOMApp or does it happen before this?
If it happens at Connect, look in the Documents\ASCOM\Logs xxxxx folder and send me the latest ASCOM trace log file.
Regards
Robert
Last edit: brownrb 2018-04-03
Hi Robert,
I followed your instructions but still having the same problem.
I am running Win7, 64 bit. Is this the problem?
When I run ASCOMApp, I see the chooser.
With the ASCOM Focuser Chooser, I can see the "myFocuserPro2ASCOM" in the scroll down menu BUT;
once I choose it, it gives the error "Incompatible Driver" error.
I can not click the "properties or OK" and can not see the setup dialog. So the story ends for me :(
Are there any logs in the documents\ascom folder?
You can try the ASCOM Diagnostics program that is installed whrn u installed ASCOM to verify your installation. Please send me the trace file.
You can also try the ASCOM Focus Simulator to see if that is working also.
If you have a client app like Nebulosity, APT, BackyardEOS, Maxim, SGP etc you could try using that to see if it will connect to the focuser driver. My preliminary suspicion is that there is something wrong with your ASCOM installation.
After installing the ASCOM driver, in the folder C:/Program Files (x86)/Common Files/ASCOM/Focuser
you should see the following files.
ASCOM.myFocuser2ASCOM.Focuser.dll
ReadMemyFocuser20.htm
If these files are not there, try running the installer myFocuser2ASCOMSetup254.exe as administrator (right mouse click, Run as administrator
Last edit: brownrb 2018-04-03
Dear Robert,
You can find ascom diagnostic logs attached. There is no other log there.
"Simulator" works but "Ascom Simulator Focuser Driver" gives the same error.
I've already tried APT focuser connection, exact similar issue :(
I reinstalled ASCOM platform 6.3. I uninstalled my antivirus software.
in the folder C:/Program Files (x86)/Common Files/ASCOM/Focuser
I see the files;
ASCOM.myFocuser2ASCOM.Focuser.dll
ReadMemyFocuser20.htm
When I read my comments i feel that all weird. But I am hopeless without your help.
I am sorry taking your time, even I owe you much appreciation with your great project.
I can see from the logfile that the ASCOMdriver is recognized and accessible.
"Simulator" works but "Ascom Simulator Focuser Driver" gives the same error.
It would appear that your ASCOM installation has an issue. You need to goto the yahoo group ASCOM-Talk and perhaps they will have an answer. This is not specific to my ASCOM driver, if, as you have indicated, it is also appearing with the Simulator, then its indicitive of a much bigger underlying problem.
09:44:59.906 FileDetails C:\Program Files (x86)\Common Files\ASCOM\Focuser\ASCOM.myFocuser2ASCOM.Focuser.dll
09:44:59.906 FileDetails Assembly Version: ASCOM.myFocuser2ASCOM.Focuser, Version=6.0.6667.31181, Culture=neutral, PublicKeyToken=5a596dde3293c610
09:44:59.906 FileDetails Assembly Framework: v4.0.30319
09:44:59.906 FileDetails File Version: 6.0.0.0
09:44:59.906 FileDetails Product Version: 6.0.0.0
09:44:59.906 FileDetails Description: ASCOM.myFocuser2ASCOM.Focuser
09:44:59.906 FileDetails Company Name: RBB
09:44:59.906 FileDetails Last Write Time: 03.04.2018 16:19:22
09:44:59.906 FileDetails Creation Time: 03.04.2018 09:31:44
09:44:59.906 FileDetails File Length: 418,304
09:44:59.906 FileDetails Attributes: Archive
09:44:59.906 PEReader Running within CLR version: v4.0.30319
09:44:59.906 PEReader Filename to check: C:\Program Files (x86)\Common Files\ASCOM\Focuser\ASCOM.myFocuser2ASCOM.Focuser.dll
09:44:59.906 PEReader Determining whether this is an assembly
09:44:59.906 PEReader.IsAssembly Found an assembly because it loaded Ok to the reflection context: True
09:44:59.906 PEReader Determining PE Machine type
09:44:59.906 PEReader.MachineType Machine - found "Intel 32bit" executable. Characteristics: 00002102, OS32BitCompatible: True
09:44:59.906 PEReader.MachineType Reading optional 32bit header
09:44:59.906 PEReader This is an assembly, determining Bitness through the CLR header
09:44:59.906 PEReader.Bitness This is a 32 bit assembly, reading the CLR Header
09:44:59.906 PEReader.Bitness Checking 16 headers
09:44:59.906 PEReader.Bitness Found "MSIL" assembly
09:44:59.906 PEReader Assembly required Runtime version: 2.5
09:44:59.906 PE.IsDotNetAssembly Returning: True
09:44:59.906 FileDetails .NET Assembly: True
09:44:59.906 PE.BitNess Returning: 2
09:44:59.906 FileDetails Bitness: BitsMSIL
09:44:59.906 PE.SubSystem Returning 32bit value: WINDOWS_CUI
09:44:59.906 FileDetails Subsystem: WINDOWS_CUI**
Thank you very much.
Hello Robert,
As we expected, the problem was related with ASCOM platform not with your driver. But still wanted to put the solution here. Because it may also effect your project.
In windows; Regional Date Seperator format for Turkey is "dot." I think it causes a problem. Because, if I change the format to English everything work flawlessly.
Yes I saw the response in the ASCOM group. Great thinking!
What I can confirm is that the myfocuserpro2 driver creates a thread, and changes the threads culture to "eng-us". only affects the display of temp offset and temp values, nothing else. Not the internal processing. This This does not change the OS or other applications, just the focuser thread. So should have zero impact.
Noting that you have exactly the same issue with the ASCOM Focuser Simulator indicates that the issue lies somehow in ASCOM as it is happening with more than one driver, so will be interesting to see what they find.
Regards