Search
Close this search box.

Tunnel – SMS Configuration parameter: “SMS_”

Suchen Sie etwas anderes?
< Zurück zur Wissensdatenbank

MTXTunnel has a lot of SMS features. SMSs can be used (sent and received) to configure, report, start/stop any service, etc.

You need to configure the SMS messaging feature with the following parameters:

SMS_sendIP

Description: MTXTunnel starts the 4G/3G/2G connection and associated services (tunnel, WebServer, telnet …) if it receives a missed call or an SMS with the text string “mtxtunnel on”. This parameter means that MTX-Tunnel has to send the obtained IP address in another SMS.

Possible values:

  • on, off
  • Default value: off

Additional notes:

  • If the parameter was already enabled (value “on”) and the G/3G/2G connection was already established, MTX-Tunnel sends the obtained IP address to the sender
  • Only authorized phones will receive a response if the SMS_allPhones parameter is “off”

SMS_ATEnabled

Description: You can execute an AT command sent in an SMS format from a mobile phone terminal by enabling this parameter.

Possible values:

  • on, off
  • Default value: off

Additional notes:

  • Use a value of “on” to enable this feature. The SMS must start with the special string header “MTXTUNNEL AT”
  • E.g. If you need to find out the remote modem network coverage, send an SMS with MTXTUNNEL AT+CSQ. Do not use “”
  • Only authorized mobile phone numbers can execute AT commands using SMS if the SMS_allPhones parameter is disabled (“off” value)

SMS_ATResponse

Description: Some SMSs can be sent to perform an operation and you do not need a response (an SMS to be sent back to you). However if you need an SMS response from MTX-Tunnel execution status, enable this parameter.

Possible values:

  • on, off
  • Default value: off

Additional notes:

  • If you send a command by SMS or RS232/485 (see SMS_tunnelString) to the end device, MTX-Tunnel waits for 5 seconds before replying and sending an SMS with the response or error

SMS_allPhones

Description: You can use this parameter to specify whether any phone number is authorized to start the GPRS session by sending an SMS (text “mtxtunnel on”) or via a missed (voice) call.

Possible values:

  • on, off
  • Default value: off

Additional notes:

  • “on” value means all end phone numbers are authorized for SMS control
  • “off” value will only allow this feature to work with configured phone numbers. See the next parameter to learn how to authorize phone numbers

SMS_validPhone1, SMS_validPhone2, … , SMS_validPhone10

Description: this parameter is used to allow up to 10 phone numbers to have MTX-Tunnel SMS control. SMS_allPhones parameter must be “off.”

Possible values:

  • Numeric phone number, either local or international
  • Default value: none

Additional notes:

  • Valid characters are the numbers “0”… “9” and the “+” character

SMS_alias1, SMS_alias2, … , SMS_alias10

Description: previous configuration parameters show how to send AT commands via SMS so they are executed by MTX-Tunnel. However, sometimes it can be uncomfortable to send an SMS with the text AT^MTXTUNNEL=SETIO,3,1 to communte a digital output, specially if the MTX-Tunnel is part of a thirdparty system.

It is possible to establish up to 10 alias for the execution of AT commands. Following the previous example, an alias could be established: Rele1on> AT^MTXTUNNEL=SETIO,3,1. With that, a received SMS by the MTX-Tunnel with the text “Rele1on” would be interpreted like the command “AT^MTXTUNNEL=SETIO,3,1.”

Possible values:

  • 64 characters max text string
  • Default value: none

Additional notes:

  • The string must contain the special character “>” to separate the alias and the AT command

SMS_aliasOk

Description: The SMS_ATResponse parameter allows us to configure MTX-Tunnel to reply via SMS to an incoming SMS that contains an AT command with the corresponding response. This parameter (SMS_aliasOk) allows us to substitute the response given by the modem with user defined text when the AT command has been correctly executed.

Possible values:

  • A text string with a maximum of 100 characters
  • Default value: none

Additional notes:

  • If the SMS_aliasOk parameter contains text (i.e. not left blank), this text will be sent via SMS as a response to the AT command instead of the technical result of the AT command generated by the modem

SMS_aliasError

Description: The SMS_ATResponse parameter allows us to configure MTX-Tunnel to reply via SMS to an incoming SMS that contains an AT command with the corresponding response. This parameter (SMS_aliasOk) allows us to substitute the (technical) response given by the modem with user defined text when the AT command has NOT been correctly executed.

You can use this parameter if the execution of an AT command was unsuccessful and there was an error. It is possible to change the error with your own text response string.

Possible values:

  • A text string with a maximum of 100 characters
  • Default value: none

Additional notes:

  • If the SMS_aliasOk parameter contains text (i.e. not left blank), this text will be sent via SMS as a response to the AT command instead of the technical result of the AT command generated by the modem

SMS_aliasResponse

Description: SMS_aliasResponse parameter allows to define the corresponding response to an alias. That means it allows to decide whether to return the full answer of the command to be run (i.e. including the executed command in the SMS) or to include the response only.

Possible values:

  • full, result
  • Default value: full

Additional notes:

  • Examples:
  • In case the value of the parameter SMS_aliasResponse is “full”, the following will occur:
    SMS sent: TEMP
    SMS received: AT^MTXTUNNEL=GETMODBUS,1;10;1;3
    25
    OK
  • In case the value of the parameter SMS_aliasResponse is “result”, the following will occur:
    SMS sent: TEMP
    SMS received: TEMP > 25

SMS_tunnelString

Description: MTXTunnel features SMS tunnelling to serial COM1. This parameter enables and configures text to be sent directly to the device connected to COM1.

A value “MTX” enables SMS tunnelling. Example: An SMS with the text “MTX+[space]123456789” will be interpreted and the text string “123456789” will be sent to the serial COM.

Possible values:

  • A text string with a maximum of 16 characters
  • Default value: none

Additional notes:

  • The space character is used as separator between the SMS_tunnelString parameter activation string and the text string to be sent to COM1
  • If SMS_responseAT parameter is enabled (value=on), MTX-Tunnel will wait 5 seconds and an SMS will be sent back with the device’s response data present at the COM1 port
  • This response must be truncated to 160 characters long so it does not exceed the string length

SMS_urc

Description: This parameter is available from version MTX-Tunnel v7.15. If the value is set to “on”, every time an SMS messsage is received, the modem will send an URC via the serial port indicating the SMS has been received.

Possible values:

  • on, off
  • Default value: off

Additional notes:

  • The URC format is:
    ^MTX_SMS[space]PhoneNumber,Textmessage
    It can be very useful if, besides using a GPRS serial gateway, you want to receive in RAW mode
    an SMS message sent from a mobile phone.

SMS_header

Description: Parameter available from version MTX-Tunnel v7.17. In v7.16 MTX-Tunnel and previous versions, all AT commands sent via SMS had to be preceded by the key “mtxtunnel”. For example, to send the AT command to check remote coverage it was necessary to send a SMS message with the text “mtxtunnel at+csq”. Or to learn the current modem IP, you had to send an SMS with the text “mtxtunnel on” It is now possible to personalize this key.

Possible values:

  • Text of up to 6 characters
  • The value “none” will make it unnecessary to enter any header in the SMS
  • Default value: mtxtunnel (for compatibility with previous versions)

Additional notes:

  • The use of an additional header is always recommended, especially if all telephone numbers are authorized to send commands via SMS

SMS_replaceText

Description: This parameter allows you to replace a string received in a SMS message with a different one. For example, if in an SMS message a text with the characters “XX” is included, these characters could be replaced by “@12345”.

Possible values:

  • TextToReplace; TextReplacement
  • Default value: none

Additional notes:

  • It can be useful to send special characters such as @
  • An example of configuration can be:
    SMS_replaceText: XX,@12345 (texts separated with a semicolon)

SMS_defaultPrefix

Description: With this parameter it is possible to set the international prefix that will be considered for those SMS or missed GSM calls which are received in the modem with any prefix. That is to say, if modem receives a GSM call and it doesn’t include the prefix, this prefix will be used.

Possible values:

  • Maximum length 16 char
  • Default value: nothing

Additional notes:

  • This parameter is only used by modem when the parameter SMS_allPhones has the value “off”, i.e. when authorized telephone numbers are authorized
  • Example. We need to make a missed call to the modem for getting the current IP address. Additionaly we want to send AT command by SMS from authorized telephone numbers
    SMS_allPhones: off
    SMS_sendIP: on
    SMS_ATEnabled: on
    SMS_ATResponse: on
    SMS_validPhone1: +34666123456
    SMS_validPhone2: +34666123457
    SMS_defaultPrefix: +34

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

  • This field is for validation purposes and should be left unchanged.
WEBDYN
IoT Products
Useful links

Webdyn © All rights reserved           Contact us | Legal notice | General terms and conditions of sales | Accessibility

Appendices and other documents

APPLICATION NOTES

 

PRODUCT END OF LIFE CYCLE

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

Appendices and other documents

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

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