Jump to content

Banner.jpg.b83b14cd4142fe10848741bb2a14c66b.jpg

Brushman

Members
  • Posts

    34
  • Joined

  • Last visited

Everything posted by Brushman

  1. I've used both the supplied power cable (into PowerTank) and a separate Baader power cable direct into mains. Both show same issue, so can only assume it's not the power cable. The handset cable seems to be working properly as the HC switches on fine to initialise and display the error message. Could it be a dodgy AZ cable? I'm not sure if this would have ever worked, but I switched it out for another ethernet cable - but this had no effect either. If it is a specialised cable then perhaps that could be a potential culprit?
  2. I was using a Baader power supply, but I just tried it with a fully charged Celesteon PowerTank and no change!
  3. Thanks for the message, but unfortunately that's not it. They are super stiff and a nightmare to get out once in, but when I retested I hear a definite click when inserting into the ports.
  4. Upon switching on the mount the handset initialises and then displays the following: "Caution..." "Both Axes... No response!" If I press enter it allows me to set my location, time etc. but will not slew. I have a SkyWatcher 10" GoTo dob with freedom find. It was bought new and gifted straight to me, so was unused before discovering this problem. The power is connected to mount and the motorised units are connected. The handset displays that it's running version 4.39.05. I've tried re-updating the firmware in the hope it left the factory corrupted, but its made no difference. This may not mean anything, but when updating and I checked the HC it displayed that I was running database version .2. I was expecting this to be .5 seems as I was running v4.39.05. Can anyone help a beginner out please?
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. By using this site, you agree to our Terms of Use.