Personal Data

Username:
rckalex
Joined:
2020-02-07 14:44:08

Projects

  • No projects to display.

User Activity

  • Posted a comment on discussion Engineering πŸ‡¬πŸ‡§ on CODESYS Forge

    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...

  • Modified a comment on discussion Engineering πŸ‡¬πŸ‡§ on CODESYS Forge

    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....

  • Modified a comment on discussion Engineering πŸ‡¬πŸ‡§ on CODESYS Forge

    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...

  • Modified a comment on discussion Engineering πŸ‡¬πŸ‡§ on CODESYS Forge

    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.

  • Modified a comment on discussion Engineering πŸ‡¬πŸ‡§ on CODESYS Forge

    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.

  • Modified a comment on discussion Engineering πŸ‡¬πŸ‡§ on CODESYS Forge

    Looking for a solution to this problem as well. It looks as if setting Holding Registers to be "Writeable" is part of the solution. Unfortunately, all holding registers are cleared when the Modbus Master disconnects.

  • Posted a comment on discussion Engineering πŸ‡¬πŸ‡§ on CODESYS Forge

    Having a similar issue. It seems that having coils and registers enabled maps them over the top of each other. With coils disabled I can write to registers externally but not from within the project. Furthermore when there is no activity for an external modbus the values set externally reset to 0.

  • Posted a comment on discussion Engineering πŸ‡¬πŸ‡§ on CODESYS Forge

    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....

View All