SUUNTO STINGER -- pc interface

bloomin 'ell 2400 that takes me back........
I had a sneaking suspicion that it was that slow, but then I thought naw...
couldn't be THAT slow...

Now where's me VT52 ?


I do agree on the serial bit too...

cheers

P



--
pat rick at vir gin dot net

www.tigershark.org.uk



"Mike Brodbelt" <mike@_nospam_coruscant.demon.co.uk> wrote in message
newsan.2004.08.16.20.43.09.505648@_nospam_corusc ant.demon.co.uk...
> On Tue, 10 Aug 2004 09:04:57 +0000, PC wrote:
>
> > Finally if your clear on your H/W setup, the ports allocation (the port
> > number) and the port has no residual devices or S/w that is grabbing and
> > not releasing the port... check your handshake protocol...I cant
remember
> > what it should be, but a good place to start is 9600,8,1,none NOTE you
> > will find the correct protocol in the stinger manual........
>
> Stingers communicate with 2400,8,1,odd. That said, the software should
> explicitly set the port mode when started, so port settings ought to be
> pretty much irrelevant.
>
> With regard to the hardware, one annoying but common problem on recent PCs
> is that they sometimes ship with the serial ports disabled in the BIOS.
> Assuming he's using real serial ports, and not USB emulation, the OP
> should try going into setup at bootup, and checking the serial ports are
> active.
>
> HTH,
>
> Mike.

I had a similar situation with my Mosquito and XP.....

Here is what I found (some of which has already been discussed):

1) Ports hijacked - The hard serial port numbers had been hijacked by
USB ports. Comm 1 was sent out to the USB hub for something. I had to
rest that
2) Conflicted ports - Port 1 & 3 and ports 2 & 4 share DMA channels so
if something has used a specific DMA channel somewhere else, it will
need to be changed.

Both of these things can be seen int he System Control Panel under
Ports.

3) Port-grabbing apps - Already mentioned but ... PDA sync, mobile
telephone sync, Smart Card or Cards readers, Mouse drivers (famous for
this - they grab Comm one out of ... spite?), modem drivers
4) The BIOS has them shut off (already mentioned)
5) Win2K and above - (Seems rather self-explanatory but....) sometimes
the serial ports are not installed. Has to do with the MB drivers. If
you are a build-it-yourselfer (i. e. build your own PC), make sure that
the Motherboard drivers for the Serial ports are installed - this can
also be seen under the Control Panel - you can see if there are any
serial ports that show up.
6) Port Speed!!! Default for installed ports is 9600, 8, 1, No Parity
(NONE). If the Interface is running at 2400, 8, 1, odd it won't
connect.
7) Do you have an Infrared I/F active? They often "steal" Comm 1 (or at
least mine did).
8) Make sure that the software is actually using an existing comm port.
Some apps will only recognize Comm 1 or 2. If you have set it up with
Comm 7 (for example) going to the 9-pin Interface, you are hosed.

My problem was a combination of apps that had already grabbed port 1, my
smart card reader for my home banking, and the fact that Comm 1 had been
co-opted for something else..... I solved the problem by settig the
software for my Mosquito to use Comm 3....

HTH!
Bret


--
bdurrett - Colorado Transplant

Bret Durrett
Frankfurt am Main, Germany

"Diving - The closest thing to outer space - and it won't cost you $20
million!"
------------------------------------------------------------------------
Posted via DeeperBlue.net - Your Online Resource for the UnderWater World.

------------------------------------------------------------------------
bdurrett's Profile: http://forums.deeperblue.net/member....nfo&userid=990
View this thread on DeeperBlue.net: http://forums.deeperblue.net/showthr...threadid=52483