Modbus Integration Kit for PAC Control User's Guide - Opto 22

More documents

Recommendations

Info

DATA TYPES SUPPORTED IN THE INPUT AND HOLDING REGISTERS For example, if you are dealing with floating point data using Data Type 2, you could try Data Type 3 in order to swap the order of the 16-bit words in the message. Using the Data Type Integer 32 Tables The example uses the following tables to designate the data type for each of the input and holding registers: • ntMB_Holding_Register_4X_Data_TypeM1 for master holding registers • ntMB_Input_Register_3X_Data_TypeM1 for master input registers • ntMB_Holding_Register_4X_Data_TypeS2 for slave holding registers • ntMB_Input_Register_3X_Data_TypeS2 for slave input registers Index 0 of these tables sets the way the data type tables are used by the subroutines. Master Subroutines Index 0 = 0 Use one data type. The data type used is in index 1. The length of the table must be 2 or more. The register offset is not used for the data type table. Index 0 = 1 The data and the data type are in the same index for each table. If the register offset is set to -7000 and the register to read is 7001 then the data will be stored in index 1 of the Modbus data table based on the data type at index 1 of the data type table. The length of the tables should be (start register + quantity + register offset + 1). The register offset is used for the data type table. Index 0 = 2 The data type index and register number are the same. If you read register 8001 it will use the data type at index 8001 of the data type table. The length of the table should be (start register + quantity + 1). The register offset is not used for the data type table. Slave Subroutines Index 0 = 0 Use one data type. The data type used is in index 1. The length of the table should be (highest register number + register offset + 1). The register offset is used for the data type table. Index 0 = 1 The data and the data type are in the same index for each table. If the register offset is set to -7000 and the register to read is 7001 then the data will be stored in index 1 of the Modbus data table based on the data type at index 1 of the data type table. The length of the tables should be (start register + quantity + register offset + 1). The register offset is used for the data type table. Index 0 = 2 Not supported 4 Modbus Integration Kit for PAC Control User’s Guide
CHAPTER 1: GETTING STARTED Protocols Supported The following protocols are supported: Comm Mode Name 0 Serial RTU protocol 1 Serial ASCII protocol 2 Modbus/TCP Important Note for Users Upgrading This Modbus integration kit replaces the Modbus/TCP Integration Kit for PAC Control (part # PAC-INT-MBTCP) and the Modbus Serial Integration Kit for PAC Control (part # PAC-INT-MBSER). This kit has the following characteristics: • The master subroutines support Modbus Serial RTU, Modbus Serial ASCII, or Modbus/TCP. • The slave subroutine can support from 1 – 4 ports. The ports can be configured as a mix of Modbus RTU, Modbus ASCII, or Modbus/TCP. • The subroutines support six data types for input and holding register data: – 16-bit unsigned – 16-bit signed – floating pt – floating pt swapped – 32-bit signed integer – 32-bit signed integer swapped A data type can be set for each register. This allows the reading and writing of multiple registers with different data types. • The subroutines support an offset variable when an offset is needed between the registers and index of the data tables. • The subroutines support a register mode variable used to make the system compatible with Modbus devices that store floats and 32-bit integers in one register and those that use two registers. • The subroutines have a string table that returns the status of communications, the transmit string and the receive string. • The subroutines have an integer 32 table used to return any error codes. The master subroutines also have the “OK” and “failed count” status for each packet sent. Installing the Integration Kit To install the integration kit on your computer, unzip the PACModbus.zip file to your C: drive. The expanded files will be placed automatically in the PACModbus directory. Modbus Integration Kit for PAC Control User’s Guide 5 5
Page 1 and 2: MODBUS INTEGRATION KIT FOR PAC CONT
Page 3 and 4: Table of Contents Chapter 1: Gettin
Page 5 and 6: Chapter 1 1: Getting Started The Mo
Page 7: CHAPTER 1: GETTING STARTED Modbus F
Page 11 and 12: Chapter 2 2: Using the Master Subro
Page 13 and 14: CHAPTER 2: USING THE MASTER SUBROUT
Page 19 and 20: Chapter 3 3: Using the Slave Subrou
Page 21 and 22: CHAPTER 3: USING THE SLAVE SUBROUTI
Page 23 and 24: CHAPTER 3: USING THE SLAVE SUBROUTI
Page 25 and 26: Chapter 4 4: Subroutine Parameters
Page 27 and 28: CHAPTER 4: SUBROUTINE PARAMETERS 02
Page 39 and 40: CHAPTER 4: SUBROUTINE PARAMETERS Su
Page 41 and 42: CHAPTER 4: SUBROUTINE PARAMETERS 6.
Page 43 and 44: CHAPTER 4: SUBROUTINE PARAMETERS -
Page 45 and 46: Chapter 5 5: Troubleshooting Troubl

Modbus Integration Kit for PAC Control User's Guide - Opto 22

Create successful ePaper yourself

Delete template?

Save as template?