Titan – AN6: Metering – How to implement a radio communication concentrator to read meters

Suchen Sie etwas anderes?

Scenario Details

The Titan routers include all the typical features of a 2G/3G/4G router. However, they also include a series of additional features that help make it one of the leading market routers based on the number of features it includes.

One of these additional features is the ability to use the Titan router as a radio communication concentrator (RF 868MHz) in order to read meters (using pulses) and send the data to a server, either via HTTP or via FTP. This is a typical metering application scenario, which, although seemingly complex, is simple to carry out using the Titan router, in particular the MTX-Router-Titan-3G-wc25 model. Below a practical example is included.

Description of the Example

In this example we will configure the MTX-Router-Titan-3G-wc25 router in order to read six water meters with pulse output (dry contacts). Three of these meters will be located no further than 1km from the concentrator, while another two will be located 3km away and the last 2km away. A Waveflow (a radio device with 868MHz frequency and internal battery, which is a pulse counter) will be connected to each water meter. The reach between the concentrator and Waveflow in a direct line of sight is 1km; thus, for those meters further away, we must use Wavetalk devices (signal boosters) as follows: for the meters 3km away, we must intersperse two Wavetalk devices, and just one Wavetalk device for the meter 2km from the concentrator. This is portrayed in the following diagram:

The aim of the setup is for the concentrator to take readings from the six meters every 12 hours, sending this data automatically using 3G to a server. That said, remote access is also required in order to take readings from any meter at any time.

Configuring 3G Communications

Configuring 3G communications is simple. We simply must specifiy the APN, login and password (and PIN if used) in the menu “Wan > Basic Settings”.

Configuring the Server to which Data will be Sent

The MTX-Router-Titan router allows data to be sent to a server in two different ways: either via HTTP GET (using a JSON object) or via FTP. In this example we will use FTP. We must configure the router’s logger using the menu “External Devices > Logger Configuration”. We must specify the FTP server’s information, as well as the frequency with which we require data to be sent from the router. Since data will be read every 12 hours, we can specify a value of once a day, for example.

Configuring Wavenis Devices

In this section we will configure the devices to be read (Waveflows) as well as the routes the boosters will follow. As per the previous diagram, we have six Waveflows with the following MAC addresses: 10604D369901, 10604D369902, 10604D369903, 10604D369904, 10604D369905 and 10604D369906. We also have the boosters, which have the following MAC addresses: 10604D369901 and 10604D369901.

Remember that each Waveflow can be used to read up to four different meters (it contains four connection points); however, in order to simplify this example, each Waveflow has been connected to just one meter.

The first thing we must do is to configure the serial port through which the 25mW Wavecard communication card connects to the MTX-Router-Titan-3G-wc25 device. This will always be in the COM4 (TTL) port. Through the menu “Serial Settings > Serial Port4 – TTL” we can set the parameters to be 9600,8,N,1, as shown in the following screen:

Once the communication port is configured, we must configure the menu “External Devices > Wavenis RF Sensors”. Here, we must activate Waveflow reading, select the COM4 TTL port, indicate the period with which the Waveflow devices will be read (in minutes; for example, for a frequency of 12 hours we need to indicate 720 minutes), and activate the logger so that the data is saved and sent to the server.

We must also indicate the MAC address of the two boosters to be used. Once completed, we must click “Save Config”.

Following this, and on the same screen, we must configure the six Waveflow devices to be read, using the information shown in the following screenshot.

Please note that for Waveflow devices 1, 2 and 3, the devices’ MAC addresses have been inputted. However, for devices 4 and 5, the MAC address has been entered, followed by the text “;R1;R2”. This is to indicate that in order to read the Waveflow devices 4 and 5, boosters 1 and 2 must be used (up to three boosters can be specified for each Waveflow device). A similar process has been followed for Waveflow device 6, this time with the text “;R1”, indicating that booster device 1 is to be used to carry out readings of this Waveflow device.

Upon completion of the configuration process, the device must be reset, after which the newly input configuration will be effective.

