[Win32] Serial ports
am 21.11.2007 21:32:51 von Joe.TsengThis is a multi-part message in MIME format.
--===============1803911681==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C82C7D.B09FC4E7"
This is a multi-part message in MIME format.
------_=_NextPart_001_01C82C7D.B09FC4E7
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
All,
=20
We have an OO perl framework here that utilizes Win32::SerialPort to
automate configuration of various network devices. One of the things we
like to do is capture device state; as a result on occasion we generate
alot of data that's piped through the console. We've noticed there are
issues with Win32::SerialPort choking while processing this data.
Another problem we've got is that our Perl scripts also seem to "forget"
it's got COM ports open. On occasion when we have a PORT_OBJ instance
saved as an object's property, that property may be nulled out for some
unknown reason during execution, and this behavior cannot be reliably
replicated.
=20
I was wondering if there was some alternative to using SerialPort.
Would WMI be something we could look into? Is there any Perl code
available that could do TCP->Serial mapping?
=20
- Joe
------_=_NextPart_001_01C82C7D.B09FC4E7
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
charset=3Dus-ascii">
have an OO perl=20
framework here that utilizes Win32::SerialPort to =
automate configuration=20
of various network devices. One of the things we like to do =
is=20
capture device state; as a result on occasion we generate alot of data =
that's=20
piped through the console. We've noticed there are issues with=20
Win32::SerialPort choking while processing this data. Another =
problem=20
we've got is that our Perl scripts also seem to "forget" it's got COM =
ports=20
open. On occasion when we have a PORT_OBJ instance saved =
as an=20
object's property, that property may be nulled out for some unknown =
reason=20
during execution, and this behavior cannot be reliably=20
replicated.
wondering if=20
there was some alternative to using SerialPort. Would WMI be =
something we=20
could look into? Is there any Perl code available that could do=20
TCP->Serial mapping?
Joe
------_=_NextPart_001_01C82C7D.B09FC4E7--
--===============1803911681==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
ActivePerl mailing list
ActivePerl@listserv.ActiveState.com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
--===============1803911681==--