Tunnel – MTXTunnel configured as TCP/IP server and occasionally connected to LTE/4G. Network operator dynamic IP addresses are used
¿Buscas alguna otra cosa?
Scenario details:
- There are 3 RS232 remote devices, configured as a 9600, 8, N, 1 and no flow control. We need to control and monitor periodically from a central server –PC with internet connection- using 4G-Serial tunnel gateway
- Server PC is waiting for incoming connections from remote MTX-Tunnel. This is the opposite to previous examples; MTX-Tunnel now connects to a known server IP address in the configured TCP/IP port. For example “server.mydomine.com” and TCP 20010 port
- MTXTunnel modems are permanently connected to the server, as the information must be in real time. As the modem connects to a well known central server IP address, the modems can use dynamic operator IP addressing
Solution: MTX-Tunnel firmware + MTX-Java-IoT/MTX-Java-T/MTX-Java-T2
Config.txt configuration file:
| Configuration | Observations |
| COMM_baudrate: 9600 COMM_bitsperchar: 8 COMM_autocts: off COMM_autorts: off COMM_stopbits: 1 COMM_parity: none GPRS_apn: movistar.es GPRS_login: MOVISTAR GPRS_password: MOVISTAR GPRS_DNS: 8.8.8.8 GPRS_timeout: 0 MTX_PIN: 0000 MTX_model: MTX-IOT-4G MTX_mode: client MTX_IDClient: equipoX MTX_urc: off TCP_IP: oficina.midominio.com TCP_port: 20010 |
Serial port baud rate 8 bit data CTS hardware control disabled RTS hardware control disabled 1 stop bit No parity GPRS APN from your network operator GPRS Login GPRS Password DNS server IP address GPRS is permanently connected If SIM card has no PIN security, use 0000 MTX terminal modem model used TCP client mode X value is different in each modem URC messages will be not sent Server IP address or DNS information Server TCP port for connection |