You can use C3.5 by using the 3S firmware on the 8202 https://us.store.codesys.com/codesys-control-for-pfc200-sl-1.html
You can use C3.5 by using the 3S firmware on the 8202 https://us.store.codesys.com/codesys-control-for-pfc200-sl-1.html
Trying to connect to a Codesys V3 datasource but am unsuccessful. The error information for the datasource reads: Failed (not nearer specified) Error ID: 418 Can anyone shed light on what that error means?
There appears to be a limit to the number of OPC Servers that can be connected simultaenously. 1-10 work but adding an 11th makes one of the previously linked ones unavailable. Is this a soft setting that can be adjusted? Using 3.5.18.30 on Win x64
Device Tested: Codesys Control Win V3 x64 (3.5.18.0) Codesys Version: 3.5 SP18 64bit Configuration: Codesys is acting as a Modbus Slave (ModbusTCP Slave Device). General Configured Parameters: Holding Registers: 10 (%QW) Writeable Input Registers: 10 (%QW) Coils: 0 Discrete Inputs: 0 Data Model: 0/0/0/0 In a global variables list I declared the following: UI_Word_1 AT %QW0 : WORD; UI_Word_2 AT %QW1 : WORD; UI_Word_3 AT %QW2 : WORD; Behavior: Unable to use the "Write Values" function in the Debug...
Devices Tested: Opto 22 Groov Epic PR 1 (3.5.17.10) and Codesys Control Win V3 x64 (3.5.18.0) Codesys Version: 3.5 SP18 64bit Configuration: Codesys is acting as a Modbus Slave (ModbusTCP Slave Device). General Configured Parameters: Holding Registers: 500 (%QW) Writeable Input Registers: 2 (%QW) Coils: 200 (%QX) Discrete Inputs: 0 Data Model: 0/0/0/0 [-img src=2022-07-21 13_21_42-Window.png width=50%: missing =-] Modbus Configurator automatically configured variables visible in the I/O Mapping section....
Moderator Please Close This Topic -- Further Testing Shows My Initial Observations Were Wrong Devices Tested: Opto 22 Groov Epic PR 1 (3.5.17.10) and Codesys Control Win V3 x64 (3.5.18.0) Codesys Version: 3.5 SP18 64bit Configuration: Codesys is acting as a Modbus Slave (ModbusTCP Slave Device). General Configured Parameters: Holding Registers: 500 (%QW) Writeable Input Registers: 2 (%QW) Coils: 200 (%QX) Discrete Inputs: 0 Data Model: 0/0/0/0 [-img src=2022-07-21 13_21_42-Window.png width=50%: missing...
In the General tab or your Modbus TCP Slave configuration, check "Writeable". Make sure you do not have a Watchdog enabled unless you want values zeroed when the master disconnects. Either map your values in the Modbus TCP Slave Device I/O Mapping tab or define your variables to overlay on the address range mapped for the Holding Registers. I can't quite workout what the "Holding and input register data areas overlay" means.