Iacdrive|Automation Solution

SCADA & HMI

SCADA will have a set of KPI’s that are used by the PLCs/PACs/RTUs as standards to compare to the readings coming from the intelligent devices they are connected to such as flowmeters, sensors, pressure guages, etc.

HMI is a graphical representation of your process system that is provided both the KPI data and receives the readings from the various devices through the PLC/PAC/RTUs. For example you may be using a PLC that has 24 i/o blocks that are connected to various intelligent devices that covers part of your water treatment plant. The HMI software provides the operator with a graphical view of the treatment plant that you customize so that your virtual devices and actual devices are synchronized with the correct i/o blocks in your PLC. So, when an alarm is triggered, instead of the operator receiving a message that the 15th i/o block on PLC 7 failed, you could see that the pressure guage in a boiler reached maximum safety level, triggering a shutdown and awaiting operator approval for restart.

Here is some more info I got from my colleague who is the expert in the HMI market, this is a summary from the scope of his last market study which is about a year old.

HMI software’s complexity ranges from a simple PLC/PAC operating interface but as plant systems have evolved, HMI functionality and importance has as well. HMI is an integral component of a Collaborative Production Management (CPM) system; simply you can define that as the integration of Enterprise, Operations, and Automation software into a single system. Collaborative Production Systems (CPS) require a common HMI software solution that can visualize the data and information required at this converged point of operations and production management. HMI software is the bridge between your Automation Systems and Operations Management systems.

An HMI software package typically performs functions such as process visualization and animation, data acquisition and management, process monitoring and alarming, management reporting, and database serving to other enterprise applications. In many cases, HMI software package can also perform control functions such as basic regulatory control, batch control, supervisory control, and statistical process control.

“Ergonometrics,” where increased ergonomics help increase KPI and metric results, requires deploying the latest HMI software packages. These offer the best resolution to support 3D solutions and visualization based on technologies such as Microsoft Silverlight. Integrating real-time live video into HMI software tools provide another excellent opportunity to maximize operator effectiveness. Live video provides a “fourth dimension” for intelligent visualization and control solutions. Finally, the need for open and secure access to data across the entire enterprise drives the creation of a single environment where these applications can coexist and share information. This environment requires the latest HMI software capable of providing visualization and intelligence solutions for automation, energy management, and production management systems.

Automation engineering

Automation generally involves taking a manufacturing, processing, or mining process that was previously done with human labor and creating equipment/machinery that does it without human labor. Often, in automation, engineers will use a PLC or DCS with standard I/O, valves, VFDs, RTDs, etc to accomplish this task. Control engineering falls under the same umbrella in that you are automating a process such as controlling the focus on a camera or maintaining the speed of a car with a gas pedal, but often you are designing something like the autofocus on a camera or cruise control on an automobile and oftentimes have to design the controls using FPGA’s or circuits and components completely fabricated by the engineering team’s own design.

When I first started, I started in the DCS side. Many of the large continuous process industries only let chemical engineers like myself anywhere near the DCS. EE landed the instruments and were done. It was all about you had to be process engineer before your became a controls engineer. In the PLC world it was the opposite, the EE dominated. Now it doesn’t line up along such sharp lines anymore. But there are lots people doing control/automation work that are clueless when comes to understanding process. When this happens it is crucial they are given firm oversight by someone who does.

On operators, I always tell young budding engineers to learn to talk to operators with a little advice, do not discount their observations because their analysis as to the cause is unbelievable, their observations are generally spot on. For someone designing a control system, they must be able to think like an operator and understand how operators behave and anticipate how they will use the control system. This is key to a successful project. If the operators do not like or understand the control system, they will kill a project. This is different than understanding how a process works which is also important.

DC Drives Field Voltage Control

To control the speed of a DC motor below its base speed, the voltage applied to the armature of the motor is varied while the field voltage is held at its nominal value. To control the speed above its base speed, the armature is supplied with its rated voltage & the field is weakened. For this reason, an additional variable-voltage field regulator is needed for DC drives with field voltage control. Field weakening is the act of reducing the current applied to a DC motor shunt field. This action weakens the strength of the magnetic field & thereby increases the motor speed. The weakened field reduces the counter emf generated in the armature; therefore the armature current & the speed increase. Field loss detection must be pro vided for all DC drives to protect against excessive motor speed due to loss of motor field current.

