Post by dawidr on Best practices for querying multiple MODBUS devices ^{CODESYS Forge talk (Post)}
Hi! What are the best practices for querying multiple Modbus devices? Single PRG or maybe multiple PRG (so basically multiple thread) per each Modbus device. In my current implementation I'm using single PRG and I'm utilizing FbMbMasterMultiQuerySerial and WagoAppPlcModbus.FbDigitalTwinMbSlaveDevice in eCockpit with PFC200. I've the timer with 2 seconds delay there and it was working fine for single device. But now I have three Modbus devices and for two of them I need to run 2/3 queries to get data from all registers. I noticed that the delays for getting the data from the Modbus devices is much bigger right now.
Last updated: 2024-07-31

Post by thysonfury on OPTO22 Groov Epic PR2 Modbus Comms Dropping out every 2 hours and 4 Mins ^{CODESYS Forge talk (Post)}
Hi after some assistance with an error on a Groov PR2 PLC. We have a few different communications set up as shown below: One Modbus TCP Slave Connection - ( Sending / Receiving Data from a PC ) Two Modbus TCP Master Connection - ( Reading Data from a UPS Panel and Reading Data Gas Chromatograph) One Modbus RTU Slave Connection 485 - (Reading Data from a fire and gas panel) One Modbus RTU Master Connection 485 - (Sending Data to a Telemetry Unit) All Licenses have been installed as per OPTO22 suggestions of the order below: Modbus TCP Master Modbus TCP Slave Modbus RTU Master Modbus RTU Slave When I check on License manager the RTU Master license seems to disappear on installing the RTU. (What ever reason I’ve been told this is “normal”). If I use Device License Read It will successfully read all the licenses correctly. Now the issue is every 2 hours and between 4. For what ever reason the communications seems to end and lock up for about 20 seconds. During this time even if I was logged into the PLC it would kick me off and I’d have to re type the password to enter. Most of the devices can handle this however the RTU flags up a communications failure at the SCADA and is raising alarms every 2 hours and 4 mins. We’ve had multiple people go through the code to check for anything obvious. Does anyone have any ideas?
Last updated: 2024-04-15

Post by thysonfury on OPTO22 Groov Epic PR2 Modbus Comms Dropping out every 2 hours and 4 Mins ^{CODESYS Forge talk (Post)}
Hi after some assistance with an error on a Groov PR2 PLC. We have a few different communications set up as shown below: One Modbus TCP Slave Connection - ( Sending / Receiving Data from a PC ) Two Modbus TCP Master Connection - ( Reading Data from a UPS Panel and Reading Data Gas Chromatograph) One Modbus RTU Slave Connection 485 - (Reading Data from a fire and gas panel) One Modbus RTU Master Connection 485 - (Sending Data to a Telemetry Unit) All Licenses have been installed as per OPTO22 suggestions of the order below: Modbus TCP Master Modbus TCP Slave Modbus RTU Master Modbus RTU Slave When I check on License manager the RTU Master license seems to disappear on installing the RTU. (What ever reason I’ve been told this is “normal”). If I use Device License Read It will successfully read all the licenses correctly. Now the issue is every 2 hours and between 4. For what ever reason the communications seems to end and lock up for about 20 seconds. During this time even if I was logged into the PLC it would kick me off and I’d have to re type the password to enter. Most of the devices can handle this however the RTU flags up a communications failure at the SCADA and is raising alarms every 2 hours and 4 mins. We’ve had multiple people go through the code to check for anything obvious. Does anyone have any ideas?
Last updated: 2024-04-15

