It's easy for a desktop PC, a PCI serial port. It's laptops where there's no
alternative that people are stuck with USB.

Chris

--- In ASCOM-Talk@yahoogroups.com, Frank Mraz <FJMRAZ@...> wrote:
>
>
> Hi Tim,
>
> My "built-for-me" computer has 8 USB ports. What do you recommend that I do to
comply with your suggestion of serial ports ?
>
> Frank M.
>
>
>
> To: ASCOM-Talk@yahoogroups.com
> From: Tim@...
> Date: Mon, 13 Feb 2012 22:57:51 +0000
> Subject: RE: [ASCOM] Re: Still can't connect my LX200GPS to my new WIN 7x64
computer
>
>
>
>
>
>
> I've grown to really hate USB, it's just not reliable enough for
> controlling robotic instruments. Where possible, I urge the installation
> of 'real' serial port cards. They can be purchased cheaply on eBay (even
> a cheap one is better than USB in my experience, but for a really good
> one look at brainboxes.com). On several computers I've used, I've
> witnessed the USB bus periodically resetting itself (maybe some attached
> peripheral did something the root hub didn't like, who knows). When this
> happens, I've noticed that serial ports can completely disappear for a
> short time and then reappear when the bus is happy again; serial devices
> do not like this happening. This can be enough to upset a connected
> program and cause data loss, timeouts or even complete disconnects. In
> my drivers' I've started adding a 'session layer' that monitors the
> serial port health and, if necessary, destroys the instance and
> re-creates a new one from scratch. Shouldn't have to do it, but such is
> life with USB.
>
> --Tim
>
> -----Original Message-----
> From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-Talk@yahoogroups.com] On
> Behalf Of lynol1000
> Sent: 13 February 2012 11:15
> To: ASCOM-Talk@yahoogroups.com
> Subject: [ASCOM] Re: Still can't connect my LX200GPS to my new WIN 7x64
> computer
>
> Sorry for jumping in here but I am chasing something that manifests
> itself on W7/64bit on Intel platforms and ASCOM 6.
>
> My driver connects, runs for some period of time polling for 3 data
> values every second (two temperature readings and position of a focuser
> hardware that can change either from the driver or buttons on the
> device) and then all of a sudden a 'Timed out waiting' error from the
> platform. This can run for 5 minutes or 4 hours.
>
> This is real simple stuff, send 3 bytes, get 4 back, send 3 bytes, get 4
> back then send 3 bytes and expect 7 back. It is the 7 bytes back that
> faults out on a 'receive counted'. The target hardware is based on a PIC
> chip running 48mips running Microchip reference USB stack. Dropping into
> terraterm after the fault shows the device is connected and talking
> happily, no errors in event log. Power management turned off everyplace
> for USB.
>
> My device itself uses windows usbser.sys driver so there is no vendor
> code driver involved.
>
> This happens on Intel based machines, AMD based machines have not
> exhibited it.
>
> All works fine on XP.
>
> Gene
>
> I'll jump in here
> --- In ASCOM-Talk@yahoogroups.com, "autostaretx" <rseymour@> wrote:
> >
> > I'll second Gary's recommendation.
> > IF you look at my "it worked for me" posting:
> > http://tech.groups.yahoo.com/group/ASCOM-Talk/message/26082
> >
> > you'll see the Keyspan USA-19HS adapter in my equipment list.
> >
> > good luck
> > --dick
> >
> > --- In ASCOM-Talk@yahoogroups.com, "rstarscope" <rstarscope@> wrote:
> > >
> > > Hi Chris,
> > > "In for a penny, in for a pound." Please can you recommend a
> Keyspan Model # ? Thank you.
> > >
> > > --- In ASCOM-Talk@yahoogroups.com, Chris Peterson <cpeterson@>
> wrote:
> > > >
> > > > In the case of USB-serial devices, the problem is often a mixture
> > > > of hardware and software. These devices frequently fail to meet
> > > > the specifications of either the USB interface, or of the serial
> standards.
> > > > Replacing the hardware could have changed out one bad design for
> > > > another, or could even result in no change in hardware at all,
> > > > given that there are only a few chipsets used by all the adapter
> makers.
> > > >
> > > > Only a few manufacturers (such as Keyspan) seem to actually follow
>
> > > > the standards closely, and people using those adapters generally
> > > > seem to avoid any issues when using ASCOM drivers.
> > > >
> > > > Enough people are using the Meade driver with Win 7 and USB serial
>
> > > > ports to suggest that if the problem is in the telescope driver
> > > > code, it's something very subtle. The USB driver code for the
> > > > adapter is a much more likely source of the problem.
> > > >
> > > > Chris
> > > >
> > > > *******************************
> > > > Chris L Peterson
> > > > Cloudbait Observatory
> > > > http://www.cloudbait.com
> > > >
> > > > On 2/7/2012 11:59 AM, rstarscope wrote:
> > > > > I just got a New and different USB to SERIAL Converter.
> Installed it, and registered to Com Port 3. Ran DevManView to make sure
> it was connected to Com port 3, and it was.
> > > > > Ran ASCOM Choose-Meade LX200GPS/R Driver-Properties Com
> Port 3-Ok. Tried to connect, and then "Timed out Waiting to received
> Data." Also, of course PhD guiding Failed to connect, "Problem with
> ASCOM Driver."
> > > > > Ran AutoStarSuite 5.5 and MyScope separately and both
> connected, and was able to move scope.
> > > > > Doesn't this say it's not hardware, but it is software?
> What the FIX???
> > > > > Rob
> > > > >
> > > >
> > >
> >
>
> ------------------------------------
>
> For more information see http://ASCOM-Standards.org/.
>
> To unsubscribe from this group, send an email FROM THE ACCOUNT YOU USED
> TO SUBSCRIBE(!) to:
> ASCOM-Talk-unsubscribe@yahoogroups.com
>
> Yahoo! Groups Links
>
> --
> ExchangeDefender Message Security: Click below to verify authenticity
> http://www.exchangedefender.com/verify.asp?id=q1DMxR0s020373&from=tim@...
> Complete email hygiene and business continuity solution available from
http://www.tigranetworks.co.uk
>