Re: sequencer programs in an IOC

[Jiro Fujita <jiro@creighton.edu>]

James, 

In short, when you write a program in state notation language (that you use for EPICS sequencer) and make the IOC, it first gets covered to C code via SNC (SNL to C compiler).  Then, the resulting C code get compiled by GCC.  In general, you should not have to do much with the C code; certainly, anything we use at STAR soft IOC, we should not have to do much with it.  


On Jan 22, 2013, at 9:56 AM, James F Ross wrote:

> Hello everyone,
> I'm trying to understand an IOC that generates a controls monitoring webpage at STAR.  For whatever reason, the IOC is not writing the html file that it should be (it has worked in the past).
> 
> The source code is a number of .stt files, each of which handles variables for a different subsystem.  Ultimately all of these variables are brought together using a file called overall.stt, and the webpage is written by a file called overallhtml.stt.  
> 
> When the IOC is compiled, these .stt files produce .c files of the same name.  What I'm wondering is, how are these c files used?  Do they become binary files when the IOC is compiled?  What generally happens in an IOC between these c files and a sequencer program being called in the start up script for the IOC?  
> 
> The sequencer programs are loaded as follows in the IOC startup file:
> seq mot_gas
> seq trig
> seq eemc
> seq bemc
> seq tofm
> seq overall
> seq overallhtml
> 
> Are these binary executable files that are being called, or does the startup script read the c code directly?  I can't find any binary files by these names on the computer, but I see no errors while compiling either.  If anyone has any insight I could use a hand.  I know you won't know specifics on my setup, but any help with sequencer programs in general would be nice.
> 
> Thanks very much!
> James Ross
>