Allen bradley контроллеры ошибки

Depending on the controller, the indication of I/O failure will be displayed in various ways. The I/O indicator of the controller (as shown in the example below) flashes green or red.

The following table lists common I/O failure codes and corresponding descriptions and recovery methods (if applicable). Each code is listed as a complete hexadecimal number.

Faults 16#0000 – 16#00ff

Code String Explanation and Possible Causes/Solutions
16#0001 Connection Error. A connection to a module failed.
16#0002 Resource unavailable. Either:

·   there are not enough connections available either for the controller or for the communication module being used to connect through.

Check the connection use of the controller or communication module. If all of the connections are used, try to free some of the used connections or add another module to route the errant connection through.

·   the I/O memory limits of the controller are exceeded.

Check the I/O memory available and make program or tag changes if needed.

·   the I/O module targeted does not have enough connections available.

Check the number of controllers making a connection to this I/O module and verify that the number of connections is within the limits of the I/O module.
16#0005 Connection Request Error: Bad Class The controller is attempting to make a connection to the module and has received an error. Either:

·   the configured address for the connection to the module is incorrect.

·   the module in use (that is, the physical module) is different than the module specified in the I/O configuration tree and is therefore causing the connection or service to fail.

The fault may occur even when the module passed the electronic keying test. This may result when Disable Keying or Compatible Module options were used in the module configuration instead of the Exact Match option.

Despite passing the electronic keying test, the module being connected to does not have the same features or settings as the module specified in the I/O configuration tree and does not support the connection or service being attempted.

Check the module in use and verify that it exactly matches the module specified in the I/O configuration tree of the Logix Designer application.

If you are using a 1756-DHRIO module, verify that the Channel type selected in the software (DH+ or remote I/O network) matches the module’s rotary switch settings.
16#0006 Connection Request Error: Bad Class. Either:

·   the response buffer is too small to handle the response data.

·   the module in use (that is, the physical module) is different than the module specified in the I/O configuration tree and is therefore causing the connection or service to fail.

The fault may occur even when the module passed the electronic keying test. This may result when Disable Keying or Compatible Module options were used in the module configuration instead of the Exact Match option.

Despite passing the electronic keying test, the module being connected to does not have the same features or settings as the module specified in the I/O configuration tree and does not support the connection or service being attempted.

Check the module in use and verify that it exactly matches the module specified in the I/O configuration tree of the Logix Designer application.
16#0007 Connection Request Error: Bad Class. A service request is unconnected, but should be connected.
16#0008 Service Request Error: Unsupported Service The controller is attempting to request a service from the module that is not supported by the module.
16#0009 Module Configuration Invalid: parameter error.

Tip: Additional Fault Information for this fault will be displayed as a hex code on the Connection Tab.

 The configuration for the module is invalid. The module configuration may have been changed in the Data Monitor or programmatically.

If available for the module, access the Connections tab of the Module Properties dialog box for the additional fault code. The additional fault code indicates the configuration parameter that is causing the fault. You may have to correct multiple parameters before this fault is cleared and connection is properly established.
16#000A An attribute in the Get_Attributes_List or Set_Attributes_List has a non-zero status. Either:

·   a connection is being created where the connection type is invalid.

·   an object attribute or tag value is invalid.

If an object attribute or tag is invalid, export the Logix Designer file, then re-import it. Reschedule the ControlNet network after re-importing if applicable.
16#000C Service Request Error: Invalid mode/state for service request. The controller is attempting to request a service from the module and has received an error. First, verify that the module is not faulted.

For an I/O module, this may indicate that the module has one of these conditions:

·   Limited communication, but has a Major Fault

·   A firmware update needs to be completed or is currently being completed. Refer to the Module Info tab to determine the exact cause.
16#000D Object already exists. An I/O map instance is created where the instance is already in use.
16#000E Attribute value cannot be set. A MSG instruction is configured to change an attribute value that cannot be changed.
16#000F Access permission denied for requested service. A MSG instruction has been configured to delete a map object that cannot be deleted.
16#0010 Mode or state of module does not allow object to perform requested service. The state of the device prevents a service request from being handled.
16#0011 Reply data too large. The reply to a message has a data size that is too large for the destination.

Change the destination to a tag that can handle the data size and type being returned.
16#0013 Module Configuration Rejected: Data size too small. The configuration for the module is invalid – not enough configuration data was sent. Verify that the correct module is being targeted.
16#0014 Undefined or unsupported attribute. A MSG instruction is configured to change an attribute that does not exist.
16#0015 Module Configuration Rejected: Data size too large. The configuration for the module is invalid – too much configuration data was sent. Verify that the correct module is being targeted.

Faults 16#0100 – 16#01ff

Code String Explanation and Possible Causes/Solutions
16#0100 Connection Request Error: Module in Use. ·   The connection being accessed is already in use. Either:

·   The controller is attempting to make a specific connection to a module and the module cannot support more than one of these connections.

·   The target of a connection recognizes that the owner is attempting to remake a connection that is already running.
16#0103 Service Request Error: CIP transport class not supported. Either:

·   The controller is requesting services not supported by the module.

·   The module in use (that is, the physical module) is different than the module specified in the I/O configuration tree and is therefore causing the connection or service to fail.

The fault may occur even when the module passed the electronic keying test. This may result when Disable Keying or Compatible Module options were used in the module configuration instead of the Exact Match option.

Despite passing the electronic keying test, the module being connected to does not have the same features or settings as the module specified in the I/O configuration tree and does not support the connection or service being attempted.

Check the module in use and verify that it exactly matches the module specified in the I/O configuration tree of the Logix Designer application.
16#0106 Connection Request Error: Module owned and configured by another controller. Module may accept only one connection if Unicast is used. An ownership conflict occurred for the connection. One of these conditions exists:

·   The Connection Request to this module has been rejected due to an Ownership conflict with another Owner (for example, another Controller). This may occur with modules such as output modules that only allow a single Owner to configure and control its outputs.

This fault may also occur if the module is configured as Listen Only and supports only one connection.

·   If the Owner is connected to the module using a Unicast connection over EtherNet/IP, other connections to the module fail since the Owner controls the one connection.

If the Owner is connected to the module using a Multicast connection over EtherNet/IP, Unicast connections to the module fail since the Owner controls the one connection.

Configure both the Owner and the Listen-Only connection as Multicast.
16#0107 Connection Request Error: Unknown type. A connection being accessed was not found.
16#0108 Connection Request Error: Connection type (Multicast/Unicast) not supported. The controller is requesting a connection type not supported by the module. One of these conditions exists:

·   The module in use (that is, the physical module) is different than the module specified in the I/O configuration tree and is therefore causing the connection or service to fail.

·   The fault may occur even when the module passed the electronic keying test. This may result when Disable Keying or Compatible Keying options were used in the module configuration instead of the Exact Match option.

Despite passing the electronic keying test, the module being connected to does not have the same features or settings as the module specified in the I/O configuration tree and does not support the connection or service being attempted.

Check the module in use and verify that it exactly matches the module specified in the I/O configuration tree of the Logix Designer application.

·   You may have configured a consumed tag to use a Unicast connection, but the producing controller does not support Unicast connections.
16#0109 Connection Request Error: Invalid connection size. Tip: Additional Error Information for this fault will be displayed as the tag name associated with the

connection instance number that has the fault.

 The connection size is inconsistent with that expected. Either:

·   the controller is attempting to set up a connection with the module and cannot – the size of the connection is invalid.

·   the controller may be attempting to connect to a tag in a producing controller whose size does not match the tag in this controller.

·   the module in use (that is, the physical module) is different than the module specified in the I/O configuration tree and is therefore causing the connection or service to fail.

·   the fault may occur even when the module passed the electronic keying test. This may result when Disable Keying or Compatible Keying options were used in the module configuration instead of the Exact Match option.

Despite passing the electronic keying test, the module being connected to does not have the same features or settings as the module specified in the I/O configuration tree and does not support the connection or service being attempted.

Check the module in use and verify that it exactly matches the module specified in the I/O configuration tree of the Logix Designer application.

If the module is a 1756 ControlNet module, verify that the chassis size is correct. For remote I/O adapters, verify that the rack size and/or rack density is correct.
16#0110 Connection Request Error: Module not configured. The controller is attempting to set up a Listen Only connection with the module and cannot – the module has not been configured and connected to by an Owner (for example, another Controller).

This controller is not an Owner of this module because it is attempting to establish a Listen Only connection, which requires no module configuration. It cannot connect until an Owner configures and connects to the module first.
16#0111 Requested Packet Interval (RPI) out of range. Either:

·   the Requested Packet Interval (RPI) specified is invalid for this module or for a module in the path to this module. See the Advanced tab to enable the RPI from the producer.

·   the module in use (that is, the physical module) is different than the module specified in the I/O configuration tree and is therefore causing the connection or service to fail.

The fault may occur even when the module passed the electronic keying test. This may result when Disable Keying or Compatible Module options were used in the module configuration instead of the Exact Match option.

Despite passing the electronic keying test, the module being connected to does not have the same features or settings as the module specified in the I/O configuration tree and does not support the connection or service being attempted.

Check the module in use and verify that it exactly matches the module specified in the I/O configuration tree of the Logix Designer application.

·   for Listen Only connections: the RPI set by the owner of this module is slower than the one requested. Either increase the requested RPI or decrease the RPI the owner controller is using.

See the Connection tab in the Module Properties dialog box for valid RPI values.
16#0113 Connection Request Error: Module connection limit exceeded. The number of connections is greater than what is available on the module. The number of connections must be reduced or the hardware must be upgraded.

To reduce the number of connections:

·   Change the Flex I/O communication adapter Comm Format from Input or Output configuration to Rack Optimization. When the Comm Format changes, the adapter must be removed and recreated in the I/O configuration tree.

·   If the configuration uses messaging over ControlNet, sequence the messages to reduce the number that are executing at the same time, or reduce the number of messages. Messages (MSG instructions) also use connections.
16#0114 Electronic Keying Mismatch: Electronic keying product code and/or vendor ID mismatch. The Product Code of the actual module hardware does not match the Product Code of the module created in the software.

Electronic Keying failed for this module. You may have a mismatch between the module created in the software and the actual module hardware.
16#0115 Electronic Keying Mismatch: Electronic Keying product type mismatch. The Product Type of the actual module hardware does not match the Product Type of the module created in the software.

Electronic Keying failed for this module. You may have a mismatch between the module created in the software and the actual module hardware.
16#0116 Electronic Keying Mismatch: Major and/or Minor revision invalid or incorrect. The Major and/or Minor revisions of the module do not match the Major and/or Minor revisions of the module created in the software.

Verify that you have specified the correct Major and Minor Revision if you have chosen Compatible Module or Exact Match keying.

Electronic Keying failed for this module. You may have a mismatch between the module created in the software and the actual module hardware.
16#0117 Connection Request Error: Invalid Connection Point. Tip: Additional Error Information for this fault appears as the tag name associated with the controller to

controller (C2C) that has the fault.

 The connection is to an invalid port or port that is already in use. One of these conditions exists:

·   Another controller owns this module and has connected with a Communications Formats: I/O modules different than the one chosen by this controller. Verify that the Communications Format chosen is identical to that chosen by the first owner controller of the module.

·   The module in use (that is, the physical module) is different than the module specified in the I/O configuration tree and is therefore causing the connection or service to fail.

The fault may occur even when the module passed the electronic keying test. This may result when Disable Keying or Compatible Module options were used in the module configuration instead of the Exact Match option.

Despite passing the electronic keying test, the module being connected to does not have the same features or settings as the module specified in the I/O configuration tree and does not support the connection or service being attempted.

Check the module in use and verify that it exactly matches the module specified in the I/O configuration tree of the Logix Designer application.

·   The controller may be attempting to connect to a nonexistent tag in a producing controller.
16#0118 Module Configuration Rejected: Format error. An invalid configuration format is used. One of these conditions exists:

·   The configuration class specified does not match the class supported by the module.

·   The connection instance is not recognized by the module.

·   The path specified for the connection is inconsistent.

·   The module in use (that is, the physical module) is different than the module specified in the I/O configuration tree and is therefore causing the connection or service to fail.

The fault may occur even when the module passed the electronic keying test. This may result when Disable Keying or Compatible Module options were used in the module configuration instead of the Exact Match option.

Despite passing the electronic keying test, the module being connected to does not have the same features or settings as the module specified in the I/O configuration tree and does not support the connection or service being attempted.

Check the module in use and verify that it exactly matches the module specified in the I/O configuration tree of the Logix Designer application.
16#0119 Connection Request Error: Module not owned. The controlling connection is not open.

