Win95 Terminal Pgm. for RS232
F L
I am trying to get HyperTerm to work with an embedded processpr's RS232
port so I can monitor the system. Anyone got this program to do this?
Seems like it has to be a dial connection only. If it is not possible
to use HyperTerm, an suggestions on a share or freeware program to
monitor the serial port on a PC?
Thanks for hany helpful information.
Dennis,
Uwe Hercksen
On Thu, 26 Feb 1998 10:18:07 -0500, F L <denn...@pop.hancock.net>
wrote:
I got it to work,
don't set any numbers to dial in the properties of the connection,
only set in the last line "connect via" "direct conection with COMx"
use the number of the COM port your embedded thing is connected to.
Click to configure and set the baud rate, data bits, parity and
stop bits to the same values used by your embedded processor. Use no
protocol for first try.
The proper connection of both serial connectors is very important!
Connect Ground to Ground, this is pin 7 on a 25 pin connector.
Transmit Data of your embedded processor to Receive Data of the PC,
pin 3
Receive Data of your embedded processor to Transmit Data of the PC,
pin 2
If your embedded Processor does not use the signals RTS, CTS, DSR, DTR
and CD, connect these at the PC side as follows:
Pin 4 RTS to Pin 5 CTS (both Pins of the same connector at the PC
side! )
Pin 6 DSR to Pin 8 CD to Pin 20 DTR.
A very common problem is the connection of TD from one side to TD of
the other side and of RD to RD. This will not work, only TD to RD and
RD to TD does work.
Sometimes you have to connect Pin 2 TD to Pin 3 RD and Pin 3 RD to Pin
2 TD, this is called a null-modem.
But sometimes the null-modem crossing is build in on one side, then
you have to connect Pin 2 with Pin 2 and Pin 3 with Pin 3.
The easiest way to check is the use of the RS 232 testers with LEDs
for each signal. Just insert this to your connection, if both LEDs for
TD and RD emit light, the connection is correct.
But if only one of this pair is bright, you will need the other way of
connection between the pins 2 and 3 of both sides.
Good luck, this is not very easy to do.
Uwe Hercksen
No....@E.Mail.please is only to protect against spam
For EMail response, please use:
User: hercksen
sub-domain: zew
domain: uni-erlangen
country: de
--------------------------------------------------
Elektronikwerkstatt Uni. Erlangen
Cauerstr. 5
D91058 Erlangen
Jeffrey D. Spiegler
In article <34f58dda...@news.uni-erlangen.de>,
No....@E.Mail.please says...
>
>On Thu, 26 Feb 1998 10:18:07 -0500, F L <denn...@pop.hancock.net>
>wrote:
>
>>I am trying to get HyperTerm to work with an embedded processpr's RS232
>>port so I can monitor the system. Anyone got this program to do this?
>>Seems like it has to be a dial connection only. If it is not possible
>>to use HyperTerm, an suggestions on a share or freeware program to
>>monitor the serial port on a PC?
>>
>>Thanks for hany helpful information.
>>
>>Dennis,
>
>I got it to work,
>
>don't set any numbers to dial in the properties of the connection,
>only set in the last line "connect via" "direct conection with COMx"
>use the number of the COM port your embedded thing is connected to.
>Click to configure and set the baud rate, data bits, parity and
>stop bits to the same values used by your embedded processor. Use no
>protocol for first try.
>
>The proper connection of both serial connectors is very important!
>
>Connect Ground to Ground, this is pin 7 on a 25 pin connector.
>Transmit Data of your embedded processor to Receive Data of the PC,
>pin 3
>Receive Data of your embedded processor to Transmit Data of the PC,
>pin 2
For 9 pin connectors:
pin 2: receive data
pin 3: transmit data
pin 5: ground
>
>If your embedded Processor does not use the signals RTS, CTS, DSR, DTR
>and CD, connect these at the PC side as follows:
>Pin 4 RTS to Pin 5 CTS (both Pins of the same connector at the PC
>side! )
>Pin 6 DSR to Pin 8 CD to Pin 20 DTR.
I didn't have to do any of this. Set Flow Control on the Configure
screen to None.
>
>A very common problem is the connection of TD from one side to TD of
>the other side and of RD to RD. This will not work, only TD to RD and
>RD to TD does work.
>Sometimes you have to connect Pin 2 TD to Pin 3 RD and Pin 3 RD to Pin
>2 TD, this is called a null-modem.
>But sometimes the null-modem crossing is build in on one side, then
>you have to connect Pin 2 with Pin 2 and Pin 3 with Pin 3.
>The easiest way to check is the use of the RS 232 testers with LEDs
>for each signal. Just insert this to your connection, if both LEDs for
>TD and RD emit light, the connection is correct.
>But if only one of this pair is bright, you will need the other way of
>connection between the pins 2 and 3 of both sides.
If you're connecting a 25 pin to a 9 pin and they're both
built/configured as DTE (data terminal equipment), you'll
be connecting pin 2 to pin 2 and pin 3 to pin 3 (and pin 7
on the 25 pin connector side to pin 5 on the 9 pin connector
side). This crosses the signals (TD <--> RD and vice-versa) even
though the wires go "straight through."
Just out of curiosity, anyone know why IBM swapped the signals
on pins 2 and 3 when they came out with the 9 pin serial connector?
>
>Good luck, this is not very easy to do.
Wasn't so bad for me...maybe half an hour.
Jeff Spiegler
Tim Forcer
F L wrote:
>
>I am trying to get HyperTerm to work with an embedded
>processpr's RS232 port so I can monitor the system.
Why not simply run the 16 bit Win3.x program "Terminal"? Should still
be on any PC which was upgraded to Win95 - just search for
"terminal.exe". If the PC came with 95 pre-installed, just find someone
with Terminal and take a copy - there's no license problem that I know,
since it's all part of Windoze. Terminal is a much simpler program, and
great for exactly your sort of application. We use Terminal to allow a
PC to host a SPARC single-board computer for a whole range of
undergraduate lab exercises - HyperTerm was just too powerful and
complex.
Tim Forcer t...@ecs.soton.ac.uk
Department of Electronics & Computer Science
The University of Southampton, UK
The University is not responsible for my opinions
Tim Forcer
I wrote:
>
>F L wrote:
>>
>>I am trying to get HyperTerm to work with an embedded
>>processpr's RS232 port so I can monitor the system.
>
>Why not simply run the 16 bit Win3.x program "Terminal"?
Downloadable from <http://www.jdstechnologies.com/downmisc.html> (site
found using Alta Vista <http://altavista.digital.com/>)
Michael A. Wiles, Sr.
I am surprised that you are having problems with hyper terminal. I use it
on a daily basis when debugging programs on a 80C31 based MPU. The only
trick is to set up a shortcut with properties that use the com port
directly. If you still encounter problems, email me and I will instruct on
how to setup a hyper terminal shortcut.
Michael A.Wiles, Sr.
mwi...@galstar.com
Tim Forcer wrote in message <34FBCD...@ecs.soton.ac.uk.nojunk>...
Anders Johansson
You can use any simple terminal program for this. If you need
more debugging features, for example displaying control characters
you might check out the serial analyzers at http://www.fifo.se
AJ
---------------------------
> >>F L wrote:
> >>>
> >>>I am trying to get HyperTerm to work with an embedded
> >>>processpr's RS232 port so I can monitor the system.
> >>
> >>Why not simply run the 16 bit Win3.x program "Terminal"?
---------------------------
Anders Johansson
Hadelko AB
e-mail and...@hadelko.se
http://www.hadelko.se
---------------------------
Josef Wolf
In <34FAB9...@ecs.soton.ac.uk.nojunk> Tim Forcer <t...@ecs.soton.ac.uk.nojunk> writes:
>Why not simply run the 16 bit Win3.x program "Terminal"? Should still
Because it don't honour RTS. When RTS is asserted, "Terminal" starts to
throw away the data much faster as it would send it over the line :-(
"Terminal" is one of the worst piece of software M$ ever made :-/
--
-- Josef Wolf -- j...@raven.inka.de -- Germersheim, Germany --
Josef Wolf
In <34F587...@pop.hancock.net> F L <denn...@pop.hancock.net> writes:
>I am trying to get HyperTerm to work with an embedded processpr's RS232
I've done. I can't recommend that. Hyperterm will bring your Pentium
down to approx 8088. Accept that M$ don't know how to handle a serial
line and use SW from an other vendor :-/
>Seems like it has to be a dial connection only. If it is not possible
>to use HyperTerm, an suggestions on a share or freeware program to
>monitor the serial port on a PC?
I'm using Term-95 from Norton-Commander. Very ugly, but at least it knows
how to deal with rs232...
Chris
Josef Wolf wrote...
>>I am trying to get HyperTerm to work with an embedded processpr's RS232
>>port so I can monitor the system. Anyone got this program to do this?
>
>I've done. I can't recommend that. Hyperterm will bring your Pentium
>down to approx 8088. Accept that M$ don't know how to handle a serial
>line and use SW from an other vendor :-/
>
>>Seems like it has to be a dial connection only. If it is not possible
>>to use HyperTerm, an suggestions on a share or freeware program to
>>monitor the serial port on a PC?
>
>I'm using Term-95 from Norton-Commander. Very ugly, but at least it knows
>how to deal with rs232...
Hello,
Why don´t using TERMINAL.EXE from Windows 3.1? Small, but working perfectly
under Win95. Not "free", but who hasn´t got an old Win3.1 license?
Christian Keydel
ChKe...@hitex.de
http://www.hitex.de
Tim Forcer
Chris wrote:
>
>...
> Why don´t using TERMINAL.EXE from Windows 3.1? Small, but working perfectly
> under Win95. Not "free", but who hasn´t got an old Win3.1 license?
As I posted in this thread on March 3:
Quote+++++
Downloadable from <http://www.jdstechnologies.com/downmisc.html> (site
found using Alta Vista <http://altavista.digital.com/>)
---Unquote
Tim Forcer t...@ecs.soton.ac.uk
Josef Wolf
In <6eqsgq$p81$1...@news.nacamar.de> "Chris" <Christian.Keydel@_remove_this_t-online.de> writes:
>Josef Wolf wrote...
>>I've done. I can't recommend that. Hyperterm will bring your Pentium
>>down to approx 8088. Accept that M$ don't know how to handle a serial
>>line and use SW from an other vendor :-/
>>I'm using Term-95 from Norton-Commander. Very ugly, but at least it knows
>>how to deal with rs232...
>Why don´t using TERMINAL.EXE from Windows 3.1? Small, but working perfectly
>under Win95. Not "free", but who hasn´t got an old Win3.1 license?
I've already written in this thread that terminal.exe don't know how
to handle RTS. Just try it: send a huge ascii-file with terminal.exe
and raise RTS. From now on terminal.exe will redirect the data into
/dev/null instead of stoping and waiting until RTS again will go down.
I don't know of any M$ product which knows how a rs232 is _really_ to
be handled. Terminal.exe don't know about Handshaking and Hyperterm
will bind your CPU to the serial line and ignore all the other tasks.
Ian Wilson
I agree, we use Win 95 Hyper Terminal all the time for monitoring
embedded processors (3 wire RS232 port - TX, RX and GND).
Just connect "direct to Com1" or "direct to Com2:" ...
Disable flow control if necessary.
Ian Wilson
Anders Johansson <and...@hadelko.se> wrote:
>You can use any simple terminal program for this. If you need
>more debugging features, for example displaying control characters
>you might check out the serial analyzers at http://www.fifo.se
>AJ
>---------------------------
>> >>F L wrote:
>> >>>
>> >>>I am trying to get HyperTerm to work with an embedded
>> >>>processpr's RS232 port so I can monitor the system.
>> >>
>> >>Why not simply run the 16 bit Win3.x program "Terminal"?
>---------------------------
Anders Johansson
Check out the serial analyzers on http://www.fifo.se
Anders
----------------------------------
>any suggestions on a share or freeware program to
>monitor the serial port on a PC?
--
---------------------------
Anders Johansson
Hadelko AB
Kronobränneriet
302 42 Halmstad
Sweden
Tel +46 (0)35 102550
Fax +46 (0)35 187515
Rolf Skowronek
Ian Wilson (le...@ozemail.com.au) wrote:
: I agree, we use Win 95 Hyper Terminal all the time for monitoring
: embedded processors (3 wire RS232 port - TX, RX and GND).
: Just connect "direct to Com1" or "direct to Com2:" ...
: Disable flow control if necessary.
: Ian Wilson
: Anders Johansson <and...@hadelko.se> wrote:
: >You can use any simple terminal program for this. If you need
: >more debugging features, for example displaying control characters
: >you might check out the serial analyzers at http://www.fifo.se
: >AJ
: >---------------------------
: >> >>F L wrote:
: >> >>>
: >> >>>I am trying to get HyperTerm to work with an embedded
: >> >>>processpr's RS232 port so I can monitor the system.
: >> >>
: >> >>Why not simply run the 16 bit Win3.x program "Terminal"?
Did you try Kermit?
Whenever I needed a terminalprogram I have been using Kermit and it always
worked well. I don't have much any experience with W95 though.
Rolf
Steve the funky Antechinus
j...@raven.inka.de (Josef Wolf) wrote:
>I've done. I can't recommend that. Hyperterm will bring your Pentium
>down to approx 8088. Accept that M$ don't know how to handle a serial
>line and use SW from an other vendor :-/
we downloaded the update from the makers of Hyperterminal (whose name
I can't remember) in the vain hope that it would be better. And in
some ways it was;
- it could now write to the screen at the same time as sending (the
previous version would buffer everything)
- It didn't crash when you tried to send a file that was in use by
another program.
But that was about all. As a bonus we got a cheap and tacky opening
graphic.
We tried sending ascii files using hardware handshaking and found that
it was unreliable, losing characters every now and then. It only
worked reliably when the buffer thresholds (that control the
handshaking) were set between 10 and 100 characters apart.
So we decided to support it, not use it. So now our software has
crippled buffer thresholds thanks to microsoft. Our product *was*
microsoft free, but they always get in somehow....
-----------------
Steve Bauer
OmniTel (Australia)
ste...@spamfree.omnitel.com.au
Real people remove the spamfree bit.
+61 3 9419 8833