CM CAN Combo
User Manual
32
4.5.1.6
Delay for Logging
By this function it is possible to define, when the CaptureModule starts sending logged
data after power on or wakeup (from sleep mode and standby mode) on the configured
logging ports.
As
default
is nothing configured. That means, incoming data on the logged ports is
directly passed via the memory to the configured output port.
A logging port is defined by the function
Output To
on the logged ports (please see
C
).
Events for starting logging:
LinkUp detected
: If this box is checked, logged data will be sent on logging port,
when there is the first linkup after wakeup. If there is no linkup, data will not be sent.
Available only as single choice.
Note
: If 95% of the internal memory is full, the captured data in the memory is
passed to output even if there is no linkup detected.
802.1AS Master detected
: If this box is checked, logged data will be sent after a
PTP Master is detected on the logging port. This event can be combined with
Control Message DataLoggerReady detected
.
Note
: If 95% of the internal memory is full, the captured data in the memory is
passed to output even if there is no PTP Master detected.
Control Message DataLoggerReady detected
: If this box is checked, logged data
will be sent as soon as the mentioned control message is detected. This event can
be combined with
802.1AS Master detected
.
Note
: If 95% of the internal memory is full, the captured data in the memory is
passed to output even if there is no control message detected.
Notes
:
If there is a datalogger as 802.1AS Master and the 802.1AS-bridge is not
established before the CaptureModule is logging, the behavior is as follows:
The timestamp in the TECMP-header of internal stored (in CaptureModule) data
will be corrected
only
if the event
802.1AS Master detected
is activated.
Otherwise the CaptureModule will send its logged data with the origin
timestamp with no correction.
If 95% (Limit one) of the internal memory is full, the data in the memory is
passed to the configured output even if the configured delay condition is not
detected! There is a hint in red text on the website of the CaptureModule. And
this information can be found in the status messages