About nexidator

I am afraid the way you suggest is not technically feasible. Even compatible object versions can have different (additional) content so it is not possible to ensure that all data is consistent after merging objects from different versions. So, the first step is to adapt the object versions used in the source project to the ones of the target project. The easiest way to achieve this is to create a copy of the source station folder directly next to the target station folder, so that both are using the same Std folder. Now, the version management dialog in the source project will automatically suggest the object versions required by the target project. After updating the versions, copy/paste between the two project should be possible. ... View more

You are right, connecting to the station directly doesn't seem to work. It does work when starting the HMI on the development computer and connecting the app to the service on the target system, that's why I thought it must work with the EventViewer as well. We will investigate the problem and get back to you. But as I understand, the file usecase is the one you really need, right? ... View more

This looks really weird, but actually I am quite sure there is no general problem with event texts using {0}. What version of the EventRecorder Service (= Runtime) are you using? Can you post the source code of the step where you set the event? (Alternatively, you can contact our helpdesk so we can give you directions how you can send us your project for analysing the behavior.) ... View more

Thanks for the hint! We are planning to add the missing OpCon string functions in one of the next versions. I am afraid the CodeChecker is slightly ahead of the times and does not distinguish between the string functions that can already be replaced and the missing ones. For the time being, please ignore the CodeChecker findings. ... View more