Post by thysonfury on OPTO22 Groov Epic PR2 Modbus Comms Dropping out every 2 hours and 4 Mins ^{CODESYS Forge talk (Post)}
Hi after some assistance with an error on a Groov PR2 PLC. We have a few different communications set up as shown below: One Modbus TCP Slave Connection - ( Sending / Receiving Data from a PC ) Two Modbus TCP Master Connection - ( Reading Data from a UPS Panel and Reading Data Gas Chromatograph) One Modbus RTU Slave Connection 485 - (Reading Data from a fire and gas panel) One Modbus RTU Master Connection 485 - (Sending Data to a Telemetry Unit) All Licenses have been installed as per OPTO22 suggestions of the order below: Modbus TCP Master Modbus TCP Slave Modbus RTU Master Modbus RTU Slave When I check on License manager the RTU Master license seems to disappear on installing the RTU. (What ever reason I’ve been told this is “normal”). If I use Device License Read It will successfully read all the licenses correctly. Now the issue is every 2 hours and between 4. For what ever reason the communications seems to end and lock up for about 20 seconds. During this time even if I was logged into the PLC it would kick me off and I’d have to re type the password to enter. Most of the devices can handle this however the RTU flags up a communications failure at the SCADA and is raising alarms every 2 hours and 4 mins. We’ve had multiple people go through the code to check for anything obvious. Does anyone have any ideas?
Last updated: 2024-04-15

Post by kislov on CODESYS Modbus 4.4.0.0 - Modbus network redundancy ^{CODESYS Forge talk (Post)}
Hi. There is next information in CODESYS Modbus 4.4.0.0 Release Notes: "Modbus network redundancy" How to use this feature? As I understand, new fields in STUCT ModbusTCPComSettings are associated with it, but more detailed information is needed.
Last updated: 2024-10-07

How to change data format of 'Trend' time data to DT or something else ^{CODESYS Forge talk (Thread)}
How to change data format of 'Trend' time data to DT or something else
Last updated: 2021-05-10

OPC connection with many data ^{CODESYS Forge talk (Thread)}
OPC connection with many data
Last updated: 2014-04-26

Beckhoff - Siemens Profinet data exchange ^{CODESYS Forge talk (Thread)}
Beckhoff - Siemens Profinet data exchange
Last updated: 2018-10-10

Data storage and Export in Codesys ^{CODESYS Forge talk (Thread)}
Data storage and Export in Codesys
Last updated: 2023-10-29

Serial modem data exchange ^{CODESYS Forge talk (Thread)}
Serial modem data exchange
Last updated: 2022-10-04

AcuCD 240 data conversions ^{CODESYS Forge talk (Thread)}
AcuCD 240 data conversions
Last updated: 2013-06-22

XY chart - pointers for data ^{CODESYS Forge talk (Thread)}
XY chart - pointers for data
Last updated: 2020-12-14

data consistency in ProfibusDP ^{CODESYS Forge talk (Thread)}
data consistency in ProfibusDP
Last updated: 2008-10-13

Error when importing PLCopen XML data ^{CODESYS Forge talk (Thread)}
Error when importing PLCopen XML data
Last updated: 2015-06-23

Recording data to CSV files ^{CODESYS Forge talk (Thread)}
Recording data to CSV files
Last updated: 2018-02-13

OPC Datasources No Live Data ^{CODESYS Forge talk (Thread)}
OPC Datasources No Live Data
Last updated: 2021-11-19

Webvisu Trace from Application data recorder? ^{CODESYS Forge talk (Thread)}
Webvisu Trace from Application data recorder?
Last updated: 2018-10-15

Data Types and following variables comments ^{CODESYS Forge talk (Thread)}
Data Types and following variables comments
Last updated: 2014-11-25

CODESYS Sensor App GPS Data ^{CODESYS Forge talk (Thread)}
CODESYS Sensor App GPS Data
Last updated: 2021-10-14

Trend Data To CSV Files? ^{CODESYS Forge talk (Thread)}
Trend Data To CSV Files?
Last updated: 2022-06-03

Webvisu and complex data access ^{CODESYS Forge talk (Thread)}
Webvisu and complex data access
Last updated: 2009-11-24

ethernet/ip data exchange problem ^{CODESYS Forge talk (Thread)}
ethernet/ip data exchange problem
Last updated: 2020-07-02

Exchange data between multi raspberry ^{CODESYS Forge talk (Thread)}
Exchange data between multi raspberry
Last updated: 2017-01-11

write data to the CSV file ^{CODESYS Forge talk (Thread)}
write data to the CSV file
Last updated: 2018-01-20

send data to com port ^{CODESYS Forge talk (Thread)}
send data to com port
Last updated: 2007-11-27

Sort by relevance or date