DC drives with motor field control provide coordinated automatic armature & field voltage control for extended speed range & constant-horsepower applications. The motor is armature-voltage-controlled for constant-torque, variable-horsepower operation to base speed, where it s transferred to field control for constant-horsepower, variable-torque operation to motor maximum speed.

Machine tool

Ahh I see the words machine tool and shop floor; now I can see where you guys are coming from. The type of machines that you talk about were controlled by relay logic and then when technology arrived the electrical drawings were probably “converted” into ladder logic. The techs had lots to do because you cannot translate relay based systems into ladder logic 100% successfully as they behave differently.

The guys doing this work are just that programmers. They are probably NOT software engineers and are closer to the shop floor techs who are fiddling about with your machines.

I can and have designed many control systems for automotive type machines such as hobbing machines, milling and borers. Very easy code to write if you do not translate the relay logic directly but use the existing documentation as a reference. All of the systems that I did work really well. I did some similar type of machines in a pharmaceutical plant but that was after another company was kicked out after failing to make the machines work. I had to redesign the whole control philosophy as the machine tool world methods used were really a bad fit for the intended application.

But that is only one facet of the work that we Industrial Automation Engineers do. I work in many different industries where the demands for quality deigned, controlled and maintained systems is paramount. We go through proper project life cycles and we deal with the project from inception through design, build, test and commissioning. We even do the maintenance of the systems. We do not sit in Ivory Towers but do the work at the customer site no matter where that is on the planet.

Electrical engineers are tasked with doing all things electrical and we are tasked with all things control. Programming, that is writing the actual code is only one part of what we do and not necessarily the most time consuming part.

I am here in Kazakhstan at the sharp end of a multi-billion dollar project a long way from any ivory tower. I fix other engineers software too, why? Because the vendor may use offshore resources to code much of the systems that are installed at site. Kazakhstan has extreme Summers (up to 60degC) and Winters (down to -50degC), most of the people are friendly but English is not so prevalent. A long way from your shop floor environment. Far more dangerous too as the plant processes H2S or will when first Oil & Gas comes onshore.

Here I have supported technicians performing loop checks and other engineers doing logic tests. I can diagnose many loop problems without even looking in the code but just by looking at what is happening. I have found that if a loop doesn’t work then the techs approach us first as a one stop shop to give them an answer rather than actually trouble shooting the loop themselves.

I said to you guys before you need to get out and look at other industries and see what is going on in the rest of the world. Much of what I have seen would go a long way to improving your world too! Engineers like myself are far away from the “programmers” you have.

Three Phase Input DC Drive

Controlled bridge rectifiers are not limited to single-phase designs. In most commercial & industrial control systems, AC power is available in three-phase form for maxi mum horsepower & efficiency. Typically six SCRs are connected together, to make a three-phase fully controlled rectifier. This three-phase bridge rectifier circuit has three legs, each phase connected to one of the three phase voltages. It can be seen that the bridge circuit has two halves, the positive half consisting of the SCRs S1, S3, & S5 & the negative half consisting of the SCRs S2, S4, & S6. At any time when there is current flow, one SCR from each half conducts.

The variable DC output voltage from the rectifier sup plies voltage to the motor armature in order to run it at the desired speed. The gate firing angle of the SCRs in the bridge rectifier, along with the maximum positive & negative values of the AC sine wave, determine the value of the motor armature voltage. The motor draws current from the three-phase AC power source in proportion to the amount of mechanical load applied to the motor shaft. Unlike AC drives, bypassing the drive to run the motor is not possible.

Larger-horsepower three-phase drive panels often consist of a power module mounted on a chassis with line fuses & disconnect. This design simplifies mounting & makes connecting power cables easier as well. A three phase input DC drive with the following drive power specifications:

