I11 user manual - Software & hardware solutions for all of your remote monitoring needs

Getting Started

About I11

I11 is communication controller optimized for remote control and monitoring of distributed automation systems.

The role of I11 controller in a geographically scattered system is to monitor devices using Modbus RTU and Modbus TCP protocol. Data collected by I11 controller is available trough InView OPC Server (see InView OPC Server manual). InView OPC Server can be located anywhere in the world, as long as I11 gateway can access it via internet or local network.

I11 controller uses serial (RS-232/485) and TCP/IP protocol to communicate with Modbus devices and TCP/IP protocol to communicate with InView OPC Server..

Data compression and economical IPP protocol ensures real-time remote data acquisition with very low latency and very modest data consumption. End-to-end data encryption ensures that data is transferred securely between I11 controller and InView OPC Server.

To avoid data loss, I11 controller stores loggable register values before sending them to InView OPC Server. If connection to InView OPC Server is unavailable, stored logs are sent later when communication is restored. These logs are accessible if we use InView WebScada for archive preview.

I11 contollers local database can store logs for one week if logging period is set to one minute. Also alarms and events are stored in local database before sending.

After initial interface setup using WebUI, the device starts to communicate with InView OPC Server and downloads the register configuration which is previously configured using the InView OPC Server Configurator. (see InView OPC Server Configurator manual) . After this step I11 is fully functional and running. As you can see, on-site deployment is very easy and requires minimal staff.

Image 2
    Downloaded register configuration consists of:
  • IP/device addresses of Modbus devices
  • Register addresses to read/write
  • Serial baud rate, log interval, etc...

When register configuration is downloaded, the communication with Modbus devices can be verified on WebUI displaying real time register values and these values are sent to InView OPC Server. After initial register configuration, this configuration is downloaded only on demand if commanded from InView OPC Server. I11 controller firmware update can be also initiated from InView OPC Server.

