B&R Configuration Management

Owned by Karl Newman
Last updated: Dec 12, 2024
1 min read

This page is intended to give guidelines for the high-level process of how the code on the B&R controllers evolves over time.

Procedure

  • Plan change with gatekeeper.

  • Attempt to upload running code from PLC. This requires that the source code has been downloaded to the PLC.

  • Compare uploaded code with the latest in Bitbucket. Resolve any differences, favoring the code in the git repository case of discrepancy. If the discrepancies are intended to be part of the running code, include them in the change plan, possibly handling them separately first before the main change is implemented.

  • Implement changes and test.

  • When test is satisfactory, write boot project and download the source code to the PLC. The active B&R projects should already be configured to transfer the source code to the PLC as part of a normal transfer, but this can be confirmed in the Configuration tab of the project. Select the top level of the active configuration and inspect the properties. In the “Source Files” tab, the option to “Store project source files on target” should be checked with “During each project transfer” selected. Further, ensure that under Storage Options, “Complete” is selected with “Include upgrades” checked. Secure the source code with the password recorded in Keeper.

  • Store modified code in Bitbucket with a descriptive comment and link to any associated Jira tickets.