Titan – AN49: LoRa server with slave LoRa gateway
Scenario Details MTX-StarLora is featured as LoRa-4G gateway packet forwarder using external LoRa Server. Check our app note 39. MTX-StarLora is also featured with ChirpStack integrated Lora Server inside and we’ll add more remote gateways and nodes Check our app note 48. This is our implementation block of our TITAN-Router with LoraServer. In a regular […]
Titan – AN48: Internal LoRa server
Scenario Details MTX-StarLora is featured as LoRa-4G gateway using external LoRa Server. Check our app note 39. MTX-StarLora is also featured with integrated Lora Server inside. That means that MTX-StarLora does not depend on external LoRa Servers, like TTN & among others, all the control over other gateways and external Lora devices is done internally. […]
EOS – Certificate
Certificate Unified management of device certificates, such as http certificates, mqtt certificates, ipsec certificates, and openvpn certificates. Certificate import: Users can import externally certificates Certificate create: Users can create certificates on the device Certificate Request: Export the certificate request file based on the existing certificate.
EOS – Modbus
Modbus
EOS – SMS Control
SMS Control For more detailed information about SMS control please refer to the application note AN5 “MTX-Router-EOS management via SMS”. SMS center: Used to forward received information. Name: Name of control brake operation. Phone Num: Designate to receive the mobile phone number control, if it is empty, receive any mobile phone number control. Action: Includes […]
EOS – Position
Position This menu is only valid for GPS versions. Configure the output port to output positioning data or differential data. GPS Output Interface: Choose the way of data output Protocol, GPS Center Address, GPS Center Port: Network Output Configuration GPS Information Contents: After checking, the output location information will contain the corresponding type data. ID […]
EOS – Traffic Flow
Traffic Flow Visual display of statistics of the upstream and downstream, as well as the total traffic.
EOS – OpenVPN
OpenVPN Please refer to Aplication Note from our website “AN2- OpenVPN configuration on MTX-Router-EOS”. Server Start Type: Startup while wan is up or system is up. Auth Mode: Support pre-shared key authentication System Generation Key: Randomly generated by the system Pre-shared Key: Configure pre-shared key Server mode: Tunnel mode or bridge mode Peer Tun Ip/ […]
EOS – AN5: MTX-Router-EOS management via SMS
Introduction The MTX-Router EOS can be managed by sending SMS. This functionality allows the user to be able to carry out actions via SMS such as restarting, checking the coverage, connecting or disconnecting from the network or knowing the value of any router configuration parameter. The SMS control configuration menu is found under „Serial and […]
EOS – AN2: OpenVPN configuration on MTX-Router-EOS
Introduction This application note will explain how to configure the MTX-Router-EOS in order to perform a client – server configuration using OpenVPN and shared key. It is not part of this application note how to configure the network interfaces of the computers, nor windows firewall options and so on. OpenVPN server configuration From the VPN […]
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.
