As an electronics technician i have to ask:' How do you troubleshoot/find faults in those systems without power applied?
First of all, it's only control power that's off (sensors are always on). Measuring a voltage is one thing, but if you need to replace a motor, you have to lock out the energy. Secondly, the electrical devices that do the controlling are usually located in electrical panels accessible from outside the guarding. Third the cell is normally designed so you can see pretty well what's going on from outside (the guarding is typically something you can see through like lexan or square mesh painted black).
I can't believe I heard about this story on the radio this morning, with the radio hosts likening it to the movie Terminator. I work in industrial automation and let me assure you that these industrial robots have absolutely nothing even remotely approaching "AI". An industrial robot is no more than a multi-axis motion control system with some fancy co-ordinate transformation math on top of it. The programs are as simple as "wait for this input, then move to this point, turn on this output, wait for this input", etc.
When we're starting up any industrial automation workcell (whether it as a robot or not), the cell design has to be certified (stamped by a professional engineer in our jurisdiction) that the safety system meets appropriate regulations and is built with certified components, all of which are specified to specific safety requirements based on hazard, etc.
The thing is, those regulations are there to protect factory workers and people interacting with the cell in normal operations. If you take any machine apart using a wrench, you're supposed to be properly trained in how to lock out all sources of energy in the machine. That said, when you're programming the cell, you're allowed to be inside the cell and power up the robot using a teach pendant with a special enabling switch you have to hold down. This requires you to put the robot in a special teach mode which also limits the robot speed to less than 250 mm/s. If the cell was built correctly, the interlock switches on the gates have to be wired into the gate inputs on the robot, and when you open the guarding, the robot can only be energized while in teach mode with the teach pendant enabled.
The system isn't fool proof. We all know impatient people. Maybe the person programming the robot didn't check that the gate switches were wired in properly, or maybe he asked his buddy to close the gate behind him and press the reset button because he wanted to see what was going on (something I've seen several people do, and have always chastised them for). Maybe the guarding wasn't completely installed yet. Maybe he mistakenly put it in "Teach 2" mode which allows full speed operation with the teach pendant enabled. This mode is generally illegal in the United States, but some jurisdictions do allow it as long as you take other safeguards, like striping out a dedicated area on the floor where the robot can't reach where you're allowed to stand.
That's why this is most certainly human error. The question is, who is liable? Did a manager pressure the guy to continue programming the robot even though proper safeguards weren't in place? Did he just get impatient and ignore his own safety training? I see lots of people do that, and I also see lots of people with missing fingers - go figure.
Data most targeted: In 31 percent of cases Trustwave investigators found attackers targeted payment card track data (up 12 percentage points over 2013). Track data is the information on the back of a payment card that’s needed for an in-person transaction. Twenty percent of the time attackers sought either financial credentials or proprietary information (compared to 45 percent in 2013) meaning attackers shifted their focus back to payment card data.
I assume this is mostly because the US still doesn't have chipped credit cards, or has that changed since a year or so ago when I was there? I thought the magstripe was going away.
There's a lot of talk about the fact that this would mean tracking everywhere you went. Why not just track miles driven by your odometer? I don't know about Oregon, but here you report your odometer reading when you pay for your license plate. You could just also pay the estimated tax (you already tell your insurance company how far you're probably going to drive) when you license your vehicle, and then pay/receive the difference when you re-register it next year, plus when you sell it. Seems a lot simpler and less expensive than a GPS tracker.
Also, seems like there should be a per-distance tax for roads, plus a gas consumption tax just to cover the increased societal costs of using gas. Use the gas tax to build out charging stations.
There is some truth to this. I am a "successful" programmer (in my opinion, since I get paid to do it and people are generally happy with the results). My job every day consists of a series of frustrating problems where the solution is not obvious, but I'm sure it should be possible to solve it. A 3rd party library causes a heap corruption about once a week, or customers refuse to send data files in a consistent format. The print spooler service keeps stopping.
People come to me with the *simplest* of problems, and they can't even be bothered to type their question into Google, let alone *read* the results that come up! Most people aren't even willing to try it or learn for themselves, just waiting for someone's permission, I guess.
"It just doesn't work" is such a commonly repeated phrase, right next to "the Internet's not working". What doesn't work? Did you try doing it like this? Did it work yesterday? Has it ever worked? Can anyone else get it to work? Don't you want to know how it works? Do you even want it to work, or are you just relieved that you have something external to blame for why you couldn't get your work done?
Seriously, the key to success is just not giving up when you know something's possible.
The one day you'd sell your soul for something, souls are a glut.