Showing posts with label PLC. Show all posts
Showing posts with label PLC. Show all posts

Tuesday, November 15, 2011

Integrated Safety And Regulatory Control

Addressing functional safety and regulatory control in a single system has been a challenge for many years – even more so when systems are destined for use in a hazardous area.

A technical solution from Siemens is said to offer these combined capabilities delivering benefits such as a simplified safety verification process, tangible cost savings and scalability Ian Curtis, safety consultant for Siemens Industry Automation, explains.

The functional safety and hazardous area protection world’s are often closely associated. However, when it comes to meeting the requirements of these two complementary yet distinct disciplines in a distributed I/O system, there are many technical challenges to overcome.

A range of SIL 3 capable failsafe I/O modules for the Siemens ET200iSP hazardous area remote I/O station gives users the potential for new safety system architectures which boast simplified engineering and a reduction in the total lifecycle cost for automation and safety.

Early process automation systems were typically distributed but, ironically, with the advent of the Distributed Control System (DCS), system architectures actually became much more centralised. In recent years, there has been a shift back toward a more distributed approach. This same trend has been reflected, albeit to a lesser extent, in distributed safety within the process industry but the recent addition of capability for integrated failsafe I/O in the hazardous area looks set to accelerate this trend.

Given the conservative nature of the industry there are still many users who prefer to stick to a centralised approach, particularly when intrinsic safety requirements are involved. The traditional practice of putting the controllers and I/O in the safe area and using IS barriers, is well understood and still in common use. However the tough economic climate of the last few years has increasingly prompted end users and OEMs to assess and adopt new concepts such as distributed failsafe systems which can actually solve many problems.

The scalability of these distributed systems, particularly those that combine control and safety in the same infrastructure, means they can also be used cost effectively for small process units, OEM skids or rotating equipment with smaller I/O counts.

The distributed approach reduces the need for multi-core cables carrying I/O signals; this means reduced installation effort; reduced risk of wiring errors and simplified bus connection of I/O stations.

SIL3 capability in a Zone 1 hazardous area is a step change that will strengthen the success of distributed I/O systems and really open up new possibilities. Users from the oil and gas industry, chemical industry, and other major hazard industries will look to benefit from the ability to combine configurations that include non-fail-safe modules, such as standard inputs/outputs and relay modules, alongside failsafe modules. Another key benefit is the potential for cost saving through the elimination the ex-barriers, less wiring and space optimisation.

Many OEM suppliers are also exploiting the possibilities of distributed automation in hazardous areas, particularly when they market their products to target emerging markets. If the end customer's employees lack expertise, the use of a centralised configuration often leads to wiring errors - and a lengthy commissioning phase.

When the ET200 iSP remote I/O station is located directly at the machine, or process skid, commissioning is straightforward and the space savings are considerable. As complicated and space-consuming as the earlier approach was – with remote I/O cables, terminals, and ex-barriers – this marshalling effort can now be completely eliminated. It is also easier to achieve the redundancy required in many applications: The ET 200iSP is connected via RS485-iS in hazardous areas. The path from the CPU in the control room to the field can also be redundant. Digital and high availability requirements are covered thanks to bus use.

Because of an increasing popularity with the OEM market, if an end user doesn't start out with distributed safety as a strategy for their plant they often “inherit” it as process skids and OEM type equipment come equipped with their own safety systems.

The first large customers for the ET200 iSP F-modules have been from the oil and gas industry. They have used the fail-safe modules in water-oil separating equipment and tank farms. Other early adopters have come from the chemical industry. Offshore projects generally also lend themselves to distributed safety and the combination of failsafe and hazardous area capability afforded by these new modules will be attractive for such applications.

An alternative to DCS or PLC/SCADA?

Traditionally, users have had a choice between a DCS or a PLC/SCADA approach when selecting a control system for use in process control applications. Richard Sturt, Rockwell Automation business development manager, process Industries, believes that Rockwell can offer a solution for users needing elements of both of these approaches.

