|
|
This is an error with the SVbony driver you must report to them. I install it to look at the problem, below is the extract from my log file, double click to open the file in a text editor, this also show the messages of class 9 that are not displayed on screen for clarity. 2026-02-21T21:00:37.679 2: Connecting Switch ASCOM "ASCOM.SVBONY.Switch" … 2026-02-21T21:00:37.710 9: ASCOM.SVBONY.Switch: Interface version: 3 2026-02-21T21:00:37.710 0: ASCOM.SVBONY.Switch: Connection error: Method 'Connect' is not supported by automation object At the row before the error we see it report an InterfaceVersion=3 , this is the new interface for ASCOM 7. The Connect method is new with this version and it is mandatory, see https://ascom-standards.org/newdocs/switch.html#Switch.Connect So they must implement it or report InterfaceVersion=2 , in this case CCDciel use the old Connected method. |
|
|
Thank you for the detailed analysis. I contacted them. |
|
|
After a long time, I finally obtained an answer from SVBony - they asked if I use the latest ASCOM driver and claimed that everything is correct on their side. Are you sure that you don't have any mistakes? I try ASCOM Connection tester and it looks working: Create Creating device Connected Connecting to device Name ASCOM.SVBONY.Switch Description ASCOM Driver for Svbony Switch DriverInfo Information about the driver itself. Version: 6.6 DriverVersion 6.6 InterfaceVersion 3 MaxSwitch 17 Connected Disconnecting from device Dispose Disposing of device Dispose Completed disposal ReleaseComObject Releasing COM instance GC Collect Starting garbage collection GC Collect Completed garbage collection <Default> ASCOM Driver for Svbony Switch COM Port COM27 Dc1_Name DC1 Dc2_Name DC2 Dc3_Name DC3 Dc4_Name DC4 Dc5_Name DC5 Dc6_Name TYPE-C+USB1-2 Dc7_Name USB3-5 Pwm1_Name PWM1 Pwm2_Name PWM1 Pwm3_Name PWM2 Trace Level False Create Creating device Connected Setting Connected = True Setup Opening setup dialogue Connected Setting Connected = False Dispose Disposing of device Dispose Completed disposal of device I also tried to use NINA - also without any problem. Can you make some kind of "try-except" fix for this issue? I know that it isn't perfect, but it should work... |
|
|
Maybe this can be bypassed by using the old Connected method but I not like this kind of hack. The best way to know if a driver is conformant is to use the ASCOM Conformance Checking tool. See : https://ascom-standards.org/COMDeveloper/Conformance.htm I run it with the SVBony switch driver on a Win11 computer. It is not important I not have the switch because the error is before it try any USB connection. Same as CCDciel it cannot connect: ISSUE Connection exception - further testing abandoned: Type library exporter encountered an error while processing 'ASCOM.SVBONY.Switch, SVBONY SWITCH'. Error: Element not found. See screenshot for more messages. You can install this tool from https://github.com/ASCOMInitiative/ConformU/releases/tag/v4.2.1 Please run it and tell me the result. If this is the same as me you can send the full log to SVBony. conformu.png (74,260 bytes) |
|
|
Here is output: 20:51:51.978 ASCOM Universal Device Conformance Checker Version 4.2.1.48140, Build time: po 09 februára 2026 12:14:24 20:51:51.989 20:51:51.990 Operating system is Windows 10 (build 18363), Processor is Intel/AMD 64bit, Application is 64bit. 20:51:51.990 20:51:51.991 COM Driver ProgID: ASCOM.SVBONY.Switch 20:51:51.991 20:51:51.995 CreateDevice INFO Creating NATIVE COM device: ASCOM.SVBONY.Switch 20:51:53.352 CreateDevice INFO Successfully created driver 20:51:54.412 CreateDevice OK Found a valid interface version: 3 20:51:54.412 CreateDevice OK Driver instance created successfully 20:51:54.412 20:51:54.414 Connect to device 20:51:54.437 ConnectToDevice ISSUE Connection exception - further testing abandoned: Type library exporter encountered an error while processing 'ASCOM.SVBONY.Switch, SVBONY SWITCH'. Error: Element not found. 20:51:54.439 20:51:54.440 ConnectToDevice Cannot connect to device, further tests abandoned. 20:51:54.441 20:51:54.442 Your device had 1 issue, 0 errors and 0 configuration alerts 20:51:54.443 20:51:54.443 Issue Summary 20:51:54.444 ConnectToDevice ISSUE Connection exception - further testing abandoned: Type library exporter encountered an error while processing 'ASCOM.SVBONY.Switch, SVBONY SWITCH'. Error: Element not found. 20:51:54.445 20:51:54.446 Timing Summary See Help for further information. 20:51:54.446 Timing Summary FAST target response time: 0.1 seconds, (configuration and state reporting members). 20:51:54.447 Timing Summary STANDARD target response time: 1.0 second, (property write and asynchronous initiators). 20:51:54.447 Timing Summary EXTENDED target response time: 600.0 seconds, (synchronous methods, ImageArray and ImageArrayVariant). 20:51:54.448 Timing Summary Conform is configured to report both good and bad timing outcomes. 20:51:54.449 20:51:54.449 No member timings were recorded. 20:52:55.936 ASCOM Universal Device Conformance Checker Version 4.2.1.48140, Build time: po 09 februára 2026 12:14:24 20:52:55.937 20:52:55.938 Operating system is Windows 10 (build 18363), Processor is Intel/AMD 64bit, Application is 64bit. 20:52:55.939 20:52:55.939 COM Driver ProgID: ASCOM.SVBONY.Switch 20:52:55.941 20:52:55.941 CreateDevice INFO Creating NATIVE COM device: ASCOM.SVBONY.Switch 20:52:56.007 CreateDevice INFO Successfully created driver 20:52:57.009 CreateDevice OK Found a valid interface version: 3 20:52:57.010 CreateDevice OK Driver instance created successfully 20:52:57.011 20:52:57.011 Connect to device 20:52:57.013 ConnectToDevice ISSUE Connection exception - further testing abandoned: Unexpected HRESULT has been returned from a call to a COM component. 20:52:57.014 20:52:57.014 ConnectToDevice Cannot connect to device, further tests abandoned. 20:52:57.015 20:52:57.015 Your device had 1 issue, 0 errors and 0 configuration alerts 20:52:57.015 20:52:57.016 Issue Summary 20:52:57.016 ConnectToDevice ISSUE Connection exception - further testing abandoned: Unexpected HRESULT has been returned from a call to a COM component. 20:52:57.016 20:52:57.017 Timing Summary See Help for further information. 20:52:57.017 Timing Summary FAST target response time: 0.1 seconds, (configuration and state reporting members). 20:52:57.017 Timing Summary STANDARD target response time: 1.0 second, (property write and asynchronous initiators). 20:52:57.018 Timing Summary EXTENDED target response time: 600.0 seconds, (synchronous methods, ImageArray and ImageArrayVariant). 20:52:57.018 Timing Summary Conform is configured to report both good and bad timing outcomes. 20:52:57.018 20:52:57.019 No member timings were recorded. 20:53:11.169 CreateDevice INFO Creating NATIVE COM device: ASCOM.SVBONY.Switch 20:53:11.231 CreateDevice INFO Successfully created driver 20:53:12.232 CreateDevice OK Found a valid interface version: 3 20:53:19.642 TestManager:SetupDialog INFO Setup dialogue task status: Running, Stop button task status: RanToCompletion 20:53:22.712 DiscoveryDiagnostics Starting discovery... 20:53:22.730 DiscoveryDiagnostics Task started 20:53:22.734 [Lib] Finder - Finder 21 Initialised 20:53:22.856 [Lib] Finder - SearchIPv4 21 Sending IPv4 discovery broadcasts 20:53:22.857 [Lib] Finder - SearchIPv4 21 Sent broadcast to: 192.168.1.11 20:53:22.857 [Lib] Finder - SearchIPv4 21 Sent broadcast to: 127.0.0.1 20:53:23.858 DiscoveryDiagnostics Discovery completed. 20:53:23.858 DiscoveryDiagnostics 20:53:23.859 DiscoveryDiagnostics INFO - There were no responses to the discovery broadcast. 20:53:23.860 No issues or information alerts found: Your Alpaca devices pass ASCOM Discovery Diagnostics validation!! 20:56:44.072 ASCOM Universal Device Conformance Checker Version 4.2.1.48140, Build time: po 09 februára 2026 12:14:24 20:56:44.073 20:56:44.074 Operating system is Windows 10 (build 18363), Processor is Intel/AMD 64bit, Application is 64bit. 20:56:44.075 20:56:44.076 COM Driver ProgID: ASCOM.SVBONY.Switch 20:56:44.077 20:56:44.078 CreateDevice INFO Creating NATIVE COM device: ASCOM.SVBONY.Switch 20:56:44.141 CreateDevice INFO Successfully created driver 20:56:45.143 CreateDevice OK Found a valid interface version: 3 20:56:45.144 CreateDevice OK Driver instance created successfully 20:56:45.145 20:56:45.145 Connect to device 20:56:45.147 ConnectToDevice ISSUE Connection exception - further testing abandoned: Unexpected HRESULT has been returned from a call to a COM component. 20:56:45.148 20:56:45.148 ConnectToDevice Cannot connect to device, further tests abandoned. 20:56:45.149 20:56:45.149 Your device had 1 issue, 0 errors and 0 configuration alerts 20:56:45.149 20:56:45.149 Issue Summary 20:56:45.150 ConnectToDevice ISSUE Connection exception - further testing abandoned: Unexpected HRESULT has been returned from a call to a COM component. 20:56:45.150 20:56:45.150 Timing Summary See Help for further information. 20:56:45.151 Timing Summary FAST target response time: 0.1 seconds, (configuration and state reporting members). 20:56:45.152 Timing Summary STANDARD target response time: 1.0 second, (property write and asynchronous initiators). 20:56:45.152 Timing Summary EXTENDED target response time: 600.0 seconds, (synchronous methods, ImageArray and ImageArrayVariant). 20:56:45.153 Timing Summary Conform is configured to report both good and bad timing outcomes. 20:56:45.153 20:56:45.153 No member timings were recorded. |
|
|
Ok, so this is really the driver that not work. You must send that to SVBony with the link to the tool from my previous message as they apparently don't known it exists. If they have question about this missing method the best is they ask to the ASCOM support forum: https://ascomtalk.groups.io/g/Developer |
- Anonymous
