On Tuesday 18 June 2002 9:27 am, Matt Hinds wrote:
Hi,
Thanks to those people who responded about my previous query - proved useful. However the next problem I have is trying to get my system to communicate with the data logging equipment on the serial port. I know the equipment works, however the software is having no joy communicating with it. How do you enable/configure the serial ports? I've tried using a combination of SetSerial and stty but to no joy!
Thanks in advance!
Cheers, Matt
Hi Matt, don't know if this is any use to you if you want two-way comms, but a simple method I use to collect call logging info from our switches is to use kermit. My script calls Kermit to get the data and then pass it to a perl script which cleans the output and stores it in a PostgreSQL db - i.e. #!/bin/bash # cmsrun - called from inittab to start call logging cd /home/cms/data # roll on log file cat cms.log >>cms.full cat /dev/null >cms.log rm -f /var/lock/LCK..ttyS0 # remote spurious locks #kermit cms.script >cms.out 2>&1 kermit ~/bin/cms.script|~/bin/cmsctrl Leeds 2>cms.err >cms.out #cms.script set port /dev/ttyS1 set speed 9600 set carrier-watch off set parity none set flow-control xon/xoff log session cms.log c
Legal Disclaimer:
This e-mail is for the intended recipient only. If an addressing or transmission error has misdirected this e-mail, please notify the sender by replying to this e-mail. If you are not the intended recipient you must not use, disclose, distribute, copy, print or rely on this e-mail. The opinions expressed in this message are those of the sender and not those of Heworth Grange Comprehensive School.
Hmmm, hope this means me !!! -- Gary Stainburn This email does not contain private or confidential material as it may be snooped on by interested government parties for unknown and undisclosed purposes - Regulation of Investigatory Powers Act, 2000