A key benefit of traditional DCSs was that the suppliers took a ‘systems approach’ and it was designed for large scale applications. Much of the work of integrating different parts of the system was taken care of by the DCS vendor by using a single database for the complete system.

The DCS approach is to configure the system using standard control objects and faceplates, reducing engineering and providing standardisation. Most DCSs also offer fieldbus communications, tools for process optimisation and asset management packages to improve maintenance. More recently DCS suppliers have introduced more scalable solutions for smaller applications

However, there are a number of potential shortcomings in the DCS approach. Many process plants have a large number of OEM packages that need to be integrated with the overall process control system and it is unlikely that the OEM will use a DCS for their control system. In some manufacturing processes there is a requirement for different types of control; process, discrete, high speed, drive control, motion control or machinery safety. The DCS is not designed to cope with these types of applications and, if a manufacturing process covers multiple disciplines, the DCS will only ever be suitable for part of the system.

DCS has, traditionally also been an expensive product to support throughout its life. Annual licensing and support costs can become a significant part of the overall cost of ownership. The majority of DCSs are engineered and supported by the original manufacturer and are not freely available though other channels, leaving the end user reliant on its DCS vendor.

Most DCSs had closed and proprietary system architectures. More recently suppliers have adopted more open standards but, in many cases, this approach has limitations which often makes it complicated to integrate with MES and other business systems.

The PLC/SCADA approach
Although PLCs were originally developed for discrete applications, most cover a wide range of applications. The term Programmable Automation Controller (PAC) is now used to describe many products to distinguish them from older systems that were focused on discrete logic. This flexible approach offers multiple programming languages, open communications, and scalability for different applications. There are many systems integrators able to integrate PLC/PAC technology, often with specific industry or application knowledge. This approach is also ideal for OEMs who can select a cost effective product to meet their requirements.

Although PLCs and PACs have become more powerful they still have a number of features that are missing when compared to the DCS approach.

A typical PLC/SCADA system has at least two databases. The user has to configure the PLC database and then separately configure the database in the SCADA system. At initial engineering stages there may be an option to import the PLC database into the SCADA system but this will require manual modification as changes are made during commissioning and when enhancements are made. If additional software packages are required they are likely to have their own separate databases too, that will need to be configured.

Another potential weakness is that not all PLCs have features required for demanding continuous process control applications. In some cases they will lack the ability to modify the system on-line or will not include high availability features like redundancy from I/O modules to supervisory systems.

Process optimisation and asset management is another area where traditional PLCs may be lacking compared to a distributed control system.

The best of both worlds
A true ‘Plant-wide Automation’ approach takes the best features from DCS and PLC/SCADA systems and combines them into a single system. It combines the ‘systems approach’ of a DCS and flexibility of a PLC/PAC to provide a solution for multiple applications.

This approach has benefits that can improve plant performance and reduce costs. A single architecture can be selected for any application whether it is continuous process control, high-speed OEM equipment or a small batch reactor. It simplifies integration and reduces engineering costs. The resulting system will have a seamless communications architecture allowing access to plant data for process optimisation, asset management and integration with MES. Support costs will also be minimised by reducing training requirements and the cost of holding spares.

Rockwell Automation has recognised the benefits of combining the features of Distributed Control Systems and PLC/SCADA solutions into a single Plantwide Automation system with its PlantPAx. As part of the companies Integrated Architecture, it allows a single architecture to be used for a wide range of applications, including process, batch, drives, motion and safety.

The importance of being able to address such a wide range of applications is key to a truly plant-wide automation system. Operating any combination of these applications through a purpose-designed single architecture and software environment makes it possible to achieve the benefits of both a DCS and a PLC/SCADA system without many of the traditional downfalls of either. It is this seamless inter-operability that makes plant-wide automation systems so effective.

At the core of the PlantPAx is the single database that is used for the Controller, HMI, Historian, Batch Management, Asset Management and Business Intelligence Tool/Reporting Package. Any data created in the system is instantly accessible to all the software packages that need it and a single security model simplifies the management of user’s profiles.

