AAG Cloudwatcher and USB-Serial Leads...?

[daz]

I think this is probably the best section for this question...

So, I have acquired an AAG Cloudwatcher device and plan to install into the obsy, of course.

I have been testing with my Lindy USB-Serial lead which has a Prolific 2303 chipset in it. I have used this cable for my EQ6 mount previously and it has been fine

BUT it will not work with the AAG device. I have an older laptop that has an actual serial port on, and tested this and it works fine. I also installed the Lindy cable onto the older laptop and it does not work, so I'm certain I need to find another USB-Serial cable.

Soooo, can you recommend any other cables, or more specifically, chip sets I can test?

Cheers!

[Earl]

I used a Startech one without any issues.

[martin_h]

I use this one on my AAG cloudwatcher works on WIN 7

http://www.hitari.co.uk/dynamode-usb-serial-rs232-adaptor.html?fee=8&fep=18196&utm_source=Hitari_GoogleShopping&utm_medium=Hitari_GoogleAds&utm_campaign=Hitari_GoogleFeed&gclid=CPj8gu_p2McCFUZAGwodXwoHaA

[daz]

Thank you chaps!

I shall investigate

[Sp@ce_d]

Hmm mine worked ok on my lindy with prolific chipset on 2 laptops running win 7. I got the lindy 2 port ftdi one for the win 8 pc now running the obsy though. At least with ftdi it keeps the same com port. You sure it's assigned the right port? Other thing might be driver issue, specially with win 8 which is why I didn't bother & went ftdi when I upgraded the obsy puter.

Sent from my iPhone using Tapatalk

[daz]

Hi Spaced

My Lindy is not the FTDI one.

The obsy PC runs Windows7 64bit, and I've tried with the latest Prolific drivers, and the 3.2.0.0 version as well.

It's definitely assigned to the right port, and as the AAG communicates when I use an older laptop that does have serial port, the only conclusion is that there is something implemented in the AAG that is present on the serial port, but in the USB conversion...

I did also try the FTDI cable I use for my mount, and had the same result. The AAG would not communicate with the PC. I suppose it could be a Windows thing.. I have not updated the PC for a while as I don't have internet out in the obsy, but that could be worth a go.

[steppenwolf]

It would be interesting to know what the signal voltage swing is on the 'real' RS232 port versus the usb adaptor as the actual signal data in terms of marks and spaces is likely to be same. I do wonder why we still have RS232 devices when the matching port is now missing from current PCs although there was a time when RS232 with a typical swing of +12v to -12v was unbelievably reliable and noise resilient!

Bring back the RS232 port to PCs I say, there is clearly a need for it even in our 3v world!

[daz]

I could rig up a little test cable for that Steve!

[Sp@ce_d]

It does sound like signal levels. I wonder if the USB port on the pc isn't supplying enough to drive the adapter properly then. I don't suppose there's an optional external power in on the adapter is there? Alternately, perhaps it could be driven via a powered USB hub? I take it you've checked the 12v supply level on the power feed to the AAG. I wonder if that were a bit low if it would have any effect on signal levels at the interface too?

Sent from my iPhone using Tapatalk

[daz]

That's an interesting thought....

I have a StarTech 7 port hub on the mount which is powered. I'll give that a go!

[daz]

Sadly not

[martin_h]

Did you get anywhere with this?

[graemlourens]

Hey Daz.

I received my AAG 2 days ago, and i could not get it working.

But i finally found it out....

I have EQDir, with Win 8.1. This requires a specific 'older' prolific driver.

When i plugged in the new adapter for AAG, it recognized it correcly, but would not work.

Only deinstalling the old prolific driver and installing the newest one, got the AAG working, BUT EQDIR does not work anymore

I am currently seraching for a USB/Serial Lead that runs with the old prolific driver, so i can have both running at the same time. Little annoying. Strangely i can not define one driver for each adapters, it always wants to use the same.

If you have any hints here that you found out, i'd be happy to hear!

Regards, Graem

[martin_h]

That's interesting! The adaptor I used in the above post came with its own driver on a mini CD and doesn't interfere with any other device.

[graemlourens]

Yea, the problem is that my adapter i was using, was also a prolific chip (as the eqdir) but a newer one.

So either one worked or the other

Waiting for my new USBSerial Lead that is NOT prolific, and then should work.

Really thought i could setup 2 different drivers for same 'type' of device, but windows 8 does not let me it seems.

Regards, Graem

[graemlourens]

Hey just as an info.

New USBSerial adapter worked, so its not a fault of AAG.

But new problem arose.

Having the EQDIR from Hitecastro, then the adapter for the AAG, and another usb/serial device - windows just throws itsself over a bridge.

WIth windows 8 i was getting Bluescreens because of the Prolific drivers, interfearing with the other usbserial adapters.

Windows 7 handles it much better, and it works, even if with a few querks (for example sometimes you have to try to connect to eqmod several times before it works, bevore it sais that the com port is unavailable)

It drove me nuts for a week.

[sloz1664]

Anyone ever sort this problem out. I have the same issue with my AAG cloudwatcher, it will not recognize either of my prolific or ftdi serial adaptors on windows 7 64 bit.

Works on my win 7 32 bit laptop and my win 10 64 bit laptop with the ftdi chip only. I have tried resetting all the port configurations and still no luck. I'm even contemplating fitting a serial pci e card onto my obsy pc see if this may work. Any ideas anyone?

One frustrated Steve. 

[daz]

In the end, I put a desktop computer in the observatory with a standard serial port - no more issues!

I would say give the PCI card a go Steve..

[sloz1664]

Cheers Daz,

 

just ordered one

 

Steve