Optional communication with InView Central Server ensures advanced trouble monitoring and support. It is a service that provides customers with higher level of monitoring and support for their automation system. (see InView website: http://www.inviewscada.com/advanced-trouble-monitoring-and-support-central-server/).


Quick installation guide

Overview

I11 controller have two RS-232/485 serial ports and two 10/100 Mbps Ethernet LAN ports, as well as a Mini PCIe socket to support cellular modules.

Package Checklist

    Before installing the I11, verify that the package contains the following items:

  • I11 gateway (with SD card)
  • Power jack
  • 3-pin terminal block for power
  • 5-pin terminal block for UART x 2

I11 Panel Layout

The following figures show the panel layouts of the I11.

Image 3
Image 4

Front view

Image 5

LED indicators

Mounting the I11

    There are two sliders on the back of the unit for DIN rail and wall mounting:
  • Mounting on a DIN rail: Pull out the bottom slider, latch the unit onto the DIN rail, and push the slider back in.
  • Image 7
  • Mounting on the wall: Pull out both the top and bottom sliders and align the screws accordingly.
  • Image 8

Connector Description

Power Connector Connect the “terminal block to power jack converter” (in the package) to the I11 DC terminal block (located on the top panel), and then connect the power adapter. It takes about 30 seconds for the system to boot up. Once the system is ready, the Ready LED will light up.

Grounding the I11

Grounding and wire routing help limit the effects of noise due to electromagnetic interference (EMI).

SG: The Shielded Ground (sometimes called Protected Ground) contact is the top contact of the 3-pin power terminal block connector when viewed from the angle shown here. Connect the SG wire to an appropriate grounded metal surface.

Image 9

Ethernet Ports

The two 10/100 Mbps Ethernet ports (LAN 1 and LAN 2) use RJ45 connectors.

Image 10

Serial Ports

The two serial RS-232 ports (P1 and P2) use terminal connectors. The pin assignments for the ports are shown in the table.

Image 11

Serial port 1 is used for debugging. Settings : 19200 8N1.

Serial port 2 is used for Modbus communication. Settings: 8N1, baud rate and serial standard can be set from WebUI. Also, baud rate can be changed by the register configuration received from InView OPC Configurator.

USB port

The USB port is on the front panel of the I11 controller. It is used for storage expansion. However, this port is unsupported by the I11 software so we recommend not to use it.

SD/SIM Card Sockets

I11 comes with an SD socket for storage expansion, and a SIM card socket for cellular communication. The SD card/SIM card sockets are located at the lower part on the front panel. To install them, remove the screw and the protection cover to access the sockets, and then plug the SD card or the SIM card into the sockets directly. You will hear “click” when finished. Remember to push in on the SD card or SIM card first if you want to remove them.

By default, the operating system and the I11 application is stored on the SD card. Do not remove the SD card because I11 will stop operating.

Cellular Module

    I11 comes with a PCIe socket inside for wireless communication. Follow these steps:

  1. 1. Remove the screws on the side panel, and take off the cover.
  2. 2. Find the location of the PCIe socket. Insert the cellular module into the socket. Fasten the socket with screws.
  3. 3. Next you need to install the antenna cable. There are two antenna connectors on the cellular module. Connect the cable onto either connector.
  4. 4. Install the other end of the cable onto the connector on the front panel of the I11. Remove the black plastic cover first.
  5. 5. Install the connector, place the locker washer first, and then insert the nut. Connect the antenna onto the connector.

I11 setup

The following steps will show you how to initially set up the I11 device and connect it to devices communicating via Modbus protocol and InView OPC Server.

Step 1: Set up device IP addresses

I11 LAN ports cannot be configured as DHCP clients, static configuration must be used. The default IP address of the I11 device is interfaces are :

Interface Default IP address Default netmask
LAN1 192.168.3.127 255.255.255.0
LAN2 192.168.4.127 255.255.255.0

1.a: Connect I11 gateway to your computer or to a switch connected to your computer. Use LAN1 connector as shown on picture 14.

Image 14

1.b: Change your computer`s network settings manually to use the same subnet as I11, but a different IP address. For example:

IP address: 192.168.3.200 Subnet mask: 255.255.255.0

1.c: Open a web browser (Chrome or Internet Explorer) and enter the address: 192.168.3.127:3700. A configuration webpage will appear as shown on picture 28. Here you can configure the I11 controller. Changed values and settings will be valid only after you reboot the device with the restart button on the bottom of the page. If you change the network settings, after rebooting you can access the configuration webpage on the new IP address (port 3700) if configured properly.

1.d: Change the IP address and subnet addresses of LAN1 interface and click “Save” as shown an picture 15.

1.e: Restart I11 controller using the Reboot button on the bottom of the page and wait 30 seconds.

1.f: Change your computers network configuration to the same network as the new IP address of interface 1.

1.e: Now you can access I11 webUI via web browser using the new IP address of LAN1 interface.

You can also access I11 WebUI using LAN2 interface if the host is connected to LAN2 interface by entering 192.168.4.127:3700 address into the browser, and reconfigure LAN2 interface.

Also, device setup videos are available on InView youtube channel:

https://www.youtube.com/playlist?list=PLNHcHX_FtMP9n95exgdkGPj9sootDNBT5

Operating modes of I11

I11 can communicate with Modbus devices via TCP and RTU protocol simultaneously as shown on picture 17. I11 will recognize its communication modes (only TCP, only RTU, TCP and RTU) from its configuration downloaded from InView OPC Server: if there are registers with IP address TCP mode will start and if there are registers with Modbus addresses (1,2,3..) RTU mode will also start. As mentioned before, the register configuration is done by the InView OPC Server Configurator. (see InView OPC Server Configurator manual).

For Modbus communication both LAN interfaces can be used, depending on the IP addresses of Modbus devices. On picture 17 we use LAN2 interface, because IP addresses of Modbus devices are in the same network with LAN2 interface. The register configuration is done by the InView OPC Server Configurator. (see InView OPC Server Configurator manual) .

Image 17

The following pages will explain operation modes Modbus RTU and Modbus TCP separately, but keep in mind that the two modes also work simultaneously


RTU mode – RS 232

In this mode, I11 will communicate with one Modbus device via serial (RS-232) cable as shown on picture 18.

Image 18

In this configuration baudrate should be set as on Modbus device and serial standard set to RS-232 using WebUI:

Modbus device address should be configured in InView WebScada Configurator. Configure LAN1 interface, OPC server IP address, OPC server address GW so that you can access OPC server. Example of interface configuration using WebUI:


RTU mode – RS 485

In this mode, I11 will communicate with multiple Modbus devices via serial (RS-485) cable as shown on picture 21:

Image 21

In this configuration baudrate should be set as on Modbus device and serial standard set to RS-485 using WebUI:

If I11 device is used in a harsh industrial environment, external rs-232/485 converter (InCom 485) usage is preferred instead of the embedded serial rs-485 controller. In that case, rs-232 serial standard should be selected in WebUI.

Modbus device address should be configured in InView WebScada Configurator. Configure LAN1 interface, OPC server IP address, OPC server address GW so that you can access OPC server. Example of interface configuration using WebUI:


TCP mode

In this mode, I11 will communicate with multiple Modbus devices using TCP/IP protocol in a local network. For Modbus communication both LAN interfaces can be used, depending on the IP addresses of Modbus devices. Also, for communication with InView OPC Server both LAN interfaces can be used, depending on the InView OPC Servers IP address and gateway to it.

On picture 24 we use LAN2 interface, because IP addresses of Modbus devices are in the same network with LAN2 interface. The register configuration is done by the InView OPC Server Configurator. (see InView OPC Server Configurator manual) . IP address examples of Modbus devices for this configuration: 192.168.6.11, 192.168.6.12,...

Image 24

Configure LAN1 interface and OPC SERVER IP addresses so that you can access InViewOPC Server. Also, LAN2 interface will be used to access Modbus devices. Example of interface configuration using WebUI:

In the next configuration on picture 26 we use LAN1 interface for Modbus communication and also for communication with InViewOPC Server, because IP addresses of Modbus devices are in the same network with LAN1 interface. Interface LAN2 is not used. IP address examples of Modbus devices for this configuration: 10.0.0.200, 10.0.0.201, …

Image 26

Configure LAN1 interface and OPC SERVER IP addresses so that you can access InView OPC Server and Modbus devices. Example of interface configuration using WebUI:


GPRS

    GPRS can be enabled only if cellular module is provided and installed in I11 gateway. GPRS module can be used as the link to InView OPC Server. The antenna should be connected on connector W1, SIM card inserted into SIM slot and proper APN, username, password, PIN number should be entered via WebUI:
  • GPRS APN: is the Access Point Name of the inserted SIM card
  • GPRS Username: is the username of previously provided APN
  • GPRS Password: is the password of previously provided APN
  • GPRS PIN: is the Personal Identification Number of the inserted SIM card

Important: if any changes are made to these parameters, Save button should be pressed before reboot

If we want to disable gprs module, just leave GPRS APN field blank.

Image 28

In this mode, I11 will communicate with multiple Modbus devices using TCP/IP protocol trough LAN2 because Modbus devices and LAN2 interface are on the same network. LAN1 interface can be also used for modbus communication if register configuration contains registers with IP addresses which are in the same network with LAN1 interface).

LAN1 and LAN2 interfaces wont be used to access InView OPC Server, because GPRS module will be used as link and the cellular network will provide gateway to InView OPC Server dinamically.

It is very important to leave OPC server primary gateway field in WebUI blank as shown on picture 29. GPRS module will work only if we do so.


WebUI

In order to I11 controller function as expected, some parameters have to be configured. This is done via webUI on the configuration page shown on picture 30:

Image 30

When all parameters are set and saved, restart the device. After restart access WebUI. if everything is set properly, you can access live values and see all the values II1 gateway reads from Modbus devices. You can access live values using the same IP address and port 3600, or use the link on the top of the config page as shown on picture 31

You can always go back to configuration page using the link on the top of this page.


WebUI parameter groups

  • LAN1 IP address: is the IP address of the LAN1 interface.
  • LAN1 IP subnet mask: is the subnet mask of the LAN1 interface.

Important: if any changes are made to these parameters, Save button should be pressed before reboot.

  • LAN2 IP address: is the IP address of the LAN2 interface.
  • LAN2 IP subnet mask: is the subnet mask of the LAN2 interface.

Important: if any changes are made to these parameters, Save button should be pressed before reboot.

  • OPC server IP address: is the IP address of the InView OPC Server.
  • OPC server IP address gateway: the device will find the InView OPC Servers IP address through this gateway. This gateway address should be in the same network range as LAN1 or LAN2 interface.

Important: if any changes are made to these parameters, Save button should be pressed before reboot.

  • GPRS APN: is the Access Point Name of the inserted SIM card
  • GPRS Username: is the username of previously provided APN
  • GPRS Password: is the password of previously provided APN
  • GPRS PIN: is the Personal Identification Number of the inserted SIM card

Important: if any changes are made to these parameters, Save button should be pressed before reboot.

• DNS Server: The DNS server address. If there is no DNS server in local network, a public one can be assigned (8.8.8.8, 8.8.4.4,...)

Important: if any change is made to this parameter, Save button should be pressed before reboot.

• OPC Server port: is the port of the InView OPC Server the device is connecting to.

Important: if any change is made to this parameter, Save button should be pressed before reboot.

• Baud rate: the baud rate of the serial communication of the device that is connected to the device via serial port 2 when the device operates in RTU mode.

• Read mode: in single mode, the device reads registers one by one. In batch mode, the device reads multiple registers or coils at once (maximum 120).

• Serial standard: the serial standard that serial port 2 uses to communicate with Modus RTU device

• Switch 32bit Integer registers: switches the read order of registers in case of 32bit integer values.

• Switch float registers: switches the read order of registers in case of float values.

Important: if any changes are made to these parameters, Save button should be pressed before reboot.

• Log interval: time interval of logging in minutes. Accepted values: 1, 2, 5, 10, 15, 20, 30, 60 .

• Message length: number of ID-value pairs sent in one single GI, UV or PI message.

Important: if any changes are made to these parameters, Save button should be pressed before reboot.

• Reconnect sleep: is the time in seconds I11 will wait before trying to reconnect

Important: if any change is made to this parameter, Save button should be pressed before reboot.

• Push GI enabled: if this function is turned on, I11 will send GI messages to InView OPC Server even without GI command received.

• Push GI period in minutes: the period in minutes between two push GI messages. Accepted values: 1, 2, 5, 10, 15, 20, 30, 60 .

Important: if any changes are made to these parameters, Save button should be pressed before reboot.

• Log buffer size: the size of the circular buffer used for logging. Maximum value: 10800 . (max one week: 7days x 24hours x 60 minutes if logging interval is one minute)

• Alarm Log buffer size: the size of the circular buffer used for logging alarms. Maximum value: 1000 .

• HB timeout: the number seconds the device will wait until it requests a “heartbeat” from the InView OPC Server (something like ping) if no other message comes from the InView OPC Server. Preferred value: 30.

• HB reset timeout: the number of seconds the device will wait until it resets the connection if no messages or heartbeat comes from InView OPC Server. Preferred value: 180.

• Modbus answer drop treashold: number of unanswered Modbus commands that triggers socket disconnection and reconnection. Preferred value: 3 for TCP mode and 11 for RTU mode .

• Modbus answer wait: the number of microseconds the device will wait for a Modbus answer if Modbus TCP is used. After that time, it moves on to the next command. Preferred value: 250000 , maximum value: 300000.

• Modbus read pause batch mode: the number of microseconds the device will wait between Modbus TCP read cycles in batch mode. Preferred value: 10000, maximum value: 300000.

• Modbus read pause single mode: the number of microseconds the device will wait between Modbus TCP read cycles in single mode. Preferred value: 10000, maximum value: 300000.

Important: if any changes are made to these parameters, Save button should be pressed before reboot.

Bar Colors

  • Colors of Red Bar
  • Colors of Yellow Bar
  • Colors of Green Bar

Copyright © inVIEW 2016. All rights reserved. | office@inviewscada.com