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!
Greetings, Could really use some help.
I'm chasing an issue which is pointing to BYEos but that is not confirmed. It appears to be a conflict between between the BYE 80D session and the Ascom Celestron Mount driver. Equipment as follows:
Celestron CGX Mount ( has the USB port on the Nexstar HC, not a serial port) I have to run a USB Chip driver PL2303 to connect to the mount per Celestron.
Polemaster PA system.
HP I5 Laptop under WIn 7
Zwo 120mm Guiding cam, running PHD2. The PHD is talking direct to the mount via the ASCOM Celestron Unified driver. ( I don't use the ST4 connection from the cam so I get full position data back from the mount to PHD).
The problem is that either the ASCOM driver or BYEos freezes first and the other follows right after. PHD will then report guiding command failures. In a few cases it has crashed the PC to the Blue screen of death with a USB Bugcode user error.
I've tested the ASCOM driver every way I can. What leads me to suspect BYEos as a possible cause is I don't see this when using Nebulosity for capture. On the other hand BYEos run stand alone to the 80D has never shown the problem.
BYEos Logs just stop with no error so I haven't attached. Is it possible for BYEos to be sending something to the ASCOM driver even though I do not have any ASCOM interfaces set up in BYEos?
Windows and the crash dump point to a failure with USBEHCI.sys as one triggering event.
Link to comment
Share on other sites
24 answers to this question
This topic is now archived and is closed to further replies.