Logging Inputs
DESCRIPTION
Individual changes in I/O state are accurately logged. The
IOLOG command
can be used to display and save I/O logs. Applications have the ability to
query I/O log detail with sufficient accuracy to calculate information such
as the RPM (Revolutions Per Minute) of a wind turbine both at high speeds
and very low speeds (fractions of RPM). The I/O logs can be used in
preference to monitoring the input state itself.
EXAMPLE
I/O Log content:
06/10/21 13:00:45.487, DIN ---- 0000 0000, RLY ---- ---- 0000 0000
06/11/21 11:10:41.197, DIN ---- 0000 0000, RLY ---- ---- 0000 0001
06/11/21 11:10:41.297, DIN ---- 0000 0000, RLY ---- ---- 0000 0000
06/11/21 13:23:29.008, DIN ---- 0000 0000, RLY ---- ---- 0000 0001
06/11/21 13:23:31.008, DIN ---- 0000 0000, RLY ---- ---- 0000 0000
06/11/21 13:23:34.813, DIN ---- 0000 0000, RLY ---- ---- 0000 0001
06/11/21 13:23:34.913, DIN ---- 0000 0000, RLY ---- ---- 0000 0000
06/11/21 13:28:30.665, DIN ---- 0000 0000, RLY ---- 0001 0000 0000
06/11/21 13:28:39.023, DIN ---- 0000 0000, RLY ---- 0001 0000 0010
06/11/21 13:30:24.665, DIN ---- 0000 0000, RLY ---- 0000 0000 0000
Note that in this example an external Power 4ROUT was added a one point
and one of its relays closed and later opened.
NOTES
High frequency input signals can impact product performance and logging for
individual inputs may be disabled if that is of concern. It may be more that
a frequently changing signal may mask the activity of other inputs given
that the I/O log queue itself is of a fixed size.
SEE ALSO
HELP Topics:
IO/Inputs/Log,
IOLOG,
JRMON
[/flash/manpages/registry.hlp:2629]