Here is described the various steps on how to get a new Simulink model running on the new PCIX front-end computers (in this work the C1OMC at the 40m).

This writing is an glorified version of R. Wards entry in the 40m ilog ([http://www.ldas-sw.ligo.caltech.edu/ilog/pub/ilog.cgi?group=40m&date_to_view=11/06/2006&anchor_to_scroll_to=2006:11:06:17:34:27-rward entry]).

Directory structure

• advLigo/
  • This is the top working/modeling directory at a location to your taste.
• /cvs/cds/caltech/target/c1omc/
  • This is the frontend executable directory with the .rtl files.
• /cvs/cds/caltech/chans/param/
  • This is the .. directory on the PCIX front-end computer.
• /cvs/cds/caltech/chans/daq/
  • This is the .. directory on the PCIX front-end computer

Simulink model

Get the latest CVS code from ([http://ldas-sw.ligo.caltech.edu/cgi-bin/cvsweb.cgi/cds/?cvsroot=CDS LIGO/LSC CVS Repositories]) and place it in a suitable directory to work in. There are a few special Simulink modules for the ADC and DAC, LIGO filter modules, etc. which are required.

You can modify the Simulink model 'omc.mdl' appropriately. Make sure you have the correct dcuid number, as it could be wrong in CVS. For more info on this see [http://www.ligo.caltech.edu/%7Eaivanov/daq_handbook.html LIGO Data Acquisition Handbook], not sure how relevant this is to the C1OMC system.

The Simulink model can only have a three (3) character file name, which usually correspond to the system name here 'omc'. Also, the model itself can only be 1 layer deep (due to current restrictions). This means that in your Simulink model you have a top-layer, and you are only allowed to place a sub-layer in your model. You can have multiple sub-layers in your top-layer.

Making the FE code

To make the real-time linux executable, go to the top directory (advLigo/) and type 'make omc'. Where 'omc' is the name of the Simulink model. This will generate a whole bunch of files and folders in the advLigo/target directory.

On the C1OMC front-end computer, remove the old target directories (c1omc and c1omcepics). Then copy the advLigo/target/omcepics to /cvs/cds/caltech/target/c1omcepics on the front-end computer.

Checking/updating the parameter files

copy the file in advLigo/target/omcepics/db/C1/autoBurt.req to target/c1omcepics find the file omc.par in advLigo/build/omcepics, and modify it with the following sed commands: s/%IFO%/C1/g s/datarate = 16384/datarate = 32768/g s/ifoid = 1/ifoid = 0/g s/rmid = 0/rmid = 1/g

Then rename it as tpchn_C2.par, and place it in /cvs/cds/caltech/chans/param/

Location of the FE executable

copy the front-end executable in advLigo/src/fe/omc/omcfe.rtl to /cvs/cds/caltech/target/c1omc/

DAQ Chennels

take the file located at advLigo/src/epics/util/C1OMC.ini, modify it to suit your tastes, and place it in /cvs/cds/caltech/chans/daq/

take the file located at advLigo/src/epics/util/C1OMC.txt, and put it in /cvs/cds/caltech/chans/

=== Restarting the FE ==

use the procedure in the wiki to restart c1omc