![]() ![]() ![]() I totally agree with the statement about the reliability of the FTDI driver/chipset combination over the Prolific version. The 5v version has a minimum of 3.2v and a max of 4.9v and a typical output of 4.1v which is the much more typical levels required for skywatcher mounts.įTDI drivers are pretty solid, even for W10 (unlike the Prolific drivers), so I would bet on it being the voltage levels rather than the OP System. I think you will find it needs 3.3v as a minimum. I think you would be better off with the 5v version since the output of the 3.3v version can be as low as 2.2v with a max of 3.2v and a typical output of 2.8v which would almost certainly be too low for your mount. Win 10, so much for plug and play - more like plug and pray The irony is that I had Eqmod happily controlling my DIY mount via AstroEq last year before I upgraded to my current mount. Really a bit annoying this one, I'm at the stage where I'm considering a reinstall of Win 10. Yes the correct drivers are installed, current build of ASCOM/Eqmod and Cdc - all checks out ok until I try to talk to the mount - cdc controlling. ![]() Have you installed the FTDI drivers? Here: ĮDIT: I've also only used the 5V variant but, as you say, the eqmod instructions say that the AZ-EQ6 is 3.3V tolerant, so it should work. Alternatively, would there be any reason for a virtual com port to cause Eqmod any problems - I know little about com ports to be honest. I'm wondering if the 3v variant of the TTL232R just can't be recognised by the mount despite the advice in the Eqmod document. ![]() I've installed ASCOM and Eqmod but still the same and there is no driver conflict shown. However when connected to Eqmod via CDC I'm still getting Eqmod not recognising the com port despite Com 4 being identified by Device Manager. I confirmed the integrity of the splice connection using the Mitty app which confirmed the Tx and Rx lines were fine. Gnd (black on FTDI) to pin 4 (shared Gnd) on Cat 5 Tx (orange on FTDI) to pin 6 (Rx) on Cat 5 Rx (yellow on FTDI) to pin 5 (Tx) on Cat 5 I spliced the TTL232R to a cat 5 patch cable as per the instructions on the eqmod sourgeforge document : I used a TTL232R supplied by RS online - (the 3v variant). Paul, I'm having no joy with the cable I made and I wonder if you could just confirm a few points in case I've missed something important. So you'd still be paying less than the commercial product and you'll be able to make up Cat5 cables for family, friends and fellow astronomers! Instructions here: Don't worry about all the technicalities, you just need to attach an RJ45 Cat5 plug on to the end of one of these: (other vendors exist!), with the wires in the right place, and you're good to go! Both of the FTDI leads that I bought are colour-coded correctly.Īs I have access to a Cat5 crimper tool at work, the total cost to me was just that of the cable: £12Įven if you don't know have access to one of these tools, you can buy them pretty cheaply e.g: I've already made two, and they both work faultlessly. The EQMOD website has all the wiring details for the each mount connector. Has anyone considered making their own? I was looking at this. I will probably invest in an FDTI-type EQDirect cable in the future. I too had Prolific driver issues when I updated from Win7 to Win10, but at the moment everything is working consistently. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |