Tunnel – Output Configuration parameters: “OUTPUT_”

Looking for something else?

All models of MTX modems have outputs, be it digital or via relays. By using OUTPUT_ parameters you will be able to control them easily. For example, you will be able to switch a relay following a programmed schedule, in function of the value of an analog input, in function of the reading of a record from a modbus device etc.

Also, OUTPUT_ parameters allow you, indirectly, to program some alarms via SMS. For example, you will be able to request an SMS message to be sent when the value of an analog input or the value of a MODBUS record is higher or lower than a certain value.

These configuration parameters OUTPUT_ are available from version MTX-Tunnel v7.21.

OUTPUT_mode1, OUTPUT_mode2, OUTPUT_mode3, OUTPUT_mode4

Description: MTX-Tunnel allows you to set up to four outputs for an MTX device. Not all MTX modems have the same number of outputs.

Possible values:

  • manual, on, off, time, analog, modbus, call, astronomical, socket
  • Default value: manual

Additional notes:

  • Description of all possible values:
    • manual: is the behaviour that the outputs from MTX devices had until version MTX-Tunnel v7.20. Using the “manual” mode you can change the status of a digital output/relay via an SMS, via webserver or Telnet.
    • on: specifying an output to “on” mode, this will be permanently activated (for example, a permanently switched relay).
    • off: specifying an output to “off” mode, this will be permanently de-activated (for example, a permanently no switched relay).
    • time: specifying an output to “time” mode, you will be able to specify an activation/ de-activation schedule for a digital output/relay.
    • analog: specifying an output to “analog” mode, you will be able to specify a maximum and a minimum value for an analog input from which a digital output/relay must be activated. Also, among other uses, you will be able to send an alarm SMS message when the value read is higher or lower than a specific analog value.
    • modbus: specifying an output to “modbus” mode, you will be able to specify the maximum and minimum values of the record from a modbus device from which a digital output/relay must be activated. Also, among other uses, you will be able to send an alarm SMS message when the value read is higher or lower than a specific modbus record.
    • call: specifying an output to “call” mode, you will be able to activate for 2 seconds a certain digital output/relay when there is a digital call from a phone number (very useful for scenarios like automatic door opening, creating resets to external devices…).
    • astronomical: specifying an output to “astronomical” mode, you will be able to activate/deactivate a specific digital output/relay depending on the Sun. The MTX-Tunnel, given the GPS position with the parameters MTX_latitude and MTX_longitude, can calculate for any point on the Earth and for every day, the sunrise and sunset times. It is possible to activate an MTX output at sunrise/sunset and even assign a configurable differential for these times.
    • socket: specifying an output to “socket” mode, you will be able to activate/de-activate a specific digital output/relay depending on socket status (connected / disconnected). Timer: This allows the command AT^MTXTUNNEL=SETOUTPUTTIMER to be used. This command allows a relay to be changed for a few seconds by a single AT command, be it sent via SMS, Telnet, etc.
    • Bitcoin: this allows a digital output or relay to be activated according to whether a transfer is made into an account using Bitcoin.

OUTPUT_config1, OUTPUT_config2, OUTPUT_config3, OUTPUT_config4

Description: By entering these parameters you can configure the behaviour of up to 4 outputs of an MTX modem. It is a complex parameter.

The structure of an OUTPUT_configX parameter depends on the mode specified in OUTPUT_modeX; that is, the configuration of OUTPUT_configX will be different if you are configuring an output that depends on the status of an analog value (OUTPUT_modeX: analog) or one depending on a modbus record (OUTPUT_modeX: modbus), etc.

Possible values:

  • Default values.: none

 

  •  If the value specified in OUTPUT_modeX is “manual”, “on”, “off” or “call” this OUTPUT_configX parameter is useless, as it does not make sense. Its use is compulsory if values like “time”, “analog” or “modbus” are specified in OUTPUT_modeX
  • If the value specified in OUTPUT_modeX is “time”, the parameter OUTPUT_configX must have the following structure:
    HH;MM;HH;MM
    This indicates the time (hour and minutes) of the digital output/relay activation and deactivation. For example, if you want to activate output 3 at 20.30 pm and deactivate it at 07.15 am, the value of the parameter in the set up file “config.txt” should be: OUTPUT_config3: 20;30;07;15
  • If the value specified in OUTPUT_modeX is “analog”, the parameter OUTPUT_configX must have the following structure:
    ID;ValueMax;ValueMin;ATCommandMax;ATCommandMin
    Where:
    ID: 0… 1 (can have the values 0 or 1, 0 if you want to read the dac0 value or 1 if you want to read the dac1)
    ValueMax: 0… 2400 (is the maximum value of the digital analog converter (dac) from which the digital output/relay must be activated)
    ValueMin: 0… 2400 (is the minimum value of the digital analog converter (dac) from which the digital output/relay must be deactivated)
    ATCommandMax: AT command to be executed (MTX-Tunnel allows you to execute an optional AT command when the dac value is equal to or higher than the indicated in ValueMax)
    ATCommandMin: AT command to be executed (MTX-Tunnel allows you to execute an optional AT command when the dac value is equal to or lower than the indicated in ValueMin)
    For example, if you want to activate the output3 relay when the value read by the digital analog converter “0” is higher than 2000 and deactivate it when it is lower than 1800, and you do not want to execute an AT command, the value to specify in the parameter would be:
    OUTPUT_config3: 0,2000;1800;;
  • If the value specified in OUTPUT_modeX is “modbus”, the parameter OUTPUT_configX must have the following structure:
    dir;command;record;valueMax;valueMin;ATCommandMax;ATCommandMin
    Where:
    dir: 1… 254 (indicates the modbus address of the device to be read)
    command: 3, 4 (allows you to specify if the modbus command is 3 or 4)
    record: 1…65535 (allows you to specify the number of modbus record to be read)
    ValueMax: 0… 65535 (is the maximum value of the modbus record from which the digital output/relay must be activated)
    ValueMin: 0… 65535 (is the minimum value of the modbus record from which the digital output/relay must be deactivated)
    ATCommandMax: AT command to execute (MTX-Tunnel allows you to execute an optional AT command when the value of the modbus records is equal to or higher than the value indicated in ValueMax)
    ATCommandMin: AT command to execute (MTX-Tunnel allows you to execute an optional AT command when the value of the modbus records is equal to or lower than the value indicated in ValueMin)
    For example, if you intend for the output 3 relay on MTX-IND to be activated when the value of record number100 of the modbus address 7 (whose modbus read command is 3) is equal to or higher than 2000 and to deactivate it when it is equal to or lower than 1800, and to also send an SMS alarm message ( “alarma mtx”) when the value is equal to or lower than 1800, then the value to specify in the parameter would be:
    OUTPUT_config3: 100;7;3;100;2000;1800;;AT^MTXTUNNEL=SMS,666123456,alarma mtx
  • If the specified value in OUTPUT_modeX is “call”, the parameter OUTPUT_configX must not be included in the set up file.
  • If the specified value in OUTPUT_modeX is “astronomical”, the parameterOUTPUT_configX must have the following structure:
    minutesSunset, minutesSunrise
    Where:
    minutesSunrise: -120… 120 (allows you to indicate a time offset so the output/relay is deactivated X minutes before or after the sunrise)
    minutesSunset: -120… 120 (allows you to indicate a time offset so the output/relay is activated X minutes before or after the sunset.
  • If the value specified in OUTPUT_modeX is “bitcoin”, the OUTPUT_configX parameter must have the following structure:
    pagoMinimo, tiempoPagoMinimo, tiempoProporcionalPago, tiempoMaximo
    Where:
    pagoMinimo: 0.001… 1.000 (Allows to indicate the minimum payment in Bitcoins to activate the relay)
    tiempoPagoMinimo: 1… 86400 (It indicates the time (in seconds) that a digital output / relay must remain activated when the minimum payment is received)
    tiempoProporcionalPago: 0 (no), 1 (yes) (Allows to indicate if we allow the time to be proportional to the payment. That is, if, for example, a payment of twice the minimum payment is made, the activation time is also double)
    tiempoMáximo: 1… 86400 (Allows to indicate the maximum time that the digital output/relay can be activated regardless of the payment received)

Additional notes:

  • It is a complex parameter, we recommend you check the examples in Annex 8 to understand it better
  • Please note that you can add the possibility of executing AT commands, as well as activating/ deactivating a digital output or relay. This will allow you, for example, to send an SMS text message to change the record of a modbus device, etc. when reading a certain analog value or modbus record
  • The outputs update period is 15 seconds. That is, every 15 seconds the MTX-Tunnel checks the time, reads the a/d converters, reads the modbus records and activates/deactivates the corresponding outputs
  • Remember that the MTX-Tunnel is using UTC. That means that when specifying a schedule for the digital outputs/relays, you must specify the corresponding UTC time

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.