Info
Content

I. QUICK GUIDE

1. Introduction

1.1 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 RTU, EthernetIP, Wireless sensor network...It connects to server system via LAN/WAN as Ethernet, WiFi or Cellular.

image-1736414444429.png

 

 

1.2 System architecture

1.2.1. Connect instruments to GLOBIOTS Platform

image-1736414202836.png

1.2.2. Connect wireless sensor to GLOBIOTS Platform

image-1736414947528.png

1.2.2. Connect wireless sensor to any PLC or HMI/SCADA

image-1736415275773.png

2. Application note

3. iConnector communication

3.1. Slave device communication

3.1.1. Modbus RTU Master

In this function, iConnector work as a Modbus RTU Master. It can poll for data from and write data to external Modbus Slaves connected to it through RS485 physical protocol. 

3.1.2. Wireless co-ordinator

Thanks to the wireless co-ordinator has been integrated in the iConnector, it is able to connect with any Daviteq Sub-GHz devices. By the Sub-Ghz technology from Texas Instruments, it is easy to establish multiple networks in same area without interference or channel conflict. One co-ordinator can handle maximum of 40 end nodes in its network. Prefer the link below to reach more detail information of this function 

Long Range Wireless Co-ordinator WS433-CL manual

3.2 Host communication

The iConnector are designed to connect to Daviteq Platform, aka Vizuo Globiots. Vizuo Globiots is a web-based software application to remotely configure device, parameter, alarm and event. In addition, Vizuo displays current values, historical values of parameters as well as events, alarms. Values of parameter are stored on database of GLOBIOTS server. 

In additional, iConnector is able to send data to any servers via common protocols such as HTTP, FTP, UDP/IP,...

Refer Section 10. How to connect device to Back-end/ Server to see more detail instruction.

4. Default Configuration

4.1. UDP Server

The iConnection was configured to connect to Daviteq's platform 

Parameters Default value
UDP_SERVER_HOST dataengine.globiots.com
UDP_SERVER_PORT 9000
DRM_TIMEOUT (sec) 20
TIME_ZONE 7

4.2. Main network

In default mode, the iConnector connects to server through WIFI. Refer section xx.xx to see how to change the network mode. 

4.3. Wireless co-ordinator

Parameters Default value
Modbus address 1
Modbus baudrate 9600 bps
Modbus parity none
Radio frequency 433.92 MHz
Tx power 15 dBm
Data rate RF 50 kbps

5. Battery/ Power Supply

iConnectors are powered via M12 Male connector. The power supply range is 7..48VDC, avg 200mA, peak 1.5A

Detail wiring instruction, please refer section 8. Installation and wiring.

6. What's in the Package?

7. Guide for Quick Test

7.1. Connecting the iConnector to the Daviteq Platform

Refer section x.xx to see how to use the iConfig software

Step 1: Configure the iConnector via iConfig software
  •  Get basic information of the iConnector to register it into Daviteq Platform including Serial number & FCC

image-1736390857113.png

  • Setup network information in order that the iConnector can go online in the internet. Base on your application, you should configure wifi or ethernet information.

WIFI mode

In this mode, there are three parameters must be configured, including MAIN_NETWORK , WIFI_NAME, WIFI_PASSWORD

Parameters Description
MAIN_NETWORK 1: WIFI mode
2: ETHERNET mode
WIFI_NAME Wifi name of WIFI network
WIFI_PASSWORD Password of WIFI network

image-1736391975822.png

ETHERNET mode

In this mode, there are five parameters should be configured, including MAIN_NETWORK , ETHERNET_STATIC_IP, ETHERNET_GATEWAY, ETHERNET_DNS_SERVER, ETHERNET_DHCP_ENABLE

Parameters Description
MAIN_NETWORK 1: WIFI mode
2: ETHERNET mode
ETHERNET_STATIC_IP The static IP of Ethernet network use for iConnector.
If running DHCP mode, ignore this parameter
ETHERNET_GATEWAY The default gateway of Ethernet network use for iConnector.
If running DHCP mode, ignore this parameter
ETHERNET_DNS_SERVER The DNS server of Ethernet network use for iConnector.
ETHERNET_DHCP_ENABLE 0 = DISABLE, 1 = ENABLE

image-1736392182743.png

image-1736392360118.png

The parameter MAIN_NETWORK is located in the WIFI tab of the software, while other parameters are in the ETHERNET tab.

Step 2: Read data of iConnector from Daviteq Platform
  • Access to Vizuo Globiots via the link https://vizuo.globiots.com and login to the system with the username and password supplied Daviteq.

image-1736393181856.png

  • Register the iConnector into Globiots
    • RIGHT-CLICK on the corresponding site in the Organization Chart => New=>Device

