/
Beckhoff Configuration Management

Beckhoff Configuration Management

This page is intended to give guidelines for the high-level process of how the code on the Beckhoff controllers evolves over time. The details of the mechanics of modifying code for the Beckhoff PLCs is detailed here: Procedure to download and activate modified code on Beckhoff PLC

Procedure

  • Plan change with gatekeeper.

  • Upload running code from PLC (assumes TwinCAT is configured correctly to download source when boot project is created).

  • Compare uploaded code with the latest in the Bitbucket repository. Resolve any differences, favoring the uploaded running code in 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, ensuring that source code is downloaded to PLC.

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

Related content

Procedure to download and activate modified code on Beckhoff PLC
Procedure to download and activate modified code on Beckhoff PLC
More like this
B&R Configuration Management
B&R Configuration Management
More like this
GIS PLC Code Configuration Management Process
GIS PLC Code Configuration Management Process
More like this
Code Reviews
More like this
Software Development Policies
Software Development Policies
More like this
Beckhoff
More like this