Where a Listen Only connection is requested, the controlling connection is not open.
16#011A Connection Request Error: Out of Connection Resources The controller is attempting to set up a connection with the module and cannot – resources required are unavailable.

If the module is a 1756 ControlNet module, up to five controllers can make Rack Optimization connections to the module. Verify that this number has not been exceeded.

If the module is a 1794-ACN15, 1794-ACNR15, or 1797-ACNR15 adapter, only one controller can make a Rack Optimization connection to the module. Verify that this number has not been exceeded.

Faults 16#0200 – 16#02ff

Code String Explanation and Possible Causes/Solutions
16#0203 Connection timed out. The owner or originator recognizes that the target device is on the network or backplane, however, I/O data and messages are not being responded to. In other words, the target can be reached, but its response is not as expected. For example, this fault may be indicated where multicast Ethernet packets are not returned.

When this fault occurs, the controller usually attempts to continuously remove and remake the connection.

If you are using FLEX I/O modules, verify that you are using the correct terminal device.
16#0204 Connection Request Error: Connection request timed out. The controller is attempting to make a connection, however, the target module is not responding.

The device also appears to be missing from the backplane or network. To recover, take these actions:

·   Verify that the module has not been removed and is still functioning and receiving power.

·   Verify that the correct slot number has been specified.

·   Verify that the module is properly connected to the network.

If you are using FLEX I/O modules, verify that the correct terminal block is in use.
16#0205 Connection Request Error: Invalid parameter. Either:

·   The controller is attempting to set up a connection with the module and has received an error – a parameter is in error.

·   The module in use (that is, the physical module) is different than the module specified in the I/O configuration tree and is therefore causing the connection or service to fail.

The fault may occur even when the module passed the electronic keying test. This may result when Disable Keying or Compatible Module options were used in the module configuration instead of the Exact Match option.

Despite passing the electronic keying test, the module being connected to does not have the same features or settings as the module specified in the I/O configuration tree and does not support the connection or service being attempted.

Check the module in use and verify that it exactly matches the module specified in the I/O configuration tree of the Logix Designer application.
16#0206 Connection Request Error: Requested size too large. Either:

·   The controller is attempting to set up a connection with the module and has received an error – the request size is too large.

·   The module in use (that is, the physical module) is different than the module specified in the I/O configuration tree and is therefore causing the connection or service to fail.

The fault may occur even when the module passed the electronic keying test. This may result when Disable Keying or Compatible Module options were used in the module configuration instead of the Exact Match option.

Despite passing the electronic keying test, the module being connected to does not have the same features or settings as the module specified in the I/O configuration tree and does not support the connection or service being attempted.

Check the module in use and verify that it exactly matches the module specified in the I/O configuration tree of the Logix Designer application.

Faults 16#0301 – 16#03ff

Code String Explanation and Possible Causes/Solutions
16#0301 Connection Request Error: Out of buffer memory. One of these conditions may exist:

·   The controller is attempting to set up a connection with the module and has received an error

– a module in the path is out of memory.

·   The controller may be attempting to connect to a tag in a producing controller that is not marked as being produced.

·   The controller may be attempting to connect to a tag in a producing controller. That tag may not be configured to allow enough consumers.

·   Reduce the size or number of connections through this module.

·   One of the network modules between the module and the controller may be out of memory. Check network configuration of the system.

·   The module may be out of memory. Check system configuration and capabilities of module.

·   The module in use (that is, the physical module) is different than the module specified in the I/O configuration tree and is therefore causing the connection or service to fail.

The fault may occur even when the module passed the electronic keying test. This may result when Disable Keying or Compatible Module options were used in the module configuration instead of the Exact Match option.

Despite passing the electronic keying test, the module being connected to does not have the same features or settings as the module specified in the I/O configuration tree and does not support the connection or service being attempted.

Check the module in use and verify that it exactly matches the module specified in the I/O configuration tree of the Logix Designer application.
16#0302 Connection Request Error: Out of communication bandwidth. The controller is attempting to set up a connection with the module and has received an error – a module in the path has exceeded its communication bandwidth capacity.

Increase the Requested Packet Interval (RPI) and reconfigure your network with RSNetWorx.

Distribute the load on another bridge module.
16#0303 Connection Request Error: No bridge available. The controller is attempting to set up a connection with the module and has received an error – a module in the path has exceeded its communication bandwidth capacity.

Distribute the load on another bridge module.
16#0304 Not configured to send scheduled data. The ControlNet module is not scheduled to send data. Use RSNetWorx for ControlNet software to schedule or reschedule the ControlNet network.
16#0305 Connection Request Error: ControlNet configuration in controller does not match configuration in bridge. The ControlNet configuration in the controller does not match the configuration in the bridge module. This may occur because a ControlNet module was changed after the network was scheduled, or because a new control program has been loaded into the controller.

Use RSNetWorx for ControlNet software to reschedule the connections.
16#0306 No ControlNet Configuration Master (CCM) available. The ControlNet Configuration Master (CCM) cannot be found. The 1756-CNB and PLC-5C modules are the only modules capable of being a CCM and the CCM must be node number 1.

Verify that a 1756-CNB or PLC-5C module is at node number 1 and is functioning properly. This fault may temporarily occur when the system is powered up and will be cleared when the CCM is located.
16#0311 Connection Request Error: Invalid port. The controller is attempting to set up a connection with the module and has received an error. Verify that all modules in the I/O Configuration tree are the correct modules.
16#0312 Connection Request Error: Invalid link address. The controller is attempting to set up a connection with the module and has received an error – an invalid link address has been specified. A link address can be a slot number, a network address, or the remote I/O chassis number and starting group.

Verify that the chosen slot number for this module is not greater than the size of the rack. Verify that the ControlNet node number is not greater than the maximum node number configured for the network in RSNetWorx for ControlNet software.
16#0315 Connection Request Error: Invalid segment type. The segment type or route is invalid. Either:

·   the controller is attempting to set up a connection with the module and has received an error

– the connection request is invalid

·   the module in use (that is, the physical module) is different than the module specified in the I/O configuration tree and is therefore causing the connection or service to fail.

The fault may occur even when the module passed the electronic keying test. This may result when Disable Keying or Compatible Module options were used in the module configuration instead of the Exact Match option.

Despite passing the electronic keying test, the module being connected to does not have the same features or settings as the module specified in the I/O configuration tree and does not support the connection or service being attempted.

Check the module in use and verify that it exactly matches the module specified in the I/O configuration tree of the Logix Designer application.
16#0317 Connection Request Error: Connection not scheduled. The controller is attempting to set up a ControlNet connection with the module and has received an error.

Use RSNetWorx for ControlNet software to schedule or reschedule the connection to this module.
16#0318 Connection Request Error: Invalid link address

– cannot route to self.

 The controller is attempting to set up a connection with the module and has received an error – the link address is invalid.

Verify that the associated ControlNet module has the correct slot and/or node number selected.
16#0319 Connection Request Error: No secondary resources available in redundant chassis. The controller is attempting to set up a connection with the module and has received an error – the redundant module does not have the necessary resources to support the connection.

Reduce the size or number of connections through this module or add another controller or ControlNet module to the system.
16#031a Connection Request Error: Rack Connection Refused. The controller is attempting to set up a Direct connection with the module and has received an error. A Rack Optimized connection has already been established to this module through the 1756-CNB/R in the same chassis.

·   Connect to this module via the 1756-CNB/R in the same chassis.

·   Connect to this module via a different 1756-CNB/R in order to use a Direct connection.

·   Change the first connection from Rack Optimized to Direct, and then reestablish the second direct connection.

