Titan – Titan Scripts

Looking for something else?

The MTX-Router-Titan II, MTX-Router-Titan and MTX-Router-Titan mini devices, from firmware version 1.06 onwards, allow the “Titan Scripts” to be edited. The “Titan Scripts” allow we to configure the device easily under given conditions. At the moment, the “Titan Scripts” are orientated to applications with Modbus devices.

For example, we can create a script so that whenever a Modbus register in device A has a specific value, the Titan writes a different value in a Modbus register in device B. Or, we can send an SMS; change a relay, etc. when a Modbus register in device A has a specific value.

The “Titan Scripts”, given they are editable by the user, allow we to create an infinite number of different applications with little effort. Below we have a guide showing the syntax of the “Titan Scripts” along with the available commands; however, the best way to learn how to use them and to see their potential is by understanding the examples.

Structure of the “Titan Scripts”

The Titan routers allow we to input up to 10 different scripts. The 10 possible scripts have the same structure, each with three text boxes, as shown below:

The first text box (IF) indicates the condition; that is, the Titan device will evaluate the logical expression contained here. The second text box (action1) is the action to be executed when the IF condition is true. The third text box (action2) is the action to be carried out when the IF condition is false. In pseudocode:

If what the first text box says is true
Execute the action in the second text box
If what the first text box is not true
Execute the action in the third text box

Even though we still do not know the commands available, let’s see an example:

This example will be interpreted as follows:

If the sum of [register 10 of the Modbus device with the address 1] and [register 11 of the
Modbus device with address 1] is greater than 100
Write [the value “1” in register 20 of the Modbus device with address 1]
If the sum of [register 10 of the Modbus device with the address 1] and [register 11 of the
Modbus device with address 1] is not greater than 100
Write [the value “0” in register 20 of the Modbus device with address 1]

Commands Supported by the “Titan Scripts”

Below we can see the commands currently supported, showing what we can do with them. The best way to understand the workings of each of them is by reading the examples in this section of the manual.

“Modbus Read” command:

  • Syntax: MR[modbusAddress,modbusRegister]
  • Description: reads a Modbus RTU device register. Can be used on the IF field, or the ACTION1 or ACTION2 fields
  • Parameters:
    • modbusAddress: modbus device address
    • modbusRegister: address of Modbus register to be read
  • Examples:
    • MR[1,10]: reads register 10 of the Modbus device with address 1
    • MR[192.168.1.20:502,10]: reads register 10 of the Modbus TCP device with IP address 192.168.1.20 and TCP port 502

“Modbus Write” command

  • Syntax: MW[modbusAddress, modbusRegister,registerValue,commandWrite]
  • Description: reads a Modbus RTU device register. It can be used on the ACTION1 and ACTION2 fields
  • Parameters:
    • modbusAddress: modbus device address
    • modbusRegister: address of the Modbus device register to be written
    • registerValue: value to be written in the register
    • commandWrite: OPTIONAL PARAMETER. The Modbus writing commands 3 or 4 can be used. If not indicated, the Modbus command 3 will be used
  • Examples:
    • MW[1,10,100]: writes the value “100” in register 10 of the Modbus device with address 1, using the Modbus writing command 3
    • MW[1,10,100,4]: writes the value “100” in register 10 of the Modbus device with address 1, using the Modbus writing command 4
    • MW[192.168.1.20:502,10,100]: writes the value “100” in reegister 10 of the Modbus TCP device with IP address 192.168.1.20 and TCP port 502 using the Modbus writing command 3
    • MW[1,10,100,4]: writes the value “100” in reegister 10 of the Modbus TCP device with IP address 192.168.1.20 and TCP port 502 using the Modbus writing command 4

“SET RELAY” command

  • Syntax: SR[idRelay, relayValue]
  • Description: activates or deactivates an internal relay of the Titan device. Can be used on the fields ACTION1 and ACTION2
  • Parameters:
    • idRelay: possible values: 1 (Relay 1), 2 (Relay 2)
    • relayValue: possible values: 0 (relay not activated), 1 (relay activated)
  • Examples:
    • SR[1,1]: Activates relay 1 of the Titan device
    • SR[2,0]: Deactivates relay 2 of the Titan device

“SEND SMS” command

  • Syntax: SS[telephoneNumber, message]
  • Description: sends an SNS to a specific telephone number
  • Parameters:
    • telephoneNumber: Telephone number where the SMS is to be sent to
    • message: message to be sent
  • Example:
    • SS[666123456,Alarm activated] Sends an SMS to the number 666123455 with the text “Alarm activated”

“PAUSE” command

  • Syntax: PA[seconds]
  • Description: makes a pause in the management of the Titan scripts
  • Parameters:
    • seconds: length (in seconds) of the pause
  • Example:
    • PA[5]: Creates a 5 second pause

Comando “DATE”

  • Syntax: DA[]
  • Description: pauses the Titan script management process
  • Parameters:
  • Example:
    • SS[666123456,Alarm activated DA[] ]: Sends an SMS to the cell 666123456 with the text “Alarm activated + date/time”
    • Generates a 5 second pause

Syntax of the “Titan Scripts”

The “Titan Scripts” syntax is very similar to that of Java. In each condition’s “IF” field, we must specify a sentence that has a result of TRUE or FALSE, so that ACTION1 is executed if the IF condition is TRUE, and ACTION2 is executed if the IF condition is FALSE.

In the IF field, we can use all the standard operators in Java to create the condition:

  • &&: AND logic condition
  • ||: OR logic condition
  • + – * /: add, subtract, multiply, divide operators
  • ==: “equal to” condition
  • >= “more than” condition
  • <: “less than” condition
  • >=: “more than or equal to” condition
  • <=: “less than or equal to” condition
  • (): parenthesis to encompass expressions

In the ACTION1 and ACTION2 field, we must use the MW, SR, SS action commands, although we can also use MR for more flexibility (this will become clearer in the examples that will come later). We can also use the operator && if we want ACTION1 and ACTION2 to carry out several actions. For example, we can make ACTION1 carry out two actions: write a Modbus register and send an SMS.

  • &&: concatenation of ACTION commands

Action Commands Execution Mode

Action fields have different execution modes. Edge mode (default), continuous (@) or only in the event of changes (#). The following examples show how this works.

  • Edge execution (default mode):

In this case the action MW[1,10,MR[2,3]] is executed just once upon the condition MR[2,2]>=18; i.e. once Action1 has been executed, it will not be executed again until the condition MR[2,2]>=18 is false, and then when the condition is true. This is useful when the user wants to send SMS message alerts or email alerts as this avoids continuous repeated messages.

  • Continuous execution (@):

In this case the action MW[1,10,MR[2,3]] is executed whenever the condition MR[2,2]>=18 is true. Do NOT use this option if SMS or emails will be sent as this will result in continuous messages being sent.

  • Execution upon changes (#):

In this case the action MW[1,10,MR[2,3]] is executed whenever there is a change in the action to be executed with respect to the the last execution. Therefore, for this example, it will be executed every time there is a change in the value MR[2,3].

Examples of “Titan Scripts”

The best way to understand how “Titan Scripts” work is by looking at examples. Below we can see a selection of examples to assist we.

EXAMPLE 1

 

If [register 10 of the Modbus device with the address 1] is greater than 100
Write [the value “1” in register 20 of the Modbus device with address 2]
Otherwise
Write [the value “0” in register 20 of the Modbus device with address 2]

EXAMPLE 2

If [register 10 of the Modbus device with the address 1] plus [register 11 of the Modbus device with address 1] is greater than 100
Write [the value “1” in register 20 of the Modbus device with address 1]
Otherwise
Write [the value “0” in register 20 of the Modbus device with address 1]

EXAMPLE 3

If [register 5 of the Modbus device with the address 1 has the value “1”] OR [register 6 of the Modbus device with address 1] is greater than 10
Write [in register 7 of the Modbus device with address 1 the current value of register 1 in the Modbus device with address 1]
Otherwise
Write [in register 7 of the Modbus device with address 1 the current value of register 2 in the Modbus device with address 1]

EXAMPLE 4

Always (since the condition 1==1 will always be true)
Write [in register 10 of the Modbus device with address 2 [the current value of register 11 of the Modbus device with address 1]

EXAMPLE 5

If [register 15 of the Modbus device with address 1] is greater than or equal to 100
Activate Titan device’s Relay 1
Otherwise
Deactivate Relay 1 on the Titan device

EXAMPLE 6

If (( [register 10 of the Modbus device with address 1] + [register 11 of the Modbus device with address 1]) is greater than 100) OR if (( [register 12 of the Modbus device with address 1] is greater than [register 100 of the Modbus device with address 2])
Write [in register 20 of the Modbus device with address 1 [the current value of register 15 of the Modbus device with address 2 multiplied by 3 plus 1]]
Otherwise
Write [in register 20 of the Modbus device with address 1 [the current value of register 15 of the Modbus device with address 2 multiplied by 2 subtract 1]]

EXAMPLE 7

If [register 10 of the Modbus device with address 1] is equal to 1
Send an SMS with the text “new alarm detected” to the telephone number 666123456

EXAMPLE 8

If [register 16 of the Modbus device with address 1] is greater than 10
Send an SMS with the text “new value: [value read from register 16 del of the Modbus device with address 1]” to the telephone number 666123456 AND AFTER Write [in register 17 of the Modbus device with address 1 the value 1]]
Otherwise
Write [in register 17 of the Modbus device with address 1 the value 0]]

EXAMPLE 9

If [register 10 of the Modbus device with address 1] is equal to 1
Send an SMS with the text “new alarm detected” to the telephone number 666123456 AND AFTER Activate the Titan device’s internal Relay 1
Otherwise
Deactivate the Titan device’s internal Relay 1

EXAMPLE 10

If [register 15 of the Modbus device with address 1] is greater than 10
[Activate the Titan device’s internal Relay 1] AND AFTER [pause for 5 seconds] AND AFTER [Deactivate the Titan device’s internal Relay 1]

EXAMPLE 11

If [register 15 of the Modbus device with address 1] is greater than 10
CONTINUOUSLY [Activate the Titan device’s internal Relay 1] AND AFTER [pause for 5 seconds] AND AFTER [Deactivate the Titan device’s Relay 1]

The difference between example 10 and 11 lies in the @ symbol. This indicates that the action is continuously executed. This means that in example 10, ACTION1 is executed just once when the IF condition is true, and will not be executed again until ACTION1 changes or ACTION2 is executed. In example 11 however, ACTION1 is executed continuously whenever the IF condition is true; i.e. the relay is changing all the time.

EXAMPLE 12

If [register 4 in Modbus device with address 1] is greater than 10
Send an email with the text “New alarm detected. Value [value read from register 4 of the Modbus device with address 1]” to the email jgallego@matrix.es

ADDITIONAL NOTES

  • Remember that if the command SE[] is used to send emails, the device must be configured beforehand using the menu “Other > Email configuration”

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

Appendices and other documents

Appendices and other documents

Appendices and other documents

FAQ

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.
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.

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 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.

Appendices and other documents

Other manuals

Application Notes

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)

Annexes and other documents

FAQ

Annexes and other documents

FAQ

Annexes and other documents

FAQ

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

Appendices and other documents

Appendices and other documents

Appendices and other documents

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.