<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://emersonexchange365.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ovation Forum - Recent Threads</title><link>https://emersonexchange365.com/community-hubs/deltav-community-connect/f/ovation-discussions-questions</link><description /><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 12 Feb 2025 12:15:47 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://emersonexchange365.com/community-hubs/deltav-community-connect/f/ovation-discussions-questions" /><item><title>Reminder to all Ovation Users - Ovation Users' Group website</title><link>https://emersonexchange365.com/thread/11215?ContentTypeID=0</link><pubDate>Wed, 12 Feb 2025 12:15:47 GMT</pubDate><guid isPermaLink="false">cd40bb2b-3d49-4868-939d-417119b40291:150ca137-86de-4e0c-aeed-d9bd082248b6</guid><dc:creator>Greg Schirm</dc:creator><slash:comments>0</slash:comments><comments>https://emersonexchange365.com/thread/11215?ContentTypeID=0</comments><wfw:commentRss>https://emersonexchange365.com/community-hubs/deltav-community-connect/f/ovation-discussions-questions/11215/reminder-to-all-ovation-users---ovation-users-group-website/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;The Ovation Users&amp;#39; Group website (&lt;a id="" href="https://www.ovationusers.com/"&gt;https://www.ovationusers.com/&lt;/a&gt;) is the recommended site for obtaining useful support information including all of the Ovation user manuals, a forum dedicated exclusively to Ovation, and various other resources. Any individual employed by an organization which owns and/or operates an Emerson Ovation system is eligible to be&amp;nbsp;a member of the site.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://www.ovationusers.com/" rel="noopener noreferrer" target="_blank"&gt;Ovation Users&amp;#39; Group website &amp;gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a title="Ovation Users Group website" href="https://www.ovationusers.com/" rel="noopener noreferrer" target="_blank"&gt;&lt;img style="max-height:480px;max-width:640px;" alt=" " src="https://emersonexchange365.com/resized-image/__size/1280x960/__key/communityserver-discussions-components-files/51/Ovation_2D00_Users_2D00_Group.png" /&gt;&lt;/a&gt;&lt;/p&gt;</description></item><item><title>process historian in ovation</title><link>https://emersonexchange365.com/thread/11212?ContentTypeID=0</link><pubDate>Mon, 10 Feb 2025 14:21:29 GMT</pubDate><guid isPermaLink="false">cd40bb2b-3d49-4868-939d-417119b40291:15c50a62-daa7-4c00-bbe9-15c1f54818e0</guid><dc:creator>Dean Schneider</dc:creator><slash:comments>4</slash:comments><comments>https://emersonexchange365.com/thread/11212?ContentTypeID=0</comments><wfw:commentRss>https://emersonexchange365.com/community-hubs/deltav-community-connect/f/ovation-discussions-questions/11212/process-historian-in-ovation/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;A few days ago the historian started to show errors in the error log and the historian diagnostic tool shows that the partner, drop201, has &amp;quot;no response&amp;quot; and the main drop has the historian connection down message displayed.&amp;nbsp; The error log is showing that is is a RAIMA problem.&amp;nbsp; Killed orphan user is the description.&amp;nbsp; There are 4 error messages.&amp;nbsp; They repeat every 30 minutes.&lt;/p&gt;
&lt;p&gt;I am not sure why this has happened.&amp;nbsp; 1 point was added to the historian.&amp;nbsp; The point works.&amp;nbsp; All the other points are trendable and do not seem to have any problems.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Any suggestions or ideas about what has happened and how to fix it?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Dean.&lt;/p&gt;</description></item><item><title>RE: process historian in ovation</title><link>https://emersonexchange365.com/thread/24769?ContentTypeID=1</link><pubDate>Mon, 10 Feb 2025 22:52:50 GMT</pubDate><guid isPermaLink="false">cd40bb2b-3d49-4868-939d-417119b40291:5fb1d50e-4ba1-4a3c-a0bc-0be47da0d915</guid><dc:creator>Andre Dicaire</dc:creator><slash:comments>0</slash:comments><comments>https://emersonexchange365.com/thread/24769?ContentTypeID=1</comments><wfw:commentRss>https://emersonexchange365.com/community-hubs/deltav-community-connect/f/ovation-discussions-questions/11212/process-historian-in-ovation/rss?ContentTypeId=0</wfw:commentRss><description>I have no exposure to the Ovation system so I&amp;#39;m afraid I cannot help you with this issue.  If you have not done so, a GSC call is recommended.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: process historian in ovation</title><link>https://emersonexchange365.com/thread/24768?ContentTypeID=1</link><pubDate>Mon, 10 Feb 2025 19:55:21 GMT</pubDate><guid isPermaLink="false">cd40bb2b-3d49-4868-939d-417119b40291:98dd4aca-cbe9-4295-9e46-f4b88a88a54c</guid><dc:creator>Dean Schneider</dc:creator><slash:comments>1</slash:comments><comments>https://emersonexchange365.com/thread/24768?ContentTypeID=1</comments><wfw:commentRss>https://emersonexchange365.com/community-hubs/deltav-community-connect/f/ovation-discussions-questions/11212/process-historian-in-ovation/rss?ContentTypeId=0</wfw:commentRss><description>This is not delta-v it is an Ovation system.  The error log is the ovation error log from the historian drop, drop 160.  I attempted to send you a snipit from the error file on drop 160, the historian drop.  It did not seem to like the snipit.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: process historian in ovation</title><link>https://emersonexchange365.com/thread/24767?ContentTypeID=1</link><pubDate>Mon, 10 Feb 2025 19:51:33 GMT</pubDate><guid isPermaLink="false">cd40bb2b-3d49-4868-939d-417119b40291:5ba8c1a3-e133-49fe-ad5a-210b5c8fb8f5</guid><dc:creator>Dean Schneider</dc:creator><slash:comments>0</slash:comments><comments>https://emersonexchange365.com/thread/24767?ContentTypeID=1</comments><wfw:commentRss>https://emersonexchange365.com/community-hubs/deltav-community-connect/f/ovation-discussions-questions/11212/process-historian-in-ovation/rss?ContentTypeId=0</wfw:commentRss><description>This is not a delta-v system. It is ovation.  It is called the Ovation Process Historian.  The error log I am referring to is the Ovation error log on the historian drop, drop160.  To follow are some lines taken from the error log.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;Err dts=&amp;quot;02/10/25 11:42:22&amp;quot; dtl=&amp;quot;1739212942&amp;quot; source=&amp;quot;drop160&amp;quot; priority=&amp;quot;3&amp;quot; identifier=&amp;quot;RAIMA&amp;quot;&amp;gt;Killed Orphan User: r00001F9800794B, PID [8088], TID [476], Cmd: D:\OvHist\bin\OvhFaultAlert.exe FAULT 179 124 9 0&amp;lt;/Err&amp;gt;&lt;br /&gt;
&amp;lt;Err dts=&amp;quot;02/10/25 11:42:32&amp;quot; dtl=&amp;quot;1739212952&amp;quot; source=&amp;quot;drop160&amp;quot; priority=&amp;quot;3&amp;quot; identifier=&amp;quot;RAIMA&amp;quot;&amp;gt;Killed Orphan User: r0000261C005309, PID [9756], TID [7428], Cmd: D:\OvHist\bin\OvhFaultAlert.exe FAULT 179 126 9 0&amp;lt;/Err&amp;gt;&lt;br /&gt;
&amp;lt;Err dts=&amp;quot;02/10/25 11:42:42&amp;quot; dtl=&amp;quot;1739212962&amp;quot; source=&amp;quot;drop160&amp;quot; priority=&amp;quot;3&amp;quot; identifier=&amp;quot;RAIMA&amp;quot;&amp;gt;Killed Orphan User: r00002A8C006D22, PID [10892], TID [7376], Cmd: D:\OvHist\bin\OvhFaultAlert.exe FAULT 179 125 9 0&amp;lt;/Err&amp;gt;&lt;br /&gt;
&amp;lt;Err dts=&amp;quot;02/10/25 11:42:42&amp;quot; dtl=&amp;quot;1739212962&amp;quot; source=&amp;quot;drop160&amp;quot; priority=&amp;quot;3&amp;quot; identifier=&amp;quot;RAIMA&amp;quot;&amp;gt;Killed Orphan User: r00000DA000763A, PID [3488], TID [11164], Cmd: D:\OvHist\bin\OvhFaultAlert.exe FAULT 179 130 9 0&amp;lt;/Err&amp;gt;&lt;br /&gt;
&amp;lt;Err dts=&amp;quot;02/10/25 12:12:22&amp;quot; dtl=&amp;quot;1739214742&amp;quot; source=&amp;quot;drop160&amp;quot; priority=&amp;quot;3&amp;quot; identifier=&amp;quot;RAIMA&amp;quot;&amp;gt;Killed Orphan User: r000000CC007E12, PID [204], TID [872], Cmd: D:\OvHist\bin\OvhFaultAlert.exe FAULT 179 124 9 0&amp;lt;/Err&amp;gt;&lt;br /&gt;
&amp;lt;Err dts=&amp;quot;02/10/25 12:12:32&amp;quot; dtl=&amp;quot;1739214752&amp;quot; source=&amp;quot;drop160&amp;quot; priority=&amp;quot;3&amp;quot; identifier=&amp;quot;RAIMA&amp;quot;&amp;gt;Killed Orphan User: r000023C0008A3E, PID [9152], TID [9024], Cmd: D:\OvHist\bin\OvhFaultAlert.exe FAULT 179 126 9 0&amp;lt;/Err&amp;gt;&lt;br /&gt;
&amp;lt;Err dts=&amp;quot;02/10/25 12:12:42&amp;quot; dtl=&amp;quot;1739214762&amp;quot; source=&amp;quot;drop160&amp;quot; priority=&amp;quot;3&amp;quot; identifier=&amp;quot;RAIMA&amp;quot;&amp;gt;Killed Orphan User: r00000EA8005941, PID [3752], TID [1112], Cmd: D:\OvHist\bin\OvhFaultAlert.exe FAULT 179 125 9 0&amp;lt;/Err&amp;gt;&lt;br /&gt;
&amp;lt;Err dts=&amp;quot;02/10/25 12:12:42&amp;quot; dtl=&amp;quot;1739214762&amp;quot; source=&amp;quot;drop160&amp;quot; priority=&amp;quot;3&amp;quot; identifier=&amp;quot;RAIMA&amp;quot;&amp;gt;Killed Orphan User: r00002B1000741B, PID [11024], TID [2264], Cmd: D:\OvHist\bin\OvhFaultAlert.exe FAULT 179 130 9 0&amp;lt;/Err&amp;gt;&lt;br /&gt;
&amp;lt;Err dts=&amp;quot;02/10/25 12:42:22&amp;quot; dtl=&amp;quot;1739216542&amp;quot; source=&amp;quot;drop160&amp;quot; priority=&amp;quot;3&amp;quot; identifier=&amp;quot;RAIMA&amp;quot;&amp;gt;Killed Orphan User: r000000E400813B, PID [228], TID [936], Cmd: D:\OvHist\bin\OvhFaultAlert.exe FAULT 179 124 9 0&amp;lt;/Err&amp;gt;&lt;br /&gt;
&amp;lt;Err dts=&amp;quot;02/10/25 12:42:32&amp;quot; dtl=&amp;quot;1739216552&amp;quot; source=&amp;quot;drop160&amp;quot; priority=&amp;quot;3&amp;quot; identifier=&amp;quot;RAIMA&amp;quot;&amp;gt;Killed Orphan User: r000027C4007C4B, PID [10180], TID [3188], Cmd: D:\OvHist\bin\OvhFaultAlert.exe FAULT 179 126 9 0&amp;lt;/Err&amp;gt;&lt;br /&gt;
&amp;lt;Err dts=&amp;quot;02/10/25 12:42:42&amp;quot; dtl=&amp;quot;1739216562&amp;quot; source=&amp;quot;drop160&amp;quot; priority=&amp;quot;3&amp;quot; identifier=&amp;quot;RAIMA&amp;quot;&amp;gt;Killed Orphan User: r000027F4006E64, PID [10228], TID [9932], Cmd: D:\OvHist\bin\OvhFaultAlert.exe FAULT 179 125 9 0&amp;lt;/Err&amp;gt;&lt;br /&gt;
&amp;lt;Err dts=&amp;quot;02/10/25 12:42:42&amp;quot; dtl=&amp;quot;1739216562&amp;quot; source=&amp;quot;drop160&amp;quot; priority=&amp;quot;3&amp;quot; identifier=&amp;quot;RAIMA&amp;quot;&amp;gt;Killed Orphan User: r00002A38005C2F, PID [10808], TID [7712], Cmd: D:\OvHist\bin\OvhFaultAlert.exe FAULT 179 130 9 0&amp;lt;/Err&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Does this help you?&lt;br /&gt;
&lt;br /&gt;
Dean.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: process historian in ovation</title><link>https://emersonexchange365.com/thread/24765?ContentTypeID=1</link><pubDate>Mon, 10 Feb 2025 18:30:01 GMT</pubDate><guid isPermaLink="false">cd40bb2b-3d49-4868-939d-417119b40291:39bec05a-65fc-423f-9d73-de779b3f96b0</guid><dc:creator>Andre Dicaire</dc:creator><slash:comments>1</slash:comments><comments>https://emersonexchange365.com/thread/24765?ContentTypeID=1</comments><wfw:commentRss>https://emersonexchange365.com/community-hubs/deltav-community-connect/f/ovation-discussions-questions/11212/process-historian-in-ovation/rss?ContentTypeId=0</wfw:commentRss><description>What Historian are you using?  DVCH, Advanced Historian, PI Enterprise?  The default DVCH historian does not support redundancy, so the referenced to the &amp;quot;partner, Drop201&amp;quot; doesn&amp;#39;t make sense to me.  DeltaV also does not support redundancy on the Advanced Historian either, which is based on PI.  Redundant Historians are supported with an Enterprise Historian, but I believe this is an AVEVA PI feature.  &lt;br /&gt;
&lt;br /&gt;
Which Error Log are you referring to?  Is this a Windows/Application log or other?  Maybe provide a more detailed example of the log content.  &amp;quot;RAIMA problem&amp;quot; is not something I&amp;#39;ve come across on the DeltaV Historians.  &lt;br /&gt;
&lt;br /&gt;
If this is relating to DVCH or Advanced Historian, which are both installed from DeltaV media on an App Station, you should log a call with GSC.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to automatically assign Areas to Alarm and Events?del</title><link>https://emersonexchange365.com/thread/24614?ContentTypeID=1</link><pubDate>Fri, 15 Nov 2024 06:53:59 GMT</pubDate><guid isPermaLink="false">cd40bb2b-3d49-4868-939d-417119b40291:956404c2-a0da-4fce-a662-69ac9c654ee7</guid><dc:creator>Valentin Borsu</dc:creator><slash:comments>0</slash:comments><comments>https://emersonexchange365.com/thread/24614?ContentTypeID=1</comments><wfw:commentRss>https://emersonexchange365.com/community-hubs/deltav-community-connect/f/ovation-discussions-questions/11155/how-to-automatically-assign-areas-to-alarm-and-events-del/rss?ContentTypeId=0</wfw:commentRss><description>Thanks Andre. I will look into this. I appreciate your help.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>How to automatically assign Areas to Alarm and Events?del</title><link>https://emersonexchange365.com/thread/11155?ContentTypeID=0</link><pubDate>Thu, 14 Nov 2024 08:48:25 GMT</pubDate><guid isPermaLink="false">cd40bb2b-3d49-4868-939d-417119b40291:9e2afd0f-c0a7-41f3-bf18-93ac56f3eb0c</guid><dc:creator>Valentin Borsu</dc:creator><slash:comments>2</slash:comments><comments>https://emersonexchange365.com/thread/11155?ContentTypeID=0</comments><wfw:commentRss>https://emersonexchange365.com/community-hubs/deltav-community-connect/f/ovation-discussions-questions/11155/how-to-automatically-assign-areas-to-alarm-and-events-del/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hello Folks,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;Is there a way to assign new Areas to &lt;em&gt;Stations&lt;/em&gt;/Alarm and Events in a faster way than manually on each and every one of them? Is there a script/utility out there that could improve this manual process? I would really appreaciate your help.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thank you,&lt;/p&gt;
&lt;p&gt;Valentin&lt;/p&gt;</description></item><item><title>RE: How to automatically assign Areas to Alarm and Events?del</title><link>https://emersonexchange365.com/thread/24611?ContentTypeID=1</link><pubDate>Thu, 14 Nov 2024 16:21:08 GMT</pubDate><guid isPermaLink="false">cd40bb2b-3d49-4868-939d-417119b40291:ed8e0da8-f1df-48cb-8663-5cc04bcaeea2</guid><dc:creator>Andre Dicaire</dc:creator><slash:comments>1</slash:comments><comments>https://emersonexchange365.com/thread/24611?ContentTypeID=1</comments><wfw:commentRss>https://emersonexchange365.com/community-hubs/deltav-community-connect/f/ovation-discussions-questions/11155/how-to-automatically-assign-areas-to-alarm-and-events-del/rss?ContentTypeId=0</wfw:commentRss><description>Not finding anything like this.  Bulk Edit does not appear to support the workstation components.  That would have been nice.  It may be possible to create a format file but all I&amp;#39;m seeing is the Alarm and Event container is not supported for bulk edit.&lt;br /&gt;
&lt;br /&gt;
Once long ago, before bulk edit supported history, I was able to manually create a bulk edit format FHX to configure the History parameters on a module.  Hmm.  So, I tried this for the Alarm areas, and it works.  Totally not supported.  Basically, I looked at the format of a Bulk Edit Import FHX that is created in the Bulk edit folder.  I exported a supported node type (CIOC) with CIOC.FMT and then imported it.  The import creates the LastImport FHX, which shows the syntax of the import, where the main item is flagged with merge=T.  I compared this to a full export of the CIOC, and then used a Full export of the Workstation to create a matching syntax.  Saved this as an FHX and then imported it as a Standard FHX (not user defined).&lt;br /&gt;
&lt;br /&gt;
The Plant area assignments are defined in the OPERATOR_SUBSYSTEM phrase.  The entire FHX looks like this:&lt;br /&gt;
SCHEMA&lt;br /&gt;
{&lt;br /&gt;
  MAJOR_VERSION=14&lt;br /&gt;
  MINOR_VERSION=3&lt;br /&gt;
  MAINTENANCE_VERSION=1&lt;br /&gt;
  BUILD_VERSION=7332&lt;br /&gt;
  BUILD_ID=&amp;quot;xr&amp;quot;&lt;br /&gt;
  VERSION_STR=&amp;quot;14.3.1.7332.xr&amp;quot;&lt;br /&gt;
}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
OPERATOR_NODE NAME=&amp;quot;WKSNAME&amp;quot;merge=T&lt;br /&gt;
{&lt;br /&gt;
  DESCRIPTION=&amp;quot;Large Screen Station &amp;quot;&lt;br /&gt;
  OPERATOR_SUBSYSTEM&lt;br /&gt;
  {&lt;br /&gt;
    ENABLED=T&lt;br /&gt;
    GLOBAL_ALARM_ACK_GROUP=1&lt;br /&gt;
    RESTRICT_WRITES_TO_AREAS=F&lt;br /&gt;
    AREA { NAME=&amp;quot;AREA_A&amp;quot; }&lt;br /&gt;
    AREA { NAME=&amp;quot;HARDWARE&amp;quot; }&lt;br /&gt;
    AREA { NAME=&amp;quot;BATCH&amp;quot; }&lt;br /&gt;
    AREA { NAME=&amp;quot;DEVICES&amp;quot; }&lt;br /&gt;
  }&lt;br /&gt;
}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
I&amp;#39;m thinking one would be able to map this out into a FMT file.  I couldn&amp;#39;t find how to create that FMT from the bulk edit tools, which would really be the way to go.&lt;br /&gt;
&lt;br /&gt;
Note that this file cannot create a workstation nor can it delete any defined areas in your configuratoin.  It can only add AREAs to the named workstation.&lt;br /&gt;
&lt;br /&gt;
Note II:  the Area must exist in the database for this import to add it to the workstation&amp;#39;s Alarm and Event container.  &lt;br /&gt;
&lt;br /&gt;
I copied the Schema header from a valid Bulk Edit LastImport.fhx to get the right syntax version information of my system, which is v14.3.1.&lt;br /&gt;
&lt;br /&gt;
So where can we go from here?  Well, an Excel spreadsheet could be created, and a script written to create this FHX file, with multiple rows that define the desired Plant Areas for each workstation.  List your plat areas across the top and the Stations down the left and fill in the matrix of what areas go to what stations.  Then, run the script and build the above phrase for each station. result would look like:&lt;br /&gt;
&lt;br /&gt;
SCHEMA&lt;br /&gt;
{&lt;br /&gt;
  MAJOR_VERSION=14&lt;br /&gt;
  MINOR_VERSION=3&lt;br /&gt;
  MAINTENANCE_VERSION=1&lt;br /&gt;
  BUILD_VERSION=7332&lt;br /&gt;
  BUILD_ID=&amp;quot;xr&amp;quot;&lt;br /&gt;
  VERSION_STR=&amp;quot;14.3.1.7332.xr&amp;quot;&lt;br /&gt;
}&lt;br /&gt;
OPERATOR_NODE NAME=&amp;quot;WKSNAME1&amp;quot;merge=T&lt;br /&gt;
{&lt;br /&gt;
  OPERATOR_SUBSYSTEM&lt;br /&gt;
  {&lt;br /&gt;
    AREA { NAME=&amp;quot;AREA_A&amp;quot; }&lt;br /&gt;
    AREA { NAME=&amp;quot;HARDWARE&amp;quot; }&lt;br /&gt;
    AREA { NAME=&amp;quot;NEWAREA&amp;quot; }&lt;br /&gt;
    AREA { NAME=&amp;quot;DEVICES&amp;quot; }&lt;br /&gt;
  }&lt;br /&gt;
}&lt;br /&gt;
OPERATOR_NODE NAME=&amp;quot;WKSNAME2&amp;quot;merge=T&lt;br /&gt;
{&lt;br /&gt;
  OPERATOR_SUBSYSTEM&lt;br /&gt;
  {&lt;br /&gt;
    AREA { NAME=&amp;quot;AREA_A&amp;quot; }&lt;br /&gt;
    AREA { NAME=&amp;quot;HARDWARE&amp;quot; }&lt;br /&gt;
    AREA { NAME=&amp;quot;BATCH&amp;quot; }&lt;br /&gt;
    AREA { NAME=&amp;quot;NEWAREA&amp;quot; } &lt;br /&gt;
    AREA { NAME=&amp;quot;DEVICES&amp;quot; }&lt;br /&gt;
  }&lt;br /&gt;
}&lt;br /&gt;
OPERATOR_NODE NAME=&amp;quot;WKSNAME3&amp;quot;merge=T&lt;br /&gt;
{&lt;br /&gt;
  OPERATOR_SUBSYSTEM&lt;br /&gt;
  {&lt;br /&gt;
    AREA { NAME=&amp;quot;AREA_A&amp;quot; }&lt;br /&gt;
    AREA { NAME=&amp;quot;HARDWARE&amp;quot; }&lt;br /&gt;
    AREA { NAME=&amp;quot;BATCH&amp;quot; }&lt;br /&gt;
    AREA { NAME=&amp;quot;DEVICES&amp;quot; }&lt;br /&gt;
  }&lt;br /&gt;
}&lt;br /&gt;
&lt;br /&gt;
This would leave you with an Excel sheet to manage the assigned areas of all defined workstations.  That gives you visibility of the system as a whole and an easy way to assign a new Plant area to as many workstations as you need.  &lt;br /&gt;
&lt;br /&gt;
added enhancements:&lt;br /&gt;
- Add a column to select which workstations to update so the created FHX only contains those nodes.&lt;br /&gt;
- add a function to parse an FHX file and populate the spreadsheet, both the row of existing Plant Area Names and the workstations where they are currently defined.&lt;br /&gt;
- add a function that parses an FHX file and identifies any discrepancies between the database and this file.  This would show if areas are assigned that you don&amp;#39;t want and areas you want that are not yet assigned.  &lt;br /&gt;
&lt;br /&gt;
Bulk Edit might not work for this as each station can have a varying number of areas.  The format file requires a fixed number of columns and isn&amp;#39;t intended to handle a different number of items per row. It would work to add one Area to multiple workstations.  I don&amp;#39;t know if that would be all that useful.  Maybe someone has a FMT file already they could share.  There can be up to 250 plant areas.  If you made the format for 250 columns, would it handle blank cells?  I don&amp;#39;t know.  &lt;br /&gt;
&lt;br /&gt;
If your handy with Excel VBA scripts, this would not be hard to accomplish.  If I have time, I think I&amp;#39;ll try to create these scripts and see how use full it is.  A similar sheet would be useful to manage User Span of control, but I have no idea (yet) how that would look like...&lt;br /&gt;
&lt;br /&gt;
Sounds like a pretty decent UDEP request, no?&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Block for greater than or equal to</title><link>https://emersonexchange365.com/thread/24608?ContentTypeID=1</link><pubDate>Wed, 13 Nov 2024 09:15:49 GMT</pubDate><guid isPermaLink="false">cd40bb2b-3d49-4868-939d-417119b40291:1c284825-6d14-4fe1-ae29-f9e73faba6cc</guid><dc:creator>Kenneth Yashim</dc:creator><slash:comments>0</slash:comments><comments>https://emersonexchange365.com/thread/24608?ContentTypeID=1</comments><wfw:commentRss>https://emersonexchange365.com/community-hubs/deltav-community-connect/f/ovation-discussions-questions/2560/block-for-greater-than-or-equal-to/rss?ContentTypeId=0</wfw:commentRss><description>Ovationm 3.8 has HIGHLOWMON function with High setpoint &amp;amp; Low Setpoint&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Block for greater than or equal to</title><link>https://emersonexchange365.com/thread/2560?ContentTypeID=0</link><pubDate>Mon, 18 Feb 2013 06:36:19 GMT</pubDate><guid isPermaLink="false">cd40bb2b-3d49-4868-939d-417119b40291:9e295196-9f41-4160-a4d2-05ce02a7e194</guid><dc:creator>Anonymous</dc:creator><slash:comments>7</slash:comments><comments>https://emersonexchange365.com/thread/2560?ContentTypeID=0</comments><wfw:commentRss>https://emersonexchange365.com/community-hubs/deltav-community-connect/f/ovation-discussions-questions/2560/block-for-greater-than-or-equal-to/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;I would like to know the name of block which shall act as a function of Greater than or equal to (&amp;gt;=). For example, Set point is 50. &amp;nbsp;if IN1 = 50 then output = 1. if IN1 = 51 then output = 1. Software is Ovation 3.3&lt;/p&gt;</description></item><item><title>Ovation Network Protocols/Ports</title><link>https://emersonexchange365.com/thread/11153?ContentTypeID=0</link><pubDate>Fri, 08 Nov 2024 16:05:16 GMT</pubDate><guid isPermaLink="false">cd40bb2b-3d49-4868-939d-417119b40291:cad79363-58af-48b7-9d39-2486bbac0f8b</guid><dc:creator>Dominick Tardogno</dc:creator><slash:comments>2</slash:comments><comments>https://emersonexchange365.com/thread/11153?ContentTypeID=0</comments><wfw:commentRss>https://emersonexchange365.com/community-hubs/deltav-community-connect/f/ovation-discussions-questions/11153/ovation-network-protocols-ports/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Greetings!&lt;/p&gt;
&lt;p&gt;I am a researcher working to develop a Wireshark dissector chain to perform security analysis in an Ovation network.&lt;/p&gt;
&lt;p&gt;I need information regarding proprietary packet formats, fields therein, default ports, and generally any technical details regarding network traffic in this environment.&lt;/p&gt;
&lt;p&gt;Thanks for any help!&lt;/p&gt;</description></item><item><title>RE: Ovation Network Protocols/Ports</title><link>https://emersonexchange365.com/thread/24607?ContentTypeID=1</link><pubDate>Tue, 12 Nov 2024 13:04:57 GMT</pubDate><guid isPermaLink="false">cd40bb2b-3d49-4868-939d-417119b40291:8d1028ef-4714-44e5-bab6-166e9610dd18</guid><dc:creator>Dominick Tardogno</dc:creator><slash:comments>0</slash:comments><comments>https://emersonexchange365.com/thread/24607?ContentTypeID=1</comments><wfw:commentRss>https://emersonexchange365.com/community-hubs/deltav-community-connect/f/ovation-discussions-questions/11153/ovation-network-protocols-ports/rss?ContentTypeId=0</wfw:commentRss><description>Andre, thanks for the response.&lt;br /&gt;
I think my question is misunderstood - my wording was poor.&lt;br /&gt;
&lt;br /&gt;
I understand that &amp;#39;proprietary&amp;#39; information should not be published here.&lt;br /&gt;
&lt;br /&gt;
My intent was to ask what knowledge or details are publicly available regarding Emerson Ovation &amp;#39;custom&amp;#39; protocols in an Ovation system.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Ovation Network Protocols/Ports</title><link>https://emersonexchange365.com/thread/24605?ContentTypeID=1</link><pubDate>Fri, 08 Nov 2024 17:00:55 GMT</pubDate><guid isPermaLink="false">cd40bb2b-3d49-4868-939d-417119b40291:1776a970-80ed-4764-90c0-bc9ed5dc2bda</guid><dc:creator>Andre Dicaire</dc:creator><slash:comments>1</slash:comments><comments>https://emersonexchange365.com/thread/24605?ContentTypeID=1</comments><wfw:commentRss>https://emersonexchange365.com/community-hubs/deltav-community-connect/f/ovation-discussions-questions/11153/ovation-network-protocols-ports/rss?ContentTypeId=0</wfw:commentRss><description>Hey Dominick, my first impression is &amp;quot;who would ask for proprietary packet formats&amp;quot; about a DCS on a public forum?  My one and only reaction is this must be a hacker.  &lt;br /&gt;
&lt;br /&gt;
If this is legit, I&amp;#39;d say you need to be more discreet about what you ask for, and make contact directly with Emerson.  This forum is by no means secure.  No one should be posting Emerson proprietary data here.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Ovation DCS</title><link>https://emersonexchange365.com/thread/23511?ContentTypeID=1</link><pubDate>Mon, 17 Jul 2023 17:55:42 GMT</pubDate><guid isPermaLink="false">cd40bb2b-3d49-4868-939d-417119b40291:47a3666f-9757-4fc9-a42d-549cf71397ce</guid><dc:creator>Yzn_Lafi</dc:creator><slash:comments>0</slash:comments><comments>https://emersonexchange365.com/thread/23511?ContentTypeID=1</comments><wfw:commentRss>https://emersonexchange365.com/community-hubs/deltav-community-connect/f/ovation-discussions-questions/10764/ovation-dcs/rss?ContentTypeId=0</wfw:commentRss><description>In this case I believe you can try to get the time using SNMP on DBS, you need the MIB file of the NTP server then mirror the time data using SNMP and copy the time to multiple packed points then compare it by building a simple logic sheet and generate the alarm on the difference, I have never did it but on paper is shall work !&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Ovation DCS</title><link>https://emersonexchange365.com/thread/10764?ContentTypeID=0</link><pubDate>Mon, 17 Jul 2023 16:53:28 GMT</pubDate><guid isPermaLink="false">cd40bb2b-3d49-4868-939d-417119b40291:6ac1c695-9369-4357-9602-44f9f4c503ed</guid><dc:creator>Priyanka Srivastava </dc:creator><slash:comments>4</slash:comments><comments>https://emersonexchange365.com/thread/10764?ContentTypeID=0</comments><wfw:commentRss>https://emersonexchange365.com/community-hubs/deltav-community-connect/f/ovation-discussions-questions/10764/ovation-dcs/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hello Everyone,&lt;br /&gt;Is there any provision in Ovation DCS thru which any notification or altert can be configured if system is not in sync with NTP server timing.&lt;/p&gt;</description></item><item><title>RE: Ovation DCS</title><link>https://emersonexchange365.com/thread/23510?ContentTypeID=1</link><pubDate>Mon, 17 Jul 2023 17:33:39 GMT</pubDate><guid isPermaLink="false">cd40bb2b-3d49-4868-939d-417119b40291:f55bdd84-c203-4df2-8f6c-d315427a1a12</guid><dc:creator>Priyanka Srivastava </dc:creator><slash:comments>1</slash:comments><comments>https://emersonexchange365.com/thread/23510?ContentTypeID=1</comments><wfw:commentRss>https://emersonexchange365.com/community-hubs/deltav-community-connect/f/ovation-discussions-questions/10764/ovation-dcs/rss?ContentTypeId=0</wfw:commentRss><description>This window command I am using to monitor the difference between local time and NTP time. &lt;br /&gt;
Pls let me know if there is any way to get notification thru altert/alarm whenever DCS system ( database server) gets out of sync from NTP server timing...&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: ovation 3.6 connection for database fail.</title><link>https://emersonexchange365.com/thread/23509?ContentTypeID=1</link><pubDate>Mon, 17 Jul 2023 17:27:46 GMT</pubDate><guid isPermaLink="false">cd40bb2b-3d49-4868-939d-417119b40291:c5a81c81-cfdc-400e-9f48-ae67404c6475</guid><dc:creator>Yzn_Lafi</dc:creator><slash:comments>0</slash:comments><comments>https://emersonexchange365.com/thread/23509?ContentTypeID=1</comments><wfw:commentRss>https://emersonexchange365.com/community-hubs/deltav-community-connect/f/ovation-discussions-questions/10592/ovation-3-6-connection-for-database-fail/rss?ContentTypeId=0</wfw:commentRss><description>Try rest the Ovation system registration agent service, it shall work.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>ovation 3.6 connection for database fail.</title><link>https://emersonexchange365.com/thread/10592?ContentTypeID=0</link><pubDate>Sun, 12 Mar 2023 05:33:37 GMT</pubDate><guid isPermaLink="false">cd40bb2b-3d49-4868-939d-417119b40291:170a6c15-2fc7-4a08-92fb-186da344db7b</guid><dc:creator>ivan lishuk</dc:creator><slash:comments>1</slash:comments><comments>https://emersonexchange365.com/thread/10592?ContentTypeID=0</comments><wfw:commentRss>https://emersonexchange365.com/community-hubs/deltav-community-connect/f/ovation-discussions-questions/10592/ovation-3-6-connection-for-database-fail/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;hello&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I&amp;nbsp;have installed Ovation 3.6.0&lt;/p&gt;
&lt;p&gt;Here is the issue we faced now.&lt;/p&gt;
&lt;p&gt;my&amp;nbsp;system is still operating normally but &amp;nbsp;we can not access Developer Studio.&lt;/p&gt;
&lt;p&gt;It alert that &amp;quot; Connecting to database failed&amp;quot; Code: 0x80004005&lt;/p&gt;
&lt;p&gt;all services running good.&lt;/p&gt;
&lt;p&gt;Please help us &amp;nbsp;troubleshoot this issue!&lt;/p&gt;
&lt;p&gt;Thank You very much!&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:480px;max-width:640px;" alt=" " src="https://emersonexchange365.com/resized-image/__size/1280x960/__key/communityserver-discussions-components-files/51/Screenshot-2023_2D00_02_2D00_26-150504.jpg" /&gt;&lt;img style="max-height:480px;max-width:640px;" alt=" " src="https://emersonexchange365.com/resized-image/__size/1280x960/__key/communityserver-discussions-components-files/51/Screenshot-2023_2D00_02_2D00_26-150636.jpg" /&gt;&lt;img style="max-height:480px;max-width:640px;" alt=" " src="https://emersonexchange365.com/resized-image/__size/1280x960/__key/communityserver-discussions-components-files/51/Screenshot-2023_2D00_02_2D00_26-150619.jpg" /&gt;&lt;/p&gt;</description></item><item><title>RE: Ovation DCS</title><link>https://emersonexchange365.com/thread/23508?ContentTypeID=1</link><pubDate>Mon, 17 Jul 2023 17:24:55 GMT</pubDate><guid isPermaLink="false">cd40bb2b-3d49-4868-939d-417119b40291:1c8137f5-c518-47ad-bca4-f54f0d79c5bb</guid><dc:creator>Yzn_Lafi</dc:creator><slash:comments>0</slash:comments><comments>https://emersonexchange365.com/thread/23508?ContentTypeID=1</comments><wfw:commentRss>https://emersonexchange365.com/community-hubs/deltav-community-connect/f/ovation-discussions-questions/10764/ovation-dcs/rss?ContentTypeId=0</wfw:commentRss><description>This will show the time difference between NTP and DBS&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Ovation DCS</title><link>https://emersonexchange365.com/thread/23507?ContentTypeID=1</link><pubDate>Mon, 17 Jul 2023 17:24:01 GMT</pubDate><guid isPermaLink="false">cd40bb2b-3d49-4868-939d-417119b40291:663102c3-f522-43d0-8e98-ce9336df14f7</guid><dc:creator>Yzn_Lafi</dc:creator><slash:comments>2</slash:comments><comments>https://emersonexchange365.com/thread/23507?ContentTypeID=1</comments><wfw:commentRss>https://emersonexchange365.com/community-hubs/deltav-community-connect/f/ovation-discussions-questions/10764/ovation-dcs/rss?ContentTypeId=0</wfw:commentRss><description>On DBS open the command prompt and type:&lt;br /&gt;
W32tm /stripchart /computer:NTP Ip address&lt;br /&gt;
&lt;br /&gt;
For example, if the NTP server IP address is 192.168.3.100, then :&lt;br /&gt;
W32tm /stripchart /computer:192.168.3.100&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Engineering Workstation communication issue with OPC and Operator Workstation DROPs
We have following DROPs for our UNIT-2 on OVATION DCS 3.6</title><link>https://emersonexchange365.com/thread/10585?ContentTypeID=0</link><pubDate>Thu, 09 Mar 2023 05:29:40 GMT</pubDate><guid isPermaLink="false">cd40bb2b-3d49-4868-939d-417119b40291:0d1f3a9f-a52b-4316-ab08-e0cfa7aa067c</guid><dc:creator>ivan lishuk</dc:creator><slash:comments>0</slash:comments><comments>https://emersonexchange365.com/thread/10585?ContentTypeID=0</comments><wfw:commentRss>https://emersonexchange365.com/community-hubs/deltav-community-connect/f/ovation-discussions-questions/10585/engineering-workstation-communication-issue-with-opc-and-operator-workstation-drops-we-have-following-drops-for-our-unit-2-on-ovation-dcs-3-6/rss?ContentTypeId=0</wfw:commentRss><description>&lt;h3 class="name"&gt;&lt;span&gt;Engineering Workstation communication issue with OPC and Operator Workstation DROPs&lt;/span&gt;&lt;/h3&gt;
&lt;div class="content"&gt;
&lt;p&gt;We have following DROPs for our UNIT-2 on OVATION DCS 3.5.X&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;DROP 200 - EWS&lt;/li&gt;
&lt;li&gt;DROP 160 - Historian&lt;/li&gt;
&lt;li&gt;DROP 180 - OPC&lt;/li&gt;
&lt;li&gt;DROP 210 - Operator workstation&lt;/li&gt;
&lt;li&gt;DROP 211 -&amp;nbsp;&lt;span&gt;Operator workstation&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;DROP 212 -&amp;nbsp;&lt;span&gt;Operator workstation&lt;/span&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;span&gt;Any graphics or logic changes that are implemented on the DROP 200 - EWS are unable to replicate on DROP 180, 210, 211 &amp;amp; 212. Recently we changed a graphics (spelling mistake) on our DROP 200 - EWS and when we tried to download it on the rest of the DROPS, only changes were made successful on DROP - 160 however on the rest of the DROPs it failed with an alert message popping up as &amp;quot;UNABLE TO COMPLETE THE REQUESTED OPERATION. CODE: 0x80004005. SOURCE: OVATION DEVELOPER STUDIO&amp;quot;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;span&gt;Kindly advise on the reason that why changes are not been able to download on the DROP 180, 210, 211 and 212?&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Please advise on the way forward to rectify this problem?&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;span&gt;&lt;img alt=" " src="https://emersonexchange365.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/51/Communciation-Issue.jpg" /&gt;&lt;/span&gt;&lt;/p&gt;
&lt;/div&gt;</description></item><item><title>Ovation Users’ Group Conference</title><link>https://emersonexchange365.com/thread/10079?ContentTypeID=0</link><pubDate>Tue, 01 Mar 2022 18:29:52 GMT</pubDate><guid isPermaLink="false">cd40bb2b-3d49-4868-939d-417119b40291:50c3abd9-4ba1-4b04-aa38-675f38c1aa2b</guid><dc:creator>Greg Schirm</dc:creator><slash:comments>0</slash:comments><comments>https://emersonexchange365.com/thread/10079?ContentTypeID=0</comments><wfw:commentRss>https://emersonexchange365.com/community-hubs/deltav-community-connect/f/ovation-discussions-questions/10079/ovation-users-group-conference/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Ovation users can join/visit the &lt;a href="https://www.ovationusers.com/" rel="noopener noreferrer" target="_blank"&gt;Users&amp;rsquo; Group website&lt;/a&gt; to learn more.&lt;/p&gt;</description></item><item><title>Identifying Ovation Control System Version from Master Database</title><link>https://emersonexchange365.com/thread/9877?ContentTypeID=0</link><pubDate>Fri, 08 Oct 2021 13:53:20 GMT</pubDate><guid isPermaLink="false">cd40bb2b-3d49-4868-939d-417119b40291:d8f151bc-4729-45f7-8608-6abb469910d6</guid><dc:creator>James Connor</dc:creator><slash:comments>0</slash:comments><comments>https://emersonexchange365.com/thread/9877?ContentTypeID=0</comments><wfw:commentRss>https://emersonexchange365.com/community-hubs/deltav-community-connect/f/ovation-discussions-questions/9877/identifying-ovation-control-system-version-from-master-database/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I have a need to identify the Ovation control system version from the tables collected from the system master database.&lt;/p&gt;
&lt;p&gt;I see values in the table SCHEMA_REVISION that seem useful, such as MAJOR = 39 &amp;amp; MINOR = 1. Could this be mapped to the control system version somehow?&lt;/p&gt;
&lt;p&gt;Or maybe the control system version is located somewhere else in the database?&lt;/p&gt;
&lt;p&gt;As an alternative, perhaps there is a simple way to collect a file or setting from an Ovation drop that would have control system version information? I&amp;#39;m looking for something relatively simple and dependable that can be done on a periodic basis.&lt;/p&gt;
&lt;p&gt;Any help would be much appreciated.&lt;/p&gt;</description></item><item><title>How acquire information on AutoCAD and SVG support and use in different system versions of Ovation</title><link>https://emersonexchange365.com/thread/9667?ContentTypeID=0</link><pubDate>Thu, 10 Jun 2021 16:37:44 GMT</pubDate><guid isPermaLink="false">cd40bb2b-3d49-4868-939d-417119b40291:c7c81a9d-255d-4686-8a53-8ec0f8aefaf9</guid><dc:creator>James Connor</dc:creator><slash:comments>0</slash:comments><comments>https://emersonexchange365.com/thread/9667?ContentTypeID=0</comments><wfw:commentRss>https://emersonexchange365.com/community-hubs/deltav-community-connect/f/ovation-discussions-questions/9667/how-acquire-information-on-autocad-and-svg-support-and-use-in-different-system-versions-of-ovation/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;&lt;span style="font-size:150%;"&gt;Hello.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size:150%;"&gt;In my work experience of configuring, modeling and data mining Emerson Ovation systems (Windows and Solaris), I have come across a need to acquire&amp;nbsp;specific&amp;nbsp;information on exactly which Ovation system versions support and use the available CAD file formats for logic (which I believe is AutoCAD or SVG formats). If the exact version of AutoCAD or SVG format is known for each Ovation system version that would be even better.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size:150%;"&gt;I have searched for this information, but I now turn to the knowledgeable users of this forum.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size:150%;"&gt;&lt;/span&gt;&lt;span style="font-size:150%;"&gt;Any assistance in finding information on which CAD formats go with which Ovation system versions&amp;nbsp;would be greatly appreciated.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size:150%;"&gt;Thanks in advance, Patrick&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size:150%;"&gt;&lt;/span&gt;&lt;/p&gt;</description></item></channel></rss>