Page 2
Every effort has been made to ensure that the material herein is complete and accurate. However, the manufacturer is not responsible for any mistakes in printing or faulty instructions contained in this book. Notification of any errors or misprints will be received with appreciation.
Table of Contents 1 GENERAL ....................5 2 MODBUS PROTOCOL IMPLEMENTATION..........6 Transmission Modes....................6 Address Field......................6 Function Field ......................6 Exception Responses ....................6 Modbus Register Addresses ..................6 Data Formats ......................7 Password Protection....................7 3 DATA SERVER ...................8 Data Server Features ....................8 Using Real-time Data Exchanges................9 3.2.1 Configuring Real-time Data Exchanges ..................9 3.2.2 Accessing Real-time Data Exchanges ..................9 3.2.3 Accessing Data Log Files .....................10...
Page 4
5 DATA FORMATS ..................21 Timestamp .........................21 Event Type ID ......................21 Event Data .........................21 Device Diagnostics (bitmap) ..................21 Shared Access Rules ....................22...
1 General This document specifies a subset of the Modbus serial communications protocol used to transfer data between a master computer station and the ETC2002. The document provides the complete information necessary to develop third-party communications software capable of communication with the ETC2002.
Modbus protocol in the ETC2002. 2.1 Transmission Modes The ETC2002 can be set up to communicate on a Modbus network using ASCII or RTU transmission mode. Refer to the "ETC2002 Installation and Operation Manual " on how to select the transmission mode in your device.
2.6 Data Formats The ETC2002 uses two data formats to pass data between a master application and the device: 16-bit short integer and 32-bit long integer formats. Data logged by the ETC2002 Data Server is collected from instruments in 16-bit short integer format.
The ETC2002 also provides up to 250 write data exchanges, of 1 to 12 registers long, and up to 250 status event data exchanges of 1 register long. Table 3-2 gives a summary of the available data exchanges.
Real-time data exchanges occupy a single continuous block of registers without gaps and are located in the ETC2002 memory in the address range of 0 to 9000. Since exchanges may have different size, the location of each exchange in the memory depends on the size of all preceding exchanges. Use the following formula to define the location of the data exchange: −...
3.2.3 Accessing Data Log Files Each data exchange is provided with a separate circular data log file. The Data server allocates a total of 1.5 Mbytes of non-volatile memory for all data log files, which will be equally divided between all active exchanges.
Data server detects a change in the status bits selected by the event mask, it records an event record to the circular Event log file. If the eXpertPower service is enabled in the ETC2002, this event will initiate a connection to the eXpertPower server.
The event log file is accessed in the same manner as data log files. Refer to Section 3.2.3 for details. 3.4 Using Data Write Exchanges The Data server can provide remote writing data to serviced devices upon user requests. Up to 250 write exchanges are supported with a size of 1 to 12 registers.
4 Modbus Register Map 4.1 Data Server Registers Address Point ID Description Options/Range Units Type Notes Real-time Data Exchange Block 0-9000 Data Exchange #1 … … Data Exchange #N Exchange Layout (120 registers maximum): +0,1 Record status 0=No data, -1=corrupted record, UINT32 Device response: function code or 1-65534 = device response code...
Address Point ID Description Options/Range Units Type Notes record, exception code (See 2.3-2.4) 1-65534 – device response code +2,3 Record time, seconds since 1/1/1970 UINT32 +4,5 Record sequence number 0-65535 UINT32 Data register 0-65535 UINT16 +119 Data register 0-65535 UINT16 Event Log Transfer Blocks 10016-10031 File Request Block...
Factory Device Settings and Identification 46080-46207 +0, 1 Device serial number UINT32 +2, 3 Device model ID 2000, 2002 UINT32 +4-11 Device model name “ETC2000”, “ETC2002” CHAR16 Null-terminated string +12-19 Reserved UINT16 Device firmware version number UINT16 Device firmware build number UINT16 +22,23...
Address Point ID Description Options/Range Units Type Notes +99-128 Reserved Device Options Setup 46256-46271 Log output Bit 0 = Dumping to console, UINT16 Bit 2 = Server Log Bit 3 = XP log Bit 4 = IPLINK log Bit 5 = Data Server log Bit 6 = Sharing log Number of XP faults for reset 0-200...
However, simultaneous file accesses to the same device could destroy device file buffers so both clients may receive corrupted data. To prevent such collisions, the user can disable shared device accesses so the ETC2002 will reject any additional requests addressed to a device that is being accessed by another client. In this event, the ETC2002 will return an exception response with the error code 10 = “Gateway is busy”...
Page 21
5 Data Formats Format Code Value Description Notes Timestamp Local time in a UNIX-style format. Represents the number of seconds since midnight (00:00:00), January 1, 1970. The time is valid after January 1, 2000. Event Type ID IRIG-B Sync Event 0x0800 XP client event (See F3 for Event data contents) DI Event...
Page 22
Format Code Value Description Notes Bit 11 = 1 RTC fault Bit 12 = 1 Configuration fault Bit 13 Reserved Bit 14 Reserved Bit 15 = 1 Master EEPROM fault Bit 16 Reserved Bit 17 Reserved Bit 18 Reserved Bit 19 Reserved Bit 20 = 1 C Library error...
Need help?
Do you have a question about the ETC2002 and is the answer not in the manual?
Questions and answers