Titan – AN26: Sending Modbus Registries to Microsoft Azure through HTTP
Introduction Titan routers can be used as Modbus RTU concentrator or Modbus TCP or both simultaneously. That is, Titan routers are able to read the Modbus registries of third-party devices and send them via MQTT, HTTP/HTTPS or FTP. This application note shows how to send Modbus registries via HTTPS to Azure, Microsoft IoT platform. Example Scenario There […]
Titan – AN25: How to Use the Router as an Access Point WiFi with Internet via 3G
Introduction One of the Titan routers many features is the ability to function as an Access Point Wifi to give 3G Internet connectivity to 8 Wifi devices. In this application note there is a typical example of the configuration for this scenario. In order to configure the Titan router as an Access Point Wifi we will do […]
Titan – AN24: Sending GPS Locations to a Web Platform
Scene Details Some Titan router models have an internal GPS. That means that, apart from doing everything a 3G router does (Internet connectivity), it can manage a small fleet. Titan routers allow to manage a GPS location in several ways. For example, it is possible to configure a Titan router to send NMEA location data through one […]
Titan – AN23: Sending SNMP Traps, SMS and Email through the Detection of Change of Status of a Digital Input
Introduction The Titan mini router family (MTX-Router-Titan-mini , MTX-Router-Titan-3G-mini, MTX-Router-Titan-3Gmini-GPS and MTX-Router-Titan-4G-mini-GPS) have a digital input in the PIN13 of their DB15 connector. That digital input has a dry contact, that is, it can be activated through GND. In order to activate the digital input, we just need to connect PIN13 with PIN14 (GND). If we want […]
Titan – AN22: Reading Wireless-MBus (OMS) Devices through Modbus-TCP Protocol
Introduction Titan routers (those which have an optional W-MBus) can be used to convert Modbus TCP – Wireless M-Bus protocols. Nowadays there are many platforms using Modbus TCP protocol to read different kinds of devices (meter boxes, network analysts, …). With MTX-Router-Titan-3G we can keep using the same existing software platforms, meaning, we can keep using Modbus TCP […]
Titan – AN21: W-MBus Device Data Hub (Order Management System)
Introduction Titan routers that have the W-MBus card, which is optional, can be used as W-MBus devices data hubs (OMS). It is very appealing when it comes to metering applications, because it easily allows to gather, package and send the data coming from meter boxes with integrated W-MBus technology or regular meter boxes connected to W-MBus impulses meter […]
Titan – AN20: Examples of Applications with Audio
Introduction Titan routers do not have audio incorporated. However, they are compatible with economic multimedia USB dongles. Using a USB dongle connected to our router Titan, we can play audio files, use an API to convert text into audio, and play files hosted in web servers, by using simple AT commands sent by Telnet, SMS, modbus, snmp, etc. […]
Titan – AN19: WiFi Connectivity to Ethernet Devices
Scene Details This application note details how to configure a Titan router to give Wifi connectivity to a ETH device. We will use a PLC with Ethernet connection as an example. We need to connect the PLC to the Internet through ADSL router with Wifi connectivity. Additionally, it should be possible to access the TCP 502 port of […]
Titan – AN18: Web Control and Data Collection Platform for Routers and Modems with Tunnel
Introduction Titan routers and modems with MTX-Tunnel firmware have the ability to send data to web platforms. Data that can be collected from sensors, but also own data, such as IP address, coverage, firmware version, etc. It is also possible to communicate with them from a web platform to execute actions, such as a configuration change or the […]
Titan – AN17: OpenVPN-EasyLink, Maintenance of Remote Routers and PLCs
Scene Details The new OpenVPN EasyLink feature is designed for those facilities requiring occasional remote maintenance. With EasyLink you do not have to pay a monthly fee like many web platforms, nor will there be any problems regardless of whether the remote router\’s SIM card has a public/private IP address or is dynamic/static. The EasyLink connection is designed […]
Les accès par défaut sont :
Saisir le mode de connexion « Ethernet » ou « modem » :
Dans le cas d’une configuration par Ethernet, veiller à ce que les paramètres IP soient compatibles avec l’accès au serveur d’après la configuration du réseau local du concentrateur. Dans le cas d’une connexion par Ethernet, la configuration doit être compatible avec la topologie du réseau local du concentrateur afin qu’il puisse accéder aux serveurs. Cette configuration se fait via la page de configuration « Networks » (voir chapitre 3.2.2.3 : « Réseaux (Networks) »).
Dans le cas d’une connexion par modem, la configuration du modem doit être correcte avant de pouvoir effectuer une connexion. Cette configuration se fait dans la page de configuration « Modem » (voir chapitre 3.2.2.4 : « Modem »).
Les paramètres des serveurs à configurer au minimum sont les suivants :
Il faut donc configurer les champs : « Interface », « Type », « Server type », « Address », « Port », « Login » et « Password ».
Les autres champs peuvent être laissés aux valeurs par défaut à condition que les répertoires aient été créés correctement auparavant. Voir chapitre 3.1.2 : « Fichiers de configuration » pour plus de détails.
Attendre. Le concentrateur va redémarrer avec sa configuration usine.
