Experimental Physics and
Industrial Control System

Michael Davidsaver <[email protected]> · Fri, 26 Jun 2015 12:01:30 -0400

All the IOC shell commands are also C functions which can be called
directly.

Also, if you look in the *Main.cpp file generated by makeBaseApp, there
are two calls to iocsh().  The first with a non-NULL argument reads a
file.  The second call with NULL starts the interactive shell.

https://github.com/epics-base/epics-base/blob/3.16/src/template/base/top/iocApp/src/_APPNAME_Main.cpp

There is also iocshCmd("") which takes a shell command as a string.

> just to be more clear, the application uses the stdin/stdout to control
> its states and I cannot use it for iocsh - how can I create an IOC
> "inside" my existing application ?

That said, you might want to explore alternatives.  The IOC shell is a
handle debugging tool which I'd be reluctant to give up.

Michael

On 06/26/2015 10:29 AM, [email protected] wrote:
> 
> Hi,
> I have developed for a Linux embedded board called uSOP various EPICS IOCs
> that publish different PVs for Belle2 environmental data (temperature, 
> humidity);
> 
> to do these tasks I use makeBaseApp.pl scripts to start developing and
> the result is an IOC that provide an iocsh prompt;
> 
> now I have to add, for a new developing activity, some EPICS PVs to an
> exisiting application (not EPICS-enabled) and my question is how to do
> this in a simple and effective way...
> 
> just to be more clear, the application uses the stdin/stdout to control
> its states and I cannot use it for iocsh - how can I create an IOC
> "inside" my existing application ?
> 
> Thanks in advance,
> Gennaro
> 

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System