Jump to content

Canada's top-tier Telescopes & Accessories
Be as specific as possible when reporting issues and *ALWAYS* include the full version number of the application you are using and your exact *CAMERA MODEL*
NEVER POST YOUR KEY IN ANY PUBLIC FORUM, INCLUDING THE O'TELESCOPE SUPPORT FORUM ::: IF YOU DO YOUR KEY WILL BE DEACTIVATED WITHOUT NOTICE!
  • 0

BYE and new celesteron SCT focuser


spokcs
 Share

Question

Just bought the new SCT autofocuser from Celestron.  Having a difficult time getting the focuser to connect to BYE.  The Driver is a unified telescope and focuser driver from ASCOM.  The telescope side connects fine, but the focuser side will not connect.  When I attempt to change the settings on the focuser, I get message that it is already connected and to choose OK.  But the focuser will not connect.  Am I missing something, or is there a known problem with BYE and this focuser?

Link to comment
Share on other sites

  • Answers 5
  • Created
  • Last Reply

Top Posters For This Question

Top Posters For This Question

5 answers to this question

Recommended Posts

  • 0

It is common that you cannot change settings once a driver is connected. You should disconnect BYE from the telescope and then connect the focuser to set the focuser settings. Once you have the settings changed you should be able to connect both devices.

This is discussed in the user manual that was installed with the driver. Important is that you need to the Celestron-supplied calibration tool before performing the ASCOM Focuser driver setup.

Link to comment
Share on other sites

  • 0

No problem at all, but are you sure Windows sees the focuser.  Also, your message is a bit confusing.  You say the focuser driver is from ASCOM.... shouldn't the driver come from the focuser manufacturer?  If you use the ASOCM  Diagnostic tool does it connect?

Link to comment
Share on other sites

  • 0

A new Celestron telescope driver was released since the first of the year. The software is not provided by Celestron, but by an independent software developer. The new driver is available for download from the ASCOM-Standrds.org web site. It has focuser control integrated with the telescope driver. Both devices are accessed via the same COM port. It just appears that because the devices are integrated that you must set them both up when neither device is connected. This apparently confused the OP.

Link to comment
Share on other sites

  • 0

I'm still struggling with this...  I believe the physical connections are correct.  The mount is an AVX.  I have power via the aux cable from the mount, and the mini usb in the bottom of the HC to the computer.  The focuser works fine with straight usb power, using the Celestron focuser software, which does not involve BYE at all.  Below is the trace error file from my last attempt.  Thanks for ideas... 

 