The key principles behind this solution can help to drive a lower cost of ownership. Using a single architecture reduces initial engineering and integration costs. The process optimisation and business intelligence tools help to maximise plant efficiency.

Monday, October 24, 2011

CP1E smaller Omron PLC

New design. For small PLC Omron. To achieve the desired result with a shorter time and cheaper cost. Of experience and learning to truly Omron developed a new concept to develop products that focus on simplicity and economy but also its readiness to continue for the future.

Input and output prices were down. This is achieved using a high-performance chips that can handle high-speed signals at 100 kHz for the control of machines with speed and precision. Also equipped with high speed-output 100 kHz (in transistors) for the type of servo motor. Completely redesigned. The input / output of CP1E are cheaper compared to similar products.

An analog of the modern machinery to control the variable parameters in analog format. To activate other devices.

With a continuous output CP1E-NA20 (under the CP1E) packed into this capability without having to buy more. The analog resolution up to 1 / 6000 or 0.016% full scale resolution detail to cover most of it.

It has USB and RS232C with it has come to a USB port for connecting a computer to upload or download downloading program. USB cable is available in the market for the RS232C standard has a touch screen and whether the presence of an external load cell. Or used in SCADA.

To further expand in the future. Whether it be on a channel by using the expansion units 3 units or more channels of communication option board is required to choose a RS485/422A, Ethernet or RS232C.

Friday, October 14, 2011

OMRON PLC - How to Use OMRON PLC Function Block

Function Block potential of our Omron CS / CJ PLCs for future projects. Our typical projects include the control of a few hundred devices (doors, intercoms, cameras, card readers, etc.). It is generally of PLC logic, just the same, except that they shall refer to various IO addresses.

Desrcibe The logic that is suitable for your project, you are perfect for Function Block processing.



If you and add a Function Block instance, copy the same instance will be labeled as you describe.
You can create a new copy by right-clicking on the Function Block and the change of the name.

However, it is quite possible the same instance in multiple copies Function Block Function Block reuse. But be careful that you do so only if the Function Block-code can be worked in, a single scan, so there are no timers, counters and data control statements, such as PID, which require multiple scans complete.
So if you Function Block contains only simple functions the same conductor Function Block instance can use and saves space. If your case requires separate Function Block user, you can still edit and update all at once through the internals of Function Block Function Block invocations.
You can find Function Block to authorities under the symbol table data type “Function Block”.
For more information about Function Block, see the “CX-Programmer Operation Manual Function Blocks Structured Text” that are found in the CX-Programmer-folder in the Start menu.

I have a love-hate relationship with building blocks. In my experience:

Function blocks are good for:
1. Mathematics (transformations, scaling, floating-point calculations, etc.)
2. Loops (I find it much easier to code loops in structured text)
3. repetitive tasks such as door logic, logic cylinder, stop logic, etc.

Function blocks are bad because:
1. too much memory
2. adds scan time
3. difficult problems if you do not know how Function Block does
4. to test more work ahead and to document
5. can be dangerous if you try to get online editing and “accidentally” change all instances of the block

The newest and latest CX Programmer Version 4 CPUs possible Function Block can not be created / edited by online processing.
CPU version 4 function blocks can be processed online, but it can not be created (from scratch) online.
CX Programmer 7.0 or higher is required for this function.

The indirect nature of the programming can be very powerful when you get your head around ..
Just a little something about Function Blocks with Omron PLC:

Look in the PLC memory usage on the “View / See Memory (UM). Sorry, but I’m in the Cx-P Spanish!
Sometimes, when large Function BlockS (ie, floating-point calculations), or simply to build only Function Blocks Omron (as Mechatrolink or DeviceNet), the PLC CJ1M become small and it must be greater than PLC (CPU43 or higher).

Function Block is a good tool to typical problems of copy and paste causes the programming to avoid if you need more time in the same routine, order, or steps, but conscious memory (EMS) are!

