Jump to content

sgl_imaging_challenge_2021_2.thumb.jpg.72789c04780d7659f5b63ea05534a956.jpg

Hitec Astro EQDIR software driver version


Recommended Posts

For a long time now I have been using the Prolific driver installer v10518 from the HitecAstro site on my windows 7 computer.

Recently I have been getting a lot of overnight crashes and lost a lot of imaging time.  An analysis of last night's crash pointed to the Prolific driver.  MS today offered me a new driver V3.6.81.357  to replace v3.3.5.122.

First signs are that it works... well I can move the mount.

My question to the group is in 2 parts:-

1) Is this new driver reliable?

2) Is this now the time to find a new more reliable EQDIR interface and if so what  recommendations can you offer.

TIA

Andy

Edited by AndyKeogh
Link to post
Share on other sites

Apologies. Looks like I was getting my driver versions and installer versions mixed up!

I recently installed the driver set from Hitec site and not had any issues as yet but I'll have to confirm what driver version I'm on.

Not aware of any better method. You could use the handset in PC direct mode but would still need drivers to assign the com ports for the connection.

Link to post
Share on other sites

This is the latest driver, well it worked with my firmware handset upgrades....

http://www.prolific.com.tw/US/ShowProduct.aspx?p_id=225&pcid=41

Thanks I will have a look at this and check which chipset HitecAstro have used.

I note that the Prolific driver you have linked to does not support Windows 8,8.1 or 10. Begs the question as to which interface one needs for those OSs

Andy

Link to post
Share on other sites

I am running W10 and wasn't aware that a MS W10 update in its infinite wisdom will replace the Prolific driver v10518 (which does work with W10) with something it thinks is better - except that it doesnt work !

Find your prolific driver in Device manager and protect it from auto updates.

Link to post
Share on other sites

Thanks I will have a look at this and check which chipset HitecAstro have used.

I note that the Prolific driver you have linked to does not support Windows 8,8.1 or 10. Begs the question as to which interface one needs for those OSs

Andy

 I have run the chip set program and the chip in my EQDIR module is a PL-2303H.  Is this the same chip version that you Tinker1947, Skipper Billy and r3i are using?

Amdy

Link to post
Share on other sites

I contacted Hitecastro support  when I was struggling to get mine to work with Win 10. I received an email which included "There is an old chipset which we have long since discontinued which will not work with windows 8 and upwards under any circumstances."  Anyway, I have got my Prolific cables working, mostly - sometimes I have to roll back the driver again.

I'd like to know how to protect an individual driver from update -  as far as I can see it is all updates across the computer (?)

Allan

Link to post
Share on other sites

Thanks, Skipper,

I have used these instruction sets via FLO's site several times. My understanding is that when you select "Never Install driver software..." that applies to all devices, not just the Prolific driver. Am I wrong here?

Link to post
Share on other sites

 I have run the chip set program and the chip in my EQDIR module is a PL-2303H.  Is this the same chip version that you Tinker1947, Skipper Billy and r3i are using?

Amdy

I've run the checker on my kit and it also reports that it is a PL-2303H chip.

Link to post
Share on other sites

Thanks Mike that is good to know.

I have run 2 overnight tests since I upgraded to the MS updated driver and it has not crashed.

Though Nebulosity has had some problems. Maybe the 12v hub that has taken the place of the mains driven netgear usb hub has changed the dynamics.

I plan to run some more tests this week with different usb cables and a simplified setup to see if I can get a clean 14 hour run without incidents.

Andy

Link to post
Share on other sites
  • 4 years later...

I have an AVX mount and a Hitech Astro cable to enable me to control my mount from the laptop using Stellarium, could someone please tell me which driver I need. Thank you in advance. Cheers 

Link to post
Share on other sites
On 06/10/2020 at 10:02, Dinoboy said:

I have an AVX mount and a Hitech Astro cable to enable me to control my mount from the laptop using Stellarium, could someone please tell me which driver I need. Thank you in advance. Cheers 

You need to provide more details about your hitech Astro cable.   It is a long time since I controlled my C8 using the Avx predecessor the CG5-AS-GT. My recollection is that it used an RS232 interface and Celestron had its own app to control the mount.  I also had a USB to RS232 adapter  as most computers stopped supplying a native RS232 interface.

