From: Les K. <vm...@ta...> - 2016-02-05 21:24:48
|
Lee, Jon; I don't see it on *this* list (oorexx-users)! If either of you see it here, why don't I? Les On 2/5/2016 1:04 PM, Jon Wolfers wrote: > Hi Lee, > > I do extremely occasionally get called on to approve posts on the sf lists. > Usually this is if the post is larger than the limit for the list ( I can't > remember what that is, but I think I've seen it happen twice). > > I did see your post and I have not been asked to approve any mails for a > while. > > Jon > <https://www.avast.com/sig-email> This email has been sent from a > virus-free computer protected by Avast. > www.avast.com <https://www.avast.com/sig-email> > <#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > On 5 February 2016 at 16:01, Lee Peedin <le...@sa...> wrote: > >> Thanks for the forward Les, but it appears that my post did make it to the >> list - about an hour after I sent it. Not sure if that is the way >> everyone's emails are posted or if "someone" down the pipe had to approve >> my post before it got sent to the list. >> >> Lee Peedin >> VP Research & Development >> Safe Data, Inc. >> Wallace, NC >> >> ----- Original Message ----- >> From: "Les Koehler" <vm...@ta...> >> To: wb...@ar..., "Open Object Rexx Users" < >> oor...@li...> >> Sent: Friday, February 5, 2016 10:53:56 AM >> Subject: Re: [Oorexx-users] Need help reading,writing to a "com" port >> >> On behalf of Lee Peedin who, for some reason, can receive posts but >> can't post (why?): >> >> Never used it, but there's a RxFuncAdd library out there in the >> wonderful world of the internet called "RxComm". It was written by >> Christian Kulovits (Austria). Its stated purpose: "RxComm is a REXX >> Communications application programming interface (API) package that >> provides access to serial communications devices from your REXX >> program." The web site also says "Version 1.3 with support for >> multiple REXX interpreters. (Regina, Raginald [sic], Object Rexx, >> Enterprise Rexx and Personal Rexx)" >> >> http://members.aon.at/kulovits/christian/downloads.htm >> >> I have no idea if it works, but at least this will maybe bring the >> conversation back on topic. >> >> Lee Peedin >> VP Research & Development >> Safe Data, Inc. >> Wallace, NC >> >> >> On 2/2/2016 11:47 AM, Bill Turner, WB4ALM wrote: >>> 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 >>> |