Tuesday, October 4, 2011

Technology in the PLC

PLC has been developing the capabilities of simple form and transform the same price level ever. And the development of which will go on. What’s left to do and tons more or no less interesting question.

As a related technology. We conclude the development of PLC from the past to current and upcoming follows.

1) patterns of language use. Still can not say that it will not use the ladder diagram (Ladder Diagram), but the role of the function block (Function Block) is more or even a programming language (Instruction List), which will combine both possible. IEC61131 requirements or not.

2) The development of the ability of PLC to manage mobile devices that generate a lot more like a servo motor. Linear motors. Inverter. By either increasing the speed of mobile functionality to support fast and accurate. Development of special cards for specific actions. Software development or software package for ease of use. These things will become easier and more common in PLC new generations.

3) the support for a network which has become a standard already. Optimization with a reduced number of cables used in plant and machinery is a current push for network-level devices (Component network), such as DeviceNet, Componet, EtherCat the needs for communication of control and order. and management of production networks driven in control and command (Control network), such as Ethernet / IP Controller Link and so on.

4) speed development. Still significant. Response to changes in a timely manner of machinery, more and more intense. The high-speed machinery. Especially in response to a device Encoder, Interrupt input, High speed pulse, even high-speed analog channels.

May be more Development plc. If you are considering the purchase or invest any new PLC. PLC that you are interested or have developed?

Sunday, September 25, 2011

Solve CP1H R88D Servo Motor Controller

I work around a CP1H R88D servo with a pulse output 0 problem. All power settings are standard, except for the electronic gear ratio. The example is the Handbook of 2000 pulses per revolution motor set.
Fine adjustment of the drive car (one horizontal spindle).

I have the move to Omron (power) function block in the CP1H.
The distance between the CP1H and the servo is about 6 m (2 m). The drive is a Panasonic with brake and encoder (not absolute).


Two cases:
1. 2000 pulses is not a revolution engine, only about 3 / 4 2000 pulses also not equal to 2000 forward pulse times (by a significant amount).
2. The highest speed I can use and still move the actuator 100, although I keep hearing that the CP1H is capable of more. The CP1H seems not the problem. When ordered with a speed of more than 100, the power simply ignore the incoming pulse.

I’ve been through all CP1H/R88D manual and found no answers. Has anyone successfully ran a similar sytem? Anyone have a hint of things to look for?
The manuals never a PNP output to the PLC station in pulse mode. It seems that the manuals are to be desired. I found three departments, which called into question. Well, I’m looking forward to implement the same system with an absolute encoder - should be a breeze - right!

Saturday, September 10, 2011

Monitoring memory space in the PLC.

Often used in the PLC to consider that choosing which version to use the CPU will have enough space to run the program. The count is difficult enough to evaluate. Because the function of machines, each machine has a different way of thinking is difficult and complex simplicity. And do not depend on the number of I / O.
So if you find ways to estimate a cursory I can do it without writing a program in advance because the CX-Programmer. Can be simulated. (Must be a joint program with the CX-Simulator).

Steps to use.

1. When writing a program so close to actually work. Is enough to see the capacity of content from programs like the CX-Programmer Tools by going to the Cross-Reference Report or press Alt + x.



2. Press the button Generate.

Total UM status means that all memory of this PLC model.
Free UM status means that the available memory remaining space to tell the normal PLC programming in units of step.

3. Commands each command of the PLC. To use the same memory. Depending on the complexity of the computation of new CPU can see that each step of the orders at the end of Part Programming Manual.


4. Students. Cross-Reference Report in addition to more memory space, the rest of the PLC can also be sure that nothing of the PLC variable that is already taken some Used many times. This would be ideal to modify or add applications. Which can be selected Report type: Usage overview (which is pretty. It shows only the active variables) Memory area: Choose the type of variables to display.

5. And then press the Generate button, the program displays a report describing the use of memory out.

Monday, September 5, 2011

History of PLCs

