26 Nov
2001
26 Nov
'01
10:17 a.m.
On Mon, 26 Nov 2001, Ethan Dicks wrote:
Well... I _hadn't_ yet. I was still rolling
around design ideas in my
head. I haven't written a byte of code yet. I really hadn't thought
that serial access was going to be a problem, but, I haven't ever
tried it from Perl. :-( I was contemplating passing a serial device
descriptor ('/dev/ttyS01', '/dev/ttya', etc.) as part of the object
constructor or as a seperate method (i.e.,
$hcr->setSerialPort($port_name)). I must admit that I never gave
DOS/Win32 Perl a single thought. I was only thinking of Solaris/Linux
since that's what I run at home. I even have Perl on my W2K laptop
(from work) - I just don't ever have cause to run it.
Well, you certainly want to check out Device::SerialPort then. As I said
before, the interface mostly sucks, but it will be good enough for what
you want to do (send commands and receive data). I am just used to having
more control of the serial stream.
The constructor in this module works pretty much as you describe. I can
help you get up and running with it so you can cut out some development
time. Once you get used to it it's pretty easy to use.
Unix has a powerful but very complex interface to the serial port. There
are a couple good tutors online for accessing serial ports in Unix, but I
haven't gotten around to hacking up a good library. I just don't have
that kind of patience anymore, though a better one is sorely needed for
Perl.
Sellam Ismail Vintage Computer Festival
------------------------------------------------------------------------------
International Man of Intrigue and Danger http://www.vintage.org