J.C. Roberts wrote:
You could automate everything as a shell script using only the utilities
in the base install, in short telnet over serial.
sounds interesting, i'll see what i can do with this first. any further
info you could provide here would be nice.
I usually don't get the luxury of UNIX shell scripting, and often have a
cross platform requirement, so I normally do the coding in perl. The
following ports will be needed and they have win32 counterparts.
/usr/ports/comms/p5-Device-SerialPort
/usr/ports/net/p5-Net-Telnet
if i need more involved data collection, i'll do it in perl or C, thanks
for the pointers here.
PLEASE BE WARNED: If you have strict timing requirements, particularly
machine operator safety requirements (i.e. people operating potentially
dangerous machines), the *ONLY* correct way to do machine automation is
to use a (hard/soft) real time operating system and write your code in
C to enforce your timing.
<sarcasm>
and this whole time i thought the correct way to automate machines is to
expose them to a myriad of repeated short video clips on a television,
have them join a fraternity and put a big ol' ladder in front of them.
i can't wait until we can code that in C.
</sarcasm>
i am well aware that running heavy machinery can be extremely dangerous.
this data is only being used for performance analysis and has no effect
on the machinery in question. your concern is appreciated.
warm regards,
jake