Today i have article that story in PLCs,Twenty-five years I was in my last year with Allen-Bradley PLC and a specialist and educator. I grew up with the PLC in 1774, the PMC. What a trip through the PLC-2, PLC 3, PLC 5, computer-based programming instead of a luggable terminal and a 10 MB hard disk for the PLC-3 GA module for remote data collection and programming remotely through the RM modules.

A laptop for programming (Data General) was more than $ 8,000. Hard drive space is outrageous expensive, and Windows will not be used. PCs were ahead, and programmers learned useful DOS software.
From 1977 to 1985 there was an enormous growth pattern that most had not imagined. Remote I / O, HMI, SCADA, and similarly, the PLC to the DCS world compromise. Servo Control was also available. Special keyboards set them up.
Bit-flipping was an art.

We had to do in ASCII module interfaces, and network modules with interfaces for mini-computers like the DEC VAX and PDP-11.

Some applications were too fast for the PLC, but not much. Everything was a good deal for the PLC and the companies and individuals.

In 1986 I founded my own company and am involved with the newfangled software arena. Life changes decision proved quite good.

ICOM, Tele-thinking, tender gray, Taylor et al. made DOS-based PC programming software. Moved to PC-based HMI and ARCnet came to town.

But what really changed since 1985? It depends on who you ask. Marketing vs Engineering is the battlefield, as hardware costs have fallen to the point of goods.

Let me table for the next month to develop a perspective on where we are and where we come from.

Applications that make use of automation changed, but some are not. The reasons for the use of automation, more enterprise-centric. This wish it was in 1985-it just was not easy to implement.

“Real time” a new meaning, so that access to data is crucial. It was, but the preservation of the data was primitive. OEMs developing and producing their own interfaces for the collection of data for customers. We just have easy access to such data today.


Electrician to resolve successfully the systems of fixed terminals. The documentation was found on the printed scale. Difficult to navigate, but they were successful.

Encoders, converters, control circuits and more linked (then and today) with special I / O. Today, however, there are I / O buses, remote I / O of something. Instead of treating a PLC data table for hiking or quantitative information, you get the data from the device. But the data is similar, yes?

At the risk has changed, old, I do not think much. ControlLogix is ​​no different than the PLC-3 from 1980. You can scan multiple cards to support redundancy, the use of special communication card, data collection and other languages. It is a remote I / O and remote programming possible in both.

Applications are available for client / server environments. Mainly based on UNIX, but they worked.

Then something really monumental happened changed the rules changed, the development cycle, and changed the operative work. This cycle / career change made changes, what we have today. We had the goods but few were in force.

The shift was monumental software. Windows 3.0, NT and IBM OS / 2 Presentation Manager creates a free-for-all. A small company called Wonderware HMI took over the company. Because it was so easy, PLC were targeted. Ethernet landed in the workplace, and ensure that each Ethernet PLC had to speak.

New and improved technology may not necessarily be a different function. get from 1985 to 2010 Oldsmobile Porsche both what you want. We want to buy different things with the data. This requires a number of different “things” and it’s slow, painful and not to the order indicated that to change much advertising.

Thursday, August 25, 2011

Automation Standard for PLC programming

The IEC 61131-3 standard for PLC programming is a non-standard, since many of the rules are so general, and because there are so many exceptions and extensions of the original proprietary software definitions and original promise of portability of software between devices are open.

Capitalism is a great positive force that could improve trade and increase economic benefit and mutual well-being of all: that is, until a few million bad apples begin to cut. Unfortunately too short-sighted and selfish business interests and their puppets legislative promise honest promises its customers and fellow citizens, but then they break for a one-sided personal gain and coat their crimes in another round of conservative financial policy. These are tumors, the invisible hand of Adam Smith should be able to clean themselves.

But combining the flypaper of false promises, advertising, spin and other trick-of-hand with a semi-conscious consumers, voters and other shellfish to purge these lesions to become resistant. Therefore, the old invisible hand can not seem to shake off the parasites, the patriotic singing her praises, and then do everything to undermine it. No wonder that vampires are so popular these days.

