Modbus Data error

[fischerp]

Hello,
Hello,
After using an older version of RapidScada for some time, I have switched to 6.2.0.3. I was able to connect a first device (inverter for PV / Modbus) without any problems. A second device (temperature recording module / Modbus) is causing problems. The module has 4 channels (input register address 400-403 16bit integer and at the same time address 450-453 32bit input register floating point), and can be read out with a Modbus Master Simulator (Radzio) without any problems. In Rapid Scada I get errors when I click on the entry under Communication Line – Modbusline.
The four channels are entered twice in the template, 400-403 Input register short (2byte) and (as a separate element group) 450-453 Input register int(4byte). that should actually fit.
The device is created with a valid name, Device Type Modbus Numeric Address 1 String address 192.168.2.48 (this is the correct IP address of the device).

Here is an excerpt from the EventLog, maybe that will help:

Request element group “Inverter”
Send (12): 6A 8E 00 00 00 06 01 03 9C 87 00 20
Receive (7/7): 6A 8E 00 00 00 00 43 01
Receive (66/66): 03 40 28 BE 0D 94 0D 93 0D 98 FF FD 0F FE 10 06 10 11 09 2E 09 46 09 4F FF FF 60 84 FF FF 13 8A FF FE 60 85 FF FF E8 91 FF FD 03 E8 FF FF 4C 76 42 05 FF FD FF FF 80 00 FF FF 80 00 64 B6 FF FF 01 F2
OK

2024-11-27 16:33:49 Session with the device [2] Temperaturmodul1
Request element group "TemperaturModul"
Send (12): 9F C4 00 00 00 06 01 04 01 8E 00 05
Receive (7/7): 9F C4 00 00 00 03 01
Receive (2/2): 84 02
Error received from device: [02] ILLEGAL DATA ADDRESS

Inverter is the first device that works without problems (Holding registers)
Temperature module1 is the second module that I wanted to integrate as described
This is what I see, if I have a look on the communication line

[2] Temperaturmodul1
--------------------
Driver       : DrvModbus 6.0.0.4
Status       : Error
Session time : 27/11/2024 17:02:45
Command time : Undefined

Sessions (total / errors) : 14989 / 14989
Commands (total / errors) : 0 / 0
Requests (total / errors) : 44967 / 44967

Current Data
+----+------+------+-------+---------+
| #  | Code | Name | Value | Channel |
+----+------+------+-------+---------+
| ******** TemperaturModul ********* |
+----+------+------+-------+---------+
| 1  | 399  | 399  |   --- |     301 |
+----+------+------+-------+---------+
| 2  | 400  | 400  |   --- |     302 |
+----+------+------+-------+---------+
| 3  | 401  | 401  |   --- |     303 |
+----+------+------+-------+---------+
| 4  | 402  | 402  |   --- |     304 |
+----+------+------+-------+---------+
| 5  | 403  | 403  |   --- |     305 |
+----+------+------+-------+---------+
| ******** Temperatur 32bit ******** |
+----+------+------+-------+---------+
| 6  | 449  | 449  |   --- |     306 |
+----+------+------+-------+---------+
| 7  | 450  | 450  |   --- |     307 |
+----+------+------+-------+---------+
| 8  | 451  | 451  |   --- |     308 |
+----+------+------+-------+---------+
| 9  | 452  | 452  |   --- |     309 |
+----+------+------+-------+---------+
| 10 | 453  | 453  |   --- |     310 |
+----+------+------+-------+---------+

If you need any further information I will be happy to post more log files, screenshots or whatever.

Thanks in advance

• This topic was modified 5 days, 11 hours ago by Mikhail.

[manjey73]

Do you have both devices on the same line?
How are your devices connected? are they both with Ethernet?

[fischerp]

Hello,
I hope I understand your question correctly.
the structure looks like this:
Communicator – Communication Lines – Modbus Line.
Under ModbusLine there are two entries, “Wechselrichter” and “Temperaturmodul”.
Or do you mean the structure of Devices?
There are two entries:
Number 1 Device Type Modbus Numeric Address 1 IP 192.168.2.49 CommLine ModbusLine
Number 2 Device Type Modbus Numeric Address 1 IP 192.168.2.48 CommLine ModbusLine

I don’t know what the Numeric Address is all about. Can it be the same? Does it have to be mentioned elsewhere?

Both devices are Modbus TCP devices that are in the same network segment behind the same router. Currently connected, port 502, IP address as mentioned above.

I can access them with the settings I made in Rapid Scada (with the ModbusMasterSimulator)

I’ll send screenshots if that helps. Can I upload them directly here in the forum if necessary?

[fischerp]

I have just seen that something is missing in my presentation of the devices:
Number 1 is the name “Wechselrichter”
Number 2 is the name “Temperaturmodul”

[manjey73]

You have different IP addresses, why don’t you create different communication lines?
Show the settings of the communication line itself in the Communicator

[Mikhail]

Hello,

If you have communication logs from the previous version, compare the Modbus packets with the new version using https://rapidscada.net/modbus/

[Mikhail]

Note that ILLEGAL DATA ADDRESS is the answer of your device.

[fischerp]

I have now created a second communications line (Modbus2). I have specified this new line as the communications line in the device.
I have synchronized in the Communicater and received an entry for the new line with the associated device.
The error remains the same.
Apart from the IP address and the registers to be queried, the settings are identical.
The computer on which the previous version was running is defective, so I no longer have access to the old log files and the old settings.
“Note that ILLEGAL DATA ADDRESS is the answer of your device.”
I can use the settings: Input registers Address 400 (401,402,403) Integer I can read the content of the 4 registers in the ModbusMasterSimulator. The setting in Rapid Scada should be the same: Input Registers short (2byte) Address 400 (401,402,403)
These 4 registers are clearly available. Do I have to specify 30400 (30401,30402,30403) for Input Register (FC04) in Rapid Scada? The manual of the connected hardware clearly states 0x190 and the following 3 > read, 16bit integer.
I don’t know where else I could look.

[manjey73]

Check that you do not need to arrive at address 1. Address settings start from 0 or start from 1. Disable all registers except the first one.
Make sure that you need the name Input Registers and not Holding Registers

If the device is responding, it means there is some kind of error in choosing the address or other registers are needed.

[Mikhail]

Use the Modbus parser to validate your requests.

[fischerp]

After following your suggestion and playing around with a value and changing the zero-dased and one-based setting, I get valid values for this one register. The others should no longer be a problem. This seems to have solved the problem for me.
Thank you very much

[fischerp]

Now I have a small problem, but it’s more of a blemish. While in the USA the comma is used as the 1000 separator, in Europe it is the period. So I would like to swap the point and comma in the display. Is there a setting for this somewhere?

[JurasskPark]

Control panel – Regional parameters – Additional parameters

[Mikhail]

While in the USA the comma is used as the 1000 separator, in Europe it is the period.

Please create a new topic. Some simple actions may be needed.

[Author]

Posts