DeltaV Discussion Forum - Recent Threads

Finding where a given GEM is used in Live

Kent — Thu, 25 Jun 2026 18:06:17 GMT

I am looking for a method for finding all the places a given GEM is used in all of my Live displays. In particular, I'm wanting to be able to look at all the Chart and Sparkline GEMs to check which tags they are referring to. Is there an easy way to do this?

OPC HDA Server tag unknown to DVCH

Kent — Fri, 19 Jun 2026 15:53:48 GMT

I'm getting a very strange error message. It says that a given tag on the DeltaV OPC HDA server is unknown to the DVCH. The tag exists but is not in the historian and never has been that I know of. The HDA server connects to a OPC HDA interface to send data to PI. The tags in question are not in PI either. I looked at the HDA server with the HDA Tool that comes with the PI interface and I don't see any of the tags in question on the HDA server. Any suggestions on how to troubleshoot this? I'm puzzled.

New Delta V monitors

Steven Harris — Thu, 18 Jun 2026 20:16:35 GMT

Looking to move from the Dell P2213 WXSGA+ to the larger 24" WUXGA screens. Has anyone experienced any problems doing that?

How do I know if my M-Series 8-wide carrier was manufactured after 2002?

Luis Alberto Navas Guzman — Tue, 16 Jun 2026 13:24:06 GMT

We want to replace some MD+ controllers with PK controllers. The PK controller only supports 8-wide carriers manufactured after 2002. Seeing my serial number T0832..... seems that i was built on year 2008 week 32. Am i Right?

Thank you!

Batch Units with History Data Points

Manuel Behrens — Thu, 11 Jun 2026 06:36:15 GMT

Hi All,

Batch Unit Classes are not supporting History Data Points. Due to that it's only possible to deploy them in the instances. For many other cases (control module instances) we are using FHX merge to add History Data Points. But for the Batch Units I'm not able to find the correct spelling... any idea?

What we use for Control Modules.. I tried some different thinks changing "MODULE_VALUES" to something else, but without success.

Maybe it's possible to bulk it?

Any idea is very welcome.

Thanks, Manuel

MODULE_VALUES TAG="R540_UNIT" merge=T
{
  HISTORY_DATA_POINT_INSTANCE NAME="U_CHARGE_COMPL"
  {
    HISTORY_DATA_POINT FIELD="CV"
    {
      DATA_CHARACTERISTIC=CONTINUOUS
      ENABLED=T
      SAMPLE_PERIOD_SECONDS=1
      COMPRESSION_ENABLED=T
      RECORD_AT_LEAST_EVERY_MINUTES=1440
      DEVIATION_LIMIT_FOR_COMPRESSION=0.01
      DATA_REPRESENTATION=AUTOMATIC
      EXPOSED=T
      ENTERPRISE_COLLECTION=F
    }
  }

}

DeltaV v11.3 PROFIBUS DEVICE ERROR on Multiple Cards

Carlos Cortazar Castaño — Wed, 10 Jun 2026 22:00:01 GMT

Hi everyone,

I have a DeltaV v11.3 system with two PROFIBUS DP Series 2 cards, each connected to a Hardy HI4050 weight transmitter.

After a power outage, both PROFIBUS cards started showing alarms and errors as shown in the image.

In DeltaV Diagnostics/Explorer, both cards show Integrity BAD.

The strange part is that communication is still working correctly and both weight transmitters continue sending valid values.

Has anyone experienced a similar issue where PROFIBUS communication remains active but DeltaV continues reporting DEVICEERROR alarms?

Offline factory reset on a Fisher DVC6200

Dan Mos — Wed, 10 Jun 2026 21:34:55 GMT

Has anyone been able to perform a factory reset on a Fieldbus DVC 6200f / DVC6000f Dev rev 4 that has been removed from a segment?

DeltaV AI Card Burnout Direction Setting

jgrunschel — Fri, 05 Jun 2026 16:07:59 GMT

Most transmitters have a setting for which direction (High or Low) the transmitter should go when there is a failure (burnout direction). The conventional wisdom is to set transmitters in loops that add energy to burnout high, then in the event of a transmitter failure, the loop will stop adding energy to the system.

