Quantcast
Channel: Emerson Exchange 365 Community Site
Viewing all 7205 articles
Browse latest View live
↧

Forum Post: RE: Configure Process History View

August 25, 2014, 9:21 am
$
0
0

Where is your event chronicle located?  Based on your description it sounds like the Pro+, because PHV can enumerate all known event chronicles.  If you look in DeltaV explorer under the Alarms and Events field of each workstation or application station node, you can see which are enabled as event chronicles. If there are more enabled than you can see in the PHV list, then the chronicles may not have been downloaded and are not working.

Obviously, localhost will only work if the workstation where you launch PHV is also a chronicle.

Defaulthost is tricky.  It represents what you as a user has selected for the client workstation as your default chronicle.   The default chronicle is used for event charts by default.  It is user-profile based, and could potentially vary for each user on each workstation.  The "default" default chronicle is localhost, I believe.

Now for testing, lets do the following:

1. **Non-Admin** user should log in to Windows and DeltaV on a workstation.

2. Open PHV and select File-->Set Default Data Servers

3. Under Event Chronicle, Select Pro+ for the Events Data Server.  Ensure 'save as my Application Startup Data Server' is checked.

4. Open a new Event file, File-->New-->Event.

5. Select Events-->Configure Events.  

6. In the Configure Event Chronicle dialog, see if the Events drop down contains any current datasets.

If you don't see current data sets, repeat this process for the admin user.  If he DOES see extra chronicles, then as I said, it would seem to be a permissions issue on the current data sets in SQL.

↧
Search

Forum Post: RE: electromagnetic flow transmitter error

August 25, 2014, 10:58 am
$
0
0

Hi Mohsen,

That is a normal response from the transmitter if the sensor/pipe is empty. The empty pipe detection function is supposed to detect an empty pipe (which would also be an electrode circuit open) condition, report that status message, and force the flow reading to zero.

The conductive process fluid completes the electrode circuit (the part of a magmeter that picks up the induced voltage). Without a sensor/pipe full of a conductive process fluid, the circuit is open and deemed empty if the empty pipe detection is active.

The status message should clear once the sensor/pipe is full of a conductive process fluid.

Additionally, the 8732C is an obsolete transmitter. It has been replaced by the 8732E. The C level revision has been obsolete for over 5 years.

Best Regards,

Mike

↧
↧

Forum Post: RE: Can't configure Flowserve Logix 3400MD Positioner with AMS 11.5 / Delta V 11.3

August 26, 2014, 6:57 am
$
0
0

Did you get this situation resolved?  Open AMS and do a rebuilt hierarchy at the DeltaV Network/go to the fieldbus Card and expand the port and scan the device by right clicking on the device.  Does the device completed the scan?  What icon do you see?

What I am trying to see if the DD(device descriptor) and the device firmware are working together that were released by the manufacturer.

↧

Forum Post: RE: Batch - Loading / Unloading

August 26, 2014, 1:01 pm
$
0
0

I believe you can modify the User Preference on each machine to change this behaviour but this is a global setting for all comm errors and not just for when a phase unloads.

In Workspace (Edit Mode) - Select Workspace menu item and select User Preferences, Then select the second tab (Animations Data Error Defaults) and change the Error Table Entry for Comm.

Regards,

Matt

↧

Blog Post: 한국 에머슨, 8월 퀴즈 당첨자 발표!

August 26, 2014, 6:42 pm
$
0
0
​ 한국 에머슨 페이스북 이벤트 참여는 여기에서!!! 가능합니다.
↧
↧

File: AMS and Moxa.pdf - 8/27/2014 7:24 AM

August 27, 2014, 5:24 am
$
0
0
This attachment "AMS and Moxa.pdf" was uploaded to this Group's Media Gallery on 8/27/2014 at 7:24 AM via email.
↧

File: nport_ia-51505250.pdf - 8/27/2014 7:24 AM

August 27, 2014, 5:24 am
$
0
0
This attachment "nport_ia-51505250.pdf" was uploaded to this Group's Media Gallery on 8/27/2014 at 7:24 AM via email.
↧

Forum Post: RE: AMS 12.0 with MUX MTL 4841 and NPort 6450 from MOXA

August 27, 2014, 5:24 am
$
0
0
See attached…
 
 
 