Points to Consider

  • In order to test the communication between the Waveflow devices and the MTX-Router-Titan-3G-wc25 device, we can use the section “Tools”, which can be found at the end of the menu “External Devices > Wavenis RF Sensors”. For example, we can input “10604D369904;R1;R2” at any time and this will read the associated device (via any defined boosters) through the push of a button.

  • In this section it is also possible to reset alarms that detect any wire faults or battery shortages (in the event that it contains a replaceable battery). The meter’s battery life can
    also be consulted from this menu.
  • Likewise, the RSSI can also be read from a specified link. If we input the MAC address 10604D369904 and click the button “GENERIC – READ RSSI”, the signal intensity between the router and the device with the specified MAC address will be read. leerá la intensidad de señal desde el router hasta el dispositivo con dicha MAC. For example, we can input “10604D369904;R1” (the booster’s MAC address can be used instead of “R1”), which will obtain the RSSI between the device with MAC address 10604D369904 and the booster device R1. Inputting “10604D369904;R1;R2” (or the boosters’ MAC address instead of “R1;R2”) will obtain the RSSI between the device with MAC address 10604D369904 and the signal booster device R2. In summary, this function allows the RSSI to be read from any point in the setup.
  • The list of Wavenis devices specifies addresses such as “10604D369904;R1;R2”. However, it is also possible to specify them in the following format:
    “10604D369904;021606300BA1;021606300BA2”. This is useful for situations in which more than 10 boosters are used, or if a Waveflow device is to be temporarily used as a booster (which is also possible). However, its disadvantage is that when a booster is replaced, the MAC address must be updated in each of the Waveflow devices that use the booster.
  • In order to test that the logger is correctly functional, we recommend using a reading period of 1 minute for both the Wavecard and the Logger. In this way, the system can be checked easily without long waits.
  • The files received in the FTP server have a specific name format. For example, the name of a file could be “358709050113764-2015-10-22-21-55.txt”, where “358709050113764” is the MTX-Router-Titan-3G-wc25 device’s IMEI number (unique for each device), “2015-10-22” is the date in the format “YYYY-MM-DD”, and “21-55” is the time in the format “HH-MM”.
  • Inside the file, the different meters that have been read are included in JSON format, as per the following example:
…
{TYPE:WAVF,TS:24/10/2015
20:03:59,IMEI:358884051175565,P:,A:10604D36990C;
R1;R2,
STATUS:OK,BAT:0,CUT1:0,CUT2:1,CUT3:1,CUT4:1,
COU1:14,COU2:6,COU3:1,COU4:4} …
…

Here, we can see the type of device that has been read (Waveflow), the date of the reading, the device’s IMEI number and its MAC address. It also contains information regarding whether a lowbattery alarm is active (0=no, 1=yes), and whether there is an active alarm for any wire faults in the four meters (0=no, 1=yes), as well as the reading of each of the four meters. Note that there is also a field “STATUS”, which indicates whether or not the reading was correctly executed; “OK” indicates that the reading was completed correctly, while “ERROR” indicates that an error occurred during the reading process.

