Connection view parameters

Parameter
Description
Requested Packet Interval (RPI) (ms)
Specifies the data exchange rate between the controller and the device. Valid values range from 500.0 ms (default) through 9999.9 ms. The RPI value cannot be edited when the minimum and maximum allowed values are equal or the controller is in Run mode.
For the first device under a HART Analog device, the value defaults to 500.0 ms. Otherwise, it matches that of other devices under the same HART Analog device.
For a pasted device that is the first under a HART Analog device, the copied RPI value is retained. Otherwise, the value matches that of other devices under the same HART Analog device.
Changes to RPI are automatically applied to all devices under the same HART Analog device. If another device has pending edits to its RPI when a 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.
IMPORTANT:
  • Changing the RPI value while online causes the connection to the device to close and open again.
Connection over EtherNet/IP
Determines whether to establish a unicast or multicast connection over the network. The default value is
Unicast
.
The connection type depends on the controller redundancy configuration.
  • If controller redundancy is enabled, only multicast connection is supported. Selecting
    Unicast
     displays a warning message.
  • If controller redundancy is disabled, only unicast connection is supported. Selecting
    Multicast
     displays a warning message.
For HART devices, the input connection type cannot be modified when online. 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 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.
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 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.
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