What OS are you running Stellarium on?

 

Andy

Link to post
Share on other sites

Hi Andy, my operating system is windows 10 and my laptop is a Dell 1500. I plug the cable directly into the hc port on the mount with the other end into my laptop. I have tried the cable ( RS232) that fits into the bottom of the hc which connects into an adapter that fits into a USB port and it works fine but with the Hitech Astro cable nothing. I have downloaded several drivers. It has never worked since the day I got it, I think it must be drivers. I check which com port then put that into Stellarium. Could it be some setting I need to do or is it a driver thing?

Link to post
Share on other sites

Can you upload a picture of your cable please.

Hitec Astro used to use Prolific chips and some were unsupported by W10

So the consensus was to use the FTDI 232R chipset .   So the question is what chipset does your cable use?

If you look in device manager at the port devices and then plug your cable in  how does it identify your cable?

If you right click on the description and select properties  Details tab what values are listed?

This image is for my Hitec Astro EQDIR cable.

COM 3 proerty hardware id.JPG

 

A little later I plugged in my FTDI cable by which time W10 had updated the status to my COM3 to PHASED OUT since 2012 but in the screen below you can see the id for the FTDI chip (COM4).   This does not need any driver loaded as it appears to be directly supported in W10.

 

W10 COM 3 & 4 property hardware id.JPG

Edited by AndyKeogh
expand on detail
Link to post
Share on other sites

Hi Andy just finished taking images Etc. When I plug in my cable it is not shown, I did step by step as you suggested and below are two images, one of the cable and the other is after double clicking on ‘ports’ in device manager. Any ideas?

F03CC33B-66C2-490B-94C5-2260663DE9B9.jpeg

3345F258-9EC7-410F-BE9F-A08EACEBFE60.jpeg

Link to post
Share on other sites

 OK the property box is a drop down. Could you select hardware ID rather than description and take another image please. I can see from your cable image that it is an FTDI chipset. Need the hardware ID to confirm that That is what w10 recognised it as.

Does com6  only appear after you plug the cable in? If so can you also screenshot  the driver tab as well.

TIA

Andy

Link to post
Share on other sites

Hi Andy, unless I plug in the cable First there is no port identified. I have taken a couple more images, you can tell I am not a computer expert or anything near, I hit the update latest drivers in the relevant window just to make sure.thanks for your help..

BBF61609-9F7A-4C40-92D6-7435D33BA662.jpeg

5D538311-5D72-4006-82B9-78A9490421D4.jpeg

Link to post
Share on other sites

OK it seems the cable is being recognised and windows is using an FTDI driver. So it should work.

The question now is what is different between this cable and the others which have worked?

I have had a quick look at the stellarium user guide and it would appear that you tell it to use com 6,

I do not use stellarium so that is the limit of how I can help.

Have you had Stellarium actually controlling you scope with another cable?

Andy

 

Link to post
Share on other sites

Yes Stellarium works with the mount but only if I use the rs232 cable and adapter. I always check which com port and put that into the configuration in Stellarium . I plug the cable directly into the hc port on the mount whereas the other cable fits into the bottom of the hc, it seems that when the hc is not used, nothing works,  I also have Cartes du Ciel on my laptop (Dell 15000) the reticule moves on the screen but the mount does not move. Stranger than fiction.

Link to post
Share on other sites

Does the Hitec Astro cable work if it is plugged into the handset controller?

As far as I can see from some quick research here https://www.celestron.com/blogs/knowledgebase/what-are-the-aux-ports-on-my-computerized-telescope-for the only RS232 interface is in your hand controller. 

So I guess to answer your original question the driver you need is a Celestron  handset.

You asked your question in an EQMOD thread about Hitec Astro’s EQDIR adapter.  Now that adapter replaces the HC. Because the EQMOD software replace all the functionality of the HC and lots more besides.

You may therefore get more details if you ask your question in a Celestron AVX  forum