[collapse]
From: frmezano [mailto:bounce-frmezano@community.emerson.com]
Sent: Tuesday, August 26, 2014 10:32 AM
To: AO@community.emerson.com
Subject: [EE365 Asset Optimization Track] AMS 12.0 with MUX MTL 4841 and NPort 6450 from MOXA
 

Hi all,

When I was as Plantweb Eng. I installed a couple of AMS DM with Comtrol, now I received a call from another FSO about an architecture they are trying to install with an AMS v12.0

They have the transmitters connected to an MTL4841 and the output of this MUX is connected to a NPort 6450 from MOXA, and then connected to DeltaV, but they have a lot of communication problems with AMS DM, is this a valid architecture?

As far as I know the MOXA converter is not approved for the AMS DM, could this be the cause of the communication failures?

Please advise.

[/collapse]
↧
Search

Forum Post: Shale Impact on the U.S. Economy and Rest of The World

August 27, 2014, 6:38 am
$
0
0

Seems like each day the impact of unconventional oil & gas revolution in the U.S. continues to amplify across the U.S. and the world.  I recently ran across an ExxonMobil blog that stated it's a billion-dollar per day shot in the arm for the U.S. economy as result of new supplies of Oil and gas.  The blog goes on to state that domestic energy supplies have increased 1,300% from January 2010 to April 2012.  A more recent article from USA Today  pegs the benefits at $2,000 per U.S. household and 3.3 million jobs created by 2020.  Energy costs for households have also reduced due to cheaper oil and gas.  All of this is a great trend that will continue to make the news and drive the economy.  Lastly saw a Twiiter post from the ONS show in Norway this week that stated investments in the north sea E&P were being re-evaluated based on the North America shale. Oh how the world has changed in the last 5 years.

↧
↧

File: Aborting phase through logic

August 27, 2014, 9:14 am
$
0
0

Hi DeltaV Experts

I am operating phases through DeltaV Batch.  I have a condition(Rupture Disc) where I have to abort the Phase through logic.  For this requirement  I added a condition block to the failure monitor composite & a parameter Fl_01 to monitor this condition from a particular step in the run phase.

I wrote in calc block to move abort into Xcommand parameter. But the phase would not move to Abort Phase as I found that when operating phases through Batch executive, the owner of the phase would be DeltaV Batch & Xcommand can be written only when the Owner is external. 

Can any one guide me on how to move to aborting phase from the running phase through logic. I am using PCSD here.

Please ignore the attachment . I attached as it was not allowing me to post without attachment

Regards,

Manzoor

↧

Forum Post: RE: Content Based Analysis during PAS modernization

August 27, 2014, 9:23 am
$
0
0

I am referring to competitive systems like Foxboro, Honeywell, Bailey and Siemens Moore APACS.  Although, the same analysis can apply to Provox and RS3. What tools did you use to migrate with and what purpose did they serve?  For the complex loops, were Functional Specs written?

I am keenly interested in where tools were used, how and what they are.  Where are these tools, who owns them?  We have the ability to do analysis that will tell us the 'class' (repetitive, think DeltaV module templates) and custom work.  I believe this type of capability would be very useful to a migration team and I'm trying to promote their use.  Is there anyone using this template and custom approach?

Often, the granularity of the legacy control configuration is small (think Bailey function blocks).  In Foxboro I/A, the AIN, PID and AOUT blocks simplify down to the PID controller in DeltaV.  It is good that your customer was able to remove 'dead', needless or overly complex functionality when they converted over to DeltaV.

↧

Forum Post: RE: Creating an Alarm List

August 27, 2014, 11:22 am
$
0
0

I also use the bulk edit method to pull the alarms for all my modules. I then use Excel on the .txt file that is generated to create a list for the process engineer in each area to review. We also use the DeltaV alarm help so the spreadsheets are used to perform alarm rationalization. After rationalization you can update the information in the spreadsheets and reverse the process to update the Process Alarms in DeltaV.

↧

Forum Post: RE: Updating Dynamos

August 27, 2014, 11:30 am
$
0
0

If the new dynamo has a different size, the location may be a bit off when using the dynamo update tool. In that case you still need to check every display separately if everything is lined up right. Update tool works great anyway.

On the second question. Bulkedit can't add, remove or rename parameters from modules, only change values of existing parameters. It also can't delete modules from the database.

If the modules are class-based, it's of course simple to modify the class and then change the values with a bulkedit in all the instances.

If the modules are template-based, I think the only way is to replace the modules. Basically delete the old ones and bulk-edit new ones. Tip: work with class-based whenever possible.

↧
↧

Blog Post: LACT Unit Base Volume versus Base Prover Volume

August 27, 2014, 11:35 am
$
0
0

Update: I should have also mentioned that Rossella will be conducting an October 15 webinar, Optimizing Wellpad Custody Transfer of Liquid Hydrocarbons. If you’re in the onshore oil & gas industry, you’ll want to register and bring your custody transfer questions.

The custody transfer process exchanging oil & gas production between business entities is a critical part of the overall production process. I received this question to an earlier post, How to Prove Your LACT Meter:

I was wondering if you could explain the difference between Base Volume and Base Prover Volume when proving meters.

In that post, Emerson’s Rossella Mimmi shared how provers were used to compare a known volume against the Lease Automatic Custody Transfer (LACT) unit’s flow meter output, where the ratio between the prover reference volume and the meter reading is the meter factor, which is used to correct the meter reading.

I shared this question with Rossella and asked her if she could help me explain the difference. She explained:

Rossella Mimmi Pipeline Oil & Gas Industry Manager Flow Solutions Group

Rossella Mimmi
Pipeline Oil & Gas Industry Manager
Flow Solutions Group

I think the question refers to how the meter factor is calculated, dividing the prover reference volume by the base volume. Basically two quantities are compared, one is the volume actually measured by the flow meter, the other one is a reference known volume that is the prover’s one.

This is a prover’s operating principle:

Daniel-48in-Pipe-ProverThe prover consists of a length of pipe whose internal volume has been very accurately determined; the displacer is forced to travel at the same velocity as the liquid in the pipe. During meter calibration the meter and the prover are connected in series so that the volume swept out by the piston or sphere can be compared with the volume registered by the meter whilst liquid is flowing steadily from one to the other. As the displacer enters the calibrated pipe section it trips a detector, thereby initiating a count of pulses from the meter under calibration.

A second detector is tripped when the displacer reaches the end of the calibrated pipe section, thus stopping the meter pulse count. This volume is compared to the volume indicated by the meter, to determine a meter factor. This operation is carried out without interrupting the flow of liquid through the meter. Automatic valves, external or internal to the prover, control or divert the flow to cause travel of the displacer during the proving run. Proving should be performed under the same conditions as it is normally expected to operate. The meter prover must have a capacity large enough to provide proving runs of adequate duration.

The question and answer were too good to leave buried in an email exchange, so I wanted to share it with you.

You can connect and interact with other flow and oil & gas professionals in the Flow and Oil & Gas tracks of the Emerson Exchange 365 community.

Related Posts:

↧

Blog Post: LACT Unit Base Volume versus Base Prover Volume

August 27, 2014, 11:35 am
$
0
0

Update: I should have also mentioned that Rossella will be conducting an October 15 webinar, Optimizing Wellpad Custody Transfer of Liquid Hydrocarbons. If you’re in the onshore oil & gas industry, you’ll want to register and bring your custody transfer questions.

The custody transfer process exchanging oil & gas production between business entities is a critical part of the overall production process. I received this question to an earlier post, How to Prove Your LACT Meter:

I was wondering if you could explain the difference between Base Volume and Base Prover Volume when proving meters.

In that post, Emerson’s Rossella Mimmi shared how provers were used to compare a known volume against the Lease Automatic Custody Transfer (LACT) unit’s flow meter output, where the ratio between the prover reference volume and the meter reading is the meter factor, which is used to correct the meter reading.

I shared this question with Rossella and asked her if she could help me explain the difference. She explained:

Rossella Mimmi Pipeline Oil & Gas Industry Manager Flow Solutions Group

Rossella Mimmi
Pipeline Oil & Gas Industry Manager
Flow Solutions Group

I think the question refers to how the meter factor is calculated, dividing the prover reference volume by the base volume. Basically two quantities are compared, one is the volume actually measured by the flow meter, the other one is a reference known volume that is the prover’s one.

This is a prover’s operating principle:

