modbus communication issue

[BacMoonShin]

I am a college student who has just come into contact with IEC61499. I successfully compiled the forte runtime in the Linux virtual machine of vmware and deployed the function block containing modbus communication through the 4diac IDE. The specific deployment situation is shown in the following figure. I set up a modbus TCP Server on the Windows host machine using the ModbusSlave software. Its IP address is 192.168.162.1 and the port is 502. In the Linux virtual machine, I used the mbpoll tool to confirm that modbus TCP Server could be accessed successfully, but I couldn't access it in forte. The specific configuration details are shown in the following figure. May I ask if the method I used is incorrect?
The version of forte is 2.0.1

[gravemalte]

Could you try to add tcp:// to the Initial Value field in 4diac-IDE and then run it again?

[K019N]

in last versions like v2.0.1 you should set CLIENT_1->ID for modbus like this: modbus[(protocol:)ip:port:pollFreqency:functionCodeRead:functionCodeWrite:(slaveId):readAddresses:sendAddresses(:responseTimeout:byteTimeout)]

functionCodeRead:
1 = Read Coils
2 = Read Discrete Inputs
3 = Read Holding Registers
4 = Read Input Register

so u can try somethink like: modbus[127.0.0.1:502:2000:3::1:0..3]
tcp protocol is default so u shouldn't specify it

[BacMoonShin]

in last versions like v2.0.1 you should set CLIENT_1->ID for modbus like this: modbus[(protocol:)ip:port:pollFreqency:functionCodeRead:functionCodeWrite:(slaveId):readAddresses:sendAddresses(:responseTimeout:byteTimeout)]

functionCodeRead: 1 = Read Coils 2 = Read Discrete Inputs 3 = Read Holding Registers 4 = Read Input Register

so u can try somethink like: modbus[127.0.0.1:502:2000:3::1:0..3] tcp protocol is default so u shouldn't specify it

Thank you very much for your suggestion. Now I am able to read the data in the Modbus TCP Server, but a new problem has arisen: According to your instructions, when the ID option is set to "modbus[192.168.162.1:502:1000:3::1:0:]" and "modbus[192.168.162.1:502:1000:3::1:3:]", the data that should be read is different, but here I am reading the same data. Could you please explain why this problem occurs?
Additionally, the explanation I found in the official GitHub documentation is different from yours. If it's convenient, could you please tell me the technical document you referred to? Thank you very much.

[K019N]

i dont know what the problem might be. The only thing u need to do after fixin the ID field is to resend the app to forte again.

on github, the documentation starts from 2024 and base on the develop branch. The information I wrote above is from the docs that was previously available on the website, but unfortunately, it is no longer available x(

[gravemalte]

The doc can be found here:

https://github.com/eclipse-4diac/4diac-documentation/blob/main/src/communication/modbus.adoc

[azoitl]

Yes our current documentation is mostly for the development / freeze branch. @kumajaya greatly improved our modbus support which made changes to the ID necessary.

With all the new features and improvements I can only recommend to switch to the freeze branch. This will soon get the 3.0 release.

[BacMoonShin]

Yes our current documentation is mostly for the development / freeze branch. @kumajaya greatly improved our modbus support which made changes to the ID necessary.

With all the new features and improvements I can only recommend to switch to the freeze branch. This will soon get the 3.0 release.

Thank you very much for your suggestion. During these two days, I attempted to switch to the "freeze" branch, but I still encountered problems during the compilation process. This time the issue is related to OPC UA communication. As shown in the figure below, as long as I follow the document instructions and add the OPC UA module in Cmake, errors will definitely occur during the compilation process. If I only select the MODBUS module, the compilation can be successfully completed. However, when I try to deploy using the IDE, an error occurs. The running result is also shown in the following picture.
In addition, I also tried using the “release” branch. But when enabling both the OPCUA and MODBUS modules simultaneously, the compilation failed. When only enabling the MODBUS module, the compilation was successful, but the same problem occurred as before. The data accessed from different addresses was the same.

[azoitl]

The freeze branch needs a newer version of open62541: 1.4.7. In the main 4diac FORTE directory you can find the file dependencies.spdx there we document the required version.

The release branch is the same as 2.0.1. It always holds the current release.

[wzj7531]

@BacMoonShin 请联系我，说不定我能给你帮助。目前我已经能够二次开发了，微信:Tony313051