|
Size: 1141
Comment:
|
Size: 1921
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 8: | Line 8: |
| This is the top working/modeling directory at a location to your taste. | This is the top working/modeling directory at a location to your taste. |
| Line 10: | Line 10: |
| * /cvs/cds/caltech/target/c1omc/ This is the frontend executable directory with the .rtl files. |
|
| Line 12: | Line 14: |
| This is the C1 .. directory | This is the C1OMC .. directory on the PCIX frontend computer. |
| Line 15: | Line 17: |
| This is the C1 | This is the C1 |
| Line 24: | Line 26: |
| == | 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. === Make the FE code === To make the real-time linux executable, go to the top directory (advLigo/) and type 'make omc'. Where remove the old target directories (c1omc and c1omcepics) copy the advLigo/target/omcepics to /cvs/cds/caltech/target/c1omcepics |
Here is described the various steps on how to get a new simulink model running on the new PCIX frontend 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 C1OMC .. directory on the PCIX frontend computer.
- /cvs/cds/caltech/chans/daq/
- This is the C1
Simulink model
Get the latest CVS code from (...) 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.
Make the FE code
To make the real-time linux executable, go to the top directory (advLigo/) and type 'make omc'. Where
remove the old target directories (c1omc and c1omcepics)
copy the advLigo/target/omcepics to /cvs/cds/caltech/target/c1omcepics