Sorry for delay in replying. Couldn't check it out till the weekend. Bags of
input from a GPS to the HyperTerminal, but nothing from the ST60 Multi. I
think it could be faulty

Thanks for steering me towards the HyperTerminal. I had never heard of it.

Phil


"Jack Erbes" wrote in message
...
Phil Stanton wrote:
Hi Wout

Thanks for the information. I will definitely investigate this further,
as in addition to the depth problem, I am having problems getting my
Laptop to talk to the Autopilot. May be a wiring fault, but apparently
the ST60 multi instrument has NMEA In and Out.

A good way to trouble shoot NMEA data problems is to use the Hyperterminal
communications utility included with Windows. That will show you the NMEA
data flow as scrolling ascii text strings. And the strings can even be
saved to a text file for later study.

To use it, select the COM port your NMEA data is on in the "Connect
using:" box. Then change the settings to 4800 baud, 8 data bits, parity
to none, and stop bits to 1. If your NMEA data is at a different baud
rate you may have to change that, the display will be repeated garbles
when that happens. Sometimes you can check the setup on your NMEA talkers
to see what baud rate is being used, they all need to be the same.

Seeing the NMEA data strings tells you your laptop setup is working and
can help you isolate the problem.

There is a known problem with Windows misidentifying a GPS or NMEA input
as a serial mouse. If you go to the device manager find a serial mouse
there, disable it and leave it disabled and that will not happen again.

Jack

--
Jack Erbes in Ellsworth, Maine, USA - jackerbes at adelphia dot net
(also receiving email at jacker at midmaine.com)

Phil Stanton wrote:
Sorry for delay in replying. Couldn't check it out till the weekend. Bags of
input from a GPS to the HyperTerminal, but nothing from the ST60 Multi. I
think it could be faulty

Thanks for steering me towards the HyperTerminal. I had never heard of it.


You're welcome. Its been a freebie with Windows as long as I can
remember, great to use as a console for talking to various devices like
switches and routers, good for testing modems, and trouble shooting some
other devices.

As an added note, someone on another group pointed out to me that
Hyperterminal will not always work as I described it. It will work for
receive only connections but if the sending device expects that there
will two way communications it will not or may not work. I'm not that
smart about RS-232 communications and can't further explain that but it
sounds reasonable to me. Nothing else in Windows is guaranteed to
always work, why should that? :)

But it has been a good trouble shooting tool for me in checking out GPS
to PC connections.

Do you know that your ST-60 is communicating in a RS-232 serial mode?
If that is a SeaTalk instrument or in that mode, it won't work because
that is Raymarine's proprietary flavor of RS-232 or something like that.

Jack

--
Jack Erbes in Ellsworth, Maine, USA - jackerbes at adelphia dot net
(also receiving email at jacker at midmaine.com)

Hi Jack

There doesn't seem to be a way of specifically setting the ST60 to output in
RS-232 serial mode. In addition to the SeaTalk connections on the back of
the instrument there are 2 pairs of connections marked NMEA Out and NMEA In.
In addition there is a setting on the instrument for "NMEA Output ON". It
all sounds terribly logical..
Have contacted RayMarine and wait their opinion.

Thanks

Phil

"Jack Erbes" wrote in message
...
Phil Stanton wrote:
Sorry for delay in replying. Couldn't check it out till the weekend. Bags
of input from a GPS to the HyperTerminal, but nothing from the ST60
Multi. I think it could be faulty

Thanks for steering me towards the HyperTerminal. I had never heard of
it.


You're welcome. Its been a freebie with Windows as long as I can
remember, great to use as a console for talking to various devices like
switches and routers, good for testing modems, and trouble shooting some
other devices.

As an added note, someone on another group pointed out to me that
Hyperterminal will not always work as I described it. It will work for
receive only connections but if the sending device expects that there will
two way communications it will not or may not work. I'm not that smart
about RS-232 communications and can't further explain that but it sounds
reasonable to me. Nothing else in Windows is guaranteed to always work,
why should that? :)

