- Run the ASP installer by role (All-in, Runtime client, historian, etc).
- During the installation create the ArcNet user.
- Assign to the domain user the same rights as the ones from ArcNet, plus administrator.
- Set all green in the configurator.
- Run the Change Network Account, but before restart run C:\Program Files (x86)\Common Files\ArchestrA\OSConfigurationUtility.exe for any OS level registry changes.
- From the IDE, ensure these Services are deployed to the nodes:
- Change the level of notifications in the uac (User Account Control Settings), from high to low.
- Network:
> Disable IPv6.
> Change the IPv4 priorities, and set priority 1 to the SCADA network. This is done in "Advanced..." > Untick "Automatic Metric" and set "Interface metric" to 1.
> Check by powershell command: Get-NetIPInterface.
> In the IDE, set the Platforms by IP rather than PC hostname. This is better and prevents having the host file and domain issues.
> Open necessary Firewall rules. MCS uses by default port 49153. Check the ping by port powershell command: Test-NetConnection 192.1.1.1 -port 49153. Note: Check the TcpTestSucceeded result. Optional flags are -InformationLevel Detailed.
> netstat -a ensures the port is open.
Notes:
- To hide a repetitive message in the Logger, open the message and copy the text. In the filter, paste the message content in the message box, and select hide. Activate the filter to apply it.
- Tags in initializing state can indicate a gateway issue (data provider). Tags in bad state can indicate an issue with MCS that can be solved by restarting MCS (PLC > MCS > GW > OPC > AppEngine > Platform).
No comments:
Post a Comment