Connection view parameters

Parameter
Description
Requested Packet Interval (RPI) (ms)
Specifies the data exchange rate between the controller and the device. The valid RPI range displays under this field. Valid ranges and default values are dependent on the device. Otherwise, the RPI field is read-only and set by the Safety Task or the Motion Group.
IMPORTANT: Changing the RPI value while online causes the connection to the device to close and open again.
You cannot edit the RPI value 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 device minimum allowed RPI is the same as the maximum allowed RPI.
  • The controller is in Run mode.
For
HART®
devices:
The RPI value is set or adjusted within the range from 500.0 ms through 9999.9 ms.
If the HART device being created is the first device under a HART Analog device, the default RPI value will be 500.0 ms. Otherwise, the RPI value matches the RPI value specified in other HART devices under the same HART Analog device.
If the HART device being pasted is the first device under a HART Analog device, the RPI value from the copy is retained. Otherwise, the RPI value matches the RPI value specified in other HART devices under the same HART Analog device.
Changes to RPI are automatically applied to all HART devices under the same HART Analog device. If another HART device has pending edits to its RPI at the time an RPI is applied in a different HART device.
  • If edits are cancelled in the other HART device, the changed RPI value is applied without notice.
  • If edits are applied in this HART device, a prompt appears asking to apply changes.
Use unicast connection over EtherNet/IP
Connection over EtherNet/IP
Determines whether to establish a Unicast or Multicast connection over the network. The default value is Unicast. The default for High Availability controllers is Multicast.
For HART devices, you cannot modify the input connection type when online.
Use Multicast or Unicast for non-redundant controllers. Use Multicast for redundant controllers.
If modifying this field while online, selecting
Apply
 causes
Connection Interruption
 to open.
IMPORTANT:
  • Changing between a Unicast and Multicast connection while online causes the connection to the device to close and re-open.
  • If the device path crosses ControlNet, the connection to the device will not open until starting RSNetWorx for ControlNet to reschedule the network.
  • Changing the Input Type / Connection over EtherNet/IP connection causes the Input Trigger column to set to default.
  • Changing to a Multicast connection will fail to reconnect with the device if the connection crosses multiple EtherNet subnets. Multicast connections are limited to one subnet.
Use scheduled connection over ControlNet
Connection over ControlNet
Determines whether to explicitly schedule the network connection over ControlNet networks.
  • 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
    , publication
    CNET-UM001
    .
  • An unscheduled connection is established with the target device.
Tip: If this connection is changed from unscheduled to scheduled, schedule the connection using RSNetWorx for ControlNet software.
Inhibit module
Inhibits or uninhibits connections to the device. Inhibiting the device causes all connections to the device to be broken and results in loss of data.
When the device is inhibited when online, the icon representing this device in the controller organizer displays the Inhibited Icon.
Select to stop communication to a device.
  • If inhibiting the device while online and connected to the device, connections to the device close. The device's outputs go to the configured Program mode state (if supported by the respective device).
  • If inhibiting the device while online but a connection to the device not established (perhaps due to an error condition or fault), the device is inhibited. The device status information changes to indicate that the device is Inhibited and not Faulted.
  • If uninhibiting a device (clear the checkbox) while online, and no fault condition occurs, connections are made to the device and the device is dynamically reconfigured (if the connection is the owner controller) with the configuration created for that device. If a listener (a Listen Only Communications Format), the device cannot be re-configured.
  • If uninhibiting a device while online and a fault condition occurs, connections are not made to the device.
Major fault on controller if connection fails while in Run mode
Determines whether the controller will enter a major fault state if connection fails while the controller is in Run mode.
Enable Automatic Diagnostics
Enables or disables Automatic Diagnostics.
Tip: Disabling this feature prevents this device from publishing diagnostics to
FactoryTalk® Alarms and Events
.
Connection fault
Displays the fault code returned from the controller (for the configured device) and the text detailing the connection fault that occurred. Common categories for errors are:
  • Connection Request Error
    . Controller attempting to make a connection to the device and has received an error. Connection not made.
  • Service Request Error
    . Controller attempting to request a service from the device and has received an error. Service not performed successfully.
  • Module Configuration Invalid
    . Configuration in device invalid.
  • Electronic Keying Mismatch
    . Electronic Keying enabled and some part of the keying information differs between the software and the device.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal