Panel firmware policy changed after one bad update in Columbus

I read on a manufacturer bulletin that a tech in Columbus pushed a new firmware without checking the release notes, and it locked up 12 panels across 5 sites. Took him two days to roll them all back with a laptop and a USB stick. My takeaway was that we now have a rule here to wait 48 hours after any update goes public before we touch a single system. Anyone else have a situation where a routine update turned into a service call marathon?

1 comments

Log in to join the discussion

Log In

1 Comment

the_oscar2d ago

Waited a week once after a bad rollout, saved my crew.

8