Daniel-48in-Pipe-ProverThe prover consists of a length of pipe whose internal volume has been very accurately determined; the displacer is forced to travel at the same velocity as the liquid in the pipe. During meter calibration the meter and the prover are connected in series so that the volume swept out by the piston or sphere can be compared with the volume registered by the meter whilst liquid is flowing steadily from one to the other. As the displacer enters the calibrated pipe section it trips a detector, thereby initiating a count of pulses from the meter under calibration.

A second detector is tripped when the displacer reaches the end of the calibrated pipe section, thus stopping the meter pulse count. This volume is compared to the volume indicated by the meter, to determine a meter factor. This operation is carried out without interrupting the flow of liquid through the meter. Automatic valves, external or internal to the prover, control or divert the flow to cause travel of the displacer during the proving run. Proving should be performed under the same conditions as it is normally expected to operate. The meter prover must have a capacity large enough to provide proving runs of adequate duration.

The question and answer were too good to leave buried in an email exchange, so I wanted to share it with you.

You can connect and interact with other flow and oil & gas professionals in the Flow and Oil & Gas tracks of the Emerson Exchange 365 community.

Related Posts:

↧
Search

Forum Post: RE: DeltaV Xi Reporter issue

August 27, 2014, 12:43 pm
$
0
0

I would first check that both the Xi Server and the Discovery Server services have started. They both depend on the DeltaV service as well. Not a common issue but you also need to make sure the Xi Server is re-installed after any upgrades. You also didn't mention where you are running the services. By default it would be the ProPlus.

↧

Blog Post: 에머슨의 무선 레벨 기술 - 제 2부

August 27, 2014, 7:53 pm
$
0
0
에머슨의 무선 레벨 기술 - 제 1부 보기​​ ​ ​에머슨의 무선 레벨 기술 - 제 2부 레벨 애플리케이션 레벨 제품이 광범위한 측정 및 제어를 위해 유정에서 널리 사용되면서, 시설과 작업자의 안전을 보장하고 공정 효율성에 기여하고 있습니다. 신규 설비의 경우에는 레벨 계기를 신속하고 손쉽게 배치할 수 있는지 여부가, 최초 오일 생산의 속도에 지대한 영향을 미치는 중요한 사안으로 작용합니다. 기존 설비의 경우, 구형 기술을 최신 레벨 측정 장치로 교체하는 것은 유지 보수를 감소시키며 정확한 측정을 가능하게 합니다. 어느 쪽이든, 케이블 작업이 필요하지 않은 무선 기술이 유정에 가시성을 추.......
↧
↧

Forum Post: RE: PCSD HCD

August 28, 2014, 2:49 am
$
0
0

Thanks for the information, Amod.

Don't get me wrong. I like the concept of PCSD, but the execution seems a bit messy sometimes looking from the outside. It works fine as it is, as long as you don't try to modify anything yourself.

HCD and the 'old' PCSD. For instance, I've had (many) operators complaining about the number of tabs on the PCSD detail pictures and the function of each one. With some extra training they now know which are important for operations and which are not. Same for some dynamos.

I haven't seen the PCSD HCD hands-on yet, so I'm very interested to see how they improved the HMI.

↧

Forum Post: RE: STRING DATA TYPE IN DELTAV

August 28, 2014, 4:22 am
$
0
0

As far as I can tell, a STRING type parameter can hold up to 124 characters. String parameters written from expressions are limited to 256 chars.

Like Youssef explains this is further limited to 200 because of the maximum serial dataset size. 200 chars can be quite a long operator request.

If possible, you could consider using an enumeration or named set instead and only send the integer over serial bus. Then on the receiving end, show the according string. In DeltaV named sets however, strings are limited even to 48 chars. So might not be usable in your case.

↧

Forum Post: RE: DV11.3.1 - Operate - How to get the alarm name ?

August 28, 2014, 4:26 am
$
0
0

In addition, I have found this way to automaticaly enlarge ALL "Alarm summary" objects on my picture :

Private Sub CFixPicture_Initialize()
On Error GoTo ErrorHandler
   frszinitPicture Me
   ' Added to enlarge DV Alm Summary fields
   Dim oOo As Object
   For Each oOo In Me.ContainedObjects
       If oOo.Description = "DO NOT CHANGE THIS FIELD : DV Alarm Summary Control" Then
           oOo.AutoFitColumns
       End If
   Next
   Exit Sub
ErrorHandler:
   frsHandleError
End Sub

↧
Viewing all 7205 articles
Browse latest View live
Search