1 | .. $Id: instructions.rst 896 2012-06-10 17:22:13Z jemian $ |
---|
2 | |
---|
3 | ========================== |
---|
4 | Instructions |
---|
5 | ========================== |
---|
6 | |
---|
7 | Install OPI screens (and other resources such as image files, javascript, |
---|
8 | or definition files) into projects within your workspace. The OPI screens |
---|
9 | from *synApps* [#synApps]_ will go into their own project within your |
---|
10 | workspace. The screens from the APS accelerator will go into another |
---|
11 | project. Your instrument and beam line screens will typically go into |
---|
12 | a single project but it is possible that you might have separate projects |
---|
13 | for upstream optics, beam line staff, and users. |
---|
14 | |
---|
15 | Each *project* within CSS may come from a separate location: |
---|
16 | |
---|
17 | * local directory within your account and CSS workspace |
---|
18 | * file server accessible from your directory space |
---|
19 | * NFS or SMB (Samba) file server |
---|
20 | * Version Control working directory |
---|
21 | |
---|
22 | You can't share the CSS Workspace with another user, |
---|
23 | even if that other user is logged in with the same name. |
---|
24 | This will likely cause abnormal behavior for CSS. |
---|
25 | **But**, you can import a common or shared directory into your CSS |
---|
26 | workspace. |
---|
27 | |
---|
28 | Leave the ``CSS`` project for use as a sandbox (special area for files |
---|
29 | which you are testing or using for a short time and do not wish to treat |
---|
30 | as part of everyone's workspace). |
---|
31 | |
---|
32 | |
---|
33 | Install CSS-BOY on your computer |
---|
34 | ++++++++++++++++++++++++++++++++ |
---|
35 | |
---|
36 | CSS [#CSS]_ (Control System Studio) was designed at DESY, Hamburg, Germany. |
---|
37 | CSS is software that provides a rich |
---|
38 | environment for EPICS controls. |
---|
39 | |
---|
40 | The SNS at ORNL added the BOY (Best Opi Yet -- |
---|
41 | where OPI is an EPICS term Operator Programmer Interface) |
---|
42 | component which is an EPICS display tool. |
---|
43 | For some time, APS developed a custom CSS product [#aps_css]_ to provide |
---|
44 | features and customizations that were not part of the SNS build. |
---|
45 | |
---|
46 | It is recommended now to use the CSS-BOY as built by the team at |
---|
47 | SNS [#css_boy_downloads]_. |
---|
48 | |
---|
49 | .. note:: |
---|
50 | You need a Java Runtime Environment (at least) to run CSS. |
---|
51 | Also, you will need one or more EPICS IOCs to serve PVs |
---|
52 | or all you can do is use the simulator inside CSS. |
---|
53 | |
---|
54 | #. Visit this URL and download most-recent version of |
---|
55 | **Basic EPICS** for your OS: |
---|
56 | http://ics-web.sns.ornl.gov/css/products.html |
---|
57 | #. Unzip the contents someplace. Typical for me is: |
---|
58 | ``~/Apps/CSS_EPICS_3.1.0`` |
---|
59 | |
---|
60 | |
---|
61 | add OPI screens from synApps as a CSS project |
---|
62 | +++++++++++++++++++++++++++++++++++++++++++++ |
---|
63 | |
---|
64 | #. Open the ``CSS_EPICS_3.1.0`` (or whatever version) directory |
---|
65 | #. Start ``css`` by double-clicking it |
---|
66 | #. Select menu ``File-->Import ...`` |
---|
67 | #. Open ``General`` category, |
---|
68 | select ``Existing Projects into Workspace``, |
---|
69 | click ``Next`` button |
---|
70 | #. Click ``Browse ...`` button (in *Import* window), |
---|
71 | navigate to ``/APSshare/epics/synApps_5_6/support/all_opi``, |
---|
72 | click ``Ok`` button |
---|
73 | #. Click ``Finish`` button (in *Import* window) |
---|
74 | |
---|
75 | define synApps default fonts and colors |
---|
76 | +++++++++++++++++++++++++++++++++++++++++++++ |
---|
77 | |
---|
78 | #. Select menu ``Edit-->Preferences ...`` |
---|
79 | #. Open item ``CSS Applications`` |
---|
80 | #. Open item ``Display`` |
---|
81 | #. Click on item ``BOY`` |
---|
82 | #. For Color File, replace text with ``/synApps/color.def`` or *Browse...* to it |
---|
83 | #. For Font File, replace text with ``/synApps/font.def`` or *Browse...* to it |
---|
84 | #. For Top OPIs, replace with OPI file of your choice |
---|
85 | |
---|
86 | .. note:: If get a console message that says: |
---|
87 | |
---|
88 | 2012-04-30 15:59:12 ERROR: Failed to read font definition file. |
---|
89 | |
---|
90 | then you've got a typo or some other error. Repeat these steps to fix it. |
---|
91 | |
---|
92 | |
---|
93 | Define a project for your EPICS installation |
---|
94 | +++++++++++++++++++++++++++++++++++++++++++++ |
---|
95 | |
---|
96 | Screens for your instrument or beam line or other installation of EPICS |
---|
97 | may already be available. If so, you might import them by following the steps |
---|
98 | above used to import synApps. If you need to develop your own screens, |
---|
99 | then follow these steps: |
---|
100 | |
---|
101 | #. Select menu ``File-->New`` |
---|
102 | #. Open ``General`` category, |
---|
103 | select ``Project``, |
---|
104 | click ``Next`` button |
---|
105 | #. Give it a Project name, something short such as *44ID* or *iocPRJ* |
---|
106 | (try to avoid using spaces, it makes things harder later on), |
---|
107 | #. In the ``Navigator`` view, |
---|
108 | open the new project by double-clicking (or any other equivalent way) |
---|
109 | |
---|
110 | Create an OPI file |
---|
111 | ****************** |
---|
112 | |
---|
113 | #. Select menu ``File-->New`` |
---|
114 | #. Open ``BOY`` category, |
---|
115 | select ``OPI File``, |
---|
116 | click ``Next`` button |
---|
117 | #. Select the folder to contain your new OPI screen, |
---|
118 | type the name of the new OPI file in the box, |
---|
119 | click ``Finish`` button |
---|
120 | |
---|
121 | Your new screen will appear in a CSS-BOY editing window. |
---|
122 | You might consider changing to the ``OPI Editor`` perspective |
---|
123 | as this will provide much more help in editing the screen. |
---|
124 | |
---|
125 | Once you have setup the CSS-BOY project for your EPICS installation, |
---|
126 | you might want one particular file to be the default *main* file |
---|
127 | for your CSS-BOY workspace. Edit the menu for *Top OPIs* via: |
---|
128 | ``Edit --> Preferences ... --> CSS Applications --> Display`` |
---|
129 | |
---|
130 | |
---|
131 | Notes |
---|
132 | ------------ |
---|
133 | |
---|
134 | .. note:: This could be set in in a ``.ini`` file. Needs some research... |
---|
135 | |
---|
136 | :: |
---|
137 | |
---|
138 | Edit (Menu) |
---|
139 | Preferences |
---|
140 | CSS Applications |
---|
141 | Display |
---|
142 | BOY |
---|
143 | OPI Search Path |
---|
144 | |
---|
145 | /synApps/areaDetector | /synApps/asyn | /synApps/autosave | /synApps/busy | /synApps/calc | /synApps/camac | /synApps/dac128V | /synApps/delaygen | /synApps/dxp | /synApps/iocStats | /synApps/ip | /synApps/ip330 | /synApps/ipUnidig | /synApps/love | /synApps/mca | /synApps/modbus | /synApps/motor | /synApps/optics | /synApps/quadEM | /synApps/softGlue | /synApps/sscan | /synApps/std | /synApps/vac | /synApps/vme | /synApps/xxx |
---|
146 | |
---|
147 | **PRJ:** Here are these instructions as I sent them in an email on 2012-06-10:: |
---|
148 | |
---|
149 | To get the synApps OPI screens, you need to do one of the following (subject to change as we improve this process over the next months as all these options are development status): |
---|
150 | |
---|
151 | import synApps project from /APSshare |
---|
152 | path: /APSshare/epics/synApps_5_6/support/all_opi |
---|
153 | |
---|
154 | |
---|
155 | checkout from SVN, then import project |
---|
156 | svn co https://subversion.xor.aps.anl.gov/bcdaext/cssboy_deployment/all_opi/ /path/to/a/new/synApps_all_opi |
---|
157 | |
---|
158 | |
---|
159 | To import synApps OPI screens as a project in CSS-BOY: |
---|
160 | |
---|
161 | Menu "File" |
---|
162 | --> "Import ..." |
---|
163 | open "General" |
---|
164 | select "Existing projects into workspace" |
---|
165 | button [Next] |
---|
166 | under "Select root directory:", browse to or enter path on file system |
---|
167 | make sure checkbox is marked for "synApps" |
---|
168 | button [Finish] |
---|
169 | |
---|
170 | |
---|
171 | You will also need to get the synApps project onto your OPI search path. Here is how: |
---|
172 | |
---|
173 | Menu "CSS" |
---|
174 | --> "Preferences:" |
---|
175 | open "CSS Applications" |
---|
176 | open "Display" |
---|
177 | click on "BOY" |
---|
178 | change text in entry box for "OPI Search Path" to this really long string (all one line) |
---|
179 | |
---|
180 | /synApps/areaDetector | /synApps/asyn | /synApps/autosave | /synApps/busy | /synApps/calc | /synApps/camac | /synApps/dac128V | /synApps/delaygen | /synApps/dxp | /synApps/iocStats | /synApps/ip | /synApps/ip330 | /synApps/ipUnidig | /synApps/love | /synApps/mca | /synApps/modbus | /synApps/motor | /synApps/optics | /synApps/quadEM | /synApps/softGlue | /synApps/sscan | /synApps/std | /synApps/vac | /synApps/vme | /synApps/xxx |
---|
181 | |
---|
182 | click "Ok" until you out of the dialogs. Now the paths should work. |
---|
183 | |
---|
184 | |
---|
185 | |
---|
186 | Definitions |
---|
187 | ----------- |
---|
188 | |
---|
189 | Some of the terms used by eclipse and CSS and CSS-BOY may be unfamiliar. |
---|
190 | |
---|
191 | ============ ================================================================== |
---|
192 | term |
---|
193 | ============ ================================================================== |
---|
194 | Workspace file system directory containing directories |
---|
195 | and files used by a single CSS-BOY user |
---|
196 | Project subdirectory within a ``workspace`` containing |
---|
197 | related files and subdirectories |
---|
198 | ``.js`` javascript file |
---|
199 | ``.opi`` display screen file used by CSS-BOY |
---|
200 | Perspective Defined arrangement of Views and Editors in eclipse. |
---|
201 | A Perspective can be customized and saved within |
---|
202 | the Workspace for later recall. |
---|
203 | View One type of display in eclipse, some can be undocked |
---|
204 | (or torn-off) so they can be a spearate window. |
---|
205 | ??? Are undocked Views saved as part of the |
---|
206 | Perspective? ??? |
---|
207 | Editor One type of display in eclipse. |
---|
208 | Navigator Used to browse the Workspace for files and subdirectories. |
---|
209 | eclipse Java-based software providing a configurable interactive |
---|
210 | development environment (IDE). Eclipse can be highly |
---|
211 | customized to deliver a specific application, |
---|
212 | such as CSS or CSS-BOY. |
---|
213 | CSS Control System Studio from DESY, based on eclipse |
---|
214 | CSS-BOY CSS Best Opi Yet EPICS Display software (replacement for medm) |
---|
215 | ============ ================================================================== |
---|
216 | |
---|
217 | Footnotes |
---|
218 | --------- |
---|
219 | |
---|
220 | .. [#eclipse] http://eclipse.org |
---|
221 | .. [#css_boy_downloads] http://ics-web.sns.ornl.gov/css/products.html |
---|
222 | .. [#css] http://css.desy.de |
---|
223 | .. [#aps_css] http://css.aps.anl.gov |
---|
224 | .. [#synApps] http://www.aps.anl.gov/bcda/synApps |
---|