Chapter 6
.
COMMREQ/Data_Init_Comm Programming
6.4
COMMREQ Descriptions and Formats
6.4.1
COMMREQ #1: Pulse Test Command
The Pulse Test command causes the Genius Gateway to send a Pulse Test datagram.
Pulse testing is used to verify the operation of outputs on discrete Genius I/O blocks. It checks
whether the outputs will change state, and whether output circuits (wires, power sources,
loads) will start or stop current flow. Any circuit faults generated by pulse tests are reported
through the normal Report Fault message. Pulse testing is recommended for blocks that
seldom change state. It is typically done once per hour, or once per shift; it should not be done
more often than once per minute. Pulse testing provides assurance that when needed, an
output will operate correctly. Blocks that control outputs that change state frequently do not
need to be pulse tested. Pulse testing does not provide enough energy to activate
mechanical devices such as motor starters, replays, or solenoid valves, but may change the
state of a very small load. If appropriate, blocks can be configured (with the Hand-Held
Monitor or via a Write Configuration command) to ignore a Pulse Test datagram. Pulse
testing can also be done using a Hand-Held Monitor.
Command Block for the Pulse Test Command
Address
Command Length
3
A1
No Wait
0
A2
Status Block memory type
70 (%I), 72 (%Q), 8 (%R), 10 (%AI), 12 (%AQ) or 196 (%W)
A3
Status Block offset
Beginning address for the COMMREQ Status Block.
A4
Idle timeout value
0
A5
Max. communications time 0
A6
Command number
1
A7
PROFINET Device number
1-255: The device number of the targeted GCG Genius Gateway.
A8
Genius Device Number
0-31: the SBA of the targeted Genius Device.
GFK-2892B
PACSystems RX3i Genius Communications Gateway User Manual
Public 57
