1. Manuals
  2. Brands
  3. SMC Sierra Monitor Manuals
  4. Server
  5. FieldServer
  6. Driver manual

SMC Sierra Monitor FieldServer Driver Manual

Fs-8704-03 modbus tcp/ip
Hide thumbs Also See for FieldServer:
Table of Contents

Advertisement

Quick Links

See also: Configuration Manual
FieldServer
FS-8704-03 Modbus TCP/IP
Driver Manual
(Supplement to the FieldServer Instruction Manual)
APPLICABILITY & EFFECTIVITY
Effective for all systems manufactured after October 2016.
Driver Revision: 1.12
Document Revision: 4.B

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the FieldServer and is the answer not in the manual?

Questions and answers

Related Manuals for SMC Sierra Monitor FieldServer

Summary of Contents for SMC Sierra Monitor FieldServer

  • Page 1 FieldServer FS-8704-03 Modbus TCP/IP Driver Manual (Supplement to the FieldServer Instruction Manual) APPLICABILITY & EFFECTIVITY Effective for all systems manufactured after October 2016. Driver Revision: 1.12 Document Revision: 4.B...
  • Page 2 Modbus TCP/IP Driver Manual Technical Support Please call us for any technical support needs related to the FieldServer product. Sierra Monitor Corporation 1991 Tarob Court Milpitas, CA 95035 Website: www.sierramonitor.com U.S. Support Information: +1 408 262-6611 +1 800 727-4377 Email: support@sierramonitor.com...

  • Page 3: Table Of Contents

    Hardware ..........................4 Hardware Connections ........................5 Data Array Parameters ........................6 Configuring the FieldServer as a Modbus TCP/IP Client ..............7 Client Side Connection Parameters ....................7 Client Side Node Parameters ......................8 Client Side Map Descriptor Parameters ..................9 5.3.1...

  • Page 4: Modbus Tcp/Ip Description

    Modbus/TCP Host Node [such as: Intellution Fix, Wondereware Intouch, GE Cimplicity, Quantum PLC (Master)] This cable is necessary for connection to the driver. It is shipped with the FieldServer and not separately with the driver. If FieldServer is used as a Modbus/TCP Client.

  • Page 5: Hardware Connections

    Modbus TCP/IP Driver Manual HARDWARE CONNECTIONS Configure the PLC according to manufacturer’s instructions. Remote Modbus Device Switch FieldServer Part # 8915-10 UTP cable Connect to an Ethernet Port on the FieldServer FieldServer Page 5 of 23...

  • Page 6: Data Array Parameters

    Modbus TCP/IP Driver Manual DATA ARRAY PARAMETERS Data Arrays are “protocol neutral” data buffers for storage of data to be passed between protocols. It is necessary to declare the data format of each of the Data Arrays to facilitate correct storage of the relevant data.

  • Page 7: Configuring The Fieldserver As A Modbus Tcp/Ip Client

    This section documents and describes the parameters necessary for configuring the FieldServer to communicate with a Modbus TCP/IP Server. The configuration file tells the FieldServer about its interfaces, and the routing of data required. In order to enable the FieldServer for Modbus TCP/IP communications the following three actions must be taken.

  • Page 8: Client Side Node Parameters

    Modbus TCP/IP Driver Manual Client Side Node Parameters Section Title Nodes Column Title Function Legal Values Up to 32 alphanumeric Node_Name Provide name for node. characters 0 – 255 Node_ID Station Address of Remote Server Node. Protocol Specify protocol used. Modbus/TCP Adapter Specify which adapter this protocol uses.

  • Page 9: Client Side Map Descriptor Parameters

    Modbus TCP/IP Driver Manual Client Side Map Descriptor Parameters 5.3.1 FieldServer Specific Map Descriptor Parameters Column Title Function Legal Values Map_Descriptor_Name Name of this Map Descriptor. Up to 32 alphanumeric characters Name of Data Array where data is One of the Data Array names from...

  • Page 10: Timing Parameters

    Modbus TCP/IP Driver Manual Set to MD_Length if write-thru operation should write all registers Write_Length* as specified by length parameter. MD_Length, -, 1 By default write-thru writes a single register. Any signed 32 bit integer in the range: Data_Array_Low_Scale* Scaling zero in Data Array. -2,147,483,648 to 2,147,483,647, 0 Any signed 32 bit integer in the range:...

  • Page 11: Map Descriptor Examples

    Modbus TCP/IP Driver Manual 5.3.4 Map Descriptor Examples All three examples below are addressing the same Modbus registers: Client Side Map Descriptors for Nodes where Address_Type is ADU Map_Descriptors Map_Descriptor_Name , Data_Array_Name , Data_Array_Offset , Function , Node_Name , Data_Type , Address , Length , Scan_Interval CMD_AI_01 , DA_AI_01...

  • Page 12: Configuring The Fieldserver As A Modbus Tcp/Ip Server

    This section documents and describes the parameters necessary for configuring the FieldServer to communicate with a Modbus TCP/IP Client. The configuration file tells the FieldServer about its interfaces, and the routing of data required. In order to enable the FieldServer for Modbus TCP/IP communications the following three actions must be taken.

  • Page 13: Server Side Node Parameters

    Fill_Gaps_With_Zero, defined in the Map Descriptor section. Fill_Gaps_With_FFFF NOTE: For this protocol, the IP address for the FieldServer is configured using the "I" menu option on the Remote User Interface. Example Server Side Nodes for new devices where 65536 registers are available in each memory area...

  • Page 14: Server Side Map Descriptor Parameters

    Modbus TCP/IP Driver Manual Server Side Map Descriptor Parameters 6.3.1 FieldServer Specific Map Descriptor Parameters Column Title Function Legal Values Map_Descriptor_Name Name of this Map Descriptor. Up to 32 alphanumeric characters Name of Data Array where data is One of the Data Array names from...

  • Page 15: Map Descriptor Examples

    Modbus TCP/IP Driver Manual 6.3.3 Map Descriptor Examples All three examples below are addressing the same Modbus registers: Client Side Map Descriptors for Nodes where Address_Type is ADU Map_Descriptors Map_Descriptor_Name , Data_Array_Name , Data_Array_Offset , Function , Node_Name , Data_Type , Address SMD_AI_01 , DA_AI_01...

  • Page 16: Appendix A. Useful Features

    If a Modbus Server sends two consecutive registers to the FieldServer representing either a floating point value or a 32 bit integer value, the FieldServer can combine and decode these registers back into their original format. To do this, declare Data Array of type Float or UINT32 and set the Map Descriptor Data_Type as ‘Float_Reg’, ‘32Bit_Reg’, etc.

  • Page 17: Appendix A.2. Node_Offline_Response

    FieldServer configured as a Modbus TCP/IP Server, when a Server Node goes offline the default behavior of the FieldServer would be to stop responding to polls for this data. This might not be what the user wants. Various options exist making it possible to signal that the data quality has gone bad without creating error conditions in systems sensitive to the default option.

  • Page 18: Appendix A.3. Splitting Registers Into Bytes Or Bits

    Sometimes it is required to split a register into Bytes or bits. The following Map Descriptors read registers and store the bytes/bits in consecutive data array locations. The FieldServer will store the least significant byte/bit at the 1st offset and will continue sequentially. To implement this feature, declare a Data Array with Data_Format Byte or bit and use that Data_Array_Name when setting up the Map_Descriptor parameters.

  • Page 19: Appendix A.4.2. Server Side Map Descriptor

    Modbus TCP/IP Driver Manual Appendix A.4.2. Server Side Map Descriptor Server Side Map Descriptors can define any object as shown below: The Driver will serve strings from the data array as an object value. The string from the data array is considered complete if the character is 0 (null) or if all characters are fetched as per the Map Descriptor length.

  • Page 20: Appendix A.6. Reading Scattered Addresses

    Modbus TCP/IP Driver Manual Appendix A.6. Reading Scattered Addresses This function enables the user to read non-contiguous registers. It also avoids multiple polls using function 3 or 4 to read non-contiguous registers. The following is an example to show the request and response to read input registers (sub function 0x04) 101 (0x65), 114 (0x72) and 149 (0x95) from Slave_ID 33 (0x21).

  • Page 21: Appendix B. Troubleshooting

    Appendix B. Troubleshooting Appendix B.1. Server Configuration of System Station Address When using the FieldServer as a Modbus Server, the FieldServer System Station address must be configured to be different from any of the configured Modbus Server Node_ID’s. Configuring these to be the same invokes proprietary system information to be transmitted, and should therefore be avoided.
  • Page 22 If this happens, the FieldServer logs errors and no communication occurs, but when the FieldServer polls the same device a bit later and there is no second poll request active the response will succeed. Therefore device communication is still intact and these errors represent no significant problem.

  • Page 23: Appendix C. Reference

    Modbus TCP/IP Driver Manual Appendix C. Reference Appendix C.1. Data Types If Node parameter Address_Type is set as ADU or PDU, then Data_Type must be specified as follows. Address_Type ADU: Address range Data_Type Function Code (Write) Function Code (Read) 1 – 65536 Coil 1 –...

Table of Contents