GENERAL USER GUIDE FOR ICONNECTOR STHC

STHC-MN-EN-01 

OCT-2020

This document is applied for the following products

SKU STHC HW Ver. 3.3 FW Ver. 3.5

1. Functions Change Log

HW Ver. FW Ver. Release Date Functions Change
3.3 3.5 Aug-2020  

2. Introduction

STHC is a Smart IoT Gateway, aka iConnector, a main component in any IoT application. iConnector has a role to connect the real World's things like sensors, meters, ,machines...to server system for data logging, data analytics, monitoring & controls...iConnector support multiple Industrial Fieldbus like Modbus, EthernetIP, Profinet, CClink, Wireless sensor network...It connects to server system via LAN/WAN as Ethernet, WiFi or Cellular.

STHC_en_1.jpg

3. Specification

Host Communication Cellular type GPRS Quadband (850/900/1800/1900)/3G-Dual band (2100/900)/3G- Penta Band (2100/1900/850/850Japan/900/800Japan),standard internal antenna, optional external antenna
Host Communication Etherner type 01 x RJ45 port, 10Mbps
Host Communication WiFi type 802.11b/g/n, 2.4Ghz,internal antenna
GPS option, only available on GPRS version or 3G-Penta band version
Host communication supports TCP/IP, UDP/IP, FTP, HTTPS, SNMP...
Fieldbus communcation ModbusRTU x 01 port, 31 slaves, max 19.2 kpbs
Vietnam Type Approval Cerification QCVN 54:2011/BTTTT, QCVN 15:2015/BTTTT (DAVITEQ B00122019)
Optional Integrated wireless co-ordinator with external antenna or internal antenna
Optional Internal buzzer (to replace Relay 1)
Power supply 7..48VDC, avg 200mA, peak 1.5A
Back-up battery Lithium Super Capacitor
On-board memory & sensors 2MB Flash, PCB temperature sensor
Electrical connectors M12, 4-pin, coding A or 9mm Power Plug and USB port
SIM slot 01 x micro-SIM (cellular versions only)
Included accessories mounting bracket for wall mount (cellular version only)
Operating Temperature/Humidity -20 .. + 60 degC / 95%RH, non-condensing
Housing/Protection Aluminum+Polycarbonate for Cellular version, anti-UV plastic for Ethernet/WiFi version. All version is IP67 protection
Dimension H106xW73xD42 for Cellular version, H130xW90xD40 for Ethernet/WiFi versions
Net weight 190 grams for Cellular version, 350 grams Ethernet/WiFi versions
Relay outputs 02 x relay SPST NO contact, 125VAC@0.3A or 24VDC@1A

4. Operation principles

4.1 General operation principles of iConnector

4.1.1 LED meaning

4.1.1.1 LED status
Status  Meaning
Fixed ON iConnector has been supplied with external power
Blinking (4 seconds blink 1 time) Without external power, iConnector is using battery.
Blinking (2 seconds blink 1 time) Low battery warning (Used for type D battery version)
4.1.1.2 LED modbus
Status  Meaning
Fixed ON Modbus connected
Blinking (1 seconds blink 2 time) Connection errors (wrong configuration of baudrate, noise, …)
OFF No modbus connection
4.1.1.3 LED network
Status  Meaning
Fixed ON Connecting with Globiots
Blinking (1s change state) Initializing wifi generator, waiting for configuration via phone or modbus tool (For iConnector wifi)
OFF No connection with Globiots

4.1.2 Memory Map

Address

Size (bytes)

Memory type

Read/Write

Description

0-0x1FFF

8096

FLASH

R/W

Save active configuration, do not allow log, realtime.

0x2000-0x22FF

768

RAM

R

Save data read from modbus slaves.

0x2300-0x24FF

512

RAM

R

The intrinsic data of iConnector

0x3000-0x30FF

256

RAM

R/W

 

0x5000-0x50FF

256

FLASH

R/W

 

0x6000-0x6FFF

4096

RAM

R

Save data read from modbus slaves

  • Data address area: 0x2000-0x22FF (768 bytes), and 0x6000-0x6FFF (4096 bytes).
  • Controller address area: 0x3000-0x30FF (256 bytes, without flash storage), and 0x5000-0x50FF (256 bytes, with flash storage).

4.1.3 Address area 0x5000-0x50FF

  • 256 bytes;
  • Save in flash (when power is lost, will keep the same value);
  • Allows reading, and writing from Globiots;
  • Allow log (realtime);
  • Allows Modbus write to Slaves;
  • It is not allowed to store data read from Modbus Slaves.

