Knowledge Base
Everything you need to know to take advantage of all the powerful features of MTX IoT connectivity devices.
MTX Knowledge Base
-
Introduction
-
Software Configuration
-
External Devices
- Titan – External Devices: Logger
- Titan – External Devices: Temperature Sensor
- Titan – External Devices: Distance Sensor
- Titan – External Devices: Generic Serial Device
- Titan – External Devices: GPS Receiver
- Titan – External Devices: ModBus RTU/TCP
- Titan – External Devices: W-Mbus Concentrator
- Titan – External Devices: Wavenis
-
Others
- Titan – Passwords
- Titan – SNMP
- Titan – Tacacs+
- Titan – Titan Scripts
- Titan – Email Configuration
- Titan – HTTPS
- Titan – Modbus TCP Slave
- Titan – Movement Detector
- Titan – MQTT
- Titan – Custom LED
- Titan – Custom Skin
- Titan – Digital Input
- Titan – Jamming Detection
- Titan – Periodic Autoreset
- Titan – Time Server (NTP)
- Titan – User Permissions
- Titan – AT Command Configuration
- Titan – DynDNS
- Titan – SMS Control
- Titan – Relays
- Titan – Backup / Examples
- Titan – Remote Console
-
VPN
-
AT Commands
-
Plugins
-
Advanced Example Scenarios and Configurations
- Titan – Example Scenario 2.1: Provide Internet access to a device with an Ethernet port we want to access remotely with a SIM card and a dynamic IP address along with the DynDNS or No-IP service
- Titan – Example Scenario 2.10: Accessing data from an electronic meter via a GSM data call (Iberdrola, Endesa, etc.) and via GPRS, giving priority to the GSM call made by the company. Also, obtaining remote access to a network analyzer using an Ethernet port via Modbus TCP
- Titan – Example Scenario 2.11: Example of how Titan Scripts are used. Updating registers in a Modbus device according to the Modbus registers in a different device. Sending SMS and changing the Titan’s relays according to the values in these registers
- Titan – Example Scenario 2.12: Example of an alarm after detecting Jamming (GSM inhibitor). Remote control of an IP camera via GPRS. Changing a relay and making a warning call when possible Jamming is detected. Sending SMS alerts when an open gate is detected
- Titan – Example Scenario 2.13: Autonomous reading of Modbus registers and automatic sending to two web platforms. HTTP GET will be used to send the registers to one platform, and to the other we will send the data via FTP
- Titan – Example Scenario 2.2: Configuration to be able to access a serial device with a 3G-RS232 gateway whilst Internet access is given to a device with an Ethernet port
- Titan – Example Scenario 2.3: Provide Internet access to a device with an Ethernet port. Another serial device will be connected to the router via an RS232 port in order to send SMS messages via AT commands
- Titan – Example Scenario 2.4: Remotely access a USB device via Internet using a 3G router
- Titan – Example Scenario 2.5: Provide remote access to a device with an Ethernet port as well as to change a relay via SMS to activate/deactivate the poour supply of a third device
- Titan – Example Scenario 2.6: Periodically send data from an RS232 temperature sensor to a Web server, as well as sending SMS alerts about the temperature, providing remote access to an IP camera and changing the router’s internal relay according to a given timetable or SMS in order to activate/deactivate another device
- Titan – Example Scenario 2.7: Periodically send data from a distance sensor to a web server and planning to send SMS alerts according to the distance measured activating a warning light via relay. How to provide Internet access to WiFi enabled tablets
- Titan – Example Scenario 2.8: Configuration to send to a webserver the Modbus readings of 5 Modbus RS485 devices, as well as providing Internet access to an Ethernet network analyzer
- Titan – Example Scenario 2.9: Access to an electricity meter’s data via a GSM data call (from the energy supplier such as Iberdrola, Endesa, etc.) as well as via Internet using an existing ADSL router, giving priority to the GSM data call from the company
-
Basic Example Scenarios and Configurations
- Titan – Example Scenario 1.1: Provide a PLC device with an Ethernet port with access to the Internet
- Titan – Example Scenario 1.2: Provide Internet access and remotely connect an IP camera with an Ethernet port
- Titan – Example Scenario 1.3: Provide Internet access to a device with an Ethernet port and to several devices with WiFi connectivity
- Titan – Example Scenario 1.4: Provide a PLC device with an Ethernet port with Internet access. WiFi devices will be able to access the Ethernet device but Internet access will be blocked
-
Application Notes
- Titan – AN1: How to use a 3G/4G network to connect to an IP camera
- Titan – AN10: Sending SMSs, Emails, SNMP Traps from a Modbus-TCP Device
- Titan – AN11: Plugin No-NAT – Solving Connectivity Problems
- Titan – AN12: OpenVPN Under Demand
- Titan – AN14: Silo Level Reading and Sending with Router Titan and Maxbotix Distance Sensor
- Titan – AN15: Using Titan Router to Read Temperature and Humidity Probe, Send Readings to the Cloud and Use AT Commands via Telnet
- Titan – AN16: OpenVPN – Client & Server
- Titan – AN17: OpenVPN-EasyLink, Maintenance of Remote Routers and PLCs
- Titan – AN18: Web Control and Data Collection Platform for Routers and Modems with Tunnel
- Titan – AN19: WiFi Connectivity to Ethernet Devices
- Titan – AN2: How to test OpenVPN
- Titan – AN20: Examples of Applications with Audio
- Titan – AN21: W-MBus Device Data Hub (Order Management System)
- Titan – AN22: Reading Wireless-MBus (OMS) Devices through Modbus-TCP Protocol
- Titan – AN23: Sending SNMP Traps, SMS and Email through the Detection of Change of Status of a Digital Input
- Titan – AN24: Sending GPS Locations to a Web Platform
- Titan – AN25: How to Use the Router as an Access Point WiFi with Internet via 3G
- Titan – AN26: Sending Modbus Registries to Microsoft Azure through HTTP
- Titan – AN27: Using the Titan Router to Read Modbus Devices and Send Data to the Cloud
- Titan – AN28: How to Activate/Deactivate 2G/3G/4G Connectivity through SMS, Digital Input, Modbus or Telnet
- Titan – AN29: How to Get the GPS Location via Modbus TCP/RTU
- Titan – AN3: How to use ALIAS to execute SMS commands
- Titan – AN30: CSD Data Call Emulator: Converting GSM Calls into IP Communications
- Titan – AN32: Using the Titan Router to Read Modbus Devices, and to Send Readings to an MQTT Broker with SSL Security
- Titan – AN33: How to Get GPS NMEA Data via Serial Port, TCP Client Socket, or TCP Server Socket
- Titan – AN34: Connecting a USB Webcam to the Titan Router, Capturing and Sending Footage
- Titan – AN35: Configuring the Router to Send Data via 3G/4G, Ethernet or WiFi
- Titan – AN36: Using Titan Router as SNMP Traps to SMS and MQTT Gateway
- Titan – AN37: How to use MQTT-USB/RS232/RS485 gateways
- Titan – AN38: RS232, RS485 and USB serial port redirects
- Titan – AN39: Link with Device Manager Cervello
- Titan – AN4: Implementing a datalogger for RS232/RS485/USB devices
- Titan – AN40: Gateway LoRa-4G with sensor data sending
- Titan – AN41: IPSEC – Server IKEv2 – EAP Authentication
- Titan – AN42: IPSEC – Server IKEv2 – PSK Authentication
- Titan – AN43: IPSEC – Server IKEv2 – Authentication with certificate
- Titan – AN44: IPSEC – Client-Server IKEv2 – Authentication with certificate
- Titan – AN45: IPSEC – Server IKEv1 – PSK Authentication
- Titan – AN46: IPSEC – Server IKEv1 – Authentication with certificate
- Titan – AN47: IPSEC – Client-Server IKEv1 – Authentication with PSK
-
Introduction
-
AT Comands. User API
-
Configuration Parameters
- Tunnel – ALARM Configuration parameter: “ALARM_”
- Tunnel – Configuration parameters related to analog inputs: “ADC_”
- Tunnel – Configuration Parameters Related with COM1: “COMM_”
- Tunnel – Configuration Parameters Related with COM2: “COMM2_”
- Tunnel – CSD Configuration Parameters: “CSD_”
- Tunnel – Digital I/O and relay configuration parameters: “GPIO_”
- Tunnel – DNS Parameter configuration: “DNS_”
- Tunnel – DUAL SIM configuration parameters: “DUALSIM_”
- Tunnel – DynDNS configuration parameter: “DYNDNS_”
- Tunnel – FIREWALL configuration parameters: “FIREWALL_”
- Tunnel – General Configuration parameters “MTX_”
- Tunnel – GPRS connection configuration parameters: “GPRS_”
- Tunnel – GPS Configuration parameters: “GPS_”
- Tunnel – IEC870-5-102 configuration parameter: “IEC102_”
- Tunnel – Link Configuration parameters: “LINK_”
- Tunnel – LOGGER configuration parameters: “LOGGER_”
- Tunnel – MODBUS configuration parameter: “MODBUS_”
- Tunnel – MODBUSTCP Configuration parameters: “MODBUSTCP_”
- Tunnel – MQTT Related configuration parameters: “MQTT _”
- Tunnel – Output Configuration parameters: “OUTPUT_”
- Tunnel – SMS Configuration parameter: “SMS_”
- Tunnel – SNMP configuration parameters: “SNMP_”
- Tunnel – TACACS+ related configuration parameters: “TACACS_”
- Tunnel – TCP Configuration parameters: “TCP_”
- Tunnel – Telnet Configuration Parameters: “TELNET_”
- Tunnel – TEMPERATURE configuration parameters: “TEMPERATURE _”
- Tunnel – UDP configuration parameter: “UDP_”
- Tunnel – ULP Configuration parameter: “ULP_”
- Tunnel – Wakeup Configuration Parameter: “WAKEUP_”
- Tunnel – WAVENIS configuration parameter: “WAVENIS_”
- Tunnel – WebServer Configuration Parameters: “WEBSERVER_”
- Tunnel – WIRELESS M-BUS configuration parameter: “WMBUS_”
-
Basic Scenarios, Configuration Examples
- Tunnel – Basic LTE/4G/3G-Serial tunnel. MTX-Tunnel is configured as a TCP/IP server and permanently connected to Internet using a SIM provided by the operator with a fixed IP address
- Tunnel – MTXTunnel configured as TCP/IP client and connected permanently to LTE/4G. Network operator dynamic IP addresses are used
- Tunnel – MTXTunnel configured as TCP/IP server and occasionally connected to LTE/4G. Dynamic IP addressing. Firewall and authorized phone numbers active
- Tunnel – MTXTunnel configured as TCP/IP server and occasionally connected to LTE/4G. Network operator dynamic IP addresses are used
-
Advanced Scenarios, Configuration Examples
- Tunnel – 4G-Serial transparent gateway with SNMP service activated
- Tunnel – 4G-Serial Tunnel with SSL security. MTX-Tunnel configured as TCP/IP Client connected to GPRS permanently using a SIM card with a dynamic IP address
- Tunnel – A GPRS-serial gateway, broadcasting data that begins with a chosen header to a server
- Tunnel – Access the RS232/RS485 serial port of a device via MQTT (for serial RAW data management). Transparent catwalk “RS232/485 – MQTT”
- Tunnel – Advanced 4G-RS232 Tunnel – Setting up the MTX Tunnel as a permanently connected TCP/IP Server and configured to send the IP address to a web server by HTTP
- Tunnel – Advanced 4G-RS232 Tunnel – Setting up the MTX Tunnel as permanently connected and TCP/IP Server configured to send the IP by socket to a private DNS server
- Tunnel – Advanced tunnel 2G/3G/4G-Serial – Settings for MTX-Tunnel as TCP/IP Client with a connection 3 times an hour
- Tunnel – Advanced Tunnel 4G-RS232. Set up the modem as a TCP/IP Server connected occasionally when a GPIO and ADC level changes
- Tunnel – Advanced tunnel 4G-serial – Receiving and sending data to servers with UDP data packets
- Tunnel – Alarms sent by SMS and MQTT message before detection of 220V power loss and before the return of power. Modem with supercap of 1 minute of autonomy
- Tunnel – Conversion of a GSM communications system into an IP (2G/3G/4G) communication system
- Tunnel – Data transmission by RS232 via SMS for the control of electronic equipment with proprietary protocols. Use of ALIAS to send nonprintable characters
- Tunnel – Double 4G-RS232 tunnel. Two RS232 devices controlled by a single modem and a single SIM card. Client socket connection type
- Tunnel – Dual Tunnel 4G-RS232. Controlling 2 RS232 devices with 1 modem and SIM card. Socket connection server type
- Tunnel – Sending GPS positions in real time to server using TCP socket or HTTP
- Tunnel – Sending GPS positions, temperature and trailer opening detection for cold chain monitoring
- Tunnel – Serial 4G-UDP Tunnel. MTX configured as Client/Server UDP connected permanently to 4G and using a SIM card with a fixed IP address
- Tunnel – Serial Cable replacer RS232-4G-RS232
- Tunnel – Serial Cable replacer RS232-4G-RS232 via MQTT
- Tunnel – Tunnel – Sending telemetries (GPIOs, ADCs values) to a web server by HTTP
- Tunnel – Tunnel 4G-RS232 – Set up the modem as a permanently connected TCP/IP server, with DynDNS and Client Temporal socket enabled
- Tunnel – Use of MTX-Tunnel as 2G/3G/4G-RS232 gateway and for time synchronization of an external device connected to the modem
- Tunnel – Use of MTX-Tunnel as a datalogger. Sending customized and periodic serial data for proprietary protocols
- Tunnel – Use of MTX-Tunnel as a serial datalogger
-
ULP Configuration and Example Scenarios
- Tunnel – IP-RS232/RS485 Tunnel using ULP consumption modem. Programmed timing activation
- Tunnel – Periodic monitoring via 4G/3G/2G of a 4-20mA sensor with ultralow consumption modem. Activating sensor supply via relay. Sending to broker MQTT
- Tunnel – Periodic sending of digital and analog input value telemetry by 2G/3G/4G using ULP modem. Sending to MQTT broker
- Tunnel – Sending an SMS alarm when the digital input is activated with ultra low power consumption
- Tunnel – Sending digital and analog input value telemetry by 2G/3G/4G according to an event (not periodically) using ultra low power modem. Sending to MQTT broker
- Tunnel – Timing alarm activation of GPRS-RS232 tunnel using MTX-ULP modem
-
API Configurations and Example Scenarios
- Tunnel – API used for reading MTX-Tunnel GPIOs and ADCs from 3rd party site
- Tunnel – Using API to send data coming from a 3rd party webpage form and output serial port MTX-Tunnel
- Tunnel – Using API to send SMS to external PLC devices connected to COM1 at the same time that the 4G-RS232 tunnel is active
- Tunnel – Using API to switch a relay from a third-party or end user webpage
-
Examples and Scenarios for Automatic Reading of Modbus Devices
- Tunnel – Advanced example for modbus devices reading and broadcasting to a web platform via a JSON object
- Tunnel – How to provide MQTT communications to master Modbus RTU and Modbus RTU slaves
- Tunnel – Modbus TCP/Modbus RTU 2G/3G/4G gateway.
- Tunnel – Periodical sending of vehicle’s GPS locations and the registers of Modbus RTU temperature sensor RS485 to a Web server. Occasional 3G-5RS232 gateway for PLC’s firmware actualization
- Tunnel – Periodically obtaining readings from 5 electronic meters and sending them to a webserver using the ModBus RTU protocol
- Tunnel – PLC Modbus RTU periodically registers readings, sends them as a JSON object to webserver
- Tunnel – Providing IP to Master Modbus RTU and Modbus RTU slaves
- Tunnel – Reading and periodic sending of records of 5 Electric meters with ModBus RTU protocol and memory map for different records to a webserver
- Tunnel – Reading and periodic sending to an MQTT broker of the MODBUS registers of a PLC. DUAL SIM configuration due to loss of connectivity of an operator.
- Tunnel – Reading and sending Modbus registers from a PLC to a webserver. Remote and occasional access to PLC registers in real time and for remote update of PLC’s firmware
- Tunnel – Reading and sending Modbus registries periodically from a PLC to an FTP server
- Tunnel – Reading and writing MODBUS records on an RS232 device using MQTT communication
- Tunnel – Reading and writing Modbus registers via SMS
- Tunnel – Reading modbus Word and Binary registries, sending data to webplaform using JSON object
- Tunnel – Regular reading and delivery of Modbus records of a PLC + IP gateway for remote update of the PLC firmware to a webserver
- Tunnel – Regular reading of 3 Modbus temperature sensors and then sending to a webserver(Model MTX-Temp-RS485-IP65 of MTX accesories)
- Tunnel – Relays control, MTX modem digital and analog inputs from a SCADA system using Modbus TCP protocol
- Tunnel – Use of an MTX as local data-logger modbus local, without SIM card or GPRS connections
-
Metering Scenario Examples. Meter Reading Scenarios via GSM and GPRS
- Tunnel – A basic example for meter reading with simultaneous GPRS connections and GSM calls
- Tunnel – An advanced example for reading 2 serial devices using a single modem/SIM and simultaneously using GPRS connection and GSM calls. There is additional serial tunnelling when there are no GSM/GPRS connections
- Tunnel – Example of meter reading via IP connection for real-time readings and for Energy operator. Preference for Energy operator’s IP connection
- Tunnel – Example of reading of pulse counters (dry contact or reed). Sending data to web platform
- Tunnel – Meter reading via GSM call and/or IP communications (without SSL/ TLS security). Incorporation of Device Manager (with SSL/TLS security) for modem management
- Tunnel – Meter reading via GSM data call (CSD) and IP communications (with SSL/TLS security). Incorporation of Device Manager (with SSL/TLS security) for modem management
- Tunnel – Monitoring of 1 IEC870-5-102 meter via RS232 in real time (every 5 minutes) with data sent to the HTTP platform.
- Tunnel – Monitoring of 16 IEC870-5-102 counters via RS485 in real time (every 5 minutes) with data sent to the MQTT platform.
- Tunnel – Monitoring of 7 meters with pulse outputs via MQTT with alarm to detect the opening of the meter access door.
- Tunnel – Reading IEC counters, DLMS/Cosem, Modbus with protocols implemented in an MQTT platform
- Tunnel – Reading meter boxes via 3G in scenarios with an already installed modem that can’t be disconnected (the current modem must be kept)
- Tunnel – Reading of counters per CSD call and IP communications with SSL/ TLS. Incorporation of Device Manager for modem management and connection between modems and the meter box reading platform
-
Example Scenarios and Configurations for the use of Digital Inputs, Digital Outputs and Relays
- Tunnel – Activate a relay by voice call and by dry contact inputs to open the parking gate.
- Tunnel – Automatic activation of relay output depending on the value of an analog 0-10V probe.
- Tunnel – Automatic activation of relays according to the value of Modbus registers. Automatic sending of state changes to the MQTT/S platform.
- Tunnel – Change by SMS of up to 9 digital outputs or 9 relays.
- Tunnel – Control of the relays, digital outputs, digital inputs and 0-10V/4-20mA analog inputs of an MTX modem from a SCADA system using the MODBUS TCP protocol.
- Tunnel – DATALOGGER. Telemetry (digital and analog inputs) sent periodically to broker MQTT (via JSON object) + transparent IP-RS232 gateway for remote access to RS232 device.
- Tunnel – DATALOGGER. Telemetry (digital and analog inputs) sent periodically to the web server via HTTP (via JSON object) + transparent IP-RS232 gateway for remote access to the RS232 device.
- Tunnel – Example of using MQTT to activate/deactivate relays of a 3G modem from an Android/IO mobile phone
- Tunnel – Instant sending of telemetries via MQTT of up to 2 analog inputs 0-10V and 4-20mA.
- Tunnel – Instant sending of telemetry via MQTT of up to 8 digital inputs.
- Tunnel – JSON customization and sending topics in the data frames sent by MTX-Tunnel.
- Tunnel – Opening of a mechanical door by a missed call from an authorized phone number
- Tunnel – Periodic monitoring by 2G/3G/4G of 0-10V sensor. Activating the sensor supply through a digital output connected to an external relay. Send to web server through HTTP
- Tunnel – Periodic monitoring by 4G/3G/2G of 0-10V sensor activating the power supply of the sensor through a relay output of the modem. Sending to web server using HTTP GET.
- Tunnel – Remote management of up to 4 0-10V analog outputs via Telnet and/or MQTT/S.
- Tunnel – Remote management of up to 9 digital outputs and relays through Telnet and/or MQTT/S.
- Tunnel – SMS alarms to change up to 2 analog inputs.
- Tunnel – SMS alarms to change up to 8 digital inputs.
- Tunnel – Switching a relay depending on the astronomical clock of the MTX and according to scheduled times for special days
- Tunnel – Switching of a relay for X seconds with an SMS message
- Tunnel – Switching of relays based on the MTX astronomical clock
- Tunnel – Voice call alarm to change up to 2 analog inputs of 0-10V and 4-20mA.
- Tunnel – Voice call alarm to change up to 8 digital inputs.
- Tunnel – Writing to Modbus RTU devices based on the digital and analog inputs of the modem.
-
Example Scenarios of connection with Web Platforms
-
MTX-Tunnel I/O Description
- I/O Description: MTX-2G-T / MTX-3G-JAVA-T / MTX-4G-JAVA-T / MTX-4G-JAVA-T-S
- I/O Description: MTX-2G-T2 / MTX-3G-JAVA-T2 / MTX-4G-JAVA-T2
- I/O Description: MTX-IoT [3-S-N-N] / MTX-IoT [4-S-N-N]
- I/O Description: MTX-IOT [4-S-N-WC868]
- I/O Description: MTX-IOT [4-S-P-N]
- I/O Description: MTX-IOT [3-S-N-GPS] / MTX-IOT [4-S-N-GPS]
-
How to use Virtual Serial Ports (VSPE)
-
Example scenarios of reading and sending data from W-Mbus devices with MTX-Tunnel
- Tunnel – Reading data from W-Mbus water meters and sending it transparently to the MQTT platform. Configuration of time windows and filter by manufacturer.
- Tunnel – Reading data from W-Mbus water meters and W-MBus temperature sensors. Sending data transparently to the MQTT platform. Configuration of time windows, period and filters by manufacturer and serial number of each device.
-
Configuration for Connection
-
Access the Configuration Web Page
-
Basic
-
Advanced
-
Wireless
-
VPN
-
Security
-
Forwarding
-
Traffic Monitoring
-
Serial and Remote Management
-
Administration
-
Application Notes
Enter the “ethernet” or “modem” connection type:
For an ethernet configuration, make sure the IP parameters are compatible with server access according to the concentrator local network configuration. For an ethernet connection, the configuration must be compatible with the concentrator’s local network topology so that it can access the servers. This configuration is done from the “Networks” configuration page (see section 3.2.2.3: “Networks”).
For a modem connection, the modem configuration must be correct before a connection can be set up. This configuration is done from the “Modem” configuration page (see section 3.2.2.4: “Modem”).
The parameters for the servers to be configured are at least the following:
Therefore the following fields need to be configured: “Interface”, “Type”, “Server type”, “Address”, “Port”, “Login” and “Password”.
The other fields can be left at the default values subject to the directories having been properly created beforehand. See section 3.1.2: “Configuration files” for more details.
Wait. The concentrator will reboot using its factory configuration.
