Your question is very general, and lacking a script using this module (yes, I SuperSearch'd), the best I can do is point you to what looks like very complete documentation...http://search.cpan.org/~bbirth/Win32-SerialPort-0.19/lib/Win32API/CommPort.pm.
If you have specific problems that the docs can't answer, please try to refine your question further. BTW, you may simply be having problems naming the COM port? I know that sometimes "COM1" is required and other times "COM1:" is necessary...but this helpful hint does not mean that I've ever used the module, just ones like it in other languages.
Good luck,
welchavw
| [reply] |
If you need to READ a serial port, I'd suggest using Kiwi Harvester, which forwards data received from the serial port onto a SysLog server.
For anything more complex, (Man - I'm about to show my antiquity...) you could use a scriptable Serial-port communication program, like Procomm Plus . I'm not sure if current Telnet clients like Putty or Terra Term Pro support the scripting you seem to need - but they are worth investigating, at NoNags.com.
"When you are faced with a dilemma, might as well make dilemmanade.
"
| [reply] |
Amen, CorpusDawg and Fellow Monk,
Yea tho' we walk through the valley of the RS-232 port our serial line analyzer and null modem cable comfort us.
Try this node.
Serial Port and IO Termination
GL,
Diskcrash | [reply] |