Industry Online Support
Technical Forum
1/17/2012 9:30 AM | |
Joined: 9/27/2009 Last visit: 1/20/2023 Posts: 1 Rating: (1) |
Hi, I hadthe same problem with monitoring clients and here is what I did: At first you have to make connection to all devices you want to monitor. The basic description youcan findhere: http://support.automation.siemens.com/WW/view/en/22880973 Steps4 says: "Repeat steps 2 and 3 for each OS that you would like to monitor. .." I did it for servers but I didn't do that on clients as I didn't find "OPC.chn" file for driver in folder and didn't want to experiment. In Lifebeat monitoring youhave to define connection(you can choose the name in the list of the field), define device type (you can choose the name in the list of the field) and write device name (I used the same name as I have in connection field) for all devices you want to monitor. (Seepicture in file.) And then update. Ihave forgotten to write, that you have to create "@Config.Pdl"picture before you update Lifebeat monitoring.. Lifebeat monitoringcreate @[device name]tag in each of your defined connection.In its Tag properties you can find thatAS devicestags have address MD0. ForOS and OS/Client you better check it(see picture in file).For OS in tag address properties I chose Itemname as the nameof tag which was created by Lifebeat monitoring (@SERVER2).For OS/Client (I have client with project!) I created internal tagon each client (tag LBM/@[computer name] (see picture in file)) and defined it onserver in tag address properties asItem name. Ihave found that you can use eny existinginternal tag on client.To see ifserver found the tag check quality of tag in its tool tip text.. The script for vizualisation of tag status on screen is here: http://support.automation.siemens.com/WW/view/en/382120 Hope it helps.. AttachmentLifebeat.zip (184 Downloads) |
Follow us on