Titan – AN41: IPSEC – Server IKEv2 – EAP Authentication
Scenario Details From a PC it is intended to remotely access the configuration of a Titan 4G router and the configuration of a PLC that is connected to the Ethernet port of said Titan router. All this through a secure IPSec type connection. It is intended to use IKEv2 and EAP authentication. Description of the […]
Titan – AN40: Gateway LoRa-4G with sensor data sending
Scenario Details This application note shows, step by step, how to carry out a scenario in which data sent by LoRa sensors, using a Titan router such as Gateway LoRa-2G / 3G / 4G, to a data collection and management platform such as Cervello, which will also act as Device Manager for the Titan router. […]
Titan – AN39: Link with Device Manager Cervello
Scenario Details Titan routers can be managed remotely through the Device Manager of the Cervello Platform. It is very useful for router maintenance and monitoring tasks, configuration changes, etc. This application note shows how to perform the autoprovisioning procedure, that is, the basic procedure for connecting to the Cervello platform. Description of the Example The […]
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.
Scenario details: It is necessary to monitor 300 W-Mbus pulse counters from the manufacturer Adeunis and 30 temperature sensors also from the manufacturer Adeunis Each meter emits 1 RF frame with the count data every 1 minute, but only the W-Mbusconcentrator must store and send 1 frame every hour to the data platform. The temperature […]
Tunnel – Reading data from W-Mbus water meters and sending it transparently to the MQTT platform. Configuration of time windows and filter by manufacturer.
Scenario details: We need to monitor 300 W-Mbus pulse counters from the manufacturer Adeunis Each counter emits 1 RF frame with the counting data every 1 minute, but only the W-Mbus concentrator must store and send to the data platform 1 frame every hour, in other words, the concentrator must configure time windows of 1 […]
Tunnel – WIRELESS M-BUS configuration parameter: “WMBUS_”
The parameters with a WMBUS_ prefix are those related to the MTX-Tunnel configurations installed in MTX modem models that have W-MBUS support. Using these configuration parameters will allow the modem to be configured to read, store and send the W-MBUS frames collected from devices that have such technology (such as temperature sensors, water meters, electricity […]
Tunnel – Monitoring of 16 IEC870-5-102 counters via RS485 in real time (every 5 minutes) with data sent to the MQTT platform.
Scenario details: An energy efficiency company needs to monitor in real time (every 15 minutes) the data of Active Absolute Energy (VabA), Inductive Reactive Absolute Energy (VabRi), Capacitive Reactive Absolute Energy (VabRc) of 16 electric meters with IEC 870-5-102 protocol with RS485 port and send the data to an MQTT platform The meters are in […]
Tunnel – Monitoring of 1 IEC870-5-102 meter via RS232 in real time (every 5 minutes) with data sent to the HTTP platform.
Scenario details: An energy efficiency company needs to monitor in real time (every 15 minutes) the data of Active Absolute Energy (VabA), Inductive Reactive Absolute Energy (VabRi), Capacitive Reactive Absolute Energy (VabRc) of 1 meter with IEC 870-5-102 protocol with RS232 port and send the data to an HTTP platform The meter is in a […]
Tunnel – Remote management of up to 4 0-10V analog outputs via Telnet and/or MQTT/S.
Scenario details: It is necessary to be able to change the state of 4 remote 0-10V analog outputs to dim some of the luminaires connected to them. Such remote activation must be done through telnet and/or an MQTT/S platform. For telnet access, only TCP connections from authorized IPs 1.2.3.4 and 1.2.3.5 must be allowed Solution: […]
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.
Scenario details: We have a Modbus RTU PLC. This PLC has in its internal memory a series of variables / registers (for example, a temperature and 3 counters, …) which must be read and periodically sent to an MQTT broker Therefore, the MTX-Tunnel must periodically interrogate the PLC through a serial port every 15 minutes […]
Geben Sie den Verbindungsmodus „ethernet“ oder „modem“ ein:
Stellen Sie bei einer Ethernet-Konfiguration sicher, dass die IP-Parameter mit dem Serverzugriff entsprechend der lokalen Netzwerkkonfiguration des Hubs kompatibel sind. Bei einer Ethernet-Verbindung muss die Konfiguration mit der lokalen Netztopologie des Hubs kompatibel sein, damit dieser auf die Server zugreifen kann. Diese Konfiguration erfolgt über die Konfigurationsseite „Networks“ (siehe Kapitel 3.2.2.3: „Netzwerke (Networks)“).
Bei einer Modemverbindung muss das Modem korrekt konfiguriert sein, bevor eine Verbindung hergestellt werden kann. Diese Konfiguration erfolgt auf der Konfigurationsseite „Modem“ (siehe Kapitel 3.2.2.4: „Modem“).
Die minimal zu konfigurierenden Serverparameter sind folgende:
Diese Felder müssen konfiguriert werden: „Interface“, „Type“, „Server type“, „Address“, „Port“, „Login“ und „Password“.
In den übrigen Feldern können die Standardwerte beibehalten werden, solange die Verzeichnisse zuvor korrekt angelegt wurden. Weitere Einzelheiten siehe Kapitel 3.1.2: „Konfigurationsdateien“.
Warten Sie. Der Hub startet nach ein paar Augenblicken mit der Werkseinstellung neu.