image-1736393787388.png

    • There are some fields must be configured, including Name, Serial number, Device ID, FCC, Memmap, Logging send frequency, Health send frequency. After the fields were configured => Click Save button
      Fields Description
      Name Optional name, must be 12 characters
      Serial number Serial number of iConnector
      *Taken from step 1
      Device ID Click Generate button in the software
      FCC FCC of iConnector
      *Taken from step 1
      Memmap Choose SUB-GHZ VIEW 2
      Logging send frequency Choose 3 minutes
      Health send frequency Choose 5 minutes

image-1736394309373.png

image-1736394276700.png

  • Add parameter to read data from the iConnector
    • Download the parameter file in link xxxxx 
    • Right-click on the device=>Pararameter

image-1736411690404.png

    • Click Import Parameter button

      image-1736412898600.png

 

    • Choose the parameter file=> Tick Replace option=> Click Import button

image-1736413052800.png

  • Add basic dashboard to show data of the iConnector
    • Download the dashboard file in link xxxxx
    • In Home screen, select Management => select sub-menu Dashboard
    • Click Stop button=> Click Import button

image-1736413581109.png

 

 

    • Choose the Dashboard file=> Tick 01 TEST ICONNECTOR => Click Import button
  •  image-1736413640913.png
  •  

 

7.2. Read data of Wireless sensors from Globiots

Make sure the process in section 7.1 was completed successfully.

Step 1: Add Sub-GHz sensor to the iConnector

- Open software=> import template

- Install the batteries to the wireless sensor, then touch the sensor to the iConnector'antenna. If the iConnector sound "beep", it mean the paring process is successful.

Step 2: Read data from Daviteq Platform

- Create the parameter

- Create the modbus command

- Add the basic dashboard to show data

7.3. Read data of Modbus slave from Globiots

Make sure the process in section 7.1 was completed successfully.

Step 1: Establish the RS485 network among iConnector and modbus slaves

- wiring

- get modbus information of slave devices

Step 2: Read data from Daviteq Platform

- Create the parameter

- Create the modbus command

- Add the basic dashboard to show data

7.4. Modbus TCP/IP converter function

Principle Flow of this function as below

  • iConnector is connected to the Modbus RTU slave as with electric meters, devices, ... via RS485 port;
  • Software / device / PLC ... with Modbus TCP Client connected to iConnector (role as TCP Server) 
  • TCP Client sends command to iConnector;
  • iConnector transfers commands from Modbus TCP to RTU and sends to devices via RS485 port;
  • iConnector waits for the devices to respond;
  • iConnector transfers the response from the RTU to the Modbus TCP and then sends it back to the TCP Client;
  • TCP Client actively closes the connection if it no longer sends command to iConnector.

Step 1: Configure the iConnector via iConfig software

Refer section x.xx to see how to use the iConfig software

  • Configure the iConnector at Ethernet tab

iConfig-1.png

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

Configure to 0, it's mean Not using DHCP → Static IP
  • Configure the iConnector at Modbus tab

image-1735869531156.png

Name Description
MODBUS_BAUD_RATE Configure the modbus baudrate to 9600 bps
MODBUS_PARITY Configure the parity to none
MODBUS_TIMEOUT Configure the modbus timeout to 1000 ms
MODBUS_POLL_CYCLE Configure the modbus poll cycle to 1s
MB_TCP_SERVER_PORT Configure the receiving port to 502
MB_TCP_SERVER_ENABLE_TRANSPARENT

Configure to 1 : To run transparent, interrupt modbus RTU poll.
MODBUS_TCP_SERVER_TIMEOUT Used for modbus TCP Server

Step 2: Read data of iConnector from TCP/IP Client software

In this guide, we use Easy Modbus Client software. You can use any other Modbus TCP/IP client software

  • Connect the iConnector to the PC via LAN cable.
  • Connect the Modbus RTU slave to the iConnector via RS485 cable.
  • Power on the devices
  • In TCP/IP Client software, input correct Server IP Adresss and Port that configured in step 1. Then, click Connect button. If the status at the bottom show "Connected to server", it means the successful connection.

image-1736324111418.png

Ensure that the IP address of the PC is configured within the same subnet as the TCP/IP server address set on the iConnector in Step 1.

  • Read a parameter base on the modbus memory map of slave device. For example, read a register 30001 of the Modbus slave 

    image-1736324748553.png

8. Installation and wiring

8.1.Installation and wiring for iConnector

 

image-1735956821705.png

8.2 Installation and wiring for wired slave device

 

8.3 Installation and wiring for wireless sensor

 

8.4 Installation and wiring for host Modbus TCP/IP

Connect the iConnector with TCP/IP client via the LAN cable.

9. Payload Document and Configuration Tables

10. How to connect device to Back-end/ Server

10.1 How to connect device to Globiots platform

10.2 How to connect device to http server

10.3 How to connect device to Modbus TCP/IP server (only for ...with Ethernet connection)

No Comments
Back to top