But it has been a good trouble shooting tool for me in checking out GPS to
PC connections.

Do you know that your ST-60 is communicating in a RS-232 serial mode? If
that is a SeaTalk instrument or in that mode, it won't work because that
is Raymarine's proprietary flavor of RS-232 or something like that.

Jack

--
Jack Erbes in Ellsworth, Maine, USA - jackerbes at adelphia dot net
(also receiving email at jacker at midmaine.com)

Phil Stanton wrote:

Hi Jack

There doesn't seem to be a way of specifically setting the ST60 to output in
RS-232 serial mode. In addition to the SeaTalk connections on the back of
the instrument there are 2 pairs of connections marked NMEA Out and NMEA In.
In addition there is a setting on the instrument for "NMEA Output ON". It
all sounds terribly logical..
Have contacted RayMarine and wait their opinion.


Sounds like you're using the right connections then. NMEA is RS-232 by
definition. The ST-60 NMEA Out and NMEA In would normally be connected
to the RS-232 RXD and TXD. If you have not tried it, reversing the
connections is worth a try. The connections are made so that the NMEA
output goes to a RS-232 input and the NMEA input comes from an RS-232
output giving you the following:

NMEA Out --- RS-232 RXD
NMEA In --- RS-232 OUT

Various terms are used for the connections, the semantics can be
confusing, and human error can rear its head. So swapping the two leads
has become a routine step in trouble shooting for me.

A final thing. If one of the devices has connections for both a
"Ground" and for "Power (-)", sometimes connecting those two together
will make it work. You can test that with a temporary jumper.

An example of that was the wiring for a cable I made for NMEA serial
connection between my iPAQ 3675 and Magellan 330M. It simply would not
work until the shield on the 330M cable and lead called "Ground" on the
3675 were connected to the negative power lead.

Jack

--
Jack Erbes in Ellsworth, Maine, USA - jackerbes at adelphia dot net
(also receiving email at jacker at midmaine.com)

"Jack Erbes" wrote in message
...
Sounds like you're using the right connections then. NMEA is RS-232 by
definition.

Wrong. NMEA is RS-422 by definition. And if everyone would have adhered to
that standard, we wouldn't have so many problems with intermixing RS-422 and
RS-232 devices. Every NMEA device should have an output labeled Out A and
Out B and an input named In A and In B. NMEA standard, chapter 3. But it was
the manufacturers who made a mess of it.
Take a look at www.shipmodul.com/en/connections.html for primer on NMEA
connections.

Meindert

Meindert Sprang wrote:
"Jack Erbes" wrote in message
...

Sounds like you're using the right connections then. NMEA is RS-232 by
definition.


Wrong. NMEA is RS-422 by definition. snip

Oops. I think I meant to say it was serial by definition. Thanks for
clarifying that.

Jack

--
Jack Erbes in Ellsworth, Maine, USA - jackerbes at adelphia dot net
(also receiving email at jacker at midmaine.com)

Jack Erbes wrote in news:mPidnfR-_vQresTfRVn-
:

As an added note, someone on another group pointed out to me that
Hyperterminal will not always work as I described it. It will work for
receive only connections but if the sending device expects that there
will two way communications it will not or may not work. I'm not that
smart about RS-232 communications and can't further explain that but it
sounds reasonable to me. Nothing else in Windows is guaranteed to
always work, why should that? :)


