Running Event recorder app on another pc,

[Tardigrade]

We are running the Event Recorder App V1.5.5, to visualise the event locally on a machine. Is there a possibility to run that app on another pc and connect to the machine? OES version V4.10c

[Tardigrade]

I can get connection via the opcondata share, that works fine, but  it would of course be easier to just connect to the target via IP and Port.

I never use the run hmi locally fucntion, i some how can't get it to work, i always get a error message in the log.

"[Error] <Driver Beckhoff at Channel Ch1>
Execption <Ads-Error 0x7 : Taget machine could not be found.> in line 1 while connecting the PLC [ADSNotification]"

Is there some manual how to do this correctly ? Maybe i am doing something wrong .

[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).

[Tardigrade · Accepted solution]

I got it working, i already had tried what you suggested. (adding an extra IPC runtime and HMI) but i kept getting the error message.

Problem was that AMS NED ID in the  OES config was not correct, and as long as there was only one HMI  on the same target systems as the plc. The connection for HMI went VIA ADS localhost 127.0.0.1.1.1 and everything worked fine. But when i added the extra IPC RT and HMI and did an export the wrong ADS NED ID was in the export files.

After putting the correct AMS NET Id in the OES and export it works fine.

Thanks for putting me on the right track !