...
| No Format |
|---|
aidaget P2BPMHER//BPMS -DBPMD=38 -DREF=0 BPMS:PR10:6012 0.0 0.0 3128.0562 0.0 17 520 BPMS:PR10:6022 0.0 0.0 3135.6562 0.0 17 520 BPMS:PR10:6032 0.0 0.0 3143.256 0.0 17 520 BPMS:PR10:6042 0.0 0.0 3150.8562 . |
Getting Magnets:
| No Format |
|---|
clarrieu@tersk09>aidaget LINAC//XCOR:BDES -DMICROS=LI10-LI10 -DUNITS=1-9999 XCOR:LI10:200 0.0 17 520 BPMSXCOR:PR10LI10:6052 201 0.0 XCOR:LI10:202 0.0 3158.4563 0.0 17 520 ... |
Setting Value: aidaset
The utility program named "aidaset" takes at least two mandatory arguments (the name of the target and the desired value), and several optional parameters control how it operates.
...
In the EPICS channel access example, we sent a single unnamed value. In the magnet example, we sent a named value. As you can see, the magent server expects two vectors, one listing magnet names and the other listing the corresponding desired values. Unless the data provider documentation indicates otherwise, the names of the vectors are not important. The following is equivalent to the above example:
| No Format |
|---|
aidasetaidaset MAGNETSET//BDES -DMAGFUNC=TRIM /sun XCOR:LI31:41 /moon 4.0 |
...
| No Format |
|---|
aidaset MAGNETSET//BDES -DMAGFUNC=TRIM /names XCOR:LI10:200 XCOR:LI10:201 /values 0.0123 -0.0321
|
And finally a contrived example illustrating how a data provider that accepts multiple named vector values per set might look:
| No Format |
|---|
aidaset MY:NAMED:VECTORS//VAL /SILLYNAME 0 1 2 3 4 5 /ANOTHERNAME 6 7 8 9 10
|