Suchen Sie etwas anderes?
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 hour
- The meters will be installed in an urban area with many other W-Mbus devices nearby, so a filter must be configured, in addition to the aforementioned 1 hour window, so that only the meters from a certain manufacturer are read: Adeunis
- The data must be read and stored within the hub’s memory and automatically sent to a platform via MQTT using a JSON object whenever there is data coverage. To save data, the W-Mbus frame must be base-64 encoded
Solution: MTX-Tunnel firmware + MTX-IoT-S [4-N]
Example of configuration (config.txt file):
Configuration | Observations |
COMM2_baudrate: 9600 COMM2_bitsperchar: 8 COMM2_autorts: off COMM2_autocts: off COMM2_stopbits: 1 COMM2_parity: none GPRS_apn: movistar.es GPRS_login: MOVISTAR GPRS_password: MOVISTAR GPRS_timeout: 0 MTX_PIN: 0000 MTX_mode: none MTX_model: 199802407 MTX_ping: 30 MTX_pingIP: 8.8.8.8 MTX_TPServer: time1.google.com MTX_TPServer: 2.europe.pool.ntp.org MTX_TPProtocol: ntp MTX_TPFormat: unit MTX_porAux: wmbus MTX_numGSMErrors: 180 SMS_allPhones: on SMS_sendIP: on SMS_ATEnabled: on SMS_ATResponse: on LOGGER_enabled: on LOGGER_registerSize: 1000 LOGGER_numRegistersRam: 1000 LOGGER_numRegistersFlash: 0 LOGGER_mode: mqtt LOGGER_mqttTopic: /LOGGER MQTT_enabled: on MQTT_server: tcp://broker.release.cervello.io.com:1883 MQTT_id: psdjs334jjsd8345 MQTT_login: 3ddg435g67899 MQTT_password: 2345433456567 MQTT_attopic1: /cervello/devices/[MQTT_ID]/rpc MQTT_atrtopic: /cervello/devices/[MQTT_ID]/rpc/response MQTT_qos: 1 MQTT_keepalive: 360 DNS_enabled: on DNS_mode: mqtt DNS_mqttTopic: /DNS DNS_period: 3600 WMBUS_mode:9 WMBUS_interval: 60 WMBUS_filter: ARF WMBUS_data: jsonrawbase64 |
Speed of serial port Data bit No flux control No flux control Stop bits Bit parity APN GPRS provided by the GSM operator GPRS Login GPRS Password Modem is always GPRS connected Pin of the SIM GPRS connection server type Modem model Ping time to oversee connection Google IP (f.e.) to ping Time server Time server backup NTP protocol Time format Auxiliar port Reset if no registration in network in 1800 secs Send SMS with commands from any phone Modem responds to a missed call/SMS Commands can be sent to the MTX by SMS MTX responds with an SMS to a command SMS MTX responds with an SMS to a command SMS Period to read counter Logger on to store readings Max. number of MTX internal registries Internal registry size Max. number of registries Sending mode via MQTT Data sending MQTT topic MQTT enabled Broker MQTT to be used Identification of the equipment in the broker No username No password MTX topic to receive AT commands Topic where MTX sends answers to commands QoS established 360 seconds keepalive Status data sending activated MQTT sending mode Topic where status data will be sent to Every 3600 seconds a sending will be made We configure work mode 9 for Wireless MBus We set a window of 1 hour (60 minutes) We configure a filter for Adeunix devices We configure the data in base 64 |
Details:
- After the configuration is carried out, the MTX-Tunnel will store in memory a single frame of each W-Mbus device from the manufacturer Adeunis. Said data will be logged in RAM (it could be in flash if necessary modifying the configuration), encapsulated in JSON format and sent to an MQTT broker at topic / LOGGER. The data corresponding to the counter within the JSON, will be encoded in BASE64.
Example:{“IMEI”:”354033091777774”,”TYPE”:”WMBUS”,”TS”:”2020-12-11T08:58:07Z”,”WDATA”:”HURGBioQACABG3IqEAAgRgYBGz8AAAAEZrcAAAASLw==”}Where:
IMEI: the IMEI of the modem sending the data
TYPE: type of frame sent
TS: Timestamp of when the W-Mbus frame was collected in the MTX-Tunnel
WDATA: W-Mbus data in BASE64 format