...
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 vectosvectors, one listing magent 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 |
|---|
aidaset MAGNETSET//BDES -DMAGFUNC=TRIM /sun XCOR:LI31:41 /moon 4.0
|
Vector elements my be listed sequentially with whitespace separators as in the following example that sets several magnets simultaneously:
| No Format |
|---|
aidaset MY:VECTORMAGNETSET//VAL 1 2 3 4 5 6 7 8 9 10BDES -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:
...