Hardware Comparison: SLC 500 Controllers vs. CompactLogix L5370/80
The Allen-Bradley SLC-500 product line was introduced nearly thirty years ago. The product line has reached Active Mature status, with many modules at End of life or discontinued. Active Mature products are still fully supported; however, you can gain value by migrating to a new product of family of products. In this post, we compare the SLC-500 family to the preferred migration product family, the CompactLogix processor.
When Allen-Bradley released the CompactLogix 5380 controller it boasted significant performance improvements (+20% capacity and 5-20x faster scan times) over previous CompactLogix models. This performance is orders of magnitudes faster and more capable than the SLC-500 platform. For an in-depth comparison, we will compare system architecture, memory, scan time, I/O capability and power connections.
|CPU||16-Bit operations||32-bit operations|
|Programming Languages||Relay ladder||Relay ladder, Structured Text, Function block, SFC|
|Operating System||Logic based on program files||Logic organization and function based on tasks, programs and routines|
|I/O Processing||Mapped to I/O data tables. Synchronous I/O scanning||Tag based I/O Asynchronous I/O scanning|
|Data||Data stored in Data Tables Global data stored in Data Tables||Tag based data, supports local and global data Can be shared with other controllers as produced/consumed tags Data table format emulation using Array tables|
|Timers||Timers based on 16-bit, Selectable time bases||Timers based on 32-bit architecture Single 1ms time base|
|Communications||Built-in Ports: SLC-5/03 – DH-485, RS-232 SLC-5/04 – DH+, RS-232 SLC-5/05 – Ethernet, RS-232||Built in ports: Dual Ethernet I/P 1-USB Client|
|Block Transfer read/write instructions (BTR/BTW) Message (MSG) instructions. EtherNet/IP, DH+, DH-485, or RS-232 (DF1, ASCII, or DH-485 protocol) communication dependent on built-in ports||MSG Instructions EtherNet/IP –Embedded switch –Single IP address USB Client (Programming & FW Updates) Communication Options: ControlNet, DeviceNet, Data, Highway Plus, Remote I/O, SynchLink|
|Integrated Motion||Motion control via additional PLC modules||EtherNet I/P|
|Memory Size (words)||SLC-5/01 – 1K, 4K||L306 – 0.6MB|
|SLC-5/02 – 4K||L310 – 1.0 MB|
|SLC-5/03 – 8,16,32K||L320 – 2.0 MB|
|SLC-5/04 – 16,32,64K||L340 – 4.0 MB|
|SLC-5/05 – 16,32,64k||L350 – 5.0 MB|
|SLC-5/03 – 8,16,32K||L380 – 8.0 MB|
||L3100 – 10.0 MB|
For memory usage comparison, a good “rule of thumb” is to allow for approximately 10-12x program size when converting from SLC-500 to Logix based programs. For example, a full 32 KB SLC program converted to a Logix program will consume approximately 360 KB in the Logix controller. For migration purposes, 32K or less SLC programs will fit in any Logix controller. For 64 KB SLC programs, select a Logix controller with at least 1Mb of memory.
The SLC-500’s 16-bit architecture is based on executing logic contained in program files. Scan time can be roughly calculated based on logic program size. CompactLogix controllers use 32-bit operations with logic execution based on based on tasks, programs and routines. In the Logix controller, each task is assigned a priority level; higher priority tasks interrupt lower priority tasks. The continuous task has the lowest priority. Scan time of Logix processors is based on the configuration of Tasks and priorities. Overall, expect a decrease of somewhere from 50% to 80% in overall program scan time when using a Logix controller as compared to a SLC controller.
|SLC-500 Processor Scan Times|
|Processor||Typ. Scan time|
|SLC-5/01||8mS / K|
|SLC-5/02||4.8mS / K|
|SLC-5/03||1.0mS / K|
|SLC-5/04, 05||0.9mS / k|
|SLC-500 I/O Capability|
|Processor||Max. Chassis||Max I/O points|
|SLC-5/01||3 / 30 Slots||3,940|
|SLC-5/02||3 / 30 Slots||4,096|
|SLC-5/03||3 / 30 Slots||4,096|
|SLC-5/04||3 / 30 Slots||4,096|
|SLC-5/05||3 / 30 Slots||4,096|
The SLC-500 system has a maximum I/O module capacity of 30 I/O cards and 4,096 total I/O points.
In the CompactLogix 5380 controller, Compact 5000 I/O modules are installed to the right of the controller as local I/O modules. A total of 31 modules can be installed in the local system.
|Processor||Local Modules, Max||EtherNet I/P Nodes, Max|
|5370 L30||16, (8 ea side of PSU)||16|
|5370 L33||16, (8 ea side of PSU)||32|
|5370 L36||16, (8 ea side of PSU)||48|
The CompactLogix controller can also use the following I/O modules over an EtherNet I/P network:
- Chassis-based I/O – Compact 5000, 1756 I/O, 1769 Compact I/O, or 1746 SLC I/O modules
- In-cabinet I/O – 1734 POINT I/O or 1794 FLEX I/O
- On-Machine I/O – 1732E ArmorBlock I/O
Calculating an exact maximum of I/O points for the CompactLogix system depends on the controller’s maximum number of EtherNet I/P nodes, the type of I/O adapter selected, and the density of the I/O module selected.
For Example 5380 L350 controller with Point I/O modules on EtherNet I/P:
- 5380 L350 can support a maximum of 120 EtherNet I/P nodes.
- 1734-AENTR Point I/O adapter can support a maximum of 63 modules with One (1) I/P address.
Assuming 4 points per module, this would be 120 x 63 x 4 = 30,240 I/O Points !!!
The above limit is somewhat theoretical because any real application would have EtherNet I/P nodes dedicated to other devices such as HMI’s, Variable Frequency Drives, etc. It should be clear, however, that even the smallest CompactLogix controller has more I/O capacity than the largest SLC-500 system.
The SLC 500 requires a power supply module attached to the leftmost of the chassis. This power supply provides power to al modules in the chassis via the backplane. The SLC 500 does not have a common Sensor / Actuator (SA) bus and requires an additional, external power supply for I/O modules and sensors such as analog modules and field devices. This requires “Field Power” to be connected to each module individually.
The Logix5380 controller requires an external 24VDC power supply connected to the MOD power terminals to supply power to all the connected modules. Unlike the SLC, the Logix 5380 controller does not require a chassis but rather has backplane connections at the side of each module.
Also unlike the SLC, the Logix 5380 has a common Sensor/Actuator (SA) bus that distributes sensor/actuator power to all modules connected to the backplane. This simplifies the wiring, especially if all I/O devices utilize same voltage. The SA power bus can be separated with a Field Potential Distributor Module If the I/O devices use two different voltages (i.e. 24V DC, 120V AC.) This allows two separate power supplies to be connected to banks of modules through isolated Sensor/Actuator buses.
That concludes our comparison article for this week! Come back next week for another article exploring the differences between your favorite pieces of hardware.
Have a suggestion for products we should compare? Leave a comment below, or send us a message on Facebook, Twitter or LinkedIn.