Korenix JetI/O 6512 Industrial Intelligent Ethernet I/O Server User Manual

Transcription

1 Korenix JetI/O 6512 Industrial Intelligent Ethernet I/O Server User Manual Sept (V1.5)

2 Korenix JetI/O 6512 Industrial Intelligent Ethernet I/O Server User Manual Copyright Notice Copyright 2009 Korenix Technology Co., Ltd. All rights reserved. Reproduction in any form or by any means without permission is prohibited. 2

3 Index 1 INTRODUCTION OVERVIEW OF JETI/O 6500 SERIES PACKAGE CHECKLIST JETI/O 6512 INTRODUCTION JETI/O 6512 PRODUCT SPECIFICATION HARDWARE INSTALLATION HARDWARE INTRODUCTION WIRING POWER INPUT WIRING I/O CONNECTORS JETI/O 6512 WIRING EXAMPLE WIRING EARTH GROUND WIRING FAST ETHERNET PORTS DIN-RAIL MOUNTING INSTALLATION PREPARATION FOR MANAGEMENT UNDERSTAND THE ETHERNET I/O SERVER ARCHITECTURE PREPARATION FOR REMOTE MANAGEMENT FEATURE CONFIGURATION BLOCK I/O CONFIGURATION UTILITY BLOCK I/O OPC SERVER UTILITY SNMP WEB UI HOW TO UPGRADE FIRMWARE CONFIGURATION BACKUP/RESTORE, RESET DEFAULT, AND REBOOT MODBUS/TCP COMMAND SET INTRODUCTION OF MODBUS/TCP PROTOCOL JETI/O 6512 MODBUS/TCP ADDRESS MAPPING APPENDIX SNMP MIB REVISION HISTORY... 84

4 1 Introduction Welcome to Korenix JetI/O 6500 Series Industrial Managed Ethernet I/O Module User Manual. Following topics are covered in this chapter: 1.1 Overview of JetI/O 6500 Series 1.2 Package Checklist 1.3 JetI/O 6512 Introduction 1.4 JetI/O 6512 Product Specification 1.1 Overview of JetI/O 6500 Series JetI/O 6500 series is a series of Managed Ethernet I/O Server for distributive monitoring and controls. The JetI/O 6500 series equipped with one Ethernet port and multiple channels Analog Input/Output, Digital Input/Output and temperature measurement connectors. Thus users can easily perform I/O data collecting, status changing, automatically activate events through the Ethernet network. JetI/O 6500 series provides Windows Utilities, and SNMP for configuration. And support Modbus/TCP protocol, OPC Server for Modbus/TCP, thus user can easily monitor and control the remote I/O devices and combine the JetI/O with existed HMI/SCADA package. Naming Rule: JetI/O 65AB A: Major Feature 1: Analog Input Series. Includes the RTD input, Thermocouple Input 2: Analog Output Series 3: Digital Input Series 4: Digital Output Series 5: Digital Input and Digital Output Series B: Sequence Number JetI/O 6500 Series includes: JetI/O 6510: Intelligent 8-CH Analog Input Ethernet I/O Server JetI/O 6511: Intelligent 8-CH Thermocouple Input Ethernet I/O Server JetI/O 6512: Intelligent 4-CH RTD Input Ethernet I/O Server JetI/O 6520: Intelligent 4-CH Analog Output Ethernet I/O Server JetI/O 6550: Intelligent 14-CH DI and 8-CH DO Ethernet I/O Server 1

5 1.2 Package Checklist Korenix JetI/O 6500 Series products are shipped with following items: One Ethernet I/O Server One attached DIN-Rail clip Terminal Blocks for I/O and Power Input Documentation and Software CD Quick Installation Guide If any of the above items are missing or damaged, please contact your local sales representative. 1.3 JetI/O 6512 Introduction JetI/O 6512 is an intelligent I/O Server equipped with 4 channels RTD Input connectors. JetI/O 6512 provides 16 bit resolution and high accuracy for temperature measurement. The supported RTD types include PT100 and Ni120 types. JetI/O 6512 provides Windows Utilities, SNMP for configuration. Industrial Modbus/TCP protocol and OPC Server for integrating JetI/O with existed HMI/SCADA. Robust aluminum case with good heat dispersing and IP31 protection. With JetI/O users can easily perform status monitoring and control the remote I/O devices. 2

6 1.4 JetI/O 6512 Product Specification System CPU: 100MHZ, RISC-Based SDRAM: 32K bytes Flash ROM: 512K bytes EEPROM: 256 bytes Watchdog Timer: 1.0 sec H/W LED: PWR: Power Input plugged and On (Red) RDY: System startup ready (Green) Network Interface Ethernet: IEEE Base-T, IEEE 802.3u 100Base-TX Connector: 1 * RJ-45, Auto MDI/MDI-X Protection: Built-in 1.5 KV magnetic isolation protection LED: Upper (LAN Activity): Orange ON & Blinking Lower (10M/100M): 10M: Green OFF, 100M: Green ON PWR: Power On (Green) RDY: System boot up Ready (Red), system booting (No LED) RTD Input Input s: 4 s Resolution: 16 bits Input Type: Pt100 and Ni120 RTD Input Connections: 3, 4 or 5 wire Input Range: Pt100 (-100 C~100 C α= ) Pt100 ( 0 C~100 C α= ) Pt100 ( 0 C~200 C α= ) Pt100 ( 0 C~600 C α= ) Pt100 (-100 C~100 C α= ) Pt100 ( 0 C~100 C α= ) Pt100 ( 0 C~200 C α= ) Pt100 ( 0 C~600 C α= ) Nickel 120 (-80 C ~ 260 C α= ) Accuracy: ±0.05% of FSR ±1LSB Sampling Rate: 10 samples/sec (total) Input Impedance: 10M ohm Calibration: On Board EEPROM Isolation Voltage: 2500Vrms Feature Network Protocols: IP, TCP, UDP, SNMP, HTTP, BOOTP, DHCP, Modbus/TCP, OPC Server Configuration: Windows Utility, SNMP, DHCP Client, TFTP Server for firmware update Windows Utility: Block I/O Utility OPC Server Utility: OPC Server for Modbus/TCP SNMP: MIB-II: System, SNMP Trap and Private MIB SNMP Trap Server: Up to 4 SNMP Trap Server I/O Rules: High-/Low- Temperature alarms Power Requirements System Power: external unregulated +24V (18-32V) Power Consumption: Max. 2.88W Mechanical Dimensions : 120 (H) x 55 (W) x 75 (D)mm Mounting: Din-Rail Material: Aluminum Environmental Regulatory Approvals: CE, FCC Class A Operating Temperature: -25 ~ 70 C Operating Humidity: 0 ~ 95% non-condensing Storage Temperature: -40 ~ 80 C Warranty: 3 years 3