Those problems are usually because of the hardware connections associated
with CTS (clear to send) and RTS (request to send) lines not being held
high. RS-232 is made for hardware handshaking between devices so the
listening device can stop the transmission when its buffer (bit bucket?) is
full. It goes way back to really dumb terminals that have no storage in
them for data. Jumpers added to the DB9 or DB25 connectors can make it run
wide open to hyperterm on dumb data....er, ah, like NMEA..(c;

http://www.aggsoft.com/rs232-pinout-...and-signal.htm

http://www.aggsoft.com/rs232-pinout-cable/
Aggsoft has a serial port monitor and a data logger you can download and
try for free....

http://www.connectworld.net/rs232.html

And, for you boys and girls, Mr Rogers has a website:
http://www.routergod.com/misterrogers/

The other problem is Com1 and 3 use IRQ 4 interrupt while Com2 and 4 use
IRQ 3 interrupt. If the Com1 serial mouse is attached, putting your data
on Com 3 will make it all go crazy.
http://www.bbdsoft.com/rs232.html

http://www.zytrax.com/tech/layer_1/c...tech_rs232.htm

"Jack Erbes" wrote in message
...
Meindert Sprang wrote:
Wrong. NMEA is RS-422 by definition. snip

Oops. I think I meant to say it was serial by definition. Thanks for
clarifying that.

Ah, easy slip of the mind, serial, RS-232, all sounds the same :-)

Meindert

"Meindert Sprang" wrote in
:

we wouldn't have so many problems

Actually, too bad NMEA didn't look ahead and use RS-485 as the standard. I
supports 32 talkers and 32 listeners on a single line.....

Er, ah, of course we wouldn't need to buy Meindert's MULTIPLEXERs under RS-
485. 32 talkers is plenty for most boats.....(c;

"Phil Stanton" wrote in message
...
Hi Jack

There doesn't seem to be a way of specifically setting the ST60 to output
in
RS-232 serial mode. In addition to the SeaTalk connections on the back of
the instrument there are 2 pairs of connections marked NMEA Out and NMEA
In.
In addition there is a setting on the instrument for "NMEA Output ON". It
all sounds terribly logical..
Have contacted RayMarine and wait their opinion.

Thanks

Phil

"Jack Erbes" wrote in message
...
Phil Stanton wrote:
Sorry for delay in replying. Couldn't check it out till the weekend.
Bags
of input from a GPS to the HyperTerminal, but nothing from the ST60
Multi. I think it could be faulty

Thanks for steering me towards the HyperTerminal. I had never heard of
it.


You're welcome. Its been a freebie with Windows as long as I can
remember, great to use as a console for talking to various devices like
switches and routers, good for testing modems, and trouble shooting some
other devices.

As an added note, someone on another group pointed out to me that
Hyperterminal will not always work as I described it. It will work for
receive only connections but if the sending device expects that there
will
two way communications it will not or may not work. I'm not that smart
about RS-232 communications and can't further explain that but it sounds
reasonable to me. Nothing else in Windows is guaranteed to always work,
why should that? :)

But it has been a good trouble shooting tool for me in checking out GPS
to
PC connections.

Do you know that your ST-60 is communicating in a RS-232 serial mode? If
that is a SeaTalk instrument or in that mode, it won't work because that
is Raymarine's proprietary flavor of RS-232 or something like that.

Jack

--
Jack Erbes in Ellsworth, Maine, USA - jackerbes at adelphia dot net
(also receiving email at jacker at midmaine.com)


Hi,
I was under the impression that the whole exercise was to determine if the
ST60 Multi instrument would display a negative depth if received in a NMEA
depth sentence.
For this test, you want to connect the Transmit line of the PC Com port to
NMEA IN. Connect your PC Com port pins 3 and 5 to NMEA IN + and NMEA IN -
and transmit a $SDDBT sentence from Hyperterminal to the ST60 Multi
instrument.
Start Windows program Notebook and type the following NMEA sentence:
$SDDBT,-2.0,f,,,,*22 Press Enter and save this text in a file. The
value -2.0 represents a "negative" depth of 2.0 feet.
Start Hyperterminal with the PC connected to the ST60 instrument as
described above. Click on Transfer at the top of the Hyperterminal screen
and select "Send Text File". Find the .txt file you saved with Notebook and
transmit. Repeat this a few times and it will become clear if the ST60 Multi
is willing to display a negative value. Try a positive depth first to check
if you've got the connections right, e.g. $SDDBT,3.0,f,0.9,M,0.5,F*09

Wout