I2019-01-26 11:04:59,622 [Main] INFO  - BackyardEOS 3.1.16.40515 started!
2019-01-26 11:04:59,637 [Main] INFO  - Built on 2017-10-06
2019-01-26 11:04:59,637 [Main] INFO  - Microsoft Windows NT 6.2.9200.0
2019-01-26 11:04:59,653 [Main] INFO  - O'Telescope Dependencies Registration.
2019-01-26 11:05:00,497 [Main] INFO  - Registration of BackyardEOS.ASCOM.Platform55 Implementations
2019-01-26 11:05:00,497 [Main] INFO  - --> ASCOMFocuser 5.5 registered.
2019-01-26 11:05:00,497 [Main] INFO  - --> ASCOMTelescope 5.5 registered.
2019-01-26 11:05:00,497 [Main] INFO  - --> ASCOMFilterWheel 5.5 registered.
2019-01-26 11:05:00,497 [Main] INFO  - Registration of BinaryRivers.ASCOM.Platform60 Implementations
2019-01-26 11:05:00,513 [Main] INFO  - --> ASCOMFocuser 6.0 registered.
2019-01-26 11:05:00,513 [Main] INFO  - --> ASCOMTelescope 6.0 registered.
2019-01-26 11:05:00,513 [Main] INFO  - --> ASCOMFilterWheel 6.0 registered.
2019-01-26 11:05:00,513 [Main] INFO  - Registration of BinaryRivers IAutofocusProvider Implementations
2019-01-26 11:05:00,513 [Main] INFO  - --> BinaryRivers.IAutofocusProvider.Beginner was registered
2019-01-26 11:05:00,513 [Main] INFO  - --> BinaryRivers.IAutofocusProvider.Advance was registered
2019-01-26 11:05:00,513 [Main] INFO  - Registration of BinaryRivers IAviEncoder Implementations
2019-01-26 11:05:00,513 [Main] INFO  - --> ByteScout was registered
2019-01-26 11:05:00,513 [Main] INFO  - --> VirtualDub was registered
2019-01-26 11:05:00,513 [Main] INFO  - Registration of BinaryRivers ICableProvider Implementations
2019-01-26 11:05:00,513 [Main] INFO  - --> DSUSB
2019-01-26 11:05:00,513 [Main] INFO  - --> DSUSB2
2019-01-26 11:05:00,513 [Main] INFO  - --> Serial COM1
2019-01-26 11:05:00,513 [Main] INFO  - --> Serial COM2
2019-01-26 11:05:00,513 [Main] INFO  - --> Serial COM3
2019-01-26 11:05:00,528 [Main] INFO  - --> Serial COM4
2019-01-26 11:05:00,528 [Main] INFO  - --> Serial COM5
2019-01-26 11:05:00,528 [Main] INFO  - --> Serial COM6
2019-01-26 11:05:00,528 [Main] INFO  - --> Serial COM7
2019-01-26 11:05:00,528 [Main] INFO  - --> Serial COM8
2019-01-26 11:05:00,528 [Main] INFO  - --> Serial COM9
2019-01-26 11:05:00,528 [Main] INFO  - --> Serial COM10
2019-01-26 11:05:00,528 [Main] INFO  - --> Serial COM11
2019-01-26 11:05:00,528 [Main] INFO  - --> Serial COM12
2019-01-26 11:05:00,528 [Main] INFO  - --> Relay COM1
2019-01-26 11:05:00,528 [Main] INFO  - --> Relay COM2
2019-01-26 11:05:00,528 [Main] INFO  - --> Relay COM3
2019-01-26 11:05:00,528 [Main] INFO  - --> Relay COM4
2019-01-26 11:05:00,528 [Main] INFO  - --> Relay COM5
2019-01-26 11:05:00,528 [Main] INFO  - --> Relay COM6
2019-01-26 11:05:00,528 [Main] INFO  - --> Relay COM7
2019-01-26 11:05:00,528 [Main] INFO  - --> Relay COM8
2019-01-26 11:05:00,528 [Main] INFO  - Registration of Canon Camera Controller Classes
2019-01-26 11:05:00,528 [Main] INFO  - Canon Camera Controller was registered
2019-01-26 11:05:00,528 [Main] INFO  - Registration of Canon Camera Controller Classes
2019-01-26 11:05:00,528 [Main] INFO  - Canon210 Camera Controller was registered
2019-01-26 11:05:00,528 [Main] INFO  - Registration of Canon215 Camera Controller Classes
2019-01-26 11:05:00,528 [Main] INFO  - Canon215 Camera Controller was registered
2019-01-26 11:05:00,528 [Main] INFO  - Registration of BackyardEOS Simulator Camera Controller Classes
2019-01-26 11:05:00,544 [Main] INFO  - Simulator Camera Controller was registered
2019-01-26 11:05:00,544 [Main] INFO  - Registration of BinaryRivers.ISkinPlus Implementations
2019-01-26 11:05:00,544 [Main] INFO  - --> Red (default)
2019-01-26 11:05:00,544 [Main] INFO  - --> White
2019-01-26 11:05:00,544 [Main] INFO  - --> Green
2019-01-26 11:05:00,544 [Main] INFO  - --> Aquamarine
2019-01-26 11:05:00,544 [Main] INFO  - --> Silver
2019-01-26 11:05:00,544 [Main] INFO  - --> Khaki
2019-01-26 11:05:00,544 [Main] INFO  - --> LightSteelBlue
2019-01-26 11:05:00,544 [Main] INFO  - --> Yellow
2019-01-26 11:05:00,544 [Main] INFO  - --> LightPink
2019-01-26 11:05:00,544 [Main] INFO  - --> Pink
2019-01-26 11:05:00,544 [Main] INFO  - Registration of Image Loader Classes
2019-01-26 11:05:00,544 [Main] INFO  - --> [GdRawImageProvider] image loader provider was registered
2019-01-26 11:05:00,544 [Main] INFO  - --> [GdJpgImageProvider] image loader provider was registered
2019-01-26 11:05:00,544 [Main] INFO  - Registration of BinaryRivers IDitherProvider Implementations
2019-01-26 11:05:00,544 [Main] INFO  - --> PHD
2019-01-26 11:05:00,544 [Main] INFO  - --> ASCOM
2019-01-26 11:05:00,544 [Main] INFO  - --> MetaGuide
2019-01-26 11:05:00,544 [Main] INFO  - Registration of Focus Metric Algorithm Classes
2019-01-26 11:05:00,544 [Main] INFO  - --> Full Width Half Maximum was registered
2019-01-26 11:05:00,544 [Main] INFO  - --> Half Flux Diameter was registered
2019-01-26 11:05:00,544 [Main] INFO  - --> Standard Deviation was registered
2019-01-26 11:05:00,544 [Main] INFO  - Registration of Image Converter Classes
2019-01-26 11:05:00,544 [Main] INFO  - --> ConvertToTIFF was registered
2019-01-26 11:05:00,544 [Main] INFO  - Registration of BinaryRivers IWeatherProvider Implementations
2019-01-26 11:05:00,559 [Main] INFO  - --> TEMPerHUMv1
2019-01-26 11:05:00,559 [Main] INFO  - --> StickStation
2019-01-26 11:05:00,559 [Main] INFO  - --> TEMPerHUMv2
2019-01-26 11:05:00,559 [Main] INFO  - --> TextFile
2019-01-26 11:05:00,559 [Main] INFO  - --> MBox
2019-01-26 11:05:00,559 [Main] INFO  - Culture is set to English
2019-01-26 11:05:00,622 [Main] INFO  - -----------------------------------
2019-01-26 11:05:00,622 [Main] INFO  - C:\Users\Steve\Pictures\BackyardTEMP
2019-01-26 11:05:00,622 [Main] INFO  - C:\Users\Steve\Pictures\BackyardTEMP\Logs
2019-01-26 11:05:00,622 [Main] INFO  - -----------------------------------
2019-01-26 11:05:00,622 [Main] INFO  - 4 CPU(s), Processor Affinity is not SET
2019-01-26 11:05:06,182 [Main] INFO  - -----------------------------------
2019-01-26 11:05:06,182 [Main] INFO  - Application state changed: 'Disconnected'
2019-01-26 11:05:06,197 [Main] INFO  - Removing exiftool.config
2019-01-26 11:05:06,510 [Main] INFO  - Licensed to spokcs
2019-01-26 11:05:14,558 [Main] INFO  - Camera action fired: 'FirePropertyValues'
2019-01-26 11:05:14,558 [Main] DEBUG - FrameType has changed to LIGHT
2019-01-26 11:05:15,355 [Main] INFO  - Camera action fired: 'FirePropertyValues'
2019-01-26 11:05:15,558 [Main] INFO  - Camera action fired: 'FirePropertyValues'
2019-01-26 11:05:15,777 [Main] INFO  - Camera action fired: 'FirePropertyValues'
2019-01-26 11:05:15,777 [Main] INFO  - Camera action fired: 'MaestroInitializeSdkOnStartup'
2019-01-26 11:05:16,339 [Main] INFO  - Camera state changed: 'Disconnected'
2019-01-26 11:05:16,933 [Main] INFO  - -----------------------------------
2019-01-26 11:05:16,933 [Main] INFO  - Application state changed: 'Disconnected'
2019-01-26 11:05:16,980 [ReadWeatherCenter(Normal)] DEBUG - No weather provider configured.
2019-01-26 11:06:00,227 [Main] ERROR - CheckDotNetExceptions ASCOM.Celestron.Focuser LinkSet System.Exception: Connect failed, no port defined and no Celestron scope detected (See Inner Exception for details)
2019-01-26 11:06:00,227 [Main] ERROR -    at ASCOM.DriverAccess.MemberFactory.CheckDotNetExceptions(String memberName, Exception e) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 630
   at ASCOM.DriverAccess.MemberFactory.SetTargetInvocationExceptionHandler(String memberName, Exception e) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 647
   at ASCOM.DriverAccess.MemberFactory.CallMember(Int32 memberCode, String memberName, Type[] parameterTypes, Object[] parms) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 373
   at ASCOM.DriverAccess.Focuser.set_Link(Boolean value) in C:\ASCOM Build\Export\ASCOM.DriverAccess\Focuser.cs:line 99
   at BinaryRivers.ASCOM.Platform60.FocuserASCOM.Connect(String drivername)
