EM1 Update P00-07-00 10/14/02

Installation Instructions
 

1. First of all make a copy of your c:\VxWorks directory (right click on VxWorks, choose "Copy" then in the same window choose "Paste"). This will create a directory called "Copy of VxWorks". Rename this to VxWorks_P00-06-00
    
2. Unzip pyLAT archive to "C:\", replacing the old files
    
3. On VxWorks enter "< startupaemevt" for AEM or "< startuptemevt" for CAL
    
4. Make sure "ActiveState Python 2.2.1 or later is installed. If not download it from:
   http://www.activestate.com/Products/Download/Download.plex?id=ActivePython
    
5. Install pyXML: Open up a "Command Prompt" and enter "pyppm". At the "PPM>" prompt enter "install pyXML". You need to have an active internet connection for this to work. If you are in an internal network, use another machine that is connected to the internet to download pyXML from http://download.sourceforge.net/pyxml/PyXML-0.8.1.win32-py2.2.exe, copy it to a floppy and then install it on the teststand machine.
    
6. Open up a "Command Prompt" and change the directory to "c:\Online\work\LAT"
    
7. Type "python -i test_aem.py" for AEM or "python -i test_cal.py" and press enter. At the ">>>" prompt type "test()" and press enter You should see the event data being displayed.
    
8. If you need to go back to using SCL, rename the VxWorks directory to VxWorks_Python and rename the VxWorks_SCL directory to VxWorks and use the "< startupaem" or "< startuptem" scripts.
    
9. We will provide tutorials and how-to documents on using the python interface in the near future. In the mean time the test_aem and test_cal examples and the LAT-SS-00586-01 Subsystem Interface Control Document should help you in developing your scripts.
    
10. In order to run the "versions" utility, at the command prompt enter "python versions.py". This should output version infor for all modules (VxWorks and python) loaded.
     
11. This release is a reorg of the python core files so that they are easier to import into the user scripts. Also in this release is the inclusion of EGU conversion functionality and constraints. See the aemEU.py file for an example.
     
12. We also removed the local flag from all block components. If you need to run the system locally you need to use the NT versions of the cmdSvr and evtSvr.
     
13. The cmdCli and evtCli class names are initial uppercase now. So you need to instantiate them in your scripts as CmdCli and EvtCli respectively.

Note1: In order to run the system without any hardware attached use the following instructions:

1. Install the package according to the above instructions.
2. Open up a 'Command Prompt', change the directory to \Online\work\LAT
3. Enter 'cmdSvr 2000'
4. Open up another 'Command Prompt', change the directory to \Online\work\LAT
5. Enter 'evtSvr 2001'
6. Open up a third 'Command Prompt', change the directory to \Online\work\LAT
7. Enter 'set COMMAND_SERVER_HOST=localhost'
8. Enter 'set EVENT_SERVER_HOST=localhost
9. Run python -i 'test_xxx.py' (where xxx is one of aem, cal, tkr depending on what subsystem you are)
10. Enter 'test()'
11. You should see the dummy event being displayed.
     

Note2: The installation installs the core python interface code into \Online\work\LAT. This is a reserved area and should not be used for subsystem development. Subsystems are encouraged to create their own directories under \Online\work (such as \Online\work\ACD or \Online\work\CAL and develop their scripts under those directories. In order to be able to import the core python interface code, in your environment, you need to set PYTHONPATH to \Online\work\LAT.
 

Version Information (retrieved by running python -i versions.py for this release):

Please contact Selim Tuvi at stuvi@slac.stanford.edu or Ric Claus at claus@slac.stanford.edu if you have problems or any questions.
 

Back