Ask our team:
  • Phone: +86 181 0690 9650
  • E-Mail sales1@apterpower.com
  • Lifecycle status

    Discontinued / Obsolete by OEM
    Apter Power checks topology, revision, file allocation, project evidence, and condition before legacy sourcing coordination.

1785-L60L

/ 4.9
1001 reviews | Need a Specific Revision?
Allen-Bradley 1785-L60L combines 64 K words, a dedicated Extended-Local I/O path, and two configurable DH+ or Remote I/O channels for large mixed-topology systems.
In Stock
Ships by Wednesday, October 28
Fast Shipping Available
Get a quick price for 1785-L60L
Quantity
*E-mail
Company
*Mobile
*Content
Upload (gif, jpg, jpeg, png, bmp, doc, docx, xls, xlsx, ppt, pdf, csv)

Technical specifications for 1785-L60L

  • Manufacturer:
    Allen-Bradley
  • Part Number:
    1785-L60L
  • Product Family:
    PLC-5
  • Product Type:
    PLC-5/60L Extended-Local I/O Programmable Controller
  • Stock:
    1
  • Maximum user memory:
    64 K words
  • Maximum total I/O:
    3,072 any mix or 3,072 inputs plus 3,072 outputs complementary
  • Communication channels:
    2 DH+ or Remote I/O; 1 Extended-Local I/O; 1 serial
  • Maximum I/O rack addresses:
    24 (0…27 octal)
  • Maximum I/O chassis:
    81 total; 16 extended-local; 64 remote
  • Maximum program file:
    56 K words
  • Maximum data-table file:
    32 K words
  • Backplane current:
    3.3 A at 5 V DC
  • Power dissipation:
    17.3 W
  • Operating temperature:
    0…60 °C
  • Storage temperature:
    -40…85 °C
  • Relative humidity:
    5…95%, noncondensing
  • Chassis position:
    Left-most slot in a supported 1771 chassis
  • Weight:
    1.42 kg
  • Estimated shipping dimensions:
    4.9 x 16.5 x 27.4 cm
  • Tariff Code:
    8537101190
  • Country of origin:
    USA
  • Place of shipment:
    Xiamen,Fujian,China
By purchasing this item, you agree to the Terms & Conditions, ApterPower is not an authorized distributor for listed manufacturers or tradenames and therefore the manufacturer's warranty does not apply. All our products come with ApterPower's 1-year warranty.

More Information

Overview Manuals Mixed Chassis Plan 64 K File Layout Restart Sequencing Product Applications

Features:

  • 64 K-word application: PLC-5/60L capacity with explicit internal file ceilings
  • Local expansion: dedicated Extended-Local I/O for as many as sixteen chassis
  • Large remote estate: two configurable channels can serve up to sixty-four remote chassis
1785-L60L scales the extended-local concept to a 64 K-word controller with a larger remote-chassis allowance.

Its value appears in mixed estates: nearby I/O uses the dedicated local path, while two other channels can be partitioned for remote scanning or DH+ communication.

A controlled replacement preserves the topology split, rack addresses, file allocation, link settings, project archive, battery, and exact firmware record.
Apter Power can coordinate topology and file-limit checks for 1785-L60L before condition review and quotation.
Allen-Bradley 1785-L60L PLC-5/60L Extended-Local I/O Programmable Controller Manuals, Datasheets, Links
Important Notice: Other accessories, manuals, cables, calibration data, software, etc. are not included with this equipment unless listed in the above stock item description. All prices are shown in USD.
  • Estate split: distinguish processor, extended-local, and remote chassis in one controlled register.
  • Local ceiling: keep the dedicated expansion chain within sixteen documented chassis.
  • Remote scope: reconcile up to sixty-four remote chassis with two scan lists and octal addresses 0…27.
  • Program boundary: hold each program file within 56 K words.
  • Data boundary: preserve the separate 32 K-word ceiling for every data-table file.
  • Conversion review: inspect file growth, indirect references, and archive checksum before project transfer.
  • Local first: prove the Extended-Local I/O path and chassis power before remote link activation.
  • Channel staging: return the two network channels independently while outputs remain controlled.
  • Retention evidence: verify battery, memory module, firmware, and project identity before an extended outage.
  • Large extended-local I/O systems: operate supported nearby 1771 expansion chassis on a dedicated path.
  • Mixed local and remote control: coordinate local expansion with two Remote I/O scanner estates.
  • High-capacity PLC-5 applications: execute 64 K-word projects within the published internal file limits.
