https://emersonexchange365.com/community-hubs/deltav-community-connect/Control & Safety Systemsen-USTelligent Community 13https://emersonexchange365.com/community-hubs/deltav-community-connect/f/deltav-discussions-questions/2855/offline-dv-explorer-tool/25364Mon, 22 Jun 2026 19:41:00 GMTcd40bb2b-3d49-4868-939d-417119b40291:2c394422-0e2d-45c2-adda-1cfd43426869AbhiHi, Could you please let me know how I can get access to the FHX Viewer tool?https://emersonexchange365.com/community-hubs/deltav-community-connect/f/deltav-discussions-questions/11444/operator-workstation-runtime-shows-empty-data-paths-after-rebuild-no-server-access/25363Mon, 22 Jun 2026 05:10:00 GMTcd40bb2b-3d49-4868-939d-417119b40291:5373f22d-9bea-4d95-a536-df249f816c69Rishi PrajapatiTry the following: 1. Copy the entire YellowPages folder from Pro+ & overwrite it in the Operator Station. 2. Download this Operator Station from DV Explorer. Now this operator station should show all datalinks with proper real time values in DV Operate Run.https://emersonexchange365.com/community-hubs/deltav-community-connect/f/deltav-discussions-questions/11466/opc-hda-server-tag-unknown-to-dvch/25362Fri, 19 Jun 2026 18:32:00 GMTcd40bb2b-3d49-4868-939d-417119b40291:a44100f9-0ecb-49ef-84ad-6c197ba34b8bKentThanks for the quick response. The problem is that the error often, but not always, is for a tag from an AI block that feeds a PID block. The only time I historize a value from the AI block is if I'm filtering the PID PV and I also want to be able to see unfiltered as well as filtered data. There are also quite a few that are calling for OUT and SP from a DC! block when I only historize PV. Very puzzling.https://emersonexchange365.com/community-hubs/deltav-community-connect/f/deltav-discussions-questions/11466/opc-hda-server-tag-unknown-to-dvch/25361Fri, 19 Jun 2026 18:15:00 GMTcd40bb2b-3d49-4868-939d-417119b40291:3df81144-ea9f-455f-9d64-40722eb5f820Andre DicaireMy first thought is the history tag is different than what you think. The history tag can include or omit the .CV field. Or the parameter has been abstracted in the module to a module level internal reference, and FIC-101/AI1/PV is historized as FIC-101/PV (with or without CV). Check the Module's History Collection to confirm the tag is configured exactly as you are trying to read it. If configured, check it hasn't been disabled. You can also check the PHIST.SCR file located in the DVDATA/Download folder of the historian. This the downloaded runtime configuration of the historian, so if it's there, then you know the configuration database is in line. Hopefully, you find a discrepancy that explains what you are seeing. If the PHIST file has the tag as you are searching for it, we have a mystery and a call to the GSC is likely warranted. When using PHV to view history, DeltaV does not have a focused list of configured available history tag. You browse the entire name space, in case you want to trend a value in real time that is not historized. But if you don't know the historized tag path (syntax), you have to try variations or check the History collection of the tag. Wouldn't it be nice if you could enter or browse a tag and see select from the focused list of historized tags of that module? Hmm. Then you wouldn't have to guess the tag name or navigate the module parameter tree to get to the tag you think you want. good luck.https://emersonexchange365.com/community-hubs/deltav-community-connect/f/deltav-discussions-questions/11466/opc-hda-server-tag-unknown-to-dvchFri, 19 Jun 2026 15:53:00 GMTcd40bb2b-3d49-4868-939d-417119b40291:1bba2e0f-9c4a-4a4a-ac7a-0aebd1622848KentI'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.https://emersonexchange365.com/community-hubs/deltav-community-connect/f/deltav-discussions-questions/11465/new-delta-v-monitorsThu, 18 Jun 2026 20:16:00 GMTcd40bb2b-3d49-4868-939d-417119b40291:7db5f738-6f1c-4f4d-954c-5dfb6e0758dcSteven HarrisLooking to move from the Dell P2213 WXSGA+ to the larger 24" WUXGA screens. Has anyone experienced any problems doing that?https://emersonexchange365.com/community-hubs/deltav-community-connect/f/deltav-discussions-questions/11464/how-do-i-know-if-my-m-series-8-wide-carrier-was-manufactured-after-2002Tue, 16 Jun 2026 13:24:00 GMTcd40bb2b-3d49-4868-939d-417119b40291:28c50689-1763-494b-9e52-40768fdd0689Luis Alberto Navas GuzmanWe 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!https://emersonexchange365.com/community-hubs/deltav-community-connect/f/deltav-discussions-questions/11444/operator-workstation-runtime-shows-empty-data-paths-after-rebuild-no-server-access/25359Mon, 15 Jun 2026 16:23:00 GMTcd40bb2b-3d49-4868-939d-417119b40291:95dea891-7809-41d4-86f8-71b689bdf4e5Ralf BaginskiYou shouldn‘t copy the whole graphics folder from other workstations, in subfolder (can‘t remember the name) is a file which refer to the local network name. Maybe you can see this in configure mode on any picture file, do not open it, only right click and select properties. You should see the reference of this file refers to the workstation you copied the folder from. It‘s not easy to resolve this, as you have no backup of this file. May another workstation configuration helps or reinstall DeltaV. You should only copy the pic, Charts folder and the scheduler, layout files. Regards Ralfhttps://emersonexchange365.com/community-hubs/deltav-community-connect/f/deltav-discussions-questions/11462/batch-units-with-history-data-points/25356Thu, 11 Jun 2026 18:05:00 GMTcd40bb2b-3d49-4868-939d-417119b40291:a1b2dad8-3f55-40ab-87e9-b00bab5868f8Andre DicaireMy first thought is why would you want to capture discrete events like this in the Continuous Historian? That creates a significant license cost. Batch events would be captured in the Batch Historian, or you could trigger a LogEvent record in the EJournal. That records these events for free, and you can create a filtered PHV file to show relative information. I've also been playing with the SQL Data source in DeltaV Live to extract data from Ejournal to provide it in a Table Object in context within the HMI environment. Curious why you want this type of data captured in DVCH,https://emersonexchange365.com/community-hubs/deltav-community-connect/f/deltav-discussions-questions/11271/deltav-operate-embedded-web-browser-default-application/25355Thu, 11 Jun 2026 15:05:00 GMTcd40bb2b-3d49-4868-939d-417119b40291:145b93f8-1a3c-43da-ae25-2a58eeb69fc6Dustin BeebeThe WebAppBrowser OLE/ActiveX is tied to Internet Explorer. There is no system setting that will allow you to change this to Microsoft Edge. DeltaV Operate is an ActiveX/OLE environment which means you cannot embed the newer COM variant of WebView2. Sounds like a cool application that you are implementing. Just brainstorming here are a couple of ideas that might help get you to your goal. 1. Depending on the report you are presenting to the operator, you could make the report unprompted. I don't know if you are looking for pull up a standard time range for the operator (eg last shift, last 24 hours, last week, etc.) 2. You could add a page that frames the report to clean up the rendering issue with IE. The challenge you are seeing is that IE is not recognizing the correct page length or scroll bars are not enabled on the page. You can always reach out to the AgileOps team. They are super helpful. I know there are some significant reporting enhancements coming out in the next versions, so it might be worth a discussion. Thanks, -Dustinhttps://emersonexchange365.com/community-hubs/deltav-community-connect/f/deltav-discussions-questions/11460/deltav-v11-3-profibus-device-error-on-multiple-cards/25354Thu, 11 Jun 2026 12:01:00 GMTcd40bb2b-3d49-4868-939d-417119b40291:7b57491a-4d09-4114-8526-2b087f931ae5Rune ReppenhagenI think the best way to resolve this issue is to contact our Global Service Center so they can assist in debugging this.https://emersonexchange365.com/community-hubs/deltav-community-connect/f/deltav-discussions-questions/11457/cross-reference-tool-error/25352Thu, 11 Jun 2026 06:40:00 GMTcd40bb2b-3d49-4868-939d-417119b40291:b8b9019e-1468-4477-8638-ec76c6dbcc27Manuel BehrensHi, is this a DeltaV Tool? What is the benefit?https://emersonexchange365.com/community-hubs/deltav-community-connect/f/deltav-discussions-questions/11462/batch-units-with-history-data-pointsThu, 11 Jun 2026 06:36:00 GMTcd40bb2b-3d49-4868-939d-417119b40291:36d72c86-62c0-456f-96e1-652e50d4f598Manuel BehrensHi 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 } } }BatchID #DeltaVBatch #BatchconfigurationDeltaVBatchhttps://emersonexchange365.com/community-hubs/deltav-community-connect/f/deltav-discussions-questions/11460/deltav-v11-3-profibus-device-error-on-multiple-cardsWed, 10 Jun 2026 22:00:00 GMTcd40bb2b-3d49-4868-939d-417119b40291:2afeeb09-796c-4f00-acdf-0149dff0da0cCarlos Cortazar CastañoHi 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?ProfibusDeltaVhttps://emersonexchange365.com/community-hubs/deltav-community-connect/f/deltav-discussions-questions/11459/offline-factory-reset-on-a-fisher-dvc6200Wed, 10 Jun 2026 21:34:00 GMTcd40bb2b-3d49-4868-939d-417119b40291:c1c6af60-5099-49bb-91c6-01912f77feaaDan MosHas anyone been able to perform a factory reset on a Fieldbus DVC 6200f / DVC6000f Dev rev 4 that has been removed from a segment?https://emersonexchange365.com/community-hubs/deltav-community-connect/f/deltav-discussions-questions/8148/is-placing-pid-block-in-bypass-bumpless/25351Wed, 10 Jun 2026 14:06:00 GMTcd40bb2b-3d49-4868-939d-417119b40291:c6528d4d-d06e-4f2a-b5cb-4c67c2c7ba65MPHymelSomething funny is happening. I have an LC cascaded to an FC. Flowmeter is bad. Set FC to Bypass, but LC won't go to auto. I suspect due to the fact that the FC can't be put in CAS unless we simulate the flowmeter input, in which case we can then put the FC in Cas. I would have expected that the whole reason for using the bypass function would be for cases when the flowmeter is bad. Am i missing something? we're V15LTS, using PCSD, and i did check that bkcal_in is pointing to the flow controller bkcal_out.https://emersonexchange365.com/community-hubs/deltav-community-connect/f/deltav-discussions-questions/11456/licenses-needed-for-a-new-remote-session-in-an-existing-remote-server/25350Fri, 05 Jun 2026 22:07:00 GMTcd40bb2b-3d49-4868-939d-417119b40291:01f43488-5bd5-4904-bec1-80f5b458cbe5Mark FloresThere is an Operator Station, View-Only license (VE2110) which is available for v12.3 and above system only. Not sure what is your DeltaV System version and OS version. Kindly note the new TS CAL and User CAL licensing if you are using newer OS (Server 2016 above).https://emersonexchange365.com/community-hubs/deltav-community-connect/f/deltav-discussions-questions/11458/deltav-ai-card-burnout-direction-settingFri, 05 Jun 2026 16:07:00 GMTcd40bb2b-3d49-4868-939d-417119b40291:e2f07335-ef7a-4787-932a-3c7e9d05e6e8jgrunschelMost 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?burnout directionDeltaV #DCSfailure directionFailure ModeburnoutDeltaVhttps://emersonexchange365.com/community-hubs/deltav-community-connect/f/deltav-discussions-questions/11457/cross-reference-tool-errorFri, 05 Jun 2026 11:49:00 GMTcd40bb2b-3d49-4868-939d-417119b40291:5321daa1-435a-4125-aa65-4a60553b8a3eMohamed AlkhoulyHi 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.https://emersonexchange365.com/community-hubs/deltav-community-connect/f/deltav-discussions-questions/11456/licenses-needed-for-a-new-remote-session-in-an-existing-remote-serverFri, 05 Jun 2026 08:56:00 GMTcd40bb2b-3d49-4868-939d-417119b40291:6e749cce-e9ac-4e48-9fd5-ec0ab5b53886dikshitshDear 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