Smart IoT Gateway - iConnector USER GUIDE FOR ICONNECTOR 3G INTEGRATED WIRELESS CO-ORDINATOR STHC-ISG02DB-WS433-CL-04 STHC-ISG02DB-WS433-CL-04-MN-EN-01 FEB-2020 This document is applied for the following products SKU STHC-ISG02DB HW Ver. 3.3 FW Ver. 3.4 WS433-CL-04 HW Ver. 2.3 FW Ver. 1.9.3 Item Code STHC-ISG02DB-WS433-CL-04 iConnector 3G Dual Band*, internal GSM antenna, integrated wireless co-ordinator with 0 dbi external antenna, M12 male connector, RS485 ModbusRTU 1. Functions Change Log HW Ver. FW Ver. Release Date Functions Change Gateway 3.3 3.4 NOV-2019 Co-odinator 2.3 1.9.3 NOV-2019 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... This iConnector is build-in a wireless co-ordinator in a wireless sensor network, a high-performance type to facilitate remote configuration and diagnostics, as well as remote monitoring and control via any IIoT platform. It is able to configure the parameters for all end nodes in the network. 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. LOS transmission distance up to 6000m. The installation and configuration is very simple. Setting up a wireless sensor network has never been this easy. 3. Specification Host Communication Cellular type Dual band (2100/900)/3G, internal GSM antenna, integrated wireless co-ordinator Fieldbus communcation ModbusRTU x 01 port Data speed Up to 50kbps Tranmission distance LOS 6000m @ 50 kpbs (antenna height is 4m minimum) Antenna Standard external antenna 0 dbi, option 3dbi, 6dbi, 9dbi Power supply 7..48VDC, avg 200mA, peak 1.5A On-board memory & sensors 2MB Flash, PCB temperature sensor Electrical connector M12-female, 4-pin A-coding Buzzer Internal buzzer Back-up battery Lithium Super Capacitor RF frequency band Free license ISM 433.92Mhz (for others 868, 915, 920Mhz, refer related datasheets) Ready to comply ETSI EN 300 220, EN 303 204 (Europe) FCC CFR47 Part15 (US), ARIB STD-T108 (Japan)** Vietnam Type Approval Certification QCVN 73:2013/BTTTT, QCVN 96:2015/BTTTT (DAVITEQ B00122019) Security Standard AES-128 Operating temperature -40oC..+85oC SIM slot 01 x micro-SIM Housing Aluminum + Polycarbonate, IP67 Included accessories Mounting bracket for wall mount Product dimension H106 x W73x D42 mm (excluded antenna) Net weight 190 grams Box dimension W160 x D150 x H100 mm Gross weight < 300g 4. Product Pictures 5. Operation Principle After the power supply will have 5 minutes to add nodes (value enb_auto_add_sensors = 1 in 5 minutes then = 0), push button function and hall sensor are only available in the first 5 minutes Push Button or Hall sensor for the first 5 minutes when power is available: Press and hold the push button or bring the magnet near the Hall sensor for 2s => see the LED blink once or the buzzer will ring 1 Beep => release the push button or take the magnet to set Data rate RF 50kbps Press and hold the push button or bring the magnet near the Hall sensor for 5s => see the LED blink twice or the buzzer beep 2 Beep => release the push button or take the magnet to set Data rate RF 625bps Press and hold the push button or bring the magnet near the Hall sensor for 10s => see the LED blinking 3 times or the buzzer buzzes 3 Beep => release the push button or take the magnet to perform the User factory reset (User factory reset = reset frequency number, RF transmit power, data rate, Node ID of 40 WS, Modbus operating parameters, compare time for data status) If it takes more than 30 seconds, the button will be deactivated 5.1 Add Sensor Node Add Sensor Node ID automatically Step 1: After supplying power the iConnector via M12 connector, the Node ID must be registered within the first 5 minutes, up to 40 WS. Step 2: Bring the wireless sensor closer to the iConnector's antenna then take off the wireless sensor battery, wait for 5s then insert the battery again. If: Buzzer plays 1 peep sound, LED blink 1 time, that means registering Node ID on iConnector successfully. Buzzer plays 2 peep sounds, LED blink 2 times, that this Node ID is already registered. If you do not hear the "Peep" sound, please disconnect the power the iConnector, wait a few minute and try again. Node id added in this way will be written to the smallest node_id_n address which is = 0. Set Rssi_threshold (see RF MODE CONFIG (in the Modbus Memmap of WS433-CL), default -25): The case if Co-ordinator is on high position and need to add node sensor. We set the sensor as close as possible and set the Rssi_threshold to -80, -90 or -100 to increase the sensitivity to allow iConnector can add sensors at a longer distance. After that, perform 2 steps of adding sensors and then reset Rssi_threshold = -25. Enb_auto_add_sensors configuration (see RF MODE CONFIG (in the Modbus Memmap of WS433-CL)): In case you do not want to turn off the power iConnector, you can set Enb_auto_add_sensors = 1, this way we have 5 minutes to add nodes (add up to 40 nodes) . After 5 minutes Enb_auto_add_sensors will automatically = 0. Configuration Protocol: Modbus RTU Address: 1 - 247 Baud rate: 9600 , 19200 Parity: none, even, odd Stop bits: 1 Memmap resgisters You can download Modbus Memmap of WS433-CL-FW_V2.0 with the following link: https://filerun.daviteq.com/wl/?id=BKEaUzdArkoc0Hc7nfpRShdPVToVrqQZ 5.2 Check after configuring the iConnector First, you need to prepare Step 1: Open Modbus tool on PC You can download Daviteq Modbus Configuration Tool Version 1.4 with the following link: https://filerun.daviteq.com/wl/?id=qK0PGNbY1g1fuxTqbFW9SXtEvCw7bpc6 Unzip TOOLS-SW-EN-02.zip and run file application "Daviteq Modbus Configuration Tool Version" Choose COM Port (the Port which is USB cable plugged in) Set the BaudRate: 9600, Parity: none Click “ Connect “ untill the Status displays “disconnected” to “connected“. It means the WS433-CL-04 is being connected with computer; Next, we need to import the configuration file for WS433-CL-04 by importing the csv file: Go to MENU: FILE / Import New / => select the file with name Template_WR433_V1.6.csv. This file is attached in the zip file. Step 2: Check information of sensor after adding S/N of each sensor 5.3 SIM configuration iConnector 3G uses micro-SIM and needs to be configured to use the data network Open iConnector cover and install the SIM card Based on the information of the mobile carrier that provides the SIM card, we configure data such as APN, username, password on the 2G/3G tab How to use iConnector config tool (Click Here) 5.4 Reset sensor and iConnector sensor node Step 1: Connect Antenna, RS485 - configuration cable and power supply co-ordinator Step 2: Put the magnet closer to the icon on iConnector until you hear "peep" 3 times to reset (2 times for 625 kps option) Step 3: Take off the sensor cover and press the button until you see LED flashes 3 times to reset (2 times for 625 kps option) 6. Installation 6.1 Mounting bracket installation The mounting bracket is made from hard metallic material. Following to these steps as the below picture 6.2 Installation location To maximize the distance of transmission, the ideal condition is Line-of-sight (LOS) between the two modules. In real life, there is no LOS condition. However, the two modules still communicate each other, but the distance will be reduced significantly. Therefore, to maximize the transmission distance, please pay attention to the following conditions: DO NOT install the wireless module inside a complete metallic box or housing. The signal can not pass through metallic wall; This wireless module would be installed a semi-metallic box, because the RF signal can pass through the non-metal wall/are; The best case is to install the wireless module inside or Non-metallic box; Some non-metallic materials: plastic, glass, wood, leather, concrete, cement… 6.3 IO Wiring & Sensor installation 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 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 Daviteq Technologies IncNo.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 Templogger Pty Ltd Tel: 1800 LOGGER Email: contact@templogger.net USER GUIDE FOR ICONNECTOR 3G STHC-B-ISG02DB-03 STHC-B-ISG02DB-03-MN-EN-01 Jul-2020 This document is applied for the following products SKU STHC-B HW Ver. 1.1 FW Ver. 1.4 Item Code STHC-B-ISG02DB-03 Iconnector 3g Dualband, internal antenna, 1 x battery size D 3.6VDC and external DC power, 1 x pulse input, 1 x 4-20mA input with 15v supply to external sensor, Ip67, 1 x M12-M for power, 1 x M12-F for IO 1. Functions Change Log HW Ver. FW Ver. Release Date Functions Change 1.1 1.4 Jun-2020 2. Introduction STHC-B is same as STHC, is a Smart IoT Gateway, aka iConnector, a main component in any IoT application. However, STHC-B is operated by a Primary battery 3.6V, suitable for applications where no grid power like Water pipeline, water network...In addition, STHC-B is also powered by external power supply 7..48VDC or Solar panel system. STHC-B has built-in 1 Pulse input to read the Pulse from flow meter...and 01 Digital input can connect to Pressure sensor, Level, Temperature, Humidity... Data will be sent back to server for data logging, data analytics, monitoring & controls...With Ultra low power design, it can uses 01 battery size D for up to 05 years (depend on configuration of data logging and sending). 3. Specification Host Communication GPRS Quadband/3G-Dual band/NB-IoT, internal antenna Host communication supports TCP/IP, UDP/IP, FTP, HTTPS, SNMP... Vietnam Type Approval Cerification QCVN 54:2011/BTTTT, QCVN 15:2015/BTTTT (DAVITEQ B00122019) Analog Input 1 x 4-20ma input with 15v supply to external sensor Pulse Input 1 x Pulse input with counting function, dry-contact, max 1Hz, auto-reset counter when reaching 9 digits Digital Sensor Input 1 x Digital sensor input for DULP sensor type (Digital Ultra Low Power ), M12 connector, IP67 Battery Supply 1 x D size battery holder, 3.6VDC External Power Supply 7..48VDC, avg 200mA, peak 1.5A Back-up battery Lithium Super Capacitor (to alert shortage of power supply) On-board logging 2MB Flash SIM slot 01 x micro-SIM Operating Temperature -20 .. + 85 degC (refer temperature working range of Battery being used) Dimension H110xW110xD70 Housing Poly-carbonate housing, IP67, wall mount pads Net weight < 250 g (excluded Battery and Sensor) 4. Applications 5. Operation principle 5.1 Process of measurement When the sensor sampling interval is reached, for example, 2 minutes (Battery Mode), iConnector will wake up and turn ON the power to supply power to the external sensor to start measuring. Depending on the type and characteristics of the external sensor, it may take a certain time to complete the measurement. For example, the measurement time is 200mS, after this time, iConnector will read the value of the sensor by I2C, it will switch the power OFF to the external sensor to save energy. If we supply external power through M12 connector, iConnector will run realtime. After reading the sensor value, the raw data is X, it can be scaled to any technical value by the following formula: Y = aX + b Where X: the raw value from sensor Y: the calculated value for parameter 1's value or parameter 2's value a: constant b: constant So, if there is no user setting for a and b ==> Y = X The Y value will be compared with Lo and Hi threshold. 5.2 Configuration via Memory map We can configure online using the memmaps shown in the table below: ADDRESS (in decimal) ADDRESS (in hex) LENGTH (in byte) TYPE NAME DESCRIPTION UNIT Server 8960 2300 4 float power supply External power supply voltage volt R 8964 2304 4 float battery Battery voltage volt R 8982 2316 1 byte gsm signal quality GSM signal strength R 902 386 4 uint32 I2C: sample_rate (sec) sensor reading cycle, e.g: 60 seconds. sec R/W 906 38A 2 uint16 I2C: calc_time (ms) time of supplying power to the sensor before reading the I2C, e.g: 200 ms. ms R/W 908 38C 2 uint16 I2C: num_of_sample The number of ADC samples taken in a reading of sensor data, the more samples the longer the sensor reading time. For example: 8 samples with each sample have a reading time of 10ms, then the total sampling time is 80ms. 910 38E 4 float I2C: prm1_a The a constants after calculation according to the formula R/W 914 392 4 float I2C: prm1_b The b constants after calculation according to the formula R/W 918 396 4 float I2C: prm1_hi_cut Cut the upper threshold of I2C e.g: If prm1_scaled_value > prm1_hi_cut then prm1_scaled_value = prm1_hi_cut R/W 922 39A 4 float I2C: prm1_lo_cut Cut the lower threshold of I2C e.g: If prm1_scaled_value < prm1_lo_cut then prm1_scaled_value = 0. R/W 9398 24B6 1 uint8 I2C: sensor type Sensor type = 20 means that the I2C sensor reads 4-20mA R/W 9399 24B7 1 uint8 I2C: error status if error status = 0, it means the sensor reading is OK, else error status = 1 is faulty. R/W 9400 24B8 4 float I2C: prm1_scaled_value The measured value has been scaled for the sensor Formula to calculate scale: prm1_scaled_value = prm1_raw_value * prm1_a + prm1_b R/W 9408 24C0 4 float I2C: prm1_raw_value Raw sensor value read from I2C R/W 5.3 Offline configuration 5.3.1 Connection First, you need to prepare Step 1: Open the cover of the iConnector Step 2:Connect the Configuration Cable to the UART Port in iConnector Step 3: Power the iConnector via M12 male connector on iConnector Step 4: Connect the USB port of the Configuration Cable to the Computer 5.3.2 Configuration tool You can download Configuration Tool with the following link: https://filerun.daviteq.com/wl/?id=s5QApxosVNZLbATxi0TtKVoJX4ms1PxD Unzip file and run file application "iconnector_config" Choose COM Port (the Port which is USB cable plugged in) Set the BaudRate: 9600, Parity: none Click “ Connect “ untill the Status displays “disconnected” to “connected“. It means the iConnector is being connected with computer; Configuration parameters: Write in the Setting column the data to be configured into iConnector Click Sync to synchronize data into iConnector After synchronizing the data into iConnector, if the data displayed in the Value column shows the corresponding data, the configuration is completed. 5.4 SIM configuration iConnector 3G uses micro-SIM and needs to be configured to use the data network Open iConnector cover and install the SIM card Based on the information of the mobile carrier that provides the SIM card, we configure data such as APN, username, password on the 2G/3G tab 5.5 Configure sensor parameters on the iConnector 5.5.1 Configure I2C_Sensor tab We configure the parameters of 4-20mA sensor in I2C Sensor tab: I2C: sample_rate (sec) sensor reading cycle, e.g: 60 seconds. I2C: calc_time (ms) time of supplying power to the sensor before reading the I2C, e.g: 200 ms. I2C: num_of_sample The number of ADC samples taken in a reading of sensor data, the more samples the longer the sensor reading time. For example: 8 samples with each sample have a reading time of 10ms, then the total sampling time is 80ms. I2C: prm1_a The a constants after calculation according to the formula I2C: prm1_b The b constants after calculation according to the formula I2C: prm1_hi_cut Cut the upper threshold of I2C e.g: If prm1_scaled_value > prm1_hi_cut then prm1_scaled_value = prm1_hi_cut I2C: prm1_lo_cut Cut the lower threshold of I2C e.g: If prm1_scaled_value < prm1_lo_cut then prm1_scaled_value = 0. I2C: sensor type Sensor type = 20 means that the I2C sensor reads 4-20mA I2C: error status if error status = 0, it means the sensor reading is OK, else error status = 1 is faulty. I2C: prm1_scaled_value The measured value has been scaled for the sensor Formula to calculate scale: prm1_scaled_value = prm1_raw_value * prm1_a + prm1_b I2C: prm1_raw_value Raw sensor value read from I2C 5.5.2 Operation mode of iConnector with different power sources When iConnector only works with D type battery: 3G network will turn off, only when the 3G data sending cycle is turned on to send data, after sending it will turn off. Not sending a ping leads to iConnector not running realtime, unable to sync from the server. Unable to configure from iConfig software. When iConnector is connected to 7-48VDC power source: 3G network is always on, running Ping and ready to receive realtime, synchronization, running full of features. Can be configured from iConfig software. 6. Installation 6.1 iConnector Installation Installed on a wall or in non-metal box. DO NOT install iConnector inside a complete metallic box or housing. The signal can not pass through metallic wall. iConnector should be installed in a semi-metallic box. Some non-metallic materials: plastic, glass, wood, leather, concrete, cement… 6.2 IO Wiring & Sensor installation Install the sensor as shown below: Step 1: Open the back cover of the sensor Step 2:Wiring to sensors Step 3: Connect Sensor to Input 4 .. 20mA port of iConnector via M12 connector For more information about DP transmitter: https://filerun.daviteq.com/wl/?id=lT9lfZuEQUQksWLhFgSoQrs28sEGY0Kt 6.3 Power Supply & Battery installation 6.3.1 Power Supply of iConnector Connect 7 .. 48VDC power supply to iConnector via M12 Male connector Use M12 female connection cable to connect to iConnector 6.3.2 Battery installation Steps for battery installation: Step 1: Using Flat Tip Screwdrivers to open the cover Step 2: Carefully pull out the top plastic housing Step 3: Insert the type D battery 3.6VDC, please take note the poles of battery Step 4: Insert the top plastic housing and locking by Flat Tip Screwdrivers 7. Troubleshooting No. Phenomena Reason Solutions 1 The value of the sensor is 0 Sensor connecting 4-20mA is loose/not connected Check sensor connection 2 The iConnector does not connected to the sever No power supply The network information of the SIM card data is incorrect No SIM card inserted Check the power supply Check that the battery is empty or not installed correctly Check the sim card configuration section 3 The battery drains quickly Turn On/Off tab configuration is incorrect Check the configuration of the Turn On/Off tab USER GUIDE FOR ICONNECTOR CELLULAR CAT M1, NB1, 2G, GLOBAL BAND STHC-ISGM1-NB1-2G-NC STHC-ISGM1-NB1-2G-01-MN-EN-01 SEP-2020 This document is applied for the following products SKU STHC HW Ver. 3.3 FW Ver. IoT_N1.0 Item Code STHC-ISGM1-NB1-2G-NC iConnector CAT M1, NB1, 2G, Global Band, internal antenna, with 02 relays 1. Functions Change Log HW Ver. FW Ver. Release Date Functions Change 3.3 IoT_N1.0 SEP-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. 3. Specification Host Communication CAT M1, NB1, 2G, Global Band, internal antenna 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 Battery Lithium Battery 3.7VDC 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 principle 4.1 Modbus communication 4.1.1 Configuration Protocol: Modbus RTU Address: 1 - 247 Baud rate: 4800, 9600, 19200 Parity: none, even, odd Stop bits: 1 4.1.2 Configuration via Memory map We can configure online using the memmaps shown in the table below: Note:   R: Read, W: Write IConnector health configuration area: ADDRESS (in decimal) ADDRESS (in hex) LENGTH (in byte) TYPE NAME DESCRIPTION UNIT Server 8960 2300 4 float power supply External power supply voltage volt R 8964 2304 4 float battery Battery voltage volt R 8982 2316 1 byte gsm signal quality GSM signal strength R Configuration area 0x7F80: ADDRESS (in decimal) ADDRESS (in hex) LENGTH (in byte) TYPE NAME VALUE (Recommended) DESCRIPTION Server 32640 7F80 20 string CAT-M1 Band R/W 32660 7F94 20 string NB1 Band R/W 32680 7FA8 1 byte RAT1 0: Configuration running Cat-M1 only, not using RAT2, RAT31: Cat-M12: NB13: GPRS R/W 32681 7FA9 1 byte RAT2 0: Not using RAT2, RAT31: Cat-M12: NB13: GPRS R/W 32682 7FAA 1 byte RAT3 0: Not using RAT31: Cat-M12: NB13: GPRS R/W 32683 7FAB 1 byte apply_new_LTE write 1 to apply new LTE config R/W 32684 7FAC 1 byte attach_network_times 10 Number of attempts to connect to 1 RAT before switching to the next RAT when connection failed; RAT1 => RAT2 => RAT3 => RAT1; One connection attempt takes about 10-20 seconds. R/W 32685 7FAD 1 byte R/W 32686 7FAE 2 uint16 time_RAT1 Every time_RAT1 minutes will try to reconnect to RAT1 if it is currently running at RAT2 or RAT3 R/W 32688 7FB0 2 uint16 time_FOTA 0 After time_FOTA minutes will connect to the server of Sierra Wireless 1 time to check for FW updates or not; Write 0 to turn off FOTA. R/W Configuration Relay: ADDRESS (in decimal) ADDRESS (in hex) LENGTH (in byte) TYPE NAME DESCRIPTION UNIT Server 12416 3080 1 byte relay 1 0: OFF, 1: ON R/W 12417 3081 1 byte relay 2 0: OFF, 1: ON R/W Configuration modem, SIM: ADDRESS (in decimal) ADDRESS (in hex) LENGTH (in byte) TYPE NAME DESCRIPTION UNIT Server 160 A0 20 string modem hl serial R 180 B4 20 string imei identification text for determination of the individual ME R 200 C8 20 string imsi International Mobile Subscriber Identity R 220 DC 20 string iccid SIM Card Identification R 240 F0 16 string modem hl fw ver R 9056 2360 10 string Model identifier R 9066 236A 22 string Active LTE Band R 4.2 Offline configuration First, you need to prepare Step 1: Connect iConnector to RS485 - configuration cable via  and power supply iConnector Step 2: Open Modbus tool on PC You can download iConnector Configuration Tool with the following link: https://filerun.daviteq.com/wl/?id=lNjzZbDo7Jwyr1x8DAD3x620tNK5u8lF How to use the Modbus configuration software Step 3: Open Modbus tool on PC Unzip file and run file application "iconnector_config" Choose COM Port (the Port which is USB cable plugged in) Set the BaudRate: 9600, Parity: none • Write in the Setting column the data to be configured into iConnector;• Click Sync to synchronize data into iConnector;• After synchronizing the data into iConnector, if the data displayed in the Value column shows the corresponding data, the configuration is completed. SIM CARD CONFIGURATIONBased on the information of the mobile carrier that provides the SIM card, we configure data such as APN, username, password on the 2G/3G tab. 4.2.1 Configure CAT-M1 Band and NB1 Band Band bitmap in hexadecimal format without the 0x prefix. This is the logical representation of 1 << (BandNumber - 1). (Currently only used for RAT CAT-M1 and NB-1.) 0000 00000000 00000000 Not available 0000 00000000 00000001 LTE Band 1 (2000 MHz) 0000 00000000 00000002 LTE Band 2 (1900 MHz) 0000 00000000 00000004 LTE Band 3 (1800 MHz) 0000 00000000 00000008 LTE Band 4 (1700 MHz) 0000 00000000 00000010 LTE Band 5 (850 MHz) 0000 00000000 00000080 LTE Band 8 (900MHz) 0000 00000000 00000100 LTE Band 9 (1900MHz) 0000 00000000 00000200 LTE Band 10 (2100MHz) 0000 00000000 00000800 LTE Band 12 (700 MHz) 0000 00000000 00001000 LTE Band 13 (700 MHz) 0000 00000000 00010000 LTE Band 17 (700 MHz) 0000 00000000 00020000 LTE Band 18 (800MHz) 0000 00000000 00040000 LTE Band 19 (800MHz) 0000 00000000 00080000 LTE Band 20 (800MHz) 0000 00000000 01000000 LTE Band 25 (1900MHz) 0000 00000000 02000000 LTE Band 26 (800 MHz) 0000 00000000 04000000 LTE Band 27 (800 MHz) 0000 00000000 08000000 LTE Band 28 (700MHz) 0002 00000000 00000000 LTE Band 66 (1800MHz) configure multiple bands, add them up according to hexadecimal. For example: Configure band 2, 3, 4, 5, then add (0x02 + 0x04 + 0x08 + 0x10) = 0x1E => Band configuration is 1E (the leading zeros can be removed) 4.2.2 RAT1 configuration 0 Configuration running Cat-M1 only, not using RAT2, RAT3 1 Cat-M1 2 NB1 3 GPRS 4.2.3 RAT2 configuration 0 Not using RAT2, RAT3 1 Cat-M1 2 NB1 3 GPRS 4.2.4 RAT3 configuration 0 Not using RAT3 1 Cat-M1 2 NB1 3 GPRS 4.2.5 Configure Apply new LTE After configuring we write down 1 to apply the new configuration, go back to RAT1. After execution, ICT will automatically reset to 0. 4.2.6 Configure Attach Network Times Number of attempts to connect to 1 RAT before switching to the next RAT when connection failed; RAT1 => RAT2 => RAT3 => RAT1; One connection attempt takes about 10-20 seconds. 4.2.7 Configure Time RAT1 (min) Every minute of time_RAT1 will try to reconnect with RAT1 if it is currently running in RAT2 or RAT3. Minimum 15 minutes. 4.2.8 Configure Time FOTA (min) After time_FOTA minutes will connect to the server of Sierra Wireless 1 time to check for FW updates or not; Write 0 to turn off FOTA. → Use to update the new FW for the HL7802 modem. 4.3 Operational principle of RAT1, RAT2, RAT3 When the ICT is started, it will connect to RAT1 first. If the connection is successful, it will run at RAT1. If the ICT connecting to RAT1 fails, it will try to reconnect (Attach Network Times) times. If not, it will be transferred to RAT2. If successfully connected to RAT2 it will run at RAT2. If the ICT connecting to RAT2 fails, it will try to reconnect (Attach Network Times) times. If not, it will be transferred to RAT3. If successfully connected to RAT3 it will run at RAT3. If the ICT connection to RAT3 fails, it will try to reconnect (Attach Network Times) times. If not, it will be transferred to RAT1. If successfully connected to RAT1 it will run at RAT1. Every time_RAT1 minutes will try to reconnect to RAT1 if it is currently running at RAT2 or RAT3. Write 1 to Apply new LTE then ICT will try to reconnect to RAT1 immediately (if it is currently running at RAT2 or RAT3). 4.4 The information of modem, sim Memmaps information of modem, sim in the table below: ADDRESS (in decimal) ADDRESS (in hex) LENGTH (in byte) TYPE NAME DESCRIPTION UNIT Server 160 A0 20 string modem hl serial R 180 B4 20 string imei identification text for determination of the individual ME R 200 C8 20 string imsi International Mobile Subscriber Identity R 220 DC 20 string iccid SIM Card Identification R 240 F0 16 string modem hl fw ver R 9056 2360 10 string Model identifier R 9066 236A 22 string Active LTE Band R Active LTE Band:Active LTE Band: see which RAT is running, which band.• Number 1 at the beginning of the sequence is NB1.• Number 4 is band 3 (1800 MHz). NOTE:The display of RAT differs from the configuration of Cat-M1, NB1, GPRS as 0, 1, 2; NOT 1, 2, 3. 5. Installation 5.1 Installation location Installed on a wall or in non-metal box. The bracket will be fixed on the wall or material with a planar surface with 2 x M4 screws; ATTENTION:DO NOT install the iConnector 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. 5.2 IO Wiring 5.2.1 Connect Power Supply and Modbus Connect PWR+ and PWR- to 7..48VDC power supply via M12 Male connector Connect A and B to RS485 connection. Use M12 female connection cable to connect to iConnector 5.3 Battery installation Steps for battery installation: Step 1: Using L hex key to unscrew M4 screws at the side of housing Step 2: Carefully pull out the top plastic housing in the vertical direction Step 3:Attach the battery connector of the lithium battery and the circuit board together Step 4: Insert the top plastic housing and locking by L hex key (NOTE: When reinstalling the cover, pay attention to put the PCB edge into the middle slot of the box inside as shown below) 5.4 Insert SIM card Open iConnector cover with hex key and install the SIM card; Please insert the SIM in the direction printed on the label. 6. Example application 7. Troubleshooting No. Phenomena Reason Solutions 1 Data does not go to server, N/A iConnector lost connection with server Check out the iConnector power supply Check the operation of the sim (data, packages, ...) Check the network coverage of the network in the area where iConnector is installed Check physical Sim, Sim tray 2 Data sent to server is held Modbus error = 20 Led modbus off Loss of the modbus connection The configuration of parameter & modbus command is wrong Check for modbus wiring Check the status of the modbus circuit of iConnector and Slaves Check the parameter & modbus command configuration on Cloud 3 The data posted on Globiots is wrong, the phenomenon of value is changed abnormally continuously Configuration parameter & modbus command is wrong Check and correctly configure parameters & modbus commands 4 Led status of iconnector not light Led status 4s flashes once (iConnector is only running on battery) Lost power iConnector Check iConnector power supply 5 Led network does not light Not yet added iConnector to server or the information is wrong Sim has run out of data The device is out of range Sim is broken Check out the information of iConnector add on server Check the operation of the sim (data, packages, ...) Check the network coverage of the network in the area where iConnector is installed Check physical Sim, Sim tray 8. Support contacts Manufacturer Daviteq Technologies IncNo.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 Templogger Pty Ltd Tel: 1800 LOGGER Email: contact@templogger.net GENERAL GUIDE FOR ICONNECTOR STHC This chapter is to provide the general guides for all kind of iConnector with SKU: STHC. It includes the following guides: * Principle of operation of iConnector STHC; * How to Wiring the iConnector * How to Config iConnector via offline cable; * How to Configure Modbus commands for iConnector; * How to Configure Alarms & Event; * How to Trouble-shoot iConnector; ... General Information STHC-MN01-EN-01 JUL-2020 This document is applied for the following products SKU STHC HW Ver. 3.3 FW Ver. 3.5 A. Functions Change Log HW Ver. FW Ver. Release Date Functions Change 3.3 3.5 Aug-2020 B. Support contacts Manufacturer Daviteq Technologies IncNo.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 Templogger Pty Ltd Tel: 1800 LOGGER Email: contact@templogger.net I. Specification of iConnector STHC 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, EthernetIP, Profinet, CClink, Wireless sensor network...It connects to server system via LAN/WAN as Ethernet, WiFi or Cellular. 1.2 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 II. Principle of operation of iConnector STHC 2.1 General operation principles of iConnector 2.1.1 LED meaning 2.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) 2.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 2.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 2.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). 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. 2.1.3 Logged data Up to 20 different log cycles; 320 log parameters maximum for all log cycles. Up to 120 log parameters per log cycle. 2.1.4 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). 2.1.5 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. 2.1.6 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 2.1.7 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 2.1.8 Health data Every 15 seconds send health pack 1 time. 2.1.9 Relay There are 2 relays: Relay control address 1: 0x3100. Relay control address 2: 0x3101. 2.2 iConnector Cellular 2.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 2.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 2.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 2.3 iConnector Ethernet 2.3.1 What is TCP/IP ? 2.3.2 Configure with iConnector Config software Refer to section 5 for more details on how to use Configuration Cable 3.3.2.1 Ethernet tab 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 DHCP → Static IP 3.3.2.2 Modbus-TCP-Server tab 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 2.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. 2.3.4 Run Modbus RTU as normal iConnector (Modbus-TCP enb transparent = 0) 3.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 3.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 2.4 iConnector Wifi 2.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 2.4.2 Configure using the Configuration Cable Refer to III. Offline configuration for iConnector for more details on how to use Configuration Cable Step 1: Open the configuration tool and switch to the Wifi tab; 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. 2.4.3 Modbus-TCP-Server Configuration Please refer to the Modbus-TCP-Server configuration section in section 4.3. III. Offline configuration for iConnector iConnector need to be configured properly so that it is able to connect to Globiots Server successfully; 3.1 Preparation 3.1.1 Configuration Cable iConnector need to be configured initially before operation, by using a configuration cable as below: Item code Description RS485-FM12-USB-1 RS485/USB multi-purpose Configuration cable with connector m12 male, female and flying leads, with Power adapter 12VDC/2.0A Below picture is illustration of this configuration cable. The configuration cable has 04 connectors:* 1st-connector is M12-F connector with 4 pin inside (A, B, PWR & GND): to connect the RS485 port of iConnector;* 2nd-connector is M12-M connector with 4 pin inside (A, B, PWR & GND): to connect to other devices with RS485 port, but its connector is M12-F;* 3rd-connector is USB Type A plug: this is to connect to the USB port of Computer;* 4th-connector is DC Socket 5.5 mm for Powering the converter circuit and iConnector or other device connected to this tool. This DC jack will be plugged by the plug of AC Power adapter. AC power adapter can be 12V/2A or 24VDC/1A;* There is a flying lead with Connector M12 to allow customer connect to other device with RS485 port but no M12 connector, like IO Module (SKU# STHM-).... 3.1.2 Offline Configuration Software: To configure the iConnector, there is a Software run on Windows OS (Window 10 is recommended); Please download the software at link below: https://filerun.daviteq.com/wl/?id=lNjzZbDo7Jwyr1x8DAD3x620tNK5u8lF Any desktop or laptop computer with USB-A port and Windows 10 OS can be used with this Software Unzip the file, it will extract 04 files as below picture: Double-click the application file, named: iconnector_config to run the application. You will see the application as below. There should be the COM port when you plug in the USB plug of configuration tool. If there is no, please:* Install the COM Port driver as below instruction 3.1.3;* After that close and open the software again. 3.1.3 Install the Driver for COM Port: In case your computer has not got the driver, please follow these step to install the driver for Window 10: https://ftdichip.com/wp-content/uploads/2020/08/AN_396-FTDI-Drivers-Installation-Guide-for-Windows-10.pdf After install the driver successfully, please close and open the software again. 3.2 Configuration Steps: Please follow these steps: Step 1: Plug the USB Plug the configuration cable to computer via USB port; Step 2: Powering Power supply 12 or 24VDC for Configuration Cable via DCSocket, by using the AC Adapter. Step 3: Connect to iConnector Plug the connector M12-Female to the RS485 port of iConnector (Right M12-male connector, as shown below picture) The LED "Status" on iConnector must be turn ON, that meant it is powered! Step 4: Select COM Port and configure it If there is no COM Port ==> please install the driver as above section 3.1.3 Select the COM Port associate with the USB port you are connecting with the Configuration tool; Set the BaudRate: 9600, Parity: none; Press button "Connect" to allow the Software connect with iConnector If connect successful, you will see Status shows "connected" as below picture If NOT, Status shows "disconnected" 3.3 Configuration parameters for iConnector * There are many parameters of iConnector to be configured before using.* However, most of the parameters were configured by the manufacturer.* Customer will only need to configure some parameters like: APN, Username, password for Cellular iConnector, or other parameters.* Please refer below sections to configure the parameter you want. 3.3.1 Configure the SIM card information for Cellular iConnector Cellular iConnector use the 2G, 3G or 4G connectivity to connect to IoT Server; It requires the Data SIM Card to be inserted into iConnector; Contact the Network Operator of Sim card to get the following information: APN: Username: Password: Click to the Tab 2G/3G on the Software; 3.3.1.1 How to configure the APN Name? Please follow these steps: Typing the APN in the Setting column, then click the check box "Sync" at that row to allow the data to be written to iConnector. Once written successfully, you will see the same data on the "Value" Column; If the data on Value column is different from the data on Setting column, that meant the data has not been written successfully to iConnector. Please check again: The connection from iConnector and Software is still connected or not? Then click the box "Sync" again. Repeat these steps to configure other parameters: User name and Password. 3.3.1.2 How to check the iConnector was configured successfully and connected to Globiots Server? After configure successfully the SIM card information, the iConnector will connect to Globiots server automatically; The LED Network will be turn ON; Using the provided account of Globiots server, log in to the Globiots system to check the status of iConnector;+ If connected, the icon will be Blue color;+ If not connected, the icon is still Grey color; If waiting for 5-10 minutes, the iConnector is still not connecting to Globiots server, please check the followings:+ SIM card is contract with data plan? + The Network operator support the Frequency bands of iConnector? Please check the frequency band of iConnector in this link: + Make sure information APN, Username and Password is all correct? + Make sure the configuration is all correct with these values? Please check carefully each leter, a space letter at the end can cause the problem! =====END===== IV. Insert SIM Card for Cellular iConnector Steps to insert SIM card: Step 1: Remove the housing 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 Step 2: Insert the SIM Card into the iConnector, Please take note the direction of the SIM Card The Sim card must be MICRO-SIM type When inserting the SIM card please disconnect the power supply to avoid damaging the device ! Step 3: Place back the 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) V. Installation iConnector STHC 5.1 Example application iConnector is used widely in many applications for Smart Factory, Smart Facility/Building, Smart City, Smart Agriculture... Please refer more information at: https://www.daviteq.com/ung-dung2/ 5.2 Installation location Depend on what kind of iConnector, the location of installation will be considered carefully. 5.2.1 if the iConnector has built-in Sub-GHz Wireless Co-ordinator or Wireless Bridge: To maximize the distance of transmission between Sub-GHz wireless sensor and iConnector, the ideal condition is Line-of-sight (LOS) between the Wireless sensor and iConnector. In real life, there may be no LOS condition. However, the Wireless sensor still communicates with iConnector, but the distance will be reduced significantly. The antenna of Sub-GHz Wireless Co-ordinator of Wireless Bridge must be placed above ground as high as possible, not lower than 2m. We recommend the minimum is 4m; It's better to place the antenna outdoor, on top of the roof of building, house, warehouse...; It's not good if the antenna is place indoor but the wireless sensor is outdoor; Only when all the wireless sensors are indoor, then you can place the antenna of wireless co-ordinator indoor, too; 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. 5.2.2 if the iConnector has Cellular connectivity like 2G, 3G or 4G: We highly recommend to install the iConnector outdoor or outside of the cabinet so that it can have strong signal of cellular; Do not put iConnector inside a metallic box as the cellular can not go thru the metal sheets; Incase the iConnector must be place inside a box for better protection, please use the box with plastic materials like ABS, ASA, Polycarbonate, Fiber Glass... 5.2.3 if the iConnector has WiFi connectivity: We highly recommend to install the iConnector at the place has strong coverage of WiFi signal; Do not put iConnector inside a metallic box as the WiFi signal can not go thru the metal sheets; Incase the iConnector must be place inside a box for better protection, please use the box with plastic materials like ABS, ASA, Polycarbonate, Fiber Glass... 5.3 Mounting bracket for installation 5.3.1 iConnector with blue housing: The mounting bracket is made from hard metallic material. Following to these steps as the below picture 5.3.2 iConnector with White housing: There are 02 holes for screwing at the left and right of housing. These holes are covered by the cover. Open the cover, you can access the hole for screwing. Using screw with size 4mm diameter maximum. VI. How to add iConnector STHC to Globiots Server System? VII. Modbus Configuration for iConnector STHC on Globiots VIII. Parameter Configuration for iConnector STHC on Globiots IX. Alarm & Event Configuration for iConnector STHC on Glbiots X. Configuring special functions of iConnector on Globiots XI. Troubleshooting iConnector and Globiots 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 Manual of STHC-ISGWET-WS433-CL-04 | FW8 I.QUICK GUIDE (Ở 1 page riêng trong chapter) 1.1 Introduction 1.1.1 Introduction: có gateway/controller/datalogger/ modbus converter1.1.2 System architecture1.1.3 System components1.1.4 How to setup the system 1.2 Application note 1.3 iConnector communication1.3.1 Slave device communication: wired RS485 modbus RTU, wireless WS4331.3.2 Host communicationCommunication with Globiots platform=> detail in quick test Real time data, logged data, event data, alarm data: limit bao nhiêu parameter, limit log cycle, limit lưu event và alarm N ngày Communication with Modbus TCP/IP device=> detail in quick test Communication with http/https server=> detail in quick testReal time data, logged data, event data, alarm data: limit bao nhiêu parameter, limit log cycle, limit lưu event và alarm N ngày1.4 Default ConfigurationĐưa ra 1 số default về modbus config, server connection: host, port, ...về Daviteq globiots, default wifi: lấy thông tin từ bảng modbus, trình bày dạng bảng (No., Configuration Name, Data type, default value... 1.5 Battery/ Power Supply Trình bày về spec nguồn cấp, wiring nguồn cấp 1.6 What's in the Package? Hình package 1.7 Guide for Quick Test Steps: Add to Globiots (link đến mục 1.10), select memap Standard => Import parameter health & bộ thu của 1 node, add modbus para, add modbus command (for 1 parameter)=> check value on memap tab => Wiring 1 modbus device (nếu dùng thêm modbus device) (optional) , wiring nguồn cấp/dùng adapter & pair 1 cảm biến (optional)=> power up, sych=> check online=> check value on memap tabNote: memmap standard sẽ có thông tin của health, bộ thu node 1, parameter của 1 thiết bị modbus (địa chỉ 2000) và modbus status tại địa chỉ 2004 1.8 Installation and wiring 1.8.1 Installation and wiring for iConnector1.8.2 Installation and wiring for wired slave device18.3 Installation and wiring for wireless sensor18.4 Installation and wiring for host Modbus TCP/IP 1.9 Payload Document and Configuration Tables Link của file iConnector memory map 1.10 How to connect device to Back-end/ Server 1.10.1 How to connect device to Globiots platform1.10.2 How to connect device to http server 1.10.3 How to connect device to Modbus TCP/IP server (only for ...with Ethernet connection) II. MAINTENANCE (Ở 1 page riêng trong chapter) 2.1 Maintenance 2.2 Troubleshooting III. ADVANCE GUIDE (Ở 1 page riêng trong chapter)3.1 Principle of Operation: Đọc modbus=> logged, realtime khi có yêu cầu, alarm , event=> gửi lên Globiots/httpsĐọc modbus=> gửi lên Modbus TCP/IP server 3.2 Configuration3.2.1 Cấu hình online từ GlobiotsCấu hình iConn, parameter, modbus, alarm, event dashboard, report32.2 Cấu hình offlineCấu hình modbus, cấu hình ip, wifi, connection, transparency... dùng phần mềm iConfig fw 8 IV.PRODUCT SPECIFICATIONS(Ở 1 page riêng trong chapter) 4.1 Specifications V. WARRANTY & SUPPORT (Ở 1 page riêng trong chapter) 5.1 Warranty(Ở 1 page riêng trong chapter) 5.2 Support(Ở 1 page riêng trong chapter) I.QUICK GUIDE | STHC-ISGWET-WS433-CL-04 | FW8 II. MAINTENANCE | STHC-ISGWET-WS433-CL-04 | FW8 III. ADVANCE GUIDE | STHC-ISGWET-WS433-CL-04 | FW8 IV. PRODUCT SPECIFICATIONS | STHC-ISGWET-WS433-CL-04 | FW8 V. WARRANTY & SUPPORT | STHC-ISGWET-WS433-CL-04 | FW8 USER GUIDE FOR ICONNECTOR WIFI STHC-ISGWF-WS433-CL-04 DEC-2021 This document is applied for the following products SKU STHC HW Ver. 1.1 FW Ver. w1.5_17101 Item Code STHC-ISGWF-WS433-CL-04 iConnector WIFI, RS485/MODBUSRTU with built-in wireless co-ordinator 1. Functions Change Log HW Ver. FW Ver. Release Date Functions Change 1.1 w1.5_17101 DEC-2021 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. 3. Specification Host Communication 802.11b/g/n, 2.4Ghz, internal Wifi antenna, integrated wireless co-ordinator 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) Power supply 7..48VDC, avg 200mA, peak 1.5A On-board memory & sensors 2MB Flash, PCB temperature sensor Electrical connectors M12, 4-pin, coding A or 9mm Power Plug and USB port Buzzer Internal buzzer Antenna Internal Wifi antenna, standard external antenna 0 dbi, option 3dbi, 6dbi, 9dbi. RF frequency band Free license ISM 433.92Mhz (for others 868, 915, 920Mhz, refer related datasheets) Security Standard AES-128 Data speed Up to 50kbps Operating Temperature/Humidity -20 .. + 60 degC / 95%RH, non-condensing Housing/Protection Aluminum+Polycarbonate. All version is IP67 protection Dimension H130xW90xD40 for Ethernet/WiFi versions Net weight 350 grams Ethernet/WiFi versions 4. Operation principle 4.1 LED meaning 4.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.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.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.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). 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.3 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.4 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.5 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.6 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.7 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.8 Health data Every 15 seconds send health pack 1 time. 5. Configure using the iConfig app on the phone After supplying power the iConnector via M12 connector, only configure using the iConfig app within the first 5 minutes.Use app on android phone then configure the Wifi Name and Password that iConnector Wifi will connect to. Please refer to how to configure using iConfig app with the following link: iConfig Mobile app for Android 6. Connect iConnector to Templogger Pro Server System 6.1 Login Please visit the link to the login page:  Templogger Pro - Login If you do not have an account on the Templogger Pro Server System, please contact the Templogger Pro technical staff for assistance. 6.2 Add iConnector STHC to Templogger Pro Server System To close or open “Organization Chart” panel, you can click on left corner of screen Organization Chart page includes all Node and Device in system: Right click on Node name, menu of Node displays:  • New: Create new Node, Device  • Delete: Delete Node  • Assign to account: Assign Node and sub-Node to account  • Rename: Change name of NodeTo create a new Device:  (1) Select Node  (2) Right click and select “New”  (3) Click “Device” to create a new Device (4) A box appears: • Enter parameters of Device:  • Name: Name of Device (require 12 characters)  •  Serial Number: provided by manufacturer (require 12 characters)  • Click “Generate” button to create Device ID or enter ID directly  • FCC: provided by manufacturer (require 4 characters)  • Click “Save” button to continue. A box appears: Serial Number , FCC :  Please contact the Templogger Pro technical staff for assistance. (5) A box appears after save: Select the same image and save. After save again at tab "Basic information". Confirm the request and enter the account to create a new device. 6.3 Check health a new Device To check health a new Device:  (1) Select Node.  (2) Select Monitoring Tab.  • Health Status: display Connection status between iConnector and server ( Connected/Waiting for connect/Disconnected)  • Config Status: display synchronization status (Synchronized or Unsynchronized) 7. Installation 7.1 Installation location Installed on a wall or in non-metal box. The bracket will be fixed on the wall or material with a planar surface with 2 x M4 screws; ATTENTION:DO NOT install the iConnector 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. 7.2 IO Wiring 7.2.1 Connect Power Supply and Modbus Connect PWR+ and PWR- to 7..48VDC power supply via M12 Male connector Connect A and B to RS485 connection. Use M12 female connection cable to connect to iConnector 8. Example application 9. Troubleshooting No. Phenomena Reason Solutions 1 Data does not go to server, N/A iConnector lost connection with server Check out the iConnector power supply Check the network coverage of the network in the area where iConnector is installed Check wifi configure, iP, gateway, internet. 2 Data sent to server is held Modbus error = 20 Led modbus off Loss of the modbus connection The configuration of parameter & modbus command is wrong Check for modbus wiring Check the status of the modbus circuit of iConnector and Slaves Check the parameter & modbus command configuration on Cloud 3 The data posted on Globiots is wrong, the phenomenon of value is changed abnormally continuously Configuration parameter & modbus command is wrong Check and correctly configure parameters & modbus commands 4 Led status of iconnector not light Led status 4s flashes once (iConnector is only running on battery) Lost power iConnector Check iConnector power supply 5 Led network does not light Not yet added iConnector to server or the information is wrong Sim has run out of data The device is out of range Sim is broken Check out the information of iConnector add on server Check the network coverage of the network in the area where iConnector is installed 10. Support contacts Manufacturer Daviteq Technologies IncNo.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 Templogger Pty Ltd Tel: 1800 LOGGER Email: contact@templogger.net xxx Manual of STHC-ISGWET-WS433-CL-04 | FW8 Instructions to connect Modbus Slave device to iConnector and show on Globiots and HMI I. Configuration for iConnector 1.1 Offline configuration process Step 1: Preparation Prepare some required devices as below01x A window PC01x USB-RS485 Configuration Cable01x  Power adapter 12-24VDC Download the Configuration software in the link Step 2: Hardware connection Connect the USB-A to the PC Connect M12 female of the cable to the iConnector Power the iConnector on by connecting DC jack from Power Adapter The above steps must be performed in order Step 3: Configuration the iConnector via iConfig software Open the iConfig software, then choose Correct Port, BaudRate and Parity. Port is based on the PCBaudRate is 9600Parity is NONE Click CONNECT button on the software (1) There are 11 configuration tabs on the top banner. Click a tab name to navigate to the corresponding sheet. (2) The first column displays the parameter names of the iConnector. (3) The second column shows the current values of the corresponding parameters (4) The third column is where users can input new configuration values. (5) After entering the new configuration in the third column, users must tick the corresponding checkbox to apply it. The tick will disappear once the new configuration is successfully written to the iConnector. After that, the updated value will appear in the second column. 1.2 Get iConnector information  for Globiots configurations Click tab Device, get basic information of the iConnector to register it into Daviteq Platform including Serial number & FCC. Note out this information for later iConnector registration  on Globiots 1.3 Configuration network parameters for iConnector * There are many parameters of iConnector to be configured before using.* However, most of the parameters were configured by the manufacturer. 1.3.1 Configure Globiots server for iConnector Click tab UPD_SERVER, input the UDP_SERVER_HOST in the Value defined by user column, then click the check box "Sync" at that row to allow the data to be written to iConnector. Once written successfully, you will see the same data on the "Value" Column. Repeat these steps to configure other parameters: UPD_SERVER_PORT, TIME_ZONE configurations. Above Globiots server configurations are usually pre-configured by manufacturer before delivery 1.3.2 Configure the network information for Ethernet iConnector Click tab Ethernet, input the ETHERNET_STATIC_IP in the Value defined by user column, then click the check box "Sync" at that row to allow the data to be written to iConnector. Once written successfully, you will see the same data on the "Value" Column. Repeat this step for ETHERNET_GATEWAY, ETHERNET_DNS_SERVER, ETHERNET_DHCP_ENABLE Then click tab WIFI and configure MAIN_NETWORK =2 Name Description ETHERNET_STATIC_IP Ethernet Static IP configuration for iConnector. Example: 192.168.1.30 ETHERNET_GATEWAY Configure gateway ETHERNET_DNS_SERVER Configure DNS Server ETHERNET_DHCP_ENABLE 0 (Off) / 1 (On) If DHCP = 0, it's mean Not using DHCP → Static IP Above configurations are applied for Ethernet iConnector 1.3.3 Configure the network information for WIFI iConnector Click tab WIFI, input the WIFI_NAME in the Value defined by user column, then click the check box "Sync" at that row to allow the data to be written to iConnector. Once written successfully, you will see the same data on the "Value" Column. Repeat this step for WIFI_PASSWORD, WIFI_STATIC_IP, WIFI_GATEWAY, WIFI_DNS_SERVER, WIFI_DHCP_CENABLE Configure MAIN_NETWORK = 1 Name Description WIFI_NAME WIFI name network WIFI_PASSWORD Password of WIFI network WIFI_STATIC_IP WIFI Static IP configuration for iConnector. Example: 192.168.1.30 WIFI_GATEWAY Configure gateway WIFI_DNS_SERVER Configure DNS Server WIFI_DHCP_ENABLE 0 (Off) / 1 (On) If DHCP = 0, it's mean Not using DHCP → Static IP Repeat these steps to configure other parameters: APN_USERNAME and APN_PASSWORD configurations. Above configurations are applied for WIFI iConnector 1.4 Configuration Modbus communication parameters for iConnector Click Modbus tab, configure Modbus communication parameters for RS485 port ( baud rate, parity, stop bit, time out, poll cycle) to match up with Modbus slave device 1.5 Register iConnector on Globiots Access to Vizuo Globiots via the link https://vizuo.globiots.com and login to the system with the username and password supplied Daviteq. Register the iConnector into Globiots RIGHT-CLICK on the corresponding site in the Organization Chart => New=>Device 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.2 Device ID Click Generate button in the software FCC FCC of iConnector*Taken from step 1.2 Memmap Choose 4.1.4-9600-RD1 Logging send frequency Choose 5 minutes Health send frequency Choose 5 minutes 1.6 Check iConnector connection on Globiots After configure successfully (step 1.1-1.4), the iConnector will connect to Globiots server automatically; The LED Network on iConnector will be 1Hz flashing Using the provided account of Globiots server, log in to the Globiots system to check the status of iConnector;+ If connected, the iConnector icon on Organization Chart section will be Blue color;+ If not connected, the icon is still Grey color; The iConnector must be powered by configuration tool during this process II. iConnector Installation and Wiring 2.1 Installation location Depend on what kind of iConnector, the location of installation will be considered carefully. 2.1.1 if the iConnector has built-in Sub-GHz Wireless Co-ordinator or Wireless Bridge: To maximize the distance of transmission between Sub-GHz wireless sensor and iConnector, the ideal condition is Line-of-sight (LOS) between the Wireless sensor and iConnector. In real life, there may be no LOS condition. However, the Wireless sensor still communicates with iConnector, but the distance will be reduced significantly. The antenna of Sub-GHz Wireless Co-ordinator of Wireless Bridge must be placed above ground as high as possible, not lower than 2m. We recommend the minimum is 4m; It's better to place the antenna outdoor, on top of the roof of building, house, warehouse...; It's not good if the antenna is place indoor but the wireless sensor is outdoor; Only when all the wireless sensors are indoor, then you can place the antenna of wireless co-ordinator indoor, too; 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. 2.1.2 if the iConnector has Cellular connectivity like 2G, 3G or 4G: We highly recommend to install the iConnector outdoor or outside of the cabinet so that it can have strong signal of cellular; Do not put iConnector inside a metallic box as the cellular can not go thru the metal sheets; Incase the iConnector must be place inside a box for better protection, please use the box with plastic materials like ABS, ASA, Polycarbonate, Fiber Glass... 2.1.3 if the iConnector has WiFi connectivity: We highly recommend to install the iConnector at the place has strong coverage of WiFi signal; Do not put iConnector inside a metallic box as the WiFi signal can not go thru the metal sheets; Incase the iConnector must be place inside a box for better protection, please use the box with plastic materials like ABS, ASA, Polycarbonate, Fiber Glass... 2.1.4 if the iConnector has Ethernet connectivity: We highly recommend to install the iConnector at the place for easy access and check LED status 2.2 Mounting bracket for installation 2.2.1 Cellular iConnector: The mounting bracket is made from hard metallic material. Following to these steps as the below picture 2.2.2 WIFI and Ethernet iConnector: There are 02 holes for screwing at the left and right of housing. These holes are covered by the cover. Open the cover, you can access the hole for screwing. Using screw with size 4mm diameter maximum. 2.3 Wiring 2.3.1 Wiring for wired slave device Connect the modbus RTU slaves to the iConnector via RS485 protocol.  Pin 2 is RS485+ (A), Pin 4 is RS485- (B) III. Globiots Configuration to read Slave Device Modbus Parameter 3.1 Configure Modbus Parameter on Globiots Login Globiots with provided user and password Click on Device, right-click, select ParameterIn List Parameters Page  • “Import Parameter”: click to Import Parameters from excel file. Excel file must have default structure.  • “Export Parameter”: click to export parameter to excel file.  • “Add parameter”: click to add a new parameter.   o Name: parameter name    o Type: Real Parameter or Virtual parameter       Real Parameter: Parameter from iConnector       Virtual Parameter: Parameter only in Server. Virtual parameter is create from formula of one or multi real parameter       If type is Virtual parameter, formula in Expression should be added        Mathematical Operators Operator Description + Additive operator / Unary plus - Subtraction operator / Unary minus * Multiplication operator, can be omitted in front of an open bracket / Division operator % Remainder operator (Modulo) ^ Power operator        Boolean Operators Operator Description = Equals == Equals != Not equals <> Not equals < Less than <= Less than or equal to > Greater than >= Greater than or equal to && Boolean and || Boolean or        Supported Functions Function* Description NOT(expression) Boolean negation, 1 (means true) if the expression is not zero IF(condition,value_if_true,value_if_false) Returns one value if the condition evaluates to true or the other if it evaluates to false RANDOM() Produces a random number between 0 and 1 MIN(e1,e2, ...) Returns the smallest of the given expressions MAX(e1,e2, ...) Returns the biggest of the given expressions ABS(expression) Returns the absolute (non-negative) value of the expression ROUND(expression,precision) Rounds a value to a certain number of digits, uses the current rounding mode FLOOR(expression) Rounds the value down to the nearest integer CEILING(expression) Rounds the value up to the nearest integer LOG(expression) Returns the natural logarithm (base e) of an expression LOG10(expression) Returns the common logarithm (base 10) of an expression SQRT(expression) Returns the square root of an expression SIN(expression) Returns the trigonometric sine of an angle (in degrees) COS(expression) Returns the trigonometric cosine of an angle (in degrees) TAN(expression) Returns the trigonometric tangens of an angle (in degrees) COT(expression) Returns the trigonometric cotangens of an angle (in degrees) ASIN(expression) Returns the angle of asin (in degrees) ACOS(expression) Returns the angle of acos (in degrees) ATAN(expression) Returns the angle of atan (in degrees) ACOT(expression) Returns the angle of acot (in degrees) ATAN2(y,x) Returns the angle of atan2 (in degrees) SINH(expression) Returns the hyperbolic sine of a value COSH(expression) Returns the hyperbolic cosine of a value TANH(expression) Returns the hyperbolic tangens of a value COTH(expression) Returns the hyperbolic cotangens of a value SEC(expression) Returns the secant (in degrees) CSC(expression) Returns the cosecant (in degrees) SECH(expression) Returns the hyperbolic secant (in degrees) CSCH(expression) Returns the hyperbolic cosecant (in degrees) ASINH(expression) Returns the angle of hyperbolic sine (in degrees) ACOSH(expression) Returns the angle of hyperbolic cosine (in degrees) ATANH(expression) Returns the angle of hyperbolic tangens of a value RAD(expression) Converts an angle measured in degrees to an approximately equivalent angle measured in radians DEG(expression) Converts an angle measured in radians to an approximately equivalent angle measured in degrees        Supported Constants Constant Description e The value of e, exact to 70 digits PI The value of PI, exact to 100 digits TRUE The value one FALSE The value zero NULL The null value         Note: Virtual parameter can't use for event.          Example 1:            Value of Virtual Parameter have address at 2012 is calculated as follow [2012] = [2000] + [2002. ]In which address 2000 and 2002 are two real parameters          Example 2:           IF [2000]>10 then [2005]=1            IF [2000]<=10 then [2005]=2            Example 3:           IF [2000]=1 And [2005]=2 then [2010]=5            IF [2000]=!1 And [2005]=!2 then [2010]=[2007]+10        Example 4:           IF [2000]>10  then [200A]=1            IF [2000]<10 And [2010]=1 then [200A]=5            IF [2000]<10 And [2010]=!1 then [200A]=10   o Unit: Unit of parameter    o Logged: Tick to permit saving value of parameter into database    o Logging Priority: enter any value    o Logging Frequency: select frequency to log data from meter/sensor/device/instrument into iConnector memory    o Time to live: select how long data will be stored in database    o Data Type: Type of parameter    o Data Length: Length of data type, byte unit, display automatically with data type. If data type is String, data length should be input    o Address: Address in iConnector memory map to store value of parameter     o Decimal Places: number of decimal after the comma.  • Save: click to finish  • “Delete All”: click to delete selected parameters  • Edit: click to edit this parameter  • Delete: delete parameter Note: After Configure Parameter, you must synchronize (refer to 5.11 Synchronize Device for more details) 3.2 Configure Modbus Command - Select Device, right-click, select Modbus Command- Modbus Configuration page displays as below:  • MODBUS CONFIG LIST (1)    o Button “Edit”: click to edit Modbus Command. Modbus Command will display in (2) to edit    o Button “Delete”: click to delete Modbus Command.    o Button “Import”: click to import Modbus Command list from excel file    o Button “Export”: click to export Modbus Command list to excel file    o Button “Delete All”: click to delete all Modbus Command  • ADD MODBUS CONFIG (2)    o Response Location: Address of parameter in iConnector    o Slave ID: Modbus ID of meter/sensor/device/instrument which connect to iConnector through RS485 port    o Function Code: Function Code of Modbus Command. Function Code consist of read function and write function. In user manual of meter/sensor/device/instrument should mention supported function code.    o Parameter 01: Starting address of parameter in memory map of meter/sensor/device/instrument    o Parameter 02: Number of registers of parameter in memory map of meter/sensor/device/instrument    o Button “Add”: Click to add new Modbus Command    o Button “Update”: After click “Edit” button in (1), “update” will display. After editing Modbus command and click “Update” to save change.      Note:        Response Location in iConnector for read Modbus data :0x2000 -> 0x21FF       Response Location in iConnector for write Modbus data: 0x3000 -> 0x307F       After configuring, Modbus Command should be synchronized to iConnector (refer to 5.11 Synchronize Device for more details)Example:Configure modbus command for reading parameter Voltage, data type: float, from address 0000 on power meter (ID=32) and store at address 2000 (hex) on iConnector, using function 04 of modbus command. The configuration as follow: Response Location = 2000 Slave address = ID=32 (decimal) =20 (Hexa)Parameter 01 = Start Address = 0000Parameter 02 = Number of register of parameter. Data type = float (4 bytes) = 02 register 3.3 Synchronize Modbus Parameter configurations and Modbus Command configurations to iConnector Right click Device name, select Sync, and tick all type of configuration to synchronize to iConnector, click Sync, enter password to confirm permissionAfter successful synchronization, Text Synchronized should appear on 4 line of dialog box. If iConnector disconnected, message should appear to inform that synchronization will implement once iConnector connect to server. IV - Globiots configuration for dashboard and report 4.1 Dashboard 4.1.1 Dashboard Description Dashboard views input text, current value and value from database. Each Dashboard is organized in one tab. When value is from database, dashboard will update the value after specific time. Dashboard consists of containers which contain widgets inside. 4.1.2 View Dashboard - In Home screen, select menu Management → select sub-menu Dashboard to display current value of parameters.- Screen of status “Dashboard”:- Screen of status “Stop” of Dashboard:  • (1): Display list of Dashboard tabs which user are assigned to view  • Button “Run”: click to run Dashboard.  • Button “Stop”: click to stop selected Dashboard.  • Button “Delete”: click to delete Dashboard  • Button “Edit”: click to edit Dashboard  • Button “Add Container”: click to add new Container in Dashboard  • Button “Export”: click to export Dashboard to Excel File  • Button “Import”: Click to import Dashboard to Excel File 4.1.3 Create new Dashboard - In Dashboard screen, click symbol “+” to create new tab- New window display  • Name: Name of new Dashboard tab  • Stop realtime after: Running time of Dashboard to get realtime data from iConnector. After this period of time, Dashboard will stop to get realtime data from iConnector. Click button “Run” on top right corner to continue to get realtime data  • Push Interval: Frequency to get realtime data from iConnector     Click Save to complete creating new Dashboard 4.1.4 Create New Container - In Dashboard tab, click Add Container to add new Container  • Title: Name of container  • Format: Font size, Style, Text color, Text align, Background.  • Poll Interval: Frequency to get logged data from database to view on Dashboard  • Layout: Select layout of container. There are 07 layouts select        Click Save to complete creating Container 4.1.5 Configure a Container (1): Edit Container(2): Delete container.Click SETTING icon to Edit Container. Following screen will appear- Click Add Widget to add new widgetNote: Stop Dashboard before configure Container/Widget 4.1.6 Widget 4.1.6.1 Widget Description Widget is a basic element of Dashboard to view constant, value of parameter. Currently, Vizuo has below widgets After select widget click Add to add new widget to Container 4.1.6.2 Widget Table - Paging: Tick to view table more than one page- Border: Select type of border: None, Border and Inside- New Column: Click to add new column- New Row: Click to add new row  • : Move column  • : Close/Delete column or row- Configure Row- After clicking SETTING icon, configuration screen for new row will appearChoose Data type: Constant (input text), Data from Database (Device Name, Parameter Name, Unit of Parameter, Last value of parameter in Database, time stamp of last value), Data from device (Realtime Data or Current Data). Realtime data is data push from iConnector and Current Data is data pull from iConnectorUp/down icon: Tick to add up/down icon. Up icon appears when last value is less than current value whereas down icon appears when last value is greater than current value. These icons are available when realtime data is displayed in cellMapping: tick Mapping and list out value and mapped text, then click  + icon to add mapping value. Mapping should be used to view meaningful text instead of value 4.1.6.3 Widget Line Chart Click SETTING icon to configure widget Line Chart, the following screen appear  • Title: Line Chart name  • Style: Format of Title  • YAxis: Fixed or Auto. If choose Fixed, enter min & max value. If select Auto, software will specify Max of Y axis based on value of displayed parameter.  • Type: Data type of parameter to view (Data from device or from database)Type Device: Realtime data and display Max point value on line chartType Database: Logged data from database, time period include: Today, Yesterday, Last 3 days or Custom (From…To)  • Line configuration: Select displayed parameter and displayed label (input text, parameter name or device name)Click Add button to add parameter to line chart. A line chart could view some parameters 4.1.6.4 Linear Gauge Click SETTING icon to configure widget Line Gauge, the following screen appear  • Title: Name  • Style: Format of title  • Direction: Vertical or Horizontal Linear Gauge  • Min, Max: Range of Gauge  • Range Color: Auto or CustomAuto: Color of Gauge changes according to value of parameterCustom: Configure specific color to specific range of value of parameter  • Data: Select type of display parameter (last logged data from Database or current value/realtime value from Device  • Device/Parameter: Select displayed parameter  • Write: Tick to enable to write value to parameter. Writing value to parameter by holding and drag on body of Linear GaugeClick Save Changes to complete configuration 4.1.6.5 Solid Gauge Click SETTING icon to configure widget Solid Gauge, the following screen appear  • Title: Name  • Style: Format of title  • Min, Max: Range of Gauge  • Range Color: Auto or CustomAuto: Color of Gauge changes according to value of parameterCustom: Configure specific color to specific range of value of parameter  • Data: Select type of display parameter (last logged data from Database or current value/realtime value from Device  • Device/Parameter: Select displayed parameterClick Save Changes to complete configuration 4.1.6.6 Circular Chart Click SETTING icon to configure widget Solid Gauge, the following screen appear  • Title: Name  • Style: Format of title  • Min, Max: Range of Chart  • Range Color: Auto or Custom  • Auto: Color of Chart changes according to value of parameter  • Custom: Configure specific color to specific range of value of parameter  • Data: Select type of display parameter (last logged data from Database or current value/realtime value from Device)  • Device/Parameter: Select displayed parameter  • Write: Tick to enable to write value to parameter. Writing value to parameter by holding and drag on body of Circular ChartClick Save Changes to complete configuration 4.1.6.7 Column Chart Click SETTING icon to configure widget Solid Gauge, the following screen appears  • Title: Column Chart name  • Style: Format of Title  • Type: Data type of parameter to view (Data from device or from database)  • Type Device: Realtime data   • Type Database: Logged data from database, last value or value series in time period include: Today, Yesterday, Last 3 days or Custom (From…To)  • Column configuration: Select displayed parameter and displayed label (input text, parameter name or device name)Click Add button to add parameter to column chart. A column chart could view some parameters 4.1.6.8 Control Panel Click SETTING icon to configure widget Control Panel, the following screen appears  • Tittle: Name of Control Panel  • Style: Format for tittle  • Column: Number of column of Control Panel  • Row: Number of row of Control Panel  • Click Add button to add new symbolsChoose one symbol and click Add• Configure Simple ButtonAfter adding Simple Button, following screen appear:  • Tittle: Name of Button  • Style: Format of Tittle/Label  • Label: Label on Button  • Parameter: Select written parameter. This parameter should have address in range 3000-307F  • Value: Value to write to parameter. If this value is blank, when the button is clicked the user should enter the value.Click Add to add button. User could add some buttons in one widget  • Configure Advanced ButtonAfter adding Advanced Button, following screen appear:  • Tittle: Name of Button  • Style: Format of Tittle/Label  • Label: Label on Button  • Parameter for reading: Select reading parameter.   • Operator: Logical Operator of Reading parameter and mask  • Mask: Mask to calculate written value. Mask format is binary or Hexa  • Parameter for reading: Select written parameter. This parameter should have address in range 3000-307F. Written value is the result of reading value and mask with logical operatorClick Add to add button. User could add some buttons in one widget  • Configure LedLed will change its color when parameter changes value.After adding Advanced Button, following screen appear  • Tittle: Tittle of LED  • Style: Format of LED tittle  • Parameter: Select Parameter to display  • Label: Label for LED  • Mapping Table: Define list of displayed label and color according to value of parameter  • Click Add to add LED 4.1.6.9 Map Map shows location of iConnector (longitude and latitude) on mapClick to configure widget Map:  • Tittle: Name of Map  • Style: Format of Tittle  • Device List: iConnector list to display location (longitude and latitude)  • Device: Select iConnector name  • Location: Configure longitude and latitude parameter. Location are static or dynamicIf location is static, user enter value of longitude and latitudeIf location is dynamic, configure longitude and latitude parameter 4.1.6.10 EMS Report EMS Report views report for energy consumption during period of time Click SETTING icon to configure widget EMS report, the following screen appears:  • Tittle: Report title  • Style: Format of tittle  • Report type: Daily, Weekly, Monthly  • Data range: Today, yesterday, last month, this month, last week, this week  • Column Configuration: Configure displayed value of parameter and displayed name of parameterClick Add to add parameter for report 4.1.6.11 Pie Chart Pie Chart compares values between some parameters. Click to configure widget EMS report, the following screen appears:  • Tittle: Tittle of pie chart  • Style: Format of tittle  • Type: Data type, realtime data or current value of device or last value in database  • Configuration: Configure displayed value and displayed name of parameter 4.2 Report 4.2.1 Create a new report - To create a new report:  • In menu Management, select Report  • In Report page select “+ ” to create a new tab Enter full information    o Name: Name of Report tab    o Report Type: EMS (for energy), CNC (for CNC machine), Historical Trending (for parameter trend)    o Parameter Configuration:       Name: Name of parameter which display in report. Name might input text or name of parameter.       Device: select Device        Parameter: select parameter of device which you want display       Click “Add” to add parameter. A report might have some parameter    o After complete adding parameter, click “save” to finish 4.2.2 Configure Report - In Report page, select Report name which you want configure  • Click “Delete” to delete report  • Click “Edit” to edit report       To edit available parameter, click SETTING icon in Action column, edit parameter, click Update        To delete parameter, click X icon in Action       To Add new parameter: enter full information and click “Add” 4.2.3 View report Select Time in “From … To …” and click “Show” to view data of parameters on report tab Click on name of parameter (below report) to temporarily ON/OFF parameter on report 4.2.4 Export report After click button Show to view report, click three line icon on top right corner of screen, select Export to Excel or Export to pdf or Export to csv       Click Export to Excel, select version of Excel (2003 or 2007), click Export. The exported file will be store on your PC       Click Export to csv, select version Date Format in csv file, click OK. The exported file will be store on your PC       Click Export to pdf, the exported file will be store on your PCV. Globiots configuration for HMI slave 5.1 Modbus Slave HMI operation HMI will be a Modbus slave to connect to iConnector via RS485 Modbus RTU Every 8 seconds, iConnector use schedule event to write values from other Modbus slaves to HMI HMI will be pre-coded to view these values on HMI screen 5.2 iConnector event configuration After logging in Globiots, to configure Event: right click Device name and select Event. “The List Of Event” page displays as below: • Import Event: Import event from excel file  • Export Event: Export event to excel file  • Add Event: click to add a new event    o Event ID: from 1 to 127 (event ID is only)    o Event name: name of event    o Comment: explain for event    o Priority: Any value     o On Delay: Delay time (second) when condition is true    o Off Delay: Delay time (second) when condition is false    o Logical Operator (AND/OR): Logical Operator for conditions of event    o Parameter: select parameter sent to server when event occur. Only display Real Parameter    o Click “Save” to finish  • Edit: Click to edit event  • Delete: Click to delete event  • Action: Click to configure action for event. An event might have some actions. The List of Actions page displays:     o Add Action: click to add a new action       Action Name: Name of Action       Action Type: Select type of Action. There are 04 type of available action          1. Type 1: 01- Parameter vs constant: Action to assign constant to parameter if condition is true          2. Type 2: 02-parameter vs parameter: Action to assign constant to parameter if condition is true and false          3. Type 3: Action to assign value of source parameter to value of destination parameter if condition is true          4. Type 4: Action to assign value of source parameter to value of destination parameter if condition is true and false       Repeat: tick to implement action once condition is still true. If Repeat: is not ticked, the action only is implemented when condition from FALSE to TRUE.       Value true: constant assigned to parameter when condition is true       Value false: constant assigned to parameter when condition is false       Write Parameter: Destination parameter which is assigned value       Read Parameter: Source parameter        True Parameter: Source parameter if condition is true       False Parameter: Source parameter if condition is false       Save: click “save” to finish    o Edit: click to edit action of event    o Delete: click to delete actionNote: Written parameter in action must have address in range 3000-307F  • Condition: click to configure condition of event. An event might have one or multi conditions. Value of total condition is formed from logical operator of multi conditions    o Add Condition: click to add new condition       Condition Name: Name of condition       Condition Type: Type of condition. There are 3 types of condition        + Type 1: 01- Parameter vs constant: Compare value of parameter to constant        + Type 2: 02-parameter vs parameter: Compare value of parameter to value of another parameter        + Type 3: 03- Parameter (bit) vs constant: Compare value of bit complex of parameter to constant       Condition: Compare value of a parameter to constant or value of a parameter to value of another parameter. Compare Operators are less than, less than or equal to, equal to, not equal, greater than, greater than or equal to       Click “Save” to finish    o Edit: click to edit condition of event    o Delete: click to delete a condition of event       Note:        Each Event have maximum 8 conditions       After configure Event, you must synchronized (refer to 5.11 Synchronize Device for more details)Example: Configure Event to create parameter Power Status:Power Status =1 when iConnector Power Supply > 8 VDC and Main Meter Error=0 in more than 2s.Power Status=0 when iConnector Power Supply <=8 and Main Meter Error=0 in more than 3 s. When event occur, event will be sent to serverConfiguration for this event, condition and action as follow: For schedule written to HMI slave device every 8 second, the event configuration as below: Condition: Condition type: Use condition type 3 (Parameter (bit) vs constant: Compare value of bit complex of parameter to constant), bit 3 Condition parameter: iConnector second parameter will be use Action: Action type: Use action type 3: Action to assign value of source parameter to value of destination parameter if condition is true Source parameter: Parameters from slave devices except HMI slave device Destination parameter: Parameter to HMI slave device