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!
Computer HP laptop w/Dual-Core A4-3305M
Telescope control: NexRemote software
Camera control: BYEOS Pro v3.10
Guiding software: PHD2 v
Guiding camera: SX Lodestar
ASCOM Platform 6 - SP1
ASCOM Celestron Telescope Driver: 5.0.30
ASCOM SX Camera Driver 184.108.40.20682
Laptop connection to camera: 5 meter USB cable
Laptop connection to mount: 5 meter USB cable->Active USB hub->1 meter USB cable ->Keyspan USB-Serial adapter->serial cable->serial port on bottom of Nexstar hand controller
I usually send the guide commands from PHD2 "on camera" (through the SX Lodestar to the ST-4 cable into the guiding port on the mount). I have never had an issue dithering from BYEOS when using this setup.
Last night I was unable to get PHD2 to connect to the mount with the "on camera" setting, so instead I connected PHD2 to the mount using ASCOM.
Guiding and BYEOS dithering worked perfectly through ASCOM, except for one problem:
For about 1/3 of the images, exactly at the point that BYEOS dithering ends and the BYEOS "cool down" period starts, PHD2 reported "star lost". Each time this happened, I had to stop PHD2 guiding, re-select the guide star, and restart guiding.
At no other time did PHD2 have any problems staying locked on the guide star - only at the end of BYEOS dithering.
Has anyone experienced this type of problem before? Could BYEOS be sending a "bad" command to PHD2 at the end of dithering that is causing the problem? Should I upgrade the ASCOM platform and/or Camera/Telescope ASCOM drivers?
Any help would be appreciated,
Link to comment
Share on other sites
7 answers to this question
This topic is now archived and is closed to further replies.