Maintenance & Support
Firmware & Configuration Updates
Keeping control firmware current, and settings aligned with a network that has changed since commissioning.
Networks change. Loads grow, feeders get split, new generation connects, and protection settings that were correct at commissioning slowly stop being correct. Firmware also gets revised, sometimes to fix behaviour that matters.
Updating either is straightforward work that is easy to defer indefinitely, until a fault reveals that nobody has looked at the settings in eight years.
What updates cover
- Control firmware version assessment and update
- Protection setting review against current network conditions
- Re-grading where upstream or downstream protection has changed
- Configuration backup before any change
- Verification testing after changes are applied
- Updated settings record issued after the work
What matters in practice
-
Back up before changing
The working configuration gets saved before anything is modified, so there is always a known-good state to return to.
-
Settings drift with the network
Protection correct for a feeder in 2018 may be poorly graded for the same feeder after two extensions and a new connection.
-
Test after updating
A firmware update or settings change is verified by injection afterwards. An untested change is an assumption.
-
Documented
What changed, when and why goes into the record, so the next engineer is not reverse-engineering someone's decision.
Related services
Settings needing review?
Tell us what you need and where the site is, and we will scope the work and quote it.