A reader recently asked what the difference was between Point I/O and Flex I/O, and in today's article I'll share my thoughts on the subject.
Note: Those not familiar with Rockwell's I/O products may also want to consider 1756 I/O, 1769 Compact I/O, 5069 Compact I/O, and 5094 Flex 5000 I/O, all of which also support being used as distributed I/O.
How Point I/O and Flex I/O are similar
Let's start by comparing features common to both lines.
Distributed I/O Focus
While in years past up to sixteen local Flex I/O modules could be controlled by a local FlexLogix controller, those controllers have long been obsolete.
So today it's safe to say that both Flex I/O and Point I/O are predominately used in distributed I/O applications, as neither has it's own dedicated controller supporting large numbers of local modules.
This design allows modules to be removed and replaced without disturbing field wiring, and many panel designers have taken advantage of this design to eliminate interposing terminal blocks commonly used with standard “rack based” PLC modules.
How Point I/O and Flex I/O are different
Modules and Bases of a Flex I/O System:
Flex I/O modules are wide and rectangular, and plug into a terminal base that looks very similar to a standard three level terminal block.
Before I/O modules can be installed, the module bases must be connected from right to left, starting with the right most terminal base and ending with the adapter.
These terminal bases support being mounted directly to a back-panel, or being installed on din-rail.
Once mounted, to connect each terminal base a bus connector must be slid from right to left, which is actually one of the weak points of the Flex I/O design.
In addition to bent pins, the little plastic “hooks” on the top left of the terminal bases also break off quite easily.
As far as the total number of Flex I/O modules supported by the above mentioned netowrk adapters, each supports up to eight modules which can be split into two rows with the use of a Flex I/O bus extension cable (right to right) as shown below:
This means that while the first bank of I/O has slot numbers which increment from left to right, the second back of I/O has slot numbers that increment from right to left.
Modules and Bases of a Point I/O System:
More Modules, but Less Terminals
That said, once you get above thirteen modules an Expansion Power Module (1734-EP24DC) is required to allow additional power to be provided to the module power bus.
Additionally, since the terminal bases also carry field power, if you change from DC to AC modules (or need to isolate module power from one set of modules to another) you'll need a Field Power Distributor Module (1734-FPD) to break the field power bus to the left of the FPD, as well as provide terminals for the new field power bus to the right of the FPD.
And while Point I/O supports many more modules per Adapter, each module typically has less I/O points per module with less terminals per point.
With Flex I/O, it's common to have sixteen point modules sitting on top of three level terminal block bases with fifty two terminals.
With Point I/O, the largest input module only has eight points, and the standard terminal base also only has eight unique terminals.
And while you can get Point I/O blocks with up to twelve terminals, the additional terminals are internally tied to four of the original terminals (4 to 8, 5 to 9, etc.)
This leaves users with either having to add an additional terminal strip to wire the remaining connections of his two and three wire devices, or requires the addition of the relatively expensive 1734-CTM (Common) and/or 1734-VTM (Voltage) Point I/O modules to provide additional terminals.
To Hold (Or Not To Hold) Last State
The final topic I'll cover is how the two platforms differ when it comes to holding last state.
In many mission critical applications it's important for remote I/O modules to maintain their last state if they lose connection with the Programmable Controller.
In those applications, even if the connection to the PLC is lost, any outputs that were on may need to hold their last state and remain on to continue to remove the unwanted gasses from the area.
And while Flex I/O will always maintain last state when set to do so, oddly enough Point I/O will not hold last state if a user downloads a program to the programmable controller that is controlling the Point I/O even when the Point I/O is set to maintain it's last state.
Let us know along with any thoughts, questions, or opinions you have by clicking on the “post a comment or question” link below.
Editor's note: If you work in the industrial automation field and would like to share your experiences with our audience, please contact us using this form: Contact Us. If we publish your article we'll send you a $30 Amazon gift card (or equivalent via PayPal) in appreciation for your efforts!
- P+F USi-Safety Rated Ultrasonic Sensor (P87) - January 19, 2022
- IFM CR1203 HMI Controller: Initial Setup & Adding Ethernet IO in CODESYS - January 6, 2022
- Happy New Year! - January 1, 2022