·   Connect to this module from a controller in the same chassis as the module (do not connect via 1756-CNB/R.
16#031e Connection Request Error: Cannot consume tag. ·   The controller is attempting to connect to a tag in a producing controller and has received an error.

·   The controller is attempting to connect to a tag in a producing controller and that tag has already been used by too many consumers. Increase the maximum number of consumers on the tag.
16#031f Connection Request Error: Cannot consume tag. No SC (servicing controller) connection object was found that corresponds to a symbol instance.
16#0322 Connection Request Error: Connection point mismatch A connection point mismatch has occurred. Either:

·   a new connection requested does not match the existing connection. Check the controllers that are using the connection and verify that all the configurations are identical.

·   the connection requested is not a listener or a controlling connection type.

Faults 16#0800 – 16#08ff

Code String Explanation and Possible Causes/Solutions
16#0800 Network link in path to module is offline. No interpretation available.
16#0801 Incompatible multi-cast RPI. No interpretation available.
16#0810 No target application data available. The controlling application has not initialized the data to be produced by the target device. This may be caused when “Send Data” connections are configured in a target device and the controlling application for that target device has not initialized the data to be produced.

For the target device associated with the “Send Data” connection reporting this connection error, start the controlling application and perform at least one write of data. Refer to the documentation for the target device and its controlling application for information on how to do this.
16#0814 Connection Request Error: Data Type Mismatch. Invalid connection status information was found.

Faults 16#fd00 – 16#08ff

Code String Explanation and Possible Causes/Solutions
16#fd03 Connection Request Error: Required Connection missing The controller is attempting to set up a connection with the module and has received an error – this module requires a particular set of connections and connection types, and one of those connection types is missing.

·   Call Technical Support
16#fd04 Connection Request Error: No CST Master Detected The controller is attempting to set up a connection with the module and has received an error – this module requires a CST master in the chassis.

·   Configure a module (typically a controller) in this chassis to be the CST master.

·   Call Technical Support
16#fd05 Connection Request Error: No Axis or Group Assigned. The controller is attempting to set up a connection with the module and has received an error – this module requires an axis or group table assigned.

·   Assign a Group or Axis.

·   Call Technical Support
16#fd06 Transition Fault The controller command to transition the SERCOS ring to a new phase returned an error from the module. Check for duplicate drive Nodes.
16#fd07 Incorrect SERCOS Data Rate An attempt to configure the SERCOS ring failed. The baud rate for all devices must be the same and supported by the drives and the SERCOS module.
16#fd08 SERCOS Comm Fault Mainly two sets of faults may cause a Comm. Fault – Physical and interface faults. A possible source of physical faults is:

·   Broken ring

·   Loose connector

·   Fiber optics not clean

·   Electrical noise due to improper drive grounding

·   Too many nodes on the ring

Interface errors are encountered when you are configuring third party drives. A possible source of interface errors is:

·   No SERCOS MST (Protocol Error)

·   Missed AT (drive did not send data when expected)

·   SERCOS timing error in phase 3

·   Error in drive data returned to SERCOS module
16#fd09 Node Initialization Fault An attempt by the controller to configure the node for cyclic operation returned an error.
16#fd0a Axis Attribute Error A bad response was received from a motion module.
16#fd0c Error Different Grandmaster Fault The end device has a different grandmaster than the controller.
16#fd1f Bad Safety Protocol Format An error occurred adding the safety network segment to a route.
16#fd20 No Safety Task No safety task appears to be running.
16#fd22 Chassis Size Mismatch Verify the number of physical expansion I/O modules configured for the controller and then update the number of modules selected from the Expansion I/O list on the General page in the Controller Properties dialog.
16#fd23 Chassis Size Exceeded To verify the number of physical expansion I/O the controller supports, open the Controller Properties dialog and expand the Expansion I/O list on the General page.

Configure the number of physical expansion I/O modules to match the selection in the Expansion I/O list.

Faults 16#fe00 – 16feff

Code String Explanation and Possible Causes/Solutions
16#fe01 An invalid configuration format was encountered.
16#fe02 Requested Packet Interval (RPI) out of range. The Requested Packet Interval (RPI) specified is invalid for this module.

·   See the Connection tab for valid RPI values.
16#fe03 The input connection point has not been set.
16#fe04 Connection Request Error: Invalid input data pointer. The controller is attempting to set up a connection with the module and has received an error.
16#fe05 Connection Request Error: Invalid input data size. Either:

·   The controller is attempting to set up a connection with the module and has received an error.

·   The module in use (that is, the physical module) is different than the module specified in the I/O configuration tree and is therefore causing the connection or service to fail.

The fault may occur even when the module passed the electronic keying test. This may result when Disable Keying or Compatible Module options were used in the module configuration instead of the Exact Match option.

Despite passing the electronic keying test, the module being connected to does not have the same features or settings as the module specified in the I/O configuration tree and does not support the connection or service being attempted.

Check the module in use and verify that it exactly matches the module specified in the I/O configuration tree of the Logix Designer application.
16#fe06 The input force point has not been set.
16#fe07 The output connection point has not been set.
16#fe08 Connection Request Error: Invalid output data pointer. The controller is attempting to set up a connection with the module and has received an error.
16#fe09 Connection Request Error: Invalid output data size. Either:

·   The controller is attempting to set up a connection with the module and has received an error.

·   The module in use (that is, the physical module) is different than the module specified in the I/O configuration tree and is therefore causing the connection or service to fail.

The fault may occur even when the module passed the electronic keying test. This may result when Disable Keying or Compatible Module options were used in the module configuration instead of the Exact Match option.

Despite passing the electronic keying test, the module being connected to does not have the same features or settings as the module specified in the I/O configuration tree and does not support the connection or service being attempted.

Check the module in use and verify that it exactly matches the module specified in the I/O configuration tree of the Logix Designer application.
16#fe0a The output force pointer has not been set.
16#fe0b Invalid symbol string. Either:

·   The tag to be consumed on this module is invalid. Verify that the tag is marked as being produced.

·   The module in use (that is, the physical module) is different than the module specified in the I/O configuration tree and is therefore causing the connection or service to fail.

The fault may occur even when the module passed the electronic keying test. This may result when Disable Keying or Compatible Module options were used in the module configuration instead of the Exact Match option.

Despite passing the electronic keying test, the module being connected to does not have the same features or settings as the module specified in the I/O configuration tree and does not support the connection or service being attempted.

Check the module in use and verify that it exactly matches the module specified in the I/O configuration tree of the Logix Designer application.
16#fe0c Invalid PLC-5 instance number. The controller is attempting to set up a connection with the PLC-5 and has received an error.

Verify that the instance number specified has been properly specified in the PLC-5.
16#fe0d Tag does not exist in peer controller. The symbol instance number was found to not be set.
16#fe0e Automatic Firmware Update in progress. The module is currently being updated.
16#fe0f Automatic Firmware Update Failed: Firmware file incompatible with the module. Firmware supervisor has attempted to update an unsupported module.
16#fe10 Automatic Firmware Update Failed: Firmware file not found. The firmware file to update the module cannot be found.
16#fe11 Automatic Firmware Update Failed: Firmware file invalid. The firmware file is corrupted.
16#fe12 Automatic Firmware Update Failed. An error has occurred while updating the module.
16#fe13 Automatic Firmware Update Failed: Detected Active Connections. An active connection could not be made to the target module.
16#fe14 Automatic Firmware Update pending: Searching NVS file for appropriate module identity. The firmware file is currently being read.
16#fe22 The target-to-originator netparams connection type is invalid.
16#fe23 The target-to-originator netparams connection does not specify whether unicast is allowed.

Faults 16#ff00 – 16#ffff

Code String Explanation and Possible Causes/Solutions
16#ff00 Connection Request Error: No connection instance. The controller is attempting to set up a connection with the module and has received an error. Verify that the physical module is the same module type (or is a compatible module) as created in the software.

If the module is a 1756-DHRIO module in a remote chassis (connected via a ControlNet network), verify that the network has been scheduled with RSNetWorx software.

Even after the network has been scheduled with RSNetWorx for ControlNet software, if you are online and if the 1756-DHRIO module is configured for DH+ network only, a #ff00 Module Fault (no connection instance) may occur. The module is properly communicating even though Faulted is displayed as its Status on the Module Properties dialog box. Disregard the error message and fault status and continue.
16#ff01 Connection Request Error: Path to module too long. The controller is attempting to set up a connection with the module and has received an error. Verify that the path to this module is a valid length.
16#ff04 The remote controller’s map instance attempted to access a connection while being in an invalid state.
16#ff08 Connection Request Error: Invalid path to module. The controller is attempting to set up a connection with the module and has received an error. Verify that the path to this module is a valid length.
16#ff0b Module Configuration Invalid: bad format. Either:

·   The configuration for the module is invalid.

·   The module in use (that is, the physical module) is different than the module specified in the I/O configuration tree and is therefore causing the connection or service to fail.

The fault may occur even when the module passed the electronic keying test. This may result when Disable Keying or Compatible Module options were used in the module configuration instead of the Exact Match option.

Despite passing the electronic keying test, the module being connected to does not have the same features or settings as the module specified in the I/O configuration tree and does not support the connection or service being attempted.

Check the module in use and verify that it exactly matches the module specified in the I/O configuration tree of the Logix Designer application.
16#ff0e Connection Request Error: No connections accepted to bridge. The controller is attempting to set up a connection with the module and has received an error.
Источник

 Allen Bradley SLC Controller Error Codes

Allen Bradley SLC Controller Error CodesMajor Faults/Errors in Allen Bradley SLC Controller can be classified as:

Non-user – a fault caused by various conditions that cease ladder program execution.  The user-fault routine is not run when this fault occurs.

Non-recoverable
– a fault caused by the user that cannot be recovered from.  The user-fault routine is run when this fault occurs.  However, the fault cannot be cleared.

Recoverable
– a fault caused by the user that can be recovered from in the user-fault routine by resetting major error halted bit (S:1/13).  The user-fault routine is run when this fault occurs.

If you are looking for the explanation of an error that does not appear in this table, it is probably an I/O error.
Refer to either method listed next to clear faults) Clearing Major Errors (via status display) Clearing
Faults (via menu selection) 

Allen Bradley SLC Controller Error Code (Hex)

Description

0001

NVRAM (non-volatile memory) error occurred.  This non-user error occurs at power up.

0002

Unexpected hardware watchdog timeout.  This non-user error occurs at power up.

0003

EEPROM memory is corrupt.  This non-user error occurs at power up or while going into REM Run mode.

0004

A memory error occurred while in the Run mode.  This non-user error occurs at run time.

0005

Reserved

0006

Reserved

0007

A failure occurred during a memory module transfer.  This non-user error occurs at power up.

0008

A fatal internal software error occurred.  This non-user error occurs at power up.

0009

A fatal internal hardware error occurred.  This non-user error occurs at power up.

0010

The processor does not meet the required revision level.  This non-user error occurs when going to run.

0011

Main program file #2 is missing.  This non-user error occurs when going to run

0012

The ladder program has a memory error.  This non-user error occurs when going to run.

0013

Either the memory module is absent or S:1/10 or S:1/11 are not set as required.  This recoverable error occurs when going to run.

0014

Internal file error.  This non-user error occurs when going to run.

0015

Configuration files error.  This non-user error occurs when going to run.

0016

Startup protection after power loss is set.  Check for a retentive data lost condition if a user-fault routine was executed with startup protection.  This recoverable error occurs when going to run.

0017

There is an NVRAM/memory module user program mismatch.  This non-recoverable error occurs at run time.

0018

The user program is incompatible with the operating system.  This non-user error occurs when going to run or at power up.

0019

A missing or duplicate label was detected.  This non-recoverable error occurs when going to run.

001F

A program integrity problem occurred during an online editing session.
This non-user error occurs at run time.

0020

A minor error bit is set at the end of the scan.  This recoverable error occurs at run time.

0021

0021   The remote power failure of an expansion I/O rack occurred.  This non-user error occurs at run time.

0022

0022   The watchdog timer expired.  This non-recoverable error occurs at run time.

0023

Invalid or non-existent STI interrupt file.  This non-recoverable error occurs at run time.

0024

Invalid STI interrupt setpoint.  This non-recoverable error occurs at run time.

0025

There are excessive JSRs in the STI subroutine.  This non-recoverable error occurs at run time.

0026

This non-recoverable, run-time error is caused by excessive stack depth/JSR calls for DII routine.

0027

There are excessive JSRs in the Fault subroutine.  This non-recoverable error occurs at run time.

0028

Invalid or non-existent startup protection fault routine file value.
This non-user error occurs at run time

0029

Indexed address reference outside of entire data file space (range of B3:0 through the last file.  This error occurs at run time; it is recoverable when using a 5/02 processor and non-recoverable when using a 5/03  or 5/04 processor.

002A

The indexed address is too large for the file.  This non-recoverable error occurs at run time.

002B

This recoverable run-time error indicates the file number does not correspond to the file type of the base address or the indirectly referenced file does not exist in the user program.

002C

Referenced indirect address element outside data file limit.  This non-recoverable error occurs at run time.

002D

This recoverable run-time error indicates the sub-element reference to an I/O slot file does not exist, or an M-file addressing error has occurred.

002E

Invalid DII input slot.  This recoverable error occurs at run time.

002F

Invalid or non-existent DII interrupt file.  This non-recoverable error occurs at run time.

0030

An attempt was made to jump to one too many nested subroutine files.  This code can also mean that a program has potentially recursive routines. This is non-recoverable and initiated by a user program instruction error.

0031

An unsupported instruction was detected.  This is non-recoverable and initiated
by a user program instruction error.

0032

An SQO/SQC instruction crossed data file boundaries.  This is recoverable and initiated by a user program instruction error. 

0033

The LFU, LFL, FFU, FFL, BSL, or BSR instruction crossed data file boundaries.
This is recoverable and initiated by a user program instruction error.

0034

A negative value for a timer accumulator or preset value was detected.
This is recoverable and initiated by a user program instruction error.

0035

An illegal instruction (TND, SVC, or REF) occurred in the interrupt file.
This is non-recoverable and initiated by a user program instruction error.

0036

An invalid value is being used for a PID instruction parameter.  This
is recoverable and initiated by a user program instruction error.

0038

A RET instruction was detected in program file 2.

xx39

Invalid string length was detected in a string file.  This is
recoverable and initiated by a user program instruction error.

xx3A

Attempting to write to protected data file xx.  (xx is the
protected data file number you are trying to write to.)

xx3B

The daughter card has an unexpected firmware revision. The daughter card firmware is not up to date with the mother board. Flash upgrade both motherboard and daughter card to
the latest version to resolve this problem.

xx3C

STI Watchdog timer time-out.  This non-recoverable error occurs at run-time.

xx3D

Jumper J4 on the motherboard is in the “Program” position and an OS upgrade cartridge is not
present. Place jumper J4 in the “Protect” position to correct this problem.

xx3E

This is a general Plastics Error (5/04P and 5/05P processors only). Refer to the processor’s hardware manual for error code definitions and corresponding corrective action.

0044

This non-recoverable run-time error indicates excessive stack depth/JSR calls for event routine.

0045

This non-recoverable run-time error indicates an invalid or non-existent event interrupt file.

xx50-xx94

I/O errors 

Source:
Rockwell Inc

Источник
  1. Обязательно представиться на русском языке кириллицей (заполнить поле «Имя»).
  2. Фиктивные имена мы не приветствуем. Ивановых и Пупкиных здесь уже достаточно.
  3. Не писать свой вопрос в первую попавшуюся тему — вместо этого создать новую тему.
  4. За поиск, предложение и обсуждение пиратского ПО и средств взлома — бан без предупреждения.
  5. Рекламу и частные объявления «куплю/продам/есть халтура» мы не размещаем ни на каких условиях.
  6. Перед тем как что-то написать — читать здесь и здесь.

Andrey_1970

Проблемы с контроллерами Allen Bradley

Сообщение

Andrey_1970 »

Уважаемые спецмалисты, может ли кто объяснить такой глюк: без видимыхх причин контроллеры Allen Bradley вырубаются (непобоюсь этого слова), слетает программа с контроллеров, причем не важно FlexLogic это или ControlLogic. Питание, через ИБП, мощность бесперебойников достоточная. Кондеционеры, батарейки в норме. Не знаю, что еще исключить, вообщем без видимых причин.

Аватара пользователя

Jackson

администратор
администратор
Сообщения: 16508
Зарегистрирован: 17 июн 2008, 16:01
Имя: Евгений свет Брониславович
Страна: Россия
город/регион: Санкт-Петербург
Благодарил (а): 624 раза
Поблагодарили: 1126 раз

Re: Проблемы с контроллерами Allen Bradley

Сообщение

Jackson »

Предполагаю электромагнитные помехи по подходящим цепям. Это относится без исключения ко всем цепям, имеющим электрическую связь с контроллером.

1) катушки реле и контакторов постоянного тока шунтированы диодами?
2) катушки реле и контакторов переменного тока шунтированы варисторами?
3) если в относительной близости стоят частотные преобразователи, стоят ли на них выходные фильтры? Отходящие кабели от частотников экранированы и заземлены?
4) Нет ли по близости мощных радиопередатчиков (базовая станция ОПСОСа, радары ближнего и дальнего привода аэропорта, низколетящие самолеты)? Может есть совсем близко и не совсем мощные: радиомодем, радиостанции внутренней связи?
5) В достаточной ли мере ИБП обеспечивает «чистое» питание и гальваническую развязку от внешнего мира? Каков уровень THD в сети до ИБП и после него? Каков уровень THD во внешних отходящих цепях?

