...
Consider a logger with channels set up as follows (note that all numbering of channels is zero-based in these messages).
Analogue channels
aip 0 | 771A WI | 771A Points motor current |
aip 1 | 771A WF | 771A Points force |
aip 2 | 422TI | 422 Track circuit current |
aip 3 | 425TI | 425 Track circuit current |
aip 4 | … | … |
Digital channels
dip 0 | 771 NWKR | 771 Normal detection |
dip 1 | 771 RWKR | 771 Reverse detection |
dip 2 | … | … |
...
- Set capture id 0 with a name of “771A N-R”, enable it, and push data to the central system.
- Start to capture data 500ms before digital channel 0 goes Down.
- Stop capturing data 500ms after digital channel 1 goes Up.
- Capture the data from analogue channels 0 and 1.
Threshold level triggers
The above example is for event triggers. To set a trigger for an analogue threshold level, use the following:
...
The SOAP call is <txc:setCfgAcqChgRequest>. The following SOAP message sets up two acquire-on-change routines, one for each of the track circuits.
Taking the first as an example, this tells the logger to:
- Set acquire-on-change on analogue channel 2, enable it, push data to the central system, acquire whenever the value changes by 2.5% of full scale, package acquired samples if there are no more samples acquired after 2 seconds or if there are 100 acquired samples waiting to be sent.
| Note |
|---|
Note that |
...
: Acquire-on-change works on a percentage of full scale deflection. Hence if the full scale of the input is 600mA, 2.5% of this is 15mA, and so the logger will acquire a sample if the input changes by more than 15mA. |
SetCfgResponse
The response from the logger to both the captures and acquire-on-change messages is as follows:
This is a very simple empty response. Any errors in setting the config are returned as SOAP faults. If there is no SOAP fault, then the command completed OK.
...
Getting configuration from the logger
To get a list of all the captures in the logger, send the following message:
To retrieve a list of all the acquire-on-change settings, send the same message as above but with a SOAP call of <txc:getCfgAcqChgRequest />.