Tunnel – LOGGER configuration parameters: “LOGGER_”

Looking for something else?

LOGGER_ prefix parameters relate to MTX internal datalogger features.

Datalogger has to be enabled when reading ModBus equipment connected to a serial port. Datalogger can be used to store readings and the status of inputs/outputs.

LOGGER_enabled

Description: enable internal MTX-Tunnel datalogger. It will store RF cards –Wavenis cards- readings, input/output values/statuses and Modbus data in the memory and sends it to a http server using GET via a JSON object.

Possible values:

  • on, off
  • Default value: off

Additional notes:

  • Please use the account support line at iotsupport@mtxm2m.com for further information

LOGGER_password

Description: this parameter can set a user password string that can be used in every JSON object frame that goes to the end server.

Possible values:

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

Additional notes:

  • Please use the account support line at iotsupport@mtxm2m.com for further information

LOGGER_server

Description: This parameter sets the server’s URL datalogger and sends its saved data using a JSON object character.

Possible values:

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

Additional notes:

  • URL example:
    www.midominio.com/set.asp?V=
    V is the variable used to send JSON information to the server
  • Please use the technical support line at iotsupport@mtxm2m.com for further information

LOGGER_registerSize

Description: This parameter sets the register size of the non volatile Flash internal datalogger for JSON objects. E.g. If using a remote Wavetherm temperature sensor, the reading will be stored in the memory in a JSON format:

{“IMEI”:357973041110401,”TS”:”18/10/12 10:04:37”,”P”:”matrix”,”A”:0B19083000D3,”BAT”:0,”T1”:23.4375,”T2”:0.0 }

The parameter value should be at least the maximum frame length that a JSON frame has.

In the above example it would be be 110. If you do not know what it could be, use 300 as the value.

Possible values:

  • 10… 1024
  • Default value: 100

Additional notes:

  • Please use the technical support line at iotsupport@mtxm2m.com for further information

LOGGER_numRegistersFlash

Description: This parameter allows you to specify the maximum number of records that the MTX-Tunnel can store in its internal flash memory.

Possible values:

  • 1… 10000
  • Default value: 1500

Additional notes:

  • Remember that the flash memory is used in cases where the MTX-Tunnel doesn’t have, at a given moment, 2G/3G/4G connectivity for the broadcasting of information. This memory is used to ensure records are not lost. When 2G/3G/4G connectivity is back those records will be sent again via GPRS.
  • It is recommended that the data file (data.txt that will be automatically created inside the modem) doesn’t occupy more than 1MByte. Remember that the size of the file is calculated by multiplying LOGGER_numRegistersFlas x Logger_registerSize.

LOGGER_ioPeriod

Description: Period time datalogger takes readings from digital and analog inputs, stores them to memory and afterwards, they are sent to server using a JSON object.

Possible values:

  • 0 (disabled), 30… 2592000
  • Default value: 0

Additional notes:

  • See this or this scenario examples for more information. Please use the technical support line at iotsupport@mtxm2m.com for any further questions

LOGGER_serverLogin

Description: This parameter allows you to specify the login (user name) that the MTX-Tunnel must use to send data to a Web platform that has an authentication system of Login and Password.

Possible values:

  • String of up to 64 characters
  • Default value: none

Additional notes:

  • If your web platform does not use a simple authentication system based on Login and Password then it is not necessary to include this parameter in the set up file. Its use is only compulsory in web platforms that use authentication mechanisms
  • This parameter is available from version MTX-Tunnel 7.27

LOGGER_serverPassword

Description: It allows you to specify the password to be used by the MTX-Tunnel to send data to a Web Platform with an authentication system of Login and Password.

Possible values:

  • String of up to 64 characters
  • Default value: none

Additional notes:

  • If your web platform does not have a simple authentication system of Login and Password, then it is not necessary to include this parameter in the setting file. It is only compulsory for web platforms with authentication systems

