Teracom TCG140-4 User Manual

Lte universal io module
Hide thumbs Also See for TCG140-4:

Advertisement

Quick Links

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the TCG140-4 and is the answer not in the manual?

Questions and answers

Summary of Contents for Teracom TCG140-4

  • Page 2: Short Description

    1. Short description TCG140-4 is a 4G LTE Cat.1 universal I/O module. It supports also 3G and 2G wireless communication and provides data connectivity on LTE-FDD, DC-HSDPA, HSPA+, HSDPA, HSUPA, WCDMA, EDGE, and GPRS networks. The device has 2 digital inputs, 4 analog inputs, digital interfaces for external sensors, and 4 relays.
  • Page 3: Specifications

    4. Specifications • Physical characteristics Dimensions: 158 x 119 x 34 mm Weight: 470 g Mounting: wall and DIN rail • Environmental limits Operating temperature: -20 to 55°C Operating temperature for USB setup: 0 to 40°C Storage temperature: -25 to 60°C Ambient Relative Humidity: 5 to 85% (non-condensing) •...
  • Page 4: Installation

    Attention! Before installing the SIM card in the card slot, please ensure that the PIN code is disabled. 5.1. Mounting TCG140-4 should be mounted in a clean and dry location on a non-flammable surface. Ventilation is recommended for installations where the ambient air temperature is expected to be high.
  • Page 5 • Apply power. It is recommended to test and configure TCG140-4 without any controlled device. Make sure that wires are properly attached to the terminals and that the terminals are tightened. Not proper wiring and configuration can cause permanent damage to the module or the equipment to which it is connected or both.
  • Page 6: Power Supply Connection

    Brown 5.2.1. Power supply connection TCG140-4 is designed to be supplied by adapter SYS1308-2412-W2E or similar, intended for use in the conditions of overvoltage category II. The power supply equipment shall be resistant to short circuits and overload in a secondary circuit.
  • Page 7 (industrial) environments. The maximum number of sensors (1-Wire or RS-485) connected to TCG140-4 is eight. MODBUS RTU protocol specifies that the address of the device should be between 1 and 247.
  • Page 8: Digital Inputs Connection

    - door contact switch, push-button, PIR detector, etc. The following picture illustrates how an alarm button can be connected to a digital input of TCG140-4. One side of the contact is connected to “Digital In” while the other side is connected to the “GND” terminal.
  • Page 9: Led Indicators

    The maximum cable length for an analog input should be up to 30 meters. 5.2.6. Relays connection The relay contacts are internally connected directly to the terminal connectors. Attention! There isn’t any internal overcurrent protection on the relays’ contact lines. For all relays normally open, normally closed and common contacts are available.
  • Page 10 The following states are displayed: • Module initialization – after power-on SIG and STA turn ON for a second, after this turn OFF for another second. • Searching for a network – after initialization, SIG is OFF, STA flashes (flash period of 200ms) •...
  • Page 11 – permanent hardware error. 7. Initial setup via USB The initial setup of TCG140-4 is done with a computer running Windows 7 or a newer Microsoft Windows operating system. After power-up, the module should be connected to the computer with a USB cable.
  • Page 12: Monitoring Page

    The only file stored on the mass storage is a tool called “TConfig”. This tool enables communication between the TCG140-4 and PC. After starting the TConfig tool, the following program will appear: Pressing the “Start” button will start the browser and display the Monitoring page of your TCG140-4. 7.1. Monitoring page The monitoring page displays the current inputs/outputs status of TCG140-4.
  • Page 13 There are two sensors sub-sections on the page - оne for 1-Wire sensors and another one for MODBUS RTU sensors. TCG140-4 supports up to eight sensors. They can be connected to both interfaces in a random ratio, settable in section “Sensors ratio setup” on the Setup->Sensors page. By default, the number of MODBUS RTU sensors is 4.
  • Page 14 7.1.3. Analog inputs section Analog inputs can be used for monitoring DC voltage sources – analog sensors, batteries, power supplies, solar panels, etc. Analog inputs 3 and 4 can be also used for monitoring of 0-20mA current loop sensors/transmitters. The mode can be changed on the “Setup-> Input/Output” section. Analog inputs are sampled faster, but the new actual value is changed in 0.5 seconds.
  • Page 15 . If all sensors are locked, removing one “in the middle” will not position change the positions of other sensors after reset. This option is very useful when TCG140-4 is used as a part of а monitoring and control system managed by HTTP API commands.
  • Page 16: Communication Setup

    All changes should be saved. If the settings are OK in the columns “Raw value” the right data will be shown. TCG140-4 supports MODBUS RTU sensors with response time-out between 10 and 500ms. The default response time-out for a new sensor is 100ms. It is recommended to use the minimum response time guaranteed by the sensor’s manufacturer.
  • Page 17 7.2.2.5.2. Sensor communication register setup This part of the tool is used to check and change the status of the communication registers of the sensor. 7.2.2.5.3. Sensor register check This part of the tool is used for general sensor register check. TCG140-4_R1.0 –...
  • Page 18: Digital Inputs

    7.2.3. Input/Output 7.2.3.1. Sensors For every sensor, a description, up to 15 symbols can be set. These descriptions will appear in the monitoring page, conditions page, XML/JSON data, SMS, and e-mail alerts. For some sensors, fields “Unit”, “Multiplier” and “Offset” are available to convert the raw values into meaningful units.
  • Page 19 For every analog input, a description, up to 15 symbols can be set. These descriptions will appear in the monitoring page, conditions page, XML/JSON data, SMS, and e-mail alerts. For every analog input, fields “Unit”, “Multiplier” and “Offset” are available to convert the raw voltage/current into meaningful engineering units.
  • Page 20: Relay Outputs

    7.2.3.4. Relay outputs For every relay, a description, up to 15 characters can be set. These descriptions will appear in the monitoring page, XML/JSON data, SMS and e-mail alerts. The pulse duration can be different for every relay. The resolution is 0.1 second, the maximum pulse value is 3600 seconds.
  • Page 21 7.2.4.1. Sensors and analog inputs For every sensor two types of fields are presented – one for the trigger conditions (“Min”, “Max”, and “Hys.”) and another one for the wanted action. “Min” and “Max” indicate the border of the working range for the monitored parameter. The “Max”...
  • Page 22 Example: TCG140-4, TST100, and an appropriate heater are used to control the room temperature. The wanted minimum temperature is 19°C. The initial temperature is 17°C. TST100 is assigned on the first position for 1-Wire sensors. For Relay1 local activation from Sensor1 is set.
  • Page 23 The “Max” value is set far enough from the wanted temperature to avoid trigger/alert conditions around it. For every sensor or analog input, there are 3 independent ways of alert when there is an alarm condition – email, SMS, and post (HTTP Post with XML/JSON file). Each alarm notification method is activated by a checkbox.
  • Page 24: System Status

    In the time when the input is in an alarm state, on the „Monitoring page“, the appropriate input will be colored in red. There are two delays - low-to-high and high-to-low for digital input change. These delays are added to the standard delay of 30ms. They have 0.1-second resolution and by default are zero.
  • Page 25: General Setup

    7.2.5.2. Data connection setup This setting can be different for each mobile operator. By default, APN (Access Point Name) is “internet”. Some mobile operators may require also a username and password. The network determines the mobile service type – 2G, 3G, or 4G LTE. By default, it is AUTO – the highest possible generation service will be used in the current position.
  • Page 26: Device Restart

    7.2.5.5. Device restart In this section, there are buttons for device restart and reset to factory default settings. 7.2.6. NTP Internal RTC (real-time clock) of the module can be set either manually or automatically. For automatic clock synchronization, the module supports NTP (Network Time Protocol) and all necessary parameters for automatic synchronization are available in this section.
  • Page 27: Smtp Setup

    The only supported method for encrypted connection from most of the public email servers is TLS. TCG140-4 supports TLS 1.0, TLS 1.1, and TLS 1.2 with a lot of cipher suites. This ensures successful operation with almost all public servers.
  • Page 28 7.3.1.3. E-mail details The subject, body header, body, and body footer can be customized. For this customization, a set of keys is used. All they are described on the page. 7.3.2. Logger The logger works in three modes – Time, Alarm, and Time&Alarm. The mode specifies what initiates a record in the logger’s memory.
  • Page 29 Example: The current settings are: • Current time = 09:12 • Logger record sync = Enable; • Sync to the minute = 00; • Logging period = 15 minutes. The settings determine 4 records per hour in HH:00, HH:15, HH:30, and HH:45. The device is powered up.
  • Page 30 7.4.1. Backup/Restore TCG140-4 supports backup and restore of all user settings. All settings are saved in an XML backup file. This file can be used after this to restore the same settings on many devices. This is very useful for multiplying similar settings to a batch of modules.
  • Page 31 8. Setup via SMS TCG140-4 supports SMS commands for parameter change, status reports, and firmware update over the air. The commands will be executed only if they come from the phone numbers available in the section "SMS setup". The commands need different rights (master/user).
  • Page 32 • Display SMS users numbers Rights: Master, Users Syntax: display˽sms˽users Example Command: display sms users Answer: m:+359885885885,u1:+359885887766,u2:+359885999888,u3,u4 • Set email users - this message is used to add/delete email users Rights: Master Syntax: set˽email˽user˽<user>:<email> Where <email> - a valid email address <user>...
  • Page 33 Example Command: status di1 Answer: di1(Garage_door)=CLOSED Command: status s22 Answer: s22(Office)=34.5%RH • Set a relay - this message is used to switch on/off the selected relay output Rights: Master, Users Syntax: set˽<relay>=<state>˽[option] Where <relay> is r1, r2, r3 or r4 <state>...
  • Page 34 Command: set purl2=www.teracomsystems.com:8802/posttest.php Answer: purl2=www.teracomsystems.com:8802/posttest.php,post=on, period=60 • Status URL – status URL’s for XML/JSON HTTP Post Rights: Master, User Syntax: status˽purl or status˽purl2 Example Command: status purl Answer: purl=www.teracomsystems.com:8801/posttest.php, post=on,period=60 Command: status purl2 Answer: purl2=www.teracomsystems.com:8802/posttest.php, post=on,period=60 • Post period – sets XML/JSON HTTP Post period Rights: Master Syntax:...
  • Page 35 Master Syntax: update˽<URL> Where <URL> is a valid URL to public server, pointing update (.cod) file Example Command: update www.teracomsystems.com/docs/TCG140-4-v1.000-P-S.cod Answer 1: Downloading firmware... Answer 2: Firmware file downloaded. Updating... Following answers are also possible in different situations: Answer: File corrupt or wrong version!
  • Page 36 HTTP is a very popular protocol for the implementation of remote monitoring and control SCADA systems. These systems are built on client-server technology. TCG140-4 supports client mode – HTTP/HTTPS Post. This makes the device compatible with all SCADA software running HTTP protocol.
  • Page 37 The HTTP Post period can be changed by the server with the appropriate HTTP command. This makes communication very flexible. 9.2.1. Commands The commands for TCG140-4 are sent in the answer’s body of HTTP Post request. The structure of command is: set yyy=xxx Where: yyy is the command;...
  • Page 38 This indicates that there are no pending commands and the session can be closed; • On next HTTP Post period, TCG140-4 sends a new HTTP Post request (5) to the server; • The server answers with “set FIN” (6) – there are no pending commands and the session can be closed.
  • Page 39 20210601103318_status.xml. 9.3. List of HTTP API commands TCG140-4 supports following HTTP commands (case sensitive): Command Description rn=xxx Turn relay n ON (xxx=on) or OFF (xxx=off) (n is 1,2,3 or 4 for the respective relay) r2=on – will turn relay 2 ON r4=off –...
  • Page 40: File Structures

    For XML file structure please see Appendix A. For JSON file structure please see Appendix B. 9.5. MODBUS RTU 9.5.1. Communication parameters For MODBUS RTU, TCG140-4 supports the following communication parameters: • Baud rate – 2400, 4800, 9600, 19200, 38400, or 57600; TCG140-4_R1.0 – February 2021...
  • Page 41: Sensor Settings

    Sensor settings The tool works with the current MODBUS RTU communication parameters. To avoid collisions the good practice is to set TCG140-4 and the sensor with the factory default MODBUS RTU communication parameters. This will ensure a smooth operation. The default MODBUS RTU communication parameters for TCG140-4 are described in 8.5.1.
  • Page 42: Data Logger

    1131908; 06.01.2021,01:02:27;Event;18.250;;18.375;;18.125;;18.438;;18.188;;18.125;;18.313;;18.313;;2.198;9.092;0;1;0;1;1;;1;;1;;1;;1;;1;;1;;1;;0;0;0;1; 11. Firmware update TCG140-4 supports firmware update over the WEB interface and over the air. For firmware update over the WEB interface please see 7.4.2. FW update. For firmware update over the air (needs 4GLTE/3G/2G connection) please follow the steps below: •...
  • Page 43: Factory Default Settings

    Master will receive a confirmation SMS message. The update procedure takes about 2 minutes. Once the firmware update is complete (about 5 minutes), TCG140-4 will restart. Attention! Don’t turn off the power supply during the update. Turning off the power supply will damage the device.
  • Page 44: Maintenance

    Joint part with external component shall have space for attachment/removal of the cable after installation. Teracom does not guarantee a successful operation of the product if the product was used under conditions deviating from the product specifications.
  • Page 45 Appendix A The XML file (status.xml) structure: <Monitor> <DeviceInfo> <DeviceName>TCG140-4</DeviceName> <HostName>TCG140-4</HostName> <ID>862632040544279</ID> <FwVer>TCG140-4-v1.000</FwVer> <MnfInfo>www.teracomsystems.com</MnfInfo> <SysContact>info@teracomsystems.com</SysContact> <SysName>TCG140-4</SysName> <SysLocation>Location</SysLocation> </DeviceInfo> <S> <S1> <description>S1:TST1xx</description> <id>2867895F07000058</id> <type>1W</type> <addr>1Wire</addr> <item1> <value>24.2</value> <unit>°C</unit> <alarm>0</alarm> <min>19.0</min> <max>100.0</max> <hys>0.5</hys> </item1> <item2> <value>---</value> <unit>---</unit> <alarm>0</alarm> <min>---</min> <max>---</max> <hys>---</hys> </item2>...
  • Page 46 <alarm>0</alarm> <min>---</min> <max>---</max> <hys>---</hys> </item1> <item2> <value>---</value> <unit>---</unit> <alarm>0</alarm> <min>---</min> <max>---</max> <hys>---</hys> </item2> </S3> <S4> <description>S4</description> <id>0000000000000000</id> <type>1W</type> <addr>1Wire</addr> <item1> <value>---</value> <unit>---</unit> <alarm>0</alarm> <min>---</min> <max>---</max> <hys>---</hys> </item1> <item2> <value>---</value> <unit>---</unit> <alarm>0</alarm> <min>---</min> <max>---</max> <hys>---</hys> </item2> </S4> <S5> <description>S5</description> <id>152DB379F9FFFF43</id> <type>MB</type> <addr>3</addr>...
  • Page 47 <max>---</max> <hys>---</hys> </item1> <item2> <value>---</value> <unit>---</unit> <alarm>0</alarm> <min>---</min> <max>---</max> <hys>---</hys> </item2> </S6> <S7> <description>S7</description> <id>0000000000000000</id> <type>MB</type> <addr>0</addr> <item1> <value>---</value> <unit>---</unit> <alarm>0</alarm> <min>---</min> <max>---</max> <hys>---</hys> </item1> <item2> <value>---</value> <unit>---</unit> <alarm>0</alarm> <min>---</min> <max>---</max> <hys>---</hys> </item2> </S7> <S8> <description>S8</description> <id>0000000000000000</id> <type>MB</type> <addr>0</addr> <item1> <value>---</value>...
  • Page 48 </AI1> <AI2> <description>Analog Input 2</description> <value>0.000</value> <unit>V</unit> <multiplier>1.000</multiplier> <offset>0.0000</offset> <alarm>0</alarm> <min>0.000</min> <max>10.000</max> <hys>1.000</hys> </AI2> <AI3> <description>Analog Input 3</description> <value>0.000</value> <unit>V</unit> <multiplier>1.000</multiplier> <offset>0.0000</offset> <alarm>0</alarm> <min>0.000</min> <max>10.000</max> <hys>1.000</hys> </AI3> <AI4> <description>Analog Input 4</description> <value>0.000</value> <unit>V</unit> <multiplier>1.000</multiplier> <offset>0.0000</offset> <alarm>0</alarm> <min>0.000</min> <max>10.000</max> <hys>1.000</hys> </AI4> </AI>...
  • Page 49 <value>OFF</value> <valuebin>0</valuebin> <pulseWidth>0.3</pulseWidth> <control>0</control> </R3> <R4> <description>Relay 4</description> <value>OFF</value> <valuebin>0</valuebin> <pulseWidth>0.4</pulseWidth> <control>0</control> </R4> </R> <HTTPPush> <Key/> <PushPeriod>300</PushPeriod> </HTTPPush> <signalpercent>67</signalpercent> <hwerr></hwerr> <Alarmed>0</Alarmed> <Scannig>Scan</Scannig> <Time> <Date>16.02.2021</Date> <Time>14:19:12</Time> </Time> <NetworkInfo> <Name>A1 BG A1 BG</Name> <SC> <MCC>284</MCC> <MNC>01</MNC> <LAC>28201</LAC> <CID>46743</CID> <SQ>-71</SQ> </SC> </NetworkInfo> </Monitor> Where: <value>--- </value>...
  • Page 50 Appendix B The JSON file (status.json)structure: "Monitor": { "DeviceInfo": { "DeviceName": "TCG140-4", "HostName": "TCG140-4", "ID": "862632040544279", "FwVer": "TCG140-4-v1.000", "MnfInfo": "www.teracomsystems.com", "SysContact": "info@teracomsystems.com", "SysName": "TCG140-4", "SysLocation": "Location" "S": { "S1": { "description": "S1:TST1xx", "id": "2867895F07000058", "type": "1W", "addr": "1Wire", "item1": { "value": "24.0",...
  • Page 51 "unit": "---", "alarm": "0", "min": "---", "max": "---", "hys": "---" "item2": { "value": "---", "unit": "---", "alarm": "0", "min": "---", "max": "---", "hys": "---" "S4": { "description": "S4", "id": "0000000000000000", "type": "1W", "addr": "1Wire", "item1": { "value": "---", "unit": "---", "alarm": "0", "min": "---", "max": "---",...
  • Page 52 "min": "---", "max": "---", "hys": "---" "item2": { "value": "---", "unit": "---", "alarm": "0", "min": "---", "max": "---", "hys": "---" "S7": { "description": "S7", "id": "0000000000000000", "type": "MB", "addr": "0", "item1": { "value": "---", "unit": "---", "alarm": "0", "min": "---", "max": "---", "hys": "---"...
  • Page 53 "hys": "0.010" "AI2": { "description": "Analog Input 2", "value": "0.000", "unit": "V", "multiplier": "1.000", "offset": "0.0000", "alarm": "0", "min": "0.000", "max": "2.000", "hys": "0.010" "AI3": { "description": "Analog Input 3", "value": "0.000", "unit": "V", "multiplier": "1.000", "offset": "0.0000", "alarm": "0", "min": "0.000", "max": "2.000", "hys": "0.010"...
  • Page 54 "description": "Relay 3", "value": "OFF", "valuebin": "0", "pulseWidth": "0.3", "control": "0" "R4": { "description": "Relay 4", "value": "OFF", "valuebin": "0", "pulseWidth": "0.4", "control": "0" "HTTPPush": { "Key": "", "PushPeriod": "300" "signalpercent": "67", "hwerr": "", "Alarmed": "0", "Scannig": "Scan", "Time": { "Date": "16.02.2021", "Time": "14:39:55"...
  • Page 55 Appendix C Fig.1 Fig.2 TCG140-4_R1.0 – February 2021 Page 55...

Table of Contents