About nexidator

This error message should not have any effect on the Event History app. The HMI communication with the PLC has nothing to do with the communication between the Event History app and the EventRecorder service. So, even if you get the error message when starting the HMI, you should be able to use the app to view the event history of the station. About the PLC communication problem: If your project has one HMI instance only which is on the same target system as the PLC, the HMI export will always generate a configuration containing the localhost AMS Net ID. In this case, when running the HMI on the development computer, it will try to connect to the local runtime, usually causing the error you are encountering. If you really want the HMI on the development computer to connect to the target system, you have to add another IPC with an HMI runtime to the OES/CpStudio project, representing your development computer. After exporting, the HMI configuration will contain the AMS Net ID you have configured for the IPC hosting the PLC, and communication to the PLC should work (provided the ADS route is configured). ... View more

Thanks for posting your code. As expected, it doesn't look like it can be the reason for the duplicate entry. (I am not sure if  "ELSE _retVal:=RUNNING" in the first step makes much sense, but I don't see how it could run into this line anyway.) One thing I forget to ask: Does the event appear twice in the HMI as well? I guess not, and otherwise this must really be a problem of the EventRecorder service. Can you try if it helps to update to the latest version of the EventRecorder service (V1.5.9)? I have seen in the change history that some bugs have been fixed since the version you are using. ... View more

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