https://forge.codesys.com/u/valeria/activity/2021-07-22T10:02:23.562000ZRecent activity for valeria2021-07-22T10:02:23.562000Z2021-07-22T10:02:23.562000Zvaleriahttps://forge.codesys.com/u/valeria/profile/https://forge.codesys.com/forge/talk/CODESYS-V2/thread/c56d799450/?limit=25#82f3

Hello, I am working with a (real) PLC which accept (so far) only the CODESYS V3.5 SP14 Patch 3 version and need to use ModbusFB library. The version I have found is the ModbusFB 3.5.17.0 (3S – Smart Software Solution GmbH) which looks to be a too recent version to fit in the CODESYS V3.5 SP14 Patch version. Does any way to get a ModbusFB library which would fit the CODESYS V3.5 SP14 Patch version?

2021-07-21T11:38:54.002000Z2021-07-21T11:38:54.002000Zvaleriahttps://forge.codesys.com/u/valeria/profile/https://forge.codesys.com/forge/talk/CODESYS-V2/thread/c39cb4cb5e/?limit=25#4623

Again, thanks for the link. I had a look at this example, understood the global idea and made a super very simple test : instance one object "clientTcp: ModbusFB.ClientTcp;" The library ModbusFB was download "automatically" via Library Manager. When I instance the object "clientTcp: ModbusFB.ClientTcp;" , I have no red underlined and when I compile the code get a bunch of errors relative to the ModbusFB library. For example "Unknown type: SysComSettings" and when I look through the ModbusFB library...

2021-07-21T11:37:31.315000Z2021-07-21T11:37:31.315000Zvaleriahttps://forge.codesys.com/u/valeria/profile/https://forge.codesys.com/forge/talk/CODESYS-V2/thread/c39cb4cb5e/?limit=25#4623

Again, thanks for the link. I had a look at this example, understood the global idea and made a super very simple test : instance one object "clientTcp: ModbusFB.ClientTcp;" The library ModbusFB was download "automatically" via Library Manager. When I instance the object "clientTcp: ModbusFB.ClientTcp;" , I have no red underlined and when I compile the code get a bunch of errors relative to the ModbusFB library. For example "Unknown type: SysComSettings" and when I look through the ModbusFB library...

2021-07-20T13:12:16.651000Z2021-07-20T13:12:16.651000Zvaleriahttps://forge.codesys.com/u/valeria/profile/https://forge.codesys.com/forge/talk/CODESYS-V2/thread/c39cb4cb5e/?limit=25#f47d

Wow! Sound good :) I have a look. Thanks

2021-07-20T11:57:23.563000Z2021-07-20T11:57:23.563000Zvaleriahttps://forge.codesys.com/u/valeria/profile/https://forge.codesys.com/forge/talk/CODESYS-V2/thread/c39cb4cb5e/?limit=25#ae1a

I'm new in Codesys. I have to communicate with a large number of remote Modbus slave. For this I would like to create an "object" (FB or others... whatever) MBslave and instantiate it several times. I can realize this graphically (in the device tree in codesys) by creating under "Ethernet" a "Modbus_Master" module and then under that create all the Modbus_Slave modules. But for reasons of maintenance I want to realize this "by hand". Is this possible? I have already declared variables of type "ModbusTCPSlave"...

2021-07-20T11:30:05.083000Z2021-07-20T11:30:05.083000Zvaleriahttps://forge.codesys.com/u/valeria/profile/https://forge.codesys.com/forge/talk/CODESYS-V2/thread/c39cb4cb5e/?limit=25#ae1a

I'm new in Codesys. I have to communicate with a large number of remote Modbus slave. For this I would like to create an "object" (FB or others... whatever) MBslave and instantiate it several times. I can realize this graphically (left tab in codesys) by creating under "Ethernet" a "Modbus_Master" module and then under that create all the Modbus_Slave modules. But for reasons of maintenance I want to realize this "by hand". Is this possible? I have already declared variables of type "ModbusTCPSlave"...