This has been cross-posted to "ooRexxUsers" and "ooRexx-devel"
==============================================================
I am now a volunteer and am associated with a County Emergency
Operations Center, and I need to put some "very old" radio
equipment back into service...

...some of which likes to communicate with a computer via an RS-232
connection.  Since most modern computers do not have RS-232 ports
anymore, I have purchased an RS-232 USB adapter cable.

I am finding that my knowledge on how to use ooRexx to communicate
with an RS-232 port is VERY limited...
...and I am having problems making it work.

1. I will be using this equipment with Windows 10 and with Linux.
    My primary test environment is Linux: Ubuntu 14.04 with Cinammon
    (Don't like UNITY!)
2. ooRexx 4.2 on all systems.
3. The USB cable shows up as  /dev/ttyUSB0  under Linux
    and as  COM1  under windows.
4. The external equipment works in a half-duplex mode.
    You send it a command and it responds with an answer.
    The "commands" are formatted in a manner very similiar to
    the old Hayes modem commands, I.E.
     "AT" followed by a command text followed by a carriage return
     (all upper case!)


I know that the hardware works, since I can use "minicom" on Linux
to communicate with the external device, which only supports
300 or 1200 baud, 8-bits no-parity or 7-bits even/odd parity.


Questions:
1. Is there a way to specify port speed, parity, etc. from INSIDE
    the ooRexx routine?

    Under Linux, I can use "stty" externally, but can not invoke it
    internally from the ooRexx routine because the change is not
    maintained for the remainder of the duration of the rexx exec.
    (apparently this is an Enviromental/Shell issue... ???)

2. More importantly, does anybody have a simple read/write ooRexx
    sample that can talk to a com port? (I beleive that stream IO
    and charin/charout are required. Lineout doesn't seem to
    transmit anything, but charout does.)

    I can get my routine to transmit, but I do not seem to be able
    to receive any data.

    Normal use:  I send a command like "ATRT" <CR>, and it responds
                 with a 6-digit message and a <CR> or <CRLF>.


3. I know that data is being transmited, because I can see the
    "flashing lights" on my rs-232 test adapter. I think, however,
    that the speed or parity might be wrong, as the remote device
    does not seem to be responding.

    As I said, the remote device uses commands that start with "AT"
    like those used in the old Hayes modems, and it will respond
    with either a "0" <CR> or possibly a 4 to 8 character message and
    a <CR> when it recognizes a command request.

4. any help would be appreciated.

/s/ Bill Turner, wb4alm


------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
Oorexx-users mailing list
Oorexx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-users

Reply via email to