Has anyone ever downloaded setup data at the Physical Network level, if so what is the risk of loss of operations?
In reply to ROBERTO OKUDA:
So why would you do a system wide setup data download? On a running system, I would do the least impactful download possible. There are times when a controller will indicate a Blue Triangle indicating a download is needed, yet there is no subsystem indicating a need to download. I would try a Changed setup download, and if this did not clear it. I would do a Setup Download. That typically takes care of it.
Now if we think this through, and are prepared to do a Setup Download to any node if it needs it, then why can't we just do a Setup download to the entire network? We can. And it should work just fine. But if the plant is in full production, and something goes wrong, explaining to the Production Manager that some "expert" on a public forum said it would be OK is not going to win you any awards.
On a running system, performing a download to the physical network is a rather broad stroke approach. Most would agree that one should manage the system in a more focused approach, and evaluate any Generate Warnings associated with any downloads. So it would also depend on how large the system is, and what the overall state of the system is. Coming off a Turnaround before start up might be a valid time to do so.
Set up download sends a series of global files to each node that are intended to be identical on every node that has them. Workstations host many more Setup files than controllers do. controllers are limited to the seven such files/items:
Node Table: DT.SCR
Alarm Annunciation Table: APT.SCR
Enumeration Sets: UENUMS.SCR
Network Configuration parameters: NCP.SCR
Configurable Node Parameter Script: CNP.SCR
System Zone Name: SZN.SCR
Adapt Licensing Table: ALT.SCR
For the workstation nodes, they get the following files:
Software Licenses: SWLIC.SCR
Remote Client Subsystem: TERMSESS.SCR
Master Gateway Node: SGW.SCR
Network Configuration Parameters: NCP.SCR
Configurable Node Parameter Script:: CNP.SCR
In the background, there are some additional files that are automatically transferred to workstations in order to maintain the global system data consistent throughout the system. The Operator stations will end over 40 configuration files, meaning most of them are transferred via Auto Update. Most of these additional files show up on a Setup Download to the Professional Plus, and are propagated to other workstations through the Auto Update service once downloaded to the Pro Plus. The ProPlus also gets some additional files for its own use. The following is a partial list of global files sent via Auto Update service:
Area Table;
System Zone Name:
Node Table:
Module Table:
Event type table
SIS Event Type table
Alarm Annunciation Table
Default Parameter/Field Lock
Parameter Lock table
Write Lock Table
Field Lock table
SIS Parameter Lock Table
SIS write Locks table
SIS field Lock table
User Key table
Enumeration Sets
Engineering Units
DST table
Batch Server List
Batch Historian List
Batch Campaign List
Process History Server List
Global Alarm Audible Groups
System Journal List
Asset Server List
Communications alarm
SISNet Domain
CSLS SISNet Domain
(there are other files not shown in Pro Plus Setup Download)
It is important to ensure the Auto Update service has not been disabled for Setup Data to your workstations. Disabling the Setup Data updates can result in issues with data presentation on workstations as the Operator Interface these files for data presentation. I'm thinking this might be useful during an online upgrade where some stations remain at the previous version for a period of time. The new ProPlus version should not be updating these files on these stations until they are upgraded. Otherwise, I don't see a reason to disable Setup data. Device Files are related to new HART or FF Devices added after software installation. These are few and don't change often. Displays and CHARTs are the ones I can see being managed by disabling auto update to control new or modified versions deployed to a few stations for testing.
On a development system, or training system, I have no concerns performing system wide setup download , and even a full system download. On a production system, I am much more purposeful on my actions. There is a time and a place for everything. Every system is unique combination of configured control modules and nodes forming a complex system. Hmm. your call...
Andre Dicaire
In reply to Andre Dicaire:
In reply to Tim Ebarb:
Hi Tim, It is always safe to Download Change Setup Data or Setup Data, even to controllers. If you ever add or modify a name set you will have to Download Change Setup Data because the controller uses the name set to provide number values. One comment you made about the blue triangle being in from of the Physical Layer made me think you might misinterpret that indication. Anytime anything needs downloading that blue triangle will be in front of the Physical Layer. All download indicators migrate upward to the highest level, so you have to "drill down" until you find the lowest level where a blue triangle exists. Then it is a good idea to start with Download Change Setup Data to see if they go away. Again, Download Change Setup Data and Download Setup Data are always safe.
Sal Salamone