Differences between revisions 2 and 3
Revision 2 as of 2009-10-09 06:33:14
Size: 3842
Comment:
Revision 3 as of 2009-10-31 02:20:15
Size: 3997
Comment:
Deletions are marked like this. Additions are marked like this.
Line 13: Line 13:
 * '''/cvs/cds/caltech/target/c1omc/'''  * '''/cvs/cds/caltech/target/c1ass/'''
Line 26: Line 26:
You can modify the Simulink model 'omc.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 [http://www.ligo.caltech.edu/%7Eaivanov/daq_handbook.html LIGO Data Acquisition Handbook], not sure how relevant this is to the C1OMC system. 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 [http://www.ligo.caltech.edu/%7Eaivanov/daq_handbook.html LIGO Data Acquisition Handbook], not sure how relevant this is to the C1ASS system.
Line 28: Line 28:
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. 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.
Line 35: Line 35:
{{{ make omc}}} {{{ make ass}}}
Line 37: Line 37:
Where 'omc' is the name of the Simulink model. This will generate a whole bunch of files and folders in the '''advLigo/target''' directory. Where 'ass' is the name of the Simulink model. This will generate a whole bunch of files and folders in the '''advLigo/target''' directory.
Line 39: Line 39:
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. 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.
Line 44: Line 44:
Copy the file in '''advLigo/target/omcepics/db/C1/autoBurt.req''' to '''/cvs/cds/caltech/target/c1omcepics''' Copy the file in '''advLigo/target/assepics/db/C1/autoBurt.req''' to '''/cvs/cds/caltech/target/c1assepics'''
Line 46: Line 46:
Find the file 'omc.par' in '''advLigo/build/omcepics''', and modify it with the following sed commands: Find the file 'ass.par' in '''advLigo/build/assepics''', and modify it with the following sed commands:
Line 62: Line 62:
Then rename it as 'tpchn_C2.par', and place it in '''/cvs/cds/caltech/chans/param/''' (why renaming?) Then rename it as 'tpchn_C2.par' (C2 is for OMC....this may be different for ASS), and place it in '''/cvs/cds/caltech/chans/param/''' (why renaming?)
Line 68: Line 68:
Copy the generated front-end executable in '''advLigo/src/fe/omc/omcfe.rtl''' to '''/cvs/cds/caltech/target/c1omc/'''. Copy the generated front-end executable in '''advLigo/src/fe/ass/assfe.rtl''' to '''/cvs/cds/caltech/target/c1ass/'''.
Line 72: Line 72:

=== This part may only be relevant once we get the PCIX card attached to the ASS working / hooked up ===
Line 83: Line 85:
Use the procedure in the wiki to restart c1omc [http://lhocds.ligo-wa.caltech.edu:8000/40m/Computer_Restart_Procedures#c1omc c1omc restart] Use the procedure in the wiki to restart c1omc [http://lhocds.ligo-wa.caltech.edu:8000/40m/Computer_Restart_Procedures#c1ass c1ass restart]

How to Make the ASS

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

  • advLigo/

    • This is the top working/modeling directory at a location to your taste.
  • /cvs/cds/caltech/target/c1ass/

    • This is the frontend executable directory with the .rtl files.
  • /cvs/cds/caltech/chans/daq/

    • This is the DAQ/Frame builder configuration directory on the PCIX front-end computer

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 ([http://ldas-sw.ligo.caltech.edu/cgi-bin/cvsweb.cgi/cds/?cvsroot=CDS 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 [http://www.ligo.caltech.edu/%7Eaivanov/daq_handbook.html 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

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:

  • s/%IFO%/C1/g
    • Set the %IFO% to your local IFO-name.
  • s/datarate = 16384/datarate = 32768/g
    • Set the datarate to your local configuration.
  • s/ifoid = 1/ifoid = 0/g
    • Set the ifoid to your local ifo ID.
  • s/rmid = 0/rmid = 1/g
    • Set rmid to your local reflective memory ID.

See also [http://www.ligo.caltech.edu/%7Eaivanov/daq_handbook.html#Configuration%20Files|region Configuration Files] which has more details about these settings.

Then rename it as 'tpchn_C2.par' (C2 is for OMC....this may be different for ASS), and place it in /cvs/cds/caltech/chans/param/ (why renaming?)

Example: []

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 c1omc [http://lhocds.ligo-wa.caltech.edu:8000/40m/Computer_Restart_Procedures#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)