Hi Phil,
Another way: you can try this https://github.com/NSLS-II/elauncher .
“Device support for easy script launcher: one can run a Python (or shell, or anything you can use in a Linux terminal) script inside an IOC through a bo record.”.
A simple bo record looks like this:
record(bo, "elauncherTestCommand") {
field(DTYP, "Launcher")
field(OUT, "@ps -ef | grep -i elauncher")
field(SCAN, "5 second")
field(VAL, "0")
field(ZNAM, "Name for zero")
field(ONAM, "Name for one")
}
A more advanced module: http://mdavidsaver.github.io/pyDevSup/
Cheers,
Yong
From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Reply-To: Mark Rivers <rivers at cars.uchicago.edu>
Date: Monday, May 9, 2022 at 10:35 AM
To: "Phillip A. Sorensen" <pas37 at cornell.edu>
Cc: "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Subject: RE: Device support of asyn port driver for system commands.
That sounds like something that would be pretty straightforward to do with an SNL program or an asub record.
-----Original Message-----
Sent: Monday, May 9, 2022 9:17 AM
Subject: Device support of asyn port driver for system commands.
I would like to be able to call a system binary from an IOC record.
Something like execute a command when a BO record is set to one, or read the result of a command into a AI record, etc. Does any one have device support or asyn port driver that might do something like this?
The other option I am looking at is writing something with like PCASpy or caproto.