|
|
To try to understand what fail I make a special test version that detail the focuser connection steps to the log. Can you install this version from : https://vega.ap-i.net/tmp/test/ Then start ccdciel, connect the devices. Use the menu "Help / Show current log" to get the full log and copy here. |
|
|
Log_20230730_150852.log (2,463 bytes) |
|
|
Thank you for the test, but I not put enough message at the very start of the connection where the error occur. Can you try with the new test version from https://vega.ap-i.net/tmp/test/ Beware the file name is the same, only the file time change. |
|
|
For some reason uploading files is not working properly (the upload screen with the logfile stays visible and is not uploading anything). The latest logfile is included here: 2023-07-31T07:10:55.483 CCDciel Version beta 0.9.85-Unknown-revision 2023/07/30 19:24:39 2023-07-31T07:10:55.483 Compiled with: Lazarus 2.2.4.0 Free Pascal 3.2.2 Win64-x86_64-win32 2023-07-31T07:10:55.483 1: CCDciel Version beta 0.9.85 Copyright (C) 2023 Patrick Chevalley. This is free software, you can redistribute it under certain conditions. 2023-07-31T07:10:55.483 1: This program comes with ABSOLUTELY NO WARRANTY; for details see Help/About 2023-07-31T07:10:55.483 9: Screen scaling : True 2023-07-31T07:10:55.483 9: Screen scale : 89% 2023-07-31T07:10:55.483 3: Using configuration file C:\Users\adrig\AppData\Local\ccdciel\ccdciel_scherpstellen zon en maan.conf 2023-07-31T07:10:55.595 9: Using a maximum of 8 parallel processor 2023-07-31T07:10:55.645 9: Microsoft Windows 10 Home 10.0.19045 64-bit 2023-07-31T07:10:55.692 9: ASCOM Platform 6.6, 6.6.1.3673 2023-07-31T07:10:55.783 2: TCP/IP server listen on port: 3277 2023-07-31T07:10:59.305 2: Connecting Camera ASCOM "ASCOM.ASICamera2.Camera" … 2023-07-31T07:10:59.664 9: ASCOM.ASICamera2.Camera: ASI Camera (1)6.5 2023-07-31T07:10:59.664 9: ASCOM.ASICamera2.Camera: Driver version: 6.5 2023-07-31T07:10:59.664 9: ASCOM.ASICamera2.Camera: Interface version: 3 2023-07-31T07:10:59.664 1: Camera connected 2023-07-31T07:11:00.762 3: ASCOM.ASICamera2.Camera: Connected 2023-07-31T07:11:00.762 2: Connecting Focuser ASCOM "ASCOM.ArcoEsatto.Focuser" … 2023-07-31T07:11:00.762 3: ASCOM.ArcoEsatto.Focuser: Create focuser object 2023-07-31T07:11:00.966 9: ASCOM.ArcoEsatto.Focuser: Interface version: 3 2023-07-31T07:11:01.083 0: ASCOM.ArcoEsatto.Focuser: Connection error: Index was outside the bounds of the array. 2023-07-31T07:11:01.779 2: Camera frame x=0 y=0 width=5 height=5 2023-07-31T07:11:58.848 9: Disconnecting devices 2023-07-31T07:11:58.848 1: ASCOM.ASICamera2.Camera: Disconnected 2023-07-31T07:11:58.848 1: ASCOM.ArcoEsatto.Focuser: Disconnected 2023-07-31T07:11:58.958 9: Abort 2023-07-31T07:12:02.849 1: TCP/IP server stopped 2023-07-31T07:12:03.928 1: Disconnecting devices … 2023-07-31T07:12:03.928 9: Disconnecting devices 2023-07-31T07:12:05.028 1: Configuration saved 2023-07-31T07:12:07.101 1: Program exit |
|
|
The properties of the driver: Focuser properties.png (59,371 bytes) |
|
|
As I write software of my own, including ASCOM related programs, I did some additional testing in C# using the focuser and the same PLL driver. And guess what? I've got the same error ... It looks like the source of the error is from ASCOM and not from CCDciel (that only catches the error). I will do some additional investigations here. ASCOM exception.txt (6,129 bytes) ASCOM exeption.png (144,811 bytes) |
|
|
Addional testing has been done with FireCapture. - Same Esatto focuser - Same PLL driver ... no problem at all (see attached screenshots). No idea what's going on here. Looks like Java applications like FireCapture don't have this issue. |
|
|
The screenshots: FireCapture 1.png (10,875 bytes) FireCapture 2.png (17,767 bytes) FireCapture 3.png (17,900 bytes) |
|
|
And the last one (could not add this picture earlier as a result of the anti-spam policy of this site): FireCapture 4.png (8,163 bytes) |
|
|
Thank you for all the testing and research. From the CCDciel log I can confirm the exception is in the ASCOM driver when the Connect method is called. One of the possible issue is 32/64 bit problem. Here you use the 64bit version of CCDciel, can you try to install the 32bit version. Also sometime it can work when connected using ASCOM DeviceHub. Another possible problem is the device is registered for another user and not work with your standard account. In this case reinstall the driver and be sure to not run the installer as administrator. |
|
|
Update: The 32 bit version of CCDciel didn't solve the problem. Because CCDciel cannot be run in Administrator mode, I used my own test program to run as an Administrator. Unfortunately, the problem still exists. I noticed that the account I 'am using on my laptop, where CCDciel has been installed, is an Administrator account (there is only ONE account present). CCDciel runs without problem. However, when running the CCDciel-exe as an Administrator, it won't start as a result of the CCDciel restrictions. Because it is no common practice to let drivers be installed by 'ordinary' users, there should be no discrepancy between the account that installed the driver and the account that is running CCDciel (there is only ONE account). So far I didn't do any testing with the ASCOM DeviceHub. In the mean time I will do some additional testing on my development PC in order to grasp what is going on here. |
|
|
After some debugging in a test environment, it looks like the problem is caused by the Esatto focuser wanting to communicate over a serial COM port but isn't able to. For that reason the connection cannot be established resulting in a (weird) 'error out of bounds' error message. I can remember that the Esatto focuser Manager connects to COM3 and that FireCapture is also configured to use COM3. That could explain that FireCapture has no issues with the focuser. But what about CCDciel? After some investigations, I found out that there is something like an ASCOM Profile Explorer (6.6.0.0). In the node called "COMPortSettings" I entered for the item "ForceCOMPorts" a new entry called "COM3". Unfortunately this COM port cannot be selected (read: not visible) as part of the driver settings for the focuser (see attached pictures). This seems not the right way to do it, but I think the missing COM port is most likely the root cause for the problem of 'not connecting'. image.png (12,314 bytes) image-2.png (27,896 bytes) image-3.png (26,488 bytes) |
|
|
The reason for the empty box: missing device drivers. Now the device is registered to operate with COM3 (laptop) or COM4 (development PC) as can be seen in the attachments. After further testing, connecting the device: Focuser F = new Focuser ( progID ); F.Link = true; But ... unfortunately the "error out of bounds" error message is back again. Still don't know what is going on here ... Untitled.png (146,733 bytes) image-4.png (31,622 bytes) |
|
|
It seems there are two possibilities left: - Testing with the ASCOM Hub - Write an email to PrimaLuceLab Still remains a mystery how FireCapture bypasses this issue ... |
|
|
In CCDciel it crash at the same place, when trying to set Connected. I don't know for Firecapture because we not have access to the source code. Do it also use the Ascom Chooser to select the focuser? Anyway this is a question for the manufacturer. The best is to tell them about your simple example, because in this case there is no possible discussion. Focuser F = new Focuser ( progID ); F.Link = true; |
|
|
"I don't know for Firecapture because we not have access to the source code. Do it also use the Ascom Chooser to select the focuser?" Just did some testing: in FireCapture the Chooser works exactly the same showing "COM3 Sillicon Labs CP210x USB to UART Bridge" when selecting the Properties. After pressing the OK button, it connects without any difficulty. Because it uses the same underlaying driver software as CCDciel and I are using, I think the problem is most likely NOT caused by the focuser driver itself. Maybe (I have to do some additional testing/investigations here) the problem is the result of a bug in the ASCOM .NET wrapper classes. This could explain the behaviour of FireCapture as it is Java based and has no problems. |
|
|
CCDciel do not use the .Net access to the driver, it is written with FreePascal and use the classic COM access. If you suspect something wrong with the ASCOM profile for this driver, you can use the procedure below, be sure to select to remove Profile and "3rd Party Drivers". https://ascomtalk.groups.io/g/Help/wiki/7788 |
|
|
I will start contacting the ASCOM user group. In my test environment, the overall layout should be in accordance with the picture below. image-5.png (50,099 bytes) |
|
|
I just posted this issue at the ASCOM talk user group ... |
|
|
I contacted the ASCOM user group and they advised me to run the ASCOM Conform Universal tool. After running the diagnostics tool, the following output was produced: 16:09:08.700 ASCOM Universal Device Conformance Checker Version 2.0.0.16486, Build time: ma 29 mei 2023 07:03:52 16:09:08.700 16:09:08.700 Operating system is Microsoft Windows 10.0.19045 64bit, Application is 64bit. 16:09:08.701 16:09:08.701 COM Driver ProgID: ASCOM.ArcoEsatto.Focuser 16:09:08.701 16:09:08.702 CreateDevice INFO Creating NATIVE COM device: ASCOM.ArcoEsatto.Focuser 16:09:08.797 CreateDevice INFO Successfully created driver 16:09:09.802 ConformanceCheck OK Driver instance created successfully 16:09:09.802 16:09:09.803 Connect to device 16:09:09.806 Connected OK True 16:09:09.806 16:09:09.806 Common Driver Methods 16:09:09.807 InterfaceVersion OK 3 16:09:09.807 Connected OK True 16:09:09.808 Description OK ASCOM PLL Focuser Driver 16:09:09.808 DriverInfo OK ASCOM PLL Focuser Driver v.3.2 16:09:09.809 DriverVersion OK 3.2 16:09:09.809 Name OK PLL Focuser 3.2 16:09:09.810 Action INFO Conform cannot test the Action method 16:09:09.815 SupportedActions OK Driver returned an empty action list 16:09:09.815 16:09:09.815 Properties 16:09:09.816 Absolute OK True 16:09:09.816 IsMoving ISSUE IsMoving is True at start of tests and it should be false 16:09:09.818 MaxStep ISSUE Unexpected error: Input string was not in a correct format. 16:09:09.820 MaxIncrement ISSUE Unexpected error: Input string was not in a correct format. 16:09:09.821 Position ISSUE Unexpected error - Position must be implemented for an absolute focuser: Input string was not in a correct format. 16:09:09.822 StepSize ISSUE StepSize must be > 0.0, actual value: 0 16:09:09.822 TempCompAvailable OK False 16:09:09.823 TempComp Read OK False 16:09:09.824 TempComp Write OK Temperature compensation is not available and a PropertyNotImplementedException (COM Error: 0x80040400) error was generated as expected 16:09:09.827 Temperature OK Optional member returned a PropertyNotImplementedException (COM Error: 0x80040400) error. 16:09:09.827 16:09:09.828 Methods 16:09:09.828 Halt OK Focuser halted OK 16:09:09.830 Move ISSUE Unexpected error: Input string was not in a correct format. 16:09:09.830 16:09:09.830 Disconnect from device 16:09:09.832 Connected OK False 16:09:09.832 16:09:09.833 Conformance test has finished 16:09:09.833 16:09:09.833 Your device had 6 issues, 0 errors and 0 configuration alerts 16:09:09.833 16:09:09.833 Issue Summary 16:09:09.834 IsMoving ISSUE IsMoving is True at start of tests and it should be false 16:09:09.834 MaxStep ISSUE Unexpected error: Input string was not in a correct format. 16:09:09.834 MaxIncrement ISSUE Unexpected error: Input string was not in a correct format. 16:09:09.835 Position ISSUE Unexpected error - Position must be implemented for an absolute focuser: Input string was not in a correct format. 16:09:09.835 StepSize ISSUE StepSize must be > 0.0, actual value: 0 16:09:09.835 Move ISSUE Unexpected error: Input string was not in a correct format. Note the line "16:09:09.815 SupportedActions OK Driver returned an empty action list". The empty list could be related to the array-out-of-bounds error message. And a second time ... 16:22:34.901 ASCOM Universal Device Conformance Checker Version 2.0.0.16486, Build time: ma 29 mei 2023 07:03:52 16:22:34.902 16:22:34.902 Operating system is Microsoft Windows 10.0.19045 64bit, Application is 64bit. 16:22:34.902 16:22:34.902 COM Driver ProgID: ASCOM.ArcoEsatto.Focuser 16:22:34.903 16:22:34.903 CreateDevice INFO Creating NATIVE COM device: ASCOM.ArcoEsatto.Focuser 16:22:35.287 CreateDevice INFO Successfully created driver 16:22:36.293 ConformanceCheck OK Driver instance created successfully 16:22:36.293 16:22:36.294 Connect to device 16:22:36.476 Connected ISSUE Exception when setting Connected to True: Index was outside the bounds of the array. 16:22:36.477 16:22:36.477 ConformanceCheck Further tests abandoned. 16:22:36.478 16:22:36.478 Your device had 1 issue, 0 errors and 0 configuration alerts 16:22:36.478 16:22:36.478 Issue Summary 16:22:36.478 Connected ISSUE Exception when setting Connected to true - testing abandoned: Index was outside the bounds of the array. Note the line "Exception when setting Connected to True: Index was outside the bounds of the array.". This is the same error as the one I got to start this topic. It is obvious that there is something wrong with the driver and/or the firmware in relation to the driver. Anyway, I shall contact PrimaLuceLab before any further action will be taken as upgrading the firmware can be a tricky operation. To be continued ... |
|
|
PrimaLuceLab answered within 5 minutes. They advised: 1) Download PLAY 1.5.9 from our website and install 2) Connect to ESATTO and update to latest firmware 3) Update ASCOM Platform to latest 6.6 4) Update "PLL Focuser ASCOM driver" to latest 3.2 version that you find in the "ESATTO software package 3.2" Actions 3 and 4 were already in place. Upgrading the firmware showed to be key as the diagnostic tool Conform Universal shows no issues anymore. I will now perform some final testing with both CCDciel and FireCapture ... |
|
|
Additional testing finished ... Both CCDciel and FireCapture are working fine now! Issue resolved. |
|
|
Thank you for the detailed description of the solution. |
- Anonymous
