It continued operating for decades after the event. I’m sure they already solved that issue. It can still be improved I’m sure though.
Comment on Microsoft inks deal to restart Three Mile Island nuclear reactor to fuel its voracious AI ambitions
echodot@feddit.uk 1 week agoI remember I had to do the 3 mile Island incident as part of my university degree. Apparently one of the biggest problems was that the control interface was hard to understand for the human operators.
So I guess if they just replaced the control system with a modern computer that would fix most of the problems. Obviously not a Windows system, otherwise we’ve just got the same issue all over again.
Cethin@lemmy.zip 6 days ago
kent_eh@lemmy.ca 6 days ago
So I guess if they just replaced the control system with a modern computer that would fix most of the problems
Introducing new Clippy for reactors.
ShaggySnacks@lemmy.myserv.one 6 days ago
“It looks like you are trying to prevent a nuclear meltdown. I can help with that.”
jadedwench@lemmy.world 6 days ago
It was the SCADA view right? A lot of SCADA software is basically running on top of windows, though you typically would never see the desktop. Ignition at least is cross platform, but that is because the server is Java and Jython. A big part of why things are running on windows is due to OPC, which was traditionally all DOM and .NET. It is basically a standard communications protocol and is what allows your HMI/SCADA to communicate with PLCs. Otherwise, you use proprietary drivers and native PLC specific protocols.
SCADA programming/design is kind of an art and is usually written by an either an overworked engineer or someone who had far too much time on their hands. You basically build screens using specialized software, hook up buttons and UI elements to PLC signals, and pass some signals from the UI to the PLC. They are all heading in the Edge/iot/cloud/web based/techno-babble direction these days…
Ignition, programming software is free!: inductiveautomation.com
Some other random ones I have seen or used in the past: www.siemens.com/global/en/…/wincc-unified.html www.aveva.com/en/products/intouch-hmi/ www.rockwellautomation.com/en-us/…/view.html
CLOTHESPlN@lemmy.world 6 days ago
“is usually written by an over worked engineer”
I’m in this post and I don’t like it.
But really these scada systems are rarely well defined by the time implementation happens. Often the architect has a great plan, but by the time it’s passed to a manager, a non-software engineer, to the product engineer to the automation team to the contractor the end result is “X data is pushed in With Y form and we use either a,b,or c date time stamp any nobody knows”