This instruction manual provides information about the installation and operation of the DGC-2020HD
Digital Genset Controllers with the Modbus™ protocol. To accomplish this, the following information is
provided:
•General information
•Register table
Conventions Used in this Manual
Important safety and procedural information is emphasized and presented in this manual through
warning, caution, and note boxes. Each type is illustrated and defined as follows.
Warning!
Warning boxes call attention to conditions or actions that may cause
personal injury or death.
Caution
Caution boxes call attention to operating conditions that may lead to
equipment or property damage.
Note
Note boxes emphasize important information pertaining to installation
or operation.
DGC-2020HD Modbus™ Protocol Preface
ii 9469300991 Rev A
This publication contains confidential information of Basler Electric Company, an Illinois corporation. It is loaned for
READ THIS MANUAL. Read this manual before installing, operating, or maintaining the DGC-2020HD
Note all warnings, cautions, and notes in this manual as well as on the product. Keep this manual with
the product for reference. Only qualified personnel should install, operate, or service this system.
Failure to follow warning and cautionary labels may result in personal injury or property damage.
Exercise caution at all times.
Basler Electric does not assume any responsibility to compliance or noncompliance with national code, local code,
or any other applicable code. This manual serves as reference material that must be well understood prior to
installation, operation, or maintenance.
For terms of service relating to this product and software, see the Commercial Terms of Products and Services
document available at www.basler.com/terms.
confidential use, subject to return on request, and with the mutual understanding that it will not be used in any
manner detrimental to the interests of Basler Electric Company and used strictly for the purpose intended.
It is not the intention of this manual to cover all details and variations in equipment, nor does this manual provide
data for every possible contingency regarding installation or operation. The availability and design of all features
and options are subject to modification without notice. Over time, improvements and revisions may be made to this
publication. Before performing any of the following procedures, contact Basler Electric for the latest revision of this
manual.
The English-language version of this manual serves as the only approved manual version.
Preface DGC-2020HD Modbus™ Protocol
9469300991 Rev A iii
Contents
General Information .................................................................................................................................... 1
Device Address Field ................................................................................................................................. 1
Function Code Field .................................................................................................................................. 1
Data Block Field ........................................................................................................................................ 2
Error Check Field ....................................................................................................................................... 2
Modbus Modes of Operation ..................................................................................................................... 2
Modbus Over Serial Line ........................................................................................................................... 2
Modbus on TCP/IP .................................................................................................................................... 3
Error Handling and Exception Responses ................................................................................................ 4
DGC-2020HD Modbus via Ethernet .......................................................................................................... 5
Detailed Message Query and Response for RTU Transmission Mode .................................................... 5
Return Query Data .................................................................................................................................... 5
Listen Only Mode ....................................................................................................................................... 6
Preset Single Register ............................................................................................................................... 7
Data Formats ............................................................................................................................................. 8
Floating Point Data Format (Float) ............................................................................................................ 8
Long Integer Data Format (Uint32, Int32, and IP Address) ....................................................................... 9
Integer Data Format (Uint16) or Bit-Mapped Variables in Uint16 Format ................................................. 9
Short Integer Data Format/Byte Character Data Format (Uint8)............................................................... 9
String Data Format (String) ....................................................................................................................... 9
General .................................................................................................................................................... 11
Bias Control ............................................................................................................................................. 50
Bus Condition .......................................................................................................................................... 56
Control Settings ....................................................................................................................................... 62
Global Settings ........................................................................................................................................ 63
Bias Control Settings ............................................................................................................................. 230
System Configuration and Status .......................................................................................................... 235
Control ................................................................................................................................................... 238
Communication ...................................................................................................................................... 239
Revision History ...................................................................................................................................... 309
DGC-2020HD Modbus™ Protocol Contents
iv 9469300991 Rev A
Contents DGC-2020HD Modbus™ Protocol
9469300991 Rev A 1
General Information
This document describes the Modbus communications protocol employed by DGC-2020HD systems and
how to exchange information with DGC-2020HD systems over a Modbus network. DGC-2020HD systems
communicate by emulating a subset of the Modicon 984 Programmable Controller.
Modbus communications use a master-slave technique in which only the master can initiate a transaction.
This transaction is called a query. When appropriate, a slave (DGC-2020HD) responds to the query.
When a Modbus master communicates with a slave, information is provided or requested by the master.
Information residing in the DGC-2020HD is grouped categorically as follows:
• General
• Global Settings
• Configuration
• Binary Points
• Metering
• Breaker Settings
• Bias Control
• Pulse Outputs
• Bus Condition
• DGC Settings
• Control Settings
• Protection Settings
• Remote Module Settings
All supported data can be read as specified in the Register Table. Abbreviations are used in the Register
Table to indicate the register type. Register types are:
• Read/Write = RW
• Read Only = R
When a slave receives a query, the slave responds by either supplying the requested data to the master
or performing the requested action. A slave device never initiates communications on the Modbus and will
always generate a response to the query unless certain error conditions occur. The DGC-2020HD is
designed to communicate on the Modbus network only as a slave device.
Refer to the Instruction Manual for Digital Genset Controller DGC-2020HD (Basler Publication
9469300990) for Modbus communication setup and wiring.
Message Structure
Device Address Field
The device address field contains the unique Modbus address of the slave being queried. The addressed
slave repeats the address in the device address field of the response message. This field is 1 byte.
Although Modbus protocol limits a device address from 1 - 247. The address is user-selectable at
installation and can be altered during real-time operation.
Function Code Field
The function code field in the query message defines the action to be taken by the addressed slave. This
field is echoed in the response message and is altered by setting the most significant bit (MSB) of the
field to 1 if the response is an error response. This field is 1 byte in length.
The DGC-2020HD maps all available data into the Modicon 984 holding register address space supports
the following function codes:
• Function 03 (03 hex) - read holding registers
• Function 06 (06 hex) - preset single register
• Function 08 (08 hex), subfunction 00 - diagnostics: return query data
• Function 08 (08 hex), subfunction 04 - diagnostics: force listen only mode
• Function 16 (10 hex) - preset multiple registers
Data Block Field
The query data block contains additional information needed by the slave to perform the requested
function. The response data block contains data collected by the slave for the queried function. An error
response will substitute an exception response code for the data block. The length of this field varies with
each query.
Error Check Field
The error check field provides a method for the slave to validate the integrity of the query message
contents and allows the master to confirm the validity of response message contents. This field is 2 bytes.
Modbus Modes of Operation
A standard Modbus network offers the remote terminal unit (RTU) transmission mode and Modbus/TCP
mode for communication. DGC-2020HD systems support the Modbus/TCP mode and RS-485 mode at
the same time. To enable editing over Modbus TCP, or RS-485, the unsecured access level for the port
must be configured to the appropriate access level. See the Instruction Manual for Digital Genset Controller DGC-2020HD (Basler Publication 9469300990) for more information on security and access
levels. These two modes of operation are described below.
A master can query slaves individually or universally. A universal ("broadcast") query, when allowed,
evokes no response from any slave device. If a query to an individual slave device requests actions
unable to be performed by the slave, the slave response message contains an exception response code
defining the error detected. Exception response codes are quite often enhanced by the information found
in the "Error Details" block of holding registers.
The Modbus protocol defines a simple Protocol Data Unit (PDU) independent of the underlying
communication layers. The mapping of the Modbus protocol on specific buses or networks can introduce
some additional fields on the Application Data Unit (ADU). See Figure 1.
ADU
Figure 1. General Modbus Frame
The client that initiates a Modbus transaction builds the Modbus Application Data Unit. The function code
indicates to the server which kind of action to perform.
Modbus Over Serial Line
Message Structure
Master initiated queries and DGC-2020HD responses share the same message structure. Each message
is comprised of four message fields. They are:
• Device Address (1 byte)
• Function Code (1 byte)
• Data Block (n bytes)
• Error Check field (2 bytes)
Each 8-bit byte in a message contains two 4-bit hexadecimal characters. The message is transmitted in a
continuous stream with the LSB of each byte of data transmitted first. Transmission of each 8-bit data
byte occurs with one start bit and either one or two stop bits. Parity checking is performed, when enabled,
General Information DGC-2020HD Modbus™ Protocol
9469300991 Rev A 3
PDU
Function code
Data
MBAP Header
and can be either odd or even. The transmission baud rate is user-selectable, and can be set at
installation and altered during real-time operation. DGC-2020HD Modbus supports baud rates up to
115200. The factory default baud rate is 19200.
DGC-2020HD systems support RS-485 compatible serial interfaces. This interface is accessible from the
left side panel of the DGC-2020HD.
Message Framing and Timing Considerations
When receiving a message via the RS-485 communication port, the DGC-2020HD requires an inter-byte
latency of 3.5 character times before considering the message complete.
Once a valid query is received, the DGC-2020HD waits a specified amount of time before responding.
This time delay is set on the Modbus Setup screen under Communications in BESTCOMSPlus
®
. This
parameter contains a value from 10 - 10,000 milliseconds. The default value is 10 milliseconds.
Table 1 provides the response message transmission time (in seconds) and 3.5 character times (in
milliseconds) for various message lengths and baud rates.
Table 1. Timing Considerations
Baud Rate
3.5 Character Time
(ms)
Message Tx Time(s)
128 Bytes 256 Bytes
2400 16.04 0.59 1.17
4800 8.021 0.29 0.59
9600 4.0104 0.15 0.29
19200 2.0052 0.07 0.15
Modbus on TCP/IP
Application Data Unit
The following describes the encapsulation of a Modbus request or response when it is carried on a
Modbus TCP/IP network. See Figure 2.
Modbus TCP/IP ADU
Figure 2. Modbus Request/Response Over TCP/IP
A dedicated header is used on TCP/IP to identify the Modbus Application Data Unit. It is called the MBAP
header (Modbus Application Protocol header).
This header provides some differences compared to the Modbus RTU application data unit used on a
serial line:
• The Modbus ‘slave address’ field usually used on Modbus Serial Line is replaced by a single byte
‘Unit Identifier’ within the MBAP header. The ‘Unit Identifier’ is used to communicate via devices
such as bridges, routers, and gateways that use a single IP address to support multiple
independent Modbus end units.
• All Modbus requests and responses are designed in such a way that the recipient can verify that
a message is finished. For function codes where the Modbus PDU has a fixed length, the function
code alone is sufficient. For function codes carrying a variable amount of data in the request or
response, the data field includes a byte count.
• When Modbus is carried over TCP, additional length information is carried in the MBAP header to
allow the recipient to recognize message boundaries even if the message has been split into
multiple packets for transmission. The existence of explicit and implicit length rules and use of a
DGC-2020HD Modbus™ Protocol General Information
4 9469300991 Rev A
CRC-32 error check code (on Ethernet) results in an infinitesimal chance of undetected corruption
to a request or response message.
MBAP Header Description
The MBAP Header contains the fields listed in Table 2.
Table 2. MBAP Header Fields
Fields Length Description Client Server
Transaction
Identifier
Protocol
Identifier
Length 2 Bytes Number of following bytes. Initialized by
Unit Identifier 1 Byte Identification of a remote
The header is 7 bytes long:
2 Bytes Identification of a Modbus
request/response
transaction.
2 Bytes 0 = Modbus protocol. Initialized by
slave connected on a serial
line or on other buses.
Initialized by
the client.
the client.
the client
(request).
Initialized by
the client.
Recopied by the
server from the
received request.
Recopied by the
server from the
received request.
Initialized by the
server (response).
Recopied by the
server from the
received request.
• Transaction Identifier – Used for transaction pairing, the Modbus server copies in the response
the transaction identifier of the request.
• Protocol Identifier – Used for intra-system multiplexing. The Modbus protocol is identified by the
value 0.
• Length – A byte count of the following fields, including the Unit Identifier and data fields.
• Unit Identifier – Used for intra-system routing purpose. It is typically used to communicate to a
Modbus or a Modbus serial line slave through a gateway between an Ethernet TCP/IP network
and a Modbus serial line. This field is set by the Modbus Client in the request and must be
returned with the same value in the response by the server.
Note: All Modbus/TCP ADU are sent via TCP on registered port 502.
Error Handling and Exception Responses
Any query received that contains a non-existent device address, a framing error, or CRC error is ignored.
No response is transmitted. Queries addressed to the DGC-2020HD with an unsupported function or
illegal values in the data block result in an error response message with an exception response code. The
exception response codes supported by the DGC-2020HD are provided in Table 3.
Table 3. Supported Exception Response Codes
Code Name Description
01 Illegal Function The query Function/Subfunction Code is unsupported;
query read of more than 125 registers; query preset of
more than 100 registers.
02 Illegal Data
Address
03 Illegal Data Value A preset register data block contains an incorrect number
A register referenced in the data block does not support
queried read/write; query preset of a subset of a numerical
register group.
of bytes or one or more data values out of range.
General Information DGC-2020HD Modbus™ Protocol
9469300991 Rev A 5
DGC-2020HD Modbus via Ethernet
Modbus can communicate through Ethernet if the IP address of the DGC-2020HD is configured as
described in the Instruction Manual for Digital Genset Controller DGC-2020HD (Basler Publication
9469300990).
Detailed Message Query and Response for RTU Transmission Mode
A detailed description of DGC-2020HD supported message queries and responses is provided in the
following paragraphs.
Read Holding Registers
Query
This query message requests a register or block of registers to be read. The data block contains the starting
register address and the quantity of registers to be read. A register address of N will read holding register
N+1. If the query is a broadcast (device address = 0), no response message is returned.
Device Address
Function Code = 03 (hex)
Starting Address Hi
Starting Address Lo
No. of Registers Hi
No. of Registers Lo
CRC Hi error check
CRC Lo error check
The number of registers cannot exceed 125 without causing an error response with the exception code
for an illegal function.
Response
The response message contains the data queried. The data block contains the block length in bytes
followed by the data (one Data Hi byte and one Data Lo byte) for each requested register.
Reading an unassigned holding register returns a value of zero.
Device Address
Function Code = 03 (hex)
Byte Count
Data Hi (For each requested register, there is one Data Hi and one Data Lo.)
Data Lo
.
.
Data Hi
Data Lo
CRC Hi error check
CRC Lo error check
Return Query Data
This query contains data to be returned (looped back) in the response. The response and query
messages should be identical. If the query is a broadcast (device address = 0), no response message is
returned.
Device Address
Function Code = 08 (hex)
Subfunction Hi = 00 (hex)
Subfunction Lo = 00 (hex)
Data Hi = xx (don't care)
Data Lo = xx (don't care)
DGC-2020HD Modbus™ Protocol General Information
6 9469300991 Rev A
CRC Hi error check
CRC Lo error check
Restart Communications Option
This query causes the remote communications function of the DGC-2020HD to restart, terminating an
active listen only mode of operation. No effect is made upon primary relay operations. Only the remote
communications function is affected. If the query is a broadcast (device address = 0), no response
message is returned.
If the DGC-2020HD receives this query while in the listen only mode, no response message is generated.
Otherwise, a response message identical to the query message is transmitted prior to the
communications restart.
Device Address
Function Code = 08 (hex)
Subfunction Hi = 00 (hex)
Subfunction Lo = 01 (hex)
Data Hi = xx (don't care)
Data Lo = xx (don't care)
CRC Hi error check
CRC Lo error check
Listen Only Mode
This query forces the addressed DGC-2020HD to the listen only mode for Modbus communications,
isolating it from other devices on the network. No responses are returned.
While in the listen only mode, the DGC-2020HD continues to monitor all queries. The DGC-2020HD does
not respond to any other query until the listen only mode is removed. All write requests with a query to
Preset Multiple Registers (Function Code = 16) are also ignored. When the DGC-2020HD receives the
restart communications query, the listen only mode is removed.
Device Address
Function Code = 08 (hex)
Subfunction Hi = 00 (hex)
Subfunction Lo = 04 (hex)
Data Hi = xx (don't care)
Data Lo = xx (don't care)
CRC Hi error check
CRC Lo error check
Preset Multiple Registers
A preset multiple registers query could address multiple registers in one slave or multiple slaves. If the
query is a broadcast (device address = 0), no response message is returned.
Query
A Preset Multiple Register query message requests a register or block of registers to be written. The data
block contains the starting address and the quantity of registers to be written, followed by the Data Block
byte count and data. The DGC-2020HD will perform the write when the device address in query is a
broadcast address or the same as the DGC-2020HD Modbus Unit ID (device address).
A register address of N will write Holding Register N+1.
Data will cease to be written if any of the following exceptions occur.
• Queries to write to Read Only registers result in an error response with Exception Code of “Illegal
Data Address”.
• Queries attempting to write more than 100 registers cause an error response with Exception
Code “Illegal Function”.
General Information DGC-2020HD Modbus™ Protocol
9469300991 Rev A 7
• An incorrect Byte Count will result in an error response with Exception Code of “Illegal Data
Value”.
• There are several instances of registers that are grouped together to collectively represent a
single numerical DGC-2020HD data value (i.e. - floating point data, 32-bit integer data, and
strings). A query to write a subset of such a register group will result in an error response with
Exception Code “Illegal Data Address”.
• A query to write a not allowed value (out of range) to a register results in an error response with
Exception Code of “Illegal Data Value”.
Device Address
Function Code = 10 (hex)
Starting Address Hi
Starting Address Lo
No. of Registers Hi
No. of Registers Lo
Byte Count
Data Hi
Data Lo
.
.
Data Hi
Data Lo
CRC Hi error check
CRC Lo error check
Response
The response message echoes the starting address and the number of registers. There is no response
message when the query is a broadcast (device address = 0).
Device Address
Function Code = 10 (hex)
Starting Address Hi
Starting Address Lo
No. of Registers Hi
No. of Registers Lo
CRC Hi Error Check
CRC Lo Error Check
Preset Single Register
A Preset Single Register query message requests a single register to be written. If the query is a
broadcast (device address = 0), no response message is returned.
Note: Only data types INT16, INT8, UINT16, UINT8, and String (not longer than 2 bytes), can be preset
by this function.
Query
Data will cease to be written if any of the following exceptions occur.
• Queries to write to Read Only registers result in an error response with Exception Code of “Illegal
Data Address”.
• A query to write an unallowed value (out of range) to a register results in an error response with
Exception Code of “Illegal Data Value”.
Device Address
Function Code = 06 (hex)
Address Hi
Address Lo
Data Hi
Data Lo
DGC-2020HD Modbus™ Protocol General Information
8 9469300991 Rev A
CRC Hi error check
CRC Lo error check
Response
The response message echoes the Query message after the register has been altered.
Data Formats
DGC-2020HD systems support the following data types:
• Data types mapped to 2 registers
o Signed Integer 32 (Int32)
o Unsigned Integer 32 (Uint32)
o Floating Point (Float)
o IP Address (IP Address)
o Strings maximum 4 characters long (String)
• Data types mapped to 1 register
o Unsigned Integer 16 (Uint16)
o Unsigned Integer 8 (Uint8)
o Strings maximum 2 characters long (String)
• Data types mapped to more than 2 registers
o Strings longer than 4 characters (String)
Floating Point Data Format (Float)
The Modbus floating point data format uses two consecutive holding registers to represent a data value.
The first register contains the low-order 16 bits of the following 32-bit format:
• MSB is the sign bit for the floating-point value (0 = positive).
• The next 8 bits are the exponent biased by 127 decimal.
• The 23 LSBs comprise the normalized mantissa. The most-significant bit of the mantissa is
always assumed to be 1 and is not explicitly stored, yielding an effective precision of 24 bits.
The value of the floating-point number is obtained by multiplying the binary mantissa times two raised to
the power of the unbiased exponent. The assumed bit of the binary mantissa has the value of 1.0, with
the remaining 23 bits providing a fractional value. Table 4 shows the floating-point format.
Table 4. Floating Point Format
Sign Exponent + 127 Mantissa
1 Bit 8 Bits 23 Bits
The floating-point format allows for values ranging from approximately 8.43X10^
floating-point value of all zeroes is the value zero. A floating-point value of all ones (not a number)
signifies a value currently not applicable or disabled.
Example
will read from two consecutive holding registers as follows:
Holding Register Value
K (Hi Byte) hex 1C
K (Lo Byte) hex 00
K+1 (Hi Byte) hex 47
K+1 (Lo Byte) hex BB
: The value 95,800 represented in floating-point format is hexadecimal 47BB1C00. This number
-37
to 3.38X10^38. A
The same byte alignments are required to write.
General Information DGC-2020HD Modbus™ Protocol
9469300991 Rev A 9
Long Integer Data Format (Uint32, Int32, and IP Address)
The Modbus long integer data format uses two consecutive holding registers to represent a 32-bit data
value. The first register contains the low-order 16 bits and the second register contains the high-order 16
bits.
Example
will read from two consecutive holding registers as follows:
Holding Register Value
K (Hi Byte) hex 76
K (Lo Byte) hex 38
K+1 (Hi Byte) hex 00
K+1 (Lo Byte) hex 01
The same byte alignments are required to write.
: The value 95,800 represented in long integer format is hexadecimal 0x00017638. This number
Integer Data Format (Uint16) or Bit-Mapped Variables in Uint16 Format
The Modbus integer data format uses a single holding register to represent a 16-bit data value.
Example
a holding register as follows:
Holding Register Value
K (Hi Byte) hex 12
K (Lo Byte) hex 34
The same byte alignments are required to write.
The Uint16 Data Format is listed in Binary Points below.
Example:
specific bit-mapped data such as 1100-0 indicates bit 0 of register 1100 is mapped to RF-TRIG.
: The value 4660 represented in integer format is hexadecimal 0x1234. This number will read from
Register 1100 occupies 16 rows in the Register Table where each row gives the name of
Short Integer Data Format/Byte Character Data Format (Uint8)
The Modbus short integer data format uses a single holding register to represent an 8-bit data value. The
holding register high byte will always be zero.
Example
from a holding register as follows:
Holding Register Value
K (Hi Byte) hex 00
K (Lo Byte) hex 84
The same byte alignments are required to write.
: The value 132 represented in short integer format is hexadecimal 0x84. This number will read
String Data Format (String)
The Modbus string data format uses one or more holding registers to represent a sequence, or string, of
character values. If the string contains a single character, the holding register high byte will contain the
ASCII character code and the low byte will be zero.
Example
Holding Register Value
K (Hi Byte) ‘P’
K (Lo Byte) ‘A’
K+1 (Hi Byte) ‘S’
K+1 (Lo Byte) ‘S’
K+2 (Hi Byte) ‘W’
K+2 (Lo Byte) ‘O’
: The string “PASSWORD” represented in string format will read as follows:
DGC-2020HD Modbus™ Protocol General Information
10 9469300991 Rev A
K+3 (Hi Byte) ‘R’
K+3 (Lo Byte) ‘D’
Example
Holding Register Value
K (Hi Byte) ‘P’
K (Lo Byte) hex 00
K+1 (Hi Byte) hex 00
K+1 (Lo Byte) hex 00
K+2 (Hi Byte) hex 00
K+2 (Lo Byte) hex 00
K+3 (Hi Byte) hex 00
K+3 (Lo Byte) hex 00
The same byte alignments are required to write.
: If the above string is changed to “P”, the new string will read as follows:
CRC Error Check
This field contains a two-byte CRC value for transmission error detection. The master first calculates the
CRC and appends it to the query message. The DGC-2020HD system recalculates the CRC value for the
received query and performs a comparison to the query CRC value to determine if a transmission error
has occurred. If so, no response message is generated. If no transmission error has occurred, the slave
calculates a new CRC value for the response message and appends it to the message for transmission.
The CRC calculation is performed using all bytes of the device address, function code, and data block
fields. A 16-bit CRC-register is initialized to all 1's. Then each eight-bit byte of the message is used in the
following algorithm:
First, exclusive-OR the message byte with the low-order byte of the CRC-register. The result, stored in
the CRC-register, will then be right-shifted eight times. The CRC-register MSB is zero-filled with each
shift. After each shift, the CRC-register LSB is examined. If the LSB IS a 1, the CRC-register is then
exclusive-ORed with the fixed polynomial value A001 (hex) prior to the next shift. Once all bytes of the
message have undergone the above algorithm, the CRC-register will contain the message CRC value to
be placed in the error check field.
General Information DGC-2020HD Modbus™ Protocol
9469300991 Rev A 11
Time
Date
GG
0136
String
16 R n/a
0 - 16
Default Register Table
The register table on the following pages contains the following groups:
General, Binary Points, Bias Control, Breaker Settings, Bus Condition, DGC Settings, Pulse Outputs,
Control Settings, Global Settings, Configuration, Remote Module Settings, Metering, and Protection
Settings.
General
NameDescriptionGroupRegisterTypeBytesR/WUnitRange
Reserved 0001-34
Land Line Modem Modem Answer Rings GG 0035 Uint8 1 R W n/a 1 - 9
Land Line Modem Modem Offline Delay GG 0036 Uint16 2 R W Minute 1 - 240
Land Line Modem Inter Dialout Activation Delay GG 0037 Uint8 1 R W n/a 15 SEC=15
Land Line Modem Pager Buffer Limit GG 0038 Uint8 1 R W n/a 80 CHARS=80
Land Line Modem Pager Comms Data Format GG 0039 Uint8 1 R W n/a 8 Bit No Parity=0
System Data Model Number GG 0040 String 64 R n/a 0 - 64
System Data Firmware Part Number GG 0072 String 64 R n/a 0 - 64
System Data
System Data
External Version GG 0104 String 32 R n/a 0 - 32
External Boot Version GG 0120 String 32 R n/a 0 - 32
30 SEC=30
60 SEC=60
120 SEC=120
120 CHARS=120
160 CHARS=160
200 CHARS=200
7 Bit Even Parity=1
Time Time GG 0144 String 16 R n/a 0 - 16
Time Year GG 0152 Uint32 4 R W n/a 2000 - 2099
Time Month GG 0154 Uint32 4 R W n/a 1 - 12
Time Day GG 0156 Uint32 4 R W n/a 1 - 31
Time Hour GG 0158 Uint32 4 R W n/a 0 - 23
Time Minute GG 0160 Uint32 4 R W n/a 0 - 59
Time Second GG 0162 Uint32 4 R W n/a 0 - 59
Time Millisecond GG 0164 Uint32 4 R W n/a 0 - 999
Time Time Zone Hour Offset GG 0166 Int32 4 R W n/a -24 - 24
Time Time Zone Minute Offset GG 0168 Int32 4 R W n/a -59 - 59
Time DST Config GG 0170 Uint32 4 R W n/a Disabled=0
Time DST UTC Respective GG 0172 Uint32 4 R W n/a No=0
Time DST Start Month GG 0174 Uint32 4 R W n/a January=0
Time DST Start Day GG 0176 Uint32 4 R W n/a 1 - 31
Time DST Start Week Of Month GG 0178 Uint32 4 R W n/a First=0
Time DST Start Day Of Week GG 0180 Uint32 4 R W n/a Sunday=0
Time DST Start Hour GG 0182 Uint32 4 R W n/a 0 - 23
Time DST Start Minute GG 0184 Uint32 4 R W n/a 0 - 59
NameDescriptionGroupRegisterTypeBytesR/WUnitRange
Time DST End Month GG 0186 Uint32 4 R W n/a January=0
Time DST End Day GG 0188 Uint32 4 R W n/a 1 - 31
Time DST End Week Of Month GG 0190 Uint32 4 R W n/a First=0
Time DST End Day Of Week GG 0192 Uint32 4 R W n/a Sunday=0
Time DST End Hour GG 0194 Uint32 4 R W n/a 0 - 23
Time DST End Minute GG 0196 Uint32 4 R W n/a 0 - 59
Time DST Bias Hours GG 0198 Int32 4 R W n/a -23 - 23
Time DST Bias Minutes GG 0200 Int32 4 R W n/a -59 - 59
Time Twelve-Hour Mode GG 0202 Uint32 4 R W n/a 12 Hour Mode=0
Time Date Format GG 0204 Uint32 4 R W n/a YYYY-MM-DD=0
Unit Information Style Number GG 0206 String 32 R W n/a 0 - 32
Unit Information Serial Number GG 0222 String 32 R W n/a 0 - 32
Load Detection EPS Threshold GG 0238 Uint32 4 R W Percent 3 - 10
Load Detection Low-Line Scale GG 0240 Float 4 R W n/a 0.001 - 3
Load Share Settings System Type GG 0242 Uint32 4 R W n/a Single Generator=0
Load Share Settings Enable Comms Fail Pre Alarm GG 0244 Uint32 4 R W n/a Disabled=0
Auto Restart Auto Restart Enable GG 0246 Uint32 4 R W n/a No=0
Auto Restart Auto Restart Timeout S ec GG 0248 Uint32 4 R W Second 30 - 1800
Auto Restart Auto Restart Attempts GG 0250 Uint32 4 R W n/a 1 - 10
ECU Config CANBus Enabled By User GG 0252 Uint32 4 R W n/a Disabled=0
ECU Config DTC Enable GG 0254 Uint32 4 R W n/a Disabled=0
ECU Config J1939 Source Address GG 0256 Uint32 4 R W n/a 1 - 253
ECU Config ECU Control Output GG 0258 Uint32 4 R W n/a FL CNTCT=0
ECU Config Pulsing Enable GG 0260 Uint32 4 R W n/a Disabled=0
ECU Config ECU Settling Time GG 0262 Uint32 4 R W Millisecond 5500 - 30000
ECU Config ECU Pulse Cycle Time GG 0264 Uint32 4 R W Minute 1 - 60
ECU Config ECU Disconnect Time GG 0266 Uint32 4 R W Second 1 - 60
ECU Config ECU Connect Time GG 0268 Uint32 4 R W Second 1 - 60
ECU Config CAN Bus Eng Ctrl Param Transmit Enable GG 0270 Uint32 4 R W n/a Disabled=0
ECU Config Requested MTU SMC Eng Operating
Mode
ECU Config SPN Conversion Method GG 0274 Uint32 4 R W n/a 1 - 4
ECU Config Voltage Regulator CANbus type GG 0276 Uint32 4 R W n/a None=0
ECU Config Voltage Regulator Primary Voltage
Setpoint
ECU Config Voltage Regulator Alternate Voltage
Setpoint
ECU Config Voltage Regulator Voltage Adjust
Bandwidth
ECU Config Voltage Regulator Field Current GG 0284 Uint32 4 R W Milliamp 0 - 3000000
ECU Config Voltage Regulator Primary
CEM 4 Contact Input 9 Contact Recognition GG 0744 Uint32 4 R W n/a Always=0
CEM 4 Contact Input 9 Alarm Configuration GG 0746 Uint32 4 R W n/a Status Only=0
CEM 4 Contact Input 9 Activation Delay GG 0748 Uint32 4 R W Second 0 - 300
CEM 4 Contact Input
10
CEM 4 Contact Input
10
CEM 4 Contact Input
10
Auto Config Detect Enable GG 0756 Uint32 4 R W n/a Disabled=0
Auto Config Detect Single-Phase Detection Threshold GG 0758 Float 4 R W Volt 0 - 480
Auto Config Detect Single-Phase Detection Gen Connection GG 0760 Uint32 4 R W n/a AB=0
Auto Config Detect Low-Line Detection Threshold GG 0762 Float 4 R W Volt 0 - 480
Contact Recognition GG 0750 Uint32 4 R W n/a Always=0
Alarm Configuration GG 0752 Uint32 4 R W n/a Status Only=0
Activation Delay GG 0754 Uint32 4 R W Second 0 - 300
Engine Running=1
Pre-Alarm=1
Alarm=2
Engine Running=1
Pre-Alarm=1
Alarm=2
Enabled=1
AC=1
Binary Points
Scale Factor Override Alternate Frequency Override 1000 0 Uint16 2 R False=0 True=1
Reserved 1000 1
System Data Logic 0 1000 2 Uint16 2 R False=0 True=1
System Data Logic 1 1000 3 Uint16 2 R False=0 True=1
Alarms Real-Time Clock Alarm 1000 4 Uint16 2 R False=0 True=1
Alarms Date/Time Set Alarm 1000 5 Uint16 2 R False=0 True=1
Alarms Firmware Change Alarm 1000 6 Uint16 2 R False=0 True=1
Alarms Frequency Out-of-Range Alarm 1000 7 Uint16 2 R False=0 True=1
Alarms Ethernet Link 1 Lost Alarm 1000 8 Uint16 2 R False=0 True=1
Alarms Ethernet Link 2 Lost Alarm 1000 9 Uint16 2 R False=0 True=1
Alarms USB COM Alarm 1000 10 Uint16 2 R False=0 True=1
Alarms IRIG Sync Lost Alarm 1000 11 Uint16 2 R False=0 True=1
Alarms Logic = None Alarm 1000 12 Uint16 2 R False=0 True=1
Alarms No User Setting Alarm 1000 13 Uint16 2 R False=0 True=1
Alarms uP Reset Alarm 1000 15 Uint16 2 R False=0 True=1
Alarms Programmable Alarm 1 1001 0 Uint16 2 R False=0 True=1
Alarms Programmable Alarm 2 1001 1 Uint16 2 R False=0 True=1
Alarms Programmable Alarm 3 1001 2 Uint16 2 R False=0 True=1
Alarms Programmable Alarm 4 1001 3 Uint16 2 R False=0 True=1
Alarms Programmable Alarm 5 1001 4 Uint16 2 R False=0 True=1
Alarms Programmable Alarm 6 1001 5 Uint16 2 R False=0 True=1
Alarms Programmable Alarm 7 1001 6 Uint16 2 R False=0 True=1
Alarms Programmable Alarm 8 1001 7 Uint16 2 R False=0 True=1
Alarms Programmable Alarm 9 1001 8 Uint16 2 R False=0 True=1
Alarms Programmable Alarm 10 1001 9 Uint16 2 R False=0 True=1
Alarms Programmable Alarm 11 1001 10 Uint16 2 R False=0 True=1
Alarms Programmable Alarm 12 1001 11 Uint16 2 R False=0 True=1
Alarms Programmable Alarm 13 1001 12 Uint16 2 R False=0 True=1
Alarms Programmable Alarm 14 1001 13 Uint16 2 R False=0 True=1
Alarms Programmable Alarm 15 1001 14 Uint16 2 R False=0 True=1
Alarms Programmable Alarm 16 1001 15 Uint16 2 R False=0 True=1
Alarms Unsupported Number of AEMs 1002 0 Uint16 2 R False=0 True=1
NameDescriptionRegisterBit TypeBytesR/WRange
Alarms Logic Alarm 1002 2 Uint16 2 R False=0 True=1
Alarms Logic Pre-Alarm 1002 3 Uint16 2 R False=0 True=1
Alarms Global Sender Fail Alarm 1002 4 Uint16 2 R False=0 True=1
Alarms Clock Not Set Alarm 1002 5 Uint16 2 R False=0 True=1
Alarms Clock Battery Low Alarm 1002 6 Uint16 2 R False=0 True=1
Alarm Report Alarm Output 1002 7 Uint16 2 R False=0 True=1
Pre-Alarm Report Alarm Output 1002 8 Uint16 2 R False=0 True=1
Contact Outputs Output 1 1002 9 Uint16 2 R False=0 True=1
Contact Outputs Output 2 1002 10 Uint16 2 R False=0 True=1
Contact Outputs Output 3 1002 11 Uint16 2 R False=0 True=1
Contact Outputs Output 4 1002 12 Uint16 2 R False=0 True=1
Contact Outputs Output 5 1002 13 Uint16 2 R False=0 True=1
Contact Outputs Output 6 1002 14 Uint16 2 R False=0 True=1
Contact Outputs Output 7 1002 15 Uint16 2 R False=0 True=1
Contact Outputs Output 8 1003 0 Uint16 2 R False=0 True=1
Contact Outputs Output 9 1003 1 Uint16 2 R False=0 True=1
Contact Outputs Output 10 1003 2 Uint16 2 R False=0 True=1