3 ms·
"1 packet from Russia"? This requires physical access to 1 wind turbine in a networked Wind farm, which is going to be at most 250 turbines and I'd be really im
by arm85 9y ago
"1 packet from Russia"? This requires physical access to 1 wind turbine in a networked Wind farm, which is going to be at most 250 turbines and I'd be really impressed if they were all networked together.
"Full speed reverse?" You could perhaps increase fatigue overtime. Some wind turbines can start spinning to get to a more favorable position in their power curve, I'm not aware of utility grade ones being able to do that, or go "full speed" enough to cause physical damage.
I have some experience with network access in a UK wind farm. They were extremely paranoid about network security.
- brianwawok 9y agoSorry I am not well versed in the rest APIs of wind turbines. But based on how most of such things, I would suspect there are switches you could flip that would make very bad things happen to the turbine... if the API is literally foolproof, then great. But an API that can cause no damage does not make a lot of sense to be paired to a device that has poor network security.
- arm85 9y agoREST API? Wind turbine SCADA systems use interfaces like modbus or canbus, etc. Security in these systems are dedicated network circuits and firewalls configured to only allow access on a specific port, from a specific IP address on a specific port.
- forgottenpass 9y agoNah man, I have it on good authority that a node.js frontend to a series of Rust microservices is the best design for these control systems. Quit joshing me that anything else is ever used in any domain.
- noir_lord 9y agoNode.js? Old technology our fusion reactors all run TypeScript compiled down to WebAssembly with some Elm interop. Mostly the Elm is there so our devs can go to conferences and look down on others for not using Elm, I mean why else would you adopt new technology if not for that?.
- horsawlarway 9y agoI don't think he really even read the article...