This is very old, and no longer useful....

Use these instructions instead.

How to Make the ASS - OAF stuff

Computer Setup and Installation

For a detailed instruction of how to install the computer hardware and CDS software, please refer to Rolf's website, or follow the link on this page http://www.ligo.caltech.edu/~rolf/CDS_PARTS_D.html#d1060e238.

Directory structure

For a simulink generated documentaion (by Rolf) of the CDS Simulink parts, including instructions on building a model, see http://www.ligo.caltech.edu/~rolf/CDS_PARTS_D.html.

Get the latest CVS code from (LIGO/LSC CVS Repositories or CD) 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 'ass.mdl' appropriately. Make sure you have the correct dcuid number, as it could be wrong in CVS (see the link at the start of this section). For more info on this see LIGO Data Acquisition Handbook, not sure how relevant this is to the C1ASS system.

The Simulink model can only have a three (3) character file name, which usually correspond to the system name here 'ass'. 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

This takes the Simulink model which you have made, and compiles it into front end code. These instructions also walk you through installing the code so that it's ready for use. After doing all of this, you should edit your MEDM screen to match.

The newest instructions come from Koji's elog #2270.

Now BURTRESTORE the c1assepics, since we don't have the in-terminal versions of burtrestore working.

The install-daq parts are important if you're changing the number of testpoints in the front end code....i.e. you've added or removed channels.

You should check to ensure that awgtpman has been started. The awgtpman which startass used to call (/target/gds/awgtpman) has been moved to /target/gds/awgtpman.091215, and /target/gds/awgtpman has a symbolic link to /opt/gds/awgtpman, which is the awgtpman that the Computer Restart Procedures tells you to start for the ASS machine. Unfortunately, this awgtpman only allows for 16kHz systems, and the ASS is 2kHz, so this still isn't a good final solution.

The following is obsolete:

To make the real-time linux executable, go to the top directory (advLigo/) and type:

 make ass

Where 'ass' is the name of the Simulink model. This will generate a whole bunch of files and folders in the advLigo/target directory.

On the C1ASS front-end computer, remove the old target directories (c1ass and c1assepics). Then copy the advLigo/target/assepics to /cvs/cds/caltech/target/c1assepics on the front-end computer.

Checking/Updating the Configuration files

Copy the file in advLigo/target/assepics/db/C1/autoBurt.req to /cvs/cds/caltech/target/c1assepics

Find the file 'ass.par' in advLigo/build/assepics, and modify it with the following sed commands:

See also region which has more details about these settings.

Then rename it as 'tpchn_C3.par', and place it in /cvs/cds/caltech/gds/param/

Example is missing here .....

Location of the FE executable

Copy the generated front-end executable in advLigo/src/fe/ass/assfe.rtl to /cvs/cds/caltech/target/c1ass/.

DAQ Channels

This part may only be relevant once we get the PCIX card attached to the ASS working / hooked up

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/

Example: []

Restarting the FE

Use the procedure in the wiki to restart c1ass c1ass restart

WikiOfRolfCDS this is a test, which has not worked...

Simulink_to_Front-End_code/MakeOAF (last edited 2012-07-27 02:31:00 by JennedriggersATligoDOTorg)