TCP/UDP Protocol Handler (SysSocketLwIP) As of version 3.5.16.0, a TCP/UDP stack is integrated in the CODESYS Control RTE V3 . In the past, there were recurring problems with Ethernet-based fieldbuses
Configuration For the integrated TCP/UDP protocol stack to be used by the runtime system, the corresponding network adapter driver has to be configured in the component list of the RTE. The driver in
Log Outputs of the Protocol Stack Log outputs are the only way for the user to monitor the behavior of the integrated protocol stack. Tip By setting the log filter, more outputs are written in the log
Communication Task of the Protocol Stack The internal protocol stack needs its own task to process many UDP and TCP/IP tasks. This task is created immediately when the runtime system is initialized an
Checking the Time Behavior Create a simple standard project with CODESYS . Configure the only task to 1ms cycle time. Program a counter variable as type DWORD that counts the cycles. As a result, you
Configuring Real-Time Behavior on Special Platforms Real-time behavior of CODESYS Control RTE V3 on special platforms The time behavior of CODESYS Control RTE V3 depends on the consistency of the CPU
Commissioning the Hilscher CIFX Card The following steps are taken to install a Hilscher CIFX network card with CODESYS Control RTE V3 . The procedure is independent of the applied fieldbus system. Th
Using GPIOs and Analog Inputs This chapter describes the limitations when using the I/O mapping of a BeagleBone Black to access the GPIOs and analog inputs. :
Access Pins on P8/P9 The P8 and P9 plugs enable access to many GPIOs and the analog inputs. However, not all of them are freely usable by default. The HDMI and Linux device tree standard “slots” use s