We recently had an issue where we lost the wire (broken) between the transmitter and the DeltaV analog input card. The loop went to -10%, regardless of the transmitter burnout direction. This got us thinking about burnout direction for Analog inputs. I know Thermocouple cards automatically burnout high when you have an open loop. It seems Analog Input cards do not have a burnout direction, they are either -10% (0 mA) or 110% (24 mA) depending on if the problem is open loop or shorted wires. We have all looked, and we cannot find any setting in DeltaV to control this behavior. I have searched the internet, and it seems there are custom-rolled solutions using HART (if you have it) or looking at the AI function block status/errors.

A lot of our heater control loops route the temperature element through a third-party transmitter that has burnout settings, and it is sent to a DeltaV analog input card through a 4-20 mA loop. In several cases, the third-party transmitter is in the same cabinet as our controller, so the likelihood of losing the analog connection between the transmitter and the DeltaV card is extremely low, and the scenarios that might cause that to happen would probably result in total loss of the cabinet anyway. However, the rest of the temperature elements have the transmitter in the field, attached to the temperature element. This exposes the analog wires to more opportunity to be damaged, which negates the burnout settings, exposing us to risk.

My question is if there is a built-in parameter/solution for burnout direction on Analog Input cards, or to see what others do to address failures of the 4-20 loop in loops that need to burnout high?

Cross Reference tool error

Mohamed Alkhouly — Fri, 05 Jun 2026 11:49:42 GMT

Hi community,

I have a problem with cross reference tool. I want to get a report for massive number of displays, but suddenly the tool gives error (such the figure below) and stop. I don't want it to stop. I want it to continue and skip all types of errors.

Also, some of the errors comes when there is an alarm summary object in display i want it to skip this error also.

Licenses needed for a new remote session in an existing Remote server

dikshitsh — Fri, 05 Jun 2026 08:56:36 GMT

Dear All

I would like to know the licenses are needed after adding a new remote session to used to as view only session with alarms and events

Previously we had used operator full span of control and alarms and events license for an existing session.

But the new session is needed to only view the graphics and alarms and events --> no operation to be done

Thanks

XFR/OUT Goes to Zero After Download When IN_2 is Selected, IN_1 Not Affected

jgrunschel — Wed, 03 Jun 2026 17:34:28 GMT

We use a transfer function block (XFR) to select between two pH probes. The SELECTOR parameter is wired to an input parameter that is written to from an operator graphic. Production decides which probe to use from the graphic. While working on the module that contains the XFR block, I noticed that XFR/OUT would go to zero after a download and then walk its way back to the actual value according to the XFR/BAL_TIME parameter (10 s in our case). I was not expecting this, since XFR is the first block in the execution order, so it caused a few tense moments while I got the process straightened out. I thought this was an initialization issue, so I added a 30 second delay to the logic after a download is performed which is enough time to let the XFR/BAL_TIME finish (in retrospect, I should probably reference that value directly in case it gets changed in the future) and there is no longer a process upset.

Fast forward to today and I downloaded the module again, but the XFR/OUT value didn't go to zero this time. During today's download, XFR/SELECTOR was 0 (IN_1), and I thought it had been set to 1 (IN_2) when the value went to zero. I momentarily disabled the associated logic and began testing. The following pizture of the PHV trend has my annotations describing my test.

My question is, why does XFR/OUT go to zero only when IN_2 is selected? This seems like a bug opportunity for improvement.

Debugging in DeltaV Live

garrett beaubien — Fri, 29 May 2026 16:44:52 GMT

Hello!

I would like to ask about debugging DeltaV Live graphics scripts.

We have a DeltaV version 14 and a DeltaV version 15 development system. When we started on the version 14 system, on any graphic (e.g. contextual detail display), I would simply add a debugger statement:

in the script I wanted to debug, run the graphic in DeltaV Live, press F12 to bring up developer tools, and when the code was hit, this would act as a breakpoint. For example if this statement was added to a button script, and the developer tools was open, every time I click the button, it would stop at this point.

When I try the same trick on our version 15 system, this no longer works.

Is there a setting to enable this behavior? or is there other recommended options for debugging?

Thank you kindly,

Garrett.

Enhancement request for PK/EIOC/SZ/DeltaV IO cards

TarashBermudez — Fri, 29 May 2026 02:22:00 GMT

Emerson customer is requesting for a prompt that will alert operator saying that the firmware of newly inserted DeltaV card does not match the current system. Client is also suggesting that Hardware coming out of Emerson's manufacturing plant should indicate the firmware on the box so that there's no need for them to plug it into DeltaV system just to find out its SW revision.

