Hi Roel,
that's a very positive response from Celestron (although I must say I'm a bit worried that they don't have the source code to their own software!). Let's hope that the extra logging helps them track down the problem and work out a solution.
clear skies!
Robin
Sync error with Celestron Nexstar 6 SE mount
Forum rules
If you have a problem or question, please check the FAQ to see if it already has an answer : https://www.sharpcap.co.uk/sharpcap-faqs
Please also read about Troubleshooting USB Issues before posting.
*** Please do not post license keys - please report any problems with licensing to 'admin' by private message ***
Please include the following details in any bug report:
* Version of SharpCap
* Camera and other hardware being user
* Operating system version
* Contents of the SharpCap log after the problem has occurred.
[If SharpCap crashes, please send the bug report when prompted instead of including the log]
If you have a problem or question, please check the FAQ to see if it already has an answer : https://www.sharpcap.co.uk/sharpcap-faqs
Please also read about Troubleshooting USB Issues before posting.
*** Please do not post license keys - please report any problems with licensing to 'admin' by private message ***
Please include the following details in any bug report:
* Version of SharpCap
* Camera and other hardware being user
* Operating system version
* Contents of the SharpCap log after the problem has occurred.
[If SharpCap crashes, please send the bug report when prompted instead of including the log]
Re: Sync error with Celestron Nexstar 6 SE mount
Yes Robin, I have read that the engineer who wrote CPWI is no longer updating this software.
He was shifted to another department to replace a engineer who leaved the company.
Regards
He was shifted to another department to replace a engineer who leaved the company.
Regards
Roel
Celestron Nexstar Evolution 8 - Celestron Nexstar 6 SE - StarSense
ZWO ASI533MC-Pro -- ZWO ASI533MM-Pro
Celestron Nexstar Evolution 8 - Celestron Nexstar 6 SE - StarSense
ZWO ASI533MC-Pro -- ZWO ASI533MM-Pro
Re: Sync error with Celestron Nexstar 6 SE mount
Hello Robin,
I can report that have found a solution to the sync issue with my 6 SE.
Because the sync works with my Evolution 8 I was looking for any soft or hardware differences.
On both mounts I work with a mini PC to do remote EAA.
Eventually I tried the mini PC from my Evolution for the 6 SE and the sync operation worked
The mini PC I use for the Evolution is a more recent one than the one for my 6 SE.
Probably their is some signal delay in the CPWI - mount communication using the older mini PC.
So for now we can close this ticket.
Again thanks for your service & time re. this issue.
Roel
I can report that have found a solution to the sync issue with my 6 SE.
Because the sync works with my Evolution 8 I was looking for any soft or hardware differences.
On both mounts I work with a mini PC to do remote EAA.
Eventually I tried the mini PC from my Evolution for the 6 SE and the sync operation worked
The mini PC I use for the Evolution is a more recent one than the one for my 6 SE.
Probably their is some signal delay in the CPWI - mount communication using the older mini PC.
So for now we can close this ticket.
Again thanks for your service & time re. this issue.
Roel
Roel
Celestron Nexstar Evolution 8 - Celestron Nexstar 6 SE - StarSense
ZWO ASI533MC-Pro -- ZWO ASI533MM-Pro
Celestron Nexstar Evolution 8 - Celestron Nexstar 6 SE - StarSense
ZWO ASI533MC-Pro -- ZWO ASI533MM-Pro
-
admin
- Site Admin
- Posts: 13280
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: Sync error with Celestron Nexstar 6 SE mount
Hi Roel,
thank makes sense, since we did find there was a fixed timeout inside the CPWI Ascom driver that was probably being exceeded - on the slower computer the actualy work that the CPWI software does for the synchronization must just take too long, so that by the time it is finished the ASCOM driver has given up waiting...
Always good to have an excuse to upgrade
cheers,
Robin
thank makes sense, since we did find there was a fixed timeout inside the CPWI Ascom driver that was probably being exceeded - on the slower computer the actualy work that the CPWI software does for the synchronization must just take too long, so that by the time it is finished the ASCOM driver has given up waiting...
Always good to have an excuse to upgrade
cheers,
Robin