2019-01-26 11:06:00,227 [Main] ERROR - Connect failed, no port defined and no Celestron scope detected
2019-01-26 11:06:00,227 [Main] ERROR - 
2019-01-26 11:06:00,227 [Main] ERROR - CheckDotNetExceptions ASCOM.Celestron.Focuser LinkSet System.Exception: Connect failed, no port defined and no Celestron scope detected (See Inner Exception for details)
2019-01-26 11:06:00,242 [Main] ERROR -    at ASCOM.DriverAccess.MemberFactory.CheckDotNetExceptions(String memberName, Exception e) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 630
   at ASCOM.DriverAccess.MemberFactory.SetTargetInvocationExceptionHandler(String memberName, Exception e) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 647
   at ASCOM.DriverAccess.MemberFactory.CallMember(Int32 memberCode, String memberName, Type[] parameterTypes, Object[] parms) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 373
   at ASCOM.DriverAccess.Focuser.set_Link(Boolean value) in C:\ASCOM Build\Export\ASCOM.DriverAccess\Focuser.cs:line 99
   at BinaryRivers.ASCOM.Platform60.FocuserASCOM.Connect(String drivername)
2019-01-26 11:06:00,242 [Main] ERROR - Connect failed, no port defined and no Celestron scope detected
2019-01-26 11:06:00,242 [Main] ERROR - 
2019-01-26 11:06:00,367 [Main] INFO  - ASCOM Focuser disconnected (or unable to connect).
2019-01-26 11:06:00,383 [Main] INFO  - Make sure the correct COM port is assigned to your device.
2019-01-26 11:06:00,383 [Main] ERROR - Unable to connect focuser drivername(ASCOM.Celestron.Focuser)
2019-01-26 11:06:00,383 [Main] ERROR -    at BinaryRivers.Orchestrator.MaestroFocuserExtensions.FocuserConnect(Maestro maestro, String drivername)
2019-01-26 11:06:00,398 [Main] DEBUG - IconPlus_MouseClick(btnChoose = '')
2019-01-26 11:06:04,411 [Main] DEBUG - IconPlus_MouseClick(iconTelescopeSelector = '')
2019-01-26 11:06:28,372 [ReadWeatherCenter(Normal)] DEBUG - No weather provider configured.
2019-01-26 11:06:30,997 [Main] ERROR - CheckDotNetExceptions ASCOM.Celestron.Telescope ConnectedSet System.Exception: Connect failed, no port defined and no Celestron scope detected (See Inner Exception for details)
2019-01-26 11:06:30,997 [Main] ERROR -    at ASCOM.DriverAccess.MemberFactory.CheckDotNetExceptions(String memberName, Exception e) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 630
   at ASCOM.DriverAccess.MemberFactory.SetTargetInvocationExceptionHandler(String memberName, Exception e) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 647
   at ASCOM.DriverAccess.MemberFactory.CallMember(Int32 memberCode, String memberName, Type[] parameterTypes, Object[] parms) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 373
   at ASCOM.DriverAccess.AscomDriver.set_Connected(Boolean value) in C:\ASCOM Build\Export\ASCOM.DriverAccess\AscomDriver.cs:line 144
   at BinaryRivers.ASCOM.Platform60.TelescopeASCOM.Connect(String drivername)
