Modbus Host User Program User Manual
Contents
1. da 2 6 Ko SE Qa vd B 1 WWW modico OP po udi uiia 1 1 Modbus Host User Program User Manual If you have comments or questions regarding this manual please direct them to your local sales representative or contact Emerson Process Management Flow Computer Division Marshalltown IA 50158 U S A Houston TX 77065 U S A Pickering North Yorkshire UK YO18 7JA Website www EmersonProcess com flow 4 Index Rev 01 032. 1 1 1 2 ee 2 10 Prva 1 2 POramefet or 2 Parameter h n Aase 2 9 Parameter eie A 2 Point HETE open Pond oid 2 0 Point or Logical Number a ceteros A 2 Pont T dori ac a 2 8 Po Py Pes banana ee 1 2 1 Damned sr 1 Poll Hr ES atu ete atte 2 4 Program Versions and Names a siete 1 4 Protocol User 1 1 A 1 H Raw 2 4 2 5 RMN A 2 KN 2 12 Register Number Address Span KE 2 7 REG USS ES Cd 2 7 Response FREE HORDE prs 2 15 ROC ICTU eS 1 5 ROC Protocol User Manual 1 1 A 1 ROCLINK 800 Configuration Software User Manual O Ma 1 1 2 10 M Bec AN 2 3 asini 2 2 2 12 RITUAUS S 2 2 S DAWG AER 2 12 1 1 Rev 01 03 Modbus Host User Program User Manual SEND diede tudes toa etu quta 2 5 SM AMES sss edis ue na mas 2 16 ET ME EN 2 5 A 2 Vinh T m 1 2 Host Configuration Display 2 12 SPOT 2 9 2 11 2 12 Ve 2 7 SE 2 2 2 13 T Table 1 1 Modbus Function Codes 1 3 Table 1 2 Versions and Program Names 1 4 Ta
3. adr EUM UE 2 0 Poser 2 9 nu 2 4 Nav A 2 liio EE aan 2 5 Inte gere 2 5 HAAAY 2 4 Integer to Float CONVEN ONS EE 3 2 INTE SOUS H 2 L 2 E 2 8 2 9 AA AA 2 5 LO Integer aaa aaa aba 2 4 EO EA DE 2 4 habei tees 1 2 2 8 A 2 Low Reading EU saoudite dio sk 2 4 M N Manuals epe x 1 1 Memory 7586626 1 4 Message ETEOLS Sos 2 15 NA do 2 5 Modbus Compa DIE ace oser 1 3 INOS NANA NANANA AA 2 10 M dbu us C ODIT N 2 3 Modbus Configuration 2 1 2 Modbus Configuration Display on iiit vat dott Gas 2 5 Low Float Sale babe 2 5 Modbis aua iod audien Er Qu 2 6 Modem Hayes AT Command Seta usce mitto es 2 2 Response preceded by modem commands 3 2 RU NS 2 2 2 2 IModus ONLI CUTAUON E 2 3 Modus Mode usua OI 2 1 ILI PE 2 4 IG V tton
4. 2 Figure 2 2 Modbus Configuration 2 3 Figure 2 3 Modbus 2 7 Figure 2 4 Modbus 4 42222222 2 11 PAGE pP n 1 5 Fork ou cibis mt clo Hoe Poo dub Dora 2 5 SCAN 2 9 Float to THOSE 2 9 loans em 2 FloBoss 103 How Manager Instruction Manual 1 1 Ad 2 2 oo stets A 2 Eno NUBT EN 2 12 2 16 Program Re Sisters 2 10 Punction Code DI 2 4 ENnctlon aan 1 3 2 12 Modbus Host User Program User Manual G Gettin Started odo base E 1 1 Gould Modbus Protocol Reference Guide 1 1 1 3 H Hayes AT Command 5 0 2 2 HE FIG at cioe a iube 2 5 HI neser Scale riec 2 4 Reading EU vs 2 4 stad darem e UE 1 2 ContIe EQUO ELE SERENE 2 10 Configuration Requests and Commands 2 10 C A o t e 2 4 2 10 Host Configuration Display FANG Soie LE 2 12 a 2 12 Host Slave BEE fon usted 1 3 EEE Form l 2 Indexing Parameter teas siete OR
5. User Programe Installed in ROC User Program and Version Modbus Host COM 1 00 Code Start Addr End Addr FFFFF User Comm Pam 3 COM Data Start Addr 47C000 End Addr 47EFFF Status ON segment 12345 6 9 1011 12 13 14 15 16 17 18 19 20 Code 0790000 000000 Data 460000 0000000000000000 Unused Used Used by Selected Program Download User Program File Code Start Segment Start Segment Segments Segments Status Download Close Figure 1 1 User Programs 3 Determine the Memory Usage The memory location must be available for the specific user program that you are loading 1 4 Getting Started Rev 01 03 Modbus Host User Program User Manual 4 Click Browse and select the user program file to download from the CD ROM Program files are typically located in the Program Files folder The Open File dialog displays the names of all the files that have the BIN extension 5 Select the File name you desire to load and click Open Refer to Table on page 1 4 6 Click Download to download the selected user program Only install one user program 7 Select the user program in the User Program Installed 1n ROC field click Enable The Status field displays ON or OFF indicating the Status of the user program 8 Select System Flags Refer to Figure 1 2 ROC Flags General Advanced Res
6. or Parameter Param 5 Aresponse message containing the data requested an error message 15 then sent back to the Host When the data response message 15 returned the data collected from the Slave 15 stored beginning at the register defined in the Save field of the Modbus Host configuration screen When configuring the table register numbers Start through End Addr and table names Tag ID should be unique Register numbers may be duplicated as long as they are located in a separate Modbus Function configuration table For example The Start register 500 may appear in Function table Tag ID Funct 1 and Function table Tag ID Funct 2 If a register number 1s duplicated within the same Modbus Function table the first occurrence will be used It is best to number the tables from the smallest register number to largest especially when using two table entries to configure a continuous group of register numbers Up to thirty different requests can be configured for Modbus Functions 3 4 and 16 three displays of ten register number ranges By making the register numbers continuous meaning the Start address of a new line 1s one greater than the End Addr end address of the previous line a continuous data table can be created up to the limit of 240 bytes This type of data table allows access to all data with one request 2 6 Modbus Configuration Rev 01 03 Modbus Host User Program User Manual Up to ten different requests can
7. 0 HiFbatSede5 n Input Data Start inn LO Float Scale 5 Output Data Start ann HI Float Scale 5 HI Integer Scale 4095 Flaat Scale LOW Integer Scale Float Scale HIFloatScalet D LOFloatScale7 0 LO Flo Scaleo HI Float 8 0 LO FloatScae 00000 Enable D ebug fa 2 Update OK x Cancel Apply Figure 2 2 Modbus Configuration Point Number indicates the Host communications port being configured and is dependent upon which user program is installed 2 Enter the transmission format as ASCII 0 or RTU 1 The data link can operate in the RTU Remote Terminal Unit mode or the ASCII American Standard Code for Information Interchange mode All devices in the same communications network must be configured with the same mode of transmission RTU mode allows for greater character density and better data throughput than ASCII for the same baud rate Each message 15 transmitted in a continuous stream Data 15 sent in 8 bit binary characters RTU mode uses Cyclic Redundancy Check CRC error checking By default RTU 1s enabled ASCII mode represents each 8 bit byte of data as two ASCII characters that are the hexadecimal representation of the value This allows the messages to be read with the use of a dumb terminal but uses twice as many characters as the RTU mode Each character sent 1s composed of a Start bit 7 or 8 Data bits and
8. 03 Modbus Host User Program User Manual Modbus Function Configuration Worksheet Starting Ending Point Tvne Logical Parameter Conversion Register Register Number Number Code Rev 01 03 Configuration Worksheets B 3 Modbus Host User Program User Manual Modbus Function Configuration Worksheet Starting Ending Point Logical Parameter Conversion Register Register Number Number Code B 4 Configuration Worksheets Rev 01 03 Modbus Host User Program User Manual INDEX RENN 2 13 Extensions BIN 1 5 inp 1 4 2 Aes 2 2 2 4 ERE 2 8 NES SR 2 7 ANETTE sut unu 2 4 2 5 Analog I O Raw Values Dest ie ce us 2 5 ANG AA 2 3 Gs Tt 2 DN 2 Bilt ASSEN chos Doe et A 2 PN A 2 ANN 1 2 2 6 2 12 tanta ocu DE 2 4 C Communications Parameters 3 1 COT ALO NTL assess rears ya ents 1 3 CONC 2 6 Connect Command 2 2 COMUMUOUS as scd sso tae dora er 2 4 CONV Rose tuo vela
9. 1 Saws 0 0 0 1 RO UNTS 1 ModemType gt 4 RW UNTS 1 3rdRTUAddr gt 6 RW UNT8 1 SthRTU Addr 8 RW AC 30 IstComneetCommand ___9 RW AC 30 2ndConneetCommand Table A 4 Modbus Configuration Modbus Config Point Types 27 LOI 34 COM2 and 37 COM1 0 RW UNT8 1 ASCH ORTU 1 RW UNT8 1 ByteOrder1 MSBlst 3 RW UNT8 1 HosAcive Acive 4 RW UNT8 1 ContinuousPolll Yes 6 RW UINT8 1 Table Stare gt 8 RW UINT16 2 _ Output Data Start 9 RW UN6 2 _ Hil Integer Seale Rev 01 03 Point Types A 3 Modbus Host User Program User Manual Modbus Config Point Types 27 LOI 34 COM2 and 37 COM1 M RW HP 4 LOFoatSeae2 1 RW HP 4 HIFloatSeale3 gt 16 RW HP 4 JjLOFlaScle3 Table A 5 Modbus Functions Modbus Functions Point Types 28 LOL 35 COM2 and 38 1 0 RW AC 10 Function Tag Identification 4 f mw une lise 2 RW UNTIG 2 EndAdd gt 3 4 5 UINTS 1 Param 00000 UINT8 1 gt A 4 Point Types Rev 01 03 3 RW bd Hap 5 RW 6 RW __7 RW gt 8 RW 9 RW UNS 1 005 10 RW n RW 2 RW 3 RW M RW gt 15 RW 16 gt Modbus Host User Program User Manual Modbus Functions Po
10. Address can have values between 1 and 255 When attempting to dial the RTU Address specified in the Modbus Host request 15 compared to the RTU Address 1n Modem control screen and determines the Connect Command to execute The RTU Address 15 then matched with the FloBoss Address ROC Information If the Host RTU Address matches the Modem RTU Address the Connect Command 15 used to connect to the modem at the FloBoss Address that 1s the same as the RTU Addresses If the Host RTU Address does not match any configured Modem RTU Address fields the first Connect Command 15 used Enter the Connect Command telephone number to be sent to the Slave device Modem configuration is based upon the Hayes AT command set NOTE Consult your modem s user manual for the valid AT command set otherwise the modem may not operate as intended Modbus Configuration Rev 01 03 Modbus Host User Program User Manual 2 2 Modbus Configuration Use the Modus Configuration screen to set up Modbus parameters Configure both Host and Slave devices to have similarly configured parameters 1 Select Configure User Data Modbus Config Refer to Figure Point Number MM eet RTU 1 NN HlFloatSeale2 0 Byte Order 1 MSB 1st I LOFloatScale2fl Log Enable 1 Enabled 0 HiFbatSede3 n Host Active T2 ctive jo LO Float Scale 3 p Continous Poll pes fo HI Float Scale 4 Poll Timer in 0 LOFlatScde 4 n Table Start
11. be configured for Modbus Function Codes 1 2 5 6 and 15 For Function Codes 1 2 5 and 15 the parameter specified should be a single byte parameter type preferably a Status parameter Each address span Start through End Addr must be unique within the Function Code for proper operation If not the first valid address is used in the Type field disables that Function Code NOTE When you specify a reference to a Parameter within another Point Type you must interpret the information returned on the display for example SPT 3 DATA2 in the following manner The first part is a three character mnemonic in this example SPT means Softpoint that indicates the Point Type The second part such as 37 indicates the Point Number but keep in mind that for all point types except points you need to add 1 to the displayed Point Number to get the actual Point Number for example 3 I 2 4 The third part is a mnemonic indicating the selected Parameter such as DATA2 To configure Modbus Functions 1 Select Configure User Data Modbus Funct Refer to Figure Modbus Funct COM Point Number MM TAG ID FUNCT 1 1 Start End Addr fo fo o fo Conv fo 2 Start fo End Addr fo Type jo Lgl Faram fo Conv fo 3 Start fo _ End Addr fo fo o o Conv fo 4 Start fo End Addr fo Type jo Lgl fo Param fo Conv fo 5 Start fo _ End Addr fo fo Lol
12. can also send commands to set outputs and to write data to a Slave device The Modbus Host mode is enabled by the Host Active field on the Modbus Config configuration display as in Figure 2 2 By default Host Active is always enabled The Host Active field 1 1s what initiates a host transmission Refer to Sending a Message on page Each Modbus Host configuration screen has a direct correlation to each Modbus Function screen For example Modbus Host COMI corresponds to Modbus Funct COMI of the Slave and Modbus Host 2 corresponds to Modbus Funct 2 of the Slave Up to forty different Host requests or commands can be configured for a communications COM port Each request or command can transmit or receive up to 240 bytes of data at NOTE Each Host request configured must have a corresponding entry in the Modbus Functions configuration table 2 10 Modbus Configuration Rev 01 03 Modbus Host User Program User Manual When a Host polls a FloBoss The Host sends the message to the FloBoss Address ROC Information screen with the The Host tells the FloBoss to perform the Function Code request or command entered in the The Function Code request or command is performed on the data register starting at the data If a Slave with a matching address RTU Addr FloBoss Address and the register numbers are valid Start gt Reg through End Addr lt Regs the Slave device performs the request or command for all data register
13. indexing When the Host requests a valid range of register numbers the Function Code tells the Slave what to do and between which registers Start through End Addr The Type Logical Number Lgl and Param fields define what data 15 collected or to what value to set the register numbers For example Point Type 14 represents the Communication Ports To set the Retry Counter to a higher value you would select Type 14 and Parameter 13 Param 13 Be aware of the different data types Character Integer Long Float and the size of the data types See Appendix A for the complete list of the ROC Point Types and Parameters 7 Enter the Conv field to specify the type of conversion required if any on the data before it is sent to the Host or before it 1s written to the FloBoss The conversions are used to allow integer values and floating point values to be converted transmitted and received Convert Codes reorganize the data bits into a specific order the Host Slave or ROC can understand Refer to the ROCLINK 800 Configuration Software User Manual Form A6121 concerning Convert Codes used with the Modbus Protocol user program The Function Codes supported display under the Slave and Host columns 2 4 Modbus Host Modbus Host mode of operation allows the FloBoss to simulate a Host device that can poll other Slave devices for data and to store the data for parameter updates for use in FST program registers and for user programs The FloBoss
14. one or two Stop bits with Even Odd or No parity ASCII mode uses Longitudinal Redundancy Checking LRC error checking In either mode ASCII or RTU a Modbus message 15 placed by the transmitting device into a frame that has a known beginning and ending point Rev 01 03 Modbus Configuration 2 3 Modbus Host User Program User Manual ASCII Message Framing Begin of Frame LRC Error Check mr 2 Characters 2 Characters N Characters 2 Characters CRLF RTU Message Framing Begin of Frame CRC Error Check T1 T2 T3 14 1 Byte 1 Byte N 1 Byte 2 Bytes T1 T2 T3 14 2 4 Enter the Byte Order of data bytes in a message transmission or request This only affects the Data field of a Modbus message and has no effect on data for Function Codes 01 02 and 05 Least Significant Byte First 0 Places the Least Significant Byte first Most Significant Byte First 1 Places the Most Significant Byte first Enter 1 in the Log Enable field to log all parameter changes made via Modbus to the Event Log Enter 1 in the Host Active field to initiate a transmission The Host Active Flag remains set while the transmission 15 in progress and then clears 0 If the Continuous Poll 15 set the Host Active flag remains set 1 Enter 1 in the Continuous Poll field to activate polling of the Slave devices If the Continuous Poll 15 set the Host Active flag remains set 1 Enter a value in seconds in the Poll Timer in Sec field to configure for h
15. x Adjusted Reading LO Integer Scale Float Range The equations used to convert integers to floating point values are Float Range HI Float Scale LO Float Scale Integer Range HI Integer Scale LO Integer Scale Adjusted Integer Integer Sent LO Integer Scale Float Value Adjusted Integer x Float Range LO Float Scale Integer Range The HI Float Scale and LO Float Scale values are also used as high and low deadband limits when Convert Code 49 through 56 is selected Refer to the Modbus Functions on page 2 6 Enter in the Enable Debug field to enable debugging of Modbus communications When an LCD liquid crystal display is installed the debug messages appear on the LCD The top line of the LCD indicates which Modbus RTU Address is currently being polled The bottom line indicates the action that the user program is performing SEND FloBoss is sending a Modbus message to the device Address displayed on the top line RCVED FloBoss has received a valid response from the device RTU Address displayed on the top line TOMSG FloBoss timed out waiting for a response from the device Address displayed on the top line Rev 01 03 Modbus Configuration 2 5 Modbus Host User Program User Manual The bottom line also indicates connection states when using an External or Internal modem e CONC FloBoss is attempting to establish a connection with the remote device WAITC FloBoss is waiting for a connec
16. 2 5 tub 2 10 Conversions INTC ger 3 2 D Data Lik 1 3 Data Bytes Upper L n 1 3 Data TY 2 Data AA 1 BED FE SEE AN 3 2 DEP ON PO 2 Dial Up Modem Communications Card 1 3 Rev 01 03 DISC 2 6 DOW MOA 1 5 Downloading the User Program 1 4 DSR o ne 3 2 E PFIN SANAE 1 3 Enable PE es 2 5 WANG NA 2 8 End Add AA 2 8 Error Codes OG ET SEE EE 2 15 Vu 2 15 DN 2 15 Errors Exception Response rri dirae teret pecu ains 2 15 FloBoss appends charater to message 3 FloBoss does not respond in point to multi point COMMS V SIG ED 3 FloBoss responds with wrong data 3 MESSE Ne TP 3 Example WOIKSNEE UT 1 Exception RESPONSE 2 15 Extensions BIN rm 1 5 e AA AA 1 4 Figure 1 1 User Programs rrrnnnnnnnnnnnnnnnnnnnnnvrvvnnnnnnn 1 4 io te PEE eed 1 5 Figure 2 1 Modbus
17. Form A6137 Part Number D301183X012 January 2003 Modbus Host User Program for FloBoss 103 Flow Managers User Manual Flow Computer Division EMERSON um RH A EY E55 ILI arai Ek ET nt Website www EmersonProcess com flow Process Management Modbus Host User Program User Manual Revision Tracking Sheet January 2003 This manual 15 periodically altered to incorporate new or updated information The date revision level of each page 15 indicated at the bottom of the page opposite the page number A major change in the content of the manual also changes the date of the manual which appears on the front cover Listed below 15 the date revision level of each page Page Revision All Pages 01 03 FloBoss and ROCLINK are marks of one of the Emerson Process Management companies The Emerson logo is a trademark and service mark of Emerson Electric Co All other marks are the property of their respective owners Fisher Controls International LLC 2003 All rights reserved Printed in the U S A While this information is presented in good faith and believed to be accurate Fisher Controls does not guarantee satisfactory results from reliance upon such information Nothing contained herein is to be construed as a warranty or guarantee express or implied regarding the performance merchantability fitness or any other matter with respect to the products nor as a recommendation to use any product or process in co
18. Operator Interface LOI Local Port or remotely via modems using the Comm ports The Slave 15 built in to the FloBoss 103 firmware Refer to the ROCLINK 800 Configuration Software User Manual Form A6121 Modbus allows a FloBoss 103 Host to access and request information from the Slave device You may also tell the FloBoss to perform an action such as changing the Status of a Discrete Output coil from OFF to ON Depending on the Host request the Slave FloBoss or other device may or may not return message Modbus is capable of sending a request to all devices attached to the communications network This type of mass request is called a Broadcast Only one Host device may poll for data while the other Slave devices respond to the message sent by the Host If the Modbus Host is running it cannot function as a Slave device at the same time on the same communication port The Modbus Host must be turned off before it can act as a Slave device However the Slave operation will work on any other communications port on which the Modbus Host is not active The Modbus Host requires the following to perform a request or action e Address Location Address of the Modbus Slave device such as a FloBoss to be polled ROC Information Each Modbus Slave has a unique Address Function Code Informs the FloBoss of the action or request to perform Data Any additional data required by the FloBoss to perform the action or request specified by
19. Program User Manual 2 4 1 Exception Response When a Host sends a message to a Slave it expects a normal return response message Broadcast mode is exempt from return response messages The following may occur The Slave device receives the message processes the action without error and returns a normal return response message The Slave receives the message but interprets a communications error in Parity LRC or CRC and does return a response message The Host times out The Slave does not receive the message due to a communications error and does not return a response message The Host times out The Slave receives the message without communications errors but is unable to process the message such as the request to preset a coil that does not exist the Slave returns a response message called an exception response indicating the cause of the error When a normal return response message 15 returned the Function Code echoes the Function Code included with the initial Host to Slave message Function Codes have a most significant bit MSB of 0 with values below 80 hexadecimal The Exception Response message 15 transmitted if the FloBoss detects an error in the received message and causes the return response message Function Code field to be Enabled This causes the Function Code value in an exception response to 80 hexadecimal thus indicating an error Refer to Table The received Function Code returns with the most significant bi
20. a valid Slave response was received and processed 128 Write ROC date error An error occurred when writing the data into the Point Type Logical Number and Parameter Number TLP database 129 Access FloBoss data error An error occurred when reading date from the FloBoss TLP database 130 Host function table error The line in the Host table request does not match the corresponding function table configuration Transmit timeout error The FloBoss was unable to transmit the Host request message This would indicate a missing communication card a communication card failure or a lockup problem which requires a power cycle to clear 131 144 Transmit or receive buffer overflow The message to be sent or received is too long Either too many registers are configured in the request message or the resulting response is too large 145 Invalid Function Number in request The line in the Host table is configured with an invalid Modbus Function Number Valid Function Numbers are 1 2 3 4 5 6 15 and 16 Status values and 2 through 8 are active on the Host transmission These values appear for a very short period and then step to the next value if the process 1s without error If an error occurs in the step the value is present until the next transmission 15 requested A transmission without error has a Status value of 8 Refer to Section Exception Response on page 2 15 2 14 Modbus Configuration Rev 01 03 Modbus Host User
21. arameter 17 of Analog Inputs Type 3 starting at the first Analog Input Lgl 0 1 So register 100 Parameter 17 of AI Point Number 1 register 101 Parameter 17 of AI Point Number 2 and register 106 Parameter 17 of Point Number 7 Another example of point indexing uses the configuration of Start 120 End Addr 120 Type 17 14 Param 5 Conv 0 Specifies one value Start 120 through End Addr 120 for Parameter 5 of a Soft Point Type 17 starting at the fifteenth Soft Point Lgl 1441 So register 120 Parameter 5 of Soft Point 15 Parameter Indexing Parameter indexing 15 used to increment the Parameter within the Point Type Indexing of parameters can also be selected by offsetting the Logical Number by 128 When using parameter indexing Logical Number Lgl 128 For example when using vertical indexing the configuration of Start 109 End Addr 114 Type 16 128 Param 2 Conv Specifies six parameters 109 through 114 for FST number 1 LGL 0 128 starting at Parameter 2 So register 109 Parameter 2 of FST Point Number register 110 Parameter 3 of FST Point Number 1 register 111 Parameter 4 of FST Point Number 1 and register 114 Parameter 7 of FST Point Number 1 Conversion Conv 1 Code 1 Float to integer Float Scale 1 15 used to convert the floating point value to an integer before the response message 15 returned to the Host For another example of parameter indexing the config
22. ble 2 1 Valid Host Register Numbers 2 8 Table 2 2 Status of Host Request or Command 2 14 Table 2 3 ROC Exception Response Example Message AAO 2 15 Table 2 4 Modbus Protocol Errors that Elicit an Exception Response 2 15 Table A 1 Point Types and Descriptions 1 Table A 2 Data TYDE iust ido ests A 2 Table 3 Modbus Modem A 3 Table 4 Modbus A 3 Table 5 Modbus 4 Table 6 Modbus A 6 Table to Eo pou A 2 dpi ec m 2 4 Rev 01 03 Index o cts Cota isa ee eaae ute 2 7 2 11 FEP NUM A 2 BOX SELCO aint d 1 2 IMOG Bian pt d ete 2 6 TOMS GG idt eR a dosi c bac M FEE bees kede 2 5 Troubleshooting FOR OCC s iere ne 2 15 p T 2 8 2 U PP TTE A COIN Em A 2 Unstened Be PET et tide Roa EL Ra bL A 2 User Defined Point Types 1 User Pro CLAIMS 1 4 1 4 V icit oe bct NAA 1 4 W Z S amen eee mer
23. ev 01 03 Modbus Host User Program User Manual APPENDIX A POINT TYPES 1 Point Types and Data Types This appendix details Point Types Table A 1 Data Types Table A 2 and User Defined Point Types for the Modbus Host user program display in Table A 3 through Table A 6 A 1 1 User Defined Point Types User Defined Point Types UDP are available in FloBoss units UDPs enable configuration data to be available to ROCLINK 800 The Modbus program for reserves UDPs for the following communication ports ROC Comm Ports Local Port LOI UDP 26 UDP 27 UDP 28 and UDP 29 COMI Port UDP 33 UDP 37 UDP 38 and UDP 39 2 Port UDP 32 UDP 34 UDP 35 and UDP 36 For standard Point Types refer to ROC Protocol User Manual Form A4199 Table A 1 Point Types and Descriptions 0 Configurable Opcode 34 Modbus Host User Program COM2 _ 8 History Parameters 1 4 Run Parameters 38 ModbusHostUserProgram COM 86 Extended History Parameters ____ Rev 01 03 Point Types A 1 Modbus Host User Program User Manual Table A 2 Data Type NT Sioned Integer number of bits follows 8m toot UINT Unsigned Integer number of bits follows FLP Floating Point IEEE Format TLP Type Point or Logical Number Parameter Number 1 2 Bit Assignments This section displays an example bit assignment used in Binary and Unsigned Integer bytes All bytes proceed fro
24. evice from which registers the data will be polled and any conversion required Refer to Section Modbus Functions on page 2 6 3 Configure the ROC Comm Ports parameters Refer to ROCLINK 800 Configuration Software User Manual Form A6121 4 Configure the Modbus Modem parameters Refer to Section Modbus Modem on page 2 1 5 Set Host Active to 1 in the Modbus Config screen to enable Host communications Refer to Section Modbus Configuration on page 2 3 6 Set Continuous Poll to in the Modbus Config screen 7 Set the Poll Time value to the desired polling frequency in seconds 8 Click Apply The message is sent beginning with the Request Number set in the Starting Register ROCLINK 800 Subsequent Request Numbers are transmitted until a Function Number of 0 1s encountered or the last Request Number 39 has been transmitted If Continuous Polling ROCLINK 800 15 Enabled the Host waits the amount of time specified and starts the transmission sequence over again 2 5 1 Controlling Modbus Host by FST An FST Function Sequence Table can be used to schedule Modbus Host requests If an FST 15 created to schedule Host requests the FST should examine the Host Active flag of the Modbus Config Point Type and wait until the request is completed before proceeding Otherwise Host requests can be skipped and the desired data transfer may not have completed before proceeding To initiate a Host transmission the Host Active flag 15 set t
25. fer to Appendix The Modbus Protocol Emulation program Function Codes 1 2 3 4 5 6 15 and 16 use the same command and response format as the functions listed in the Modicon Modbus Protocol Reference Guide January 1955 form PI MBUS 300 Rev B Depending upon the Parameter configured Byte Word Double Word or Floating Point Function Codes 3 4 and 6 can contain more Data bytes than the other Function Codes The Data byte upper limit 1s 240 bytes Table 1 1 provides details of the Modbus Function Codes supported by the FloBoss Table 1 1 Modbus Function Codes Slave Function Request Data from Slave Action Valid TLP Codes 01 Read Logic Coil Status Obtain current Status ON OFF of a group of Type and outputs LGL 02 Read Discrete Input Obtain current Status ON OFF of a group of Type and Status inputs LGL 03 Read Output Holding Obtain current binary value in one or more Type LGL Registers output holding registers and Param Read Input Registers Obtain current binary value in one or more Type LGL input registers and Param Host Function Transmit Data to Slave Action Valid TLP Code 05 Force Single Logic Coil Force logic output coil to a Status of ON or Type and OFF LGL Preset Single Holding Place a specific binary value into an output LGL Register holding register and Param 15 Force Multiple Logic Force a series of consecutive logic output coils Type and Coils to a defined ON or OFF Stat
26. fo o Conv fo b Start fo End Addr fo Type jo fo Param fo Conv fo 7 Start f _ End Addr fo Type fo Lol fo Faram fo Conv fo o Start fo End Addr fo Type jo fo Param fo Conv fo 9 Start fo _ End Addr fo fo Lgl lo Faram fo Conv fo 10 Start fo End Addr jo Type jo Lol fo Faram fo Conv fo Update OK X Cancel Apply Figure 2 3 Modbus Functions Point Number indicates the Host communications port being configured and is dependent upon which user program 15 installed Tag ID displays the tag identification indicates the Point Number 2 Enter the Start address that represents the first data register in the address span In certain Modbus Host devices the register 40101 is actually transmitted as 100 The value 100 should be placed in the Start address field since the FloBoss uses the actual number sent by the Host A Start address of 0 15 a valid address Any number from 0 to 65535 is valid Register numbers can be duplicated as long as they are in separate Modbus Function configuration tables The tables should be numbered from smallest to largest Rev 01 03 Modbus Configuration 2 7 Modbus Host User Program User Manual 2 8 For example the Host device requests the Start address Reg 500 through End Addr Regs 700 The Slave Start address is 400 and the End Addr is 700 register numbers requested by the Host 500 through 700 are valid and would be responded to because the Re
27. for each of the ROC Point Types Enter the Lgl Logical Number to specify where to start collecting the Point Type data and if necessary whether to increment the Point Type or the Parameter The Logical Number field specifies the Logical Number to be assigned to the Start address When the Host requests a valid range of register numbers the Function Code tells the Slave what to do and between which registers Start through End Addr The Type Logical Number Lgl and Param fields define what data 15 collected or to what value to set the register numbers The Logical Number is used to increment the Point Type number or the Parameter Point indexing is used to increment the Point Type number When using point indexing Logical Number Lgl lt 128 Parameter indexing is used to increment the Parameter within the Point Type When using parameter indexing Logical Number Lgl gt 128 Modbus Configuration Rev 01 03 Modbus Host User Program User Manual Point Indexing Point indexing is used to increment the Point Type number If the range of addresses is greater than 0 the next address Start address 1 corresponds to the value specified by Logical Number 1 Lgl 1 When using point indexing Logical Number Lgl lt 128 For example when using horizontal indexing the configuration of Start 100 End Addr 106 Type Lgl 0 Param 17 Conv 0 Specifies seven values 100 101 102 103 104 105 and 106 for P
28. g through Regs numbers match or fall in between the Start and End Addr register numbers 400 through 700 The Reg and Regs fields are defined in the Modbus Host configuration screen The Modbus Host register numbers must be valid requests or an error will result Refer to Table Table 2 1 Valid Host Register Numbers Modbus Functions Modbus Host End Addr Enter the End Addr End Address that represents the last register number of a Point Type s data The value for this number is computed by End Address Start address Number of Functions 1 Enter the Point Type to set or acquire data Point Type data 15 associated with an address Start through End Addr When the Host requests a valid range of register numbers the Function Code tells the Slave what to do and between which registers Start through End Addr The Type Logical Number Lgl and Param fields define what data 15 collected or to what value to set the Point Type register numbers The Type field relies on the Logical Number Lgl field to determine if the Point Type increments horizontal indexing as data 15 gathered or set For example Point Type 47 15 used to indicate the Meter Flow Values To read the Energyrate per Day you would select Type 47 and Parameter 1 Param 1 If the Type field 15 set to 0 the line in the configuration table is considered invalid and skips when processing a request Appendix A has a complete list of parameters
29. git 0 Savett 0 HReas 0 Statusfo _ 7 ATU addrfo Fnc Regit 0 Savett 0 Regs D Statusfo 8 ATU addrfo Fnc Regit 0 Savett 0 Regs D Statusfo 9 ATU addrfo Fnc 0 Regit 0 Savett 0 HRegs Status 0 Update v OK X Cancel Apply Figure 2 4 Modbus Host Rev 01 03 Modbus Configuration Modbus Host User Program User Manual 2 12 Point Number indicates the Host communications port being configured and is dependent upon which user program is installed Tag ID displays the tag identification indicates the Host table number for the selected Point Number Enter the RTU Addr Remote Terminal Unit Address of the Slave device which to poll The RTU Address can be a number from 0 to 255 This is the FloBoss Slave Address set in the ROC Information screen of ROCLINK 800 The RTU Addr must match a FloBoss Slave Address in the same communications network or an error will occur RTU Address 0 is used to Broadcast a command to all devices connected to the communications port When the RTU Addr is 0 Broadcast every Slave device receives the same Function Code and performs the same action but the Slave devices do not send a response message Enter the Fnc Num to specify the Modbus Function Code to be sent to the Slave device Function Codes tell the Slave device what kind of action to perform Refer to Table Modbus Function Codes Function Numbers are entered as decimal values For example to set a sing
30. he Slave this is the starting register where the data collected from the Slave is stored in the Host This register number does not need to be the same as the device register number Reg The sequence of data registers following the Save must be large enough to hold the total number of data bytes sent back to the Host after the action requested by the Function Code has been performed Care must be given to insure that the Host has enough points to support the points being written to or read from the Slaves Utilization of Soft Point parameters unused I O module parameters and FST parameters may be required to store all of the necessary data Use the Modbus Host Configuration worksheet in Appendix B of this manual to assist in documenting configurations Modbus Configuration Rev 01 03 Modbus Host User Program User Manual The Host Save must be present in the Modbus Functions table for the same communications port you are configuring For example if you set the Saves field to 10 in the Modbus Host screen the Modbus Funct COMI screen must have 10 present in or between the Start and End Addr fields The response message is stored beginning at the register entered in the Save field To view the returned message navigate to the TLP location where the data 15 stored Enter the Regs to specify the number of registers data bytes for the Host to request or set The Modbus Functions table for the specified number of data bytes
31. int Types 28 LOL 35 COM2 and 38 1 18 RW UNS Cov gt Rev 01 03 Point Types A 5 Modbus Host User Program User Manual Modbus Functions Point Types 28 LOL 35 COM2 and 38 1 RW UINT8 1 gt Table A 6 Modbus Host Modbus Host Point Types 29 LOI 36 COM2 and 39 COM1 0 RW AC 10 Host Tag Identification 1 RW UNT8 JORTUAdd 00 0 0 2 RW 1 Pe Num 3 RW UINTI6 2 0 0 R W 5 RW UINT8 1 Regs 000 6 RW Stats 0 0 000 8 RW UINT8 1 FneNm 00 5 9 RW UNTI6 2 A 6 Point Types Rev 01 03 Modbus Host User Program User Manual Modbus Host Point Types 29 LOI 36 COM2 and 39 COM1 Rev 01 03 Point Types A 7 Modbus Host User Program User Manual Modbus Host Point Types 29 LOI 36 COM2 and 39 COM1 Read Write Data Type Length UINT 8 60 RW UINT8 A 8 Point Types Rev 01 03 Modbus Host User Program User Manual APPENDIX B CONFIGURATION WORKSHEETS The Modbus Function and Host Configuration worksheets are provided to assist you in configuring the Modbus program Make copies as needed Rev 01 03 Configuration Worksheets B 1 Modbus Host User Program User Manual Modbus Host Configuration Worksheet Function Slave Register Host Register Number of B 2 Configuration Worksheets Rev 01
32. le coil enter 05 on the Fnc Num field or the Host desires to send Function Code 02 to a FloBoss The Host sets the FloBoss Address in the RTU Addr field The Host sets the Function Code value in the Fnc Num field of the Modbus Host screen A Function Number of 0 disables this request or command Any other Function Numbers not described previously result in an error Status 145 and abort the request or command Enter the Reg starting data register for this request in the Slave device This corresponds to a data register matching or between the Start and End Addr parameters in the Modbus Functions screen This 15 the first data byte sent to the Slave and tells the Slave at which register to begin the action associated with the Function Code A register number is valid as long as it matches the beginning register number Start the ending register number End Addr or any number in between for that particular entry in the table Start gt Reg through End Addr lt Regs If no register number match is located an error message Exception Response returns For example the Host desires to send Function Code 02 Read Discrete Input Status to a FloBoss The Host sets the FloBoss Address in the RTU Addr field The Host sets the Function Code 02 value in the Fnc Num field The Host specifies the starting register in the Reg field and how many registers to read through in the Regs field Enter the Save value When a message is returned from t
33. m left to right with bit 7 the furthest to the left A 1 in any bit indicates that it is active or enabled Bit 7 6 5 4 Response Code 1 0 0 0 0 0 0 0 Communication kb Parse Parity Reserved Overrun butter Overt low Framing Error Undefined 1 3 Archive Point Type Table Fields The Archive Point Type tables have a name and five columns Table Name The table name indicates the Point Type and a brief description of the Point Type The Point Type corresponds to the Type field 1n the Modbus Functions configuration tables detailed in Section 3 A list of all Point Types 15 included in Table A 1 starting on page 1 Parameter The Parameter column defines the specific parameter number associated with that Point Type The number in the Parameter column corresponds to the Param field in the Modbus Functions configuration tables detailed in Section 3 Read Write The Read Write column indicates if the parameter can be read and written to R W or if the parameter 15 Read Only R O Data Type Data Types are defined in Table A 2 on page A 2 Length The length of the parameter 15 indicated in the Length column Description A brief description of each parameter is provided in the Description column A 2 Point Types Rev 01 03 Modbus Host User Program User Manual Table A 3 Modbus Modem Modbus Modem Point Types 26 LOT 32 COM2 and 33 COM1 0 RW 118
34. must be sized the same as or greater than the Regs field The values of the Start and End Addr fields in the Slave Modbus Function table must accommodate the number of data bytes set in the Regs For example you cannot request registers Reg 300 through Regs 500 if the Start value is 100 and the End Addr value is 200 because the registers are not configured in the Slave Modbus Function table A register number 15 valid as long as it matches the beginning register number Start the ending register number End Addr or any number in between for that particular entry in the table Start 2 Reg through End Addr lt Regs If no register number match is located an error message Exception Response returns Refer to Table and Section 4 Exception Responses Status displays the status of the Host request or command Table 2 2 lists the possible status values Rev 01 03 Modbus Configuration 2 13 Modbus Host User Program User Manual Table 2 2 Status of Host Request or Command Staus scription SS mn Inactive or start of transmission This line in the Host table is inactive or beginning a transmission Receive timeout error A slave response was not received This indicates that the slave did not receive the request message or the RTU Address within the request message was incorrect Make sure that the Address of the Host and Slave Address match Check the cabling between the Host and Slave and make sure that pinouts are cor
35. n their respective instruction manuals ROCLINK 800 Configuration Software User Manual Form A6121 FloBoss 105 Flow Manager Instruction Manual Form A6114 ROC Protocol User Manual Form A4199 Modicon Modbus Protocol Reference Guide January 1985 form PI MBUS 300 Revision B available from Modicon AEG Schneider Automation BEBE WWW modicon com Web site 1 3 Organization of Manual Section 2 Modbus Configuration describes configuration of the Modbus Modem Configuration Function and the Host Section 3 Problem Solving provides information detailing response failures error messages responses containing invalid data multi point communication errors and other conditions Appendix A FloBoss Point Types provides information detailing Point Types Data Types Point Type Parameters Opcodes and User Defined Point Types Appendix B Configuration Worksheets provides worksheets to help you configure and maintain a record of your Modbus Host Slave network Topical Index Lists alphabetically the items contained in this manual including the section and page number Rev 01 03 Getting Started 1 1 Modbus Host User Program User Manual 1 4 Modbus Protocol Host User Program Overview The Modbus Protocol Host User Program allows a FloBoss 103 to emulate the Modbus Protocol Host This makes it possible to enable a FloBoss to be a Host Modbus device FloBoss units may communicate directly using the Local
36. nflict with any patent Fisher Controls reserves the right without notice to alter or improve the designs or specifications of the products described herein i Rev 01 03 Modbus Host User Program User Manual TABLE OF CONTENTS iii Secon CONN RC 1 1 t 1 1 12 Additonal 1 1 1 3 Organization of 1 1 0 02 2 1140200000000000000000000055508 000005 sinn nnns 1 1 1 4 Modbus Protocol Host User Program 1 1 5 User Program Names Versions nna 4 SECTION 2 Modbus Configuration ENS Eo AGANG E EN Mr 2 2 NR Con HOUT AU OU 25 NOCOU UU AA AA 2 6 nA 2 10 225 JMN 2 16 Seccion ORV INO ooo eo ane ater Sal FIOBOSS T103 0r Sl ve Eror MESSAGES 3 2 FloBoss or Slave Responds with Wrong Data Response a 3 3 FloBoss Appends a Character to 3 4 FloBoss Does Not Respond in Point to Multi Point Comm System 39 Integer to Float BIST m TT 2 3 6 FloB
37. ns port being configured in the Modbus Functions screen of the Slave to be polled 2 1 Modbus Modem Use the Modus Modem Comm Port 2 only screen to configure modem parameters for the Host s communication port The Modbus program initializes the modem upon power up Host modem dial up and modem disconnect Upon initialization commands are sent to the modem to configure it for proper operation 1 Select Configure User Data Modbus Modem Refer to Figure Modbus Modem COM Ei Paint Number 1 Status fo ModType 1 Est 2 Int 0 ATU Addr fo Connect Command Addr fo Connect Command ATU Addr fo Connect Command Addr fo Connect Command Addr fo Connect Command Addr fo Connect Command Update v OK X Cancel Apply Figure 2 1 Modbus Modem Point Number indicates the Host communications port being configured and is dependent upon which user program is installed Rev 01 03 Modbus Configuration 2 1 Modbus Host User Program User Manual 2 2 Status reflects codes returned from the modem OK 1 Connect 1 2 Ring The ModType 1 2 Ext 2 Int field indicates the location of the modem as externally 1 or internally 2 Use ROC Comm Ports to configure the modem Enter the RTU Address of the Slave device to be associated with the Connect Command Up to six different Modbus Slaves can be dialed up through one Communication Port The RTU Remote Terminal Unit
38. o a 1 Upon completion of the request the Host Active flag 1s cleared 0 Wait for this Host Active flag to clear 0 before proceeding NOTE The Host Active flag does not clear if the Continuous Poll flag is also set 1 Using an FST other scenarios can be developed to control the Modbus Hosts ability to dial other Modbus devices on a regular interval FST Timers can be set to indicate when it 1s time for the Modbus Host to call other Modbus devices Comparing values for status change limit exceeded or Deadband exceeded can initiate Modbus Host requests to signal warnings to other Modbus devices 2 16 Modbus Configuration Rev 01 03 Modbus Host User Program User Manual SECTION 3 PROBLEM SOLVING 3 1 FloBoss 103 or Slave Error Messages Error messages are usually caused by the FloBoss or Slave configuration Check to see that 1 The proper format ASCII or RTU 15 selected 2 The Modbus Functions are configured correctly The Start gt Reg through End Addr lt Regs are not valid 3 Enough continuous registers are configured 4 The requested Type Lgl and Param match the configured Type Lgl and Param 5 The conversions Conv are used correctly 3 2 FloBoss or Slave Responds with Wrong Data in Response Wrong data is usually caused by the FloBoss or Slave configuration Check to see if 1 The data order is wrong Check MSB and LSB configuration in the Modbus Config screen 2 The wrong register numbers are config
39. odbus Host User Program User Manual These values are signed integers ranging from zero to 32767 The default signal range is 800 to 4000 which represents a 1 to 5 volt or 4 to 20 milliAmp signal These data fields can also be used to scale the Analog I O to integer values with an implied decimal point For example all Analog Raw values can be transmitted with 0 to 1000 values 0 to 100 0 decimal point implied by setting the values in this field to for the LO Integer Scale and 1000 for the HI Integer Scale The scaling is used only on Analog I O specified by I O Point Type 3 AIN Parameter 17 Raw A D Input and I O Point Type 4 AO Parameter 9 Raw D A Output Enter the HI Float Scale and LO Float Scale values The HI Float Scale and LO Float Scale fields are normally used when the Host is not able to process floating point numbers Eight sets of floating point ranges for values can be specified This allows floating point values such as PID Setpoints to be read and set by the Host as integer values The FloBoss units floating point values are converted to integers by configuring a register or range of registers with the Conv conversion fields set in the Modbus Function configuration screens The equations used to convert floating point to integer values are Float Range HI Float Scale LO Float Scale Integer Range HI Integer Scale LO Integer Scale Adjusted Reading Float Reading LO Float Scale Integer Integer Range
40. oss Response Preceded By Modem 2 Appendix A Pont LY DE ET ED SERVILI 1 AT Poimi Types UU m 1 Appendix Configuration 2 26 e ee eese I 1 Rev 01 03 Table of Contents lil Modbus Host User Program User Manual iV Table of Contents Rev 01 03 Modbus Host User Program User Manual SECTION 1 GETTING STARTED 1 1 Overview The Modbus Protocol Host Emulation User Program is designed to allow the FloBoss 103 Flow Managers version 1 10 or greater to emulate the communications protocol used by Modbus Host devices This makes it possible to integrate the FloBoss 103 units and Modbus devices into the same Host Slave system NOTE Modbus Slave capabilities are standard in the firmware while the use of this user program allows host capabilities This manual describes how to configure and use the Modbus Protocol Host Emulation Program which is configured by using the ROCLINK 800 Configuration Software version 1 10 or greater 1 2 Additional Information This document 15 intended to be used in conjunction with the following manuals and Internet Web sites to assist you The physical aspects of the FloBoss units are contained i
41. ow many seconds the Slaves are polled Enter a value for the Table Start for the Modbus Address Table Certain Modbus Hosts request the Address Table from the FloBoss for configuration of the Host Normally during initialization the Host reads the Address Table to determine where the Input and Output data tables are located and to determine the 100 and 0 values for all analog data Function Code 03 allows the transmission of the Input Data Start register Output Data Start register HI Integer Scale and LO Integer Scale values The Address Table normally resides at the start of the Modbus registers either at location 0 or 40000 Enter the Input Data Start for the starting register address for the block of registers of the input data table Enter the Output Data Start for the starting register address for the block of registers of the output data table Enter the HI Integer Scale values for the 100 High Reading EU value for all analog data registers Enter the LO Integer Scale values for the 0 Low Reading EU value for all analog data registers In the FloBoss the endpoints of the Analog Inputs and the Analog Outputs are used to scale or calibrate the range of the input or output signal Because each I O point can have different scaling the Raw Values from the Analog I O points are normalized to the values defined by the HI Integer Scale and LO Integer Scale fields Modbus Configuration Rev 01 03 13 14 M
42. rect Received address check A byte of the response has been received and the check of the RTU Address is in progress If the status remains at 2 the wrong RTU Address was received and the program will check the next byte received until a match is found May indicate that the first byte was missed or there are extra bytes being sent Received Function Number check The RTU Address check has passed the second byte of the response has been received and the check of the Modbus Function Number is in progress If the Status remains at 3 the configured Host table Function Number did not match the received Function Number 4 Number of expected bytes check The expected number of data bytes in the response message is being checked If the Status remains at 4 The wrong number of data bytes was received Receiving Slave response The RTU Address check Function Number check and number of data bytes check have all passed The data is now being received If the Status remains at 5 an error occurred reading the data bytes of the response CRC or LRC check In RTU mode the LSB of the CRC has been received In the ASCII mode of operation the LRC has been received and the calculated LRC did not match the received LRC 7 CRC or LRC check In RTU mode the MSB of the CRC has been received If the Status remains at 7 the calculated CRC did not match the received CRC Not used in ASCII mode of operation Valid Slave response The Host request was sent and
43. s between the Reg starting register and Regs total registers The Slave responds by sending a message with the results of the request or command or an 1 corresponding RTU Address 2 Fnc Num field 3 register entered in the Reg field 4 to act upon values 5 error if the request fails 6 The request or command results data bytes are stored in the register beginning with the value entered in the Save field The Status field displays the current status of the Host request or command Care must be given to insure that there are enough points in the Host to support the points being written to or read from the Slaves Utilization of Soft Point parameters unused I O module parameters and FST parameters may be required to store all of the necessary data Use the Modbus Host Configuration worksheet in Appendix B of this manual to assist in documenting configurations To configure the Modbus Host 1 Select Configure User Data Modbus Host Refer to Figure Point Number HOST 0 9 0 ATU addrfo _ Fnc Regit 0 Savett 0 Regs D Statusfo 1 ATU addrfo Fnc 0 Regit 0 Savett 0 0 Statusfo 2 ATU addrfo Fnc Numfo Regit 0 0 Regs D Status 0 3 ATU addrfo Fnc Numfo Regit 0 Savett 0 Reas D Statusfo 4 ATU Addr 0 Fnc Regit 0 Savett 0 Regs D Statusfo 5 ATU addrfo Fnc 0 Regit 0 Savett 0 0 Statusfo ATU addrfo Fnc Numfo Re
44. t set to signify an error The exception codes listed in Table 2 4 are for reference only When a normal return response message 15 received by the Host the Slave returns data results or statistics acquired during the poll When an error occurs the exception code displays 1n the Data field The exception code details why the error occurred Table 2 3 ROC Exception Response Example Message Device Exception Message Field Function Code Error Check Byes 1 1 qo TX Order pf 5 FC 80H CRC 16 Table 2 4 Modbus Protocol Errors that Elicit an Exception Response Message Error Detected Usage Illegal Function Code Implemented Ilegal Data Address Implemented Illegal Data Value Implemented Error Code 01 Function Code not listed Refer to Table Error Code 02 Register value not configured The Start gt Reg through End Addr lt Regs are not valid Error Code 03 Wrong number of data bytes sent Refer to Table 2 2 Rev 01 03 Modbus Configuration 2 15 Modbus Host User Program User Manual 2 5 Sending a Message To send a message to a Slave device 1 Configure the parameters in the Modbus Host screen to indicate to which Slave Address RTU Addr the message 15 to be sent which Function Code the Slave device 15 to perform and to which registers Refer to Section Modbus Host on page 2 10 2 Configure the parameters in the Modbus Functions screen to indicate which data 15 require from the Slave d
45. tart Warm Start Cold Start Cold Start amp Clear ROC Displays Cold Start amp Clear FST Cold Start amp Clear History Cold Start amp Clear ALL 2 Update v Ok X Cancel Apply Flash Memory Save Configuration Clear Status Figure 1 2 ROC Flags 10 Click Flash Memory Save Configuration and click Yes This ensures that the program automatically restarts after a Cold Start Refer to Figure 11 Click OK NOTE You can enable security for the communications port using ROC gt Security options Rev 01 03 Getting Started 1 5 Modbus Host User Program User Manual 1 6 Getting Started Rev 01 03 Modbus Host User Program User Manual SECTION 2 MODBUS CONFIGURATION The Modbus Protocol Emulation Program functions are configured using ROCLINK 800 configuration software Use the following screens to configure the Modbus Host User Program Modbus Modem Modem configuration parameters for the Host communication port Comm Port 2 only Modbus Configuration Configures the Modbus parameters Configure both Host and Slave devices to have similarly configured parameters Modbus Function Corresponds to the same communications port being configured in the Modbus Host screen of the Host that 1s to poll the Slave device Modbus Host Sets up the Modbus configuration parameters to allow the FloBoss to act as a Host This corresponds to the same communicatio
46. the Function Code Error Checking Informs the Host if the action or request was successful Reply Message After the message 15 sent and the Slave performs the action or request the Host receives a reply message containing the information it requested The Slave device receives the message and performs the following Recognizes that a message has been addressed to the Slave device s ROC Address Determines the action or request sent by the Host This includes the Function Codes and any necessary Data Acquires the data information or performs the action as stated in the message Creates a reply message Sends the reply message to the Host containing any information data required by the initial message or sends an error code if the action or request failed Replies are not sent when a Broadcast message 15 requested The Modbus Host User Program 15 configured and downloaded to Flash memory by ROCLINK 800 The FloBoss uses physical addressing of I O while Modbus applications use logical I O addressing to retain compatibility with Modbus The Modbus messages are configured and input output parameters are referenced in the FloBoss in the same manner as standard Point Type parameters by Point Type Type Logical Number 1 2 1 2 Getting Started Rev 01 03 Modbus Host User Program User Manual and Parameter Param to define point locations Each input output I O Point Type must be individually configured Re
47. tion TMOCT FloBoss has timed out waiting for a connection DISCC FloBoss is disconnecting from a remote device 2 3 Modbus Functions Modbus Functions correspond to the same communications port being configured in the Modbus Host screen of the Host that 1s to poll the Slave device When a message 15 received from the Host the Slave device 1 Reads the RTU Addr from the Host Config screen sent from the Host and matches it with the FloBoss Address ROC Information screen of the Slave 2 If the message is for that Slave device or is a Broadcast message the Slave reads the Function Code Fnc Num so that it knows what action to perform If the RTU Addr does not match the FloBoss Address the message 15 1gnored 3 Next the Slave searches the Function configuration table Figure 2 3 for the Modbus register numbers requested Reg through Regs starting with the first table first Tag ID entry down to the last last Tag ID 4 If a register number match is found Start gt Reg through End Addr lt Regs it builds response based on the TLP configured in the table If no register number match 15 located an error message Exception Response returns The User Program locates a register number as long as it matches the beginning register number Start the ending register number End Addr or any number in between for that particular entry in the table NOTE TLP is the Point Type Type Logical Number Lgl
48. uration of Start 57428 End Addr 57437 Type 17 Lel 137 Param 2 Conv 0 Specifies ten 57428 through 57437 parameters for Soft Point number 10 Lgl 9 128 starting at Parameter 2 So register 57428 Parameter 2 of Soft Point 10 register 57429 Parameter 3 of Soft Point 10 and register 57437 Parameter 11 of Soft Point 10 Another way to explain the Logical Number Lgl field is that when the Logical Number is 128 or greater the Point Type number remains the same and the Parameter within that point increments When the Logical Number 15 less than 128 the Point Type number increments and the Parameter number remains the same Logical Numbers are zero based For example there are 32 Soft Points with the first being logical 0 and the last being logical 31 for a total of 32 To get the correct Logical Number for the point you wish to access subtract 1 from the number Soft Point 5 15 Logical Number 4 and Soft Point 27 15 number logical 26 Analog Input 3 1s number logical 2 and so on Rev 01 03 Modbus Configuration 2 9 Modbus Host User Program User Manual Modbus protocol supports 32 Soft points so the valid Soft Point Logical Numbers are 0 31 and 128 159 6 Each Type has multiple Parameters associated with the Point Type Enter a value in the Param field to specify the starting Parameter of the Point Type and relies on the Logical Number Lgl field to determine if the Parameter 15 incremented using vertical
49. ured Check the Reg Regs Start and End Addr fields 3 The wrong Parameter is selected Check the Type Lgl and Param fields 4 Indexing is not proper See Section 3 Lgl field 3 3 FloBoss Appends a Character to Message Check to see if a Turnaround Delay or Key Off Delay is configured in the Communication Parameters screen ROC gt Comm Ports when it is not required 3 4 FloBoss Does Not Respond in Point to Multi Point Comm System Check to see if the FloBoss responds in a point to point hook up If it does the problem is associated with delays in the system Check 1 The FloBoss Key On Delay ROC gt Comm Ports has been configured correctly 2 The FloBoss Turnaround Delay or Key Off Delay has been configured correctly 3 The Host has configurable Key On Delay and Turnaround Delay or Key Off Delay 4 Each FloBoss must have a unique FloBoss Address Rev 01 03 Problem Solving 3 1 Modbus Host User Program User Manual 3 5 Integer to Float Conversion Integer to float conversions may not produce a fractional component To correct use a float scale range that more closely corresponds to the range of the integer being converted Refer to Section Conv fields 3 6 FloBoss Response Preceded By Modem Commands If the FloBoss sends modem commands before the transmission of a response to a request connect the FloBoss DSR signal to the modem s DCD signal or a similar pin indicating modem activity 3 2 Problem Solving R
50. us LGL 16 Preset Multiple Holding Place specific binary values into a series of LGL Registers consecutive holding registers and Param 1 4 1 Data Link The data link between the Host device and the FloBoss include Direct Link LOI Local Port Direct Link EIA 485 RS 485 Comm Port 1 EIA 232 RS 232 Serial Communications Card Comm Port 2 EIA 485 RS 485 Serial Communications Card Comm Port 2 Dial Up Modem Communications Card Comm Port 2 Rev 01 03 Getting Started 1 3 Modbus Host User Program User Manual 1 5 User Program Names and Versions Program versions and names display in Table 1 2 Only one user program 15 required Table 1 2 Versions and Program Names Program User Archive FloBoss Type Task Point Code Blocks Data Blocks Mb103 0 bin FloBoss 103 Version 1 10 26 27 7 7 474000 476FFF or greater 28 29 Mb103 1 bin 08058 103 Version 1 10 33 37 760000 7 478000 47AFFF or greater 38 39 Mb103 2 bin 28055 103 Version 1 10 32 34 760000 7FFFFF 47 000 47EFFF or greater 35 36 NOTE Mb103 2 bin is required for modem communications 1 5 1 Downloading the User Program To download the user program 1 Connect the FloBoss 103 to ROCLINK 800 software through the LOI port 2 Select Utilities User Program Administrator User Program Administrator x
Download Pdf Manuals
Related Search