Edited by AndyKeogh
Link to post
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Ade Turner
      I’ve just bought a Skywatcher EQ6-R Pro. I’m trying to drive it from Stellarium using EQMOD but I’m running into a problem I haven’t the experience to solve.
      This is my set up:
      Windows 7 Laptop > 10m active USB 3.0 cable > 4 port powered Atolla USB 3.0 hub > Lynx Astro EQMOD cable > Mount (plugged directly into hand control socket)
      When I first connected the mount to the laptop (a 2015 Dell Inspiron) Windows 7 searched for a serial/USB driver and installed it on COM 8 (according to Device Manager).
      In Stellarium I created a profile for the mount but it wouldn’t autodetect the COM port. So I manually set it to 8.
      When I try to connect to the mount it sits for a while and then tells me the connection has timed out.
      Anyone have any suggestions as to where I should start to try and get the connection sorted please? Thanks.
    • By SteveBz
      Hi Guys,
      Wim has wisely persuaded me to go for an eqdir cable from my RPi to my SynScan controller. I currently have a usb:db9 + db9:st4 setup to the SynScan handset (ie 3 cables connected). Can I just change the db9 to st4 to a db9:Rj45 or similar? Eg:
       https://www.ebay.co.uk/itm/201608325158
      Plus an old ethernet cable? Ie does the pinout of an ethernet cable correspond to the pinout of the SynScan controller handset socket?
      Regards
      Steve.
       
       
       
    • By morayskies
      Hi All
      Has anybody else had this problem?
      I use a single, ageing laptop (HP620 8Gb RAM) running Windows 7 Pro 64bit to control my imaging setup using the following software;
      Cartes du Ciel and EQMOD to control EQ5 Pro mount via EQDIRECT cable connected via powered USB Hub
      BackyardEOS to capture images from Canon 450D via same USB powered hub
      PHD2 for guiding using GP-CAM 130C and EQMOD pulse guiding
      What confuses me is that some evenings everything works absolutely fine.  Another evening, using exactly the same hardware, software and even connections (ie I always plug the leads into the same ports) the system will be working fine but then suddenly fail.  The failure affects EQMOD indicating a timeout or port not available issue and the Canon 450D also 'locks' requiring a restart of the camera and BackyardEOS.
      I have run USBTree during such a failure and it is showing that the EQDIRECT cable (ie serial converter) is still connected to COM4 (which is correct) and the Canon 450D is also still connected.  I basically have to ensure that all the software is closed and any associated services also stopped.  Of course, the scope is now pointing away from its home position so I have to move it manually back to 'home' before starting again.
      My thoughts are that there could be a number of issues;
      1. Use of a USB hub
      2. A dodgy EQDIRECT cable
      3. USB cables too long (ie about 5m)
      4. Windows is turning off a connection (I have set the power management for each USB port to 'off')
      5. Canon 450D somehow 'freezing'

      When using this laptop, I turn off the Wifi and Anti Virus and Automatic Updates are also off.
      It just baffles me that sometimes this system works flawlessly for hours and yet other nights it keeps failing.
      Any suggestions gratefully received.
      Thanks for looking.
    • By adyj1
      Hi
      I'd like to make my own FTDI EQDIR USB Adapter for my new(to me) AZ GTi  mount... 
      Does anyone know what the pinouts for the rj12 connector are? The 8-pin RJ45 connections are well documented, but I can't find a 6-pin RJ12 wiring diagram...
      Lynx astro do make one, so I know it is possible ? 
      Thanks
      Ady
       
    • By Demonperformer
      I am at a complete loss to understand why eqmod was not syncing on CdC last night. I have had a look at this video, I had the star centred on the screen [3m33s], I pressed sync on CdC, I got the dialog box [3m39s], I clicked 'yes' and NOTHING happened: the white circle stayed where it was, no sync points were added to EQMOD, zilch!
      I can get round most problems, but this really one stymies my GOTOs and, therefore, my imaging process.
      I have been unable to find anything in the EQMOD documentation that deals with such an error and a search on here has turned up no help (but that always depends on the words put into the search!). I checked all the obvious things (location, date/time, etc - but why any of these should stop sync working is beyond me). It's all running on Windoze 10.
      Any suggestions on why this should have stopped working and (more importantly) how I might get it working?
      Thanks.
×
×
  • 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.