LOGGER_serialFrequency

Description: This allows you to establish the frequency with which the internal logger must register the received serial data.

Possible values:

  • 0… 1000 (seconds)
  • Default value: 0

Additional notes:

  • This configuration parameter is valid in versions from MTX-Tunnel 8.10
  • A value of 0 means that no data is registered in the modem’s serial port.
  • A value of 1 means all received data is registered in the serial port.
  • A value of 6 means 1 in every 6 data strings is registered. This is useful in situations such as with a temperature sensor that automatically sends data (without the option to change this), and we need to change the frequency.
  • The data should be sent consecutive, without pauses. The maximum size is 256 bytes.

LOGGER_serialData1… LOGGER_serialData10

Description: this allows you to configure up to 10 data strings to be sent by the modem; i.e. every X seconds (configured in the LOGGER_serialPeriod parameter), MTX will send this data via serial ports, logging the responses to send them to a platform at a later time.

Possible values:

  • A5B78912… FE80916F (string in hexadecimal)
  • Default value: none

Additional notes:

  • This configuration parameter is valid in versions from MTX-Tunnel 8.10
  • The strings must be in hexadecimal format
  • Data is sent according to the period indicated in the LOGGER_serialPeriod parameter. The minimum pause between each of the 10 strings being sent is 2 seconds
  • The response from the device connected to the serial port can’t be more than 256 bytes

LOGGER_serialPeriod

Description: this specifies how often the modem will send data contained in the LOGGER_serialData1 … LOGGER_serialData10 parameters.

Possible values:

  • 0 (disabled), 30… 2592000
  • Default value: 0

Additional notes:

  • This configuration parameter is valid in versions from MTX-Tunnel 8.10 Please consult the examples for a clearer understanding of this parameter. If you require additional help, contact iotsupport@mtxm2m.com.

LOGGER_https

Description: Allows to state if information is sent via http or via https in encrypted format.

Possible values:

  • on, off
  • Default value: off

Additional notes:

  • Keep in mind that if you want to activate this option, you will need a web server with SSL support

LOGGER_httpMode

Description: Allows to choose the type of communication to be used with a Web Platform. It is possible to choose between “getjson” and “postjson.”

Possible values:

  • getjson, postjson
  • Default value: getjson

Additional notes:

  • Here are some examples of the format of data sent both by means of getjson and postjson methods. Remember that data frames sent by Logger can be very diverse, because Logger is engaged in different internal processes of MTX-Tunnel. The following examples show Logger frames where the I/O of MTX-Tunnel are sent every certain period of time (LOGGER_ioPeriod >0). They belong to ‘IOS” type, but it is possible to receive the following types: “IOS”, “SERIAL”, “TEMP”, “WMBUS”, WAVT”, “WAVSC”, “WAVSV”, “WAVF”, “WAVL”, “POWER”, “MBUS”
  • Example of “getjson” mode:
{“TYPE”:”IOS”,”IMEI”:357042060366409, “P”:”ID00001”, “TS”:”09/08/16 18:32:53”,”IO1” :0,”IO2”:0,”IO3”:0,”IO4”:0, “IO5”:0,”IO6”:0,”IO7”:0,”IO8”:0,”IO9”:0,”IO10”:0,”AD1”:0,”AD2”:0, “CO1”:”0”,”CO2”:”0”}

Where:
TYPE: IOS frame type
IMEI: MTX internal indentification
P: user’s field in LOGGER_password parameter
TS: TimeStamp of when data are collected
IO1: Value of digital input/output 1 of the modem (if it is available)
IO2: Value of digital input/output 2 of the modem (if it is available)
IO3: Value of digital input/output 3 of the modem (if it is available)
IO4: Value of digital input/output 4 of the modem (if it is available)
IO5: Value of digital input/output 5 of the modem (if it is available)
IO6: Value of digital input/output 6 of the modem (if it is available)
IO7: Value of digital input/output 7 of the modem (if it is available)
IO8: Value of digital input/output 8 of the modem (if it is available)
IO9: Value of digital input/output 9 of the modem (if it is available)
IO10: Value of digital input/output 10 of the modem (if it is available)
AD1: Value of analog input 1 of the modem (if it is available)
AD2: Value of analog input 2 of the modem (if it is available)
CO1: Value of pulse counter input 1 (if it is available)
CO2: Value of pulse counter input 2 (if it is available)

  • Example of “postjson” mode:
{“IMEI”:357042060366409,”TS”:”09/08/16 18:32:53”,”TYPE”:”IOS”,”IO1”:0,”IO2”:0,”IO3”:0,”IO4”:0,”IO5”:0,”IO6”:0,”IO7”:0,”IO8”:0,”IO9”:0,”IO10”:0,”AD1”:0,”AD2”:0,”CO1”:”0”,”CO3”:”0”}

TYPE: IOS frame type
IMEI: MTX internal indentification
P: user’s field in LOGGER_password parameter
TS: TimeStamp of when data are collected
IO1: Value of digital input/output 1 of the modem (if it is available)
IO2: Value of digital input/output 2 of the modem (if it is available)
IO3: Value of digital input/output 3 of the modem (if it is available)
IO4: Value of digital input/output 4 of the modem (if it is available)
IO5: Value of digital input/output 5 of the modem (if it is available)
IO6: Value of digital input/output 6 of the modem (if it is available)
IO7: Value of digital input/output 7 of the modem (if it is available)
IO8: Value of digital input/output 8 of the modem (if it is available)
IO9: Value of digital input/output 9 of the modem (if it is available)
IO10: Value of digital input/output 10 of the modem (if it is available)
AD1: Value of analog input 1 of the modem (if it is available)
AD2: Value of analog input 2 of the modem (if it is available)
CO1: Value of pulse counter input 1 (if it is available)
CO3: Value of pulse counter input 3 (if it is available)

LOGGER_header1, LOGGER_header2, LOGGER_header3

Description: allows to use personalized HTTP headers. Very useful for the communication between MTXTunnel and third-party web platforms (like THINGWORKS).

Possible values:

  • Cadena ascii hasta 64 caracteres
  • Default value: none

Additional notes:

  • The headers format is the following: nameHeader;valueHeader . That is to say, fields are separated by ; (semicolon)
  • You will find them necessary if you want your MTX-Tunnel to communicate with some generic platforms. For example, to communicate with Thingworks platform you will have to specify something similar to:
    LOGGER_header1: Content-Type;application/json
    LOGGER_header2: Accept;application/json
    LOGGER_header3: appKey;194f5476-7346-4638-ac30-bbca28595be1

LOGGER_mode

Description: It allows to select the mechanism of data sending registered in the internal datalogger.

Possible values:

  • http, mqtt, ftp
  • Default value: http

Additional notes:

  • If you select “mqtt”, remember to use the MQTT_ parameters indicated in this manual
  • If you specify “mqtt”, you must also configure the LOGGER_mqttTopic parameter
  • If you select “FTP,” you also need to specify the FTP server address, username and password in the following parameters respectively: LOGGER_server, LOGGER_serverLogin, and LOGGER_serverPassword

LOGGER_mqttTopic

Description: Configure the topic that MTX-Tunnel will use to publish all data stored in the Logger.

Possible values:

  • String up to 64 characters
  • Default value: none

Additional notes:

  • In the same way as the MQTT_attopicX parameters, you can use the [IMEI] tag in the parameter and the MTX-Tunnel will internally replace that tag with the appropriate value. For example, if your modem has the IMEI 354740050182909 you could specify in the config.txt configuration file the value:
    LOGGER_mqttTopic: [IMEI]/LOGGER
    And the MTX-Tunnel would send logger data using the topic::
    354740050182909/LOGGER

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.