Of course, process control and automation sector is far from immune to this disease. Technical misinformation, dishonest marketing and products that do more to suppliers market shares, as a service to protect the customer “has his years of characteristics of the production. More than 10 years old, I thought it would be good to compare an article PLCs (SPS) and other devices to write head-to-head, if only to get a better idea of how this may have a particular application better than the other brand. What a rookie. Not only do I not have the technical means to do it, but I found it almost impossible to direct comparisons between the control and regulation technology components as a consequence of the small but significant and seemingly inexplicable differences in their specifications and operating parameters of research. Resources told the time to me that many of these differences redundant and seemed to exist only in order to avoid comparison with competing products. How beautiful.

And do not even get me started on the long struggle fieldbus and the subsequent eight-member non-standard IEC 61158 standard. It was as one would a bunch of clowns came through on a railway line argument for the Ethernet Express and mowed them down all. Of course some of the more nimble acrobats survived by jumping on a moving train with their versions of its Ethernet, they used to dilute, I mean, make Ethernet robust enough for the manufacturing sector since.

“I weep for you,” said the Walrus. “I am deeply sorry.” With sobs and tears he from which the biggest, sorted with his handkerchief to his eyes streaming. -Lewis Carroll, Through the Looking-Glass and what Alice found there, 1872. ”
One of the most unfortunate examples of this misleading and useless arguments that further development of the IEC 61131-3 standard for programming PLCs. Introduced in 1993 and revised in 2003, including the five sections of software rules for ladder logic diagrams, block diagram, structured text, sequential lessons and lists.

But for many programmers, developers and users believe it is another non-standard, since many of the rules are so general, and because it can be so many exceptions and proprietary software enhancements, that their original definitions and original promise of portability of software between the devices is open.

“I have already maintained by that I do not believe that a standard as much as a guide for the vendor product,” says Jeremy Pollard. Our many years of “Embedded Intelligence columnist in Control Design and staff, has detailed offer about the problems with 61131-3 and the benefits they can still use. You can read all about it on www.controldesign.com/articles/2008/107.html.
Unfortunately, reminds a lot about the development of standards 61131-3 and other efforts to undermine me about Captain Barbossa in Pirates of the Caribbean. When talking about the pirates’ code of brotherhood, “he rolled his eyes and says,” Well, they tend guidelines. ”
Refer from By Jim Montague

Tuesday, August 23, 2011

What can you expect from Mitsubishi Modular PLCs?

Global use
A wide range power supply means your Modular System Q will work all over the world and with the huge range of shipping approvals, CE compliance, as well as manufacturing to Automotive industry quality levels, SystemQ is a product to trust.

Totally scalable
System Q is designed to grow with your application, from the Q00J standalone solution to the networked and redundant process CPU Q25PRH. System Q's platform concept allows you to add and customize the special functions you need.

Multi CPU
The SystemQ Automation Platform allows you to use multiple CPU’s on a single backplane. You can combine up to four CPU types, such as PLC, Motion, PC, Q-C and Process CPU’s, as a single seamless solution.

Multi network connectivity
From basic AS-Interface to Ethernet based networks, System Q can communicate easily with Mitsubishi or third party products. To increase the productivity in your plant, System Q can also provide a direct connection to any database based on SQL via an Ethernet connection.

Flexibility
The wide range of power supplies, CPU’s, I/O Modules, Special Modules and Communication Modules makes System Q one of the most flexible modular automation systems in the world.

Dual redundancy
The redundant Process CPUs Q12/25PRH can, with standard PLC technology, provide a hot standby system with the automatic synchronization of data. The modular concept also allows different degrees of redundancy from power supply and control systems to redundant network modules.

Friday, July 1, 2011

Mitsubishi Electric Modular PLC – MELSEC L Series

The Melsec L series is a powerful but compact modular controller with many features built-in to the CPU itself. With its excellent cost performance and usability it is ideal for use in mid-size control applications.

