I just got a shoestring eqdir (serial to usb from bintel) and i cant get it working. Installed all the drivers, removed them, reinstalled, tried older versions, checked and double checked COMs and nothing.
It always ends up with a Connection timeout. The cable seems to be working fine, yet it cannot get a response from the mount.
What can it be? Is the mount's electronics blown? Or am I the problem? I can use the hand controller without any issue, and was currently guiding using phd and st4 with no problems... (and using win10)
Cheers!
Edit: If you are here cause you have the same issue, this thread will sort it out somehow (for sure).
Last edited by alex-borek; 29-11-2017 at 08:19 PM.
Reason: Issue solved!
First simple test. If the mount works with only the handbox itself plugged in, then the "mount" electronics are OK.
As per Kens post, how are you connecting it???? and how do you know it is working???
My assumption is that when connecting the cable without connecting it to the mount and it pops up in the device manager, it should be alright.. (i guess i should not be assuming that)...
Any suggestions on how to find out if its a dodgy cable? Or just get a swap?
I may be a bit confused here but the "Shoestring EQDIR" is just a lump that fixes to the mount and you then fit your normal ( rs232 ) USB2Ser adapter to it.
( ie it only converts the rs232 to TTL logic levels and remaps the wiring )
As such, if your existing USB2Ser adapter works into the Hbx using the Synta supplied Hbx update cable, then it should work with the EQDIR.
The "Shoestring USB2EQ6" is a dedicated TTL level cable with its own driver to suit the chip in it, and goes direct from lappie to mount.
The fact the "converter" shows up in device mangler means it is being detected, but we just need to know what it really is ????
ie an EQDIR wont show up there, only the converter will.
I may be a bit confused here but the "Shoestring EQDIR" is just a lump that fixes to the mount and you then fit your normal ( rs232 ) USB2Ser adapter to it.
( ie it only converts the rs232 to TTL logic levels and remaps the wiring )
As such, if your existing USB2Ser adapter works into the Hbx using the Synta supplied Hbx update cable, then it should work with the EQDIR.
The "Shoestring USB2EQ6" is a dedicated TTL level cable with its own driver to suit the chip in it, and goes direct from lappie to mount.
The fact the "converter" shows up in device mangler means it is being detected, but we just need to know what it really is ????
ie an EQDIR wont show up there, only the converter will.
Andrew
Sorry my bad wording, it is indeed the "Shoestring USB2EQ6" that I am using.. So I might drive down to bintel tomorrow and sort it out... So frustrating when this kind of stuff wont work
Thanks a lot Andrew!
Gday Alex
If thats the case, then what app are you using to connect to the mount to see if it works????
In the EQMod setup screen, have you confirmed you have the correct com port number and baud entered ???
Gday Alex
If thats the case, then what app are you using to connect to the mount to see if it works????
In the EQMod setup screen, have you confirmed you have the correct com port number and baud entered ???
Andrew
I've tried using SkytechX, Cdc, EqDirCheck and the eqascom toolbox. What happens is that the edmod window flashes once or twice and dies. When using the toolbox, I can read the connection timeout error. Double checked the port number and baud, tried to change the port number in the device manager and checked if the settings were correct.
Gday Alex
I have a little app that will connect to any Synscan mount using the low level commands, but doesnt use EQASCOM.
You could always try that to see if it finds your mount.
Only problem is the latest update of Firefoox has killed off my FTP manager so need to find out how to get you a link. :-(
Gday Alex
Fooled those hillbillies at Firefox by going back to XP :-)
I have an app at http://members.optusnet.com.au/johan...taTester30.zip
It is a standalone exe and uses low level comms to talk to the mount with nothing in between
Select the com port and baud and hit connect.
The log page will show what happens and if it gets a connection.
If it does connect, then there may be something wrong in your EQMod installation.
If not, then irts more likely the cable.
Andrew
Gday Alex
Fooled those hillbillies at Firefox by going back to XP :-)
I have an app at http://members.optusnet.com.au/johan...taTester30.zip
It is a standalone exe and uses low level comms to talk to the mount with nothing in between
Select the com port and baud and hit connect.
The log page will show what happens and if it gets a connection.
If it does connect, then there may be something wrong in your EQMod installation.
If not, then irts more likely the cable.
Andrew
Mmmm, even without a driver it should give a sound and present as unrecognised device.
The good news though is you're dealing with Bintel - phone call sounds like a good place to start?
Alex mentioned the cable was detected earlier in the thread, and as such, will normally just show in device mangler without sounds etc when replugged in.
If it showed as an available port in my app, that also tells us its "chip" has been detected, so its either a cabling problem between chip and mount, or the driver is somehow misbehaving.
Alex mentioned the cable was detected earlier in the thread, and as such, will normally just show in device mangler without sounds etc when replugged in.
If it showed as an available port in my app, that also tells us its "chip" has been detected, so its either a cabling problem between chip and mount, or the driver is somehow misbehaving.
Andrew
Might be useful to see a screenshot of device manager ports versus EQMOD config screen perhaps?
Update: got it replace today and guess what... it must be some driver issue. Gonna try on ubuntu in the next few hours in case i cant get it running using win10.
Mmmm, even without a driver it should give a sound and present as unrecognised device.
The good news though is you're dealing with Bintel - phone call sounds like a good place to start?
I've been clearing up some drivers and now it does make a sound when I plug the usb in!
That data is not what is expected
the :e1[0D] command asks the mounts motor card to return the current firmware version loaded and "mount type"
It "should" have returned 4 bytes for version, 2 bytes that define the mount type and a following [0D]
ie AABBCC[0D] the value of CC sets the mount type ie EQ6/EQ8/AZEQ5 etc and an EQ6Pro should have returned CC = 00
If you are on Win10, some people have reported having problems with the latest versions of the prolific driver ( and IIRC, thats whats in the shoestrings ). They fixed it by loading older versions of the driver.