Nominal line voltage for three-phase-230/460 V AC
Voltage variation-+15%, -10% of nominal
Nominal line frequency-50 or 60 cycles per second
DC voltage rating 230 V AC line: Armature voltage 240 V DC; field voltage 150 V DC
DC voltage rating 460 V AC line: Armature voltage 500 V DC; field voltage 300 V DC

Floor programmer and office programmer

The biggest differences between the floor programmer and the office programmer is often a piece of paper (knowledge and experience do not replace a piece of paper in the mind of HR person that has no understanding of the position they are seeking to fill) and that the floor programmer must produce a working machine. Also many an excellent programmer will never put up with the office politics seen in many companies. To appear right for me is worthless when being right is the goal. In a physical world it can be shown that a program is right or wrong because the machine works or does not. In the theory driven world of the office that can not happen, so appearing correct as well as being correct is necessary.

If you are the best programmer in your company or the worse. If you are the worse one then maybe you are correct. But if you are the best then please take a close look at the worse programmer’s work and tell us if there is not a need for some improvement.

I have cursed out more than one officer programmer for missing logic which on the floor is easy to see is necessary. The office programmer was more than once, myself. Making logic to control machine in theory is far more difficult a task than modifying that logic on a real running machine. Maybe your imagination and intelligence can create a theoretical image that matches the physical one.

Many office programmers are not up to that level. They lack the intelligence, imagination, experience or time to take an offline program that can be loaded and run a machine without help. But no fear, most start-up techs cannot debug a machine after the build is complete and remove all issues that will surface when the machine enters a customer’s plant and full production.

A good program will grow as time passes. To fill in the gaps in the software, to change the design from what design intended to what production requires and to cover the design changes as product models evolve. Static is not the floor condition of a good company, products and machines evolve and grow. More reliable, durable, quicker tool changes or device swaps, lower cycle times or more part types. There are examples of logic once written it never changes but that is not the whole of the world just one part of it.

Single Phase Input DC Drive

Armature voltage-controlled DC drives are constant torque drives, capable of rated motor torque at any speed up to rated motor base speed. Fully controlled rectifier circuits are built with SCRs. The SCRs rectify the supply voltage (changing the voltage from AC to DC) as well as controlling the output DC voltage level. In this circuit, silicon controlled rectifiers S1 & S3 are triggered into conduction on the positive half of the input waveform & S2 & S4 on the negative half. Freewheeling diode D (also called a suppressor diode) is connected across the armature to provide a path for release of energy stored in the armature when the applied voltage drops to zero. A separate diode bridge rectifier is used to convert the alternating current to a constant direct current required for the field circuit.

Single-phase controlled bridge rectifiers are commonly used in the smaller-horsepower DC drives. The terminal diagram shows the input & output power & control terminations available for use with the drive. Features include:

Speed or torque control
Tachometer input
Fused input
Speed or current monitoring (0-10 V DC or 4-20 mA)

“critical” operation with a double-action cylinder, hydraulic or pneumatic

If I had a “critical” operation with a double-action cylinder, hydraulic or pneumatic, I’d put proximity sensors on both ends of travel, typically with small metal “marker” on the shaft. Each input “in series” with the “output” to each coil, time delayed to give the cylinder a chance to reach its destination. The “timer” feeds the “alarm.” If you want to spend the money for a pressure switch (or transducer) on each solenoid output, that’s a plus.

Now you can tell if there was an output to the solenoid from internal programming, if not another interlock prevented it from actuating. If there is an output to the solenoid and no pressure, then the signal did not reach the coil (loose wire somewhere), if it did the coil may be bad, if the coil is good and no pressure, the solenoid may be stuck or no pressure to it from another supervised failure or interlock. If there was sufficient pressure and the cylinder travel not reached, then the cylinder is stuck.

As a technician crawling over all kinds of other people’s equipment since 1975, I could figure out a lot of this from an old relay logic or TTL control system. A VOM confirms whether there is an output to the correct solenoid at the control panel terminals. This lets you now which direction to head next. If there is no power, it’s “upstream” of there, another interlock input that needs to be confirmed, time to dig into the “program.”

