About nexidator

My remark about memory usage was more like a general thought. I just wanted to say we need to have an in-depth look at your proposal before we can adopt it. About "Replace constants": This option only applies to scalar types, so it doesn't change anything in this usecase. See at the bottom of this page: Beckhoff Information System - English I am not sure if there is a general recommendation by BCI, but my recommendation is to always activate "Replace constants". It should improve performance slightly (as the Beckhoff documentation confirms) and it makes the HMI start faster, especially when having many digital I/O. The disadvantage is that ADR cannot be used anymore and that no symbol is generated for replaced constants. I don't think these constraints really matter, and actually the reduced number of sub-symbols of the BinIo FB is the reason why the HMI starts faster. ... View more

Very interesting idea! As often, it is probably a matter of balancing between memory usage and performance. I will discuss this with my colleagues. About the most commonly used objects: At least BasMove uses GetAddress when entering the Operational state and works with pointers after that, so the performance should be good already. ... View more

That's good news! At least we have a simple workaround now. For everyone as background information: Mosquitto is an MQTT broker that is used for communication between the main HMI process and the 3D Navigation (=VirtualAssist) process. The HMI checks at startup if Mosquitto is already running and starts it otherwise. And that's the point where something goes wrong on Windows 11. If Mosquitto was already running, the HMI won't start it and also won't stop it when it is closed. So, if you are working on Windows 11, you can just start Mosquitto once in the beginning and always leave it open. Of course, we will investigate why it doesn't work on Windows 11 asap, but I am glad this workaround should enable everyone to work with the HMI on the development computer. ... View more