MVI56-MCM ♦ ControlLogix Platform Configuration as a Modbus Slave
Modbus Communication Module
Page 52 of 159 ProSoft Technology, Inc.
July 24, 2008
MVI Address 0xxx 1xxxx 3xxxx 4xxxx Tag Address
100 1601 to 1616 11601 to 11616 30101 40101 WriteData[100]
200 3201 to 3216 13201 to 13216 30201 40201 WriteData[200]
500 8001 to 8016 18001 to 18016 30501 40501 WriteData[500]
598 9569 to 9584 19569 to 19584 30599 40599 WriteData[598]
599 9585 to 9600 19585 to 19600 30600 40600 WriteData[599]
600 to 999 N/A N/A N/A N/A Reserved
1000 31001* 41001 ReadData[0]
1001 31002* 41002 ReadData[1]
1002 31003* 41003 ReadData[2]
1003 31004* 41004 ReadData[3]
1004 31005* 41005 ReadData[4]
1005 31006* 41006 ReadData[5]
1006 31007* 41007 ReadData[6]
1007 31008* 41008 ReadData[7]
1008 31009* 41009 ReadData[8]
1009 31010* 41010 ReadData[9]
1010 31011* 41011 ReadData[10]
1050 31051* 41051 ReadData[50]
1100 31101* 41101 ReadData[100]
1200 31201* 41201 ReadData[200]
1500 31501* 41501 ReadData[500]
1598 31599* 41599 ReadData[598]
1599 31600* 41600 ReadData[599]
The above addressing chart will work with many Modbus applications. Values
listed in the ReadData array for 31001 to 31600 are shown with an * beside
them.
Although these are valid addresses, they will not work in the application. The
master must issue a Write command to the addresses that correspond to the
ReadData array. For Modbus addresses 3xxxx these are considered Input
registers, and a Modbus Master does not have a function code for this type of
data.
5.2.2 Customizing the Memory Map
In some cases, the above memory map will not work for the application.
Sometimes a master must read bits starting at address 0001, and also read a
register starting at 40001. With the above memory map, this is not possible, as
WriteData[0] is seen as both 0001 to 0016, and 40001. To accommodate this,
you can customize the starting location within the module for each device using
the parameters shown below.
To Next Page
Loading...
Need help?
General