I/O Configuration

  • Module icons in the I/O Configuration folder change to indicate the module has faulted or the connection to the module has been interrupted.
  • To remove a yellow triangle warning symbol, first check the connection status. If the status is "Connection is not scheduled", re-open the RSNetWorx software. Return to RSLogix 5000 software and the yellow triangle should be gone.
  • To easily find a module in the Select Module Type dialog, simply start typing any part of the module name or description. When you start typing, the Find Module dialog is launched automatically.
  • Use rack optimized communication formats for digital I/O modules to minimize amount of controller memory and communications overhead associated with these modules.
  • RSLogix 5000 automatically creates controller tags when you create an input or output module. You can reference these tags directly in your logic.
  • Use alias tags to assign names to specific input/output data and/or to provide a short alternative to lengthy structure member names.
  • When you configure an analog I/O module, hold the shift key as you move the slider to increment HH, H, L, and LL values in whole numbers.
  • Copy I/O data to a User-Defined Type (UDT) so you can synchronize I/O data with program scan. The UDT also enables easier mapping of physical I/O.
‹ Controller ProjectsupTasks, Programs and Equipment Phases ›

( categories: )

"•To remove a yellow

Submitted by Coowallsky (not verified) on Fri, 2011-12-16 11:58.

"•To remove a yellow triangle warning symbol, first check the connection status. If the status is "Connection is not scheduled", re-open the RSNetWorx software. Return to RSLogix 5000 software and the yellow triangle should be gone."

By merely opening the RSNetworx software the triangle should be gone? There's more to it than that.

"Use rack optimized

Submitted by Anonymous (not verified) on Fri, 2011-12-16 12:00.

"Use rack optimized communication formats for digital I/O modules to minimize amount of controller memory and communications overhead associated with these modules."

But understand that status and point-level diagnostic information will not be available in the Controller Tags collection even if the I/O modules are of the diagnostic variety.

"•Copy I/O data to a

Submitted by Coowallsky (not verified) on Fri, 2011-12-16 12:06.

"•Copy I/O data to a User-Defined Type (UDT) so you can synchronize I/O data with program scan. The UDT also enables easier mapping of physical I/O."

And I would add, address ONLY the UDT I/O members in logic (or aliases to the UDT members) instead of the physical I/O OR aliases to the physical I/O UNLESS an Immediate I/O condition/status for particular I/O points is desired.