FAQs

  • It is possible to still use the MTX-Router-Titan-3G-wc25 device for other tasks, such as controlling an IP camera, using serial ports as a 3G-RS232 gateway, using relays, SMS management, reading Modbus devices, etc., at the same time Wavenis devices are read?
    Yes, it is.
  • Everything works and I receive data to my FTP server; however, I do not have a SIM card with a public IP address and therefore cannot access the router remotely. What can I do?
    You have several options:
    1. Obtain a SIM card with a public IP address
    2. Obtain a private APN via your telephone operator
    3. Configure the Titan router as an OpenVPN client and install an OpenVPN server in your office (consult the corresponding Application Note that explains this process)
  • I have an Ethernet/Wi-Fi connection where I plan on installing the MTX-Router-Titan-3G-wc25 device. Can this connection be used instead of a 3G connection?
    Yes, it can. 3G or 4G communications can be used, but so can Ethernet/Wi-Fi. If you only require this type of connection, the MTX-Router-Titan-wc25 device (only Ethernet/Wi-Fi) would be your preferred device, as it works out cheaper.
  • I have an MTX-Router-Titan-3G-mini device already. Can I use this to read Wavenis devices?
    You could use this device, but due to its reduced size the Wavecard 25mW communication card cannot be integrated into it. You would need to obtain a Waveport USB (along with a microUSB-USBA adaptor), connecting this to the MTX-Router-Titan-3G-mini device’s microUSB port.
  • I would like to be able to use the MTX-Router-Titan-3G-wc25 device to carry out special operations on the Waveflow devices because I already know the protocol used for communications. Can the router be used as a 3G-Wavecard gateway? For example, I would like to send protocol from my server to the Wavecard transparently so that this communicates with each of the remote Wavenis devices. Is this possible?
    Yes, it is, but with restrictions. First of all, you must access the menu “Serial Settings > Serial Port 4 (TTL)” to change the option “Function: Nothing or User by External Device” to “Function: Serial IP Gateway (TCP Server)”. In this way, a transparent 3G-Wavecard gateway is created. However, you must take into consideration that certain ACK exist in Wavenis protocol.

Do you have a question? Need a quote? Please contact us.

  • This field is for validation purposes and should be left unchanged.

Appendices and other documents

Annexes et autres documents

Appendices and other documents

Appendices and other documents

Appendices and other documents

Appendices and other documents

Appendices and other documents

Appendices and other documents

Appendices and other documents

Product End of Life cycle

FAQ

No, the concentrator is not able to decrypt data from WM-BUS equipment because it does not have a safe on board to guarantee the security of the encryption keys of your equipment. The recovered data is deposited without modification (without decryption) by the concentrator on your remote 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. Look to move the product or install an external antenna to improve signal quality.
  • The last configuration file: a bad configuration file can block the product.

Remotely, by checking the regularly uploaded files if the product configuration is correct.

On site, by passing the magnet over the product, you will hear 3 short beeps.

Replace the product and inject the configuration from the old product into the new one. If a white list is used, remember to inject it into the new product as well.

Appendices and other documents

Other manuals

Application Notes

Product End of Life Cycle

FAQ

Gateway configuration:

Start by checking that the computer’s IP parameters are compatible with the WebdynSunPM IP address (by default 192.168.1.12)

Launch a web browser (Chrome, Firefox, Edge, Safari, etc.) and enter the WebdynSunPM concentrator IP address in the address bar. An authentication page is displayed:

The default accesses are:

IdentifiantMot de passe
userhighhigh

Click “Login”

There are two configuration solutions, using the web interface and using text messages:
  • Configuration using the web interface:
Start by establishing a connection to the concentrator by connecting to it to access the server configuration: Enter the “ethernet” or “modem” connection type: For an ethernet configuration, make sure the IP parameters are compatible with server access according to the concentrator local network configuration. For an ethernet connection, the configuration must be compatible with the concentrator’s local network topology so that it can access the servers. This configuration is done from the “Networks” configuration page (see section 3.2.2.3: “Networks). For a modem connection, the modem configuration must be correct before a connection can be set up. This configuration is done from the “Modem” configuration page (see section 3.2.2.4: “Modem). The parameters for the servers to be configured are at least the following: Therefore the following fields need to be configured: “Interface”, “Type”, “Server type”, “Address”, “Port”, “Login” and “Password”. The other fields can be left at the default values subject to the directories having been properly created beforehand. See section 3.1.2: “Configuration files for more details.
  • Text message configuration:
Text message configuration requires sending the following commands:
      • Apn: to configure the SIM card APN. (see section 3.2:“apn” modem configuration command)
      • Ftp: to configure the FTP server that will contain the concentration configuration (see section 3.3: “ftp” FTP configuration command”).
      • Connect: to launch the connection to the FTP server and load the configuration (see section 3.1: ““connect” connection command

Access to the FTP server depends on the selected solution.

If you have chosen a portal, it will give you the FTP server access identifiers.

If you want to use your own FTP server, contact your network administrator.

For all other configurations, and to determine the best solution, contact the Webdyn sales department which will advise you and direct you to the relevant contacts: contact@webdyn.com

General gateway use

There are 2 methods to force a concentrator factory reset:
  • Press the Factory Reset button on the concentrator for 20 seconds:
Wait. The concentrator will reboot using its factory configuration.
  • If a SIM card is installed and configured, a “factory” text message can also be used for factory reset. Just send the “factory” text message to the SIM card phone number (see section 3.7: “factory” reset command”)

It is possible to send commands to connected devices if they accept them.

The WebdynSunPM can store up to 50Mb of uncompressed data per declared device.

If there is no access to the remote server, the WebdynSunPM concentrator can store the data for several months.

The maximum data storage time varies depending on the amount of data to be collected and the configured collection frequency.

The average storage time varies from 3 to 4 months.

The average service life of the battery is 5 years.

It may vary depending on the installation environment.

All our products are guaranteed for 2 years.

For more information, read the general terms and conditions of sale.

The data volume depends on the exchanged files.

The average is about 5 MB per month but this varies from one installation to another.

Inverter compatibility

See section 1.4: “Supported devices”.

Modbus device compatibility:

Yes, different Modbus devices can be connected to the same serial port.

Device compatibility:

    • Same type of RS485 or 4 wire connection.
    • All devices should be able to be configured using identical bus specifications. Same speed, same parity, same number of stop bits and data bits on all devices and on the WebdynSunPM.
    • Each device must be assigned a unique Modbus address (between 1 and 247) on the bus. (UnitID)

Appendices and other documents

Product End of Life Cycle

FAQ

CONFIGURATION OF THE WEBDYNSUN GATEWAY

  • Start by checking that your computer’s IP parameters are compatible with the WebdynSun’s “IP” address (the default is 192.168.1.12). 
  • Next, launch a web browser (Firefox or IE) and enter the WebdynSun’s IP address in the address bar. An authentication page will appear: 

The default accesses are:
Username: userhigh
Password: high

  • Click on “log in”  

There are two types of configuration: via the web interface or via SMS.

Configuration of the web interface:

1/ Go to the configuration page with the gateway IP address (default 192.168.1.12)

2/ Go to the Configuration tab.

3/ Select either the Ethernet or modem connection mode:

If connecting via the local network (Ethernet):

  • Edit the WebdynSun’s IP parameters by assigning it a network-compatible address.

Please note, all fields must be completed in accordance with the configuration of your local network.

If connecting via the GPRS network (Modem):

  • Change the connection settings of the GPRS modem to the settings provided by your mobile operator.

4/ Edit the FTP server parameters.

5/ Confirm the changes.

6/ Restart the WebdynSun gateway using the new settings.

7/ In the menu, click on the “installation” tab, followed by the “connection” sub-tab and start the connection.

Configuration via SMS:

This configuration method requires the use of an active SIM card with a data option and a pin code that must be either “0000” or disabled.
The SIM card must be inserted into the unit before connection to the mains supply.
After connection to the mains supply, send the following SMS messages to the number of the previously inserted SIM card:

SMS for configuring the APN:
After replacing the generic fields with those of your operator, send the following SMS*:
apn=apn_name;usr=user_name;pwd=password;

Replace the above SMS fields with the following information:

  • apn_name: APN name supplied by your mobile operator
  • user_name: APN ID supplied by your mobile operator
  • password: APN password supplied by your mobile operator

SMS for FTP configuration:
After replacing the generic fields with those of your FTP server, send the following SMS*:
Ftp=server_name:user_name:password:port;

Replace the above SMS fields with the following information:

  • server_name: FTP server address
  • user_name: FTP account ID
  • Password: FTP account password
  • Port: FTP server port (the default port is 21)

Connection SMS:

Send the word “connect” by SMS* to launch a connection to the FTP server

*Please note: the formatting of the SMS must be exactly identical to that shown above (e.g.: no spaces between characters, etc.)

There are 2 ways of resetting the gateway.

  • If connecting by Ethernet:
    • Disconnect from the mains
    • Remove the cover
    • Disconnect the battery
    • Put the DIP Switch 2 on the WebdynSun card in “ON” position
    • Start the WebdynSun by connecting it only to the mains power supply
    • Wait until all the LEDs flash and then stop flashing (3 to 5 mins).
    • Disconnect from the mains
    • Reset the Dip Switch 2 to “OFF” 
    • Reconnect the battery
    • Reconnect to the mains supply and the WebdynSun starts normally.
  • If there is a SIM card inserted in the unit:
    • Send an SMS message containing the word “factory” to the number of the inserted SIM card.

NB : Resetting the gateway restores the configuration to its original state. Please note: data will be saved but the specific settings will not. Therefore, all the settings must be reconfigured.

Commands can be sent to connected devices with the exception of certain inverters and Modbus slaves that do not accept write requests.

If the device allows it, command files can be created on the FTP server.

The WebdynSun has a memory of about 100MB.

Therefore, if the remote server cannot be accessed, the WebdynSun gateway can backup data for several months.
The maximum data backup time varies depending on the amount of data to be collected.

The average backup time ranges from 3 to 4 months.

The average battery life is 5 years.

It may vary depending on the installation environment.

Yes, data may be sent to a PLC if the latter is equipped with a Modbus protocol.
The “Report” configuration file allows the WebdynSun gateway to automatically write the values read on a Modbus slave

All our products are guaranteed for 2 years.

For further information, please see our general conditions of sale.

Files uploaded by the WebdynSun gateway are compressed in Gz format.

The data contained in these files is structured in csv format.

The data volume depends on the files exchanged.

The average is about 5 MB per month but this varies from one installation to another.

INVERTER COMPATIBILITY WITH THE WEBDYNSUN GATEWAY

Different brands of inverter may be connected to the RS485(B) port or via the Ethernet port if the inverter protocol is based on the Modbus protocol (RTU or TCP).

However, different brands of inverters cannot be connected to the same RS485(A) port.

For a list of compatible inverters, please see the product page of the WebdynSun data gateway
  • Check if the correct inverter protocol is selected before starting detection:
  • Check the wiring and configuration of the inverters by referring to the inverter appendices.
  • Check that the inverters are not in OFF or stand-by mode.
  • Check that the line end plugs on the RS 485(A) Bus are turned on.

COMPATIBILITY WITH MODBUS DEVICES

Yes, any device you wish to connect must be configured and its Modbus definition file must be created.

The configuration is mainly based on the RS485 serial bus parameters and the IP parameters.

Yes, different Modbus devices can be connected to the same RS485 (B) port.

However, they must have the same communication parameters (bus parameters or compatible IP parameters), in order for them to communicate with each other.

Appendices and other documents

Appendices and other documents

Appendices and other documents

Appendices and other documents

Appendices and other documents

  • Warning – Firmware update V4.07.02 For the old version with SIM CARD of the pin code is 0000 you can update in this version. For the second case : When you insert a SIM CARD with pin code is 0000 used in this version (4.07.02) Downgrading to a previous version is not permitted.


PRODUCT END OF LIFE CYCLE

Appendices and other documents

  • Warning – Firmware update V4.07.02 – For the old version with SIM CARD of the pin code is 0000 you can update in this version.

    For the second case : When you insert a SIM CARD with pin code is 0000 used in this version (4.07.02) Downgrading to a previous version is not permitted.

PRODUCT END OF LIFE CYCLE

Annexes and other documents

FAQ

Annexes and other documents

FAQ

Annexes and other documents

FAQ

Annexes and other documents

FAQ

CONFIGURATION OF THE WEBDYNRF GATEWAY

  • If the file is deleted from the directory after connecting the WebdynRF gateway, the problem is usually due to a file format error. The configuration and control files must follow the format described in the schema (XSD) files. To check schema consistency, open the XML file with the Notepad++ text editor and install the “XML Tool” add-on. Next, copy the corresponding XSD file to the XML file in the same directory, and select “Validate now” in XML Tool. Errors detected by the tool should be displayed.
  • If the file is not deleted from the server, the most common problem is that the file has not been located correctly. The file must be available on the server in the “INBOX” directory and in the sub-directory bearing the product UID name (e.g.: “/INBOX/0045CE/”).

GENERAL USE OF THE WEBDYNRF GATEWAY

The amount of data exchanged on the GPRS network varies depending on the configuration. However, the average consumption would be about 5MB / month.
The WebdynRF gateway consumes an average of about 250mA.

There are 2 firmware updating methods:
Local updating:
On the WebdynRF configuration interface, go to the “Actions” tab and select the updater in the “File upload” menu before clicking on the “Upload” button

Remote updating:
Upload the file containing the updater (file with extension “.bz2”) in the “BIN” directory to the FTP server . Next, place the update command in the INBOX directory corresponding to your gateway (“INBOX/”, with, the identifier of the gateway concerned)

The update command must follow the following format:

      updater.tar.bz2
      checksum_md5

updater.tar.bz2
checksum_md5

With:

  • updater.tar.bz2: Updater file name uploaded to the “BIN” directory
  • checksum_md5: Md5 code of the updater file

A lack of connection to the FTP server may be due to a network connection problem (Ethernet or GPRS), an FTP login problem or a failure to initiate the connection.

If you cannot connect to the network, check the following points:

  • Ethernet:
    • Modem set to “off” or “always off”
    • “Gateway” fields correctly entered
    • At least one DNS server must be configured
  • GPRS:
    • Modem set to “on”
    • APN, APN ID and APN password correctly entered
    • GPRS call number set to “*99***1#”

If you cannot log in, check the following points:

  • Incorrect FTP parameters
  • TCP port 21 closed at output
  • Domain name resolution problem: the DNS server is not specified

If the connection fails to initiate:

In this case, only the automatic connection does not work. The problem is probably caused by an incorrect schedule configuration. Please note, the schedule ID must be an integer.

 PARTICULAR APPLICATION OF THE WEBDYNRF WIRELESS M-BUS GATEWAY

For the WM-bus module data to be transmitted, you must:

  • Choose the mode corresponding to the modules used (S, T or N)
  • Define the modules or groups of modules to be processed

A module may be defined in a unique way by all the fields below:

  • Id
  • Manufacturer
  • Version
  • Medium

If a module’s data is encrypted, the encryption key for this module can be defined in the “Key” field.

To simplify the entry of the modules to be processed, a module group can be defined that conforms to the fields entered. The other fields will then be left empty (below is an example of a configuration for retrieving all Webdyn manufacturer (WDN) modules with the encryption key “00000000000000000000000000000000”.

  •   Id :
  •   Manufacturer : WDN
  •   Medium :
  •   Version :
  •   Label : Webdyn
  •   Key : 00000000000000000000000000000000

Note: In order for the modules (filters) entered to be taken into account, the “ByPass filter” mode must be deactivated.

Click here to read the media file 

Click here to read the units file 

 PARTICULAR APPLICATION OF THE WEBDYNRF WAVENIS

The tool is connected to the gateway via the installer access (install).

It is therefore necessary to use the installer password (default is “middle”), and not the administrator’s password (default is “high”)

The statuses transmitted by the WebdynRF gateway are the raw values contained in the Wavenis modules. They are transmitted without interpretation. For further details, please refer to the Coronis module manuals.

Appendix and other documents

FAQ

CONFIGURATION OF THE WEBDYNRF GATEWAY

  • If the file is deleted from the directory after connecting the WebdynRF gateway, the problem is usually due to a file format error. The configuration and control files must follow the format described in the schema (XSD) files. To check schema consistency, open the XML file with the Notepad++ text editor and install the “XML Tool” add-on. Next, copy the corresponding XSD file to the XML file in the same directory, and select “Validate now” in XML Tool. Errors detected by the tool should be displayed.
  • If the file is not deleted from the server, the most common problem is that the file has not been located correctly. The file must be available on the server in the “INBOX” directory and in the sub-directory bearing the product UID name (e.g.: “/INBOX/0045CE/”).

GENERAL USE OF THE WEBDYNRF GATEWAY

The amount of data exchanged on the GPRS network varies depending on the configuration. However, the average consumption would be about 5MB / month.
The WebdynRF gateway consumes an average of about 250mA.

There are 2 firmware updating methods:
Local updating:
On the WebdynRF configuration interface, go to the “Actions” tab and select the updater in the “File upload” menu before clicking on the “Upload” button

Remote updating:
Upload the file containing the updater (file with extension “.bz2”) in the “BIN” directory to the FTP server . Next, place the update command in the INBOX directory corresponding to your gateway (“INBOX/”, with, the identifier of the gateway concerned)

The update command must follow the following format:

      updater.tar.bz2
      checksum_md5

updater.tar.bz2
checksum_md5

With:

  • updater.tar.bz2: Updater file name uploaded to the “BIN” directory
  • checksum_md5: Md5 code of the updater file

A lack of connection to the FTP server may be due to a network connection problem (Ethernet or GPRS), an FTP login problem or a failure to initiate the connection.

If you cannot connect to the network, check the following points:

  • Ethernet:
    • Modem set to “off” or “always off”
    • “Gateway” fields correctly entered
    • At least one DNS server must be configured
  • GPRS:
    • Modem set to “on”
    • APN, APN ID and APN password correctly entered
    • GPRS call number set to “*99***1#”

If you cannot log in, check the following points:

  • Incorrect FTP parameters
  • TCP port 21 closed at output
  • Domain name resolution problem: the DNS server is not specified

If the connection fails to initiate:

In this case, only the automatic connection does not work. The problem is probably caused by an incorrect schedule configuration. Please note, the schedule ID must be an integer.

 PARTICULAR APPLICATION OF THE WEBDYNRF WIRELESS M-BUS GATEWAY

For the WM-bus module data to be transmitted, you must:

  • Choose the mode corresponding to the modules used (S, T or N)
  • Define the modules or groups of modules to be processed

A module may be defined in a unique way by all the fields below:

  • Id
  • Manufacturer
  • Version
  • Medium

If a module’s data is encrypted, the encryption key for this module can be defined in the “Key” field.

To simplify the entry of the modules to be processed, a module group can be defined that conforms to the fields entered. The other fields will then be left empty (below is an example of a configuration for retrieving all Webdyn manufacturer (WDN) modules with the encryption key “00000000000000000000000000000000”.

  •   Id :
  •   Manufacturer : WDN
  •   Medium :
  •   Version :
  •   Label : Webdyn
  •   Key : 00000000000000000000000000000000

Note: In order for the modules (filters) entered to be taken into account, the “ByPass filter” mode must be deactivated.

Click here to read the media file 

Click here to read the units file 

 PARTICULAR APPLICATION OF THE WEBDYNRF WAVENIS

The tool is connected to the gateway via the installer access (install).

It is therefore necessary to use the installer password (default is “middle”), and not the administrator’s password (default is “high”)

The statuses transmitted by the WebdynRF gateway are the raw values contained in the Wavenis modules. They are transmitted without interpretation. For further details, please refer to the Coronis module manuals.

Annexes et autres documents

  • WARNING :  Pour les anciens produits qui disposent d’une carte SIM avec un code PIN à 0000 , la mise à jour vers la version 4.07.02 sera fonctionelle.

    Second cas : Si la carte SIM avec un code PIN à 0000 est utilisée dans cette version (4.07.02), le passage vers une mise à jour antérieure est interdit. 

NOTICE DE FIN DE VIE DES PRODUITS