800xA Nodes load Calculation
If possible can anyone share the procedure.
TIA.
Answers
On the client node got “Start – Run – ‘afwapplogviewer.exe’” and click two times “Ok” to start the ApplogViewer tool with default values.
1. As next select the client node where you have started the Plant Explorer at the left upper corner.
2. 2. Select the application ‘AfwWorkplaceApplication.exe’.
3. 3. Select ‘Logs’.
4. 4. Select the component ‘OPC Communicator – CSLIBClient’ and change the value for ‘Level’ to ‘3’. Do the same for component ‘OPC Communicator – Common’.
5. 5. At ‘Start time’ click on button ‘Now’.
6. 6. Click on button ‘Get messages’.
7. 7. At the 800xA Plant Explorer navigate to the tag, e.g. ‘test1’ and open the ‘Control Connection’ aspect.
8. 8. Check the box ‘Subscribe for live data’ and wait a minute.
9. 9. Uncheck the box ‘Subscribe for live data’.
10. Save the log messages via ‘File – Save log messages as…’ to a file.
Close the ApplogViewer tool and forward the log message file to us please.
10. 
Use applog to pull the AdvDsOPCConnector Statistics (not adapter) operation on all OPC DA Connectors on all connectivity servers (this task can easily be done working from a remote engineering node).
The first page of output from above mentioned operation contains a table of connected clients and their OPC item count. With this data at hand you can edit affinity to achieve a more balanced client/item load on your source OPC servers.
However, my sincere recommendation in terms of affinity is to prioritize availability over load balancing. Better spread two adjacent client workstations over different OPC servers than striving for an exact 50/50 OPC item count spread. If an OPC server should freeze its values, or worse deliver incorrect data, my first wish as a process operator would be to have immediate access to ”a second opinion”.
An easy method to accomplish this is using Node Groups
Groups:
Odd Clients: ...
Even Clients: ...
Odd Servers: ... (but no AS)
Even Servers: ... (but no AS)
Engineering Workstations: ...
Affinity:
Odd Clients: AS1, Odd Servers, All Nodes
Odd Servers: AS1, Odd Servers, All Nodes
Even Clients: AS2, Even Servers, All Nodes
Even Servers: AS2, Even Servers, All Nodes
Engineering Workstations: AS3, Odd Servers, All Nodes
This rule is in fact the only affinity rule required, regardless of service (with exception of that some services don’t need affinity, eg the ones using Service/Standby concept or pure internal services like Alarm Logger, etc where no clients connect).
Add new comment