Maintenance. Settings for monitoring of network components

The profile does not match the selected device. The profile does not include all required variables.
The variables list 'automationManufacturerId,automationFunctionTag' could not be found for device 'SCALANCE_X208' . Please check whether or not the device supports this and, if applicable, select the current profile file. Note: Only these variables are unavailable. The remaining functionality is not affected.
Is it too bad? Should I select another profile if I get such a warning?

Hello again.

Phantom75, thank you for the reply. I read those documents and still had troubles..

I requested for Siemens support and some issues are now decided. I guess I may post here some answers:

The CP1623 is a special network adapter because the CP1623 is able to emulate a network adapter as well as the real physical network adapter. The emulated network adapter is also named with NDIS adapter. On the Plantbus (with the physical network adapter) only ISO protocol or IP protocol is used and you can not open Web Based Management with the normal physical network adapter. This is the reason why the NDIS adapter is necessary to make use of the integrated Web Based Management of the Scalance switches on the Plantbus. The Web Based Management can only opened with the TCP/IP protocol (normal office network communication) and this is the reason why you can see the NDIS adapter in your Windows Network Configuration! If you just use CP1623 for ISO protocol or IP protocol, no CP1623 adapter is seen in the Windows Network Configuration (Note on that: Since PCS7 V7.1 the SIMATIC Miniport adapter – or NDIS adapter – is preinstalled on the PCS7 IPC machines).

1. In that case you have to use the NDIS adapter. Physically you go out with one cable but internally an emulated network adapter (NDIS adapter) is created and therefore the connection is separated.

All right, it is working! My problem was that I was told about that strange connection between CP1623 and another Ethernet adapter + that manual told about additional TCP/IP adapter needed, so I agreed. And I assigned IP 192.168.1.2x for free Ethernet adapter, so when you told me that I should use simply CP1623 I tried just to unplug Ethernet cable that was connecting CP and Eth-adapter – and it was a wrong testing approach. And when I had finally disabled Eth-adapter, the NDIS adapter began working. I can also just change IP network identifier from 192.168.1.xx to 192.168.0.xx – ok too.

2. It’s clear now. I disabled so called Plant bus SNMP Eth-adapter and changed its name to “reserved”.

3. Clear.

4. If you want a detailed diagnostic for your IPC stations I would prefer the communication via OPC because then you have also temperature or fan control. Otherwise, simply “computer is online / offline” mode is activated.
You configure the Terminalbus IP-Address in the Plant Configuration of your OPC Server.

I can't see a detailed diagnostic for IPC stations. Simply "online/offline"

5. The community of the IPCs isn’t correct. You selected “public”, but “SOL” is correct (You won’t find it in the drop down menu but you can simply write it into the field).

Further, please take only the released and tested profiles for Scalance.

Please select the profiles which are named in the following FAQ:

http://support.automation.siemens.com/WW/view/en/27833758
Page 33

So, if you will use a SCALANCE 208 you have to take the profile “SCALANCE X200_V”XX”.txt”

The message for “automationManufacturerId,automationFunctionTag” can be ignored because this is a new variable which is available only in the new Scalance and new PCS7 Version. This has no effects on your plant.

Good.

6. Please use the correct profile. The profiles which are listed in the documentation are released and tested with PCS7.
I’ve changed profiles for SCALANCE X204 and X208 to Profil_SCALANCE_X200_V11.txt
Now I see:
Function:
Location:
Description: ---
Message: ---
Identifier: SCALANCE_X204B
Address: 192.168.1.202
Device type: 204-2, 6GK5 204-2BB10-2AA3, HW: 8, FW: V4.04
Manufacturer:
Order number: 6GK5 204-2BB10-2AA3
Serial number: VPC1506597
Installation date: ---
HW-Revision: 8
SW-Revision: V 4.4.3
Last update: 2012-04-06 17:14:49

See attachment.

But in WEB Management of that Scalance the Device type field is: SCALANCE X204-2

7. Do I need to adjust DiagMonitor if PCS7 is used? No

Does it connected with PCS7 Asset Management? Yes

Local machine is added in DiagMonitor on every IPC – is it enough? Yes

Should it be started with Windows and could it work as a system Service? Yes, it should be started with Windows and Service is not necessary.

If DiagMonitor is launched with Windows it won't hide to System tray despite of the settings of DiagMonitor: 'Start with Windows' and 'Minimize to System tray' I think this is no matter? If yes, we have to open a separate ServiceRequest for our colleagues which are responsible for DiagMonitor.

This is not too bad, but I would like DM to hide to system tray automatically.

- By the way, I tried to use “Export CSV” while changing PC name and adding Nodes. But I’ve got an error with “Import CSV” function.
Then I tried to make Import of exported file without changing it – the same error:

Object Properties (4502:1063)
The format of the imported file is invalid.

Then I opened .csv and leaved just one row of data. And so “Import CSV” function showed no error. But I can’t make Import with one-row-csv several times to fill the Node list, because every Import operation is cleaning the list beforehand.

Nevertheless I changed the names to CWA03 etc, exported Tags to WinCC and updated Diagnostic screens. All PC stations were removed from Network objects Diagnostic screen (they were SNMP devices of type OSM there). In PC stations Diagnostic screen all block icons were changed from type PC_Station to type IPC_Station – this is good. One little exception is present – ES is of type IPC_Station (because it is named as the Computer is), but I’ll also use my ES as MS Client and this second PC Station can’t be named as Computer because this name is already used by ES, so I named it just MSCLIENT and now update Diagnostic screens function is adding a block icon of type PC_Station (not IPC) for MSCLIENT. I guess I don’t need two block icons for the same PC, so I should delete second block icon manually after each update, right?

- How can you prevent the creation of two PC stations (ES and MS client) in the process picture of the Maintenance Station when they are configured on the same computer?

Nothing new for the 6th question about Device type field. I guess I should correct it with a script, split the data and show just the correct part..