На самом деле, наиболее вероятен п.п. 1, 2 и 3 — где-то банально щелкает контактор или автомат и прилетает помеха. У нас как то было что ЧРП без фильтров и с неэкранированным кабелем при включении выносил мозги всей автоматики по измерительным цепям (проблема решилась прокладкой экранированного кабеля с заземлением, а после и фильтры поставили).

Но встречался на практике и с п.п. 4 и 5. В аэропорту в операторской энергетика, что стояла в 100 метрах от радара ближнего привода (стены — тройной кирпич со стальными листами между слоями кирпича, заэкранировано и заземлено всё что только можно) один кабель затащили из внешнего мира почему-то неэкранированный и без развязки, хотя была это кажется банально сеть внешнего освещения операторской (будку освещали снаружи чтоб мимо двери не пройти). При первом же после монтажа этого кабеля включении радара, в операторской выжгло половину оборудования: контроллеры, компьютеры, преобразователи….

В общем, проверяйте провода.

По вопросам работы Форума можно обратиться по этим контактам.

andrmur

освоился
освоился
Сообщения: 227
Зарегистрирован: 24 июл 2008, 09:22
Имя: Мурашко Андрей Викторович
Страна: Россия
город/регион: Москва
Благодарил (а): 4 раза
Поблагодарили: 2 раза

Re: Проблемы с контроллерами Allen Bradley

Сообщение

andrmur »

Андрей,

Я передал Ваш телефон, который указан в профиле, нашему сервисному инженеру — он Вам позвонит.

Какая инженерная фирма внедряла АСУТП у вас на заводе и обращались ли Вы к ним с этим вопросом?

с наилучшими пожеланиями,
Андрей Мурашко

Andrey_1970

Re: Проблемы с контроллерами Allen Bradley

Сообщение

Andrey_1970 »

Огромное спасибо всем за ответы. Дело скорее всего действительно в счетчике контроллера. Хотя, я уточню периодичность. И по цепям надо пройтись, по физическим; а то может в проекте одно, а в шкафах другое. Вся система проектрировалась и монтировалась силами завода, во всяком случае очень многое из существующего.

И еще раз спасибо за пищу для ума!

Аватара пользователя

Jackson

администратор
администратор
Сообщения: 16508
Зарегистрирован: 17 июн 2008, 16:01
Имя: Евгений свет Брониславович
Страна: Россия
город/регион: Санкт-Петербург
Благодарил (а): 624 раза
Поблагодарили: 1126 раз

Re: Проблемы с контроллерами Allen Bradley

Сообщение

Jackson »

Дмитрий Милосердов писал(а):А сколько по времени ПЛК в работе? На гарантии? Такое ощущение, что вотчдогтаймер где-то срабатывает. Хотя если программа слетает- это м.б. с батарейкой проблемы. А в сам Роквелл пробовали обращаться?

Дима, а разве при срабатывании сторожевой собаки ПЗУ контроллера должно сбрасываться? Просто Cold Start ведь должен быть и всё, а у человека программа вся слетает. Правда если батарейка в контроллере сдохла, то и правда сбросится…

По вопросам работы Форума можно обратиться по этим контактам.

AlexV

здесь недавно
здесь недавно
Сообщения: 7
Зарегистрирован: 24 июл 2008, 10:49
Имя: Вишневский Алексей Анатольевич
Страна: Россия
город/регион: Мирный, Якутия

Аватара пользователя

Jackson

администратор
администратор
Сообщения: 16508
Зарегистрирован: 17 июн 2008, 16:01
Имя: Евгений свет Брониславович
Страна: Россия
город/регион: Санкт-Петербург
Благодарил (а): 624 раза
Поблагодарили: 1126 раз

Re: Проблемы с контроллерами Allen Bradley

Сообщение

Jackson »

Дмитрий Милосердов писал(а):

genelectric писал(а):
Но похожую гадость я только с софтПЛК, на заре автоматизации (в середине 90-х) :) ловил. В классических не встречалось ни разу на практике.

Вот и я о том же. 1 раз такое видел, в контроллере села батарейка, память сбрасывалась при cold start либо при сбросе питания. Контроллеру было 11 лет, внутри батарейка села просто. То был TSX 07 nano.

По вопросам работы Форума можно обратиться по этим контактам.

AlexV

здесь недавно
здесь недавно
Сообщения: 7
Зарегистрирован: 24 июл 2008, 10:49
Имя: Вишневский Алексей Анатольевич
Страна: Россия
город/регион: Мирный, Якутия

Re: Проблемы с контроллерами Allen Bradley

Сообщение

AlexV »

genelectric писал(а):
Н-да. Забавно. Получается, это системная ошибка конкретного железа?

Боюсь, что нет… в отдельных случаях — совместная проблема определенной партии железа совместно с промежуточной версией прошивки. Перешивка на правильную версию помогала редко…

наиболее вероятный сценарий :)

genelectric писал(а):
Но встречался на практике и с п.п. 4 и 5.

радиостанции моторолла… поговорит кто-нить поблизости — все что угодно может произойти (конечно, если в проводах проблемы есть)

У нас десятки процессоров на разных объектах, в том числе и флексы и компакты… ни одного самопроизвольного стирания программы за пять лет.

Кстати, состояние батарейки всегда индицируется, причем до того, как произойдет потеря программы (т.е. индикатор уже показывает разряженную батарею, но потеря питания на несколько минут не приводит к сбросу памяти)

Diesel

Re: Проблемы с контроллерами Allen Bradley

Сообщение

Diesel »

Добрый день!

Решил присоединиться к теме, потому что уже наболело, столько проблем с сиcтемой полностью построеной на АВ как у меня, я нигде не слышал, но вот тут хоть одна из них.
Система построена на контроллерах ControlLogix 5000, время эксплуатации 1 год, такая проблема проявлялась 3 раза, приносит очень много проблем. Большинство советов что все тут писали проверил, боьшинство никак не влияет.

С уважением
DIESEL.

AlexV

здесь недавно
здесь недавно
Сообщения: 7
Зарегистрирован: 24 июл 2008, 10:49
Имя: Вишневский Алексей Анатольевич
Страна: Россия
город/регион: Мирный, Якутия

Re: Проблемы с контроллерами Allen Bradley

Сообщение

AlexV »

Проблема со стиранием программы действительно серьезная… Недавно и мы столкнулись напрямую с этой бякой.
Самое печальное, что самый свежий отказ случился в «тепличных» условиях, на стенде… :shock:

Diesel писал(а):
Решил присоединиться к теме, потому что уже наболело, столько проблем с сиcтемой полностью построеной на АВ как у меня, я нигде не слышал, но вот тут хоть одна из них.

А перечислить весь набор ваших проблем можете?

Diesel писал(а):
Система построена на контроллерах ControlLogix 5000, время эксплуатации 1 год, такая проблема проявлялась 3 раза, приносит очень много проблем. Большинство советов что все тут писали проверил, боьшинство никак не влияет.

Какие симптомы конкретно у вас? Просто теряется программа? Процессор при этом в шасси виден или глухо зависает?
Сколько у вас процессоров? Проблема проявляется только с одним или сразу со всеми одновременно, или может с разными в разное время?
Какие типы процессоров? Со встроенной энергонезависимой памятью или с CompactFlash?

Diesel

Re: Проблемы с контроллерами Allen Bradley

Сообщение

Diesel »

Добрый день!

У нас всего 4 контроллера, т.е. 2 с резервированием. 2 абсолютно одинаковых блока (шкафа) каждый управляет отделным агрегатом, связь друг с другом через Ethernet. Происходит зависание контроллеров абсолютно не предсказуемо, никаких работ не проводиться, никаких скачков напряжения, технологически рабочий режим, все данные залипают на экранах, не понятно работает или нет система, подключиться невозможно к контроллеру, при этом резервный так же не работоспособен, программа слетает, необходимо заново загружать, выходим из ситуации при помощи перезагрузки(отключением включением питания) всего шкафа управления агрегатом, времени конечно же толком разобраться не дают,происходит это либо на одном либо на другом агрегате, т.е. не на одном и том же, перезагружать по отдельности(основной и резервный) контроллеры не помогает, контроллеры в составе с модулями ControlNEt, EtherNET, DeviceNEt.
Проверили все заземление, питание в норме, наводок нет, перебрали весь шкаф заново.

С уважением
DIESEL.

Вернуться в «Средний уровень автоматизации (управляющий)»


Перейти

  • Работа форума
  • База знаний (Knowledge Exchange)
  • ↳   Eplan Electric P8
  • ↳   Общий F.A.Q.
  • ↳   Общие вопросы
  • ↳   Новости
  • ↳   Ошибки
  • ↳   Проект
  • ↳   Изделия
  • ↳   Устройства
  • ↳   Соединения
  • ↳   Кабели
  • ↳   Клеммы
  • ↳   ПЛК
  • ↳   Компоновка 2D
  • ↳   Макросы
  • ↳   Eplan API
  • ↳   Сценарии (Только готовые решения)
  • ↳   Внешняя обработка
  • ↳   ProPanel
  • ↳   Инструкции ProPanel (Только готовые решения)
  • ↳   Прочие направления Eplan
  • ↳   FieldSys (Топология)
  • ↳   Preplanning
  • ↳   Harness proD
  • ↳   EEC One
  • ↳   Advantech
  • ↳   F.A.Q., Инструкции
  • ↳   Allen Bradley
  • ↳   Общие вопросы
  • ↳   ПЛК
  • ↳   Операторские панели
  • ↳   B&R Automation
  • ↳   F.A.Q.
  • ↳   Danfoss
  • ↳   DEIF A/S
  • ↳   Общие вопросы
  • ↳   UNI-LINE
  • ↳   MULTI-LINE
  • ↳   MULTI-LINE 300
  • ↳   Emerson
  • ↳   Общие вопросы
  • ↳   КИП и регуляторы
  • ↳   DeltaV
  • ↳   ОВЕН
  • ↳   Прософт-Системы
  • ↳   Общие вопросы
  • ↳   ПЛК REGUL
  • ↳   Schneider Electric
  • ↳   Общие вопросы
  • ↳   ПЛК
  • ↳   Панели оператора
  • ↳   SCADA
  • ↳   Электротехника
  • ↳   Приводная техника
  • ↳   SIEMENS
  • ↳   Общие вопросы
  • ↳   LOGO!
  • ↳   ПЛК SIMATIC (S7-200, S7-1200, S7-300, S7-400, S7-1500, ET200)
  • ↳   Simatic Step7
  • ↳   Simatic TIA Portal
  • ↳   Simatic PCS 7
  • ↳   Операторские панели
  • ↳   WinCC
  • ↳   Приводная техника (Sinamics, Micromaster, Masterdrive, Simoreg, Simotics)
  • ↳   SmartGen
  • ↳   Общие вопросы
  • ↳   Промышленные (береговые) контроллеры
  • ↳   Морские контроллеры и устройства
  • ↳   WEINTEK (операторские панели)
  • ↳   F.A.Q., Инструкции
  • ↳   Архив
  • ↳   Микроконтроллеры и электроника
  • ↳   Arduino
  • ↳   Raspberry
  • ↳   Другие микроконтроллеры
  • ↳   Электроника
  • Общие вопросы АСУТП
  • ↳   Общие вопросы
  • ↳   Вопросы от студентов
  • ↳   Литература
  • ↳   Новости и отчётность
  • ↳   Нормативы, ГОСТы, стандарты
  • ↳   Информационная безопасность
  • ↳   Проектирование и САПР
  • ↳   Системная интеграция
  • ↳   Разбор полетов
  • ↳   Работа
  • ↳   Заготовки для базы знаний
  • ↳   Производство и технология
  • ↳   MES — Системы автоматизации управления производством
  • ↳   Метрология, КИП и датчики
  • ↳   Исполнительные устройства, регуляторы
  • ↳   Средний уровень автоматизации (управляющий)
  • ↳   ПЛК Flexem
  • ↳   Алгоритмы
  • ↳   Операторские панели
  • ↳   Верхний уровень автоматизации (отображение)
  • ↳   GE iFix
  • ↳   Wonderware Intouch
  • ↳   MasterScada
  • ↳   SCADA+
  • ↳   Альфа платформа
  • ↳   Интерфейсы, протоколы, связь
  • ↳   Радиосвязь
  • ↳   Полезное ПО
  • ↳   Электротехника, энергетика и электропривод
  • ↳   Генераторы, электростанции и силовые агрегаты
  • ↳   Теплотехника
  • ↳   Подбор аналогов
  • F.A.Q.
  • ↳   Документация (вариант 1)
  • ↳   Документация (вариант 2)
  • ↳   Электротехника и электроэнергетика
  • ↳   F.A.Q. по программируемым логическим контроллерам (PLC)
  • ↳   Обсуждение F.A.Q. по PLC
  • ↳   F.A.Q. по выбору PLC
  • ↳   F.A.Q. по аппаратной части PLC
  • ↳   F.A.Q. по языкам программирования
  • ↳   F.A.Q. по структуре программ
  • ↳   F.A.Q. по взаимодействию PLC с HMI
  • О жизни
  • ↳   Для дома, для семьи
  • ↳   Комната смеха
  • ↳   Электродвижение