7 2 Hardware Installation This chapter includes hardware introduction, installation and configuration information. Following topics are covered in this chapter: 2.1 Hardware Introduction Dimension Appearance LED Indicators 2.2 Wiring Power Input 2.3 Wiring I/O Connectors 2.4 Wiring Ethernet Ports 2.5 DIN-Rail Mounting Installation 2.1 Hardware Introduction Dimensions: 120 (H) x 55 (W) x 75 (D) mm 4

8 JetI/O 6512 Appearance: LED Indicators: System LED PWR RDY Power Input plugged and On (Green) System startup ready (Red) Ethernet LED Upper (LAN Orange On & Blinking Activity) Lower(10M/100M) 10M (Green Off) /100M(Green ON 2.2 Wiring Power Input Follow below steps to wire JetI/O DC power inputs. 1. Follow the pin assignment to insert the wires into the contacts on the terminal block connector. 2. Tighten the wire-clamp screws to prevent DC wires from being loosened. 3. Connect to and turn on the power source. The suitable working voltage is 24VDC. 4. When the unit is ready, the PWR LED turns Greed, the RDY LED turns Red. Note1: It is a good practice to turn off input and load power, and to unplug power terminal block before making wire connections. Otherwise, your screwdriver blade can 5

9 inadvertently short your terminal connections to the grounded enclosure. Note 2: The range of the suitable electric wire is from 12 to 24 AWG. 2.3 Wiring I/O Connectors Follow the pin assignment to insert the wires into the front contacts on the terminal block connector. Tighten the wire-clamp screws to prevent the I/O wires from being loosened. The wiring diagram of the JetI/O 6512 is as below: Pin No Description Pin No Description EXC0+ CH0 RTD Excitation Current + EXC1+ CH1 RTD Excitation Current + SEN0+ CH0 Analog Input + SEN1+ CH1 Analog Input + SEN0 CH0 Analog Input - SEN1- CH1 Analog Input - EXC0- CH0 RTD Excitation Current - EXC1- CH1 RTD Excitation Current - AGND Analog GND AGND Analog GND EXC2+ CH2 RTD Excitation Current + EXC3+ CH3 RTD Excitation Current + SEN2+ CH2 Analog Input + SEN3+ CH3 Analog Input + SEN2- CH2 Analog Input - SEN3- CH3 Analog Input - EXC2- CH2 RTD Excitation Current - EXC3- CH3 RTD Excitation Current - AGND Analog GND AGND Analog GND 2.4 JetI/O 6512 Wiring Example JetI/O wire RTD input wiring example JetI/O wire RTD input wiring example 6

10 2.5 Wiring Earth Ground To ensure the system will not be damaged by noise or any electrical shock, we suggest you to make exact connection with JetI/O products with Earth Ground. On the bottom side of JetI/O 6500 Series, there is one power earth ground pin in the Power Input terminal block. Pin No 1(+24V) 2(FGND ) 3(0V) Description DC+24V Power Input Power Earth Ground Referenced Ground for Power Input 2.6 Wiring Fast Ethernet Ports JetI/O 6500 series includes 1 RJ45 Fast Ethernet ports. The fast Ethernet ports support 10Base-T and 100Base-TX, full or half duplex modes. The fast Ethernet port will auto-detect the signal from connected devices to negotiate the link speed and duplex mode. Auto MDI/MDIX allows users to connect another switch, hub or workstation without changing straight through or crossover cables. Connect one side of an Ethernet cable into the Ethernet port and connect the other side to the attached switch or host. The link LED will light up when the cable is correctly connected. Refer to the LED Indicators section for descriptions of each LED indicator. Always make sure that the cable length between the 2 ends is less than 100 meters (328 feet). The wiring cable types are as below. 10Base-T: 2-pair UTP/STP Cat. 3, 4, 5 cable, EIA/TIA ohm (100m) 100 Base-TX: 2-pair UTP/STP Cat. 5 cable, EIA/TIA ohm (100m) 1000 Base-TX: 4-pair UTP/STP Cat. 5 cable, EIA/TIA ohm (100m) 2.7 Din-Rail Mounting Installation The DIN-Rail clip is already attached to the JetI/O 6500 Series when packaged. If the DIN-Rail clip is not screwed on the JetI/O, follow the instructions and the figure below to attach DIN-Rail clip to JetI/O. Figure 1. Insert the upper end of DIN-Rail clip into the back of DIN-Rail track from its upper side. 7

11 b. Lightly push the bottom of DIN-Rail clip into the track. c. Check if DIN-Rail clip is tightly attached on the track. d. Korenix suggests reserve at least 5mm interval distance between the JetI/O devices. This is good for heat dispersing. e. To remove JetI/O 6500 from the track, reverse the steps above. 8

12 3 Preparation for Management Before you start to configure the JetI/O, you need to know the system architecture of the JetI/O products, configure the device s IP address, and then you can remotely manage the Ethernet I/O via the network. This chapter introduces the basic knowledge of the related technologies. Following topics are covered in this chapter: 3.1 Understand the Intelligent Ethernet I/O Server Architecture 3.2 Preparation for Remote Management 3.1 Understand the Ethernet I/O Server Architecture The Figure 1 shows the JetI/O Intelligent Ethernet I/O Server Architecture. In the top level shows the typical applications run in the remote I/O environment. The middle level is the Ethernet infrastructure. The low level, gray block include the software agent, signal types of the JetI/O 6500 series intelligent Ethernet I/O Server. Figure 1. The JetI/O Intelligent Ethernet I/O Server Architecture. 3.2 Preparation for Remote Management JetI/O 6500 series Intelligent I/O Server provides several types remote management methods. You can configure the JetI/O via the Ethernet network. You just need to know the device s IP address and then you can remotely control or monitor the I/O channels information. JetI/O provides several ways for users to configure the IP address. The default IP address is You can directly connect the JetI/O one after one to change its 9

13 IP address. Or connect the JetI/Os to the same switch or network, then the host PC can modify the IP address via the switch or network. If you purchase several JetI/Os and connect them to the same network before change their IP address. They must have the same default IP address, and you may not control them well due to the IP conflict. At this time, you should change their IP address first. The JetI/O Block I/O configuration utility and its Device Finder Popup Window can help you to do this. Note 1: Device Finder Popup Window allows you to discover the JetI/Os which have the same IP address. Change the IP address of the JetI/O one after one. After you configured the new IP address for the unit, please notice whether the ARP table of the device is flashed or not. If not, you can choose Start -> Run, type cmd to open the DOS prompt. Use arp d to clear the ARP cache. Note 2: After changed IP address or changed the DHCP client mode in Block I/O Configuration utility, the utility will automatically reboot the unit. Please rescan the devices after around 5 seconds. Note 3: You can find the detail progress in the next chapters. 10

14 4 Feature Configuration JetI/O 6500 series Industrial Managed Ethernet I/O module provides several configuration methods. This chapter introduces the configuration steps. Following topics are covered in this chapter: 4.1 Block I/O Configuration Utility 4.2 Block I/O OPC Server Utility 4.3 SNMP 4.4 Web UI 4.5 Modbus/TCP Command set Introduction of Modbus/TCP protocol JetI/O 6512 Modbus/TCP command set 4.1 Block I/O Configuration Utility Block I/O Utility is the major JetI/O Configuration Utility. With this tool, you can browse the available units, view the status of each channel, configure the I/O settings, configure active alarms and Conditions&Go logic rule Installation 1. Go to the Utility -> IO Configuration folder. Click Setup.exe to run the setup progress. 2. Click Next and type the Name and Company in the User Information window. Then click Next. 3. Choose the Destination Directory in the Choose Installation Location window. Then click Next. 11

15 4. Type the name for the Block I/O Configuration Utility or use the default name, Block IO Utility (Korenix) for the program in the Program Folder field of the Select Program Folder window. Then click Next. 5. Click Next in the Starting Copying File window to continue the setup progress. 6. As long as you see the Setup Complete window that means the progress is finished. Click Finish to exit the setup progress. 7. Go to Start -> Program, and then you can see the Block IO Utility (Korenix) folder. There are 2 utilities are installed, Block IO OPC Server and Block IO Utility. 12

16 4.1.2 Device Finder Device Finder helps you search JetIO 6500 devices on the same physical subnet, even if their IP addresses are conflit or if their IP address setting are not on the same subnet with your host PC. Device Finder also helps you configure the IP address and upgrade firmware of the found devices. Select the Device Finder icon launch Device Finder. from toolbar or select Tools Device Finder to Figure II. Click Search to search the JetI/O devices. You can see the available devices in the list. The following information is displayed: Item ID Model Name FW version MAC Description DHCP Current IP Addr Subnet mask Gateway Description index of the list JetIO model name The firmware version MAC address A short description of the device, max 16 characters DHCP client function status: Enable or disable If DHCP is enabled, dynamic IP is acquired from the DHCP server, Else, static IP is assigned as dynamic IP. Subnet mask Gateway IP address 2. Select the target unit and click Setup button to configure the device. Click Submit to apply the new setting. Note: When changing IP address, the new IP address and the NIC s (Network Interface Card) IP address should be located within the same subnet. 13

17 3. Select the target units and click Reboot to reboot the device. You can reboot one or multiple units in one time. 4. Select the target units and click Upgrade to upload the new firmware. Please refer to the section 4.4 to know the detail step by step progress. 5. Click Exit to exit the device finder tool. Note: Clear the ARP cache (arp d in DOS prompt) if you can t change the second unit s IP address. In DOS prompt, arp a can help you to see the ARP table. arp d can help you to clear all the ARPs in your host PC Device Scan 1. Lunch the Block IO Utility and then press Open to enable the network Interface. The square LED shows Green after you opened the interface. Click Close can close the network interface. 2. Click Scan to open the Scan Network Module(s) popup window. Click Scan to start the searching. 14

18 Note: Please modify the IP address of your target devices. The scan feature can t browse the devices which have the same IP address. Only one of the devices which have the same IP address can be found. This is the current restriction. Please modify the IP address first. You can use Block I/O Utility or Device Finder to do the IP modification. 3. Click Add to add the available JetI/O units. Then you can see the JetI/O units are listed in the left column. Figure 1. Move the mouse over to one of the JetI/O units. Select the unit then you can configure and monitor the configurations of the JetI/O. The features Block I/O Configuration utility provides are similar. Please find your model name and go to its configuration introduction chapter in below JetI/O 6512 Configuration Go to General page. Once you select one of the existing I/O modules in the Network interface tree, the main window defaults to the General page. 15

19 It should be noticed that the privilege setting is required to gain access to do the further configuration options. When you install the I/O module in first time, the default password is admin. You just need to click on Login button and type the password of Admin on password for entry field. If you want to make password changes, click Change button and then the dialog of Chang Password prompts you to update the new password with up to six characters. Note 1: The password protection is the new feature provided in firmware F206 and Utility V1.3 or later. Note 2: When you upgrade firmware from F204 to F206, the default password is disabled, please change new password for your device. Note 3: If you forget the password, you may need to reset the module via Modbus/TCP RESET command to clear the password and load factory defaults. This will result in the clear all the configuration settings as you assigned. Each module has its own page to display and configure the TCP/IP parameters. If the function of DHCP is disabled, user can type the IP address, Gateway and Subnet Mask information on the page. When everything is ok, user can push the Update button. This setting will be affected after restarting the module. 16

20 Note: After changed IP address or changed the DHCP client mode, the utility will automatically reboot the unit. Please rescan the devices after around 5 seconds Go to Data page. In this page, you could monitor the current working status of each channel on AI as well as the channels range configuration. Check Box Select the check box to monitor the info of the channel. Unselect the check box when you don t want to monitor it. Blinking The indicator in the bottom of the Data Area means the utility is monitoring the status of the channels. If there is error occurred, the color become to red or not light. 17

21 The s Range Configuration area, you can choose either Fixed input range on all channels or Individual input range on all channels. The factory default setting is Fixed input range on all channels. Just select the appropriate range from the Input range combo box and then click Update to take effect. If you want to set a different range for each channel, select the Individual input range on all channels, set the channel number in the index combo box, and then select the range in the Input range combo box. After selecting appropriate range, click the Apply button. For example, channel 1 with Ni Type meanwhile the others with Pt type. Note: The individual input range on the different channels is the new feature provided in hardware version Rev. B or later Go to Alarm page. In this page, you can setup the High/Low alarm value (Voltage or Current) for each channel and enable generic alarms (Device Cold Reboot, LAN Link Up). 18

22 Alarm : Select the channel. Alarm Mode: Enable or Disable High Alarm Value, Low Alarm Value: Type the value here. Update: Activate the new setting Go to Logic Rules page. In this page, you can configure the I/O logic rule. It allows you to define the logic operation and process rules in this utility and then download the rules to the I/O module. The module will automatically execute the logic rules to process different action depending on the input conditions as you defined. The theory is the same as the IF-Then rule. It s easy to understand rules, no need know extra program script to configure this. 19

23 Double click the Rule ID and then you can go to the Logic Rulle#ID Configuration page. Select Enable and configure the Condition and Actions then press Apply to enable the rule. Thus, when the Conditions is reached, the system automatically activates the Actives. For example: Rule Status Condition Action #1 Enable (AI-0 > 100) Flag-0 = ON #2 Enable (AI-0 100) Flag-0 = OFF 20

24 Rule #1: If condition is equal to (AI-0 > 100 degree), the Flag-0 is automatically ON. Again, configure the reverse way in the rule #2: If condition is equal to (AI degree), the Flag-0 is automatically OFF. In this meantime, the local internal flag, that says Flag-0, on the module can be mapping to remote digital outputs on different destination modules via. peer-to-peer I/O activity. The maximum I/O logic rules support up to 16. Each rule can support up to 4 different conditions and 4 different actions. There are 16 internal flags (i.e., auxiliary channels) on each module. The data type of internal flags is digital, meaning its value is either logic True or logic False. It allows you to choose these internal flags as input for condition rule as well as these flags as output for action state. Therefore, you could easy to use these internal flags to implement logic rule in cascade mode and mirror these flags to/from the remote modules via peer-to-peer I/O activity. The supported conditions and actions are as below: Condition ON, OFF, ON to Internal Flag Internal Flag OFF, OFF to ON Action ON, OFF Analog Input Relation between Conditions =, >, <,, (Number) OR, AND SNMP (Trap Server IP) After completing all configurations for I/O logic rule, click Save button in the bottom of the Logic Rules area. All the mapping configurations will be flushed into flash memory on the module. In order to extend the flash memory life, it is strongly recommended that you should save all configurations together at one time instead of saving individual setting many times Go to Peer to Peer I/O page. With peer to peer I/O activity, input channel status on one module could be actively updated to specific output channel on another module over the existing Ethernet connection. The above data exchange will be transferred automatically without any controller or programming needed. Each channel including all the internal flags on the source module can be mapping to channel including all the internal flags on different destination 21

25 modules. The Peer-to-Peer I/O activity on all the modules not only supports the one-to-one mapping but also multiple-to-one/from-one and one-to/from-multiple mapping simultaneously. The below will guide you on how to configure peer-to-peer functions step-by-step walkthrough. (1) Enable Peer to Peer I/O activity The Peer to Peer I/O activity is disabled by default. You could enable this function by checking Enable peer to peer I/O on this page. (2) Configure module s input channels mirrored to remote IP Select Mirror my input channels to:, the input channel status on the input module could be assigned to send those input data including all the internal flags to one remote destination IP address as defined on the field of Remote IP, e.g., as the above figure. (3) Configure module s output channels mirrored from remote IP Select Mirror my output channels from:, the output channel state on the output module could be mirrored from one remote input channels or internal flags on different destination modules. Click Rule and do the further assignments for those internal flags which will mirror the remote internal flags on the corresponding remotely input module as defined on the 22

26 field of Remote IP address. It could support up to 8 rules assignment. Press Apply to activate the new setting. After completing all configurations for Peer-to-Peer I/O activity, click Save button, all the mapping configurations will be flushed into flash memory on the module. In order to extend the flash memory life, it is strongly recommended that you should save all configurations together at one time instead of saving individual setting many times. The indicator in the left of the Save button shows the status of being flushed into flash memory. If there was error occurred, the color become to red. Otherwise, the system will automatically restart the module and prompt you to rescan the module on the network again. Refer to above Figure as below, in the bottom field of this Peer to Peer I/O page is the motoring area. It is monitoring the status both on peer-to-peer I/O activity and internal flags. Click Active Status button, the dialog of 23

27 peer-to-peer I/O active status will popup to represent the status code on peer-to-peer I/O activity. If there is error occurred, you could directly browse the latest activity from status code of peer-to-peer I/O activity. The status code is defined as below. Status Code Descriptions 0x0000 NO Errors 0x0001 Requested Content Not Satisfiable. That is, The content was well-formed but was unable to be followed due to non-satisfiable data. For example, module type associated with data format was NOT consistent. 0x0002 Remote Module Not Found 0xFFFF Not Enabled the Peer-to-Peer I/O Activity Click Internal Flag button, the internal flag dialog will prompt for you to browse all the internal flags. If you use internal flags as the inputs of logic rules and/or peer-to-peer I/O activity, you can dynamically change the flag values in the monitoring by double clicking the Flag# row as you selected, and then the flag values will be changed from True to False, or from False to True. 24

28 Go to SNMP page. IP Setting: You can configure up to 4 SNMP Trap Server s IP here. Type the IP address and press Update to activate the new setting. Click Refresh to reload the current SNMP trap server s IP from registers. Once the SNMP trap has been activated by I/O login rule, you need to press Reset to acknowledge it and then allow the next SNMP trap activity. The round LED shows green when press update and the setting is correct Emulation Mode Block I/O Configuration Utility provides Emulation mode that allows users to know the functions it supports, and good practice for users to know how to operate block I/O configuration utility even when users don t have physical devices on hand Select Tools -> Emulation. 25

29 Follow the to scan the network, you ll find the models JetI/O currently supported. Click Add to add the models Follow the to practice JetI/O configuration. Select the model and read or write status and configurations. As to how to operate the JetI/O configuration of other model, please refer to its manual Terminal Mode Block I/O Configuration Utility provides Terminal mode for user to read and write Modbus/TCP registers, thus users do not need additional tools but still can practice Modbus/TCP protocol well Open Terminal Mode. Click Open and then select Terminal. The terminal emulation popup screen appears. 26

30 Single Command mode. Type the correct IP address of target unit in IP Address field, PLC address in the Command field. Then click Enter key. You can read the Response of the PLC address. Note: If you type the wrong IP address, the utility will re-try the connection few times. This may take few seconds, please wait and close the popup alert screen and type the correct IP address again To read register, just type the PLC address. To write register, user needs to type the new value behind the PLC address. The example is 40001:1234 (ASCII word) or 40001:FF00h (16x Hex) Command File mode. Type PLC address you want read or write in the text file. Type the correct IP address of target unit in IP Address field. Browse the text file to load the file. Example: Write below commands in Modbus test.txt file and browse it Commands: Run Send to run the multiple commands. Run Stop to stop the program. Select Continue to run all commands once. Select Loop to continuously run all commands. The commands can be applied to Single Command mode and Command File mode. 27

31 The above screen shows you the result of running Modbus test.txt example in

32 4.2 Block I/O OPC Server Utility OPC Server Utility 1. Go to Start -> Program, and then you can see the Block IO Utility (Korenix) folder. There are 2 utilities are installed, Block IO OPC Server and Block IO Utility. 2. Open the Block IO OPC Server. 3. Select File -> New to create new profile. Or select File -> Open to open profile you saved. 4. Select Add -> New Device, the popup window Driver Selection will appear. (Only appear in the first time you add new device). Click Add and type the driver name and correct IP address. Click OK to next popup windows for Driver Selection. Use Edit -> Comm Setting can modify the parameters. Note: Different model should have different Driver Name. We recommend user add the entire driver for all the available models you connected first. 29

33 Figure 4.1 Add the New Device. Figure 4.2 Driver Selection Window. Click Add to next popup window. Figure 4.3 Ethernet Driver popup Window. Type the Driver Name and IP address for the device. Figure 5: Example: Add all the drivers for available models. If you have 5 models over the same network, add them and give them different name for identification in next steps. Like: (Model Name/6510)_(IP address/10). 30

34 5. Type the Device Name and select the Device Type and the Driver in the Device Properties window. Device Type means the JetI/O model name. Driver is the name you configured in last step. 6. Select Add -> New Group to create new group for the later new tags you ll create. Select Add -> New Tag and fill the Tag Properties in the popup window. Select the tag and Edit > Properties, you can modify the tag properties. Note: The Simulation Signal is used when choosing Simulate I/O mode. Simulate I/O mode is selected in Device Properties. This feature allows you to generate simulation values and run testing when you operate the OPC client. You can see the value is continuously changed. The Sine, Ramp and Random are the different type s simulation signal. 7. Select the device in the device list. Choose Add -> Generate Tags, the utility generate all the channels tags for the device you choose. This step can save the time to create all channels tags. 31

35 Name: The name of the channel. You can manually change this value. Type: The input type of the channel. : The channel ID. Value: The value of the channel, you can use Monitor to read them. Description: The description of this channel, you can manually change this value. 8. Select View -> Monitor to monitor the status of the tags. Or you can click the Monitor icon in the UI. 9. Select File -> Save to save the profile, then your OPC Client can monitor the Jet I/O status. 32

36 4.3 SNMP Simple Network Management Protocol (SNMP) is a protocol used for exchanging management information between network devices. SNMP is a member of the TCP/IP protocol suite. JetI/O 6500 series acts as SNMP node, SNMP browser can discover and read/write channels information. An SNMP managed network consists of two main components: agents and manager. An agent is a management software module that resides in a managed switch. An agent translates the local management information from the managed device into a SNMP compatible format. The manager is the console through the network. JetI/O 6500 series supports Public MIB: MIB II-System. This is for SNMP browser discovering. Private MIB includes channels information. Please refer to the appendix 1 (6.1). SNMP Trap allows the JetI/O to send the active alarm to trap servers. The SNMP Trap supports Device Cold Start, LAN interface Link Up trap (Common), Low and High Voltage/Current/Temperature (651x) and Logic Rules traps (655x). You can configure this through Modbus/TCP registers or I/O Configuration utility. 4.4 Web UI Type the IP address of the device. Then you can access the embedded web browser of the I/O server. The web browser allows you monitor the information/status of each channels. 4.5 How to Upgrade Firmware The JetI/O server allows you remotely upgrade the firmware to fix the known issues or to update the new software features. Device Finder provides a user-friendly environment for firmware upgrade, which includes two modes: 1. Mode A (Firmware Upgrade): Used to upgrade the firmware of a JetI/O module which is with valid firmware and workable. Device Finder supports batch upgrade in this mode. User can upgrade more than one JetI/O device (the same model) at the same time. 2. Mode B (Firmware Rescue): Used to reload the firmware of a JetI/O without firmware. When user starts the progress of the firmware upgrade, the JetI/O runs as the DHCP client mode to get the IP from DHCP Server and download the firmware from the server. Note 1: The progress is also known as BootP, Get IP address and upgrade new firmware in the same progress. Please note that there is only one DHCP server available over the same network. Otherwise the device may get the wrong IP. Since Device Finder builds in a BOOTP server, Korenix suggests you make sure there is only one DHCP/BOOTP server on the network when you upgrade the JetIO firmware. Upgrade Procedure for Mode A (Firmware Upgrade): 1. Lunch the Block I/O utility and then select the Device Finder from toolbar or select Device Finder from Tools menu to enable the Device Finder tool. 2. Press Search button to search all JetIO modules on the network and check the IP address (e.g ) of the JetIO target module. 33

37 Notes: (a). Disable Firewall (b). Enable only one network card on your PC I. Set a proper IP address with the same segment as the IP address of your PC (d). ON'T configure more than one IP address on the network interface. (e). Select a correct module firmware code (i.e., 6550_Fxxx.bin for JetIO 6550) 3. Select the target module and click Upgrade to upload the new firmware, and then the Firmware Upgrade dialog prompt you to do the further setting. 4. Select the JetIO target module from the device list of Device Finder console. You can select one more modules with the same model name to do batch upgrade. 5. Press Upgrade button to pop up the Firmware Upgrade dialog. 6. The default value of the Module IP Address field is the current IP address of the device. For batch upgrade, you do not need to change this field. 7. Press the browser button to select a correct firmware code. Please do not modify the filename. Device Finder uses the filename of the firmware to identify if the firmware matches the model of the JetI/O device. 8. Press Upgrade Firmware button to start upgrading the new firmware code. 9. The JetIO target module should be rebooted automatically after the new JetIO firmware code was upgraded successfully. Upgrade Procedure for Mode B (Firmware Resure): 1. Lunch the Block I/O utility and then select the Device Finder from toolbar or select Device Finder from Tools menu to enable the Device Finder tool. 2. A JetI/O with invalid firmware can not be found by search. Notes: (a). Disable Firewall (b). Enable only one network card on your I(c). Set a proper IP address with the same segment as the IP address of your PC (d. DON'T configure more than one IP address on the network interface. 34

38 (e). Select a correct module firmware code (i.e., 6550_Fxxx.bin for JetIO 6550) 3. Press Upgrade button to pop up the Firmware Upgrade console. 4. Set a proper IP address for JetIO module boot loader. Please note that the IP address should be set to the same network segment of your PC. 5. Press the browser button to select a correct JetIO firmware code. Please do not modify the filename. Device Finder uses the filename of the firmware to identify if the firmware matches the model of the JetI/O device. 6. Press Upgrade Firmware button to start upgrading the new JetIO firmware code. 7. Press Yes to start the progress when seeing the upgrading information popup window. Press No to stop the progress. 8. The JetIO target module should be rebooted automatically after the new JetIO firmware code was upgraded successfully. 4.6 Configuration Backup/Restore, Reset Default, and Reboot The backup/restore configuration functions are accessed by right clicking on a JetIO module in the network interface tree. 35

39 Select Backup Config. to and Restore Config. from command to backup and restore the configuration of the JetIO to/from a text file. It should be noticed that you will need to login first and then gain a privilege to do these functions. Click Reset to default and Reboot in the popup menu to set factory default or reboot the device. It should be noticed that you need to rescan network after completing the Reset to default and Reboot activity. Below is the related configuration information corresponding to JetIO s Modbus registers as well as module IP configuration for your reference (i.e., internally script command to implement backup and restore configuration activity). JetIO-6512 Module [Backup] 0=irange.conf 1=snmp.trap.ips 2=alarm.conf 3=mis 4=#ip.conf 5=#alarm.limit.conf [mis.plcaddr] 0=40001: =41000:

40 [irange.conf.plcaddr] 0= =40022 [snmp.trap.ips.plcaddr] 0=40024:40032 [alarm.conf.plcaddr] 0=40023 [ip.conf.program] key=ip.conf var0=ip.ip var1=ip.mask var2=ip.gateway var3=ip.dhcp [alarm.limit.conf.program] key=alm.limit var0=40014:

41 5 Modbus/TCP Command Set This chapter introduces the Modbus/TCP command set JetI/O provided. When you creating application for your SCADA/HMI or coding your own programs. The command set is helpful for you to find the value of each registers. Following topics are covered in this chapter: 5.1 Introduction of Modbus/TCP Protocol 5.2 JetI/O 6512 Modbus/TCP Address Mapping 5.1 Introduction of Modbus/TCP Protocol Modbus/TCP Protocol The Modbus protocol, developed by Gould-Modicon, is widely used in industrial communications to integrate PLC s, computer, terminals and other various I/O devices. Intelligent JetI/O Server equipped with communication interface provides an Ethernet communication links with Modbus/TCP protocol support. Modbus/TCP is a variant of the Modbus family of communication protocol. Modbus/TCP is a Master/Slave communication protocol. A master (a host PC) initiates queries, a slave (one of the JetI/O servers) then responds by supplying the requested data to the master by using Modbus/TCP commands Function Code (FC) The Intelligent JetI/O Server uses a subset of the standard Modbus/TCP function code to access device-dependent information. Modbus/TCP function code is defined as below. FC Name Usage 01 Read Coils Read the state of a digital output 02 Read Input Status Read the state of a digital input 03 Read Holding Register Read holding register in 16-bits register format 04 Read Input Registers Read data in 16-bits register format 05 Write Coil Write data to force a digital output ON/OFF 06 Write Single Register Write data in 16-bits register format 15 Force Multiple Coils Write data to force multiple consecutive coils Error Checking The utilization of the error checking will help eliminate errors caused by noise in the communication link. In Modbus/TCP mode, messages include an error-checking field that is based on a Cyclical Redundancy Check (CRC) method. The CRC filed checks the contents of the entire message. It applied regardless of any parity check method used for the individual BYTE actors of the message. The CRC value is calculated by the transmitting device, which appends the CRC to the message. The receiving device recalculates a CRC during receipt of the message, and compares the calculated value to the actual value it received in the CRC filed. 38

42 5.1.4 Exception Response If an error occurs, the slave sends an exception response message to master consisting of the slave address, function code, exception response code and error check field. In an exception response, the slave sets the high-order bit (MSB) of the response function code to one. The exception response codes are listed below. Code Name Descriptions 01 Illegal Function The message function received is not allowable action. 02 Illegal Data Address The address referenced in the data field is not valid. 03 Illegal Data Value The value referenced at the addressed device location is no within range. 04 Slave Device Failure An unrecoverable error occurred while the slave was attempting to perform the requested action. 05 Acknowledge The slave has accepted the request and processing it, but a long duration of time will be required to do so. 06 Slave Device Busy The slave is engaged in processing a long-duration program command. 07 Negative Acknowledge The slave cannot perform the program function received in the query. 08 Memory Parity Error The slave attempted to read extended memory, but detected a parity error in the memory. 5.2 JetI/O 6512 Modbus/TCP Address Mapping Note: Some of the results are using Hex (Ex: FF00H) mode, Signed (-1Iode... or others mode. This result depends on the value of the address. There are two types Modbus/TCP addresses. The protocol address is an address from 0000 to the last address of the function code you choose. The PLC address is the fixed address number of the function code. This is also defined in Modbus/TCP protocol. Please choose the type your application uses. Should you encounter problem on reading this, please contact our technical support engineer, korecare@korenix.com Protocol Address (Hex) JetI/O 6512 Common Register Map (Holding Registers, Function Code =03) PLC Address (Decimal) Access Description R/W (Read/Write) Host Watch-dog enable/disable R/W:AABB AABB:0000H AABB:FF00H (disable) (enable) R/W (Read/Write) Host Watch-dog cycle count R/W:AABB 39

43 AABB:0001H~00FFH (0.1*AABB)=Cycle Time (sec) R/W R: Read the host-watchdog status W: Reset the host-watchdog status R:AABB AABB:0000H (remote module OK) AABB:FF00H (host-watchdog fail) W: AABB AABB:FF00H(reset) R Read the firmware version R:AAAA AAAA: F203 (HEX) R Read module name R:AAAA AAAA: 6512 (HEX) R Read reset status R:AABB AABB:0000H ( after using this read command) AABB:0001H(The value is equal to0001h after reset module) R Read AD offset Calibration Coefficients R:AABB(bit 16~23) R Read AD offset Calibration Coefficients R:00AA(bit 0~15) R Read AD span Calibration Coefficients R:AABB(bit 16~23) R Read AD span Calibration Coefficients R:AABB(bit 0~15) 000A R/W Input code (address low) Code:20H~27H 20H: pt100 ( -100 ~ 100 α= ) 21H: pt100 ( 0 ~ 100 α= ) 22H: pt100 ( 0 ~ 200 α= ) 23H: pt100 ( 0 ~ 600 α= ) 24H: pt100 ( -100 ~ 100 α= ) 25H: pt100 ( 0 ~ 100 α= ) 26H: pt100 ( 0 ~ 200 α= ) 27H: pt100 ( 0 ~ 600 α= ) 28H: Nickel 120Ω( -80 ~

44 α= ) 000B R/W Offset (Zero) calibration (R: no used) W: AABB AABB:FF00H Note: timeout time 300 ms at least (Warning: You should calibrate the value for the selected input range by the certificated calibrator when need.) 000C R/W Span calibration (R: no used) W: AABB AABB:FF00H Note: timeout time 300 ms at least (Warning: You should calibrate the value for the selected input range by the certificated calibrator when need.) JetI/O 6512 Special Register Map (Holding Registers) 000D R/W Read/write 0 Low alarm value R/W:AABB 000E R/W Read/write 0 High alarm value R/W:AABB 000F R/W Read/write 1 Low alarm value R/W:AABB R/W Read/write 1 High alarm value R/W:AABB R/W Read/write 2 Low alarm value R/W:AABB R/W Read/write 2 High alarm value R/W:AABB R/W Read/write 3 Low alarm value R/W:AABB R/W Read/write 3 High alarm value R/W:AABB R/W Read/write masked AD-channels of the module R/W:AABB AA:00 BB:0000XXXX(Binary) X: 1 Enable X: 0 Disable R/W Enable / Disable alarm status R/W: 0000xxxx (Binary) 41

45 X : 1 Enable X: 0 Disable Least bit means the channel R/W Read/write SNMP Trap Number R/W:AAAA AAAA:0000~ : close SNMP trap R/W (Read/Write)SNMP Trap IP1 Lo-Word R: AABB(hex) W: AABB(hex) IP=X.X.AA.BB R/W (Read/Write)SNMP Trap IP1 Hi-Word R: AAB R/W B(hex) W: AABB(hex) IP=AA.BB.X.X 001A R/W (Read/Write)SNMP Trap IP2 Lo-Word R: AABB(hex) W: AABB(hex) IP=X.X.AA.BB 001B R/W (Read/Write)SNMP Trap IP2 Hi-Word R: AABB(hex) W: AABB(hex) IP=AA.BB.X.X 001C R/W (Read/Write)SNMP Trap IP3 Lo-Word R: AABB(hex) W: AABB(hex) IP=X.X.AA.BB 001D R/W (Read/Write)SNMP Trap IP3 Hi-Word R: AABB(hex) W: AABB(hex) IP=AA.BB.X.X 001E R/W (Read/Write)SNMP Trap IP4 Lo-Word R: AABB(hex) W: AABB(hex) IP=X.X.AA.BB 001F R/W (Read/Write)SNMP Trap IP4 Hi-Word R: AABB(hex) W: AABB(hex) IP=AA.BB.X.X 42

46 R/W (Write) Repeat enable SNMP Trap W: FF00(hex) R Read AD offset Calibration Coefficients R:AABB(bit 16~23) (factory calibration value) R Read AD offset Calibration Coefficients R:00AA(bit 0~15) (factory calibration value) R Read AD span Calibration Coefficients R:AABB(bit 16~23) (factory calibration value) R Read AD span Calibration Coefficients R:00AA(bit 0~15) (factory calibration value) 01F R/W (Read/Write) RuleEnable Logic 0~15 R: xxxxxxxxxxxxxxxx(bit) W: xxxxxxxxxxxxxxxx(bit) 0: disable 1: enable (write to Flash RAM) 01F R/W (Read/Write) RuleEnable Logic 0~15 R: xxxxxxxxxxxxxxxx(bit) W: xxxxxxxxxxxxxxxx(bit) 0: disable 1: enable (write to Flash RAM) 01F R/W (Read/Write) Select OR or AND R:AAAA(hex) W: AAAA (hex) AAAA:xxxxxxxxxxxxxxxx X: 0 OR Logic 1 AND Logic (write to Flash RAM) 01F R/W (Read/Write) Select condition AI channel (or Auxflag channel) for Rule 0 A: condition #3 Logic AI B: condition #2 Logic AI C: condition #1 Logic AI D: condition #0 Logic AI (write to Flash RAM) 01F R/W (Read/Write) Select condition AI channel (or Auxflag channel) for Rule 43

47 1 A: condition #3 Logic AI B: condition #2 Logic AI C: condition #1 Logic AI D: condition #0 Logic AI (write to Flash RAM) 01F R/W (Read/Write) Select condition AI channel (or Auxflag channel) for Rule 2 A: condition #3 Logic AI B: condition #2 Logic AI C: condition #1 Logic AI D: condition #0 Logic AI (write to Flash RAM) 01F R/W (Read/Write) Select condition AI channel (or Auxflag channel) for Rule 3 A: condition #3 Logic AI B: condition #2 Logic AI C: condition #1 Logic AI D: condition #0 Logic AI (write to Flash RAM) 01FA R/W (Read/Write) Select condition AI channel (or Auxflag channel) for Rule 4 A: condition #3 Logic AI B: condition #2 Logic AI C: condition #1 Logic AI D: condition #0 Logic AI (write to Flash RAM) 44

48 01FB R/W (Read/Write) Select condition AI channel (or Auxflag channel) for Rule 5 A: condition #3 Logic AI B: condition #2 Logic AI C: condition #1 Logic AI D: condition #0 Logic AI (write to Flash RAM) 01FC R/W (Read/Write) Select condition AI channel (or Auxflag channel) for Rule 6 A: condition #3 Logic AI B: condition #2 Logic AI C: condition #1 Logic AI D: condition #0 Logic AI (write to Flash RAM) 01FD R/W (Read/Write) Select condition AI channel (or Auxflag channel) for Rule 7 A: condition #3 Logic AI B: condition #2 Logic AI C: condition #1 Logic AI D: condition #0 Logic AI (write to Flash RAM) 01FE R/W (Read/Write) Select condition AI channel (or Auxflag channel) for Rule 8 A: condition #3 Logic AI B: condition #2 Logic AI C: condition #1 Logic AI D: condition #0 Logic AI 45

49 (write to Flash RAM) 01FF R/W (Read/Write) Select condition AI channel (or3auxflag channel) for Rule 9 A: condition #3 Logic AI B: condition #2 Logic AI C: condition #1 Logic AI D: condition #0 Logic AI (write to Flash RAM) R/W (Read/Write) Select condition AI channel (or Auxflag channel) for Rule 10 A: condition #3 Logic AI B: condition #2 Logic AI C: condition #1 Logic AI D: condition #0 Logic AI (write to Flash RAM) R/W (Read/Write) Select condition AI channel (or Auxflag channel) for Rule 11 A: condition #3 Logic AI B: condition #2 Logic AI C: condition #1 Logic AI D: condition #0 Logic AI (write to Flash RAM) R/W (Read/Write) Select condition AI channel (or Auxflag channel) for Rule 12 A: condition #3 Logic AI B: condition #2 Logic AI 46

50 C: condition #1 Logic AI D: condition #0 Logic AI (write to Flash RAM) R/W (Read/Write) Select condition AI channel (or3auxflag channel) for Rule 13 A: condition #3 Logic AI B: condition #2 Logic AI C: condition #1 Logic AI D: condition #0 Logic AI (write to Flash RAM) R/W (Read/Write) Select condition AI channel (or Auxflag channel) for Rule 14 A: condition #3 Logic AI B: condition #2 Logic AI C: condition #1 Logic AI D: condition #0 Logic AI (write to Flash RAM) R/W (Read/Write) Select condition AI channel (or Auxflag channel) for Rule 15 A: condition #3 Logic AI B: condition #2 Logic AI C: condition #1 Logic AI D: condition #0 Logic AI (write to Flash RAM) R/W (Read/Write) Select Operators condition for Rule 0 A: Operators condition #3 Logic 47

51 B: Operators condition #2 Logic C: Operators condition #1 Logic D: Operators condition #0 Logic Value: 0 : ON (Auxflag) 1:OFF (Auxflag) 2:Lo-Hi (Auxflag) 3:Hi-Lo (Auxflag) 4: = (AIValue = SetAIValue) 5: > (AIValue > SetAIValue) 6: < (AIValue < SetAIValue) 7: >= (AIValue >= SetAIValue) 8: <= (AIValue <= SetAIValue) (write to Flash RAM) R/W (Read/Write) Select Operators condition for Rule 1 A: Operators condition #3 Logic B: Operators condition #2 Logic C: Operators condition #1 Logic D: Operators condition #0 Logic Value: 0 : ON (Auxflag) 1:OFF (Auxflag) 2:Lo-Hi (Auxflag) 3:Hi-Lo (Auxflag) 4: = (AIValue = SetAIValue) 5: > (AIValue > SetAIValue) 6: < (AIValue < SetAIValue) 7: >= (AIValue >= SetAIValue) 8: <= (AIValue <= SetAIValue) (write to Flash RAM) R/W (Read/Write) Select Operators condition for Rule 2 A: Operators condition #3 Logic 48