You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -81,15 +81,15 @@ The services are DIM RPC services. Every RPC is called with a string and expects
81
81
* An SCA command and data pair (e.g. `0x0000f00d,0x0000cafe`)
82
82
* A wait operation (e.g. `30,wait`) in ms, defaults to 3
83
83
* An SCA connect operation (e.g. `connect`)
84
-
* An SCA reset operation (e.g. `reset`)
84
+
* An SCA reset operation (`reset`)
85
+
* An SC global reset operation (`sc_reset`)
85
86
* An instruction to execute the sequence atomically (`lock` - needs to lead the sequence)
86
87
* Returns:
87
88
* Sequence of SCA output as follows:
88
89
* SCA command and SCA read pairs
89
90
* Wait confirmations with time waited
90
91
* Connect confirmations made up of a "connect" string
91
-
* No entries for `reset` directives
92
-
* No entries for `lock` directives
92
+
* No entries for `reset`, `sc_reset`, and `lock` directives
93
93
94
94
* Example:
95
95
* DIM input: `0x00000010,0x00000011\n3\n0x000000020,0x00000021`
@@ -101,21 +101,21 @@ The services are DIM RPC services. Every RPC is called with a string and expects
101
101
* Sequence of SWT word and operation pairs as follows:
102
102
* Operations may be:
103
103
*`write` with SWT prefix (e.g. `0x0000f00d,write`)
104
-
*`reset` (without SWT word)
104
+
*`sc_reset`without prefix, is global
105
105
*`read` with optional TimeOut prefix (e.g. `2,read`)
106
106
*`wait` with optional WaitTime prefix in ms (e.g. `5,wait`), defaults to 3
107
107
*`lock` which instructs ALF to execute the sequence atomically (needs to lead the sequence)
108
108
* Returns:
109
109
* Sequence of SWT output as follows:
110
110
*`write` always retuns `0`
111
111
*`read` returns the SWT words present in the CRU SWT FIFO
112
-
*`reset` returns nothing
112
+
*`sc_reset` returns nothing
113
113
*`wait` returns time waited
114
114
*`lock` returns nothing
115
115
116
116
* Example:
117
-
* DIM input `reset\n0x0000000000badc0ffee,write\nread\n0xbadf00d,write\n4,read`
118
-
* DIM input (atomic) `lock\nreset\n0x0000000000badc0ffee,write\nread\n0xbadf00d,write\n4,read`
117
+
* DIM input `sc_reset\n0x0000000000badc0ffee,write\nread\n0xbadf00d,write\n4,read`
118
+
* DIM input (atomic) `lock\nsc_reset\n0x0000000000badc0ffee,write\nread\n0xbadf00d,write\n4,read`
119
119
* DIM output `0\n0x0000000000badc0ffee\n0\n0x000000000000badf00d\n`
120
120
121
121
##### IC_SEQUENCE
@@ -216,7 +216,7 @@ The services are DIM RPC services. Every RPC is called with a string and expects
216
216
## Slow Control library
217
217
ALF can also be used as a C++ library to access the Slow Control interface of the CRU. The three available interfaces (IC, SCA & SWT) can be accessed through single operations, or sequences of operations.
218
218
219
-
For each Slow Control (SC) class a handle can be acquired by passing the card ID as an `std::string` argument and, optionally, the SC channel to use as an `int`. Constructors have no side-effects; an SC reset would need to be performed manually before starting operations (e.g. `swt.reset()`).
219
+
For each Slow Control (SC) class a handle can be acquired by passing the card ID as an `std::string` argument and, optionally, the SC channel to use as an `int`. Constructors have no side-effects; an SC reset would need to be performed manually before starting operations (e.g. `swt.scReset()`).
220
220
221
221
### Single operations
222
222
Depending on the type, an SC class offers a different interface for single operation execution. `SWT` and `IC` offer `read()` and `write()` standalone operations, while `SCA` only offers `executeCommand()`.
@@ -226,7 +226,7 @@ All the above offer **no implicit locking** and should be manually locked throug
226
226
### Sequences of operations
227
227
All SC classes offer a function to execute a sequence of their respective operations. This function receives an `std::vector`, consisting of an `std::pair` made up of the compatible SC operation and SC data, as these are defined in their headers.
228
228
229
-
For example, `SWT` offers `Read, Write, Wait, and Reset` operations which expect a `TimeOut`, an `SwtWord`, a `WaitTime`, and no argument, respectively.
229
+
For example, `SWT` offers `Read, Write, Wait, and SCReset` operations which expect a `TimeOut`, an `SwtWord`, a `WaitTime`, and no argument, respectively.
0 commit comments