2019-01-26 11:06:30,997 [Main] ERROR - Connect failed, no port defined and no Celestron scope detected
2019-01-26 11:06:30,997 [Main] ERROR - 
2019-01-26 11:06:30,997 [Main] ERROR - CheckDotNetExceptions ASCOM.Celestron.Telescope ConnectedSet System.Exception: Connect failed, no port defined and no Celestron scope detected (See Inner Exception for details)
2019-01-26 11:06:30,997 [Main] ERROR -    at ASCOM.DriverAccess.MemberFactory.CheckDotNetExceptions(String memberName, Exception e) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 630
   at ASCOM.DriverAccess.MemberFactory.SetTargetInvocationExceptionHandler(String memberName, Exception e) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 647
   at ASCOM.DriverAccess.MemberFactory.CallMember(Int32 memberCode, String memberName, Type[] parameterTypes, Object[] parms) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 373
   at ASCOM.DriverAccess.AscomDriver.set_Connected(Boolean value) in C:\ASCOM Build\Export\ASCOM.DriverAccess\AscomDriver.cs:line 144
   at BinaryRivers.ASCOM.Platform60.TelescopeASCOM.Connect(String drivername)
2019-01-26 11:06:30,997 [Main] ERROR - Connect failed, no port defined and no Celestron scope detected
2019-01-26 11:06:30,997 [Main] ERROR - 
2019-01-26 11:06:31,013 [Main] INFO  - ASCOM Telescope disconnected (or unable to connect).
2019-01-26 11:06:31,013 [Main] INFO  - Make sure the correct COM port is assigned to your device.
2019-01-26 11:06:31,013 [Main] ERROR - Unable to connect Telescope drivername(ASCOM.Celestron.Telescope)
2019-01-26 11:06:31,013 [Main] ERROR -    at BinaryRivers.Orchestrator.MaestroTelescopeExtensions.TelescopeConnect(Maestro maestro, String drivername)
2019-01-26 11:06:31,013 [Main] DEBUG - IconPlus_MouseClick(btnChoose = '')
2019-01-26 11:07:17,693 [ReadWeatherCenter(Normal)] DEBUG - No weather provider configured.
2019-01-26 11:07:49,589 [Main] DEBUG - IconPlus_MouseClick(iconFocuserSelector = '')
2019-01-26 11:07:57,622 [Main] ERROR - CheckDotNetExceptions ASCOM.Celestron.Focuser LinkSet System.Exception: Focuser not found (See Inner Exception for details)
2019-01-26 11:07:57,622 [Main] ERROR -    at ASCOM.DriverAccess.MemberFactory.CheckDotNetExceptions(String memberName, Exception e) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 630
   at ASCOM.DriverAccess.MemberFactory.SetTargetInvocationExceptionHandler(String memberName, Exception e) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 647
   at ASCOM.DriverAccess.MemberFactory.CallMember(Int32 memberCode, String memberName, Type[] parameterTypes, Object[] parms) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 373
   at ASCOM.DriverAccess.Focuser.set_Link(Boolean value) in C:\ASCOM Build\Export\ASCOM.DriverAccess\Focuser.cs:line 99
   at BinaryRivers.ASCOM.Platform60.FocuserASCOM.Connect(String drivername)
