CIG-AP129 - Rockwell Automation
Contents
1. New Routine de cut Unscheduled Prograrr 4 Paste the Modbus_Interface program into the ModTask task in your RSLogix 5000 project amp RSLogix 5000 My_Modbus_Project 1756 File Edit View Search Logic Communications alela alle ol Offline fl RUN NoForces p ae f No Edits a Evo E Controller My_Modbus_Project Controller Tags Controller Fault Handler i Power Up Handler amp Tasks a MainTask 3 MainProgram Unsched New Program amp Motion Group Cut Ctx Ungroupi Cte Trends ul rer ats Te User Def Publication CIG AP129A EN P February 2004 16 Using Logix5000 Controllers as Masters or Slaves on Modbus A Right click on your controller B Click Properties A Click on the Serial Port tab B Use the pulldown menu to change the mode to User C If you need to change your Read Write Buffer Size apply your changes and move to step 3 on page 17 D If you do not need to change your Read Write Buffer Size click OK and move to page 17 Publication CIG AP129A EN P February 2004 Configure the Controller s Communication Port After you copy the new UDTs controller tags ModTask task and Modbus_Interface program into your RSLogix 5000 project configure the communication port for the Logix5000 controller in your RSLo2. Ep Strings Git Predefined Gi Module Defined I O Configuration 1 1756 1B16D 2 1 1756 CNBR E Local_Contr f 6 IB16 G Mod_Commands 0 Starting4ddress Mod_Commands 0 NumberofPoints_ BERR RRO R ee PaAnees Enable the New Program Mod_Commands 0 Spare1 Mod_Commands 0 Spare2 Finally you must enable the new program before it will run To enable the new program you must change the Mod_Active controller tag to 1 By default this tag 0 so you can load the program using the steps described in this document to your RSLogix5000 project without the program starting Verify that the Modbus_Interface Program is Working Once you copy everything from the Modbus Master ACD file into your RSLogix 5000 project monitor your controller s Main Task to make sure the Modbus_Interface program is returning data correctly To see how to monitor your project to make sure it is operating properly see page 32 Publication CIG AP129A EN P February 2004 22 Using Logix5000 Controllers as Masters or Slaves on Modbus Using Logix5000 Controllers is ee een file aes you use a Logix5000 controller as a ske Modbus The ACD file contains as Slaves on Modbus ER i e 10 controller tags e 1 periodic task You must do the following tasks to use an Logix5000 controller as a slave on Modbus 1 Copy Controller Tags From the ModbusSlave ACD File to Your RSLogix 500
3. H EE Salo Configuration ii jEr T InpReg3 i poe i E Mod_RangeHoldReg4 To change the Modbus Register Range tags size do the following steps 1 On the Monitor Tags tab highlight the tag value E Controller My_Modbus_slave_proje Controller Tags f Controller Fault Handler E be Tag size highlighted 1O Configuration 1 1756 17612 2 1756 IF6C15 A TLLELLLOLLo ee lee eg gle AANI Publication CIG AP129A EN P February 2004 New tag size Using Logix5000 Controllers as Masters or Slaves on Modbus 31 2 Type the new size 3 Press the Enter key to see the new size reflected in the tag S RSLogix 5000 My_Modbus_slave_project 1756 L63 File Edit View Search Logic Communications Tools Window Help alsa 8 e 2 slsls Te Ve eel Offline F RUN A ed Pah eroro dall NoForces P e a i Tica bs Noes Al 4 Bei pel aooo of __ 0 ie Redundancy W9 D 4 of Favorites Timericounter m e B S Controller My_Modbus_slave_proje A Controller Tags G Controller Fault Handler Power Up Handler 5 8 Tasks B S MainTask Ej a MainProgram ModTask ts C3 Modbus Slave i eae mE Unscheduled Programs Mod_Active 0 Decimal B00L E E Motion Groups _ EMod Data Coisd RE Decimal INT 50 Un
4. Logic Communications Tools Window Help asa a ele elif al ERAN Offline J F RUN E EA Pan nono R d2 NoFoces gt E No Forces b ToK No Edits 2 0 Kii ajaja aejk E Redundancy i w aft Favorites Timer Counter TpuOuiput K Compare JE Controller My_Modbus_slave_proje Controller Tags Controller Fault Handler Power Up Handler 6 8 Tasks B S MainTask a MainProgram E Unscheduled Programs 5 6 Motion Groups Ungrouped Axes AB 1756_Al6 Fo AB 1756_AI6_CJ_ AB 1756_Al6 Flo AB 1756_Al6_ Flo B00L Mod_Active a Trends Mod_Data_Coils0 INT 100 9 Data Types Mod_Data_Contacts1 _ INT 100 GR User Defined H F Mod_Data_InpReg3 INT 100 E Strings al E Mod DataHoldReg4 TINTEO0 E Module Defined T Mod_Node_Address SINT 5 6 1 0 Configuration A F Mod_Range_Coils0 DINT fJ 1 1756 17612 Mod_Range_Contt DINT i B 2 1756 1F6c15 A J E Mod_Range_InpReg3 DINT I E Mod_FRangeHoldReg4 DINT EJN Table 4 Tag name Mod_ Active Using Logix5000 Controllers as Masters or Slaves on Modbus 25 New Modbus Slave Controller Tags Table 4 describes the controller tags you copied from the ModbusSlave ACD file to your RSLogix 5000 project Tag type BOOL Description
5. Mod_Commands x StartingAddress Mod_Commands x Numberofpoints Before you configure the tags listed above make sure you understand how a Modbus master uses the tag configuration to read data from and write data to its data table Publication CIG AP129A EN P February 2004 18 Using Logix5000 Controllers as Masters or Slaves on Modbus Tag Arrays in Modbus Master Data Table There are 4 tag arrays in Modbus master data tables one for each of the following e Coil data Mod_Data_Coils0 tags data is read from or written into this array in bit format e Contact data Mod_Data_Contacts1 tags data is written to this array in bit format e Input Register data Mod_Data_InpReg3 tags data is written to this array in word format e Hold Register data Mod_DataHoldReg4 tags data is read from or written into this array in bit format Depending on how you configure the Mod_Commands tags in this solution the Modbus master e uses 1 of its 4 arrays at a time determined by the function code e reads data from or writes data to a specific location determined by the address offset and the starting address e reads or writes a specific amount of data determined by the number of points e reads the data to be written to a slave node or writes data that was read from a slave node to a specific location For more information see the example on page 19 Publication CIG AP129A EN P February 20
6. Mod_Data_InpReg3 INT 250 Modbus register Input registers that the Modbus master receives from the slave Mod_Data_HoldReg4 INT 250 Modbus register Output registers that the Modbus master sends to the slave Publication CIG AP129A EN P February 2004 14 Using Logix5000 Controllers as Masters or Slaves on Modbus Table 2 Tag name Tag type Description Valid values Mod_Echo_MaxTime DINT Maximum time milliseconds for We recommend you set this time the master to wait for a echo from a greater than the time it takes to send slave before determining the slave the longest MSG in your project node is missing Mod_Scan_Preset DINT Number of scans the master should 0 40 perform We recommend at least 2 Copy ModTask From the ModbusMaster ACD File to Your RSLogix 5000 Project After you have copied the new UDTs and controller tags into your RSLogix 5000 project you must copy the ModTask task and its corresponding Modbus_Interface program to your RSLogix 5000 project IMPORTANT The ModTask is configured as a Periodic task with a Period 9ms We determined this period to allow for the best performance of the solution If you would like this solution to use less controller resources A Right click on ModTask B Click Copy Publication CIG AP129A EN P February 2004 increase the period Do these steps to copy the task 1 Copy the ModTask task from the ModbusMas
7. Mod_Commands x AddressOffsetinMaster tag to determine the starting address when the master reads or writes data in its data table Depending on the command element s function code this value may be in bits or words For example if this tag 5 ina command element that uses function code 01 bit level code Read Coils the address offset is increased by 5 bits However if the command element uses function code 03 word level code read holding registers the address offset is increased by 5 words Valid values Application specific Mod_Commands x Numberofpoints NT Designates the number of points that the controller should read or write Depending on the command element s function code this value may be in bits or words For example if this tag 10 ina command element that uses function code 03 word level code Read Holding Registers the controller reads 10 words Application specific Mod_Commands x Spare1 INT Not used Mod_Commands x Spare2 INT Not used Mod_CommdMax DINT Maximum number of commands you want to use in your program 40 default Mod_Data_Array_Max DINT Modbus_Data registers size Modbus_Data register size Mod_Data_Coils0 INT 250 Modbus register Output bit that the Modbus master sends to the slave Mod_Data_Contacts1 INT 250 Modbus register Input bit that the Modbus master receives from the slave
8. This tag determines whether your project runs the new program ina Logix5000 controller This tag 0 i e the solution is disabled by default and you must change the tag to 1 to run the solution Valid values 0 Do not run the program default 1 Run the program Mod_Data_Coils0 INT Modbus Data Register Output bits that the Modbus master writes data to Mod_Data_Contacts1 INT Modbus Data Register Input bits that the Modbus master reads data from Mod_Data_InpReg3 INT Modbus Data Register Input register that Modbus master reads data from Mod_Data_HoldReg4 INT Modbus Data Register Output register that Modbus master writes data to Mod_Node_Address SINT Modbus Slave Node Address Represents the Modbus slave s node address 0 255 Mod_Range_Coils0 DINT Modbus RegisterSize Tag that monitors the array size of the Mod_Data_Coils0 tag The default size for this tag is 100 words meaning the Mod_Data_Coils0 tag is limited to 100 words of data You only need to change the size of this tag if you change the size of the tag it monitors For example if you change the Mod_Data_Coils0 tag size to 50 words you should change this tag size to 50 or less Publication CIG AP129A EN P February 2004 26 Using Logix5000 Controllers as Masters or Slaves on Modbus Table 4 Tag name Mod_Range_Cont1 Tag type DINT Description
9. ae Purpose of the Document Who Should Use This Document Application Solution Using Logix5000 Controllers as Masters or Slaves on Modbus This application solution and the associated RSLogix 5000 project files help you use Logix5000 controllers as Modbus RTU masters or slaves The term Logix5000 controller refers to any controller that is based on the Logix5000 operating system such as e ControlLogix controllers 1756 e CompactLogix controllers 1769 e FlexLogix controllers 1794 e PowerFlex 700S with DriveLogix controllers The sample RSLogix 5000 projects provided with this solution use ControlLogix controllers However you can use the controller tags periodic tasks and user defined data types described later in this document with any Logix5000 controller This manual is intended for individuals who program applications that use Logix5000 controllers on Modbus such as e software engineers e control engineers e application engineers You should be familiar with e Logix5000 controllers e RSLogix 5000 e Modbus RTU IMPORTANT This application solution is intended for experienced Modbus users Publication CIG AP129A EN P February 2004 2 Using Logix5000 Controllers as Masters or Slaves on Modbus Before You Begin Publication CIG AP129A EN P February 2004 Before you use this application solution consider the following e Application Solution Disclaimer e Controller
10. command elements 5 39 This number should match the number of command elements used in your project Mod_Commands Command 40 Command file that contains multiple user defined configurable parameters described below Mod_Commands x Enable INT Determines if the command 0 Command element disabled element is enabled 1 Command element enabled always 2 Command element enabled when controller reaches the scan number listed in the Mod_Commands x ScanNumber tag 3 Command element enabled only on the 1st scan Mod_Commands x EchoReceived INT The master controller writes a 0 Command element was either number in this field if the command element was successfully executed The number written matches that used in the Mod_Commands x Enable tag For example if you set the Mod_Commands x Enable tag 3 the controller writes a 3 in this field if the command element was executed successfully disabled or did not execute successfully 1 2 or 3 Command element was successfully executed typically this value is 1 because the Mod_Commands x Enable tag is typically 1 Write 0 in this field before enabling the instructions to monitor the change after the Command element executes Publication CIG AP129A EN P February 2004 12 Using Logix5000 Controllers as Masters or Slaves on Modbus Publication CIG AP129A EN P February 2004 Table 2 Tag name Tag type Description Valid values Mod_Com
11. Help alela a selejoojf a PIB IE OB IQ Offline F RUN T N E ath rone z amp aj rt feat 4 wo 40 oj a Favorites Kon a Controller My_Modbus_project A Controller Tags Controller Fault Handler lolx Gi Power Up Handler tasks MainTask amp Modbus_Slave Unscheduled Programs 5 6 Motion Groups Gi Ungrouped Axes G Trends 5 6 Data Types GR User Defined E Strings E E Predefined Oy Module Defined E Yo Configuration BOOL INT 100 INT 100 INT 100 INT 100 SINT DINT DINT DINT DINT 5 Paste the controller tags into your RSLogix 5000 project File Edit View Search Logic Communications ajajaj S tele ejer Offline fl F RUN Lh No Forces b E ok f No Edits T BAT a F 1 0 a Controller Demo Controller Fault Handler Power Up Handler B 83 Tasks ata MainTask Publication CIG AP129A EN P February 2004 24 Using Logix5000 Controllers as Masters or Slaves on Modbus gt B Make sure you are in the Tag Editor C Make sure you are pasting the tags into the controller scope D Right click on the bottom tag line E Click Paste New controller tags in the Modbus master file Publication CIG AP129A EN P February 2004 SLogix 5000 My_Modbus _slave_project 1756 1 163 File Edt View Search Logic Communications Tools Window Help aleju
12. Modbus RegisterSize Tag that monitors the size of data used in the Mod_Data_Contacts1 tag The default size for this tag is 100 words meaning the Mod_Data_Contacts1 tag is limited to 100 words of data This tag s size is purposely 2 words smaller than the tag it monitors to prevent array overflow You only need to change the size of this tag if you change the size of the tag it monitors Valid values Mod_Range_HoldReg4 DINT Modbus RegisterSize Tag that monitors the size of data used in the Mod_Data_HoldReg4 tag The default size for this tag is 100 words meaning the Mod_Data_HoldReg4 tag is limited to 100 words of data You only need to change the size of this tag if you change the size of the tag it monitors Mod_Range_InpReg3 Publication CIG AP129A EN P February 2004 DINT Modbus RegisterSize Tag that monitors the size of data used in the Mod_Data_InpReg3 tag The default size for this tag is 100 words meaning the Mod_Data_InpReg3 tag is limited to 100 words of data You only need to change the size of this tag if you change the size of the tag it monitors Using Logix5000 Controllers as Masters or Slaves on Modbus 27 Copy ModTask From the ModbusSlave ACD File to Your RSLogix 5000 Project After you copy the controller tags from the ModbusSlave ACD file into your RSLogix 5000 project you must copy the ModTask task and its corresponding program to your project as well
13. No Forces b oes I No Edits Ale 4 EASE m0 Redundancy Bo m B Controller My_Modbus_project A Controller Tags E Controller Fault Handler G Power Up Handler 6 8 Tasks B S Maintask E MainProgram Unscheduled Programs 5 8 Motion Groups Ungrouped Axes Trends 4g Data Types Ch New Data Type E E Predefin om c Ctri x oe Module 3 IO Configur H E Strings opy Ctrl Ke Paste Ctrl You can only paste one UDT at a time 6 Repeat the previous Copy Paste steps for the second UDT Publication CIG AP129A EN P February 2004 8 Using Logix5000 Controllers as Masters or Slaves on Modbus Copy Controller Tags From the ModbusMaster ACD File to Your RSLogix 5000 Project Do the following steps to copy the controller tags to your Modbus program 1 Copy the controller tags from the ModbusMaster ACD file i i RSLogix 5000 Modbus_Master in Mq File Edit View Search Logic Communic alsia a soley 2 Offline fl E RUN i No Forces b OK _ No Edits a E a Controller Modbus_Master Controller Tags Controller Fault Handler Power Up Handler B 68 Tasks 5 ModTask E G Modbus_Interface Unscheduled Programs A Double click on Controller Tags in the Modbus master file gt Picrstonn sono modbus masier mmodusmasiaraco tiroen Fie Edit View Search Logic Communications Tools Window Help alsm S e eo 7 gsls E ve aa Offline 0 F
14. amp ee zk q J al ma n Tipe RA Po lt none gt See Ok an pees iae sete a al gt Favorites ABit A Timer Counter A B 83 Controller My_Modbus_slave_proje Controller Tags My_Modbus_slave_project ca Controller Tags 4 Se ma My a 1 Modbus_sl gt Show Show All Controller Fault Handler panikk ho Power Up Handler Se TagName Brine Alias F 5 Tasks Monitor Tag a a MainTask X Edit Tag Properties Alt Enter MainProgram 7 Edit Data T Unscheduled Programs seed 5 Create Tag which aliases Ungrouped Axes Trend Tag G Trends ats 6 8 Data Types Go to Cross Reference Ctrl E i User Defined Goto Axis Wizard oe Strings si Go to Axis Properties i Predefined aie 4 ER Module Defined ES y 5 6 1 0 Configuration Go to Coordinate System Properties J 1 1756 1T612 Goto Motion Group Wizard B 2 1756 IFecis a fs Go to Coordinate System Wizard i Go to Motion Group Properties Go to PID Properties B Go to Message Properties Go to Cam Cam Profile Editor Go to Output Cam Editor Go to Message Path Editor Go To Ctrl G Options Cut Ctrltex Insert Clipboard contents a Copy cele RSLogix 5000 pastes the new tags into your RSLogix 5000 project and keeps them together because all 10 tags use a Mod_ prefix as shown below SLogix 5000 My_ Modbus _slave_project 1756 L631 le Edit View Search
15. function code e f the command uses a write function code the slave merely answers the master with the same data the master is writing In this case this tag shows the high starting address of the data written to the slave e f the command uses a read function code the slave returns the requested data i e the data the master is reading from the slave In this case this tag shows the number of bytes needed to return the data requested in the Mod_Commands x Numberof points controller tag in the command Publication CIG AP129A EN P February 2004 Table 6 This Program Tag Mod_Status x LowStartAddress_Data Mod_Status x HiNumOfPoints_Data Mod_Status x LowNumOfPoints_Data www rockwellautomation com available in this ACD file ModbusMaster ACD file only Power Control and Information Solutions Headquarters has this description This tag corresponds to the Mod_Commands x Starting Address controller tag in the command Data shown is dependent on whether the command used a read or write function code e f the command uses a write function code the slave merely answers the master with the same data the master is writing In this case this tag shows the low starting address of the data written to the slave e f the command uses a read function code the slave returns the requested data i e the data the master is reading from the slave In this case this tag shows the data at the low startin
16. 0 Project 2 Copy ModTask From the ModbusSlave ACD File to Your RSLogix 5000 Project 3 Configure New Controller Tag Sizes 4 Enable the New Program 5 Verify that Your RSLogix 5000 Project is Working Copy Controller Tags From the ModbusSlave ACD File to Your RSLogix 5000 Project Do the following steps to copy the controller tags to your Modbus program 1 Start RSLogix 5000 2 Open the ModbusSlave ACD file The ACD file is available at either of the following locations e Allen Bradley Channel Extranet Download the file from the United States Channel Extranet e Vendor Sample Project PDF Access the PDF via the Help menu in RSLogix 5000 3 Open your RSLogix 5000 project in a second instance of RSLogix 5000 Publication CIG AP129A EN P February 2004 Using Logix5000 Controllers as Masters or Slaves on Modbus 23 4 Copy the controller tags in the ModbusSlave ACD file File Edit View Search Logic Communicatio alsa 3 dele ol Offline D E RUN No Forces b ae No Edits a r A 1 A Double click on T Controller Faut Handler Controller Tags i Power Up Handler b Tasks E a MainT ask 23 Modbus_Slave a Unscheduled Programs fS RSLogix 5000 My_Modbus_project in ModbusSlave ACD 1756 L1 lolx B Select the 10 controller tags C Copy the tags using the CTRL C keystroke A Double click on Controller Tags File Edit View Search Logic Communications Tools Window
17. 0 keep the new tags together in your RSLogix 5000 project because all 11 tags use a Mod_ prefix as shown below ict hes oo ef Favorites KETC My_Modbus_project aaa ope My_Modbus_project 7 SI G Controller Fault Handler Power Up Handler TN earring MainTask ie MainProgram E Unscheduled Programs Mod_Cmd_Number A Mod_Commands Mod_CommdMax Mod_Data_Array_Max i _ F Mod_Data_Coils0 New controllertags _ Predefined Bey E Mod Data_Contacts1 i H it Mod_Data_In inoue Depus tle 510 configuration FE Mod_Echo_MaxTime A Mod_Scan_Preset 3 1756 IB161 Publication CIG AP129A EN P February 2004 Using Logix5000 Controllers as Masters or Slaves on Modbus 11 New Modbus Master Controller Tags Table 4 describes the controller tags you copied from the ModbusMaster ACD file to your RSLogix 5000 project Table 2 Tag name Tag type Description Valid values Mod_Active BOOL This tag determines whether your 0 Do not run the program default project runs the new program ina Logix5000 controller 1 Run the program This tag 0 i e the solution is disabled by default and you must change the tag to 1 to run the solution Mod_Cmd_Number DINT Number of command elements i e Any value from 1 40 Mod_Commands tag scanned For example if you set this tag 5 the controller only scans command elements 0 through 4 and ignores
18. 04 Using Logix5000 Controllers as Masters or Slaves on Modbus 19 EXAMPLE If you want the following to occur when a command is executed e the command is always enabled G e occurs with every scan e the master writes the coil data beginning at word 2 in the Coil data register e coil data is read from the Modbus slave at node 2 e the master begins writing at bit 3 of word 2 in the Coil data register e 32 bits of coil data are read from the slave Configure your command with these tag values e Mod_Commands 0 Enable 1 e Mod_Commands 0 AddressOffsetinMaster 2 e Mod_Commands 0 SlaveAddress 2 0 FunctionCode 1 0 StartingAddress 4 0 Numberofpoints 32 e Mod_Commands e Mod_Commands e Mod_Commands This example command is shown in the graphic below 32 bits Mod_Commands 0 Numberofpoints 32 Coil data register Slave at Node 1 in Modbus master ___ S lt Si cco ill data are read data table Mod_Commands 0 FunctionCode 01 Word 0 Word 1 from the slave at node 2 Word 2 VV Mod_Commands 0 SlaveAddress 2 Slave at Node 2 Word 3 gt Word 4 the coil data is written beginning in word 2 e Mod_Commands 0 AddressOffsetinMaster 2 Slave at Node 3 Word 249 the coil data is written beginning at the 4th coil bit 3 of word 2 Mod
19. 40 Asia Pacific Rockwell Automation Level 14 Core F Cyberport 3 100 Cyberport Road Hong Kong Tel 852 2887 4788 Fax 852 2508 1846 Publication CIG AP129A EN P February 2004 Copyright 2004 Rockwell Automation Inc All rights reserved Printed in the U S A
20. Do the following steps to copy the ModTask task to your RSLogix 5000 project 1 Copy the ModTask task from the ModbusSlave ACD file s RSLogix 5000 My_Modbus_project in Modb File Edit Yiew Search Logic Communications alsel a Hae Offline J E No Forces gt ro EJ mses M BAT No Edits a To Al B Controller My_Modbus_project A Controller Tags Controller Fault Handler Gi Power Up Handler A Right click on is read New Program ModTask ee cu ars 5 6 Motion Gro aN E ngre B Click Copy TT Trends 6 6 Data Type Delete Del User D ele ee E G Strings Cross Reference Ctrl E Ga Predef es Gg Module Properties 2 Paste the ModTask task into your RSLogix 5000 project RSLogix 5000 My_Modbus_slav File Edit View Search Logic Comr alsa 2 e Offline fl E RUN No Forces b a No Edits Ale Va Redundancy ooo 3J Controller My_Modbus_slave_pr Controller Tags Controller Fault Handler Gi Power Up Handler A Right click on Task ey man ae Cut Ctrl X r Copy Ctrl C B Click Paste Publication CIG AP129A EN P February 2004 28 Using Logix5000 Controllers as Masters or Slaves on Modbus 3 Copy the Modbus_Slave program from the ModbusSlave ACD file RSLogix 5000 ModbusSlavel in ModbusSlave42 ACD 1756 L1 1 ire es wy Rea Po eee DY Mef Fovortes A Con
21. RUN R EA Path none S era MOK r aj fl ed dF ae F w gt No Forces ap M BAT 4 gt Favorites No Edits Ale in af B Make sure you are in the Tag Editor B 68 Controller Modbus_Master oj A Controller Tags amp Controller Fault Handler Power Up Handler SS tasks E ModTask E E Modbus_Interface Gi Unscheduled Programs B E Motion Groups BOOL DINT C Highlight the 11 controller tags D Copy the tags using Ungrouped Axes G Trends the CTRL C E ta Toe a User Defined keystroke Es Mod_Command_Structure i Mod_status H E Strings E E Predefined m Marile Nefined Publication CIG AP129A EN P February 2004 A Double click on Controller Tags in your project gt B Make sure you are in the Tag Editor C Make sure you are pasting the tags into the controller scope D Right click on the bottom tag line E Click Paste in your project Using Logix5000 Controllers as Masters or Slaves on Modbus SLogix 5000 My Modbus E File Edit View Search Logic Communica alsm a ele E Offline D M RUN No Forces b i _ No Edits Ale iz Redundancy So B S Controller My_Modbus_project Controller Tags Controller Fault Handler Power Up Handler 6 8 Tasks aa MainTask 2 Paste the controller tags into your RSLogix 5000 project SLogix 5000 My _Modbus_project 1756 L63 Fil
22. Serial Port Unvailable as a Programming Connection If Used as a Master on Modbus e Subset of Modbus Function Codes e Automatic Conversion of Little Endian Data to Big Endian Data e Connect Logix5000 Controller to RS485 Network Via 1761 NETAIC e Sample Files in RSLogix 5000 v13 Format Application Solution Disclaimer All information is provided AS IS No warranty or implied merchantability Controller Serial Port Unvailable as a Programming Connection If Used as a Master on Modbus When you use your Logix5000 controller as a master on Modbus as described beginning on page 5 you must change your controller s mode to User In this case your controller s serial port is unavailable as a programming connection Using Logix5000 Controllers as Masters or Slaves on Modbus 3 Subset of Modbus Function Codes This solution only supports a subset of Modbus function codes Table 1 describes the function codes this solution supports Table 1 Function code Name Data level Description 01 Read Coils Bit level This function code is used to read from 1 to 2000 contiguous status of coils in a remote device The coils in the response message are packed as one coil per bit of the data field 0 OFF 1 0N 02 Read Discrete Inputs This function code is used to read from 1 to 2000 contiguous status of discrete inputs in a remote device The discrete inputs in the response message a
23. Tag Ctrl Monitor Tags Edit Tags Verify Export Tags Print Publication CIG AP129A EN P February 2004 34 Using Logix5000 Controllers as Masters or Slaves on Modbus 2 Scroll to the tags you need to monitor The example screen below shows Mod_Status tags used in the ModbusMaster file to monitor the operation of command element 1 Scope Interface E Show ER 7 Sort Tas Name a ANA Mod_Status 60 Mod_Status Mod_Status 0 tey Mod_Status 1 AA Mod_Status 1 NodeAddress l4 Decimal SINT A Expand the tags as needed E Mod_Status 1 FunctionCode 15 Decimal SNTE B Monitor these values e Mod StatusittHiStertAddr ByteGoont_ o Decimal SINT Mod_Status 1 LowStartAddress_Data 2 Decimal SINT i Mod_Status 1 HiNumOfPoints_Data h 0 Decimal SINT Mod_Status 1 LowNumOfPoints_Data 3 Decimal SINT Some of the Program Tags correlate directly to Mod_Commands elements Table 6 on describes some of the Program Tags you can use to monitor and troubleshoot your program Table 6 This Program Tag available in this ACD file has this description MsgCountRec ModbusMaster ACD file Counts the number of messages received every 10 seconds e In the ModbusMaster ACD file this tag should closely ModbusSlave ACD file match the MsgCountTrans tag If there is a considerable difference then some commands may have be
24. _Commands 0 StartingAddress 3 In this example the Mod_Commands 0 StartingAddress and Mod_Commands 0 Numberofpoints tags represent bit values because the Modbus function code was 01 Read Coils a bit level code If a word level Modbus function code e g 03 Read Holding Registers was used the Mod_Commands 0 StartingAddress and Mod_Commands 0 Numberofpoints tags would represent word values In other words instead of reading 32 bits of data from the slave the master would read 32 words of data from the slave and write 32 words into its data table beginning with word 5 Publication CIG AP129A EN P February 2004 20 Using Logix5000 Controllers as Masters or Slaves on Modbus Do these steps to change the tag values 1 Access the controller tags s RSLogix 5000 My_Modbus_project Double click on Controller Tags in your project Power Up Handler Tasks E Maintask 2 Select the Monitor Tags tab 3 Change the tags as necessary For example the screen below shows the Commands 0 Enable tag E RSLogix 5000 My_Modbus_project 1756 L63 Controller Fault Handler Power Up Handler amp Tasks EE MainTask O amp mainProgram A Highlight the tag value B Type a new value C Press the Enter key Publication CIG AP129A EN P February 2004 Using Logix 5000 Controllers as Masters or Slaves on Modbus 21 The sample screen below uses tags tha
25. _Commands x FunctionCode tag in the command sent from the master to the slave Shows the function code of the command element sent to the slave if the command was executed successfully In this case the tag shows one of the function codes supported in this solution i e 1 2 3 4 5 6 15 or 16 If the command was not executed successfully this tag shows one of the following 0 Command is disabled In this case 0 appears in all Mod_Status fields 1 Command is sent but the node does not answer The node may not have answered because e the slave does not exist e the slave exists but took too long to respond e the master sent a function code this solution doe not support e the master sent a bad CRC 2 Command is not sent because the number of bits exceeds 320 or array limits in the Master were exceeded 10 Command is not sent because an invalid function code is used in that command 1xxx Command is sent but the slave cannot execute the command and returns the function code plus Hex80 This then appears as Function Code 128 in decimal notation 1xx Command with Mod_Commands x Enable 3 one time execution was processed In this case xx represents the function code This display may be old because it shows last time execution data This tag corresponds to the Mod_Commands x Starting Address controller tag in the command Data shown is dependent on whether the command used a read or write
26. e Edit View Search Logic Communications Tools window Help aisle a ole 1 17 a1 ilo Offline fl RUN No Forces b ao HOES 2 m vo Redundancy Dad TE Path erone a e AAE 4 P Favorites Bit Timer Counter Imp B 83 Controller My_Modbus_project Controller Tags E Controller Fault Handler GE Power Up Handler B 86 Tasks B S MainTask H E MainProgram a Unscheduled Programs ca Ungrouped Axes Trends amp J Data Types GR User Defined Mod_Command_Structure Mod_Status Gi Strings Gih Predefined Gp Module Defined 1 0 Configuration A 1 1756 1B816D 2 1 1756 CNBR E Local_Contr S1 1756 IB16I e My_Modbus_project 7 A Show Show All Insert Clipboard contents P Tag Name amp Alias F P I Monitor Tag Edit Tag Properties Alt Enter Edit Data Type Create Tag which aliases Trend Tag Go to Cross Reference Ctrl E _ Goto Axis Wizard Go to Axis Properties Go to Coordinate System Wizard Go to Coordinate System Properties Go to Motion Group Wizard Go ta Motion Group Properties Go to PID Properties Go to Message Properties Go to Cam Cam Profile Editor Go to Output Cam Editor Go to Message Path Editor Go To Ctrl G Options Cut Ctrl x Copy Ctrl C SEAT ITEE TOTTA Sar ee Publication CIG AP129A EN P February 2004 10 Using Logix5000 Controllers as Masters or Slaves on Modbus RSLogix 500
27. en sent to a slave that does not exist or cannot respond e In the ModbusSlave ACD file this tag may not closely match the MsgCountIrans tag because the slave receives all messages but only transmit when addressed MsgCountTrans Counts the number of messages transmitted every 10 seconds e In the ModbusMaster ACD file this tag should closely match the MsgCountRec tag If there is a considerable difference then some commands may have been sent to a slave that does not exist or cannot respond e In the ModbusSlave ACD file this tag may not closely match the MsgCountRec tag the slave receives all messages but only transmit when addressed MsgTimeSpent Measures the time used for a transaction from the moment it is sent by the master until an answer is received from the slave If the slave does not answer this tag will match the MsgTimeMax program tag Mod_Status x NodeAddress ModbusMaster ACD file only This tag corresponds to the Mod_Commands x SlaveAddress tag in the command sent from the master to the slave Shows the node address of the slave to which the master sent the command Publication CIG AP129A EN P February 2004 Using Logix5000 Controllers as Masters or Slaves on Modbus 35 Table 6 available in this ACD file This Program Tag Mod_Status x FunctionCode Mod_Status x HiStartAddr_ByteCount ModbusMaster ACD file only has this description This tag corresponds to the Mod
28. fered in this document In other words you want to make sure your application is operating correctly Both the ModbusMaster and ModbusSlave ACD files provide diagnostic features to verify that e a command executed e a command transmitted e slaves answer correctly after receiving a master s command e slaves rejecting a command do so with an error code Both ACD files used in this application solution provide diagnostics although the ModbusMaster ACD file provides significantly more diagnostics than the ModbusSlave ACD file Verify Successful Command Execution You can verify that a command executed successfully when your Modbus master sends a command element to a Modbus slave simply by monitoring the Mod_Commands x EchoReceived tag Do these steps to verify successful execution 1 Before sending a command to a Modbus slave set the Mod_Commands x EchoReceived tag 0 via the Tag Monitor in RSLogix 5000 2 Send the command to the Modbus slave 3 Monitor the value in the Mod_Commands x EchoReceived tag e If the tag value changes to match the value used in the command elements Mod_Commands x Enable tag i e 1 2 or 3 the command executed properly and the slave returned a valid response Note that the execution may continuously repeat if repeated scans are occurring e If the tag value of the command element s Mod_Commands x Enable tag remains 0 the command was not executed successfully Using Logix5000 Cont
29. g address This tag corresponds to the Mod_Commands x Numberof points controller tag in the command Data shown is dependent on whether the command used a read or write function code e f the command uses a write function code the slave merely answers the master with the same data the master is writing In this case this tag shows the high point number of the data written to the slave e f the command uses a read function code the slave returns the requested data i e the data the master is reading from the slave In this case this tag shows the 2nd byte of data requested This tag corresponds to the Mod_Commands x Numberof points controller tag in the command Data shown is dependent on whether the command used a read or write function code e f the command uses a write function code the slave merely answers the master with the same data the master is writing In this case this tag shows the low point number of the data written to the slave e f the command uses a read function code the slave returns the requested data i e the data the master is reading from the slave In this case this tag shows the 3rd byte of data requested Americas Rockwell Automation 1201 South Second Street Milwaukee WI 53204 2496 USA Tel 1 414 382 2000 Fax 1 414 382 4444 Europe Middle East Africa Rockwell Automation Vorstlaan Boulevard du Souverain 36 1170 Brussels Belgium Tel 32 2 663 0600 Fax 32 2 663 06
30. gix 5000 project Do these steps to configure your controller s communication port 1 Access the controller s properties fe SLogix 5000 My_Modbus_Project 1756 L1 alsa a Hale 914 Properties age oases sat Stews me oy System E fl None 1 Gontinuous Barrier Using Logix5000 Controllers as Masters or Slaves on Modbus 17 3 If necessary configure the User Protocol tab Your controller s default Read Write Buffer Size 82 bytes If you expect to read and write more data than that in your RSLogix 5000 project increase this buffer size to accommodate your project F Controller Properties My_Modbus_Project Minor Faults Advanced SFCExecution Fie Memory A Click on the User Serera Hsen System Potoci User Protocol MajorFaults Protocol tab nee n 3 82 4 Bytes B Change the E H Bres Read Write Buffer Termination Character S7 En Append Character 1 sr 2 sr Size to accommodate your project 1_ SON X0FF I Echo Mode C Click OK Configure the New Controller Tags Once the new controller tags are copied into your RSLogix 5000 project you need to configure the tag described in Table 3 Table 3 This tag is configured once per Mod_Number_of_Instr project Mod_Commands x Enable command Mod_Commands x ScanNumber Mod_Commands x AddressOffsetinMaster Mod_Commands x SlaveAddress Mod_Commands x FunctionCode
31. grouped Axes E Mod_Data_Contacts1 EA Decimal INT 100 i Trends _ EMod_Data_InpReg3 iar Decimal INT 100 aa Se ce i _ Mod_DataHoldReg4 eS lt Decimal INT 100 E E Strings __ E Mod Node Address 10 Decimal SINT a5 P 50 Decimal DINT E Module Defined _ EMod_Range_Conti 100 Decimal DINT 5 6 1 0 Configuration E Mod_Range_InpReg3 100 Decimal DINT i De ES gt E Mod _RangeHoldReg4 100 Decimal DINT Enable the New Program Finally you must enable the new program before it will run To enable the new program you must change the Mod_Active controller tag to 1 By default this tag 0 so you can load the program using the steps described in this document to your RSLogix5000 project without the program starting Verify that Your RSLogix 5000 Project is Working Once you copy everything from the ModbusSlave ACD file into your RSLogix 5000 project monitor the controller s Main Task to make sure the Modbus_Slave program is returning data correctly To see how to monitor your project to make sure it is operating properly see page 32 Publication CIG AP129A EN P February 2004 32 Using Logix5000 Controllers as Masters or Slaves on Modbus Monitoring and Troubleshooting Your Modbus Project Publication CIG AP129A EN P February 2004 Whether you use a Logix5000 controller as a master or slave on Modbus you may want to monitor your program once you have implemented the solutions of
32. mands x ScanNumber INT Determines at which scan the slave Any value from 0 12 executes the command element For Default 12 example if you type a 3 in this tag the slave only executes this command element on scan 3 out of 10 This tag is only used if the Mod_Commands x Enable tag 2 If the Mod_Commands x Enable tag 0 or 1 this tag is ignored Mod_Commands x AddressOffsetin INT Sets a word level offset in the 0 No offset Master controller s data table when a read or write is executed Positive nonzero number Offset This value is added to the value of the Mod_Commands x Starting Address tag to determine where the master begins reading or writing data in its data table Mod_Commands x SlaveAddress INT Designates the node number of the 0 255 slave where the controller writes data to and reads data from Mod_Commands x FunctionCode INT Designates the function code of the Bit level function codes service commanded 01 Read Coil Status 02 Read Input Status 05 Write Single Coil 15 Write Multiple Coils Word level function codes 03 Read Holding Registers 04 Read Input Registers 06 Write Single Register 16 Write Multiple Registers For a full description of these function codes see Table 1 on page 3 Table 2 Tag name Mod_Commands x Starting Address Tag type INT Using Logix5000 Controllers as Masters or Slaves on Modbus 13 Description This value is added to the address offset i e
33. nel Extranet e Vendor Sample Project PDF Access the PDF via the Help menu in RSLogix 5000 3 Open your RSLogix 5000 project in a second instance of RSLogix 5000 4 Copy the following user defined data types UDTs e Mod_Command_Structure e Mod_Status from the ModbusMaster ACD file You can only copy one UDT at a time so repeat the process below for the second UDT E RSLogix 5000 Modbus_Master in ModbusMaster ACD 17 File Edit View Search Logic Communications Tools Window alsa S Hee oo es Noe Blea BEIE J Controller Modbus_Master Controller Tags E Controller Fault Handler Power Up Handler 5 8 Tasks 6 ModTask Modbus_Interface Unscheduled Programs Motion Groups Ungrouped Axes l Trends Si Data Types A Open the User Defined Data Types folder B Right click on the first UDT E Strings Cp Predefined rE Module Defined I O Configuration C Click Copy Delete Monitor Tags Cross Reference Ctrl E Print gt Properties Publication CIG AP129A EN P February 2004 Using Logix5000 Controllers as Masters or Slaves on Modbus 7 A Right click on the User Defined Data Types folder 5 Paste the UDT into your RSLogix 5000 project S RSLogix 5000 My_Modbus_project 1756 L63 File Edit View Search Logic Communications Too alsa S e o T Offline 0 E RUN LA F
34. ny of the values you receive in your project Connect Logix5000 Controller to RS485 Network Via 1761 NETAIC Use the AIC Advanced Interface Converter 1761 NET AIC to connect your Logix5000 controller to the RS485 network For more information on how to use the 1761 NET AIC converter see the following publications e Advanced Interface Converter AIC Installation Instructions publication 1761 IN002 e Advanced Interface Converter AIC User Manual publication 1761 6 4 You can view download or order these publications from http www theautomationbookstore com Sample Files in RSLogix 5000 v13 Format The RSLogix 5000 project files associated with this solution use RSLogix 5000 version 13 To use these files with an RSLogix 5000 version previous to 13 you must use the Import Export function We recommend you use this solution with RSLogix 5000 version 13 or greater Remember your Logix5000 controller must use a firmware revision that matches the RSLogix 5000 version i e we recommend you upgrade your Logix5000 controller to firmware revision 13 x or greater to use this solution Using this Application Solution Using Logix5000 Controllers as Masters on Modbus Using Logix5000 Controllers as Masters or Slaves on Modbus 5 There are two parts to this solution This section Uses this RSLogix 5000 project Begins on Using Logix5000 Controllers as ModbusMaster ACD page 5 Masters on Modbus Using Logix5000 C
35. ontrollers as ModbusSlave ACD page 22 Slaves on Modbus The ACD files give you e controller tags e periodic tasks e user defined data types Gin the ModbusMaster ACD file only that you can copy into your RSLogix 5000 project to communicate with the Logix5000 controllers via Modbus RTU function codes e g Read Coil Status The ModbusMaster ACD file helps you use a Logix5000 controller as a master on Modbus The ACD file contains e 11 controller tags e 1 periodic task e 2 user defined data types You must do the following tasks to use an Logix5000 controller as a master on Modbus 1 Copy User Defined Data Types From the ModbusMaster ACD File to Your RSLogix 5000 Project 2 Copy Controller Tags From the ModbusMaster ACD File to Your RSLogix 5000 Project 3 Copy ModTask From the ModbusMaster ACD File to Your RSLogix 5000 Project 4 Configure the Controllers Communication Port 5 Configure the New Controller Tags 6 Enable the New Program 7 Verify that Your RSLogix 5000 Project is Working Publication CIG AP129A EN P February 2004 6 Using Logix5000 Controllers as Masters or Slaves on Modbus Copy User Defined Data Types From the ModbusMaster ACD File to Your RSLogix 5000 Project Do the following steps 1 Start RSLogix 5000 2 Open the ModbusMaster ACD file The ACD file is available at either of the following locations e Allen Bradley Channel Extranet Download the file from the United States Chan
36. re packed as one input per bit of the data field 0 OFF 1 0N 05 Write Single Coil This function code is used to write a single output to either ON or OFF in a remote device 0 OFF 1 0N 15 Write Multiple Coils This function code is used to force each coil in a sequence of coils to either ON or OFF in a remote device 0 OFF 1 0N 03 Read Holding Registers Word 16 bit This function code is used to read the contents of a contiguous block level of holding registers in a remote device 04 Read Input Registers This function code is used to read from 1 up to 120 contiguous input registers in a remote device 06 Write Single Register This function code is used to write a single holding register in a remote device 16 Write Multiple Registers This function code is used to write from 1 up to 120 contiguous registers in a remote device IMPORTANT This solution only supports Modbus RTU transmission mode Modbus ASCII transmission mode is not supported The Modbus protocol specification is available at http www modbus org Publication CIG AP129A EN P February 2004 4 Using Logix5000 Controllers as Masters or Slaves on Modbus Publication CIG AP129A EN P February 2004 Automatic Conversion of Little Endian Data to Big Endian Data The solution automatically converts data from the format used on Modbus format i e little endian to the format used with Logix5000 controllers i e big endian You do not need to convert a
37. rollers as Masters or Slaves on Modbus 33 Use Program Tags With both the ModbusMaster and ModbusSlave portions of this solution you copied periodic tasks to your RSLogix 5000 project Each task contains Program Tags that allow you to monitor your project s performance The Program Tags are located in either e the Modbus Interface program for the Modbus Master file or e the Modbus Slave program for the Modbus Slave file To use the Program Tags do these steps A Open the newly copied periodic task and program B Right click Program Tags C Click Monitor Tags TIP Before monitoring the data for a particular command element you may want to set the Mod_Commands x Enable tag for that command element 3 With this value the command only executes one time instead of repeatedly and you can monitor static However if you want to monitor dynamic data to verify that any changes are occurring correctly use 1 or 2 in the Mod_Commands x Enable tag 1 Access the Program Tags This example shows how to access the tags in the ModbusMaster file f RSLogix 5000 My_Modbus_project in Modbu File Edit View Search Logic Communications To alsa S ele ool Offline f RUN NoFoces p T OK p fora eH mi B Controller My_Modbus_project Controller Tags Controller Fault Handler G Power Up Handler Tasks a D MainTask E amp Modbus_Interface r M New
38. t were configured for the example on page 19 The command is always enabled Mod_Commands 0 Enable 1 The command was successfully executed The controller automatically fills in this number when the command is executed successfully Mod_Commands 0 EchoReceived 1 The address offset in the master data table is 2 words Mod_Commands 0 AddressOffsetinMaster 2 The slave node address is 4 Mod_Commands 0 SlaveAddress 4 Coil data is read from the slave Mod_Commands 0 FunctionCode 1 4 bits bits because the function code is a bit level code are added to the address offset in the master data table Mod_Commands 0 StartingAddress 4 32 bits of data are read from the slave and written to the master data table Mod_Commands 0 Enable 32 RSLogix 5000 My_Modbus_project 1756 L63 Controller Tags My_Modbus_project controller Fil dit View Search Logic Communications Tools Window Help alama sale olol S 30 5 ie E Ale No Forces _P e Y 7 eee NoEdts Dy Pa a elea e Redundancy Set 4 gt Favorites Abit X Timer Counter Fi Input Output X Compare Controller My_Modbus_project Scope Hdy_Modbus_project Y Show Show All had Sot Tas Controller Tags TNSE al Vale elf amp g L User Defined Powerh Tasks E MainTask G E MainProgram
39. tab highlight the number in the tag type field f RSLogix 5000 My_Modbus_slave_project 1756 L63 File Edit View Search Logic Communications Tools Window Help alata ga J sisle T ve alel Offfine 0 ERUN A e NoForces OK Moeis 8 pe a Hlal Redundancy 59 Dy of Favorites 3 Controller My_Modbus_slave_proje A Controller Tags Controller Fault Handler Gi Power Up Handler i Tasks f AB 1756_Al6 Flo B MainTask i AB 1756_AI6_CJ_ MainProgram AB 1756_Al6 Flo 5 ModTask AENA Local ABA756_AIG Flo Oi rechecked Pregas Mod Active BOOL Decimal Shed Batata Dim Decima E Ungrouped Axes E Mod_Data_Contacts1 INTO Decimal E Trends E Mod Data_InpReg3 INTIVOO Decimal ea Papen EMod_DataHoldReg4 INT T00 Decimal ig sen F Mod Node Address SINT Decimal Gh Predefined C EMod Range _Cois0 DINT Decimal ER Module Defined C E Mod Range_Contt DINT Decimal i 1 43 Yo Configuration IT E Mod_Fange_InpReg3 DINT Decimal i u ei T E Mod_RangeHoldReg4 DINT Decimal 2 Type the new size Publication CIG AP129A EN P February 2004 30 Using Logix5000 Controllers as Masters or Slaves on Modbus 3 Press the Enter key to see the new size reflected in the tag RSLogix 5000 My_M roject 1756 L63 a Eafe e oa 0 BY oes New tag size
40. ter ACD file File Edit Yiew Search Logic Communications 1 alsa S ale oll Offline D E RUN d NoForces gt No Edits a 5 Controller Modbus_Master A Controller Tags Controller Fault Handler Power Up Handler E A ey New Program Unsche y 2 3 Motion Gror 2 Ctrl x Ctrl Delete Del Gi Data Types Cross Reference Ctri E B Mo E Strings Properties A Right click on Task B Click Paste A Right click on Modbus_Interface B Click Copy A Right click on ModTask B Click Paste Using Logix5000 Controllers as Masters or Slaves on Modbus 15 2 Paste the ModTask task into your RSLogix 5000 project ff RSLogix 5000 My Modbus_Proj File Edit View Search Logic Comr Als a e lt Offline D E RUN No Forces py OK No Edits Controller My_Modbus_Project Controller Tags Controller Fault Handler 3 Power Up Handler M New Task aot Bony Gils Bite 3 Copy the Modbus_Interface program from the ModbusMaster ACD file RSLogix 5000 Modbus Master in ModbusMaster ACD 1756 L1 File Edit View Search Logic Communications Tools Window Help alsa a s alejo jT g a i co No Forces bo Eo No Edits aye a eee Bel E LH revortes KK eT E E Controller Modbus _Master Controller Tags Controller Fault Handler Power Up Handler
41. troller Tags Controller Fault Handler A Right click on Modbus_lInterface B Click Copy 2 leet Op Predefined Gig Module Defined 5 8 1 0 Configuration 8 1756 04161 ov o gt BJ 9 175644161 inp 4 Paste the Modbus_Slave program into your RSLogix 5000 project A Controller Tags ontroller Fault Handler Power Up Handler MainTask MainProgram A Right click on ModTask B Click Paste Publication CIG AP129A EN P February 2004 Tag size highlighted Using Logix5000 Controllers as Masters or Slaves on Modbus 29 Configure New Controller Tag Sizes The Modbus Data Register tags i e Mod_Data_Coils0 Mod_Data_Contacts1 Mod_Data_HoldReg4 and Mod_Data_InpReg3 use a default size 100 words If you need to increase the tag sizes you can However if you increase the size of the Modbus Data Register tags you must also change the size of the corresponding Modbus Register Range tags that monitor them Table 5 explains which Modbus Data Register Range tags must be changed to accommodate new sizes in the Modbus Data Register tags Table 5 If you change the size of this tag Mod_Data_Coils0 Mod_Data_Contacts1 Mod_Data_InpReg3 Mod_Data_HoldReg4 You must change the size of this tag Mod_Range_Coils0 Mod_Range_Contacts1 Mod_Range_InpReg3 Mod_Range_HoldReg4 To change the Modbus Data Register tags size do the following steps 1 On the Edit Tags
Download Pdf Manuals
Related Search