Due to extension of our DeltaV-system we need to move a lot of existing control modules from one area to another. This is needed to divide the correct alarms to the correct operator station.
Moving the control modules is very easy. But what do you need to download to get this active?
Sure, you have to download the affected operator station. But as we tested it on a test-system it seems that you also have to download the control modules. Wich is not that obvious in a running plant. Is there a way to get this active without downloading the control modules? For example by downloading the pro+ or the setup data of the controller?
Also units wich run in batch are changed from one area to another. Do we need to download them also? I suppose running batches on this units will be affected, when downloading the batch executive?
gr,
Jeroen
You don't need to download everything but you do need to download setup data to all the nodes that deal with those control modules. Downloading setup data should not affect the operation of the other parts of the plant.
In reply to carllemp:
We downloaded setup data of the affected OS, Controller and PRO+, but the alarm does not come active in the new area assigned to the OS. On OS where the old area is still assigned the alarm does appear.
It seems downloading the setup data is not enough. Only by downloading the control module, the alarm changes from one area to the other.
Anyone suggestions?
In reply to Jeroen Hoorelbeke:
I had to move running modules in a power station once before (V10) and ended up having to download them (at appropriate times) to get rid of the blue triangles, regardless of other issues.
In reply to Chris:
You have to change the logged in user in DeltaV Operate for some setup data changes to be visible.
Log on as a supervisor and then back as the operator.
Changing the assigned Area, Description, Control Display, Instrument Display or Detail Display will set the module change flag and requires a module download to clear. These fields are part of the module download script to the controller, in addition to being part of the setup data sent to all workstations.
The Setup data allows each console to work with a module, knowing where it is in the system, what area it belongs to for security locks, and what to display in the faceplate and alarm system fields, as well as which displays are assigned.
I don't know if this information was always part of the module script or if this was added when Zones was introduced. Local modules are defined in the system setup data, but remote modules in other zones are not. For a workstation to properly handle the Area, displays and description, the information needs to be provided at runtime, and this is likely why the data is now in the modules. In any case, changing these fields will set the download flag and a module download is needed to clear the flag.
Andre Dicaire