Reading The Event Recorder; Reading The Counters Related To Event Memory - Netronix CTU-M Series Technical Data Sheet

NETRONIX
E.g. In4Trig-In1Trig configuration byte sequence: 0x00,0x31,0x40,0x08, causes, that
events will be written in case of:
Any state change of input with index 10 occurs
−
Positive slope appears on input with index 8
−
Positive slope appears on input with index 7
−
Negative slope appears on input with index 1
−
During configuring the event triggers, decide which port is configured as an input. Do
not configure events for those I/O's, which are outputs.
To guarantee correctness of event write process, time between two subsequent
triggers must be longer than 20 ms.

Reading the event recorder

5.12.2.
Command frame:
Header C_GetEventTrig
Wherein:
Parameter name
C_GetEventTrig
0x7E
Response frame:
Header C_GetEventTrig+1 CardTrig, In1Trig

Reading the counters related to event memory.

5.12.3.
Command frame:
Header C_GetEventParam
Wherein:
Parameter name
C_GetEventParam
0x78
Response frame:
C_GetEvent
Header
Param+1
CapH:CapL – two-byte value, which defines event memory capacity.
PointerH:PointerL – two-byte value, which marks from first free event.
TotB3:TotB2:TotB1:TotB0 – four-byte value, which defines number of events recorded
from the moment of counter reset.
Events are recorded in sequence from index 0 up to Cap-1. In the moment memory
gets full, the counter is being "overturned", and older inputs are overwritten.
NETRONIX
Parameter description
Reading the configuration of event recorder
Parameter description
Reading the configuration of event recorder
CapL, CapH, PointerL,
PointerH,TotB3,TotB2,TotB1,TotB0
CTU-Mxx
CRC
Value range
0x7E
OperationCode CRC
CRC
Value range
0x78
OperationCode CRC
.
33