Arctic P - Series User Manual. Arctic Protocol Gateway (P-2220, P-2250, P-2260)

Transcription

1 Arctic P - Series User Manual (P-2220, P-2250, P-2260) May 2015

2 Copyright and Trademark Copyright , Viola Systems Ltd. All rights to this manual are owned solely by Viola Systems Ltd. (referred elsewhere in this User s Manual as Viola Systems). All rights reserved. No part of this manual may be transmitted or reproduced in any form or by any means without a prior written permission from Viola Systems. Viola Systems Ltd. Lemminkäisenkatu B FI Turku Finland info@violasystems.com Technical Support Phone: Fax: support@violasystems.com Internet: 2

3 Disclaimer Viola Systems reserves the right to change the technical specifications or functions of its products or to discontinue the manufacture of any of its products or to discontinue the support of any of its products without any written announcement and urges its customers to ensure that the information at their disposal is valid. Viola software and programs are delivered as is. The manufacturer does not grant any kind of warranty including guarantees on suitability and applicability to a certain application. Under no circumstance is the manufacturer or the developer of a program responsible for any damage possibly caused by the use of a program. The names of the programs as well as all copyrights relating to the programs are the sole property of Viola Systems. Any transfer, licensing to a third party, leasing, renting, transportation, copying, editing, translating, modifying into another programming language or reverse engineering for any intent is forbidden without the written consent of Viola Systems. Viola Systems has attempted to verify that the information in this manual is correct with regard to the state of products and software on the publication date of the manual. We assume no responsibility for possible errors which may appear in this manual. Information in this manual may change without prior notice from Viola Systems. 3

4 Declaration of Conformity (according to ISO/IEC Guide 22 and EN 45014) Manufacturer s Name: Viola Systems Ltd. Manufacturer s Address: Lemminkäisenkatu B FI Turku Finland declares that this product: Product Name: conforms to the following standards: EMC: IEC (Edition ) 1. CISPR : Radiated Disturbance 2. CISPR : Conducted Disturbance IEC Immunity Tests 1. EN ( ): Electrostatic Discharge (ESD) 2. EN ( ): Radiated Radio-Frequency Electromagnetic Field 3. EN ( ): Electrical Fast Transient (EFT) 4. EN ( ): Surge 5. EN ( ): Conducted Radio-Frequency Electromagnetic Field Supplementary Information: The product complies with the requirements of the Low Voltage Directive 73/23/EEC and EMC directive 89/336/EEC.! This is a Class A product. In a domestic environment this product may cause radio Interference which may make it necessary for the user to take adequate measures. Manufacturer s Contact Information: Viola Systems Ltd. Lemminkäisenkatu B FI Turku Finland Phone: Fax:

5 Warranty and Safety Instructions Read these safety instructions carefully before using the products mentioned in this manual: Warranty will be void if the product is used in any way in contradiction with the instructions given in this manual or if the product has been tampered with. The devices mentioned in this manual are to be used only according to the instructions described in this manual. Faultless and safe operation of the devices can be guaranteed only if the transport, storage, operation and handling of the devices is appropriate. This also applies to the maintenance of the products. To prevent damage both the product and any terminal devices must always be switched OFF before connecting or disconnecting any cables. It should be ascertained that different devices used have the same ground potential. Before connecting any power cables the output voltage of the power supply should be checked. This product is not fault-tolerant and is not designed, manufactured or intended for use or resale as on-line control equipment or as part of such equipment in any hazardous environment requiring fail- safe performance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic control, direct life support machines, or weapons systems, in which the failure of Viola Systems manufactured hardware or software could lead directly to death, personal injury, or severe physical or environmental damage. 5

6 Revisions Date Document version 05/ Firmware version Description of changes Manual released 6

7 Contents COPYRIGHT AND TRADEMARK... 2 DISCLAIMER...3 DECLARATION OF CONFORMITY... 4 WARRANTY AND SAFETY INSTRUCTIONS...5 REVISIONS INTRODUCTION About this User s Manual...9 Arctic P-series Protocol Gateways PHYSICAL INTERFACES Front Panel Description...10 Back Panel Description Side Panel Description...14 Product Information Label...15 Firmware Version QUICK INSTALLATION Connection Principle...16 Connecting cables Logging in to Arctic Setting Ethernet port function to LAN Configuring Mobile WAN (cellular network interface) Configuring default gateway NETWORK CONFIGURATION Configuration screens Host and domain names Ethernet WAN Mobile WAN WAN Failover and backup routing settings Ethernet LAN Network monitor Routing Routing parameters Default route WAN redundancy/failover Routing serial <-> Ethernet...26 Network services DNS proxy...26 Network status information System status screen Mobile WAN status LEDs Modem info screen SERIAL PORT CONFIGURATION Configuring a serial port...29 Configuring serial gateway

8 6. ADDITIONAL SYSTEM CONFIGURATION Changing system password Date and time...30 System log...31 Factory default settings Firmware update...31 Configuration profiles IEC-104 APPLICATION SETTINGS General settings Serial settings Network settings IEC-104 Settings IEC-101 settings ASDU Converter...43 Packet collector Other settings MODBUS APPLICATION SETTINGS Introduction Parameters Common parameters Routes Configuring Network Master to Serial Slaves Mode Settings Common parameters Configuring Serial Master to Network Slaves Mode Settings Common Parameters Settings Routes TROUBLESHOOTING...64 SPECIFICATIONS LIMITED WARRANTY TECHNICAL SUPPORT

9 1 Introduction 1.1 About this User s Manual This User s Manual describes the operation of the. All devices in this User s Manual are referred to as Arctic, unless otherwise mentioned. This manual provides introductory information as well as detailed instructions on how to set up and manage the Arctic as part of a network environment. It is intended for anyone involved in installing and managing Arctic devices. It is assumed that the reader of this manual is familiar with basic working principles of Internet technology. Figure Arctic P-series Protocol Gateways The Arctic P-series product family includes a number of Arctic protocol gateway product variants. Arctic protocol gateways provide highly robust network components for rugged industrial environments, ease of use, and proven long-term field operation. Arctic protocol gateways make it possible to have a cost-effective communication system over long distances, at high data rates (up to 100 Mbps) and with integrated protocol conversion support. The protocol conversion feature means that the IEC-101 or Modbus RTU serial devices can be attached to a modern TCP/IP based IEC-104 or Modbus TCP SCADA system. 9

10 2 Physical Interfaces The Arctic unit contains three panels for interface connections and status indication. 2.1 Front Panel Description The front panel of the Arctic consists of the following connectors and switches: Figure 2. Front Panel Description 1. Power supply connector 2. Console serial port (RS1) 3. Power switch 4. Console switch 5. DIP switches 6. Application serial port (RS2) 7. Ethernet connector The Arctic has rails to enable wall or DIN rail mounting. The front panel contains slots for nuts or other mounting accessories (optional) in order to gain access to these rails. Power Supply Connector The Arctic has a VDC power supply connector as shown in the figure below. 10

11 Figure 3. Power supply connector Pin 1 is positive (+) Pin 2 is negative ( ) The unit is protected against reversed polarity in specified voltage range. Power Switch Enables or disables the operation of the Arctic. Console Enable Switch Enables or disables console access. When it is disabled, both serial ports may be used as an application serial port. When the switch is in the right position, RS1 is in serial port mode and when in the left position, RS1 is in console mode. DIP Switches It selects an application port (RS-2) mode and settings (RS-232 or RS-485). By default all are set to 0 when the port is acting as an RS-232. DIP switches 2-4 apply only when RS-485 mode is selected by DIP switch 1. Table 1: DIP Switches Number Function State Explanation 1 0 = RS-232 Selects RS-port operation RS-232/RS = RS HALF/FULL 0 = full Selects between half-duplex (2-wire) and full-duplex (4-wire) 1 = half 3 BIAS 0 = OFF RS-485 biasing 1 = ON 4 TERMINATION 0 = OFF RS-485 termination 1 = ON Serial Ports (RS-232, RS-422/485 -connectors) Arctic has two serial port connectors. These are 9-pin male connectors (DB9). A null modem cable (product code: 3100) may be used to connect the Arctic to a PC. The Arctic supports CTS/RTS flow control. The figure of Arctic s DB9 (DTE) Male connector is shown in the figure below. 11

12 Figure 4. DB9 male connector The serial port 1 (RS1) is a full RS-232 port. The pin description of this port is as follows: Table 2: RS-232 Port PIN Description Pin Number Name Direction Explanation 1 DCD IN Data Carrier Detect 2 RXD IN Received Data 3 TXD OUT Transmitted Data 4 DTR OUT Data Terminal Ready. Handshake output 5 GND - Signal ground. 6 DSR IN Data Set Ready. Handshake input 7 RTS OUT Ready To Send. Handshake output 8 CTS IN Clear To Send. Handshake input 9 RI IN Ring Indicator The serial port 2 (RS2) can be configured either as a half RS-232 or an RS-422/485 (DTE Master). The Pin description is same as in RS1, when in RS-232 mode. The pin description of this port is as follows in RS-485 mode. Table 3: RS-485 Port PIN Description Pin Number RS-485,Full duplex (4-wire) RS-485 Half duplex (2-wire) 1 NC NC 2 RXD+ (in) NC 3 TXD (out) TXD/RXD- (out/in) 4 NC NC 5 GND GND 6 NC NC 7 TXD+ (out) TXD/RXD+ (out/in) 8 RXD (in) NC 9 NC NC! Make sure that you DO NOT connect RS-422 or RS-485 devices to a port which has been configured to operate as an RS-232 port. Ethernet Connector Arctic has an RJ45 connector for 10/100 Mbps Ethernet connection. Maximum length of the Ethernet cable is 100m. 12

13 The figure and pin description of the Arctic s RJ45 Ethernet connector is as follows: Figure 5. RJ45 Ethernet connector Table 4: RJ45 Ethernet connector PIN Description 2.2 Pin Number Name Direction Explanation 1 Rx+ IN Data Receive Positive 2 Rx IN Data Receive Negative 3 Tx+ OUT Data Transmit Positive 4 NC NC Tx OUT Data Transmit Negative 7 NC NC - - Back Panel Description The Arctic has an antenna connector and a slot for a SIM card on the back panel. Figure 6. Back Panel 13

14 1. SMA (female) connector for an antenna. 2. SIM Card slot. 2.3 Side Panel Description The side panel of the device contains ten LEDs which are used to indicate the status of the Arctic and only five of them are connected. The LEDs are numbered from 1 to 10 starting from the rear panel side. A detailed description of each LED is listed below: Figure 7. LED Description Table 5: LED Description LED LED Number 1 Battery 2 Status Power/Error System Eth 1 State Description Not connected ON VPN connection is up Blinking VPN onnection is starting OFF VPN connection is disabled ON Operating power is turned on OFF Operating power is turned off ON Device is starting Blinking Device is operating normally ON Ethernet link is up Blinking Ethernet link is transferring data OFF Ethernet link is down Eth 2 Not connected 14

15 LED LED Number 2.4 State Description 7 LED 1 Not connected 8 LED 2 Not connected 9 LED 3 Not connected 10 LED 4/GPRS Blinking Wireless communication is starting or transferring data OFF Wireless communication is inactive Product Information Label The product information label on the underside of the Arctic contains the following information: 1. Product type 2. Serial number 3. MAC address The Ethernet address (MAC address) of the unit is printed on the product label. Each address code starts with the digits 00:06:70, but the remaining six digits are unique for each unit. Figure 8. Product Information Label 2.5 Firmware Version The Arctic firmware version may be checked from the welcome page ( Log in the device > Welcome ). 15

16 3 Quick Installation 3.1 Connection Principle The Arctic has configurable network interfaces, Ethernet WAN or Ethernet LAN port for a cable network, and Mobile WAN for wireless communication. The WAN interfaces are used for connecting the Arctic to public Internet or private APN. Ethernet LAN is used for connecting other Ethernet devices to the Arctic's local network. The WAN interfaces can be configured to get redundant system where one WAN automatically gets traffic if the other one goes down. For example, if the primary Ethernet connection goes down, the traffic is automatically switched to mobile WAN (secondary connection) and back when the Ethernet interface comes up again. This way the availability of the remote system is better than with just one interface. 3.2 Connecting cables 1. Verify that the power switch is in the OFF position. 2. Connect the Ethernet cable between Arctic (Ethernet LAN connector) and the computer used for the configuration. 3. Connect power supply to Arctic and toggle the power switch to ON position. 4. The power/error LED and function LED should turn on immediately after the power switch is turned on. 5. After the system has initialized, the function LED starts to blink. 3.3 Logging in to Arctic This section describes how to log in to Arctic using web configuration menu. 16

17 1. Configure the computer to use the same IP address space as the Arctic (laptop IP for example with netmask ). Check with ping command. 2. Connect to the Arctic using the web browser. The default IP address of Arctic is (netmask ). Please make sure to connect to a HTTPS port (see the figure below). Figure 9. Browser https example! You can ignore the browser's warning about a self-signed certificate. 17

18 3. Enter the username and password and press Login button in the log-in screen. The actual screen depends on the used web browser.! Default username is viola-adm and default password is violam2m. It is recommended that the default password is changed before the product is connected to a public network. 4. White texts on the blue background on the left are the primary navigation texts and they are always visible on the screen. Individual screens may have their own tabs which split the configuration fields on larger screens. See the figure below. Figure 10. Configuration menu 3.4 Setting Ethernet port function to LAN Disable automatic IP address detection by changing the port function to LAN. If the Port function is at the default setting of auto, the Ethernet LAN port tries to automatically obtain the IP address using DHCP when the device boots. If the DHCP discovery fails, the Arctic automatically uses IP address

19 ! Make the following change before changing any other Ethernet settings. 1. In the left pane, select Network > Ethernet Port. 2. Change Port function to LAN. 3.5 Configuring Mobile WAN (cellular network interface) The Mobile WAN interface is used for connecting the Arctic to a cellular network. The Arctic can use a GPRS (2G), UMTS (3G) or LTE (4G) cellular network connection depending on the product model. Install the SIM card before configuring the Mobile WAN. See Back Panel Description on page 13 for the location of the SIM card slot. 1. Select Network > Mobile WAN from the left menu. 2. Enter the preferred configuration to the configuration fields. 3. Press Submit on the bottom to save the settings. 3.6 Configuring default gateway 1. Select Network WAN Failover from the left menu. 2. Set "WAN Default Route"="Yes". This has to be enabled to use either WAN as default route interface. 3. If the mobile WAN has to be set as a default gateway, set "Primary WAN Interface"="Mobile WAN". This is a typical setting. 4. If Ethernet WAN has to be set as a default gateway: a) Select Network > Ethernet port settings > WAN. b) Set "PrimaryWAN Interface"="EthernetWAN" 19

20 5. If both Ethernet WAN and Mobile WAN configured, define the Backup WAN Interface. If the primary WAN interface comes down, the Arctic automatically switches default route to backup WAN interface. The figure below shows example configuration where Ethernet WAN is configured as default route. Figure 11. Ethernet WAN default route example 6. Press Submit on the bottom to save the settings. 7. Select Tools > Reboot from the left menu and press Reboot button to restart the unit. 20

21 4 Network Configuration This chapter describes how to configure network interfaces Configuration screens Host and domain names Host and domain names can be set from the System General Settings screen. Figure 12. General Settings Ethernet WAN This screen configures the Ethernet WAN interface on Arctic. Figure 13. Ethernet WAN configuration Connectivity Monitor settings are used when WAN redundancy functionality is required. Monitor keeps checking the connection to the given remote host to determine the network status. If the ping does not get an answer for a given time window, it informs the WAN switch logic to try the secondary interface. If the WAN redundancy is implemented by using two separated Ethernet connections with different gateways, the Backup Gateway parameter needs 21

22 to be configured towards the correct backup gateway. Backup Gateway parameter is not needed if WAN redundancy is implemented with wireless connection. See section WAN Failover and backup routing settings on page 23 for more details about WAN redundancy Mobile WAN This screen configures the Mobile WAN interface on the Arctic. The configuration screen fields are described below. PIN code The 2G/3G/LTE cellular networks use a SIM card. The SIM card can be protected by PIN code (personal identification number). If the PIN code is used, it must be entered to Arctic s Mobile WAN settings. Leave the PIN code field empty if no PIN code is used. If a wrong PIN code is entered, correct the code and enter the correct PIN code to the SIM by using a mobile phone. APN By default automatic APN discovery is used. Arctic tries default APN values based on network ID received from cellular network. If automatic settings do not work, set to APN parameter from Automatic to Manual. APN The APN parameter defines the cellular access point name. If APN is set to Manual the access point works as a gateway from the cellular network to internet. There are public and private access points. A public access point is usually defined. A private access point requires contract with a cellular operator. Viola M2M solution is compatible with both public and private access points. Define the access point name as according to information received from the cellular operator. Authentication, username, password If the cellular network requires authentication for using the access point, the access point s username and password need to be defined in the Arctic. In this case, select the authentication type (PAP, password authentication protocol or CHAP, challenge handshake authentication protocol) as according to information received from the cellular operator. DNS selection, DNS servers Allows user defined DNS servers, receiving DNS server IP addresses from cellular network or leaving DNS configuration as disabled. The DNS 22

23 servers are used for resolving names to IP addresses. Figure 14. Mobile WAN configuration To configure the mobile WAN, enable the connection by selecting "Enable"="Yes" on the top of the page and enter PIN code if set, APN name and authentication details if needed. If the Arctic acts as a wireless router to Ethernet devices and DNS is needed, enter DNS configuration as well. When ready, press the Submit button on the bottom of the page to save settings. The Arctic need to be restarted before the mobile WAN configuration is active WAN Failover and backup routing settings WAN Failover screen configures the default gateway settings on the Arctic. 23

24 Figure 15. WAN Failover configuration To enable any default routes, set "WAN Default Route"="Yes". Any route settings are not effective if this parameter is not enabled. Set "On Demand"="Yes" if the backup WAN interface to come up only when primary interface goes down. Disable if both wireless and wired WAN interfaces have to be up all the time Ethernet LAN This screen configures the Ethernet LAN interface on the Arctic. Figure 16. Ethernet LAN Configuration Network monitor This screen configures the interface connectivity monitor on Arctic. 24

25 Figure 17. Network monitor configuration The usage of the monitor is heavily recommended to detect the connection drops Routing Routing parameters There are multiple configuration options that define the routing on Arctic : Ethernet WAN - Gateway (IP address) IP address of router used to reach the internet. Leave empty if unused. WAN Failover - WAN Default Route (selection: Yes/No) Usually "Yes" if default route is defined by "static routes". If the selection logic is done on VPN level select "No" WAN Failover - On Demand (selection: Yes/No) Select "Yes" to activate the backup interfaces only when required. Select "No" to have all the WAN interfaces to be available simultaneously for e.g. VPNs. WAN Failover - Primary WAN Interface (selection: None/Mobile WAN/ Ethernet WAN/Ethernet WAN Secondary) WAN Failover - Backup WAN Interface(selection: None/Mobile WAN/ Ethernet WAN) 25

26 4.2.2 WAN Failover - Secondary Backup WAN Interface (selection: None/Mobile WAN/Ethernet WAN/Ethernet WAN Secondary) These three settings configure the high level default gateways. Must be configured to enable default route. OpenVPN Client Settings - Interface (selection: Any WAN/Ethernet WAN/ Wireless WAN/Ethernet LAN) Which Interface to use for connection OpenVPN Client Settings - Routing mode (selection: None/host/net/default route) This defines how the routing is configured with OpenVPN. See OpenVPN application note. Default route Default route can be configured from WAN Failover screen. See section WAN Failover and backup routing settings on page WAN redundancy/failover To configure redundancy between WAN interfaces, configure multiple WAN interfaces to WAN Failover. See section WAN Failover and backup routing settings on page Routing serial <-> Ethernet See section Serial Port Configuration on page Network services DNS proxy To use this feature, configure the device to use Arctic Ethernet LAN IP address as its DNS server. This way, the DNS queries from the device get routed through the Arctic Network status information System status screen Network status information can be seen from System > Status screen. 26

27 Figure 18. Network status screen Mobile WAN status LEDs See Table 5: LED Description on page COM LED starts to blink when the connection is started. 2. SIM LED starts to blink when SIM card is searched and turns on when the card is found and PIN code accepted. 3. SIM LED starts to blink when the operator network is searched and gets lit when the network is found. 4. COM LED gets lit when the connection is up Modem info screen In troubleshooting situations, checking the system logs helps to identify the problem. Also modem info page can be used to check the status of the wireless modem. 27

28 Figure 19. Modem info screen 28

29 5 Serial Port Configuration 5.1 Configuring a serial port The Arctic P-series supports the following serial port application modes: Application Mode Description Serial device protocol Serial Gateway Transparent connection to any serial device N/A IEC-104 IEC-101 to IEC-104 conversion IEC-101 Modbus Modbus conversion Modbus/RTU or Modbus/ ASCII 1. Select Serial Port and I/O > Serial Port Configuration. 2. Select the serial port mode. 5.2 Configuring serial gateway This section describes how to configure serial <-> IP functionality. The serial gateway feature enables data from the serial port attached device to be routed to Ethernet/mobile network (serial over IP) and vice versa. Serial gateway processes the transmitted data transparently and does not alter it any way except for buffering it for transmission. Because of the transparent communication, any protocols can be used in actual communication between nodes. Figure 20. Serial gateway configuration screen Serial gateway configuration depends on used protocols. 29

30 6 Additional System Configuration 6.1 Changing system password Username and password can be changed from Tools > User Config screen. It is always recommended to change the password from the factory default when the Arctic is connected to a public network. Figure 21. User Config screen 6.2 Date and time Date and time can be changed from System > Time screen. Date and time can be configured either manually entering the time or automatically from connected PC. Figure 22. System time configuration screen, automatic setting Figure 23. Manual setting To set time manually, enter the time and then press Submit button. To copy time from PC, press Copy PC button and answer "Yes" to question about changing time. that the PC may not necessarily have correct time set and that needs validation. Also note that the copy functionality requires JavaScript support from the browser. 30

31 6.3 System log System log is visible on the Tools > System Log screen. To refresh the system log, use web browser reload button. 6.4 Factory default settings Factory default settings can be applied by restarting the unit pressing down reset button until the LEDs blink. To restore factory default settings, go to Tools > Default settings. 6.5 Firmware update Create a backup of the current configuration starting the firmware update. Current running firmware version can be viewed from the System > Status screen. Arctic firmware can be updated in the Tools > Firmware Update screen. Figure 24. Firmware update screen 1. Verify for a valid firmware on the PC before attempting to update the firmware. 2. Select Select file button to open file browsing dialog. The actual dialog depends on the used browser. 3. Select the updated firmware from the file dialog and return to the firmware update screen. 4. Press Update button to start the firmware update. 5. Confirm the update. The update takes a few minutes. 6. Once the update is finished, restart the device. 6.6 Configuration profiles Profiles can be configured and saved for future use. Several profiles are created and selected for the activation. It is possible to import, export and clone profiles, and also reset them to factory default settings. 31

32 Figure 25. Configuration profiles 32

33 7 IEC-104 application settings The IEC-104 and IEC-101 protocols share the same ASDU level messaging but differ on the link level. The IEC-104 is intended for packet-switched TCP/ IP communication whereas the IEC-101 is intended for serial communication. By using the Arctic, the IEC-101 slaves (e.g. RTUs) can be connected to a IEC-104 master (e.g. SCADA). The Arctic requests event from the IEC-101 slave locally and sends them to the IEC-104 master. This eliminates the need to continuously poll the data remotely and therefore reduces the communication costs on pay-per-use wireless network. This approach also eliminates the IEC-101 parameter adjutancy problems caused by variable round-trip delays on wireless networks and makes the information exchange faster and more reliable. You can view and change the application settings in Serial Port and I/O > IEC-104 Gateway (RSx). Figure 26. IEC-104 Application Settings 33

34 7.1 General settings IEC-104 gateway enabled Enables or disables IEC-104 to IEC-101 gateway functionality. Table 6: IEC-104 gateway enabled IEC-104 gateway enabled Boolean N/A Value range No, Yes 7.2 Serial settings The serial settings define the properties of physical serial communication between the Arctic and an IEC-101 slave. The selection between RS-232/422/485 is done with physical DIP switches located below the RS2 serial port. Figure 27. Serial Settings Speed (bps) Table 7: IEC-101 serial communication speed (bps) IEC-101 serial communication speed (bps) Serial speed Bits per second Value range 1200, 2400, 4800, 9600, 19200, 38400, Data bits Table 8: Number of data bits used on IEC-101 serial communication Number of data bits used on IEC-101 serial communication Serial data bits Bits 34

35 Number of data bits used on IEC-101 serial communication Value range 5, 6, 7, 8 Parity Table 9: Parity method used on IEC-101 serial communication Parity method used on IEC-101 serial communication Serial data parity Bits Value range None, Even, Odd Stop bits Table 10: Number of stop bits used on IEC-101 serial communication Parity method used on IEC-101 serial communication Serial data stop bits Bits Value range 1, 2 Use HW flow control Table 11: Number of stop bits used on IEC-101 serial communication HW flow control mechanism (RTS/CTS) on IEC-101 serial communication 7.3 Boolean N/A Value range Yes, No The HW handshaking is available only on RS-232 mode. Network settings The Network settings define the general TCP/IP networking properties between the Arctic and the IEC-104 master. Figure 28. Network Settings 35

36 Network protocol Network protocol defines the network transmission layer protocol (either TCP or UDP) used on IEC-104 network communication. The IEC-104 standard protocol uses TCP but for reliable slow speed packet switched networks (e.g. Mobitex), the UDP protocol can be used to minimize the packets transmitted over network. Table 12: Network protocol on IEC-104 communication Network protocol on IEC-104 communication Network transmission layer protocol N/A Value range UDP, TCP The IEC-104 standard specifies only TCP protocol. Network port to listen Table 13: TCP or UDP port to listen for incoming IEC-104 connections TCP or UDP port to listen for incoming IEC-104 connections Network port Port number Value range The IEC-104 standard specifies TCP port Network idle timeout It defines the idle timeout of the network connection in seconds. If there is no network data received during the specified interval, the connection is closed by Arctic. This parameter is required in order to detect partially closed connections and release the resources for new connections especially if the New connection priority parameter is disabled. Value 0 disables the network idle timeout detection. Table 14: Network idle timeout for IEC-104 connections Network idle timeout for IEC-104 connections Timeout Seconds Value range The network idle timeout must be longer than IEC-104 link test interval (t3). New connection priority It defines the action when a new connection request arrives while a connection is already active. If the set value is No, the new connection is rejected. If the set value is Yes, the present connection is terminated and the new connection is accepted. 36

37 Table 15: New connection priority for IEC-104 connections New connection priority for IEC-104 connections 7.4 Boolean N/A Value range No, Yes It is recommendable to set this value to Yes in normal configurations having only one IEC-104 master. IEC-104 Settings The IEC-104 settings define the properties of IEC-104 link layer and application layer parameters as described in the IEC standard. The IEC-104 communication is carried out between the Arctic and the IEC-104 master over the TCP/IP network. Figure 29. IEC-104 Settings TX window size (k) TX window size defines the maximum number of I format APDUs the Arctic may send before requiring the IEC-104 master to acknowledge them. If there are k unacknowledged frames sent the Arctic will stop polling IEC-101 slave for events until acknowledgement is received. Table 16: IEC-104 TX windows size (k) IEC-104 TX windows size (k) Window size Packets Value range 1-20 The k must be always less than the maximum sequence number defined below. The IEC-104 standard suggests k to be

38 RX window size (w) It defines the maximum number of I format APDUs the Arctic may receive before sending acknowledgement to the IEC-104 master. Table 17: IEC-104 RX windows size (w) IEC-104 RX windows size (w) Window size Packets Value range 1-20 The w should not exceed two-thirds of TX window size k. The IEC-104 standard suggests w to be 8. I frames TX timeout (t1) It defines the timeout in seconds the Arctic waits for acknowledgement from IEC-104 master after sending last I format APDU or control frame (e.g. link test). If no acknowledgement is received during the defined time the Arctic will close the network connection and the IEC-101 link. Table 18: IEC-104 I frames TX timeout (t1) IEC-104 I frames TX timeout (t1) Timeout Seconds Value range The t1 must be longer than the network round-trip-time. The IEC-104 standard suggests 15 seconds. I frames RX timeout (t2) This defines the timeout in seconds from the last received I format APDU before sending acknowledgement. Table 19: IEC-104 I frames RX timeout (t2) IEC-104 I frames RX timeout (t2) Timeout Seconds Value range The t2 must be smaller than t1. The IEC-104 standard suggests 10 seconds. Link test interval (t3) This defines the interval in seconds how often the IEC-104 link is tested if there is no other activity. 38

39 Table 20: IEC-104 link test interval (t3) IEC-104 link test interval (t3) Timeout Seconds Value range Adjust this parameter according to the criticality of the link. The IEC-104 standard suggests 20 seconds but for pay-per-use GPRS connections the practical value may be substantially longer. Suspended timeout This defines the time in seconds how long a connected IEC-104 link can be in suspended state (STOPD) before the Arctic closes the connection. Table 21: IEC-104 suspended timeout IEC-104 suspended timeout Timeout Seconds Value range Using this parameter increases the probability of detecting partially closed network connections especially in UDP mode. Max sequence number These are the maximum sequence number used in IEC-104 communication. The value zero selects the standard value Table 22: IEC-104 suspended timeout IEC-104 suspended timeout Sequence number Packets Value range = as suggested by the IEC-104 standard. Cause of transmission length (IEC-104) It defines the length of IEC-104 Cause of transmission ASDU header field in bytes. Table 23: IEC-104 ASDU cause of transmission length IEC-104 ASDU cause of transmission length Field length Bytes Value range 1-3 The IEC-104 standard defines value 2. 39

40 Common address length (IEC-104) This defines the length of IEC-104 Common address ASDU header field in bytes. Table 24: IEC-104 ASDU common address length IEC-104 ASDU common address length Field length Bytes Value range 1-3 The IEC-104 standard defines value 2. Info object address length (IEC-104) This defines the length of IEC-104 Information object address ASDU header field in bytes. Table 25: IEC-104 ASDU information object address length IEC-104 ASDU information object address length 7.5 Field length Bytes Value range 1-3 The IEC-104 standard defines value 3. IEC-101 settings The IEC-101 settings define the properties of IEC-101 link layer and application layer parameters as described in the IEC standard. The IEC-101 communication is carried out between the Arctic and a IEC-101 slave. Figure 30. IEC-101 Settings 40

41 Slave link address (IEC-101) Table 26: IEC-101 slave link address IEC-101 slave link address Link address N/A Value range The link-level address of IEC-101 slave. Link address field length Defines the length of the IEC-101 link-level address field in bytes. Table 27: IEC-101 slave link address field length IEC-101 slave link address field length Field length Bytes Value range 1, 2 The link-level address of IEC-101 slave. Event poll interval It defines the IEC-101 event polling interval in 0.1 second increments (class 1 or 2 poll). Table 28: IEC-101 event poll interval IEC-101 event poll interval Interval 0.1 seconds Value range The events are polled only when the IEC-104 connection is active. Link test interval It defines the IEC-101 link test interval in 0.1 second increments. Link test is performed if there is no other activity. Table 29: IEC-101 link test interval IEC-101 link test interval Interval 0.1 seconds Value range The link test is performed if there is no other activity during defined interval. 41

42 Keep link open Defines that the IEC-101 link is kept always open even when there is no active IEC-104 connection. If the functionality is enabled the Arctic sends link test frames and restarts the IEC-101 link if the test fails. The events are still not polled before the IEC-104 connection is active. Table 30: IEC-101 keep link open IEC-101 keep link open Boolean N/A Value range No, Yes Some IEC-101 slaves require the link to be continuously open in order to operate. Reply header timeout Defines the timeout Arctic waits the reply to start from IEC-101 slave after command or request. Table 31: IEC-101 reply start timeout IEC-101 reply start timeout Timeout Milliseconds Value range Reply end timeout Defines the maximum duration of IEC-101 slave response. Table 32: IEC-101 reply end timeout IEC-101 reply end timeout Timeout Seconds Value range Retry limit Defines the number of retries sent to a IEC-101 slave in case of no reply. If no reply is still received the Arctic closes the IEC-101 and IEC-104 connections. Table 33: IEC-101 retry limit IEC-101 retry limit Retry limit 42

43 IEC-101 retry limit Retries Value range Cause of transmission length (IEC-101) Defines the length of IEC-101 Cause of transmission ASDU header field in bytes. Table 34: IEC-101 ASDU cause of transmission length IEC-101 ASDU cause of transmission length Field length Bytes Value range 1-3 The IEC-101 standard defines value 1. Common address length (IEC-101) Defines the length of the IEC-101 Common address ASDU header field in bytes. Table 35: IEC-101 ASDU common address length IEC-101 ASDU common address length Field length Bytes Value range 1-3 The IEC-101 standard defines value 2. Info object address length (IEC-101) Defines the length of IEC-101 Information object address ASDU header field in bytes. Table 36: IEC-101 ASDU information object address length IEC-101 ASDU information object address length 7.6 Field length Bytes Value range 1-3 The IEC-101 standard defines value 2. ASDU Converter The ASDU converter can be used to convert ASDU header field lengths between IEC-101 and IEC-104 protocols. 43

44 Figure 31. ASDU Converter Use ASDU converter This defines if the ASDU header level IEC-101 <-> IEC-104 conversion performed. If enabled the ASDU header field lengths are converted between IEC-104 and IEC-101. This parameter must be enabled if the ASDU header lengths differ between the IEC-104 and the IEC-101. Table 37: Use ASDU converter Use ASDU converter Boolean N/A Value range No, Yes The information on the field must fit in the shorter one of the two. It s not possible to convert e.g. value to a one byte field. Use ASDU type replacer The ASDU type replace function can be used to convert an ASDU type (Original type) to another (Applied type) type e.g. in cases when the IEC implementation differs between master and slaves. Table 38: Use ASDU type replacer Use ASDU type replacer Boolean N/A Value range No, Yes Original type The original ASDU type searched by ASDU type replacer. Applied type The new ASDU type is replaced by the original type. 7.7 Packet collector The packet collector can be used to collect many IEC-101 messages/events to a single network packet instead of sending every message separately. 44

45 This function is useful for slow packet switched communication network (e.g. Mobitex) for speeding up especially the general interrogation response. Figure 32. Packet Collector Use packet collector Table 39: Use packet collector Use packet collector Boolean N/A Value range No, Yes Max bytes Max bytes is defined as the maximum bytes trigger for packet collector. Before a new packet is inserted into the packet collector buffer the amount of bytes is checked. If the insertion of the new packet would cause the number of bytes in the packet collector to exceed MAX BYTES the old content is sent to the network before inserting the new one. Table 40: Maximum collected bytes Maximum collected bytes Packet size Bytes Value range The value should be smaller than the MTU/MRU of network used. Max time Max time is deived as the maximum collect time trigger for packet collector in 0.1 secs increments for packet collector. If there has been data on packet collector over MAX TIME the data is sent to network. Table 41: Maximum collected time Maximum collected time Timeout 0.1 seconds 45

46 Maximum collected time Value range The value must be smaller than t1. Max packets Max packets are defined as the maximum amount of IEC-101 packets stored into the packet collector before sending the data to the network. Table 42: Maximum collected packets Maximum collected packets Packet count Packets Value range Other settings Write syslog It defines whether the error messages are stored to system log file or not. Table 43: Write system log Write system log Boolean N/A Value range No, Yes The system log is available by using WEB UI. 46

47 8 Modbus application settings 8.1 Introduction These configuration instructions are intended only for configuring Modbus on Viola Arctic device. The Modbus Gateway is an adapter application enabling conversions between Serial and Network Modbus protocols. The gateway can operate on two modes; either connecting serial Masters to Slaves behind the network or connecting network Master to Serial slaves. The gateway offers following core properties: Supports Modbus RTU and Modbus ASCII serial protocols. 8.2 Supports ModbusTCP, ModbusRTU over TCP, ModbusRTU over UDP, Modbus ASCII over TCP and Modbus ASCII over UDP network protocols. It can generate and filter out gateway exceptions. It can route traffic on network based on Modbus addressing enabling intelligent use of network resources. Makes automatic connection management. Enables multiple server sessions over network. Offers unlimited amount of Masters on serial or Network side. Offers 30 routes over network to slaves. Parameters The parameters are divided into two groups: Common parameters Routes Common parameters define for e.g. the protocols used in serial and network communications, serial port settings and protocol specific timeouts. Route parameters are only required on Serial Master to Network Slaves mode defining the IP and Modbus addresses of slaves behind the network. You can change the parameter values in Serial Port and I/O > Modbus Gateway (RSx) Common parameters The common parameters define general settings and settings for Network Master to Serial Slaves mode. 47

48 Figure 33. Modbus application settings General Settings Gateway Status Table 44: Gateway Status Identifier Gateway Status Description Tthe Modbus gateway functionality enabled for the serial port. Values Enabled Modbus Gateway is enabled Disabled Modbus Gateway is not enabled s Each serial port of Arctic has its own Modbus Gateway definitions. Gateway Mode Table 45: Gateway Mode Identifier Gateway Mode Description The slaves located on network or serial side. Values Network Master to Serial Slaves Slaves are on serial side. Serial Master to Network Slaves Slaves are on network side. 48

49 Identifier Gateway Mode s If slaves are on network side, the routes are also needed to be defined. Protocols Serial Protocol Table 46: Serial Protocol Identifier Serial Protocol Description Defines the Modbus protocol used on serial communication. Values Modbus RTU Serial devices use Modbus RTU protocol Modbus ASCII Serial devices use Modbus ASCII protocol s Modbus RTU is more efficient and should be used whenever possible. Network Protocol Table 47: Network Protocol Identifier Network Protocol Description Defines the TCP/IP and Modbus protocol used on network communication. Values Modbus TCP Modbus TCP protocol over TCP Modbus RTU over TCP Modbus RTU protocol over TCP Modbus RTU over UDP Modbus RTU protocol over UDP Modbus ASCII over TCP Modbus ASCII protocol over TCP Modbus ASCII over UDP Modbus ASCII protocol over UDP s If Viola Systems M2M Gateway is used to tunnel network traffic over SSH, use Modbus RTU over UDP when possible for efficient communication. The SSH tunnel already contains TCP properties like reliable message delivery. Framing Slave Response Timeout Table 48: Slave Response Timeout Identifier Slave response timeout Description Defines the time in microseconds (10E-6 seconds) how long Arctic waits the response from Modbus slave. If the response is not received, Arctic can generate and return Modbus gateway exception. Values microseconds (0 90 seconds) 49

50 Identifier Slave response timeout s The reply timeout of Modbus Master must be greater than the Gateway (Arctic) timeout. Otherwise the flow of request-reply communication is violated. Arctic does not accept a new request before the reply from slave is received or the reply timeout is elapsed. The delays in network communication can vary especially in wireless (e.g. GPRS/EDGE/ Mobitex) networks. When the slaves are located on network side, use e.g. PING to estimate the delay packets spend on network. Inter-Frame Timeout Table 49: Inter-Frame Timeout Identifier Inter-frame timeout Description Defines the idle time in microseconds (10E-6 seconds) that marks the end of Modbus frame in serial communication. If the value is zero, the Gateway uses standard 4 character time. Values microseconds (0 2 seconds) s Use as small value as possible to speed up communication and increase the value if problems arise. Some PC programs can insert unexpected delays between serial characters. Exceptions Generate Gateway Exceptions Table 50: Generate Gateway Exceptions Identifier Generate Gateway exceptions Description Defines does the Gateway generate and return Modbus Gateway exception message to Master if no valid reply is not received from slave. Values Enabled Generation of Gateway exceptions is enabled Disabled - Generation of Gateway exceptions is disabled s This functionality is useful for debugging. See also parameter Pass Gateway exceptions. Pass Gateway Exceptions Table 51: Pass Gateway Exceptions Identifier Pass Gateway exceptions Description Defines are the Gateway exception replies from slave side passed to master. Values Enabled Gateway exception replies are passed to Master Enabled Gateway exception replies are filtered away s filtered away s 50

51 Serial Settings Serial Port Table 52: Serial Port Identifier Serial Port Description Defines the serial port that Gateway uses for Modbus serial communication. Values Port 1 Serial port 1 (RS-232 console/application port) Port 2 Serial port 2 (RS-232/422/485 application port) s If a single serial port or RS-422/485 is required, use Port 2. If Port 1 is used, the console switch of Arctic must be on Application position. DIPswitches below the DB-9 serial connector specify the RS-232/422/485 settings of Port 2. Serial Speed Table 53: Serial Speed Header 1 Speed Description Defines the serial port speed for Modbus communication. Values 300, 1200, 2400, 4800, 9600, 19200, 38400, 57600, bps s Check the speeds supported by connected Modbus equipment. If special serial port speed is required, please contact Viola Systems. Serial Data Bits Table 54: Serial Data Bits Identifier Serial Data bits Description Defines the number of data bits used on Modbus serial communications. Values 5, 6, 7, 8, Auto (8 for Modbus RTU, 7 for Modbus ASCII) s Check the data bits supported by connected Modbus equipment. Generally Modbus RTU communication uses 8 data bits and Modbus ASCII communication uses 7 data bits. Serial Stop Bits Table 55: Serial Stop Bits Identifier Serial Stop bits Description Defines the number of stop bits used on Modbus serial communications. Values 1,2 s 51

52 Serial Parity Table 56: Serial Parity Identifier Serial Parity Description Defines the parity method used on Modbus serial communication Values None no parity method used Even even parity bit generated and inspected Odd odd parity bits generated and inspected s Serial Flow Control Table 57: Serial Flow Control Identifier Serial Flow control Description Defines is the hardware (RTS/CTS) flow control used on Modbus serial communication Values Enabled RTS/CTS flow control used Disabled RTS/CTS flow control not used s Use of hardware flow control is suggested Network Settings Server TCP/UPD Port Table 58: Server TCP/UPD Port Identifier Server TCP/UDP port Description Defines the TCP or UDP port that Masters can form connections to. Default Modbus TCP/IP communication port is 502. Values s If multiple Modbus Gateways are running on same device (for both serial ports) the TCP/UDP communication ports must not be same. Use e.g. ports 502 and 504. The network and Arctic firewalls must enable TCP or UDP communication for that port. Maximum Number of Clients Table 59: Maximum Number of Clients Identifier Maximum number of clients Description Defines how many network masters can be connected to Gateway simultaneously. Values 0-20 s Generally use value at least 2 when using TCP communication. Otherwise if the Gateway does not recognize partially closed 52

53 Identifier Maximum number of clients connection, forming of new connections is not accepted by Gateway before Connection idle timeout is elapsed. Connection Idle Timeout Table 60: Connection Idle Timeout Identifier Connection idle timeout Description If the connected Master hasn t sent valid Modbus packets during that timeout the connection is closed by Arctic and therefore the resources are available for new connections. This parameter is especially useful when the network connection is not reliable causing hanging or partially closed connections. Values seconds s Set this value about two times the polling interval of master. Enable Keepalive Table 61: Enable Keepalive Identifier Enable keepalive Description Defines is the connection testing enabled for TCP network communication. Values Enabled Testing the TCP connection with Master is enabled Disabled Testing the TCP connection with Master is disabled s The testing is done by sending TCP keepalive packets on certain intervals. Routes When the Arctic Modbus Gateway is configured to Serial Master to Network Slaves mode the routes are needed to be defined for each connected Modbus slave. Gateway can route traffic based on Modbus addressing therefore enabling more efficient communication where each slave receives only data addressed to it. Route in Use Table 62: Route in Use Identifier Route in use Description Defines is this route entry used to decide to which IP address Modbus request is sent. Values Yes Route information is used No Route information is not used s If no route is found for Modbus request is it dropped and Gateway exception is generated if enabled. 53

54 Host Table 63: Host Identifier Host Description Defines the IP address or Host name where packets are routed by that entry. Values IP address or Host name s If Host names are used the DNS server IP address is required to be defined on Arctic Network settings. The Network Protocol setting on Common parameters defines the network- and Modbus protocol used on network communication. TCP or UDP Destination Port Table 64: TCP or UDP Destination Port Identifier TCP or UDP destination port Description Defines the UDP or TCP destination port where this route entry sends Modbus requests. Values (Modbus default is 502) s The port must be same as used on the network slave device or Gateway behind network. Filter Slave Address Table 65: Filter Slave Address Identifier Filter slave address Description Defines is the routing based on Modbus addresses used for that entry. If not enabled every Modbus request is routed to this entry. If enabled only Modbus requests having destination address matching the Address list of entry are routed. Values Yes Route entry checks for Modbus destination address No Route entry enables any Modbus destination address s It s generally good to use Modbus address filtering avoiding unnecessary network traffic. Address to Filter Table 66: Address to Filter Identifier Address to filter Description Comma separated list of the Modbus addresses of slaves behind on this route entry (max. 20 pcs.). 54

55 Identifier Address to filter Values Maximum 20 pcs. of comma (,) separated Modbus destination addresses. s The Filter Slave address parameter of Route entry needs to be enabled these addresses to take effect. Connection Idle Timeout Table 67: Connection Idle Timeout Identifier Connection idle timeout Description If there hasn t been communication on this route during given amount of seconds the Gateway automatically closes the TCP connection to slave and therefore frees Slave s communication resources. This is especially useful when multiple Masters access same Slave. Values seconds s Set this parameter about two times the polling interval of Master. Enable TCP Keepalive Table 68: Enable TCP Keepalive Identifier Enable TCP keepalive Description Defines is the connection testing enabled for TCP network communication. Values Enabled Testing the TCP connection with Slave is enabled Disabled Testing the TCP connection with Slave is disabled s 8.3 The testing is done by sending TCP keepalive packets on certain intervals. Configuring Network Master to Serial Slaves Mode When the PLC/RTU slaves supporting serial based Modbus communication are required to be controlled over TCP/IP networks the Gateway on slave side needs to be configured to Network Master-Serial Slaves mode. 55

56 Figure 34. Arctic Modbus Gateway connecting serial slaves to network On that mode, the Arctic acts like network server where Masters (clients) can connect (the default port being 502) and transmit Modbus requests. The Arctic makes conversions between network and serial protocols. If the slave does not reply during defined timeout or if the reply is corrupted, the Arctic sends gateway exception message back to Master if the exception generation is enabled. Otherwise, the reply is returned. Multiple masters can connect simultaneously to Gateway, which handles the multiplexing between masters.! Each Arctic must have a fixed IP address in order the Master to know where to connect. Many client-use optimized networks (like public GPRS, xdsl) does not offer fixed IP addresses but allocate them dynamically. This situation can be solved by using Viola Systems M2M Gateway Settings Common parameters Only the common parameters are configured. The routes are unused on Network Master to Serial Slaves mode. The configuration menu is located on Applications > Modbus GW menu of Arctic WEB configuration. 56

57 Figure 35. Example of common parameters for Network Master to Serial Slaves mode Table 69: Setting guideline for Network Master to Serial Slaves mode Parameter Value Parameter Value Gateway Status Enabled Gateway Mode Network Master to Serial Slaves Serial Protocol Depends on connected Modbus slave Prefer Modbus RTU when possible Network Protocol Depends on Master side If Viola Systems M2M tunneling is used, prefer UDP based Modbus network messaging. Slave response Depends on connected Modbus timeout slave Increase this value if problem is on serial communication. Inter-frame timeout Modbus RTU protocol has standard timeout of 4 character time. Use value 0 for default. Increase this value if the problem is on serial communication. Generate Gateway exceptions Enable or Disable Enabling Gateway Exceptions can help system debugging and testing. Pass Gateway exceptions Enable or Disable Serial Port Select Port 1 or Port 2 Serial Speed Depends on connected Modbus slave. If single serial port or RS-422/485 functionality is required, use Port 2. Serial Data Bits Depends of connected Modbus slave. Use of Auto selects 8 data bits for Modbus RTU and 7 data bits for Modbus ASCII. 57

58 Parameter Value Serial Stop Bits Depends on connected Modbus slave. Serial Parity Depends on connected Modbus slave. Select None, Even or Odd. Serial HW Handshaking Enable if require by slave. Server TCP/ UDP Port Default port for Modbus network communication is 502. Max. Number of clients Normally use minimum value 2. If the network is wireless or If multiple Masters are allowed to unreliable, increase this value connect, then increase the value. if there is a problem during the connection. If multiple Protocol Gateway applications are running on same Arctic, the ports must be different for each application. Use e.g. ports 502 and 504. Connection idle Set about two times the polling timeout interval of Master. If the polling interval is very long (over hour) use e.g. polling interval+200 seconds Enable keepalive Enabled if the polling interval or idle timeout is very long. Saving Parameters When the settings are complete, press the Apply button and permanently store the parameters by clicking on Commit button. Wait for acknowledgement after pressing the Commit button. Now reboot the Arctic by pressing Reboot button. The Arctic is now ready to deliver data from Network Masters to Serial Slaves. 8.4 Configuring Serial Master to Network Slaves Mode When Modbus Master supporting serial based Modbus, communication needs to control slaves over TCP/IP network. The Gateway on Master side needs to be configured to Serial Master Network Slaves mode. 58

59 Figure 36. Arctic connecting serial Master to network On that mode, the Arctic routes serial Modbus packets to network and performs conversions between serial and network protocols. The routing based on Modbus addressing allows intelligent use of network resources, which is especially useful for pay-per-use networks like GPRS. The settings consist of two parts: Common settings Settings for each route Settings Common Parameters The configuration menu is located on Applications > Modbus GW menu of Arctic WEB configuration. 59

60 Figure 37. Example of common parameters for Serial Master to Network Slaves mode Table 70: Setting guideline for Network Master to Serial Slaves mode Parameter Value Gateway Status Enabled Gateway Mode Serial Master to Network Slaves Serial Protocol Depends of connected Modbus Master Prefer Modbus RTU when possible Network Protocol Depends of Slave devices If Viola Systems M2M tunneling is used, prefer UDP based Modbus network messaging. Slave response Depends of connected Modbus timeout slave and delays of TCP/IP network. Increase this value if problems on slave communication. Inter-frame timeout Modbus RTU protocol has standard timeout of 4 character time. Use value 0 for default Increase this value if problems on serial communication Generate Gateway exceptions Enable or Disable Enabling Gateway Exceptions can help system debugging and testing Pass Gateway exceptions Enable or Disable Serial Port Select Port 1 or Port 2 Serial Speed Depends of connected Modbus Master 60 If single serial port or RS-422/485 functionality is required use Port 2

61 Parameter Value Serial Data Bits Depends of connected Modbus Master. Use of Auto selects 8 data bits for Modbus RTU and 7 data bits for Modbus ASCII. Serial Stop Bits Depends of connected Modbus Master Serial Parity Depends of connected Modbus Master. Select None, Even or Odd Serial HW Handshaking Enable if require by Master Server TCP/ UDP Port Default port for Modbus network Value is not used on Serial communication is 502 Master to Network Slaves mode. Max. Number of clients Normally use minimum value 2. If multiple Masters are allowed to connect increase the value. Value is not used on Serial Master to Network Slaves mode. Connection idle Set about two times the polling timeout interval of Master. If the polling interval is very long (over hour) use e.g. polling interval+200 seconds Value is not used on Serial Master to Network Slaves mode. Each route entry has it s own idle timeout. Enable keepalive Value is not used on Serial Master to Network Slaves mode. Each route entry has it s own keepalive setting. Enable if the polling interval or idle timeout is very long. Settings Routes The route entries define how Modbus packets are routed on network from Serial Master to Network Slaves. Up to 30 routes can be specified each having up to 20 slaves. If the routing is based on Modbus addressing is not required or there are more than 20 slaves behind the route, the address filtering for that entry can be disabled. Figure 38. Route summary The route entry can be edited by pressing Edit button. The routes can also be disabled or enabled by pressing following buttons: Disables the Route entry Enables the Route Entry The active routes do not have strikethrough line. 61

62 Pressing the Edit button opens following configuration screen: Figure 39. Route edit Table 71: Setting guidelines for Routes Parameter Value Route in use Enable or Disable Each IP address and TCP/UDP port of slaves needs to be defined on separate route entries. Host The IP address or Host name of slave or Gateway behind the route. If Host names are used the DNS server IP address is required to be defined on Arctic Network settings. The Network Protocol setting on Common parameters defines the network- and Modbus protocol used on network communication. TCP or UDP destination port The TCP or UDP port that slave or Gateway on slave side is listening. Default Modbus port is 502. Filter slave addresses Defines is the routing based on Modbus addresses used for that entry. If not enabled, every Modbus request is routed to this entry. If enabled only Modbus requests having destination address matching the Address list of entry are routed. It s generally good to use routing based on Modbus addressing in order to avoid unnecessary network traffic. Address to filter Comma separated list (max 20 The Filter Slave address pcs.) of Modbus slave addresses parameter of Route entry needs behind this route entry. to be enabled these addresses to take effect. Connection idle timeout (TCP) Set about two times the polling interval of Master. If the polling interval is very long (over hour) use e.g. polling interval+200 seconds. Enable TCP keepalive Enable if the polling interval or idle timeout is very long. 62