I am part of a small team using a DDM60 pro and autoslew in a remote obervatory. We have had this setup for 2,5 years now and have har some crashees of autoslew occationaly sin the start. But during the last 12 month the issue of a crashing autoslew has been increasingly frequent. Has some of you noticed similar behaviour?
Our setup is permanetly setup in a remote observatory and user fairly frequent.
We have had a lot of communication error issues that has been resonably keept at bay via cleaning and applying contact spray, but recently this issue is increasing, getting more frequent harder to mittigate.
We also have issues with stiction in the mount bearings (our percieved root cause;), over 1-3 hours drivning the motor currents up to a point where on or the other motor is turned of, occationally resulting in the sope pointing in strange directions when our imaging software (starkeeper voyager) detects the failure and tries to end session and park the scope...
We have balances, tuned and tried lots of adjustmets to get as perfect conditions as possible, we also have created a parallell software that detects hig currents and send an event to voyager to pause - performs a number of release sleews and the signals voyager to resume - this works most of the times but..
We are now reaching out to all of you owner of a ddm60 (or ddm85) that uses Autoslew,
-have you also had reoccuring crashing issues?
-have you come up with potential solutions/workarounds that mitigate the issues?
-have anybody been in contact with ASA? Is Autoslew/Sequence totally retired products?
-any suggestions to what can be done to Autoslew/Sequence to allow our nice mounts to keep on being able to be used? (maing Autoslew, parts om sequence open source?)
Question
RoWal
Hi
I am part of a small team using a DDM60 pro and autoslew in a remote obervatory. We have had this setup for 2,5 years now and have har some crashees of autoslew occationaly sin the start. But during the last 12 month the issue of a crashing autoslew has been increasingly frequent. Has some of you noticed similar behaviour?
Our setup is permanetly setup in a remote observatory and user fairly frequent.
We have had a lot of communication error issues that has been resonably keept at bay via cleaning and applying contact spray, but recently this issue is increasing, getting more frequent harder to mittigate.
We also have issues with stiction in the mount bearings (our percieved root cause;), over 1-3 hours drivning the motor currents up to a point where on or the other motor is turned of, occationally resulting in the sope pointing in strange directions when our imaging software (starkeeper voyager) detects the failure and tries to end session and park the scope...
We have balances, tuned and tried lots of adjustmets to get as perfect conditions as possible, we also have created a parallell software that detects hig currents and send an event to voyager to pause - performs a number of release sleews and the signals voyager to resume - this works most of the times but..
We are now reaching out to all of you owner of a ddm60 (or ddm85) that uses Autoslew,
-have you also had reoccuring crashing issues?
-have you come up with potential solutions/workarounds that mitigate the issues?
-have anybody been in contact with ASA? Is Autoslew/Sequence totally retired products?
-any suggestions to what can be done to Autoslew/Sequence to allow our nice mounts to keep on being able to be used? (maing Autoslew, parts om sequence open source?)
Kind Regards
Roger / Team SDST @ e-eye spain
Edited by RoWalLink to comment
Share on other sites
3 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now