2019-01-26 11:07:57,622 [Main] ERROR - Focuser not found
2019-01-26 11:07:57,622 [Main] ERROR - 
2019-01-26 11:07:57,622 [Main] ERROR - CheckDotNetExceptions ASCOM.Celestron.Focuser LinkSet System.Exception: Focuser not found (See Inner Exception for details)
2019-01-26 11:07:57,622 [Main] ERROR -    at ASCOM.DriverAccess.MemberFactory.CheckDotNetExceptions(String memberName, Exception e) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 630
   at ASCOM.DriverAccess.MemberFactory.SetTargetInvocationExceptionHandler(String memberName, Exception e) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 647
   at ASCOM.DriverAccess.MemberFactory.CallMember(Int32 memberCode, String memberName, Type[] parameterTypes, Object[] parms) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 373
   at ASCOM.DriverAccess.Focuser.set_Link(Boolean value) in C:\ASCOM Build\Export\ASCOM.DriverAccess\Focuser.cs:line 99
   at BinaryRivers.ASCOM.Platform60.FocuserASCOM.Connect(String drivername)
2019-01-26 11:07:57,622 [Main] ERROR - Focuser not found
2019-01-26 11:07:57,622 [Main] ERROR - 
2019-01-26 11:07:57,653 [Main] INFO  - ASCOM Focuser disconnected (or unable to connect).
2019-01-26 11:07:57,653 [Main] INFO  - Make sure the correct COM port is assigned to your device.
2019-01-26 11:07:57,653 [Main] ERROR - Unable to connect focuser drivername(ASCOM.Celestron.Focuser)
2019-01-26 11:07:57,653 [Main] ERROR -    at BinaryRivers.Orchestrator.MaestroFocuserExtensions.FocuserConnect(Maestro maestro, String drivername)
2019-01-26 11:07:57,653 [Main] DEBUG - IconPlus_MouseClick(btnConnect = '')
2019-01-26 11:08:11,587 [Main] DEBUG - IconPlus_MouseClick(iconTelescopeSelector = '')
2019-01-26 11:08:13,868 [Main] DEBUG - IconPlus_MouseClick(btnConnect = '')
2019-01-26 11:08:18,165 [ReadWeatherCenter(Normal)] DEBUG - No weather provider configured.
2019-01-26 11:08:37,371 [Main] DEBUG - IconPlus_MouseClick(btnChoose = '')
2019-01-26 11:08:41,856 [Main] DEBUG - IconPlus_MouseClick(iconFocuserSelector = '')
2019-01-26 11:08:51,760 [Main] ERROR - CheckDotNetExceptions ASCOM.Celestron.Focuser LinkSet System.Exception: Focuser not found (See Inner Exception for details)
2019-01-26 11:08:51,775 [Main] ERROR -    at ASCOM.DriverAccess.MemberFactory.CheckDotNetExceptions(String memberName, Exception e) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 630
   at ASCOM.DriverAccess.MemberFactory.SetTargetInvocationExceptionHandler(String memberName, Exception e) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 647
   at ASCOM.DriverAccess.MemberFactory.CallMember(Int32 memberCode, String memberName, Type[] parameterTypes, Object[] parms) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 373
   at ASCOM.DriverAccess.Focuser.set_Link(Boolean value) in C:\ASCOM Build\Export\ASCOM.DriverAccess\Focuser.cs:line 99
   at BinaryRivers.ASCOM.Platform60.FocuserASCOM.Connect(String drivername)
