1. Manuals
  2. Brands
  3. Flexitron Manuals
  4. Home Automation
  5. WebdynEasy W M-Bus
  6. User manual

Flexitron WebdynEasy W M-Bus 868MHz User Manual

Hide thumbs Also See for WebdynEasy W M-Bus 868MHz:
Table of Contents

Advertisement

Quick Links

Download this manual
WebdynEasy W M-Bus
868MHz / 434MHz
User Manual
www.webdyn.com

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the WebdynEasy W M-Bus 868MHz and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Flexitron WebdynEasy W M-Bus 868MHz

Summary of Contents for Flexitron WebdynEasy W M-Bus 868MHz

  • Page 1 WebdynEasy W M-Bus 868MHz / 434MHz User Manual www.webdyn.com...

  • Page 2: Table Of Contents

    Index Glossary .............................. 5 Presentation ..........................9 General Description ............................9 Operating Principle ............................9 Interfaces ..............................10 Supported Equipment..........................13 Product and Accessory References ......................13 Technical Specifications ..........................14 1.6.1 General specifications ........................... 14 1.6.2 Technical Specifications ........................15 1.6.3 Software specifications ......................... 17 1.6.4 Battery life ..............................
  • Page 3 4.2.1.1 Local ............................. 43 4.2.1.2 Security ............................44 4.2.2 Radio WM-Bus ............................45 4.2.2.1 « whiteList » ..........................48 4.2.2.2 L Field for format B frames ......................49 4.2.3 Hub Connectivity ............................ 50 4.2.3.1 Modem ............................50 4.2.3.2 FTP/FTPS ............................. 53 4.2.3.3 NTP ...............................
  • Page 4 10 Appendix ..........................92 10.1 Configuration- Variable list ........................92 10.2 Log- List of events ............................97 11 Offices & Support contact ...................... 98...

  • Page 5: Glossary

    Glossary NAME DESCRIPTION Advanced Encryption Standard Synthetic encryption algorithm. Access Point Name The name of the access point the gateway uses to connect to the Internet via a mobile.hi connection. Base64 Encoded data using an alphabet with 64 characters. Bluetooth Low Energy Wireless transmission technique in the form of a Bluetooth- based open standard, characteristically having much lower power consumption.
  • Page 6 Message protocol in charge of addressing and sending TCP packets over the network. JSON JavaScript Object Notation JSON is an easily interpretable data exchange format. LTE-M/CAT- Long Term Evolution - Machine 4G mobile network specific to connected objects, i.e. low consumption and long range. NB-IoT NarrowBand-Internet of Things 4G mobile network dedicated to connected objects, i.e.
  • Page 7 About this document This guide describes all features of the WebdynEasy W M-Bus product. Its purpose is to help operators install and configure their WebdynEasy W M-Bus and to allow operating entities to include the collected data in their IS. This manual is split into six separate sections : Section 1: General presentation Section 2: Installation...
  • Page 8 Product History Version Content V1.0 Creation V1.1 Modification of the functioning of the product regards the magnet and the number of bips. Adding of a scheme concerning file management. V1.2 Addition and Modification on the supervision part. Adding autonomy. V1.3 Additions in the glossary, modification of the command file.

  • Page 9: Presentation

    Automatic reboot with a simple "reboot" file on the USB drive (from V2.05) Added 434MHz version (from V2.06 available on 15/11/2022) V3.1 New parameters "ciFilter", "isManufAllowList", "isMediumAllowList", "isCiAllowList", "operator", "checkBcast" Broadcast functionality for FTP. SIM card management controls. Firmware downgrade prohibited. V3.2 Clarification on how the FTP Schedule works 1 Presentation...

  • Page 10: Interfaces

    1.3 Interfaces Old interfaces :...
  • Page 11 1. HALL Effect Sensor 2. Mini-USB connector 3. Indicator Lights : LED 1 : reserved LED 2 : reserved LED 5 : Modem Status 4. Radio 868MHz or 434MHz SMA antenna 5. Housing output for 868MHz or 434MHz external radio antenna (optional) 6.
  • Page 12 New interfaces : 1. HALL effect sensor 2. Buzzer 3. Mini-USB connector 4. Indicators: LED 1: reserved LED 2: reserved LED 5: Modem status 5. 868MHz or 434MHz radio SMA antenna 6. Holder for holding the battery pack 7. Breakable output of the box for installation of M16 cable gland allowing the installation of an external 868MHz or 434MHz radio antenna (optional) 8.

  • Page 13: Supported Equipment

    antenna LTE-M/NB-IoT/2G modem (optional) 14. LTE-M/NB-IoT/2G Modem SMA antenna 15. Reset button 16. SIM card holder 1.4 Supported Equipment The hub supports all equipment compliant with the 868MHz Wireless M-Bus standard and using one of the following modes : T1, S1 and T1+C1. The concentrator supports all equipment complying with the Wireless M-Bus standard at 434MHz and using the following mode: T1.

  • Page 14: Technical Specifications

    1.6 Technical Specifications 1.6.1 General specifications References Descriptions Power supply +12V Battery 7.2V 14Ah lithium battery pack (non-rechargeable) - in optimal configuration,the battery life is at least 10 years. Consumption P : 2 W Pmax : 5 W Dimensions Old case: 160 x 150 x 55 mm New case: 150 x 153 x 57 mm Interior use Weight...

  • Page 15: Technical Specifications

    Regulation : CE marking created in the framework of European technical harmonisation legislation. It is mandatory for all products covered by one or more European regulatory texts (directives or regulations). : Symbol indicating that the waste must be collected via a specific channel and must not be disposed of as household waste.
  • Page 16 BLE interface Bluetooth 4.2 compliant SIM format SIM standard (mini SIM) format 2FF 1.8V compatible Webdyn does not supply any SIM cards. Please contact an M2M operator that supports the 2G , NB-IoT and LTE-M network. Connectivity data : RF Band Emission Frequencies Max.Power 2G GSM 900...

  • Page 17: Software Specifications

    LTE-M/NB-IoT – Bande 19 830 MHz – 845 MHz LTE-M/NB-IoT – Bande 20 832 MHz – 862 MHz LTE-M/NB-IoT – Bande 25 1850 MHz – 1915 MHz LTE-M – Bande 26 814 MHz –849 MHz LTE-M – Bande 27 807 MHz – 824 MHz LTE-M/NB-IoT –...
  • Page 18 With LTE-M : LENGTH OF LISTENING 2 uploads / day 1 upload / day 1 upload / week WINDOW IN MINUTES > 15 years > 15 years > 15 years 13 years > 15 years > 15 years 12 years 14 years >...
  • Page 19 With NB-IoT : LENGTH OF LISTENING 2 uploads / day 1 upload / day 1 upload / week WINDOW IN MINUTES 11 years > 15 years > 15 years 9 years 12 years > 15 years 8 years 11 years 14 years 8 years 10 years...
  • Page 20 With 2G : LENGTH OF LISTENING 2 uploads / day 1 upload / day 1 upload / week WINDOW IN MINUTES > 15 years > 15 years > 15 years 12 years > 15 years > 15 years 11 years 13 years 14 years 10 years...

  • Page 21: Safety Instructions

    1.7 Safety instructions Follow all the safety instructions in this guide. Failure to follow these instructions can damage equipment and endanger people. Electric connection: All wiring work must be carried out by a specialised qualified electrician. Please follow all the safety instructions featured in the equipment documentation The WebdynEasy W M-Bus product can be damaged by electrostatic discharges (ESD).

  • Page 22: Installation

    1.8 Regulations The product complies with the European directives according to the EU Declaration of Conformity available from Webdyn or on website: www.webdyn.com Recycling : The European directives enacted into national law covering battery waste and electric and electronic equipment provide the framework for the actions needed to limit the negative impact of the product’s end of life.

  • Page 23: Identification

    2.2.2 Identification The commercial reference differs depending on whether or not the hub includes a customer configuration. The commercial reference is composed as follows: Without configuration : the commercial reference is WG0612-A12. With configuration : the commercial reference is WG0612-A12 to which the customer identifier is added. For example, the following reference can be obtained: WG0612-A12-WG.

  • Page 24: Assembly

    2.3 Assembly 2.3.1 Opening/closing the box Follow these steps to open the hub box: The box can only be opened if it is not fixed to the wall. In the case where the box is fixed to a wall, it will have to be unhooked to be able to open it. If the box is well-mounted Old Case : Open the 2 hatches on the front side.

  • Page 25: Interface Description

    2. Tighten the 4 screws. 2.4 Interface Description 2.4.1 Product Power Supply 2.4.1.1 External Power Supply The WebdynEasy W M-Bus hub can be powered using 12V DC with or without a battery pack connected. Power is supplied from terminal block J8 on the left side of the battery pack. End users must use a CE certified power supply of less than 15 watts.

  • Page 26: Battery Pack

    In the new box, the cable gland is optional and is installed after breaking the breakable part provided in the box. Make sure the power supply wires are connected to the proper terminals. Product power consumption varies depending on its configuration. Make sure the power supply used can provide a minimum power of 10 watts.

  • Page 27: Radio

    Never install a battery pack that is not new because the capacity meter is reset to 100% following connection. Once a battery pack is installed, never disconnect it except to replace it. CAUTION, THERE IS A RISK OF EXPLOSION IF THE BATTERY PACK IS REPLACED BY A BATTERY PACK OTHER THAT RECOMMENDED BY WEBDYN.

  • Page 28: Cellular Network

    In the new box, the cable gland is optional and is installed after breaking the breakable part provided in the box. End users must make sure their installation using remote antennas meets applicable EMC standards. 2.4.3 Cellular Network The WebdynEasy W M-Bus hub includes a 2G, NB-IoT and LTE-M network compatible modem.. 2.4.3.1 Antenna The hub has a female SMA connector labelled “4G”...

  • Page 29: Sim Card

    2.4.3.2 SIM Card To use the LTE-M, NB-IoT or 2G modem connection to allow the hub to communicate with the remote server, the box must be opened(see section2.3.1: “Opening/closing the box”) and a mini SIM card inserted into the SIM card housing inside the hub.

  • Page 30: Indicators & Buttons

    2.4.4 Indicators & buttons The hub is equipped with: 1 Hall Effect sensor. 1 push button. 1 modem indicator. Hall Effect sensor LED5 LED1 LED2 Led 5 Led 2 Led 1 Button RESET 2.4.4.1 Hall effect sensor The WebdynEasy W M-Bus hub is equipped with a Hall effect sensor that activates when a magnet is passed over the top of the box.

  • Page 31: Reset Button

    The Hall effect sensor is used for various actions such as : Requesting the current operating mode and activating the interfaces for local configuration. Changing the operating mode. Re-applying factory settings (combined with the RESET button). 2.4.4.2 RESET button The RESET button has two functions: Restarting the product: a short press on the button Re-applying factory settings by following this procedure: 1.

  • Page 32: Bluetooth Interface (Ble)

    From version 2.05, the “info.bson” configuration file is systematically present on the WebdynEasy USB disk. From version 2.05, it is possible to restart the WebdynEasy by creating a file called “reboot” on the USB disk and using the system command to eject from the PC. The product will restart and process any command or configuration files present on the partition.

  • Page 33: Product Operation

    3 Product Operation 3.1 Starting the product By default, the WebdynEasy W M-Bus hub is shipped in either: STORAGE if the product is delivered with a customer configuration. FACTORY SETTINGS : if the product is delivered without a configuration. These are low-power modes for products to be stored for long periods of time limiting battery consumption. To find out whether the WebdynEasy W M-Bus has a customer configuration, check the product’s commercial reference.

  • Page 34: Operating Mode

    3.1.1 Operating Mode The module has 3 operating modes: FACTORY SETTINGS (no configuration) STORAGE (configuration) Mode changes are always initiated by the installer. The state machine below shows the 3 modes, the mode change conditions, and the beeps for each mode. An action on the Hall Effect sensor is taken into account as soon as a magnet passes over it.

  • Page 35: Factory Settings Mode

    . From an installer’s point of view: Passing a magnet once gives the current mode: 1 long beep: an action is underway, please wait for the action to end to ask for the function mode. 2 short beeps: the product is in STORAGE mode (customer configuration). 3 short beeps: the product is in RUNmode and the last connection with the server was successful.

  • Page 36: Storage Mode

    3.1.1.2 STORAGE Mode The product is delivered in STORAGE mode if it has a factory pre-configuration. The hub is then on standby and its consumption is minimal. When a magnet is passed, a short beep will sound to indicate that the magnet has been detected and indicate the mode.

  • Page 37: Reset

    There are 3 possibilities: Activation du Bluetooth BLE + Modem : The product waits for a configuration or an update via Bluetooth or Modem within 4 minutes before starting the RUNmode and deactivating the Bluetooth and Modem. Diagnosis command : allows the recovery of WM-BUS data from the sensors over a configured period of time (see the radio parameter "config radio duration") and to initiate the connection via modem in order to deposit them on the server.

  • Page 38: Wm-Bus Task

    3.1.2.1 WM-BUS Task The WM-BUS Radio task is used to retrieve WM-BUS data from the sensors. It has its own scheduler to set its periodicity as well as its date and time of execution. It is also possible to configure the listening time in WM-BUS. Frame Recording Principle: During a WM-Bus listener window, only the first frame of each size sent by a module is recorded.

  • Page 39: Local Configuration

    4.1 Local Configuration To configure the WebdynEasy W M-Bus locally, the hub must be in RUN or FACTORY SETTINGS mode. Local configuration can be by : USB. Bluetooth (BLE). 4.1.1 Connecting the USB cord to the product wakes it up. A new drive called “WebdynEasy W M-Bus” appears as a thumb drive.
  • Page 40 Now that you are connected to the hub, you can configure the mobile data and choose the network type as well as enter the FTP configuration. You can also run various tests such as getting the number of WM-Bus meters detected by the hub. The hub will remain in synchronisation standby mode for 4 minutes.

  • Page 41: Configuration File And Command

    4.2 Configuration file and command The configuration files exchanged with the hub are in BSON format, which is a binary version of JSON. The format described in the document is in JSON format. To transform the JSON format into BSON or vice versa, you will need to use a library available on the official website: http://bsonspec.org/implementations.html In order to avoid file alteration during exchanges, a CRC32 is integrated into each file.Voir chapitre 5.1.1.5 : «...
  • Page 42 3: Debug If the functioning mode of the product is changed to FACTORY SETTINGS or STRORAGE via FTP configuration, the gateway can only be put into RUN mode locally. (see chapter 3.1 “Start-up of the product”. Example : Using a JSON file (to be converted to BSON format for the hub): "config": "mode": "run", "name": "WebdynEasy",...

  • Page 43: Local

    4.2.1.1 Local All the hub local variables are in the “local” object in JSON. Parameters Description Magnet Configuration of the magnet action in RUN mode: 0: Bluetooth BLE+ Modem (default) 1: diagnosis command 2: request command (default) blePin Bluetooth BLE identification code (default: “1234”) testCount Number of diagnostic command sequences in a row between 1 and 30 (default 1)

  • Page 44: Security

    4.2.1.2 Security All the hub security variables are in the “security” object in JSON.. Parameters Description crcMode BSON file CRC check: 0: No CRC check 1: Partial check (no check if CRC is 0) (default) 2: CRC check enabled encryption BSON file AES encryption: true: file encryption enabled false: file encryption disabled (default)

  • Page 45: Radio Wm-Bus

    Example : Using a JSON file (to be converted to BSON format for the hub): "config": "security": "crcMode": 1, "encryption": true, "key": {"$type": "00","$binary": "RACq94N4BJyrE+5ONQ4oGw=="} "crc": 4.2.2 Radio WM-Bus All the hub WM-Bus radio variables are in the “radio” object in JSON Parameters Description mode...
  • Page 46 Typical use case: Allows you to retrieve only the short frames sent. BFormatLFieldAdaptation Modification of the L field of the WM-Bus frame for B format frames (see chapter 4.2.2.2: “L field for B format frames”): true: Adaptation of the L field from format B to format A (by default).
  • Page 47 false: blacklist IC Filter Type: isCiAllowList true: whitelisted (default) false: blacklist If the VersionField and/or the MediumField parameters of any WM-Bus endpoint are modified, it is essential to update the whitelist file into the concentrator unless you are using “skipVersionField” and/ or “skipMediumField” parameters. Example : Using a JSON file (to be converted to BSON format for the hub): "config":...

  • Page 48: Whitelist

    "config": "radio": "mode": [2,0], "duration": [120,180], "manufFilter": { "$type": "00","$binary": "TDARpQ=="}, "mediumFilter": { "$type": "00","$binary": "BwE="} "crc": Explanation : Data recovery will start with T1+C1 mode for 120 seconds, then continue with S1 mode for 180 seconds. 4.2.2.1 « whiteList » It is possible to activate the management of acquisitions of sensors or counters according to the WM- Bus identifiers entered in the white list.

  • Page 49: L Field For Format B Frames

    The concentrator whitelist table is in the “wlFilter” object, then each device is in the “id” object stored in binary format (type 0x00 in JSON) in JSON. The equipment contains 8 bytes allowing the identification of the sensor or the WM-BUS meter and is composed as follows: M-field A-field...

  • Page 50: Hub Connectivity

    4.2.3 Hub Connectivity All the hub connectivity variables are in the “remote” object in JSON. They are split into 3 families: Modem 4.2.3.1 Modem All the hub modem variables are in the “modem” object in JSON. Parameters Description Mode Connection type selection: 2G: forces the modem to 2G LTEM: Forces the modem to LTE-M NB-IoT: Forces the modem to NB-IoT...
  • Page 51 operator Digital operator code (optional) Example: 20801 Network Access Point (APN) identifier (32 characters max) null: no APN (default) user PPP connection identifier (32 characters max) null: no identifier (default) pass PPP connection password (32 characters max) null: no password (default) timeout Maximum time to connect to a network in seconds (between 60 and 1800)
  • Page 52 If no “band” parameter is entered, the modem scans all available NB-IoT bands. In order to optimize the search for the network in NB-IoT, it is strongly recommended to enter the bands authorized by the operator and the country. Please find below a table of the bands deployed worldwide for your information: Bands U.S.

  • Page 53: Ftp/Ftps

    Example : Using a JSON file (to be converted to BSON format for the hub): "config": "remote": "modem": "mode": "auto", "scanseq": [ "LTEM", "2G", "NB-IoT" "band": [ "deregisterOnLocalAction": false, "cpin": 1234, "apn": null, "user": null, "pass": null, "timeout": 240, "randomDelay": "crc": 4.2.3.2 FTP/FTPS...

  • Page 54: Ntp

    FTP server root directory (64 characters max) null: FTP account root directory The "user", "pass" and "dir" fields must not contain the "" character. Example : Using a JSON file (to be converted to BSON format for the hub): "config": "remote": "ftp": "mode": 0,...

  • Page 55: Alarmes

    Example : Using a JSON file (to be converted to BSON format for the hub): "config": "remote": "ntp": "pool.ntp.org" "crc": 4.2.4 Alarmes All the hub alarm variables are in the “alarms” object in JSON. Parameters Description oneAlarmPerDay Only one alarm transmission per modem per day: true: sends at most one alarm transmission per day (default) false: transmission of all alarms during a day...

  • Page 56: Schedule (Planification) And Monitoring

    Example : Using a JSON file (to be converted to BSON format for the hub): "config": "alarms" "oneAlarmPerDay" : true, "temperature" : null, "timeGap" : null, "battery" "crc": 4.2.5 Schedule (planification) and Monitoring The hub has: A Radio Schedule: which is used to retrieve data from WM-Bus meters and sensors. An FTP Schedule: which is used to upload files and synchronise the product clock.

  • Page 57: Radio Schedule

    Each field can be associated with the following value types: Type Example When triggered A specific value "5 * * * *" at hh:05 where hh stands for every hour (once per hour) All values (*) "0 * * * 1" at hh:00 every Monday, where hh stands for every hour (24 times on Mondays)

  • Page 58: Schedule Ftp

    If the “data” listening window is not entered, then the listening window duration will be the one defined in “config>radio>duration” (see section 4.2.2: “WM-Bus radio”). Example : Using a JSON file (to be converted to BSON format for the hub): "config": "scheduleRadio": "cron"...

  • Page 59: Monitoring

    Parameters Description cron Timer trigger: mm hh dd MM DD data Type of file to be sent: Bit 0: Data (1=enabled, 0=disabled) Bit 1: supervision (1=enabled, 0=disabled) Bit 2: log (1=enabled, 0=disabled) Example : Using a JSON file (to be converted to BSON format for the hub): "config": "scheduleFTP": "cron"...

  • Page 60: Operation

    Example : Using a JSON file (to be converted to BSON format for the hub): "config": " monitoringPeriod ": "crc": 5 Operation 5.1 The Remote Server The hub communicates with a remote server using the FTP protocol. This server is used to manage the hub remotely. The remote server has several roles: Report data and alarms collected locally by the hub: each time a connection is made to the server, whether by manual request, the triggering of an alarm or the triggering of the Connection Schedule, the hub takes...

  • Page 61: Arborescence Du Serveur

    You can configure your hub remotely from your FTP server. This is only possible if your WebdynEasy W M-Bus hub is correctly configured to upload and synchronise its configuration on an FTP server. 5.1.1.2 Arborescence du serveur The FTP server must have a tree structure specific to the WebdynEasy W M-Bus product. Below the root directory, the FTP server must have the following directories : Name Rights...
  • Page 62 “<uid>-cfg.bson” The command for the hub is in the following format: “<uid>-cmd.bson” /BIN Write Contains the update files Where : <uid>: Hub identifier. <timestamp>: Number of seconds elapsed since January 1st, 1970 at midnight UTC precisely. The minimum access rights to the different directories must be defined as specified in the table above. If the directories on the FTP server do not exist the first time the hub connects, it will create them.

  • Page 63: Operation

    5.1.1.3 Operation The hub always uploads files to the FTP server using a 2-step process: At the start of the transfer the file has an additional “.tmp” extension. When the file transfer is complete, it is renamed by removing the “.tmp” extension. This process allows the remote server to easily differentiate between files being uploaded and files that are completely uploaded.

  • Page 64: File Format

    5.1.1.5 File format The files exchanged with the remote server are in BSON format which is a binary version of JSON. The format described in the document is in JSON format. To convert JSON format to BSON format or vice versa, a library available on the official website is needed: http://bsonspec.org/implementations.html.
  • Page 65 <uid>: Concentrator identifier <timestamp>: Number of seconds elapsed since January 1, 1970 at midnight UTC precisely. Example : 123456-1591083697-config.bson A configuration file can be sent locally via USB, or remotely via the FTP “INBOX” directory. Locally : 1. Connect the USB to the hub. Then upload the configuration file (“<uid>-cfg.bson”). 2.

  • Page 66: The Data

    Refer to section 4.2: “Configuration file” or to “Appendix A – Configuration – Variable list” to see the list of variables and their possible values. 5.3 The data The data is uploaded to the “/DATA” directory of the FTP server in BSON format files. Below is the data file name format: <uid>-<timestamp>-data.bson Where :...

  • Page 67: Alarms

    Content of the received frame (header + payload without CRC) in binary format. (type 0x00 in JSON). (Base64 format in the JSON file) Example of a data file converted to JSON: "uid": "WE_1234", "source": "schedule", "TS": 1560068897, "frameCount": 2, "data": [ "T": 1560066602, "R": 199, "F":...

  • Page 68: Ack Acknowledgements

    source Source that triggered the (alarm) file upload File creation timestamp (Number of seconds elapsed since January 1st , 1970 at midnight UTC precisely) alarm Alarm Information The “alarm” alarm information is as follows: Parameters Description type Alarm type: temperature, battery or ntp value Value of the item of data that triggered the alarm Example of an alarm file converted to JSON:...

  • Page 69: Commands

    Hub identifier source Source that triggered the file upload (ftp, usb, ...) File creation timestamp (Number of seconds elapsed since January 1st , 1970 at midnight UTC precisely) Command acknowledgement The “ack” command acknowledgement consist of the following: Parameters Description type Command type corresponding to the acknowledgement cmd: command...
  • Page 70 <num>-cmd.bson With : <uid>: Concentrator identifier <num>: Number used to sequence a sequence of commands. (optional) Examples : 123456-cmd.bson 123456-1-cmd.bson 123456-2-cmd.bson The command file can be uploaded by: FTP to the remote server “/INBOX” directory for the hub (“/INBOX/<uid>/”, where <uid>...

  • Page 71: Request " Command

    firmware Hub software update diag Launch a diagnosis configGet Force the upload of the config to the remote server whiteListErase Erase the radio white list operatorInit Reset the modem network operator selection logGet Force logs to be uploaded to the remote server logClean Erase the event log supervisionClean...

  • Page 72: Factory " Command

    5.6.2 « factory » Command The “factory” command is used to restore the hub factory settings. No subcommands or parameters are required for this command. Example : Using a JSON file (to be converted to BSON format for the hub): "cmd": { "type": "factory", "cid":...

  • Page 73: Whitelisterase " Command

    "cmd": { "type": "configGet", "cid": "123456" "crc": 5.6.6 « whiteListErase » Command The “whiteListErase” command is used to erase the WM-Bus radio white list. No subcommands or parameters are required for this command. Example : Using a JSON file (to be converted to BSON format for the hub): "cmd": { "type": "whiteListErase", "cid":...

  • Page 74: Logclean " Command

    "cmd": { "type": "logGet", "cid": "123456" "crc": 5.6.9 « logClean » Command The “logClean” command is used to clear the log files. No subcommands or parameters are required for this command. Example : Using a JSON file (to be converted to BSON format for the hub): "cmd": { "type": "logClean", "cid":...

  • Page 75: Certificate " Command

    5.6.12 « certificate » Command The “certificate” command allows you to add a certificate to the concentrator. In the order, you must indicate the name of the certificate to be taken into account in the “data” field. You must also attach the certificate to add: Locally (USB): you must deposit the certificate and the order at the root of the mounted local disk “WebdynEasy”.

  • Page 76: Commande " Simpin

    The “simStatus” command lets you know if the SIM card PIN code is activated as well as the number of remaining PIN and PUK attempts. By JSON file ( to be converted into BSON format for the concentrator): "cmd": { "type": "simStatus", "cid": "c_1234"...

  • Page 77: Simnewpin " Command

    If you activate the PIN code, you must also specify the PIN code separated by a comma. (Max. 8 characters) Using this command causes a modification of the configuration of WebdynEasy. Example : Activation of the PIN code with a PIN code “1234” By JSON file (to be converted into BSON format for the concentrator): "cmd": { "type": "simPin",...
  • Page 78 The “simNewPin” command is used to change the PIN code of the SIM card. In the “data” field of the order, you must indicate the new PIN code. (max. 8 characters) To use this command, it is mandatory to have entered a PIN code in the configuration of WebdynEasy WM-Bus.

  • Page 79: Commande " Simpuk

    "uid": "WE_123", "source": "usb", "TS": 1560068897, "ack": "type": "cmd", "cid": "c_1234", "result": "ko", "data": "value error: 12346789" "crc": 5.6.18 Commande « simPuk » The “simPuk” command unlocks the SIM card after 3 incorrect PIN codes. In the “data” field of the order, you must indicate the new PIN code and the PUK code separated by a comma. (Max. 8 characters per code) The use of this command causes a modification of the configuration of WebdynEasy If you enter 10 incorrect PUK codes, the SIM card is permanently blocked.

  • Page 80: Supervision

    Command error: wrong PUK code "uid": "WE_123", "source": "usb", "TS": 1560068897, "ack": "type": "cmd", "cid": "c_1234", "result": "ko", "data": "invalid PUK code or PIN code format error, remaining try=9" "crc": 5.7 Supervision The supervision information is uploaded to the “/SUPERVISION” directory on the FTP server in BSON format. This is the supervision file name format: <uid>-<timestamp>-supervision.bson Where : <uid>: Hub identifier.
  • Page 81 name Hub name Serial number version Hardware Version Software version of the application swBle Software version of the Bluetooth BLE module Software swModem version of the Modem uptime Total operating time in RUN mode in seconds radio Total radio listening time in seconds modem Total modem time in seconds lowPower...
  • Page 82 radio Total number of wake-ups by the radio Schedule Total number of wake-ups by USB Number of watchdog triggers fault Number of fatal errors dates lastConfig Timestamp of the last configuration update (optional) lastUpdate Timestamp of the last software update (optional) lastPowerOn Timestamp of the last power-up (optional) lastCnxOk...
  • Page 83 Sometimes the “num” phone number is empty because some mobile operators do not enter the phone number on the SIM. This does not impact hub operation. The temperature “histogram” bar chart is as follows: Parameters Description below -10°c Number of times the hub temperature was below -10°C -10°c to 0°c Number of times the hub temperature was between -10°C and 0°C 0°c to 10°c...
  • Page 84 "uid": "WE_1234", "source": "schedule", "TS": 1598349735, "supervision": { "identity": { "uid": "WE_1234",, "name": "1234", "SN": "SN20200423_9876543210" "version": { "hw": 11, "sw": "01.04", "swBle": "0.1", "swModem": "BG95M3LAR02A03_01.005.01.005" "uptime": { "run": 85484, "radio": 69090, "modem": 5873, "lowPower": 336583 "measures": { "vAlim": 7100, "temperature": 15, "histogram": { "below...

  • Page 85: The Log

    5.8 The Log The logs are uploaded to the “ /SUPERVISION “ directory on the FTP server, in BSON format. This is the supervision file name format: <uid>-<timestamp>-log.bson Where : <uid>: Hub identifier. <timestamp>: Number of seconds elapsed since January 1st, 1970 at midnight UTC precisely. Example : 123456-1591083697-log.bson Log files are uploaded when connecting to the FTP server.
  • Page 86 Example of a log file converted to JSON: "uid": "WE_1234", "source": "schedule", "TS": 1560068897, "log": [ "T": 1598348100, "C": 33554432, "D": "[APP][appModeInit():133]mode: run" "T": 1598348100, "C": 33554432, "D": "[APP][appRun():27]run application" "T": 1598348100, "C": 3, "D": "[RADIO][appRadioTask():57]radio task" "T": 1598348100, "C": 3, "D": "[FRAME][Frame_FastFilter_Init():57]white list filter disable"...

  • Page 87: Update

    6 Update The WebdynEasy W M-Bus hub can be updated locally via USB or remotely via FTP. The product has 2 firmwares. One for the application part and the other for Bluetooth BLE management. The latest version of the firmware (“WebdynEasy W M-Bus_Vx.x.bson” and “WebdynEasy W M-Bus_BLE_ Vx.x.bson”) as well as the associated command are available for download on our site at the following address: https://www.webdyn.com/en/support/webdyneasy/ To update the hub, an “firmware”...

  • Page 88: Local

    Example of an application firmware update: Using a JSON file (to be converted to BSON format for the hub): "cmd": { "type": "firmware", "cid": "firmwareAPP", "data": "WebdynEasy_V1.0.bson" "crc": Example of Bluetooth (BLE) firmware update: Using a JSON file (to be converted to BSON format for the hub): "cmd": { "type": "firmware", "cid": "firmwareBLE",...

  • Page 89: Tools & Diagnostics

    7 Tools & diagnostics WebdynEasy WM-Bus configuration software: In order to facilitate the configuration of the WebdynEasy WM-Bus concentrator, product-specific configuration software has been developed by Webdyn. The software makes it possible to manage the configuration, to easily create “whiteLists” but also to send commands to the products. This “WebdynEasyConfigurator”...

  • Page 90: Support

    8 Support In case of technical problems relating to our products, contact WEBDYN support: Webdyn S.A.S 26 Rue des Gaudines 78100 Saint-Germain-en-Laye Tel.: +33 1 39 04 29 40 Mail : support@webdyn.com https://www.webdyn.com/fr/support Bring the following items: Type of product Product serial number.

  • Page 91: Faq

    9 FAQ Why has the hub stopped uploading files to the FTP server? Please check these items in this order: The battery level: if the battery level is too low or empty, the product will not run properly or not run at all. Modem reception level: a bad signal at the modem may also prevent the hub from uploading files.

  • Page 92: Appendix

    10 Appendix 10.1 Configuration- Variable list DEFAULT INFO FROM NAME+TREE STRUCTURE DESCRIPTION TYPE VALUE ONLY VERSION /version Application version Integer ● /timestamp Timestamp of the last Text ● configuration (number of seconds elapsed since 1st January 1970 at midnight UTC precisely) /uid Hub identifier...
  • Page 93 /radio/ciFilter CI field list of authorized List : sensors or counters in binary format (type 0x00 in JSON) byte 1 of CI-field in binary format (maximum 8 codes) Refer to the meter manufacturer’s manual. /radio/longHeader Use of meter information Boolean: true •...
  • Page 94 /local/timeout Maximum execution time Integer (min 60 max 3600) and disabled of the action in seconds. Functional only if the “testCount” parameter is 1. /remote/modem/mode Connection type selection List: auto •2G: forces the modem to 2G •LTEM: Forces the modem to LTE-M •auto: The modem manages the network automatically /remote/modem/scanseq...
  • Page 95 /remote/ftp/checkFtpDir Allows to make optional Boolean: true 2.05 • true: verification enabled (default) the verification of the tree • false: verification disabled structure of the FTP server during the connection /remote/ftp/checkBcast Allows you to activate the Permet d’activer la fonction Boolean: Boléen : false...
  • Page 96 /scheduleFTP/cron Timer trigger “cron” timer trigger: mm hh dd MM DD •mm: represents the minutes (from 0 to •hh: represents the hour (from 0 to 23) •dd: represents the day of the month (from 1 to 31) •MM: represents the month (from 1 to •DD : represents the day in the week: - 0 = Sunday - 1 = Monday...

  • Page 97: Log- List Of Events

    Description of the event Generic error Memory error 16777216 Generic warning 33554432 Generic info 33554435 Wakeup 33554436 LowPower 50331649 (Reset) 50331650 Initialization DEBUG Generic debug contact@webdyn.com | webdyn.com | 97 V3.02 sous réserve de modifications | Webdyn © par Flexitron Group...

  • Page 98: Offices & Support Contact

    E-mail : contact@webdyn.com Delhi Téléphone : +91.1141519011 E-mail : support-india@webdyn.com PORTUGAL Av. Coronel Eduardo Galhardo 7-1ºC 1170-105 Lisbonne Téléphone : +351.218162625 E-mail : comercial@lusomatrix.pt contact@webdyn.com | webdyn.com | 98 V3.02 sous réserve de modifications | Webdyn © par Flexitron Group...

This manual is also suitable for:

Webdyneasy w m-bus 434mhzWg0612-a02Wg0612-a03Wg0612-a12Wg0612-a13Webdyneasy w m-bus

Table of Contents