Password Protection DeltaV Live

fraguila — Thu, 28 May 2026 17:36:36 GMT

How to set password protection for data entry in graphics using script?

DeltaV Live Variables

Tyler Bolick — Wed, 27 May 2026 18:57:18 GMT

Within DeltaV Live is there a way to pull the current workstations/terminal sessions area assignments from the assigned alarms and events?

Pulling the workstation name and even the session shouldn't be a problem, but is there a variable that can be read which contains this information? Is there a backwards way to get that information? Looking to check if an area is assigned to perform some conditional visibility functions.

Thanks in advance

Termination resistor for Serial Card Series 2 RS485 half-duplex 1300' / 400 M total, 3 nodes queried, 19200 baud

John Rezabek — Wed, 27 May 2026 18:50:10 GMT

Does anyone deploying serial RS485 networks include a 120 Ohm terminating resistor at the DeltaV Serial card terminals?

I've been communicating via Modbus RTU over RS485 for years and have never used any (either end) but the runs were shorter (more like 200 M) and baud rates were 9600.

Thanks,

John

Compatibility Inquiry – DeltaV Redundant Serial Interface Card HW Revision E vs G

DeltaV_User — Tue, 26 May 2026 09:20:27 GMT

Dear Members,

Technical clarification regarding compatibility of DeltaV redundant Serial Interface Cards installed in our running DeltaV system.

Existing healthy/redundant card details:

Model: KJ3241X1-BA1
Description: Serial Interface Card, 2 Port RS232/RS485, Redundant
Series: Series 2
Part Number: 12P2506X062
Hardware Revision: Rev G
Firmware/Software Revision observed in diagnostics: 1.53

Replacement card details:

Model: KJ3241X1-BA1
Description: Serial Interface Card, 2 Port RS232/RS485
Series: Series 2
Part Number: 12P2506X042
Hardware Revision: Rev E
Firmware/Software Revision observed in diagnostics: 1.19

System behavior after insertion of Rev E card into redundant pair:

DeltaV Diagnostics indicate the following:

HwRev = Unsupported
Model = Unknown Card Type
Status = Bad – Configuration Error
Switch_Avail = Unavailable – missing standby
Pair Integrity = BAD
Overall Integrity = BAD
State = Standby

Although the card is physically detected by the system, redundancy is not established and the card is reported as unsupported/unknown.

Additional information:

We currently have two (02) available cards with HW Revision E and P/N 12P2506X042.
Existing running card in service has HW Revision G with P/N 12P2506X062.
Both cards are labeled KJ3241X1-BA1 Series 2 Serial Interface Cards.

Kindly clarify the following:

Are P/N 12P2506X042 Rev E and P/N 12P2506X062 Rev G mutually compatible in redundant configuration?
Is HW Revision E supported in DeltaV version 12.3 ?
Can firmware/software of Rev E card be upgraded to achieve compatibility with Rev G card?
Is there any required DeltaV hotfix/service pack/device definition update for recognition of Rev E cards?
Can two HW Revision E cards operate together as a redundant pair independently?

Your technical guidance is highly appreciated.

DeltaV FXH Parser and index tool

Richard Canales — Fri, 22 May 2026 01:44:34 GMT

I created a FHX parser and put it on Git hub the README is pretty easy to follow if any one would like to check it out. It even creates an Index.html that you can run in any browser and dont need to host it just works

https://github.com/ricorick/deltav-database-parser

DeltaV Live Search

Kenneth Simpton — Thu, 21 May 2026 19:53:50 GMT

In the search function for DeltaV Live, version 15, is it possible to modify the font without affecting the menu hierarchy? Increasing the font for the menu hierarchy makes anything typed into the search function too large for the text box. Is it possible to uncouple the two fonts?

Operator Workstation Runtime Shows Empty Data Paths After Rebuild – No Server Access

Gustavo Frank — Thu, 21 May 2026 17:17:24 GMT

Hello everyone,

I'm troubleshooting an issue on a DeltaV Operator Workstation (v14.3.1) and would appreciate any insights.

Here is what I did step by step:

1. Formatted the workstation using the recovery media

2. Renamed the machine and joined it to the domain

3. Installed DeltaV

4. Completed the workstation configuration

5. Transferred the graphics folder from an identical operator station (attempted pic-by-pic, the full pics folder, and the full graphics folder)

