EM1 Update P00-06-00 10/7/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-05-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. With this release you can specify the host for command and event servers through environment variables. The environment variable names are COMMAND_SERVER_HOST and EVENT_SERVER_HOST respectively. This is especially useful when you want a script to work with different hosts at different times and you don't want to change the parameter to the connect() function every time. In fact, for this to work properly, do not pass any parameters to the connect() method.


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