Frequent problems of DEXGate2

In the Modbus log appears the error: MODBUS EXCEPTION

In this case, if it is a device already integrated in the DEXGate2 check:

• That the Modbus configuration configured on DEXGate2 is the same for all devices connected to it. Check the speed, parity, data bit and stop bit data that are configured in the DEXGate2, they must be the same as those that are configured in the devices:

#baud:   9600, 19200, 57600, 115200, etc

bridge.speed=9600

#parity: "even", "odd" or "none"

bridge.parity=even

#data_bits: 5, 6, 7, 8

bridge.data_bit=8

#stop_bits: 1, 2

bridge.stop_bit=1

• That the slave address of the device is correct. Each device on the same bus must have a unique slave address, it cannot be repeated. If there is more than one device of the same model, the addresses must be separated by a comma, for example:

devices.circutor-cvm-mini = 1,2,3

• Check the bus cable, that there is no interference or that the cable is damaged, if you have another cable at hand, try another cable. Depending on which devices are on the bus, it is necessary to connect a resistor at the end of the bus. (see article DEXGate2 RS485 cable)
• If it is a custom device that we have configured in the DEXGate2, we may not have correctly configured the register where the DEXGate2 has to ask and that is why it gives an error, check the Modbus register map of the device.

In the Modbus log the error appears that the DEXGate2 cannot publish the data on the server: IOException

The DEXGate2 has successfully read all the devices, but cannot publish the data.

There is a firewall in the building network

If there is a firewall, check the connection requirements of the DEXGate2, that the ports are open so that the DEXGate2 publish the data:

DEXGate2 will need an IP address. This IP address can be obtained using DHCP or statically configured.
DEXGate2 only uses outgoing connections, so if you don't have a firewall and use NAT it will work out of the box. It uses the following ports:

• Basic:
  • Sending data to the server: TCP port 80 to is3.dexcell.com
  • Sending data to the server: TCP port 443 to is3.dexcell.com
  • Using internet to sync time: UDP port 123 to various servers
• Optional:
  • Remote control of the device: UDP port 1196 to remote.dexcell.com

Memory is full

The DEXGate2 can store data in its memory, so if it cannot publish, it will save the readings in the DEXGate2 memory creating files we call “queues”. When DEXGate 2 manages to publish the data read at that moment, then it will start to publish all the data stored in the "queues".

If it has been a long time (months) without being able to publish the data, the DEXGate2 may have saturated memory and cannot publish, then the following should be done:

• You will have to physically go to where the DEXGate2 is located
• Download the WINSCP program
• Connect using a laptop to DEXGates2's Wifi:
  • Wi-Fi name: DEXGATE2_MAC
  • Wifi password: MAC of DEXGate2 with capital letters
• Open the WINSCP program and enter the following data:

Connection type: SCP

IP: 172.16.0.1

Port: 22

User: root

Password: dexcell

• On the right side you will have your computer, on the left the DEXGate2 folders
• Go to the var / staticqueues folder
• Select all the files and transfer them to your computer.
• Open a browser and put the DEXGate2 IP 172.16.0.1
• Enter the configuration interface (by default admin / admin)
• Go to Modbus-> Configuration
• Select "Save and reboot" (green button)
• Go to the Modbus logs and see if data is being inserted
• If they are being inserted, return to the WINSCP program and transfer the files from the queues (not all at the same time), first try 5 at 5, then 10 at 10 and go up depending on the response of DEXGate2.

A file in the queue is corrupt.

Sometimes it happens that a corrupted file is created which makes the DEXGate2 unable to publish and files accumulate in the queue.

To do this, follow the steps in the previous point but DO NOT put the first and second files in the queues back into DEXGate2 (one of them will be corrupt)

I have forgotten the password to access the DEXGate2 configuration interface.

If we have forgotten the password to access the DEXGate2 configuration interface or we do not know which it is, follow these steps to return to the "default" password, which is admin.

• Download the WINSCP program
• Connect to the DEXGate2 Wi-Fi:
  • Wi-Fi name is DEXGATE2_MAC
  • Wifi password: MAC of the DEXGate2 (00D0XXXX), the letters in capital letters.
• Open the WINSCP program and enter the following data:
  Connection type: SCP
  IP: 172.16.0.1
  Port: 22
  User: root
  Password: dexcell
• On the right you will have the folders of your computer and on the left the folders of the DEXGate2.
• In DEXGate2 go to the following folder: / opt / sysadmin / config, there you will find a file called "password.txt"
• Enter to edit the file "password.txt"
• Delete all the content and insert the following line: admin:d033e22ae348aeb5660fc2140aec35850c4da997
• Disconnect and reconnect the DEXGate2 to power
• When the DEXGate2 Wifi reappears, reconnect.
• Open the browser and put the IP 172.16.0.1 and try to enter the DEXGate2 configuration interface with the user admin and the password admin

I want to extend or reduce the time that the DEXGate2 takes to ask the devices (polling interval).

By default, the DEXGate2 is programmed to ask connected devices every 15 minutes. We can reduce or extend this time. To do this, follow the following steps:

In the Modbus configuration within the DEXGate2 configuration interface, add the line:

bridge.scheduled-polling-interval = n, where n are the minutes that you want to pass between one sending and another.
Set the minutes you want and reboot the Modbus, clicking on the green button "Save and restart".

How to access DEXGate2 via SSH