Connection Tab Overview

Use this tab to define controller-to-module behavior. On this tab:
  • Select a requested packet interval.
  • Specify the type of connection.
  • If supported, select an input trigger.
  • Choose to inhibit the module.
  • Configure the controller so that a loss of connection to this module causes a major fault in the controller.
  • Choose whether to use a scheduled or unscheduled connection over ControlNet.
  • View module faults.
    NOTE: The data on this tab comes directly from the controller. This tab displays information about the condition of the connection between the controller and the module.
Parameters
Name
Displays the name of the connection as it appears in the Module Definition group in the
Modules Properties
 dialog box -
General
tab.
If the controller has no configured connections to this module, the text
<No connections configured>
shows.
Requested Packet Interval (RPI) (ms)
The RPI is the data exchange rate between the controller and the module. If applicable, enter the RPI value. The valid RPI range is shown to the right of the field. Valid ranges and default values are dependent on the module.
Otherwise, the RPI is read-only and set by the Safety Task or the Motion Group.
The RPI value cannot be edited under these conditions:
  • The connection is a Safety Output connection.
  • The connection is a Motion connection.
  • The connection is a Safety Connection and the Safety Controller is Safety Signed or Safety Locked.
  • The module's minimum allowed RPI is the same as the maximum allowed RPI.
  • The controller is in Hard Run Mode.
    NOTE: Change the RPI for a Safety Input connection also in the
    Safety
    tab.
WARNING:
Changing the RPI value while online causes the connection to the module to close and re-open.
Input Type / Connection over EtherNet/IP
Select to establish a Unicast or Multicast connection over the network. The default value is Unicast.
Use Unicast for non-redundant controllers. Use Multicast for redundant controllers.
If modifying this field while online, selecting
Apply
causes the
Connection Interruption
dialog box to open.
WARNING:
Changing between a Unicast and Multicast connection while online causes the connection to the module to close and re-open.
WARNING:
If the module path crosses ControlNet, the connection to the module will not open until starting RSNetWorx for ControlNet to reschedule the network.
WARNING:
Changing the Input Type / Connection over EtherNet/IP connection causes the Input Trigger column to set to default.
WARNING:
Changing to a Multicast connection will fail to reconnect with the module if the connection crosses multiple Ethernet subnets. Multicast connections are limited to one subnet.
Input Trigger (if supported)
Select one of these input trigger options for the trigger mechanism of input data for the module:
  • Cyclic
     - data is produced at the specified Requested Packet Interval (RPI).
  • Change of State
     - data production occurs when the data changes state in the module.
  • Application -
    data production is triggered by the target device application.
The default value is Cyclic (if supported by the module). Otherwise, the default value is Change of State (if supported by the module). Otherwise, the default value is Application.
WARNING:
Changing the Input Trigger (for example, from Cyclic to Change of State) while online causes the connection to the module to close and re-open.
WARNING:
If the module path crosses ControlNet, the connection to the module will not open until starting RSNetWorx for ControlNet to reschedule the network.
WARNING:
Changing the Input Type / Connection over EtherNet/IP connection causes the Input Trigger column to set to default.
Connection over ControlNet
Select whether to explicitly schedule the network connection over ControlNet networks. Valid values include:
  • Scheduled
    - A scheduled connection is established with the target device. Use RSNetWorx for ControlNet software to schedule the network in order to activate the configured devices in the application. Refer to the
    ControlNet Network Configuration User Manual
     (CNET-UM001).
  • Unscheduled
    - An unscheduled connection is established with the target device.
    NOTE: If this connection is changed from unscheduled to scheduled, schedule the connection using RSNetWorx for ControlNet software.
Inhibit Module
Select or clear this box to inhibit or uninhibit connections to the module. Inhibiting the module causes all connections to the module to be broken.
WARNING:
Inhibiting the module causes all connections to the module to break and results in loss of data.
When the module is inhibited when online, the icon representing this module in the controller organizer displays the Inhibited Icon.
Select This check box to:
Online
Stop communication to a module.
  • If inhibiting the module while online and connected to the module, connections to the module close. The module's outputs go to the configured Program mode state (if supported by the respective module).
  • If inhibiting the module while online but a connection to the module not established (perhaps due to an error condition or fault), the module is inhibited. The module status information changes to indicate that the module is Inhibited and not Faulted.
  • If uninhibiting a module (clear the check box) while online, and no fault condition occurs, connections are made to the module and the module is dynamically reconfigured (if the connection is the owner controller) with the configuration created for that module. If a listener (a Listen Only Communications Format), the module cannot be re-configured.
  • If uninhibiting a module while online and a fault condition occurs, connections are not made to the module.
Major Fault On Controller If Connection Fails While in Run Mode
Select this box to configure the controller so that a connection failure causes a major fault on the controller when in Run mode.
This check box is automatically selected for the 1769 Virtual Backplane adapter and all 1769 I/O modules that are children of the virtual adapter.
NOTE: This parameter only applies to standard connections. It is disabled when only safety connections are established to the module.
Module Fault
Displays the fault code returned from the controller (for the configured module) and the text detailing the Module Fault that occurred. For more information, see the
Module Faults
 topic in the Logix Designer online help.
Common categories for errors:
  • Connection Request Error
     - Controller attempting to make a connection to the module and has received an error. Connection not made.
  • Service Request Error
     - Controller attempting to request a service from the module and has received an error. Service not performed successfully.
  • Module Configuration Invalid
     - Configuration in module invalid.
  • Electronic Keying Mismatch
     - Electronic Keying enabled and some part of the keying information differs between the software and the module.
Status
Displays the status the controller has with the module:
This status:
Indicates:
Standby
Transient state when shutting down.
Faulted
Controller unable to communicate with the module.
When the status is Faulted, the Connection tab displays the fault.
Validating
Transient state before connecting to the module.
Connecting
State while connection(s) being established to the module.
Running
Module communicating and everything working as expected.
Shutting Down
Connections closing.
Inhibited
Connection to module inhibited.
Waiting
Connection to module not yet made due to one of these reasons:
  • Parent has not yet made a connection.
  • Parent is inhibited.
  • Parent is faulted.
Offline
Controller not online.
Reconfiguring
Configuration information being downloaded to the module again.
Firmware Updating
Modules firmware being updated.
Configuring
Module being configured by the Logix controller.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal