Titan – AN40: Gateway LoRa-4G with sensor data sending

Looking for something else?

Scenario Details

This application note shows, step by step, how to carry out a scenario in which data sent by LoRa sensors, using a Titan router such as Gateway LoRa-2G / 3G / 4G, to a data collection and management platform such as Cervello, which will also act as Device Manager for the Titan router.

Description of the Example

It is necessary to install a network of dozens of LoRa sensors distributed in a wide area of ​​cultivation of 10 km radius. Digital input sensors are needed to monitor the opening of doors and hatches, as well as 0-10V and 4-20mA analog input sensors to monitor parameters such as humidity, temperatures, well levels, etc.

The sensors will not have external power, so they must have an internal battery and the autonomy of this must last several years. In order to save energy, digital and analog sensors must be able to be configured to send their reading data in two ways to a Management Platform, from where all the data received from the sensors must be managed and visualized as well as reports generated, alerts, etc.

The two reasons that will cause a LoRa sensor to send data should be:

  1. When an event occurs (such as a change in a digital input or a threshold exceeded in an analog input)
  2. For security, you must send your status every 12 hours

Due to the requirements of this scenario, the resolution approach is raised with the following devices / services:

LORA SENSORS:
ARF8170BA LoRa sensor with 4 digital inputs
ARF8190BA LoRa sensor with 2 configurable 4-20mA or 0-10V analog inputs

These battery-powered LoRa sensors allow the previously indicated sending configuration, that is, sending their data in the event of an event and / or periodically.

GATEWAY LORA:

MTX-Router-Titan-4G-LoRa, Gateway LoRa Capable 4G Router

This 4G router has the LoRa-IP Gateway capability (where IP communications can be routed through Ethernet, Wifi or 2g / 3g / 4g). In the case of the present example, the routing by 2g / 3g / 4g will be chosen. That is, this Titan router will collect the LoRa data emitted by the sensors in its range of action and will forward them to the LoRa server in TTN.

This Titan router also allows to be managed remotely in multiple ways (SMS, IP, Openvpn, Modbus TCP or, the most comfortable, from the Cervello Platform).

SERVER LORA:

TTN: The Things Network, a platform that will carry out the LoRa Server mission to manage the Device Network. It will be the part that is in charge of collecting the data from the sensors relayed by the Titan router.

DEVICE MANAGER PLATFORM AND SENSOR DATA TREATMENT:

Cervello: The Cervello platform manages the reception of sensor data from the TTN server. In other words, Cervello connects to TTN and, via MQTT, receives all the data from the LoRa sensors, storing them in its Database. In addition, it provides the visualization of the sensor data through gauges, allows the generation of the pertinent reports, generates alarms (SMS, emails, etc.) based on the data received from the sensors, etc.

It also performs the function of Device Manager of the Titan routers, allowing their remote management.

The following shows how to configure the different elements of the described scenario.

Configuration of Titan router as LoRa-2G/3G/4G Gateway

The first thing to do on the Titan router is to configure 2g / 3g / 4g connectivity. For this, you must enter the Titan router configuration through its default IP address 192.168.1.2 and user / password admin / admin.

To configure the Internet access of the TITAN router via SIM card, you must access the router\’s configuration menu WAN > Basic Settings

Once in this configuration screen, enter the parameters Sim PIN of the SIM card (if you have the PIN), and the APN, Username and Password of the operator used. Once this is done press the SAVE CONFIG button. Finally, restart the router (Other > Reboot menu) so that the Titan router starts up with the new settings and proceeds to connect to the Internet.

Once connected to the Internet, access the configuration menu “Other > LoRa Gateway” and enter the configuration as indicated below, specifying the Latitude / Longitude of where the Gateway will be located and selecting the “Gateway Lora – Packet Forwader” mode) .

Then enter a unique ID for the Gateway with 8 hexadecimal characters (in the example 010203040A0B0C0D). Where it indicates server address, enter router.eu.thethings.network (if your router will not be in Europe, search TTN for the most appropriate DNS). Finally complete the rest of the parameters as shown in the next screen. Once this screen is configured, save the changes and restart the Titan router.

Gateway Registration Configuration in TTN

This section assumes that the user has registered at www.thethingsnetwork.org. Once registered, the console section must be accessed: console.thethingsnetwork.org Once inside the console, the “Gateways” option must be selected. This will configure the TTN service to accept the connection from the Titan router as a LoRa Gateway.