Description
Large mixed-topology 1771 systems use 1785-L60L to keep a sixteen-chassis Extended-Local I/O path distinct from two configurable DH+ or Remote I/O channels. The documented architecture reaches eighty-one total chassis without merging local and remote ownership.

Project organization remains important on 1785-L60L: the 64 K-word application space retains separate 56 K program-file and 32 K data-table-file limits. These boundaries affect migration even when the overall controller memory appears sufficient.

With 3,072 I/O in any mix and serial communication, 1785-L60L is the PLC-5/60L controller for extensive local and remote estates. Selection should preserve the L-suffix hardware, rack allocation, Series/Revision, battery state, and validated project checksum.
Revisions

Revision Part #

Also known as

1785-L60L Series B
1785-L60L/B, Series B, Revision S.2
1785-L60L Series C
1785-L60L/C, Series C, Revision U.2
1785-L60L Series D
1785-L60L/D, Series D, Revision L.2
1785-L60L Series E
1785-L60L/E, Series E, Revision K.2
Alternative Names
Allen-Bradley 1785-L60L Rockwell Automation 1785-L60L AB 1785-L60L 1785L60L 1785 L60L PLC-5/60L Extended-Local I/O Programmable Controller 1785-L60L
Technical notes
Before deploying 1785-L60L, separate the sixteen-chassis Extended-Local I/O plan from the two Remote I/O scan lists. Keep program files within 56 K words and data-table files within 32 K words, even when total memory remains. A non-L PLC-5/60 does not document the same local-expansion path.
Exceptional Service

Our Mission

  • 100% Satisfaction

    We believe expertise is priceless. With over 20 years of experience, and top engineers on staff, we can help you solve or avoid problems that threaten your business.
  • Trust Guaranteed

    Not only do we have a vast inventory, our team makes sure every piece of equipment is in working condition. Your purchases are also backed by our Warranty.
  • Expertise

    Time is money, especially when your equipment is down. We work quickly to get your equipment on its way so you can get it back up and running.

FAQS

The following is a list of questions commonly asked by our customers. Please contact us if you have a question about our process that is not answered below.
How does 1785-L60L keep Extended-Local I/O separate from its remote chassis estate?
Document the dedicated local chain independently, then assign every octal remote rack to one of two scanner channels and validate each physical link before combining operation.
Why can a 64 K project still violate a file rule on 1785-L60L?
Check each program file against 56 K words and each data-table file against 32 K words, then review indirect references before restructuring the offline project.
What should be checked before adding the sixty-fourth remote chassis to 1785-L60L?
Audit racks 0…27, both scan lists, rate-dependent cable length, device count, termination, power, scan time, and the sixteen extended-local chassis already consuming system resources.
How should a 1785-L60L outage be planned after BATT illuminates?
Verify the current project and checksum, record channel and rack settings, assess the remaining power-off window, obtain the correct battery, and test the recovery package before shutdown.
Can 1785-L60L be replaced by a standard PLC-5/60 with the same memory?
Not without redesign. Confirm the installed Extended-Local I/O chain, cable, chassis assignments, channel roles, and project configuration; stop if the proposed controller lacks the L-suffix path.
How should 1785-L60L restart be staged across local and remote chassis after an outage?
Prove the Extended-Local I/O chain first, then return the two scanner channels independently with outputs controlled. Reconcile the project checksum and rack ownership before restoring the complete estate.