6. Downloaded the station

Diagnostics show no issues.

The problem: When I open the Runtime, all my displays load correctly, but every data path is blank — all parameter fields show as empty boxes. Additionally, when I attempt to browse a data path, I get an error stating that I don't have access to the server.

It is worth noting that the other operator station (from which the graphics were transferred) is working normally, and so is the ProfessionalPLUS station.

Has anyone encountered this before? Any help is greatly appreciated.

Thank you.

DeltaV v11.3 PROFIBUS communication active but integrity BAD

Carlos Cortazar Castaño — Thu, 21 May 2026 15:24:21 GMT

I have a DeltaV v11.3 system with PROFIBUS DP Series 2 cards. The system was working normally until a power outage occurred early in the morning.

After power recovery, operators started getting a popup related to Batch Arbitration Control saying that no Executive Node could be found for the control. The popup kept reappearing multiple times before finally stopping.

Since then, we have an active alarm:
ADVISE [MULT] IO: DEVICEERROR - PROFIBUS CARD, C05,P01

In Diagnostics, the PROFIBUS port P01 shows:

BAD integrity
“Pic Device Error”

However, the strange part is that the PROFIBUS card, port, and devices are still detected correctly, and process variables coming from that segment are still updating in DeltaV. So communication does not appear to be completely lost.

The PROPLUS server has already been rebooted, but the issue remains exactly the same. The controller/TRULOGIC hosting the PROFIBUS card has not been rebooted yet.

Has anyone experienced something similar after a power outage in DeltaV v11.3? Any recommendations before rebooting the controller?

Additionally, I have this reference image showing how the diagnostics section appears.

Thanks.

DeltaV Graphics at the L3/L4

David-m.walker — Wed, 20 May 2026 09:27:13 GMT

The recent conversation about the automation architecture prompted me to wonder what people think about accessing DeltaV Graphics at the L3/L4 layer.

The reason I ask is because I've just got my hands on the first release of DeltaV Live Enterprise View.

This uses the DeltaV Edge Environment to display process graphics to anyone with a web browser.

If anyone has any comments I would appreciate the feedback to help me ensure my messaging is aligned with user requirements.

If you'd like to see DeltaV Live Enterprise View I'd be happy to run a demo session.

Thanks in advance,

Dave

PS: I work for Emerson.

Auto Logout a specific user or group of users from DeltaV Operate

s_brwn — Mon, 18 May 2026 16:46:20 GMT

Vers 13.3.1- PCSD, DeltaV Operate

How can I log out of DeltaV Operate (not windows)a particular user and/or group of users after X amount of time? My goal is to address someone with Tune privilege that forgot to logout or switch back to the operator user.

I don't want to log out of Windows but just DeltaV Operate.

I wasn't sure if there might be some type of script that can run in the background or ... that could trigger some code to log off?

Thanks

How To Upload Parameters From Multiple Modules at Once

jgrunschel — Fri, 15 May 2026 20:59:19 GMT

I might be losing my mind, but I remember being able to select multiple modules, right click, select "Upload", and the resulting dialog showed the uploadable parameters from ALL of the selected modules. Now (Version 15.LTS) I am only allowed to upload from one module at a time. If I select multiple modules (and all of them have uploads available), the contextual menu changes and doesn't even show "Upload" as an option.

I cannot properly put into words the magnitude of this loss in functionality. If this is truly the path forward, it is proof of yet another major company actually making their products worse when they think they are improving.

DeltaV v16 Roadmap: IT/OT Harmonization and Platform Decoupling

Vincent J. Scurria — Thu, 14 May 2026 16:37:33 GMT

With DeltaV v16, is Emerson’s roadmap moving toward greater decoupling of hardware, software, and system versions as part of a broader shift toward modernized, virtualized architectures?

In that context, is v16 intended to help drive a more harmonized IT/OT architecture across projects to support secure, resilient, and standardized operations at scale?

Specifically, are there defined or emerging standards for core infrastructure areas such as:

Active Directory integration
Network management and monitoring
Patch and update management
Backup and recovery architecture
Software lifecycle management

Additionally, how is Emerson addressing consistency in system deployments (e.g., virtual machine architectures and configurations), given that implementations can vary significantly between projects today?

More broadly, should users expect DeltaV to evolve toward a more standardized and repeatable platform model across deployments, or will these elements continue to be defined on a project-by-project basis?