Once inside Gateway, click on register gateway and proceed to enter the Titan router parameters. In the Gateway EUI box, enter the Gateway ID that was entered during the Titan router configuration process (in the example, 010203040A0B0C0D). A description must also be entered as well as the working frequency (Europe = 868MHz).

After completing the Gateway registration process (Titan router), after a few seconds the Gateway should appear as “Connected” as shown in the following figure. At this point the Gateway (Titan router) is already correctly connected with the TTN platform).

Setting Up an Application in TTN

In order to register the different LoRa sensors, an application must be created in TTN. To do this, in the console, you must go to the Applications menu. Once there, click on the link Create application.

Complete the Application ID fields (with a unique identifier of your choice), a description and the most appropriate handler.
The next screen shows the data to be completed.

Once the Application is created, it must be noted that: the Application EUI (as it must be specified in the sensors configuration to indicate which application to send the data to) and the Access Key of the application (as it will be necessary to communicate the Cervello platform with TTN).

LoRa Sensors Registration in TTN Application

In the same screen above, click on “register device” to register the different LoRa sensors in the newly created application.

For each sensor, enter a “Device ID” and the “Device EUI”. This last parameter is an identifying number that is printed on the attached label of each sensor.

Once the sensor is created, the APP Key must be noted, as it will also need to be entered in the sensor configuration.

LoRa Sensors Configuration

The most convenient way to configure Adeunis LoRa sensors is to use the Adeunis PC configuration application “IOT CONFIGURATOR”. Simply connect the LoRa sensor via a USB cable to access its configuration by pressing the CONNECT button. You will find the microUSB connector of the LoRa sensor by opening the sensor from its bottom.

Once inside the configuration there are two sections to configure. On the one hand Applicative Configuration, where the behavior of the sensor will be indicated, and on the other hand Network Configuration, with the network configuration. In “Applicative Configuration” several menus to configure will be displayed.

In Global Configurations you must specify Production, in Transmission periods you must specify how many seconds the sensor should transmit its data periodically. If you want them to send their status every 12 hours, you must specify 12×60 / 20 = 72.

In the Channel X configuration menus, the behavior of the analog and digital channels must be configured, depending on the type of sensor. That is, it sends analog measurements when they exceed a certain threshold, or when a digital sensor changes state, according to needs.

Then the Network configuration section must be configured. The activation mode OTAA must be specified in the General section. In the OTAA section, the “Application EUI” that was noted during the creation of the Application in TTN (section 4 of this application note) as well as the parameter “LORA_APP_KEY” generated in section 5 of this note must be specified. Note that LORA_APP_KEY is different for each registered sensor.

From this point on it is already possible to obtain data from the sensors configured in TTN each time any of them emit data.

Receiving Data from LoRa Sensors on the Cervello Platform

To receive the data from the LoRa Sensors in Cervello, it is only necessary to create a VPI and add 2 components to it. An “MQTT broker” component, which will be configured to connect with the TTN MQTT broker, and an “MQTT subscribe” component, used to subscribe to the appropriate TTN topic that will receive the data from the LoRa sensors associated with the application. created.

The configuration of the Broker MQTT component will be as follows:

In “hostname” you must enter the broker indicated in TTN (in Europe “eu.thethings.network”). In Port the port 1883 will be indicated. In the parameter Client ID a unique identifier for the MQTT client that is being configured must be indicated, and in password the Access KEY that was noted at the end of the point 4 of this application note.

Finally, the component “MQTT subscribe” must be configured as described in the previous figure. In “Select a broker”, the name of the “MQTT broker” component that has just been created must be chosen. In Topic you must enter the topic specified in TTN for receiving data from LoRa sensors, which is generically: + / devices (+ / up. You must also click on the Enable Console Debug checkbox, since in this way it will be possible to visualize the frames received from the LoRa sensors in the debug section.

If everything has been configured correctly, “Connected” should be displayed on both components.

The right section of the screen is where the debug is located. When devices transmit data, they should be shown in that section as shown in the following figure.

Note that when receiving data from a sensor a field of the received JSON object has the name payload_raw. This parameter contains the data (payload) sent by the sensor. In the case of the example, it shows the data of an analog sensor ARF8190BA. This data is configured in Base64, which can be easily decoded. Following this example, the QiARAAAAIQAAAA == data is decoded from Base64 as:

42 20 11 00 00 00 21 00 00 00

The values ​​indicated in red being the value of the 2 analog inputs of the sensor as specified in the Adeunis ARF8190BA sensor manual.

For any questions, contact us at iotsupport@mtxm2m.com.

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.