2019-01-26 11:08:51,775 [Main] ERROR - Focuser not found
2019-01-26 11:08:51,775 [Main] ERROR - 
2019-01-26 11:08:51,775 [Main] ERROR - CheckDotNetExceptions ASCOM.Celestron.Focuser LinkSet System.Exception: Focuser not found (See Inner Exception for details)
2019-01-26 11:08:51,775 [Main] ERROR -    at ASCOM.DriverAccess.MemberFactory.CheckDotNetExceptions(String memberName, Exception e) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 630
   at ASCOM.DriverAccess.MemberFactory.SetTargetInvocationExceptionHandler(String memberName, Exception e) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 647
   at ASCOM.DriverAccess.MemberFactory.CallMember(Int32 memberCode, String memberName, Type[] parameterTypes, Object[] parms) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 373
   at ASCOM.DriverAccess.Focuser.set_Link(Boolean value) in C:\ASCOM Build\Export\ASCOM.DriverAccess\Focuser.cs:line 99
   at BinaryRivers.ASCOM.Platform60.FocuserASCOM.Connect(String drivername)
2019-01-26 11:08:51,775 [Main] ERROR - Focuser not found
2019-01-26 11:08:51,775 [Main] ERROR - 
2019-01-26 11:08:51,791 [Main] INFO  - ASCOM Focuser disconnected (or unable to connect).
2019-01-26 11:08:51,807 [Main] INFO  - Make sure the correct COM port is assigned to your device.
2019-01-26 11:08:51,807 [Main] ERROR - Unable to connect focuser drivername(ASCOM.Celestron.Focuser)
2019-01-26 11:08:51,807 [Main] ERROR -    at BinaryRivers.Orchestrator.MaestroFocuserExtensions.FocuserConnect(Maestro maestro, String drivername)
2019-01-26 11:08:51,807 [Main] DEBUG - IconPlus_MouseClick(btnChoose = '')
2019-01-26 11:09:03,322 [Main] DEBUG - IconPlus_MouseClick(iconTelescopeSelector = '')
2019-01-26 11:09:09,293 [Main] DEBUG - IconPlus_MouseClick(iconStop = '')
2019-01-26 11:09:18,554 [ReadWeatherCenter(Normal)] DEBUG - No weather provider configured.
2019-01-26 11:09:21,023 [Main] DEBUG - IconPlus_MouseClick(iconHelp = '')
2019-01-26 11:09:36,260 [Main] DEBUG - ButtonPlus_MouseClick(btnSettings = 'Setting')
2019-01-26 11:09:39,824 [Main] DEBUG - IconPlus_MouseClick(iconClose = '')
2019-01-26 11:09:39,856 [ReadWeatherCenter(Normal)] DEBUG - No weather provider configured.
2019-01-26 11:09:48,456 [Main] DEBUG - ButtonPlus_MouseClick(btnViewLogFolder = 'Open log folder')
2019-01-26 11:10:19,045 [ReadWeatherCenter(Normal)] DEBUG - No weather provider configured.
2019-01-26 11:11:19,666 [ReadWeatherCenter(Normal)] DEBUG - No weather provider configured.
2019-01-26 11:12:20,194 [ReadWeatherCenter(Normal)] DEBUG - No weather provider configured.
2019-01-26 11:13:20,778 [ReadWeatherCenter(Normal)] DEBUG - No weather provider configured.
2019-01-26 11:14:21,185 [ReadWeatherCenter(Normal)] DEBUG - No weather provider configured.
2019-01-26 11:15:21,594 [ReadWeatherCenter(Normal)] DEBUG - No weather provider configured.
2019-01-26 11:16:22,007 [ReadWeatherCenter(Normal)] DEBUG - No weather provider configured.
2019-01-26 11:17:22,051 [ReadWeatherCenter(Normal)] DEBUG - No weather provider configured.
2019-01-26 11:17:56,132 [Main] DEBUG - ButtonPlus_MouseClick(btnViewLogFolder = 'Open log folder')
 

