Re: Opening high-numbered COM ports

Were there any clues passed around which I missed or is this still among the
great unsolved mysteries? Just curiosity today, perhaps a life or death,
show stopping requirement tomorrow. We never know.

******************************************
"Curiosity is the hunger of reason"
from Space Relations: SF by Donald Barr; Charterhouse 1973

> ----------
> From: Bob Nash[SMTP:BNash_at_smud.org]
> Reply To: sftalk_at_forth.com
> Sent: Wednesday, February 14, 2001 2:40 PM
> To: sftalk_at_forth.com
> Subject: [sftalk] Opening high-numbered COM ports
>
> Has anyone used the words contained in ComPort.f to access high-numbered
> com
> ports?
>
> For example, I am using a multi-port serial device that attaches to my PC
> via a ethernet port (similar to a terminal server, but for raw RS-232 with
> handshake).
>
> The device maps 8 com ports to COM13 through COM20. I can bring up
> Hyperterm and talk to these ports just fine. I can also access these
> ports
> with other programs such as Wonderware.
>
> I can use the SF ComPort access words to communicate with COM1 and COM2,
> the
> local PC ports. I have also accessed local PC ports COM3 and COM4 on a
> different machine.
>
> But, when I pass a number like 13 or 15 to OPEN, I get a bad ior (-1). I
> have also verified that the right number gets into PORT and that the
> correct
> zstring (COM13) is generated for the Windows call. I have also verified
> that COM13 has a "CLOSED" status before attempting to open it.
>
> Does anyone know what Hyperterm knows about opening these ports that the
> ComPort routines do not?
>
> P.S. The device I am using is Nport Server manufactured by MOXA.
>
> Robert Nash bnash_at_SMUD.org <mailto:bnash_at_SMUD.org> Tel: 916-732-5150
> FAX:
> 916-732-6846
>
----------------------------------------------------------------------
sftalk_at_forth.com The SwiftForth programming discussion email list
Received on Tue Mar 20 2001 - 11:31:43 PST