Источник

Allen-Bradley MicroLogix 1500 User Manual

  1. Manuals
  2. Brands
  3. Allen-Bradley Manuals
  4. Controller
  5. micrologix 1500
  6. User manual

  • Contents

  • Table of Contents

  • Bookmarks

Quick Links

MicroLogix™ 1500

Programmable

Controllers

(Bulletin 1764)

User Manual

AB Spares

loading

Related Manuals for Allen-Bradley MicroLogix 1500

Summary of Contents for Allen-Bradley MicroLogix 1500

  • Page 1
    MicroLogix™ 1500 Programmable Controllers (Bulletin 1764) User Manual AB Spares…
  • Page 2
    Important User Because of the variety of uses for the products described in this publication, those responsible for the application and use of this control equipment must satisfy Information themselves that all necessary steps have been taken to assure that each application and use meets all performance and safety requirements, including any applicable laws, regulations, codes and standards.
  • Page 3
    If you do not, obtain the proper training before using this product. Purpose of this Manual This manual is a reference guide for MicroLogix 1500 controllers. It describes the procedures you use to install, wire, and troubleshoot your controller. This manual: •…
  • Page 4
    Information on the MicroLogix 1500 Controllers instruction set MicroLogix 1200 and 1500 1762-RM001B-US-P Programmable Controllers Instruction Set Reference Manual Information on mounting and wiring the MicroLogix 1500 Base Units, MicroLogix 1500 Programmable 1764-IN001A-ML-P including a mounting template for easy installation Controllers Base Unit Installation Instructions A description on how to install and connect an AIC+.

  • Page 5: Preface P

    Preface Rockwell Automation Rockwell Automation offers support services worldwide, with over 75 Sales/ Support Offices, 512 authorized Distributors and 260 authorized Systems Support Integrators located throughout the United States alone, plus Rockwell Automation representatives in every major country in the world. Local Product Support Contact your local Rockwell Automation representative for: •…

  • Page 6
    Preface Publication 1762-RM001A-US-P…

  • Page 7: Table Of Contents

    Hardware Features ……..1-1 MicroLogix 1500 Component Descriptions ….1-2 Programming .

  • Page 8
    Replacement Parts MicroLogix 1500 Replacement Kits ……B-1 Lithium Battery (1747-BA) ……B-2 Replacement Terminal Blocks.

  • Page 9: Hardware Features

    Chapter Hardware Overview Hardware Features The MicroLogix 1500 programmable controller contains a power supply, input circuits, output circuits, and a processor. The controller is available in 24 I/O and 28 I/O configurations. The hardware features of the controller are: PROG…

  • Page 10: Micrologix 1500 Component Descriptions

    Hardware Overview MicroLogix 1500 A controller is composed of a standard processor (1764-LSP or enhanced 1764-LRP with RS-232 port) and one of the base units listed below. The FET Component Descriptions transistor outputs are available on the 1764-28BXB base only.

  • Page 11
    Hardware Overview Data Access Tool (Catalog Number 1764-DAT) 1764-DAT mounted on 1764-LSP processor. Memory Modules/Real-Time Clock Memory module mounted on 1764-LSP processor. The following memory modules and real-time clock modules are available: Catalog Number Function Memory Size 1764-RTC Real-Time Clock not applicable 1764-MM1 Memory Module…

  • Page 12: Programming

    RSLogix™ 500, Rev. 4.0 or later. Communication cables are not included with the software. Communication Options The MicroLogix 1500 can be connected to a personal computer. It can also be connected to the DH-485 network using an Advanced Interface Converter (catalog number 1761-NET-AIC) and to the DeviceNet™ network using a DeviceNet Interface (catalog number 1761-NET-DNI).

  • Page 13
    To use an additional bank of I/O, you must have. Product Catalog Number MicroLogix 1500 Processor 1764-LSP, Series A, Revision C or higher 1764-LSP, Series B, Revision A or higher 1764-LRP, Series B, Revision A or higher Operating System Version Firmware Revision Number (FRN) 3 or higher Programming Software RSLogix 500, Version 3.01.09 or higher, RSLinx, Version 2.10.118 or…
  • Page 14
    Adding an I/O Bank System Guidelines A maximum of one 1769 Expansion Cable can be used in a MicroLogix 1500 system, allowing for two banks of I/O modules (one connected directly to the controller, and the other connected via the cable). Each I/O bank requires its own power supply (Bank 1 uses the controller’s embedded power supply).
  • Page 15
    Hardware Overview The following illustrations show a MicroLogix 1500 with an expansion I/O bank. Vertical Orientation Expansion I/O Bank 1 1769-CRRx Expansion Cable Expansion I/O Bank 2 1769-ECL End Cap (1) The x in this catalog number can be either a 1 or a 3 representing the length of the cable: 1 = 1 foot (305 mm) and 3 = 3.28 feet (1 meter).

  • Page 16: Micrologix 1200 And

    Expansion I/O Bank 2 Expansion I/O Power Failure Expansion I/O errors represent failures of the I/O bus or the modules themselves. The error codes are listed in the MicroLogix 1200 and MicroLogix 1500 Programmable Controllers Instruction Set Reference Manual, publication 1762-RM001B-US-P.

  • Page 17: Agency Certifications

    Chapter Installing Your Controller This chapter shows you how to install your controller system. The only tools you require are a Flat or Phillips head screwdriver and drill. Topics include: • agency certifications • compliance to European Union Directives • using in hazardous locations •…

  • Page 18: Installation Considerations

    EN 61131-2 Programmable Controllers, Part 2 — Equipment Requirements and Tests. For specific information required by EN 61131-2, see the appropriate sections in this publication, as well as the following Allen-Bradley publications: • Industrial Automation Wiring and Grounding Guidelines for Noise Immunity, publication 1770-4.1 •…

  • Page 19: Safety Considerations

    Installing Your Controller Safety Considerations Safety considerations are an important element of proper system installation. Actively thinking about the safety of yourself and others, as well as the condition of your equipment, is of primary importance. We recommend reviewing the following safety considerations.

  • Page 20
    Installing Your Controller Disconnecting Main Power WARNING Explosion Hazard — Do not replace components or disconnect equipment unless power has been switched off. The main power disconnect switch should be located where operators and maintenance personnel have quick and easy access to it. In addition to disconnecting electrical power, all other sources of power (pneumatic and hydraulic) should be de-energized before working on a machine or process controlled by a controller.

  • Page 21: Power Considerations

    If the power source cannot supply this inrush current, the source voltage may sag momentarily. The only effect of limited inrush current and voltage sag on the MicroLogix 1500 is that the power supply capacitors charge more slowly. However, the effect of a voltage sag on other equipment should be considered.

  • Page 22: Preventing Excessive Heat

    Installing Your Controller Loss of Power Source The power supply is designed to withstand brief power losses without affecting the operation of the system. The time the system is operational during power loss is called “program scan hold-up time after loss of power.” The duration of the power supply hold-up time depends on the type and state of the I/O, but is typically between 10 milliseconds and 3 seconds.

  • Page 23: Master Control Relay

    Installing Your Controller Master Control Relay A hard-wired master control relay (MCR) provides a reliable means for emergency machine shutdown. Since the master control relay allows the placement of several emergency-stop switches in different locations, its installation is important from a safety standpoint.

  • Page 24
    Installing Your Controller Using Emergency-Stop Switches When using emergency-stop switches, adhere to the following points: • Do not program emergency-stop switches in the controller program. Any emergency-stop switch should turn off all machine power by turning off the master control relay. •…
  • Page 25
    Installing Your Controller Schematic (Using IEC Symbols) 230V ac Disconnect Fuse 230V ac Circuits Isolation Operation of either ofthese contacts will Transformer remove power from the external I/O circuits, stopping machine motion. 115V ac or 230V ac Emergency-Stop Master Control Relay (MCR) Start Stop Push Button…
  • Page 26
    2-10 Installing Your Controller Schematic (Using ANSI/CSA Symbols) 230V ac Disconnect Fuse 230V ac Output Circuits Isolation Operation of either ofthese contacts will Transformer remove power from the external I/O 115V ac or 230V ac Emergency-Stop Master Control Relay (MCR) Push Button Start Stop…

  • Page 27: Base Unit Mounting Dimensions

    Installing Your Controller 2-11 Base Unit Mounting Dimensions 1764-24AWA 1764-24BWA 1764-28BXB Dimension Height (A) DIN latch open: 138 mm (5.43 in.), DIN latch closed: 118 mm (4.65 in.) Width (B) 168 mm (6.62 in.) Depth (C) 87 mm (3.43 in.) (1) See Controller Dimensions on page A-7 for more dimensional information.

  • Page 28: Mounting The Controller

    2-12 Installing Your Controller Mounting the Controller Do not remove protective debris strips until after the base and all ATTENTION other equipment in the panel near the base is mounted and wiring is complete. The debris strips are there to prevent drill fragments, wire strands and other dirt from getting into the controller.

  • Page 29
    DIN rail meets the recommended spacing requirements, see Controller Spacing on page 2-11. Refer to the mounting template from the inside back cover of the MicroLogix 1500 Programmable Controller Base Units Installation Instructions, publication 1764-5.1. 2. Hook the top slot over the DIN rail.
  • Page 30
    2-14 Installing Your Controller To remove your base unit from the DIN rail: 1. Place a flat-blade screwdriver in the DIN rail latch at the bottom of the base unit. 2. Holding the base unit, pry downward on the latch until the latch locks in the open position.

  • Page 31: Installing Controller Components

    Installing Your Controller 2-15 Installing Controller Prevent Electrostatic Discharge Components Electrostatic discharge can damage integrated circuits or ATTENTION semiconductors if you touch bus connector pins. Follow these guidelines when you handle any module: • Touch a grounded object to discharge static potential. •…

  • Page 32
    2-16 Installing Your Controller 4. Make sure the actuator is pushed closed. 5. To remove the processor from the base unit, make sure base unit power is off. Push the actuator to the open position until the processor is ejected slightly. Once the processor has been ejected, it can be removed from the base unit.
  • Page 33
    Installing Your Controller 2-17 Data Access Tool (DAT) 1. Remove cover from processor. 2. Holding the DAT in the proper orientation (as shown), place the DAT onto processor. Align DAT port on the processor with the plug on the DAT. 3.
  • Page 34
    2-18 Installing Your Controller Memory Module/Real-Time Clock 1. Remove the cover (or DAT if installed) from the processor as shown below. Electrostatic discharge can damage semiconductor devices ATTENTION inside the base and processor units. Do not touch the connector pins or other sensitive areas. 2.
  • Page 35
    Installing Your Controller 2-19 Compact I/O Attach and Lock Module (Module-to-Controller or Module-to-Module) A Compact I/O module can be attached to the controller or an adjacent I/O module before or after mounting to the panel or DIN rail. The module can be detached and replaced while the system is mounted to a panel or DIN rail.
  • Page 36
    To attach and lock modules: Remove ESD barrier when attaching I/O modules to a NOTE MicroLogix 1500 base unit. 1. Disconnect power. 2. Check that the bus lever of the module to be installed is in the unlocked (fully right) position.

  • Page 37: Wiring Requirements

    Chapter Wiring Your Controller This chapter describes how to wire your controller. Topics include: • wiring requirements • using surge suppressors • grounding guidelines • sinking and sourcing circuits • wiring diagrams, input voltage ranges, and output voltage ranges • minimizing noise Wiring Requirements Wire Type Wiring Torque…

  • Page 38
    Wiring Your Controller Calculate the maximum possible current in each power and ATTENTION common wire. Observe all electrical codes dictating the maximum current allowable for each wire size. Current above the maximum ratings may cause wiring to overheat, which can cause damage.

  • Page 39: Using Surge Suppressors

    The diameter of the terminal screw head is 5.5 mm (0.220 in.). The input and output terminals of the MicroLogix 1500 base unit are designed for a 6.35mm (0.25 in.) wide spade (standard for #6 screw for up to 14 AWG) or a 4 mm (metric #4) fork terminal.

  • Page 40
    24V dc common Suitable surge suppression methods for inductive ac load devices include a varistor, an RC network, or an Allen-Bradley surge suppressor, all shown below. These components must be appropriately rated to suppress the switching transient characteristic of the particular inductive device. See the table on page 3-5 for recommended suppressors.
  • Page 41
    Surge Suppression for Inductive dc Load Devices Output Device Diode (A surge suppressor can also be used.) Recommended Surge Suppressors Use the Allen-Bradley surge suppressors shown in the following table for use with relays, contactors, and starters. Suppressor Device Coil Voltage Catalog Number…

  • Page 42: Grounding The Controller

    Wiring Your Controller Grounding the Controller In solid-state control systems, grounding and wire routing helps limit the effects of noise due to electromagnetic interference (EMI). Run the ground connection from the ground screw of the base unit to the electrical panel’s ground bus prior to connecting any devices.

  • Page 43: Wiring Diagrams

    Wiring Your Controller Wiring Diagrams This section shows the wiring diagrams for the MicroLogix 1500 controllers. Controllers with dc inputs can be wired as either sinking or sourcing configuration. (Sinking and sourcing does not apply to ac inputs.) See pages 3-11 through 3-14 for sinking and sourcing wiring diagrams.

  • Page 44
    Wiring Your Controller Terminal Block Layouts The base unit terminal block layouts are shown below. The shading on the labels indicates how the terminals are grouped. A detail of the groupings is shown in the table following the terminal block layouts. Group 0 Group 1 Group 2…
  • Page 45
    Wiring Your Controller Terminal Groupings Controller Inputs Input Group Common Terminal Input Terminal 1764-24BWA Group 0 DC COM 0 I/0 through I/3 Group 1 DC COM 1 I/4 through I/7 Group 2 DC COM 2 I/8 through I/11 1764-24AWA Group 0 AC COM 0 I/0 through I/3 Group 1…

  • Page 46: Sinking And Sourcing Circuits

    3-10 Wiring Your Controller Sinking and Sourcing Any of the MicroLogix 1500 DC embedded input groups can be configured as sinking or sourcing depending on how the DC COM is wired on the group. See Circuits pages 3-11 through 3-14 for sinking and sourcing wiring diagrams.

  • Page 47
    Wiring Your Controller 3-11 1764-24BWA Sinking Wiring Diagram Input Terminals +24V IN 3 IN 4 IN 6 IN 9 POWER IN 1 IN 11 COM 2 COM 0 COM IN 0 IN 2 IN 5 IN 7 IN 8 IN 10 COM 1 Output Terminals (Lo)
  • Page 48
    3-12 Wiring Your Controller 1764-24BWA Sourcing Wiring Diagram Input Terminals +24V IN 3 IN 4 IN 6 IN 9 POWER IN 1 IN 11 COM 0 COM 2 COM IN 0 IN 2 IN 5 IN 7 IN 8 IN 10 COM 1 +DC -DC Output Terminals…
  • Page 49
    Wiring Your Controller 3-13 1764-28BXB Sinking Wiring Diagram Input Terminals IN 1 IN 3 IN 4 IN 6 IN 9 IN 11 IN 13 IN 15 USED COM 0 COM 2 IN 0 IN 2 IN 7 IN 8 IN 14 IN 5 IN 10 IN 12…
  • Page 50
    3-14 Wiring Your Controller 1764-28BXB Sourcing Wiring Diagram Input Terminals IN 1 IN 3 IN 4 IN 6 IN 9 IN 11 IN 13 IN 15 USED COM 0 COM 2 IN 0 IN 2 IN 7 IN 8 IN 14 IN 5 IN 10 IN 12…

  • Page 51: Controller I/O Wiring

    To help reduce the effects of environmental noise, install the MicroLogix 1500 system in a properly rated (i.e. NEMA) enclosure. Make sure that the MicroLogix 1500 system is properly grounded.

  • Page 52
    3-16 Wiring Your Controller Publication 1764-UM001A-US-P…

  • Page 53: Default Communication Configuration

    • Communications Toggle Push Button • Connecting to the RS-232 Port • Connecting to a DH-485 Network • Connecting to DeviceNet Default Communication The MicroLogix 1500 has the following default communication configuration. Configuration Table 4.1 DF1 Full-Duplex Configuration Parameters Parameter Default Baud Rate 19.2K…

  • Page 54
    Communication Connections Communications Toggle The Communications Toggle Push Button is located on the processor. You must remove processor door or DAT to access the Communications Toggle Push Button. Push Button Use the Communications Toggle Push Button to change from the user-defined communication configuration to the default communications configuration and back.
  • Page 55
    Connecting to the Making a DF1 Full-Duplex Point-to-Point Connection RS-232 Port You can connect the MicroLogix 1500 programmable controller to your personal computer using a serial cable from your personal computer’s serial port to the controller, as shown in the illustrations below.
  • Page 56
    Communication Connections Using a Modem You can use modems to connect a personal computer to one MicroLogix 1500 controller (using DF1 Full-Duplex protocol), or to multiple controllers (using DF1 Half-Duplex protocol), or Modbus Slave RTU protocol, as shown in the following illustration.
  • Page 57
    Communication Connections Constructing Your Own Modem Cable If you construct your own modem cable, the maximum cable length is 15.24 m (50 ft) with a 25-pin or 9-pin connector. Refer to the following typical pinout for constructing a straight-through cable: AIC+ Optical Isolator Modem or 1764-LRP Channel 1…
  • Page 58
    Communication Connections Connecting to a DF1 Half-Duplex Network Use this diagram for DF1 Half-Duplex Master-Slave protocol without hardware handshaking. MicroLogix 1500 (DF1 Slave) SLC 5/03 (DF1 Master) 1761-CBL-AM00 or 1761-CBL-HM02 1761-CBL-AP00 or 1761-CBL-PM02 AIC+ AIC+ straight 9-25 straight 9-25 pin cable…
  • Page 59
    Communication Connections Connecting to a DH-485 The following illustration shows how to connect to a DH-485 network. Network MicroLogix 1500 connection from port 1 or port 2 to MicroLogix Channel 1 Personal Computer 1761-CBL-AP00 or 1761-CBL-PM02 1747-CP3 AIC+ or 1761-CBL-AC00…
  • Page 60
    Communication Connections DH-485 Communication Cable The communication cable consists of a number of cable segments daisy-chained together. The total length of the cable segments cannot exceed 1219 m (4000 ft). However, two segments can be used to extend the DH-485 network to 2438m (8000 ft).
  • Page 61
    Communication Connections Multiple Cable Connection When connecting multiple cables to the DH-485 connector, use the following diagram. to Previous Device to Next Device Table 4.3 Connections using Belden #3106A Cable For this Wire/Pair Connect this Wire To this Terminal Shield/Drain Non-jacketed Terminal 2 — Shield Blue…
  • Page 62
    4-10 Communication Connections Connecting the AIC+ The AIC+, catalog number 1761-NET-AIC, enables a MicroLogix controllers to connect to a DH-485 network. The AIC+ has two isolated RS-232 ports and one RS-485 port. When two MicroLogix controllers are closely positioned, you can connect a controller to each of the RS-232 ports on the AIC+.
  • Page 63
    Communication Connections 4-11 1761-CBL-HM02 1761-CBL-AM00 Cable Length Connections from to AIC+ External Power Power Selection Supply Required Switch Setting 45cm (17.7 in) MicroLogix 1000 or 1500 port 2 cable 1761-CBL-AM00 2m (6.5 ft) to port 2 on another AIC+ port 2 external 1761-CBL-HM02 (1) External power supply required unless the AIC+ is powered by the device connected to port 2, then the selection switch should be set to cable .
  • Page 64
    4-12 Communication Connections 1761-CBL-PM02 Series C (or equivalent) Cable Wiring Diagram 1761-CBL-PM02 Series C or later Cable 8-pin Mini Din 9-pin D-shell 6 8 7 Programming Controller Device 9-Pin D-Shell 8-Pin Mini Din Publication 1764-UM001A-US-P…
  • Page 65
    Communication Connections 4-13 Recommended User-Supplied Components These components can be purchased from your local electronics supplier. Table 4.5 User Supplied Components Component Recommended Model external power supply and chassis power supply rated for 20.4-28.8V dc ground NULL modem adapter standard AT straight 9-25 pin RS-232 cable see table below for port information if making own cables…
  • Page 66
    Installing and Attaching the AIC+ 1. Take care when installing the AIC+ in an enclosure so that the cable connecting the MicroLogix 1500 controller to the AIC+ does not interfere with the enclosure door. 2. Carefully plug the terminal block into the RS-485 port on the AIC+ you are putting on the network.
  • Page 67
    Power Options Below are two options for powering the AIC+: • Use the 24V dc user power supply built into the MicroLogix 1500 controller. The AIC+ is powered through a hard-wired connection using a communication cable (1761-CBL-HM02, or equivalent) connected to port 2.

  • Page 68: Connecting To Devicenet

    4-16 Communication Connections Connecting to You can connect a MicroLogix 1500 to a DeviceNet network using the DeviceNet Interface (DNI), catalog number 1761-NET-DNI. For additional information on DeviceNet using the DNI, refer to the DeviceNet Interface User Manual, publication 1761-6.5.

  • Page 69: Chapter 5 Trim Pot Operation

    Chapter Using Trim Pots and the Data Access Tool (DAT) Trim Pot Operation The processor has two trimming potentiometers (trim pots) which allow modification of data within the controller. Adjustments to the trim pots change the value in the corresponding Trim Pot Information (TPI) register. The data value of each trim pot can be used throughout the control program as timer, counter, or analog presets depending upon the requirements of the application.

  • Page 70
    Using Trim Pots and the Data Access Tool (DAT) Trim Pot Information Function File The composition of the Trim Pot Information (TPI) Function File is described in the MicroLogix 1200 and MicroLogix 1500 Instruction Set Reference Manual, publication 1762-RM001B-US-P. Error Conditions…

  • Page 71: Data Access Tool (Dat)

    Using Trim Pots and the Data Access Tool (DAT) Data Access Tool (DAT) The DAT is a convenient and simple tool that provides an interface for editing and monitoring data. The DAT has five primary features: • Direct access to 48 bit elements •…

  • Page 72
    DAT configuration is stored in the processor in a specialized configuration file called the DAT Function File. The DAT Function File, which is part of the user’s control program, is described in the MicroLogix 1200 and MicroLogix 1500 Instruction Set Reference Manual, publication 1762-RM001B-US-P.
  • Page 73
    Using Trim Pots and the Data Access Tool (DAT) Power Save Timeout (PST) Parameter The power save timeout turns off the DAT display after keypad activity has stopped for a user-defined period of time. The power-save (DAT:0.PST) value is set in the DAT Function File.
  • Page 74
    Using Trim Pots and the Data Access Tool (DAT) PROTECTED ENTER Entering Bit Mode Bit mode allows you to view and modify up to 48 contiguous bit locations in the controller. The DAT enters the bit mode automatically following a successful power-up.
  • Page 75
    Using Trim Pots and the Data Access Tool (DAT) If the data is protected or undefined, pressing the up/down key NOTE scrolls to the next element in the list. 5. Press ENTER to load the new data. Press ESC or INT/BIT to discard the new data.
  • Page 76
    Using Trim Pots and the Data Access Tool (DAT) 1200 and MicroLogix 1500 Programmable Controllers Instruction Set Reference Manual, publication 1762-RM001B-US-P, for information on the SVC instruction. Non-Existent Elements When the DAT determines that an element number does not exist in the controller, the element value displays as three dashes.
  • Page 77
    Using Trim Pots and the Data Access Tool (DAT) Error Conditions When the DAT detects an error in its own operation, it displays the error screen. The error screen consists of “Err” and a two-digit error code, as shown below. PROTECTED ENTER The DAT can experience two different types of errors, internal errors and…
  • Page 78
    5-10 Using Trim Pots and the Data Access Tool (DAT) Publication 1764-UM001A-US-P…

  • Page 79: Real-Time Clock Operation

    If a module is installed while the MicroLogix 1500 is in an executing mode (Run or Remote Run), the module is not recognized until either a power cycle occurs, or until the controller is placed in a non-executing mode (program mode or fault condition).

  • Page 80
    Using Real-Time Clock and Memory Modules Writing Data to the Real-Time Clock When valid data is sent to the real-time clock from the programming device, the new values take effect immediately. The real-time clock does not allow you to write invalid date or time data. RTC Battery Operation The real-time clock has an internal battery that is not replaceable.

  • Page 81: Memory Module Operation

    (run or remote run) mode. To enable this feature, set the S:2/9 bit in the system status file. Refer to the MicroLogix 1200 and MicroLogix 1500 Instruction Set Reference Manual for more information.

  • Page 82
    If a memory module is installed while the MicroLogix 1500 is executing, the memory module will not be recognized until either a power cycle occurs, or until the controller is placed in a non-executing mode (program mode or fault condition).

  • Page 83: Controller Specifications

    Appendix Specifications Controller Table A.1 General Specifications Specifications Description 1764-24BWA 1764-24AWA 1764-28BXB Number of I/O 12 inputs 12 inputs 16 inputs 12 outputs 12 outputs 12 outputs Line Power 85 to 265V ac 85 to 265V ac 20.4 to 30V dc at 47 to 63 Hz at 47 to 63 Hz Power Supply Usage…

  • Page 84
    Specifications Choosing a Power Supply This section contains information for selecting a power supply for applications using a 1764-28BXB base unit. Use the tables in Appendix F to calculate the total power (Watts) consumed by the system. With that information, use the graphs below to chose a power supply.
  • Page 85
    Specifications Table A.2 Input Specifications Description 1764-24AWA 1764-24BWA and 1764-28BXB Inputs 0 thru 7 Inputs 8 and Higher On-State Voltage 79 to 132V ac 14 to 30.0V dc at 30°C 10 to 30.0V dc at 30°C Range (86°F) (86°F) 14 to 26.4V dc at 55°C 10 to 26.4V dc at 55°C (131°F) (131°F)
  • Page 86
    Specifications Table A.4 Response Times for Normal dc Inputs 8 Through 11 (1764-24BWA) and 8 Through 15 (1764-28BXB) Maximum Frequency Filter Minimum Maximum Minimum Maximum at 50% Duty Cycle Setting ON Delay ON Delay OFF Delay OFF Delay (kHz) (ms) (ms) (ms) (ms)
  • Page 87
    Specifications Table A.7 1764-28BXB FET Output Specifications Specification General Operation High Speed Operation (Outputs 2 thru 7) (Outputs 2 and 3 Only) Surge Current per peak current 4.0A Not Applicable Point maximum surge duration 10 msec Not Applicable maximum rate of once every second Not Applicable repetition at 30°C (86°F)
  • Page 88
    Specifications Table A.9 Working Voltage (1764-24BWA) Specification 1764-24BWA Power Supply Input to Backplane Verified by one of the following dielectric tests: 1836V Isolation ac for 1 second or 2596V dc for 1 second 265V Working Voltage (IEC Class 2 reinforced insulation) Power Supply User 24V Output to Verified by one of the following dielectric tests: 600V ac Backplane Isolation…
  • Page 89
    168 mm 35 mm (6.62 in.) (1.37 in.) Expansion Base Unit DIN rail center line. 132 mm 122 mm (5.19 in.) (4.813 in.) 147 mm 38 mm (5.78 in.) (1.49 in.) AB Spares…

  • Page 90: Compact I/O Dimensions

    Specifications Compact I/O Dimensions Panel Mounting For more than 2 modules: (number of modules — 1) X 35 mm (1.38 in.) 28.5 Refer to host controller for this dimension. (1.38) (1.12) NOTE: All dimensions (5.197) are in mm (inches). Hole spacing 122.6±0.2 tolerance: ±0.4 mm (4.826±0.008)

  • Page 91: Micrologix 1500 Replacement Kits

    • a table of MicroLogix 1500 replacement parts • procedure for replacing the lithium battery • illustrations of the MicroLogix 1500 replacement doors and terminal blocks MicroLogix 1500 The table below provides a list of replacement parts and their catalog number.

  • Page 92: Lithium Battery (1747-Ba

    Replacement Parts Lithium Battery When the processor’s Battery Low indicator is lit, install a IMPORTANT (1747-BA) replacement battery immediately. After the indicator turns on, the battery lasts for at least: • 14 days for the 1764-LSP • 7 days for the 1764-LRP Installing Follow the procedure below to ensure proper replacement battery installation.

  • Page 93
    Replacement Parts Battery Handling Follow the procedure below to ensure proper battery operation and reduce personnel hazards. • Use only for the intended operation. • Do not ship or dispose of cells except according to recommended procedures. • Do not ship on passenger aircraft. •…

  • Page 94: Replacement Terminal Blocks

    San Diego, CA 92173 Port Washington, NY 11050 (619) 661-4801 (516) 621-4980 Replacement Terminal This figure illustrates how to replace the MicroLogix 1500 terminal blocks. Blocks Catalog Numbers: • 1764-RPL-TB1: 17-point terminal block • 1764-RPL-TB2: 21-point terminal block Publication 1764-UM001A-US-P…

  • Page 95: Replacement Doors

    Replacement Parts Replacement Doors The following figures illustrate the procedure for installing the MicroLogix 1500 replacement doors. Base Terminal Door (1764-RPL-TDR1) Processor Access Door (1764-RPL-CDR1) Base Comms Door (included in 1764-RPL-DR) Trim Pots/Mode Switch Cover Door (included in 1764-RPL-DR) AB Spares…

  • Page 96
    Replacement Parts Publication 1764-UM001A-US-P…

  • Page 97: Understanding Controller Leds

    Appendix Troubleshooting Your System This chapter describes how to troubleshoot your controller. Topics include: • understanding the controller LED status • controller error recovery model • identifying controller faults • calling Rockwell Automation for assistance Understanding The controller status LEDs provide a mechanism to determine the current status of the controller if a programming device is not present or available.

  • Page 98
    Troubleshooting Your System When Operating Normally The POWER and RUN LEDs are on. If a force condition is active, the FORCE LED turns on and remains on until all forces are removed. When an Error Exists If an error exists within the controller, the controller LEDs operate as described in the following tables.

  • Page 99: Controller Error Recovery Model

    Troubleshooting Your System Controller Error Use the following error recovery model to help you diagnose software and hardware problems in the micro controller. The model provides common questions you Recovery Model might ask to help troubleshoot your system. Refer to the recommended pages within the model for further help.

  • Page 100: Identifying Controller Faults

    S:1/13. The controller then continues in the Run or test mode. The subroutine does not execute for non-user faults. Refer to the MicroLogix 1200 and MicroLogix 1500 Instruction Set Reference Manual for information on creating a user fault subroutine. Fault Messages…

  • Page 101: Calling Rockwell Automation For Assistance

    Troubleshooting Your System Calling Rockwell If you need to contact Rockwell Automation or local distributor for assistance, it is helpful to obtain the following (prior to calling): Automation for • controller type, series letter, and revision letter of the base unit Assistance •…

  • Page 102
    Troubleshooting Your System Publication 1764-UM001A-US-P…

  • Page 103: Appendix D Preparing For Upgrade

    Appendix Upgrading Your Operating System The operating system (OS) can be upgraded through the communication port on the controller. In order to download a new operating system, you must have the following: • ControlFlash™ Upgrade Kit containing the new OS •…

  • Page 104: Performing The Upgrade

    Upgrading Your Operating System Performing the Upgrade The following steps occur during the upgrade process. 1. Controller mode and communications parameters are checked. 2. Download begins. 3. During the download, the Force, Battery, and Comms LEDs perform a walking bit pattern. 4.

  • Page 105: Communication Interface

    See Communication Connections on page 4-1 for information about required network devices and accessories. RS-232 Communication The communications port on the MicroLogix 1500 utilizes an RS-232 interface. RS-232 is an Electronics Industries Association (EIA) standard that specifies the Interface electrical characteristics for serial binary communication. It provides you with a variety of system configuration possibilities.

  • Page 106
    Connecting to a PC to Channel 0 We recommend using an Advanced Interface Converter (AIC+), catalog number 1761-NET-AIC, as your optical isolator, as shown below. See page 4-10 for specific AIC+ cabling information. MicroLogix 1500 with 1764-LSP or 1764-LRP processor 1761-CBL-AM00 or 1761-CBL-HM02…
  • Page 107
    Understanding Communication Protocols Connecting a PC to Channel 1 MicroLogix 1500 Controller Personal Computer with 1764-LRP processor 1747-CP3 Connecting a Modem to Channel 0 We recommend using an AIC+, catalog number 1761-NET-AIC, as your optical isolator. Personal Computer Modem Cable (straight-through) MicroLogix1500 Controller with…

  • Page 108: Df1 Half-Duplex Protocol

    (including the master) on the DF1 Half-Duplex link. The MicroLogix 1500 can only act as a slave device. A device that can act as a master is required to “run” the network. Several Allen-Bradley products support DF1 Half-Duplex master protocol.

  • Page 109
    Understanding Communication Protocols When a communication port is configured for DF1 Half-Duplex Slave, available parameters include: Table E.2 DF1 Half-Duplex Configuration Parameters Parameter Options Baud Rate 300, 600, 1200, 2400, 4800, 9600, 19.2K, 38.4K Parity none, even Source ID (Node Address) 0 to 254 decimal Control Line no handshaking, handshaking…
  • Page 110
    Link When communication is between either your programming software and a MicroLogix Programmable Controller or between two MicroLogix 1500 Programmable Controllers via slave-to-slave communication on a larger multi-drop link, the devices depend on a DF1 Half-Duplex Master to give each of them access in a timely manner.

  • Page 111: Using Modems With Micrologix 1500 Programmable Controllers

    Understanding Communication Protocols Using Modems with The types of modems that you can use with MicroLogix 1500 controllers include dial-up phone modems, leased-line modems, radio modems and line drivers. MicroLogix 1500 Programmable For point-to-point Full-Duplex modem connections that do not require any…

  • Page 112: Communication Protocol

    (up to several miles). Line drivers are available in Full- and Half-Duplex models. Allen-Bradley’s AIC+ Advanced Interface Converter is a Half-Duplex line driver that converts an RS-232 electrical signal into an RS-485 electrical signal, increasing the signal transmission distance from 50 to 4000 feet (8000 feet when bridged).

  • Page 113
    Understanding Communication Protocols DH-485 Token Rotation A node holding the token can send a message onto the network. Each node is allowed a fixed number of transmissions (based on the Token Hold Factor) each time it receives the token. After a node sends a message, it passes the token to the next device.
  • Page 114
    E-10 Understanding Communication Protocols Devices that Use the DH-485 Network In addition to the MicroLogix 1500 controllers, the devices shown in the following table also support the DH-485 network. Table E.4 Allen-Bradley Devices that Support DH-485 Communication Catalog Number Description…
  • Page 115
    Understanding Communication Protocols E-11 Important DH-485 Network Planning Considerations Carefully plan your network configuration before installing any hardware. Listed below are some of the factors that can affect system performance: • amount of electrical noise, temperature, and humidity in the network environment •…
  • Page 116
    E-12 Understanding Communication Protocols Planning Cable Routes Follow these guidelines to help protect the communication cable from electrical interference: • Keep the communication cable at least 1.52m (5 ft) from any electric motors, transformers, rectifiers, generators, arc welders, induction furnaces, or sources of microwave radiation.
  • Page 117
    The best network performance occurs at the highest baud rate, which is 19200. This is the default baud rate for a MicroLogix 1500 device on the DH-485 network. All devices must be at the same baud rate. This rate is stored in the controller Communications Status file (CS0:5/8 to CS0:5/15).
  • Page 118
    (AIC+, catalog number 1761-NET-AIC). For more information on the AIC+, see the Advanced Interface Converter and DeviceNet Interface Installation Instructions, Publication 1761-5.11. DH-485 Network with a MicroLogix 1500 Controller MicroLogix 1500 connection from port 1 or port 2 to MicroLogix Channel 1…
  • Page 119
    Understanding Communication Protocols E-15 Typical 3-Node Network (Channel 0 Connection) PanelView 550 PanelView RJ45 port 1761-CBL-AS09 or 1761-CBL-AS03 TERM MicroLogix 1500 with SHLD CHS GND 1764-LSP or 1764-LRP DC SOURCE CABLE Processor EXTERNAL 1747-CP3 or 1761-CBL-AC00 1761-CBL-AM00 or 1761-CBL-HM02 Typical 3-Node Network (Channel 1 Connection)
  • Page 120
    SLC 5/04 processor bridge connection. When using this method (as shown in the following illustration): • PLC-5 devices can send read and write commands to MicroLogix 1500 controllers. • MicroLogix 1500 controllers can respond to MSG instructions received.

  • Page 121: Modbus Rtu Slave Communication Protocol (Micrologix 1764-Lsp And 1764-Lrp Series B Processors Only

    Read/Write System Status File space Status (S) words 0 to 65 For more information on the MicroLogix 1500 configuration parameters for Modbus Slave RTU (Remote Terminal Unit transmission mode) protocol, refer to the MicroLogix 1200 and 1500 Programmable Controllers Instruction Set Reference Manual, publication 1762-RM001A-US-P.

  • Page 122: Ascii Protocol

    You can use ASCII protocol by configuring the RS-232 port, channel 0 for ASCII driver (For the 1764-LRP only, you can select either Channel 0 or Channel 1). Refer to Series B Processors the MicroLogix 1200 and MicroLogix 1500 Programmable Controllers Instruction Set only) Reference Manual, publication 1762-RM001B-US-P for detailed configuration information.

  • Page 123: System Loading Limitations

    5V dc and 24V dc current consumed by controller, expansion I/O, and user supplied equipment. Use the MicroLogix 1500 System Expansion Worksheet — Example on page F-2 to validate your specific configuration.

  • Page 124
    For an electronic version of the worksheet, visit the MicroLogix NOTE web site. On the Internet, go to http://www.ab.com/micrologix. Enter MicroLogix 1500; go to Tools and Tips, Expansion I/O System Qualifier. Catalog Number Device Current Requirements…
  • Page 125
    System Loading and Heat Dissipation Validating System Loading — Examples 1764-24AWA and 1764-28BXB Base Units Loading Value Total 5V dc Current Consumed Total 24V dc Current Consumed Total Watts Maximum Current 2250 mA 400 mA Calculated Current 650 mA + 670 mA = 1320 mA 120 mA + 250 mA = 370 mA Maximum Power Calculated Power…
  • Page 126
    A system is valid if the current and power requirements are satisfied. For an electronic version of the worksheet, visit the MicroLogix NOTE web site. On the Internet, go to http://www.ab.com/micrologix. Enter MicroLogix 1500; go to Tools and Tips, Expansion I/O System Qualifier. Catalog Number Device Current Requirements Current Consumed…
  • Page 127
    System Loading and Heat Dissipation Validating System Loading 1764-24AWA and 1764-28BXB Base Units Loading Value Total 5V dc Current Consumed Total 24V dc Current Consumed Total Watts Maximum Current 2250 mA 400 mA Calculated Current Maximum Power Calculated Power 1764-24BWA Base Units Add any User 24V sensor current for applications with dc input sensors (1764-24BWA base units only).
  • Page 128
    I/O and user supplied equipment. For an electronic version of the worksheet, visit the MicroLogix NOTE web site. On the Internet, go to http://www.ab.com/micrologix. Enter MicroLogix 1500; go to Tools and Tips, Expansion I/O System Qualifier. Catalog Number of Module Current Requirements…
  • Page 129
    System Loading and Heat Dissipation Validating System Loading for 1769-PA2 and 1769-PB2 Power Supplies Power Supply Current Capacity Specification 1769-PA2 1769-PB2 Expansion Bus Output Current Capacity 2A at 5V dc and 0.8A at 24V dc 2A at 5V dc and 0.8A at 24Vdc at 0°…
  • Page 130
    System Loading and Heat Dissipation Figure 6.3 1769-PA2 Current with +24V dc User Load = 0.25A Valid Operating Range 0.2 0.3 0.7 0.8 +24V dc Load (Amps) System Using a 1769-PB2 To validate your system, the total 5V dc current and 24V dc current consumed must be considered.

  • Page 131: Calculating Heat Dissipation

    System Loading and Heat Dissipation Calculating Heat Use this procedure when you need to determine the heat dissipation for installation in an enclosure. Use the following table. Dissipation Catalog Number Heat Dissipation Equation or Constant Calculation Subtotal 1764-24AWA 18W + (0.3 x System Loading) 18W + (0.3 x ______ W) 1764-24BWA 20W + (0.3 x System Loading)

  • Page 132
    F-10 System Loading and Heat Dissipation Publication 1764-UM001A-US-P…

  • Page 133: Glossary

    Glossary The following terms are used throughout this manual. Refer to the Allen-Bradley Industrial Automation Glossary, Publication Number AG-7.1, for a complete guide to Allen-Bradley technical terms. DGGUHVV A character string that uniquely identifies a memory location. For example, I:1/0 is the memory address for data located in Input file word 1, bit 0.

  • Page 134
    H[SDQVLRQ ,2 Expansion I/O is I/O that is connected to the controller via a bus or cable. MicroLogix 1200 controllers use Bulletin 1762 expansion I/O. MicroLogix 1500 controllers use Bulletin 1769 expansion I/O. For MicroLogix controllers, expansion I/O is all I/O residing at slot 1 and higher.
  • Page 135
    Glossary ILOH A collection of data or logic organized into groups. IXOOGXSOH[ A mode of communication where data may be transmitted and received simultaneously (contrast with half-duplex). KDOIGXSOH[ A mode of communication where data transmission is limited to one direction at a time.
  • Page 136
    Glossary ODGGHU ORJLF A graphical programming format resembling a ladder-like diagram. The ladder logic programing language is the most common programmable controller language. OHDVW VLJQLILFDQW ELW /6% The element (or bit) in a binary word that carries the smallest value of weight. /(‘ /LJKW (PLWWLQJ ‘LRGH Used as status indicator for processor functions and inputs and outputs.
  • Page 137
    Glossary QRU PDOO\ FORVHG Contacts on a relay or switch that are closed when the relay is de-energized or deactivated. They are open when the relay is energized or the switch is activated. QRU PDOO\ RSHQ Contacts on a relay or switch that are open when the relay is de-energized or the switch is deactivated.
  • Page 138
    Glossary RXWSXW VFDQ The controller turns on, off, or modifies the devices connected to the output terminals. 3&&& Programmable Controller Communications Commands SURFHVVRU A Central Processing Unit. (See CPU.) SURFHVVRU ILOHV The set of program and data files resident in the controller. SURJUDP ILOH Areas within a processor that contain the logic programs.
  • Page 139
    Glossary 56 An EIA standard that specifies electrical, mechanical, and functional characteristics for serial binary communication circuits. UXQ PRGH An executing mode during which the controller scans or executes the logic program. UXQJ A rung contains input and output instructions. During Run mode, the inputs on a rung are evaluated to be true or false.
  • Page 140
    Glossary XSORDG Data is transferred from the controller to a programming or storage device. ZDWFKGRJ WLPHU A timer that monitors a cyclical process and is cleared at the conclusion of each cycle. If the watchdog runs past its programmed time period, it causes a fault. ZULWH To send data to another device.
  • Page 141
    1764-28BXB selection guide for the AIC+ 4-11 features selection guide for the DeviceNet network 4-16 1764-28BXB sinking wiring diagram 3-13 calling Allen-Bradley for assistance 1764-28BXB sourcing wiring diagram 3-14 CE mark 1764-LRP processor certification 1764-LSP processor channel configuration DF1 full-duplex…
  • Page 142
    Index ControlFlash connecting missing/corrupt OS LED pattern description sequence of operation example system configuration using using a modem controller DF1 halfduplex protocol definition description glossary-1 determining faults DH485 communication protocol fault messages configuration parameters features DH485 network grounding configuration parameters E-13 installation connecting…
  • Page 143
    Index processor 2-15 installing your base unit F1 Functions on DIN rail 2-13 F1 key using mounting screws 2-14 F2 Functions installion 2-15 F2 key instruction glossary-3 false glossary-2 instruction set fault recovery procedure definition glossary-3 fault routine integer key faults Integer Mode automatically clearing…
  • Page 144
    Index data file protection output scan glossary-6 program compare output specifications program/data backup 1764-28BXB FET removal/installation under power Memory Module Information File memory module/real-time clock panel mounting installing 2-18 base unit 2-14 mnemonic glossary-4 PCCC glossary-6 Modbus communication protocol E-17 planning considerations for a network E-11 Modbus definition…
  • Page 145
    Allen-Bradley for assistance safety circuits controller error recovery model safety considerations determining controller faults disconnecting main power identifying controller faults periodic tests of master control relay circuit…
  • Page 146
    Index wiring recommendation wiring your controller UL certification Working Screen Operation upload glossary-8 working voltage (1764-24AWA) specifications working voltage (1764-24BWA) wire requirements specifications wiring working voltage (1764-28BXB) spade lug specifications wiring diagrams write glossary-8 Publication 1764-UM001A-US-P…
  • Page 147
    AB Spares…
  • Page 148
    Back Cover Publication 1764-UM001A-US-P — April 2000 PN 40072-091-01(A) Supersedes Publication 1764-6.1 — February 1999 and 1764-6.1-DU1 — September 1999 © 2000 Rockwell International Corporation. Printed in the U.S.A.
  • Page 149
    AB Spares…

Источник

Обновлено: 19 сентября 2023 г. 17:45

Фото ПЧ Allen Bradley PowerFlex40

При работе промышленной электроники Allen Bradley в системах вентиляции, теплоснабжения или автоматизированном производственном оборудовании часто возникают неисправности, распознать которые можно считав коды ошибок и произведя расшифровку этих кодов по инструкции на конкретную модель электронного оборудования. Наиболее частое использование в промышленном оборудовании получили следующие частотные преобразователи фирмы Allen Bradley: PowerFlex, 1305 Series, 1332 Series, 1333 Series, 1334 Series, 1336 Series, 1341 Series, 1351 Series, 1352 Series, 1361 Series, 160 Series,. В свою очередь серия Allen Bradley PowerFlex включает в себя следующие модели: PowerFlex 755T, PowerFlex 755TL, PowerFlex 755TR, PowerFlex 755TM, PowerFlex 753, PowerFlex 755, PowerFlex 755T, PowerFlex 70, PowerFlex 700S, PowerFlex 700, PowerFlex 700L, PowerFlex 523, PowerFlex 525, PowerFlex 527, PowerFlex 4M, PowerFlex 4, PowerFlex 40, PowerFlex 40P, PowerFlex 400. Своевременная расшифровка ошибок может значительно ускорить диагностику и ремонт преобразователей частоты, подробнее об этом написано здесь.

Частотные преобразователи Allen Bradley имеют следующие распространенные ошибки:

Наиболее частые ошибки преобразователей Allen Bradley PowerFlex 40:

Ошибка F2 (error F2) — ошибка входа Auxiliary;
Ошибка F3 (error F3) — обрыв фазы на входе;
Ошибка F4 (error F4) — пониженное напряжение;
Ошибка F5 (error F5) — перенапряжение;
Ошибка F6 (error F6) — механическая неисправность двигателя;
Ошибка F7 (error F7) — перегрузка двигателя;
Ошибка F8 (error F8) — перегрев радиатора;
Ошибка F12 (error F12) — аппаратная перегрузка по току;
Ошибка F13 (error F13) — короткое замыкание на землю;
Ошибка F29 (error F29) — ошибка аналогового входа;
Ошибка F33 (error F33) — превышено количество попыток автоматического повторного включения — АПВ;
Ошибка F38 (error F38) — замыкание фазы U на землю на выходе ПЧ;
Ошибка F39 (error F39) — замыкание фазы V на землю на выходе ПЧ;
Ошибка F40 (error F40) — замыкание фазы W на землю на выходе ПЧ;
Ошибка F41 (error F41) — короткое замыкание между фазами UV;
Ошибка F42 (error F42) — короткое замыкание между фазами UW;
Ошибка F43 (error F43) — короткое замыкание между фазами VW;
Ошибка F48 (error F48) — параметры EEPROM были сброшены;
Ошибка F63 (error F63) — перегрузка по току по программной уставке;
Ошибка F64 (error F64) — перегрузка во время работы;
Ошибка F70 (error F70) — неисправность силовой части;
Ошибка F71 (error F71) — ошибка связи;
Ошибка F80 (error F80) — ошибка автонастройки;
Ошибка F81 (error F81) — ошибка связи RS485;
Ошибка F100 (error F100) — ошибка контрольной суммы записанных параметров;
Ошибка F122 (error F122) — ошибка платы ввода-вывода.

Похожие статьи:

  • Типы выходов датчиков
  • Свинцово-кислотные аккумуляторные батареи
  • Ni-Cd аккумуляторные батареи
  • Delta Servo ASDA-A2 ошибки — расшифровка кодов неисправностей сервоприводов
  • Ремонт и поверка установок Тангенс-3М

Время выполнения запроса: 0,00748205184937 секунды.

Источник

Понравилась статья? Поделить с друзьями:
  • All wheel drive опель инсигния ошибка
  • Alldata ошибка 4502
  • All wheel drive ошибка опель мокка
  • All recursive ошибка 1
  • All radio ошибка