Jump to content

Stargazers Lounge Uses Cookies

Like most websites, SGL uses cookies in order to deliver a secure, personalised service, to provide social media functions and to analyse our traffic. Continued use of SGL indicates your acceptance of our cookie policy.

sgl_imaging_challenge_banner_dslr_mirrorlesss_winners.thumb.jpg.9deb4a8db27e7485a7bb99d98667c94e.jpg

MikeP

Moderators
  • Content Count

    6,192
  • Joined

  • Last visited

Community Reputation

838 Excellent

About MikeP

  • Rank
    Moderator

Profile Information

  • Gender
    Male
  • Location
    Kent
  1. Snap. Ordered mine an hour or so after it appeared on FLO's site for pre-ordering. Mike
  2. Hi Todd, welcome to SGL. I lived and worked in Austin back in the 1980's. I was there for a visit a couple of years ago and was shocked at how much bigger and busier it had become. Still a lovely place to live though. Mike
  3. Happy New Year from me too. Mike
  4. IconRestorer will put it back to your last save. Mike
  5. I replaced my Hitecastro lead with one of FLO's a few weeks ago. Absolutely no problems since. No faffing with out-of-date drivers either. Mike
  6. Hi Bottletopburly, My cable is quite old and has the blue bit on the RJ45(?) end that plugs into the mount. You will see from my post above that normal service has been resumed but I'm going to follow you lead (no pun intended) and buy a Lynx replacement. Windows updates mean I can't easily isolate my computers from potential harmful effects but a more modern cable / driver is a small price to pay for hopefully reducing the probability of future problems. Thanks for replying. Mike PS Don't suppose you'd care to explain your user name would you?
  7. Hi Atreta. I took your advice and tried the Toolbox. It gave a message indicating it could not find the port - at least that was consistent. I went back to the Device Manager and looked at the properties for the port and found an error code of 10 - that was not showing yesterday. Following HitecAstro's instructions, I uninstalled and deleted the driver and reinstalled. Error code went away but still with the same results in Toolbox. More out of hope than expectation, I uninstalled the driver in port properties and then click install driver. I expected a dialogue asking where to get the driver from but it just installed. Result - success in Toolbox. I restarted the laptop, started CduC, connected to the mount and happily slewed back and forth. I have no idea where Windows got the driver from or why the Hitecastro one worked then didn't work but all OK now. Thank you for taking the trouble to respond. Mike
  8. Having bought a new portable imaging rig based around an ASIAir, I decided to revamp the wiring and software in my observatory. I now have a Raspberry Pi at the mount connected into my home network and connected to the mount via USB using a HitecAstro Eqdir. Using KStars on my obsy Windows 10 PC, I can control the mount via the RPI, so the Eqdir cable seems to be OK. When I bought the mobile rig, I bought a Polemaster so I thought while I was at it, I might as well polar align the obsy mount. It is awkward to see the monitor from the mount, so I used a Windows 10 laptop. I disconnected the Eqdir from the RPi and plugged it and the Polemaster into the laptop. I tried to connect to the mount using Cartes du Ciel but couldn't. The Eqmod interface (or something) flashes on and then immediately off. I tried using EQASCOM_Run, that does the same but does so continuously and has to be killed (Kill EQASCOM doesn't stop it). Eventually I gave up and connected to the mount via RPi and used that to do the slewing part of the Polemaster routine, which worked fine. While trying to get the laptop to connect to the mount, I checked the port to which the PL2303 HitecAstro was assigned and made sure it was correctly set in EQASCOM and I also replaced the driver. I couldn't think of anything else to try. The only other thing I noticed was that clicking on the Find button in the EQASCOM set up could not find a port. I'm pretty sure the laptop is the problem but I don't know where. I have the latest ASCOM, EQASCOM and CduC. Does anyone have any ideas? I've been using EQMOD for years so I am quite embarrassed to ask. Mike Mike
  9. Hi Alan, Many years ago I had problems with an EQ6 with EQMOD. This was my solution: Slew to anything. Slew back to Polaris. Switch off the mount, disconnect / shut down the planetarium program. Undo the clutches and physically put the scope back to the home position - just eyeball it. Switch back on, reconnect etc and try again. Mike
  10. That sounds good value Michael. Mike
  11. Are the bolts different lengths and you have the round the wrong way? Mike
  12. You may be mistaking this for having a slight weight imbalance so that the gears remain meshed. Mike
  13. Welcome SIDO. Spent a year not too far from you in Waverley IO back in the 1990's - nice area and nice people. Mike
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.