All Neighborhoods

CODESYS Talk

    CODESYS Forge

  • husarz17 posted a comment on discussion Runtime 🇬🇧

    My codesys is 3.5.21.30. I am using function ModbusServer from library ModbusTCP_Slave. The reason is that I need share 9000 Holding registers. By standard configuration it is only 4096. fbMbTcpDevice: ModbusTCP_Slave.ModbusServer; fbMbTcpDevice( wPort := 502, pInputData := ADR(awInputReg), pOutputData := ADR(awHoldingReg), uiInputDataSize := 10, uiOutputDataSize := 9000, xEnable := TRUE, tTimeout := 10000, InterfaceName := "eth0", xBusy => xBusy, xError => xError, byClientConnections => byConnections...

  • nulltrace posted a comment on discussion Runtime 🇬🇧

    Please explain how you configured that. Normaly, the Server should answer to all UID as long as gateway isn't activated. With activated gateway all UID will be forwarded to Serial-Interface, in taht case 255 has to be used for Gateway-Diagnostics. So that means, there is somethink wrong on your configuration. Which CDS-Version, Which Runtime-Version and so on are used.

  • husarz17 posted a comment on discussion Runtime 🇬🇧

    I need the same issue. In my application TCP server on raspberry (codesys) should have UnitID 1. But it only works when I am requesting with UnitID 255. And my application can't work with this parameters...

  • thierry-b posted a comment on discussion Engineering 🇬🇧

    Hello, I am currently investigating the network behavior of CODESYS 3.5 (IDE + Gateway) in environments where the engineering workstation is connected to a very large /16 network. In such networks, the automatic device scan performed at IDE startup (and the manual “Scan Network” device discovery) can cause significant delays or freezes, due to the broadcast‑based discovery mechanism. After analyzing the traffic with Wireshark, I identified that the IDE uses the following UDP ports: 1740 – broadcast...

  • sheberle posted a comment on discussion Runtime 🇬🇧

    Hello Alex, the message is generated by the CODESYS code generator based on the DevDesc settings of the memory areas available for the target. The problem arises when after too many online changes the area is full. Therefore no more boot project can be generated. Short-term remedy as described in the dialog: Clean and fresh download. This way the initial memory size will be "used" again After how many online changes did this error occur? There is no set limit on the number of online changes, but...