1. Help with serial I/O
Hi,
I need some help in serial I/O. My goal is to develop an application for
interacting with a host. In the specific the host is a digital switch
exchange, which has its own command language. This application will send
commands to the switch and (this is the point) read output from it. I think
I will complete this with a sort of "macro language" to build on top of the
existing one, which is very rude.
If somebody knows 'expect' which is built with TCL, he knows what i mean.
I tried to use serial I/O routines i found on Euphoria Web site, but with no
result. Anyone out there has some info or, better 
, code ?
Many TIA,
Maurizio
---------------------------------------------------------
Maurizio Moroni
Omnitel Pronto Italia SpA
Network Testing Dept.
e-mail : maurizio.moroni at omnitel.it
---------------------------------------------------------
2. Re: Help with serial I/O
At 02:08 PM 5/27/98 +0200, Maurizio Moron wrote:
>Hi,
>
>I need some help in serial I/O. My goal is to develop an application for
>interacting with a host. In the specific the host is a digital switch
>exchange, which has its own command language. This application will send
>commands to the switch and (this is the point) read output from it.
>I tried to use serial I/O routines i found on Euphoria Web site, but with no
>result. Anyone out there has some info or, better , code ?
When you say "no result", do you mean that you were unable to
send or receive *anything*, or that it was unreliable?
I connected a computer to a digital pbx a few years ago to
log calls. The pbx used 9600 baud. There's also the question of handshaking
and parity. The one I connected to used hardware handshaking.
Which ports.e are you using? Jacques Deschenes' ports.e routines
are written in assembler, some of the earlier ports.e were not,
and so are too slow.
This is an interesting application for Euphoria - please keep
us informed on your progress.
Regards,
Irv
3. Re: Help with serial I/O
At 08:38 AM 5/27/98 -0400, you wrote:
>---------------------- Information from the mail header -----------------------
>Sender: Euphoria Programming for MS-DOS <EUPHORIA at LISTSERV.MUOHIO.EDU>
>Poster: mountains at MINDSPRING.COM
>Subject: Re: Help with serial I/O
>-------------------------------------------------------------------------------
>
>At 02:08 PM 5/27/98 +0200, Maurizio Moron wrote:
Maurizio: Please excuse the typo above ^^^. Mea culpa!
]
Irv
4. Re: Help with serial I/O
Greg Harris wrote:
> Have you tried to communicate with an existing terminal program?
From
> that you could derive the need communication settings. It may not
be the
> standard 8N1.
I am able to communicate using any existing terminal program. The settings
are 9600, 7E2 (!). I have also downloaded e-term package from Irv's web
site. I works quite fine, but I still receive some "garbage" when the switch
displays the login prompt. Due to this, I'm not able to input username and
password correctly, because the switch always gives me an authorization
failure message.
I think it's a problem in interpreting some escape sequence sent by the
switch. I will investigate....
> You maybe able to use a FOSSIL driver with it. Like X00 or BNU. I
coded
> in the past a terminal in Euphoria that works with a FOSSIL driver
but I
> have deleted the routines. I probably could recode them as several
> people have asked for them.
Anything would be *very* appreciate !!!!
Thanks,
Maurizio
5. Re: Help with serial I/O
At 03:47 PM 5/27/98 +0200, Maurizio wrote:
>I am able to communicate using any existing terminal program. The settings
>are 9600, 7E2 (!). I have also downloaded e-term package from Irv's web
>site. I works quite fine, but I still receive some "garbage" when the switch
>displays the login prompt. Due to this, I'm not able to input username and
>password correctly, because the switch always gives me an authorization
>failure message.
>
>I think it's a problem in interpreting some escape sequence sent by the
>switch. I will investigate....
E-term2 should be able to keep up with 9600 baud (at least
short bursts). You may be right about the escape sequences.
The pbx we were connected to was designed to talk to a WYZE
terminal, not a pc. Therefore it sent some "weird" codes -
cursor position, etc. Don't count on them all beginning with
esc, either.
Hopefully, the info will be in the manual
(and, hopefully, I will win the lottery - about the same chance)
The manufacturers of the switch may give you some info, but
most likely you will have to find this out by trial and error.
There are a couple of DOS port monitor programs available on
the web. They can keep track of the input and the output
streams, so you can see what's going on. I'm sorry I don't
remember the names.
I think it would be good to rewrite e-term.ex so it sends a line
at a time, rather character by character. You could avoid
echoing the ugly backspace character this way.
Irv
