wiki Discussion
hughbecker
wiki
(Discussion)
Forum for wiki comments
Last updated: 2025-12-31
blog Discussion
hughbecker
blog
(Discussion)
Forum for blog comments
Last updated: 2025-12-31
(no subject)
hughbecker
wiki
(Thread)
Last updated: 2025-12-31
Home
hughbecker
wiki
(WikiPage)
Project Members: hughbecker (admin)
Last updated: 2025-12-31
wiki Discussion
thulane
wiki
(Discussion)
Forum for wiki comments
Last updated: 2026-01-01
blog Discussion
thulane
blog
(Discussion)
Forum for blog comments
Last updated: 2026-01-01
(no subject)
thulane
wiki
(Thread)
Last updated: 2026-01-01
Home
thulane
wiki
(WikiPage)
Project Members: thulane (admin)
Last updated: 2026-01-01
Post by karsonsv on CODESYS HMI and 2 monitors
CODESYS Forge
talk
(Post)
I need open visualization on two monitors (every monitor 19201080). In TargetVisu i configure Scaling Options as Fixed 38401080. But visualization open onli main monitor and onli half.
Last updated: 2026-01-02
wiki Discussion
karsonsv
wiki
(Discussion)
Forum for wiki comments
Last updated: 2026-01-02
blog Discussion
karsonsv
blog
(Discussion)
Forum for blog comments
Last updated: 2026-01-02
(no subject)
karsonsv
wiki
(Thread)
Last updated: 2026-01-02
Home
karsonsv
wiki
(WikiPage)
Project Members: karsonsv (admin)
Last updated: 2026-01-02
Home (version 1) discussion
karsonsv
wiki
(Thread)
Home (version 1) discussion
Last updated: 2026-01-03
Alarmgruppenvorlage kann über Kontextmenü keine weitere Latch Variable hinzugefügt werden
CODESYS Forge
talk
(Thread)
Alarmgruppenvorlage kann über Kontextmenü keine weitere Latch Variable hinzugefügt werden
Last updated: 2026-01-05
wiki Discussion
tobiassantos
wiki
(Discussion)
Forum for wiki comments
Last updated: 2026-01-05
blog Discussion
tobiassantos
blog
(Discussion)
Forum for blog comments
Last updated: 2026-01-05
(no subject)
tobiassantos
wiki
(Thread)
Last updated: 2026-01-05
Post by worker69 on Alarmgruppenvorlage kann über Kontextmenü keine weitere Latch Variable hinzugefügt werden
CODESYS Forge
talk
(Post)
Hallo, ich habe das problem, dass ich in einer Alarmgruppenvorlage keine wietere LATCh Variable hinzufügen kann. Wenn ich dies über das Kontextmenü versuche, dann erscheint folgende Fehlermeldung "Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt". Ich verwende Codesys V3.5.19 P0 und 23.5.19 P7 Was mache ich falsch
Last updated: 2026-01-05
Post by tobiassantos on History of Alarms
CODESYS Forge
talk
(Post)
I am running tests using the Windows runtime environment. The alarm history is not being logged and displays the error: "Some kind of disk I/O error occurred. Check disk space" in the alarm table. Furthermore, it is not possible to export the alarms. I have already tried to find a configuration field in Alarm storage and Alarm configuration to fix this problem, but I haven't found any related fields.
Last updated: 2026-01-05
Post by alexgooi on Codesys KNX implementation
CODESYS Forge
talk
(Post)
Dear forum, We are currently doing some research on the Codesys KNX implementation (https://store.codesys.com/en/codesys-knx-sl.html). We almost have it working but we are missing the last part. The setup: We have a Codesys virtual control container running on docker (4.17.0.0), the I/O is running over an Ethernet IP coupler (Weidmüller), and this is running fine. As far as I’m concerned this tells me that the ethernet device is working properly (the container has access to the outside world, including multicast). Underneath this ethernet adapter the KNX module is added (see picture). In the KNX device (Codesys) 2 input variables are added (see picture), and these are exported to ETS (ETS 5). In ETS A Codesys KNX device has been imported and the Codesys export was imported, afterwards the group addresses are attached to the variables (see picture). Afterwards this configuration is downloaded to the Codesys controller (Container) via ETS. ETS asks for the pressing of the programming button, when the virtual programming button is pressed the download starts and finishes without any errors. This tells me that ETS is communicating with the Codesys controller, and that the download process is ok (so far so good). Now the part where we are struggling with, somehow we need to convert the KNX TP to KNX IP. For this we have the following interface: Zenio KIPI SC (https://www.zennio.com/product/kipi-sc/) this is a KNX TP to IP interface. We have the following setup for this device (see picture) (an IP in the same subnet is used). We tried multiple combinations of IP addresses but the TP devices are simply not communicating to the Codesys container. Does anyone has any advice on what to try next. To make the question more explicit how can we link the TP bus to the Codesys device? Kind Regards Alex
Last updated: 2026-01-05
History of Alarms
CODESYS Forge
talk
(Thread)
History of Alarms
Last updated: 2026-01-05
Home
niklasf
wiki
(WikiPage)
Project Members: niklasf (admin)
Last updated: 2026-01-05
Post by tobiassantos on History of Alarms
CODESYS Forge
talk
(Post)
I am running tests using the Windows runtime environment. The alarm history is not being logged and displays the error: "Some kind of disk I/O error occurred. Check disk space" in the alarm table. Furthermore, it is not possible to export the alarms. I have already tried to find a configuration field in Alarm storage and Alarm configuration to fix this problem, but I haven't found any related fields.
Last updated: 2026-01-05
CODESYS OPC UA Security: HMI Client Not Receiving Server Certificate
CODESYS Forge
talk
(Thread)
CODESYS OPC UA Security: HMI Client Not Receiving Server Certificate
Last updated: 2026-01-06