Is there a function block that can be used for a matrix for 26 by 26. I need a placeholder for values and call them on reference the value in the array/matrix. I'm trying to use the signal characteristic but its only allowing me to add one column in the matrices but in help it says its limited to 20 by 20. Having no luck also with the cause and effect matrices but again don't what to use it as it only goes to 16. Any help would be great. Regards Thomas
↧
Forum Post: Control studio function block.
↧
Forum Post: Alternatives to Embedding Module Blocks into Equipment Modules Discussion, Pros and Cons
As per the subject really. Using PCSD shell Equipment modules would lead you towards embedding Module Blocks into your Equipment Modules, which is fine but is a little limiting as it only allows access to parameters at the top level of the embedded module instances. Previously I've used Dynamic Reference composites and bespoke external reference composites to overcome this limitation, but each has it's own pros and cons. I'd like to throw it open to the community (developers and end users) to discuss the pros and cons and see if there is a consensus on the best approach. Perhaps listing any system performance issues using any of the approaches may have. Here are some of my initial thoughts on the three options I've considered. 1. Embedded (DEVX) Module Blocks (as per DeltaV product intent presumably), major downside this only lets EM code reference top level parameters of the embedded Modules, but can check for cross references to a device and us the device IGNORE function and allows for Private/Shared representation and binding withing the control strategy hierarchy (the only method that allows this) 2. Embedded (DEVX) Dynamic References composite that contain sufficient dynamic reference parameters for your purpose that are bound on first download using a single DEVX_ID string parameter containing the module name. These allow access to any module parameter (not just top level), they can be easily enhanced should you find you need access to further modules parameters. Main con is that you can't check for cross references (in explorer), clients (maintenance/debuggers) don't particularly like this for obvious reasons. 3. Embedded (DEVX) External References composite that contain sufficient external reference parameters for your purpose. These allow access to any module parameter (not just top level), they can be easily enhanced should you find you need access to further modules parameters. A pro compared to dynamic reference composites is that you can check for cross references (in explorer). The downside compared to dynamic reference composite is that configuration is more tedious where you only need to specify the module tag in a string rather than configuring potentially bundles of reference strings per DEVX composite.
↧
↧
Forum Post: DELTAV EXPLORER
espected sir, i am using DeltaV 8.3 version , DCS system working normally . but when i try to open the DELTAV EXPLORER pop up open the Alarm show Connected with the data base server but failed to open a database connection ,please read specific message below and take appropriate action Reason Failed to open the database please check the event log on the Pro+for Details For more information ,click on the detail button even i checked the User name and password is same and correct please help to diagnose the problem khalid javed 00923008339859
↧
Forum Post: Recipe Exchange Sample client in Version 12.3.1
Guys Has anybody sucessfully used the recipe exchange client that comes preinstalled in the samples folder with ver 12.3.1. I am under a time crunch on the current project and need to see if anybody has sucessfully used this. If so I can continue to persue this with support. If not I will just create my own parser to get data out. System is VSphere running Server 2012 with a DeltaV domain of VMs running Server 2008. Details; App starts normally and need to connect to system. Press connect and popup appears three fields to fill in other three are prepopulated. User: (Enter my account with admin level priviliges). Password: Current password. Domain: Enter AxxxxxDCS54. When hit OK app appears to freeze and become unresponsive. Have tried this on servers PRO and APP and workstations PRO and OWS. Also tried on a seperate DEV system we have. Response the same. Hoping somebody out there has already been through this and can let me know what the resolution was.
↧
Forum Post: RE: FHX to XML converter
Jack, OK...so there is a lot of work going on under the hood in the conversion, I suspected as much, but wasn't sure. So far I haven't seen any issues with the output its producing, but if I find something, I'll let you know. As to what I'm using it for, I'm working on a fairly large pharma project, and I've been using it to help with verifying the as-built documents against the code that was delivered to the site. I'm mostly a VBA programmer, and with the XML it's much easier to parse the export to get the information that I need than trying to parse the raw FHX. Only suggestion for a minor improvement might be to allow the user to select multiple files at once for conversion in case someone wants to process several smaller exports from a DB instead of working on the whole DB at once. Regards, Greg
↧
↧
Forum Post: RE: Alternatives to Embedding Module Blocks into Equipment Modules Discussion, Pros and Cons
Neil, My thoughts on those options are ... 1. Embedded (DEVX) Module Blocks I like this approach for organizational purposes as it documents which CMs are under the control of a given EM. I agree that the inability to drill down below the first level of parameters is limiting. We would commonly provide parameters on the top level of the CMs for commonly accessed lower level parameters. In other cases, we would add an external reference to the EM that would need configuration on instance level. These work, just not as cleanly as I would like. Your option 1 is still my preferred method provided I can get to the parameters I need. Maybe Emerson will enhance the capabilities around embedded Module Blocks in the future. 2. Embedded (DEVX) Dynamic References composite that contain sufficient dynamic reference parameters for your purpose that are bound on first download using a single DEVX_ID string parameter containing the module name I avoid dynamic references unless there isn’t another good option. I’ve seen issues (v9 & v10) where the EXEC_TIME or an EM increased by a factor of 10 when a dynamic reference in it was not resolved. Since the dynamic reference was used to dynamically reference parameters in other modules on demand, it was very common (over 50% of time) the dynamic reference would not be set. We had to modify to reference a dummy variable when not in use. So, there were ways to work around the issue, but this turned me off to the dynamic references. 3. Embedded (DEVX) External References composite that contain sufficient external reference parameters for your purpose I’ve used this method when I didn’t need to (or couldn’t) organize the CM under the given EM (or CM). I found this method more configuration intensive as each parameter reference had to be set. emersonexchange365.com/.../6447 I would love to see the Internal Reference and External Reference parameter types be replaced with a single Reference parameter. The internal / external paths would be determined by the method used to denote the parameter path (just like how it is done in a calc block or action in a sequence). This would be very helpful in class based Ems. We often wanted to reference a dummy variable in an EM or CM when an external parameter didn’t exist.
↧
Forum Post: RE: Control studio function block.
Thomas, You can us a floating point array parameter type but it can only have 240 cells (rows x columns) and a maximum number of row/column of 127. If you need that much data (676 cells) you will have to build something special using multiple array parameters. (i.e. the rows or columns are floating point array parameters) 26 parameters with 26 rows by 1 column (can name the parameters like what the column heading would be) 9 parameters, 8 with 26 rows by 3 columns and 1 with 26 rows by 2 columns 4 parameters, 3 with 26 rows by 7 columns and 1 with 26 rows by 5 columns 3 parameters, 2 with 26 rows by 9 columns and 1 with 26 rows by 8 columns etc Depending on what you are needing this for would make the decision on how best to do this but I would probably lean more to 26 individual parameters. As an example where I have used this is for a Raw Material User Queue where we have 25 users of a Raw material and needed to keep track of user priority request, target, total, target flow rate, etc. for each User of the queue. Each one of those would be a floating point array so it was pretty easy to understand the logic when it would be using '^/TARGET_AMT'['^/DESTINATION.CVI'][1] in logic (Current destinations requested target amount in this case).
↧
Blog Post: Continuous Floating Roof Tank Condition Monitoring
Floating roofs are used on storage tanks to minimize vapor space between the top of the tank and the level of the liquid, typically a petroleum-based product, inside the tank. Per the External floating roof tank Wikipedia entry: The roof rises and falls with the liquid level in the tank. As opposed to a fixed roof tank there is no vapor space ( ullage ) in the floating roof tank (except for very low liquid level situations). In principle, this eliminates breathing losses and greatly reduces the evaporative loss of the stored liquid. There is a rim seal system between the tank shell and roof to reduce rim evaporation. In this 3:40 YouTube video, How to Increase Safety with Continuous Surveillance of Floating Roof Movements , Emerson’s Ulf Johannesson explains how wired or wireless radar level measurement technologies are used to monitor the location of the roof in relationship to the level of the liquid. By continuously monitoring the roof location at different points on the roof, issues such as a stuck or tilted roof condition can be discovered early and corrected before an abnormal situation occurs and worsens. Ulf opens highlighting some of the common issues that can occur with floating roof tanks. These include wind-induced roof tilt, imbalance causes by rain or snow, rim seal friction, pontoon or deck leaks, tank wall abnormalities, roof access ladder binding and block roof drains. The traditional way to monitor for these conditions was visual inspections by tank farm personnel. This practice placed personnel in hazardous locations and provided only intermittent monitoring which could miss the early stages of a developing problem. Ulf highlights two approaches for monitoring floating roof level and tilt conditions. The wired approach uses non-contacting radars mounted at the top of the tank shell. Spacing 3 or more non-contacting radar measurement instruments around the tank provides a measurement from the top of the tank shell down to the floating roof level inside the tank. The second approach is to install three or more wireless guided wave radar measurement instruments in which the probes penetrate through the roof down into the tank to measure the airspace above the liquid. In both cases, a separate reading is used to measure the liquid level as shown in the picture below. Differences between the measurements indicate a tilt, stuck roof or improper draining condition. You can connect and interact with other tank gauging and level measurement experts in the Tank Gauging and Level groups in the Emerson Exchange 365 community. Related Posts Improving Safe Operations with Wireless Vibrating Fork Level Switches Remote and Continuous Tank Floating Roof Monitoring Selecting Best Solids Level Measurement Technology Improving Heat Rate with Better Measurements Guided Wave Radar Level Measurement in Vessel Bypass Chambers Changing Guided Wave Radar Probe Length The post Continuous Floating Roof Tank Condition Monitoring appeared first on the Emerson Process Experts blog.
↧
Forum Post: RE: Control studio function block.
You may as well consider DeltaV Excel Add-in. I do not have a ready made solution, but can certainly imagine a spreadsheet would be usefull.
↧
↧
Forum Post: RE: Alternatives to Embedding Module Blocks into Equipment Modules Discussion, Pros and Cons
In reply to the last point in your post, it is possible to browse an internal dummy parameter with an External Reference.
↧
Forum Post: RE: Alternatives to Embedding Module Blocks into Equipment Modules Discussion, Pros and Cons
Hi Alfred, You are correct that it can be done. If I remember correctly, I had to browse the long way around and enter the path as an external parameter that just happened to be located in the same control module. In some cases, it would be beneficial to default to a dummy parameter and then configure as needed on the instance level. This really isn't possible (as far as I know) since the control module name would need to be in the external parameter path. If there is a way to do this otherwise, I would love to know it.
↧
Forum Post: RE: Alternatives to Embedding Module Blocks into Equipment Modules Discussion, Pros and Cons
True, you have to configure every External Reference at instance level (or use Aliases in the default reference in the class module).
↧
Forum Post: RE: Alternatives to Embedding Module Blocks into Equipment Modules Discussion, Pros and Cons
I agree with everything that Michael has stated but there is also another option to consider. Equipment Modules along with other modules can be placed under class based unit instances and the logic (EMs, Modules, Interlocks, etc) can use the aliases of the unit instance in their logic. Pros: Any parameter of any block in a module is usable at any time as long as the unit class alias is only resolved to the module name (no massive downloads of module class instances to get to a new parameter needed for a class!). No issues because of parameter differences while importing between the module class used for the module block alias and the resolution of that module block alias to the module instance required for that alias. Module block aliasing is really picky with linkages to module classes for the module blocks (instance resolutions has to match exactly all the parameter structures of what the class used has). An example where a module that was a certain class type that had to change from an AI (Phase 1) to a PID_LOOP on a new EM class (Phase 2), the configuration (EM class, instances and modules) being imported would fail if the module level parameters of the AI and PID_LOOP don't match. When this occurs a lot of manual work has to be done to figure out why it failed and then fix the problem(s) identified with module(s) manually (the error trapping for this isn't very intuitive as to what the real problem is for this case, which for this example would be to manually convert the AI module to a PID_LOOP module). Cons: It does require the Advanced Unit Management license which is counted by the number of class based unit instances used in the current version, while pre-v12 versions was DST based. This is typically considered too costly but some customers have done their own evaluation between previous experiences using module blocks for aliasing and using unit instance aliases and concluded that this expense is well worth it to them. References of a module aren't caught by the tag being used in a Unit instance alias (dynamic reference setups are also not found). It would be outstanding if this type of aliasing was somehow a part of the EM itself and didn't require a Class Based Unit instance or module blocks to do the aliasing as this method for aliasing is by far the best solution for both configuration and operations of the plant.
↧
↧
Forum Post: RE: FHX to XML converter
Thanks Greg. My tool give correct translation. The improvements concern only working time. Yes, XML format is very usefull to elaborate working documentation. I frequently use it (in Excel VBA) for a large Swiss pharma plant projects to list the recipe parameters and design their flow through the phases; a kind of batch cross-referencing. About improvement, yes, I could easily add this kind of option, but if this tool is incorporated to an automation of information processing, it could not stay a freeware. I take this opportunity to point out that we will shortly produce a client-server software to establish the cross-referencing of DeltaV modules and Provox points in the iFix displays (DV 8 to 12). Currently, the product (called TCR for "Template Cross Reference") works very well, but some improvements are being made to manage, in particular, the impact of the removal of displays on the cross references database. I'll give you more information ASAP or contact me for further information. Regards.
↧
Forum Post: RE: Alternatives to Embedding Module Blocks into Equipment Modules Discussion, Pros and Cons
Neil, I agree with all your thoughts and I always using option 3, because option 1 cannot be used if you do have a slightly different class for some modules. By using bulk-edit for creating the external references in the EQM instances I found it quit workable to work around extra amount of work. Another downside of option 1 is that when you change something in one of the modules I noticed that often a download of the whole EQM and all of its modules is required. Note that in version 13 you can use #IGNORE for external references and a 'DUMMY' is not required, but the downside of that is that the reference does not get a nice defined value.
↧
Forum Post: RE: UNABLE TO OPEN DeltaV EXPLORER
DELTAV EXPLORER respected sir, i am using DeltaV 8.3 version , DCS system working normally . but when i try to open the DELTAV EXPLORER pop up open the Alarm show Connected with the data base server but failed to open a database connection ,please read specific message below and take appropriate action Reason Failed to open the database please check the event log on the Pro+for Details For more information ,click on the detail button even i checked the User name and password is same and correct please.. I will appreciate if anyone can assist with likely solution to the problem.
↧
Forum Post: RE: Alternatives to Embedding Module Blocks into Equipment Modules Discussion, Pros and Cons
Some points to consider: 1- Download behavior. Currently command/state-driven EQM parameters dos not retain their value after download. Having a module block rather than a composite hosting EQM is a solution for that. Also note that setting same name in module block as composite eliminates the need to re-code SFCs. I use to replace TP parametrs by a a module, having all TPs, declared as private into EQM class. This also opens a door to implement additional functions as having a dedicated module instance for each EQM instance allows to implement enhanced parameter management (enable/disable, lock/unlock based on process conditions) without worring about EQM classes modification. 2-Module block bound module provide it's own dynamo, faceplate, detail and primary display. Function block dynamos or faceplates may be used with composites but it's not currently part of PCSD items. 3-Execution times, module block approach allows setting differen scan rate on underlying modules. 4-When related modules are deployed into different controller we have the issue that partial download could destroy inter-controller communications the requires download of setup data to be fixed. DeltaV explorer has specific features to handle that when using module blocks, using "download equipment moduls and contained non sis modules" option.
↧
↧
Forum Post: RE: FHX to XML converter
Jack, I use FhxToXml2005.exe and XmlToFhx2005.exe rather than FhxToXml.exe and XmlToFhx.exe without issues. Theese xxxx2005 versions come with a .config file so I guess they are developed using .NET framework v4.0. I'm working on Access XML import on FhxToXml2005 created files to obtaing Access database containing deltav configuration. Results are good but I've did not cover any posible deltav item yet. I also plan to use XmlToFhx2005.exe to create valid FHX from that access database. I'm using XSLT transformations on Access XML import/exports, resulting in very fast import/export with very few VBA scripting.
↧
Forum Post: RE: Alternatives to Embedding Module Blocks into Equipment Modules Discussion, Pros and Cons
Great stuff Matt, we were trying to avoid AUM, but perhaps the system life cycle costs could be a swaying factor.
↧
Forum Post: RE: Alternatives to Embedding Module Blocks into Equipment Modules Discussion, Pros and Cons
Some interesting information about download behaviour to consider, thanks
↧