About nexidator

Thanks for reporting the problem. We were not aware of this change in ctrlX 02VRS. In 01VRS, the ARM compiler was more tolerant concerning misaligned structs. I am afraid there is no solution for this problem, at the moment. The DDL event FB can only send struct arrays if the struct definition does not contain any padding bytes, that's why this struct uses pack mode 1. And obviously, OpconSetupRealData is often used in DDL telegrams, so we cannot change this. When the struct is used by variables that are shown in the HMI (e.g. online data in the data editor), the symbols need to be published, which causes the problem you ran into. It looks like it is impossible to show any variables of this type in the HMI when using the ctrlX CORE X3 because of the ARM processor. X5 or X7 do not have this problem. ... View more

This behavior is intentional. The thought was that units are usually hardware independent and more likely to work on any PLC type. That's why they default to NotTested. Peripheral objects often need explicit IO linking information for each supported PLC type, that's why they default to No. By the way: If the whole SupportedPlcTypes element is missing, BTC support is assumed as "Yes" for compatibility reasons. ... View more

The ManualFunctionKey can only be linked to manual functions. Add-ons don't have an Extension, so they cannot have manual functions. If you want to bring manual functions through the object definition, your object has to be a unit, not an add-on. Of course, it is possible to create a manual function in the project that calls a command of an add-on. You cannot link the command to the manual function in CpStudio, but the call would have to be implemented manually in the PLC code. ... View more

I agree something must be wrong on your PC, but no idea what's the problem. I also found WMI related problems when searching the internet. Here ist another way how to repair the WIM, but no guarantee this will help... ... View more