High system flexibility
The rack-free design promotes high system flexibility with minimum form factor. The single-CPU architecture includes built-in Ethernet and Mini-USB interfaces, a SD/SDHC memory card slot for program storage and data logging, and 24 digital I/O for simple high-speed counting and positioning functions. The high-performance CPU also includes a CC-Link V2 Master/Local station for connection to the powerful open field network CC-Link.

Besides the functions already built-in, the CPU can be supplemented with up to 10 extension and special function modules for additional digital and analog I/Os, highspeed counters, communications interfaces, Simple Motion, positioning etc.

The compact size, easy expandability, networking capabilities, and multitude of built-in high-powered functions makes the L series ideal for both stand-alone machines as well as networked stations in larger applications.

Data logging
The built-in data logging function provides an easy way to collect information for troubleshooting, performance evaluation, and other uses. The included configuration tool makes setting up the data logging function a breeze with a step-by-step wizard like interface. Using GX LogViewer, the captured data is easy to interpret and understand.

USB and Ethernet as standard
The built-in USB 2.0 port or Ethernet interface can be used to connect directly at the installation site. The Ethernet interface supports direct connection and does not require any configuration of the PLC or PC to operate.

Advanced programming software
GX Works2 represents the next generation in PLC maintenance and programming software and is perfectly suitable for the L series.

Monday, June 6, 2011

Mitsubishi Electric Modular PLC – PLC control

The modular concept
Building on its predecessor, the AnSH, System Q is a control concept that allows users to mix and select the best combination of CPUs, communication devices, specialist control modules and discreet I/O on a back- plane. This allows users to configure systems into what they need, when they need it, where they need it.

Multiple capabilities
Basic and advanced PLC CPUs, specialist motion and process controllers and even PCs can be combined into a single System Q solution with up to four different CPUs. This gives users a choice of control philosophies, programming concepts and programming languages – all from a single platform.

An automation platform for the future
Flexibility and scalability are key design features that enable System Q to truly be a single Automation Platform. Users can apply simple control to an individual machine or integrated plant wide management all from the same hardware base.

Supporting the System Q platform is a suite of software tools enabling easy and comprehensive integration through EZSocket, Mitsubishi’s own middleware. In addition, Mitsubishi also offer software tools that comply with international standards such as IEC1131.3, OPC and Active X. This tremendous flexibility permits users to reduce development time, simplify commissioning, and provide ongoing system maintenance.

Basic PLCs
Not every control application requires the full power of System Q. For example, many machine builders embed control technology into their machines and require small compact designs featuring flexible high-speed operation. System Q’s Basic PLC CPUs offer just this kind of solution, balancing power and performance against cost. A good example of this is the Q00J CPU.

This all-in-one unit provides power supply, CPU and backplane as a single, ready-to-use unit ideal for small systems that still require powerful performance. Other Basic PLC CPU options include the classic modular designs Q00 and Q01, the first steps on the path to the full System Q automation platform.

Advanced PLCs
For advanced machine designs and controlling manufacturing cells, including infrastructure and site-wide management, System Q’s advanced PLC CPUs offer incredible performance and versatility.

Processors are available with a wide range of memory capacities, all of which can be expanded as required. This means that System Q PLCs can support complex programs as well as store large volumes of operation data.

Universal PLC CPUs
These universal PLC CPUs are the latest generation of modular CPUs for the MELSEC System Q controller platform and they are the foundation of the iQ Platform system. They can be combined with the motion, robot and NC CPUs to configure scalable and highly flexible modular automation systems.

Scalable
With the exception of the embedded Q00J CPU, all System Q PLC processors are interchangeable, which means processing power can be increased as applications grow, protecting your investment in infrastructure and hardware.

Multi Processor support
Up to four separate System Q PLC CPUs can be placed in a single system. These can be used to control their own set of dedicated tasks or for sharing the processing and control load, making the total system highly responsive. This provides users with faster, more dynamic control, leading to better production quality and improved production rates.