Link to comment
Share on other sites

  • 0
50 minutes ago, spokcs said:

2019-01-26 11:06:00,227 [Main] ERROR - CheckDotNetExceptions ASCOM.Celestron.Focuser LinkSet System.Exception: Connect failed, no port defined and no Celestron scope detected (See Inner Exception for details)
2019-01-26 11:06:00,227 [Main] ERROR -    at ASCOM.DriverAccess.MemberFactory.CheckDotNetExceptions(String memberName, Exception e) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 630
   at ASCOM.DriverAccess.MemberFactory.SetTargetInvocationExceptionHandler(String memberName, Exception e) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 647
   at ASCOM.DriverAccess.MemberFactory.CallMember(Int32 memberCode, String memberName, Type[] parameterTypes, Object[] parms) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 373
   at ASCOM.DriverAccess.Focuser.set_Link(Boolean value) in C:\ASCOM Build\Export\ASCOM.DriverAccess\Focuser.cs:line 99
   at BinaryRivers.ASCOM.Platform60.FocuserASCOM.Connect(String drivername)
2019-01-26 11:06:00,227 [Main] ERROR - Connect failed, no port defined and no Celestron scope detected

The error message says it all.

"BYE failed to connect to the focuser failed because no port was defined and no Celestron scope was detected."

  I do not believe that this is a BYE issue since it works with other focusers. You need to correctly configure the ASCOM driver to control both the Telescope and the Focuser. The PDF file from the driver provides instructions. Below are my instructions.

Connect the port at the base of the AVX hand controller to the PC.
Connect the focuser to the AUX port on the AVX.
Power up the mount. Do a Quick Align or use the Last Alignment.
Start BYE
In the ASCOM panel, select the Telescope and click on the Settings button (the gear icon, not the checkmark icon). This should launch the ASCOM Telescope Chooser.
Select Celestron Telescope Driver from the dropdown and click on Properties.
Select the correct COM port and the correct Track Mode from the dropdowns. You can select the Advanced mode and complete the other information if you want.
Click on both OK buttons to save the settings and close the Chooser.
Now select the Focuser in the BYE ASCOM panel and click on the Settings button to launch the ASCOM Focuser Chooser.
Select the Celestron Focuser Driver from the dropdown and click on Properties.
Choose the same COM port as for the telescope and click OK twice.
Now, click on the Connect button (with the checkmark) to connect to the focuser.
If the focuser connects, then you should be able to switch the BYE ASCOM panel to the Telescope and click that Connect button.

If all went well, then you are now connected to both devices. If not, you should read the PDF file that was installed with the driver and follow the instructions for troubleshooting and support. Then submit the collected information to the driver author.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share


×
×
  • Create New...

Important Information

This site uses cookies to offer your a better browsing experience. You can adjust your cookie settings. By closing this banner, scrolling this page, clicking a link or continuing to browse otherwise, you agree to the use of cookies, our Privacy Policy, and our Terms of Use