NOTE:

Flash recorded about 100,000 times will be damaged so do not use this area to contain the value is changed several times.

    4.1.4 Logged data

    • Up to 20 different log cycles;
    • 320 log parameters maximum for all log cycles.
    • Up to 120 log parameters per log cycle.

    4.1.5 Modbus

    • Support modbus RTU.
    • Address slave 1… 247.
    • It is not allowed to set address slave = 0.
    • Baudrate 4800/9600/19200.
    • Parity none / odd / even.
    • Up to 100 modbus instructions.
    • The address area for storing read data: 0x2000-0x22FF (768 bytes), and 0x6000-0x6FFF (4096 bytes).
    • Controller address area: 0x3000-0x30FF (256 bytes, without flash storage), and 0x5000-0x50FF (256 bytes, with flash storage).

    4.1.6 Realtime

    • Read up to 200 parameters.
    • If all parameters are float (4 bytes) then read up to 140 parameters.
    • The fastest realtime sending frequency is 1 second.

    4.1.7 Alarm

    • Up to 28 alarms.
    • Supported data types:

    PrmType

    Description

    # Byte

    Range

    1

    BYTE

    1

    0 to 255

    2

    UINT16

    2

    0 to 65,535

    3

    UINT32

    4

    0 to 4,294,967,295

    4

    FLOAT

    4

    -/+3.40282347 * (10^+38)

    5

    INT16

    2

    -32,768 to 32,767

    6

    INT32

    4

    -2,147,483,648 to 2,147,483,647

    4.1.8 Event

    • The event table is 1024 bytes.
    • The number of events depends on the short length of the event configured.
    • Supported data types:

    PrmType

    Description

    # Byte

    Range

    1

    BYTE

    1

    0 to 255

    2

    UINT16

    2

    0 to 65,535

    3

    UINT32

    4

    0 to 4,294,967,295

    4

    FLOAT

    4

    -/+3.40282347 * (10^+38)

    5

    INT16

    2

    -32,768 to 32,767

    6

    INT32

    4

    -2,147,483,648 to 2,147,483,647

    4.1.9 Health data

    • Every 15 seconds send health pack 1 time.

    4.1.10 Relay

    There are 2 relays:

    • Relay control address 1: 0x3100.
    • Relay control address 2: 0x3101.

    4.2 iConnector Cellular

    4.2.1 GSM signal quality

    Value

    RSSI dBm

    Condition

    0-9

    ≤-113 to -95

    Marginal

    10-14

    -93 to -85

    OK

    15-19

    -83 to -75

    Good

    20-31

    -73 to ≥-51

    Excellent

    99

     

    not known or undetectable

    4.2.2 GSM status

    Value

      Status

    0

    Connect to the server: OK

    1

    Connect to network operator: OK, the server is not connected yet

    2

    Communicate with GSM modem with AT command: OK

    3

    The GSM modem is starting

    4.2.3 APN Configuration

    • Use the iConnector Config Software to connect and configure iConnector

    Refer to section 5 for more details about how to use Configuration Cable.

    Refer to section 6 for more details about how to insert SIM Card.

    Refer here for more details on how to add sensor to the iConnector integrated Co-ordinator.

    • Open the 2G / 3G tab, then fill in the APN information of the SIM Card (APN, Username, Password,..) in Setting. Finally click Sync to configure

    iconfig-h2.png

    4.3 iConnector Ethernet

    4.3.1 What is TCP/IP ?

    4.3.2 Configure with iConnector Config software

    Refer to section 5 for more details on how to use Configuration Cable

    4.3.2.1 Ethernet tab

    iconfig-h3.png

    Name Description
    IP Static IP configuration for iConnector. Example: 192.168.1.30
    Gateway Configure gateway
    DNS Server Configure DNS Server
    DHCP

    0 (Off) / 1 (On)

    If DHCP = 0, it's mean Not using DHCPStatic IP

    4.3.2.2 Modbus-TCP-Server tab

    iconfig-h4.png

    Name Description
    Modbus-TCP Port Configure the receiving port, for example 502
    Modbus-TCP enb transparent

    1 : To run transparent, interrupt modbus RTU poll.

    0 : Run modbus RTU poll as normal iConnector, not transparent

    Modbus-TCP timeout (ms) Used for modbus TCP Server

    4.3.3 Description of transparent mode operation (Modbus-TCP enb transparent = 1)

    Suppose we have: Static IP address: 192.168.1.30 | Port 502

    1. iConnector is connected to the Modbus RTU with electric meters, devices, ... via RS485 port;

    2. Software / device / PLC ... with Modbus TCP Client connected to iConnector (role as TCP Server) at Static IP address 192.168.1.30 | Port 502 in internal network;

    3. TCP Client sends command to iConnector;

    4. iConnector transfers commands from Modbus TCP to RTU and sends to devices and clocks via RS485 port;

    5. iConnector waits for the devices to respond;

    6. iConnector transfers the response from the RTU to the Modbus TCP and then sends it back to the TCP Client;

    7. TCP Client actively closes the connection if it no longer sends command to iConnector.

    4.3.4 Run Modbus RTU as normal iConnector (Modbus-TCP enb transparent = 0)

    4.3.4.1 TCP Client connects to iConnector via internet

    1. iConnector needs static IP configuration, For example: IP 192.168.1.30 | Port 502

    2. The external internet network must also have a static IP, Example: IP 118.69.111.101

    3. Network administrator must implement NAT port 502, TCP to IP of iConnector

    4. At that time, TCP Client will connect to IP address 118.69.111.101 | Port 502

    4.3.4.2 TCP Client read/write parameters on the iConnector memmap

    iConnector supports command 3 (0x03) for read, command 16 (0x10) for writing.

    The Unit Identifier is 31 (0x1F) to read and write memmap iConnector, not 31 will make devices transparent read and write via RS485.

    These commands are changed to match the address of iConnector (address in bytes but not in registers like modbus).

    1. Command 3:

    Modbus TCP is:

    0001 0000 0006 1F 03 006B 0003

    • 0001: Transaction Identifier
    • 0000: Protocol Identifier
    • 0006: Message Length (6 bytes to follow)
    • 1F: The Unit Identifier (31 = 1F hex)
    • 03: The Function Code (read Analog Output Holding Registers)
    • 2000: The Data Address of the first register requested This will be the address on the memmap
    • 0003: The total number of registers requested. (read 3 registers 40108 to 40110) This number 3 will be 3 bytes, not 3 registers anymore.

    At that time iConnector will respond to data of 3 bytes, not 6 bytes

    2. Command 16:

    Modbus TCP is:

    0002 0000 0009 1F 10 3000 0002 04 000A

    • 0002: : Transaction Identifier
    • 0000: Protocol Identifier
    • 0009: Message Length (6 bytes to follow)
    • 1F: The Unit Identifier (31 = 1F hex)
    • 10: The Function Code 16 (Write Function)
    • 3000: The Data Address of the first register requested This will be the address on the memmap
    • 0002: The number of registers to write This is the length to write is 2 bytes, not 2 more registers.
    • 04: The number of data bytes to follow
    • 000A: The value to write to register data 2 bytes need to write

    4.4 iConnector Wifi

    4.4.1 Configure using the iConfig app on the phone

    Please refer to how to configure using iConfig app with the following link:

    iConfig Mobile app for Android

    4.4.2 Configure using the Configuration Cable

    Refer to section 5 for more details on how to use Configuration Cable

    Step 1: Open the configuration tool and switch to the Wifi tab;

    iconfig-h5.png

    Step 2: Step 2: Configure the Wifi Name and Password that iConnector Wifi will connect to;

    Step 3: Check the Network LED. If the LED is always on, the connection is successful.

    4.4.3 Modbus-TCP-Server Configuration

    Please refer to the Modbus-TCP-Server configuration section in section 4.3.

    5. Configuration

    5.1 Setup

    Using the configuration cable to connect to the iConnector as below pictures:

    STHC-ISG02DB-WS433-CL-04-H8.png

    Step 1: Install the iConnector Configurator Software in the link below

    https://filerun.daviteq.com/wl/?id=lNjzZbDo7Jwyr1x8DAD3x620tNK5u8lF

    How to use the Configuration Software 

    Step 2: Plug the configuration cable to computer via USB port;

    STHC-ISG02DB-WS433-CL-04-H13.png

    Step 3: Power supply 12-24VDC for Configuration Cable via DC port;STHC-ISG02DB-WS433-CL-04-H11.png

    Step 4: Plug the connector to the configuration port;

    STHC-ISGM1-NB1-2G-H5.png

    5.2 Configure with iConnector Config software

    Serial port configuration on the computer:

    * COMPort, Baudrate: 9600, Parity: None, Stop bit: 1, Data bit: 8

    * Modbus RTU: Reading data by Function 3 / Writing data by Function 16.

    Step 1: Choose COM Port (the Port which is USB cable plugged in). Set the BaudRate: 9600, Parity: none;

    iconfig-h1.png

    Step 2: Click Connect to connect the iConnector with App;

    Step 3: Configure parameters for iConnector.

    6. Installation

    6.1 Example application

    Gateway is used in many applications such as agriculture, power monitoring,... refer Here.

    6.2 Installation location

    To maximize the distance of transmission, the ideal condition is Line-of-sight (LOS) between the Wireless sensor and Gateway. In real life, there may be no LOS condition. However, the Wireless sensor still communicates with Gateway, but the distance will be reduced significantly.

    ATTENTION:

    DO NOT
    install the Wireless sensor or its antenna inside a completed metallic box or housing, because the RF signal can not pass through the metallic wall. The housing is made from Non-metallic materials like plastic, glass, wood, leather, concrete, cement…is acceptable.

      STHC-WS433.png

      6.3 Mounting bracket installation (iConnector Cellular)

      The mounting bracket is made from hard metallic material. Following to these steps as the below picture

      STHC-ISGM1-NB1-2G-H6.png

      6.4 Insert SIM Card for iConnector Cellular

      Steps to insert SIM card:

      Step 1: Using L hex key to unscrew M4 screws at the side of the housing and carefully pull out the top plastic housing in the vertical direction

      STHC-ISGM1-NB1-2G-H10.png

      Step 2: Insert the SIM Card into the iConnector, 

      Please take note the direction of the SIM Card

      When inserting the SIM card please disconnect the power supply to avoid damaging the device !

      STHC-ISG02DB-WS433-CL-04-H16.png

      Step 3: Insert the top plastic housing and locking by L hex key

      ATTENTION:

      When reinstalling the cover, pay attention to put the PCB edge into the middle slot of the box inside as shown below)

      STHC-ISGM1-NB1-2G-H11.png

      7. Troubleshooting

      No. Phenomena Reason Solutions
      1 Cannot read modbus
      • No power supply, the power cord is incorrectly connected
      • Modbus connection pin A, B is loose or wrong
      • Configuration slave address, baudrate, parity is not correct
      • Reading the wrong command, wrong address register
      • Check the power connection
      • Check the connection modbus A, B
      • Check the configuration of slave address, baudrate, parity
      • iConnector only supports modbus 3, 4, and 16. Check if the value of modbus status returned by 2 or 3 is an incorrect address reading.
      2

      Failed to add auto sensor

      (iConnector integrated Co-ordinator version)

      • When the first 5 minutes are up, the sensor cannot be added
      • Node needs to be added further away from WS433-CL
      • The iConnector and the node are configured to run at 2 different RF frequencies, or different data rates
      • Unplug, wait 10 seconds, plug in again to enable automatic add or write to modbus Enb_auto_add_sensors = 1
      • Bringing nodes and iConnector together or temporarily setting the smaller Rssi_threshold can add sensors farther (then return the old values)
      • Check the RF frequency, data rate of iConnector and the node
      3 Read modbus normal health values but read the data of the node, all are 0
      • The modbus 4 command only supports FW 1.9, old FWs can't read command 4
      • Check the FW of WS433-CL in iConnector if it is older than 1.9 then use command 3 to read data and other registers
      4 The node's data has no data of prm1 and prm2
      • The sensor attached to the node is loose
      • For the WS433-M12F node, if the sensor is attached after the battery is attached to the node, the sensor type may be different so the data cannot be read.
      • Attach the sensor to the node firmly
      • Attach the sensor to the WS433-M12F node first. Then remove the node pin, wait for 10 seconds, re-attach to the node to re-identify the sensor
      5 Status led of iConnector doesn’t light
      • No power supply
      • Check if the power cable is disconnected
      • Check if the connector of iConnector is loose or disconnected
      6 Mobus led of iConnector doesn’t light
      • No RS485 connection
      • Check if the signal cable is loose or disconnected
      7 Network led of iConnector doesn’t light
      • No network connection
      • Check if the power cable is disconnected
      • Check if the connector of iConnector is loose or disconnected

      8. Support contacts

      Manufacturer

      logo-01.png

      Daviteq Technologies Inc
      No.11 Street 2G, Nam Hung Vuong Res., An Lac Ward, Binh Tan Dist., Ho Chi Minh City, Vietnam.
      Tel: +84-28-6268.2523/4 (ext.122)

      Email: info@daviteq.com | www.daviteq.com

       

      Distributor in Australia and New Zealand

      temploggerlogo.png

      Templogger Pty Ltd

      Tel: 1800 LOGGER

      Email: contact@templogger.net