Allen Bradley PLC-5 Classic Controller Complete Guide

I/O backplane transmission time (approximately 1-2ms/full rack)

Remote I/O scan time

Processor program scan time

Output module delay (typical 8.8ms)

6.2 Optimization of Remote I/O Scanning Time

Remote I/O scanning time=(number of racks) × (scanning time per rack @ baud rate)+additional overhead for block transmission

Scanning time per rack: approximately 10ms at 57.6kbps, approximately 2.5ms at 115.2kbps, and approximately 0.7ms at 230.4kbps.

Additional cost of block transmission=(word count x milliseconds per word)+fixed cost. For example, transmitting 10 words at 115.2kbps requires 10 × 0.14+2.5=3.9ms.

Optimization suggestions:

Allocate time critical I/O to separate channels (PLC-5/15 and/25 have two remote I/O channels? Actually, there is only one remote I/O port, but it can be expanded through the 1785-BCM backup module? The manual specifies that PLC-5/25 only has one remote I/O port. But it can be optimized by separating local, extended local, and remote racks

Use a configurable scan list to exclude or reduce scanning frequency for racks that do not require quick updates

Increase baud rate (requires all devices to support and cable length to meet requirements)

Place modules that do not require frequent block transfers locally or expand local racks

6.3 Estimation of Instruction Execution Time

The execution time of different types of instructions varies significantly. For example:

False condition XIC instruction: approximately 1.4 μ s

MVM instruction with true conditions (shielded transmission): approximately 258 μ s

FAL file arithmetic instruction: 98+W × (42.5+N) μ s, where W is the number of processed elements

Indirect addressing and file addressing will increase additional time (approximately 0.8 μ s/address over 256 words, as well as additional overhead for indirect file or element numbers). Using program constants (integers or floating points) is faster than using data table addresses, but modifications require editing the program.

Typical troubleshooting cases

Case 1: Processor PROC LED flashes red

Possible reasons: Invalid memory or EEPROM loading failure. Check if the EEPROM is installed correctly and if bits 13/14 of S: 1 are set correctly (it is recommended to set "EEPROM transfer at power up" to bits 13=1 and 14=1). If it still cannot be restored, try clearing the memory and downloading the program again.

Case 2: All outputs of the remote I/O rack remain in their final state

Check the switch 1 setting of the adapter module (1771-ASB). If switch 1 is turned on, the output will remain in its final state in case of communication failure; If power-off safety is required, it should be set to OFF. At the same time, check whether the fault handling program detects the fault through the global fault bit and performs a safe shutdown.

Case 3: Block transmission always times out or reports errors

Confirm that the rack and group number settings of the block transmission module match the parameters in the programming instructions

For PLC-5/15 or/25 in adapter mode, check if half slot addressing is used and located in a 16 slot rack - block transfer cannot be used at this time, and an adapter image file must be created as a replacement

Check if the terminal resistance of the remote I/O link is correct

In scanner mode, please note that each remote I/O scanning cycle can only perform one block transfer per rack. If there are multiple BT instructions sent to the same rack in the program, they will queue up

Case 4: DH+communication response is extremely slow

Check if there are offline nodes in the network - token loss may cause network reconstruction. Use programming software to view the activity node table (S: 3-s: 6 characters). If there are a large number of PLC-5 processors in the network and each one frequently sends large blocks of messages, consider moving the programming terminal to an independent DH+link or reducing the frequency of sending non essential messages (such as using timed triggering instead of continuous triggering).

System upgrade and replacement considerations

When the classic PLC-5 controller faces a shortage of spare parts or insufficient performance, the following solutions can be considered:

If only the processor needs to be replaced: same series upgrades (such as upgrading from/10 to/25) usually only require replacing the processor module, reloading the program memory, and basic compatibility of I/O configurations

If you need to keep the 1771 I/O rack: you can choose to use the ControlLogix platform with the 1771-ASB adapter, or use the 1756-DHRIO module bridge

If complete system modernization is required: migrate to ControlLogix or CompactLogix platforms, utilize PLC-5 program conversion tools, and retest I/O timing

However, regardless of the solution, the hardware configuration, addressing mode, special function module settings, and fault handling logic of the existing system should be recorded in detail before conversion to ensure seamless replacement of the new system.