Controller Projects

  • Whenever you go online using RSLogix 5000, changes made to controller are simultaneously made to a temporary copy of the project file (.ACD). Save makes these changes permanent. Therefore, an upload is only necessary to obtain the latest copy of the tag data in the controller.
  • Both Rockwell Automation and third-party sample projects are installed with RSLogix 5000. You can find them in the RSLogix 5000 Samples folder. These projects demonstrate program techniques and code that you can use to program select modules.
  • Avoid pointing one alias tag to another alias tag to ensure the application maintains the appropriate references after an upload.
  • Avoid pointing multiple alias tags to the same base tag to ensure the application maintains the appropriate references after an upload.
  • All tag names are downloaded and resident in the controller along with your logic.
  • On download, if the ControlNet schedule stored in the offline RSLogix 5000 project file is old, RSLogix 5000 will retrieve the latest ControlNet schedule from the associated RSNetWorx project file. To make an association to an RSNetWorx project file, use the RSNetWorx tab in the Module Properties dialog of the ControlNet scanner.
  • RSLogix 5000 supports moving your project from one Logix platform/controller to another.
  • ACD, L5K, CSV, and L5X files are independent of which translated version of RSLogix 5000 imports or exports the file. The software doesn't create language-specific import/export files.
  • Use any translated version of RSLogix 5000 software to go online to a controller without having to re-download.
  • In a safety controller, standard tags in a safety mapped relationship follow safety restricted states. For example, a standard tag mapped to a safety tag is read-only in a safety locked state.
  • Use Add-On Instructions to initialize tag values to specific values at the beginning of each routine or program scan. Then source protect the AOI to assure that values are correctly initialized and not overwritten manually.
  • The order of members within a User-Defined Data Type affect the memory size of the data type. Within the UDT, keep members of the same data type together.
‹ KeyboardupI/O Configuration ›

( categories: )

"Therefore, an upload is

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

"Therefore, an upload is only necessary to obtain the latest copy of the tag data in the controller."

Well, tags are automatically updated once you go online. Uploads are necessary when there are changes in the logic in the controller vs. the open project file, OR if while saving changes it is desirable to update the tags in the project file to reflect the current values in the controller.

"•The order of members

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

"•The order of members within a User-Defined Data Type affect the memory size of the data type. Within the UDT, keep members of the same data type together."

While technically true, it is not good programming practice. First, it means you're letting the memory issue dictate the structure of your UDT/AOI members/parameters. That's NOT what the purpose of UDTs/AOIs are for. They are for programming in a manner that is most beneficial to the process AND to the benefit of programming/support pesonnel.

Second, with processor memory ranges up to 32MB, the worrying over 8 or 9 DINT's worth of data potentially wasted means you have bigger fish to fry if those 8 or 9 DINT's worth of data can make or break using a 5562 over a 5561.

Bottom line, arrange the members in a logical and understandable order. Memory should NOT be an issue in deciding their order.