
http://www2.merrick-inc.com/mct/GCMModbus.pdf Page 9 2014-05-18/Lars
Protocol used. 1 or 2 for Modbus. See “Setting the GCM communications
parameters” on page 2.
Transient indication of the last protocol initialized. Normally same as “Prot”
Index of the baud rate used: See “Setting the GCM communications parameters” on
page 2.
Line parameters. See “Setting the GCM communications parameters” on page 2.
Protocol Selector for the UART interrupt service routine. Typically same as Prot
Routing for the XDC board. Always 0 for Modbus.
Prelude State. Not used, always zero.
Port index. 0 for port 1 (UART 0, lower row on connector) 1 for port 2 (UART 1,
upper row on connector)
UART Interrupt counter. Increments for any serial activity. Since the UARTs have 16
byte FIFOs, this counter typically increments slower than Rxchs and Txchs.
Received characters counter
Transmitted characters counter
Receiver UART error counter.
UART Line Status Register at the last UART error. Bit encoded:
Bit 0 Receiver data ready. This is not an error
Bit 1 Overrun error
Bit 2 Parity error
Bit 3 Framing error
Bit 4 Break condition
Bit 5 Transmitter holding register empty. This is not an error
Bit 6 Transmitter empty. This is not an error
Bit 7 At least one error in receiver FIFO
UART Line status register at the last character received. See Rxlua above. Typically
0x61.
Hex representation of the last character received
Counter for illegal Modem Status Interrupt. The UART is configured to not generate
MSRs. Only UART1 has modem status lines. Should always be 0.
Counter for illegal (not enabled) UART error interrupts. Should always be 0.
Transmitter buffer overrun counter. Increments if an attempt is made to transmit
characters past the end of the transmitter character buffer, indicating a bug in the
protocol handler. Should always be 0.
Receiver buffer overrun counter. Increments when the receiver buffer is filled up
without an end of telegram condition.
UART Interrupt Identification Register at last interrupt.
Indicates that the last UART receiver interrupt was a UART character timeout (Stale
data in FIFO) rather than a “FIFO trigger limit reached”.
Counter for undocumented IIR patterns. There appears to be a bug in the UART
that, under adverse conditions, causes this to happen.
Controller/Station/Node number ID of the GCM in multidrop settings. Must be
different for each connected GCM on the Modbus segment.
Enumeration of the CIT map format. Set to 1 for standard CIT mapping.
Silence time for isTimeout (see below) in seconds. A value of zero is interpreted as
“never” meaning isTimeout will never be true.
Comentarios a estos manuales