Hello JPTGlobal;
According to Avocent engineering We tested up to RSA7.1 only.
Regards;
Danny
Hello JPTGlobal;
According to Avocent engineering We tested up to RSA7.1 only.
Regards;
Danny
Hi Imran,
Answering your questions:
1. First thing you shall know, is the SZ is not the Logic Solver, thus, no safety logic is allowed to run at the SZ, all the safety logic will be assigned to the CSLS on the SIS Electronic Marshalling architecture. The main function of the SZ controller is to integrate the Local Safety Network to the DeltaV Control Network, featuring as a firewall, you can have as much as 16 CSLSs assigned to each LSN. As a controller, the SZ also runs PCS logic, you can assign up to 4 CIOC, or 4 WIOC, or a mix of both, in oder to drive Non-SIS IO from the SZ controller. Other importante feature is, for StandAlone application, the SZ has a native Modbus TCP interface, allowing a very straightforward integration to 3rd part Systems.
2. As per previous answer, we can use the SZ to run PCS logic.
3. You can have up to 16 CSLS assigned to the LSN on a single SZ controller, so what you can do is separate the application by CSLS within the same LSN.
4. Our CHARMs have integrated diagnostic, HART for Analog channel, LM for Discrete Output, Short and Open Circuit for Discrete Input.
Hope it Helps!
Tadeu Batista
Tony_M,
If you come up with a permanent solution, please post how it was done. I am with you when you say that you are not completely sure how to implement it.
Hi,
I am facing the following problem:
In CAS mode I would like to bypass the setpoint of the PID to the out of the PID, this realised the bypass parameter to on. When the PID is placed in MAN normal operations will copy the OUT to the SP, to block the function I set the bypass parameter back to off. This bypass parameter is read-only when PID mode is CAS, I would like to write the bypass parameter when the PID changes from MAN to CAS.
Using a CALC block and checking the actual and target mode doesn't seam to work, in my opinion when the PID is changed from MAN to CAS there should be a state where the PID actual state is MAN and the target state is CAS in this state I should be able to force the bypass parameter back to on.
Maybe I miss a state why this logic doesn't work:
Thanks,
Werner
We have DeltaV 11.3 and quad monitor set-ups with ATI FirePro V3750 (FireGL) graphics cards. I am trying to get the operator prompt to populate on the monitor that they are using instead of the number 1 monitor. I have read the previous thread about the Hydravision fix, but I believe that doesn't apply to me.
The ARC View “PEMEX Onshore Developments Feature End-to-End Wireless” highlights the difference between the wireless sensor network and the wireless backhaul:
Today the focus of wireless is very much the wireless sensor network used at the sensor-actuator level, primarily WirelessHART, because it is a relatively new technology. However, only a few years ago wireless was only used as the “backhaul” network in a SCADA system; between the RTU and the HMI/SCADA software. SCADA system with RTU is very common in the oil & gas industry since many years ago and continues to be so today, particularly in the upstream oil & gas industry.
ARC explains SCADA systems in upstream oil & gas consist of RTUs and transmitters at well pads that send process measurement to control centers located many kilometers away. The SCADA system's backhaul network typically uses wireless. That is, SCADA systems today may use both a wireless sensor network and a wireless backhaul network; albeit using different wireless technologies.
ARC notes that the major wireless backhaul technology options are GSM/GPRS, WiMAX, Wi-Fi, and proprietary radios.
ARC brings up a notable example “State-owned PEMEX has an ambitious plan for developing onshore oil & gas resources in its North Region of Mexico. This calls for completing over 1,000 wells in the Veracruz area over the next few years. To support these new installations, PEMEX has standardized on equipment both at the well pads and throughout the upstream system. Instruments at most of the remote locations will use IEC 62591 (WirelessHART) communication that will be managed by a WirelessHART gateway at the well pad. That gateway provides an Ethernet network connection that needs to be backhauled to PEMEX's SCADA system.”
Where locations had GSM/GPRS coverage, GSM/GPRS modems was the backhaul choice in these locations. Other sites in this and many other SCADA systems use proprietary sub-gigahertz radios operating in unlicensed ISM bands.
ARC notes “Upstream oil & gas applications for wireless backhaul have been one of the most common wireless applications in recent years, while well pads have also become one of the most common applications for wireless process measurement.”
That is, the wireless sensor network and wireless backhaul network complement each other. WirelessHART, Wi-Fi, and WiMax etc. complement each other, they are not competing. Multiple technologies are required because one size does not fit all.
What technology do you prefer for the SCADA backhaul?
Thanks very much everyone for your replys. The problem we found was with the password expiry.
Hi i've got two Sun computers i want to connect via their serial ports. First one is an old Ultra-5 and the second one is a SunFire X2250. i used to have the Ultra-5 connected to a Cyclades using an Avocent Sun-Cyclades DB9 to RJ45 adapter but the Cat-5 cable i made for the connection has been lost. Now i just want to connect the Ultra-5 to the X2250, which has an RJ45 serial port. i found the specifications for the X2250 serial port below and was wondering if someone could tell me how to wire the Cat-5 cable so it will work with the Avocent adapter? thanks
For those in Malaysia this week, join us at POWER-GEN Asia 2014Booth 2002, September 10-12 for the gathering of power industry professionals. Emerson will have a nice booth highlighting solutions designed for the power industry.
MPUIQ-VMCHS can be used as a replacement for DSRIQ's which are EOL since October 2013. MPUIQ-VMCHS is supported on
* MergePoint Unity appliance
* DSR1031 appliance
* DSR1024 appliance
* DSRxx30 appliance
* AutoView 1500/2000/1415/1515/2015 appliances
* AutoView 2020/2030 appliances
* AutoView 3050/3100/3200 appliances
* AutoView 3008/3016 appliances
The appliance must be upgraded to latest firmware to support MPUIQ-VMCHS.
Unfortunately older KVM switches are not supported and there is no replacement available.
Are you actually using the PID algortihm at any point in this control strategy? If not,. then you might consider replacing the PID with an Analog output or Manual loader function block to provide the pass-through setpoint function you require without having to toggle bypass on and off. Analog output block option SP-PV track in man can be disabled to ensure when the output is written in Man, the SP does not track.
If you need to use the PID, have you looked into disabling some of the pertinent CONTROL_OPTS for the PID? (Track In Man etc.)
MPUIQ-VMCHS can be used as a replacement for DSRIQ's which are EOL since October 2013. MPUIQ-VMCHS is supported on
* MergePoint Unity appliance
* DSR1031 appliance
* DSR1024 appliance
* DSRxx30 appliance
* AutoView 1500/2000/1415/1515/2015 appliances
* AutoView 2020/2030 appliances
* AutoView 3050/3100/3200 appliances
* AutoView 3008/3016 appliances
The appliance must be upgraded to latest firmware to support MPUIQ-VMCHS.
Unfortunately older KVM switches are not supported and there is no replacement available.
Hi,
after Equipment Module customization in the Library, I wanted to Download the the 4 concerned Equipment to the controller, and this Error message (error code 327781, RTC_NO_FB_DEFINITION_EXISTS) appeared. Somebody know what's the best way to solve this problem ?
Many Thanks
The problem with the THISUSER/USERNAME parameter is that (like all other THISUSER parameters) they are specifically local to the workstation and not shared outside of the workstation.
If you need to have this knowledge distributed outside of the workstation by other means than described already, you can try bouncing the information off of a module.
In Operate, create a text variable in user.fxg or si_globals.fxg whose currentvalue that is animated to the THISUSER/USERNAME parameter.
Edit script for the variable and create an onchange event for that variable in vb that writes the currentvalue of the variable to a control module parameter.
You can create one control module that simply is a storage location for the users on each workstation, written by Opereate automatically on user change.
You can assign this module to an app station so as to not introduce overhead to the controllers for a non-control function.
Your display can then just have datalinks to the module's workstation/user parameters.
I found it. I searched for "Hydravision" in Guardian. Thanks.
In industrial environments, high process temperatures, pressures, and vibration make it necessary to have a robust temperature sensor. Fast response time, accuracy, and stability are also needed. While several types of temperature sensors are available, such as thermistors, infrared pyrometers, fiber optic, and others, the two most commonly used in the process measurement industry are resistance temperature detectors (RTD) and thermocouples (TC).
The RTD provides sensitivity (minimum detectable change in temperature), repeatability, and drift that are an order of magnitude better than the thermocouple, as shown in Table 1-1. Threshold sensitivity and repeatability are two of the three most important components of accuracy. The other most important component, resolution, is set by the transmitter. Drift is important for extending the time between calibrations and the temperature loop running at the right setpoint. The data in this table dates back to the 1970s and consequently doesn’t include the improvements made in thermocouple sensing element technology and premium versus standard grades. However, the differences are so dramatic that the message is still the same.
The temperature range shown for the RTD in the table is optimistic. At temperatures above 500°C, changes in sensor sheath insulation resistance have caused errors of 10°C or more.
There are many stated advantages for thermocouples, but if you examine them more closely you realize they are not as important as perceived for industrial processes. Thermocouples are more rugged than RTDs. However, the use of good thermowell designs and good installation practices makes an RTD sturdy enough even for high-velocity streams and nuclear applications. Thermocouples appear to be less expensive until you start to include the cost of extension lead wire and the cost of additional process variability from less sensor sensitivity and repeatability.
The case of using TC or RTD input cards in a distributed control system (DCS) is not considered because of the error introduced by these input cards as a percent of span is large and individual sensor offset and drift errors cannot be individual corrected as they are with a dedicated temperature transmitter.
The IEC 751 standard describes an ideal relationship between the resistance of a platinum RTD and the temperature to which the RTD is subjected. The difference between the actual RTD curve and the ideal RTD curve results in a measurement error, which is referred to as a sensor interchangeability error.
The Callendar-Van Dusen equation offers an alternative to the IEC 751 standard. This equation can be programmed into a transmitter so that the transmitter can use the actual RTD curve rather than an ideal curve (e.g., IEC 751 standard) to translate the sensor’s resistance signal into a temperature value. The Callendar-Van Dusen equation enables the transmitter calibration to be matched to the sensor. When a sensor is replaced the parameters for the equation are entered into the transmitter.
The main reasons for selecting RTDs or T/Cs can be summarized in the following lists. In all cases, field temperature transmitters are assumed to be used rather than DCS TC or RTD input cards.
Why Use an RTD Rather Than a TC?
Why Use a TC Rather Than A RTD?
You should now recognize the importance of drift, threshold sensitivity, repeatability and range in the selection of temperature sensors. This knowledge provides the fundamental essential first step that sets a control loop’s ability to keep temperatures and consequently many compositions at their optimum operating point. The principles here can be extended to other sensors. In the next post we will take a look at the next step, which is sensor installation.
Last week I highlighted an updated book for process control engineers, Tuning and Control Loop Performance, by Greg McMillan. It’s amazing how prolific Greg is, even in his “retirement” over these past several years. I can only aspire to be so active when my golden years arrive!
Process Automation
Hall of Fame member,
Greg McMillan
This book, to be published by ISA, is due out soon and I’ll update the post with how to order it.
Here is the overview found on the back cover [I've included some hyperlinks]:
Written from a practical perspective, Advances in Reactor Measurement and Control underscores how control system design can address the different process responses and fundamental characteristics of the major types of reactors in the process industry.
This book enables the reader to learn what measurements, control strategies, controller features and tuning parameters will achieve process objectives for a given type of reactor. No prior education or experience in process engineering or control theory is needed. This book starts with the fundamentals and principles needed to become proficient in getting the best reactor and control system performance. The practitioner will be able to design, implement and support straightforward configurations based on the type of process and equipment.
McMillan—the author of more than 20 books, including several ISA best sellers, Process Automation Hall of Fame Inductee and the recipient of the ISA Life Achievement Award—educates through a practitioner’s experience and perspective, outlining the general concepts and details, from the field to the control room, for the control and optimization of batch and continuous reactors.
“Taking a practitioner’s approach, I believe, is unique,” McMillan says. “The concepts in this book are developed to help the reader understand the fundamental differences in reactor applications and improve the performance of nearly all types of reactors. This book is unique in providing readily configurable practical solutions for batch and fluidized bed reactors besides the more traditional continuous stirred tank reactors.
According to McMillan, the book’s practical value is reinforced through its:
- Simple presentation of the characteristics and implications of each of the dynamic responses needed to achieve the necessary efficiency, capacity, quality, and safety in operation.
- Clear explanation of the PID features and tuning and control loops needed for addressing the lack of smoothing in dead time dominant processes and the lack of negative feedback in integrating and runaway processes.
The material in this book represents knowledge from leading participants in the ISA Mentor program, Brian Hrankowsky and Héctor Torres, reflecting decades of experience in the pharmaceutical and chemical industry, respectively.
You can connect and interact with Greg and the folks he’s mentored over the past few years in his Mentoring Engineers discussion track in the Emerson Exchange 365 community.
Brian,
Do you have process history view on all four of your quad monitors?
If so, that is really what we are looking for.
Thanks.
Josh