If there is power and the cylinder does not move it’s a problem outside of those terminals and the control system. I’d remove the wiring and check for coil resistance, confirming the coil and field wiring integrity while still at the panel. If everything checks out then go to the cylinder and see if a pressure gauge shows pressure on the line with the coil energized – presuming there is pressure to the valve. No pressure would be another “input alarm” from another pressure switch. If there is pressure and power to the valve and no pressure, the valve is bad. If there is pressure on the output side and the cylinder does not move – the cylinder is stuck or mechanically overloaded.

I&E “technicians” may know a lot about programming and code, but if they don’t know how a piece of equipment operates I/O wise then they don’t have a clue where to start looking. Then I guess you need all the sensors and step by step programmed sequences to “spell it out” for them on a screen. A device sequence “flow chart” may help run I/Os out for something like above. I/O status lights on the terminals like PLCs can easily confirm at a glance if you have the proper inputs for a sequence to complete, then you should have the proper outputs. Most output failures are a result of correct missing inputs. The more sensors you’re willing to install, the more the sequence can be monitored and spelled out on an HMI.

From a factory tech support in another location, being able to access the equipment remotely is a huge plus, whether directly through modem, or similar, or indirectly through the local technician’s computer to yours i.e. REMOTE ASSISTANCE. A tablet PC is a huge plus with IOMs, schematics and all kinds of info you can hold in one hand while trouble-shooting.

DC Drives Basic Operation Principles

DC drives vary the speed of DC motors with greater efficiency & speed regulation than resistor control circuits. Since the speed of a DC motor is directly proportional to armature voltage & inversely proportional to field current, either armature voltage or field current can be used to control speed. To change the direction of rotation of a DC motor, either the armature polarity can be reversed, or the field polarity can be reversed.

DC drive diagram

The block diagram of a DC drive system made up of a DC motor & an electronic drive controller. The shunt motor is constructed with armature & field windings. A common classification of DC motors is by the type of field excitation winding. Shunt wound DC motors are the most commonly used type for adjustable-speed control. In most instances the shunt field winding is excited, as shown, with a constant-level voltage from the controller. The SCR (silicon controller rectifier), also known as thyristor, of the power conversion section converts the fixed-voltage alternating current (AC) of the power source to an adjustable-voltage, controlled direct current (DC) output which is applied to the armature of a DC motor. Speed control is achieved by regulating the armature voltage to the motor. Motor speed is directly proportional to the voltage applied to the armature.

The main function of a DC drive is to convert the fixed applied AC voltage into a variable rectified DC voltage.

SCR switching semiconductors provide a convenient method of accomplishing this. They provide a controllable power output by phase angle control. The firing angle, or point in time where the SCR is triggered into conduction, is synchronized with the phase rotation of the AC power source. The amount of rectified DC voltage is controlled by timing the input pulse current to the gate. Applying gate current near the beginning of the sine-wave cycle results in a higher aver age voltage applied to the motor armature. Gate current applied later in the cycle results in a lower average DC output voltage. The effect is similar to a very high speed switch, capable of being turned on & off at an infinite number of points within each half-cycle. This occurs at a rate of 60 times a second on a 60-Hz line, to deliver a precise amount of power to the motor.

Design and Implementation

The owner of the system should provide clear requirements of what the system should do and should define what constitutes “maintainability” of the system. This places a burden on the owner of the system to consider the full life-cycle of the system.

1. You need good design documentation.

2. All source code should be well-documented.

3. Coders should be trained on the techniques used and mentored,

4. The use of “templates” helps ensure that coders and maintenance alike are familiar with routine functions.

5. The HMI should provide clear indication of faults and interlocks.

6. The HMI should provide clear indication of equipment statuses.

7. Any code that is hidden must “work as advertised”. This means that it must be completely and unambiguously documented for all inputs, outputs, statuses, and configurations. It must be thoroughly tested and warranted by the vendor,

8. All code should be well-tested. (I have found that the first line of defense is to simply read the code!)

Post-Startup
1. The owner should have a change-control procedure to manage modifications.

2. All users and maintenance support personnel should have adequate training. Training needs to be periodically refreshed as it can become stale through lack of use.