Customers that are familiar with programming Logix PLCs can use the same tools to configure Rockwell Automation's Stratix 8000 Ethernet switch. The switch appears in the software configuration tree just like a controller, I/O module and drives in the control system architecture.
A brochure is a flyer, pamphlet or leaflet that is used to pass information about something. Brochures are advertising pieces mainly used to introduce a company or organization and inform about products and/or services to a target audience. Brochures are distributed by radio, handed personally or placed in brochure racks. They may be considered as grey literature. They are usually present also near tourist attractions.
The most common types of single-sheet brochures are the bi-fold (a single sheet printed on both sides and folded into halves) and the tri-fold (the same, but folded into thirds). A bi-fold brochure results in four panels (two panels on each side), while a tri-fold results in six panels (three panels on each side).
Other folder arrangements are possible: the accordion or "z-fold" method, the "c-fold" method, etc. Larger sheets, such as those with detailed maps or expansive photo spreads, are folded into four, five, or six panels. When two card fascia are affixed to the outer panels of the z-folded brochure, it is commonly known as a "z-card".
It has been my experience so far that for many applications the higher speeds aren't justified with the associated costs. When I was working for an OEM, the extremely high-speed stuff was handled with a separate dedicated bus. The rest of the automation system didn't require the speed as much as the reliablity.
Not completely sure. Maybe others can weigh in. One Gig Ethernet is very commonly used for first tier consumer level gear. I suspect most installations, especially in control applications, are operating at 10 Gb/sec. Moving to the higher speeds for a typical installation just doesn't justify the extra cost at this point. But as the cost moves down, we know the need for speed will move up ... especially with the complexity of the plant-wide Ethernet networks growing.
Changes in industrial networking have always been "life in slow motion" especially with the amount of legacy systems running older proprietary protocols. It's not going to happen overnight. But except for simpler device-level networks, Industrial Ethernet protocols are the 800 lb gorilla in the room at this point when it comes to industrial control/factory enterprise networking and connectivity. The other networking technology to keep an eye on is WiFi.
I like this trend; I'm wholeheartedly behind it and reach for Ethernet/IP whenever possible in my projects.
(You can hear the BUT coming, can't you?)
This trend is riding on a venerable but misused component. Industrial networks should not be relying on RJ45 connectors. They're not robust and were never intended for the factory floor. I'd like to see a new standard industrial connector for Ethernet, and I'd like to see the companies involved for once agree quickly on it. M12 Code D would be nice, but I won't insist on it. But something better than what was originally designed for office and home use has to get onto the factory floor.
I guess I must be old. I look at a the combined Rockwell/Cisco proposed 'Campus netowrk, a single robust network infrastructure' where everything is connected as:
- cryptography - makes it harder to troubleshoot
- layers of firewall with many rules, which should be consistent but are REALLY easy to mess up
- selected services enabled 'by exception only' filtering unknown data at multiple points
- edge ports disabled by default, making troubleshooting more difficult
- a complex backup system required for the various switche configuration, with their various VLANS
- administration to keep the versions of all the switches synchronized and working together
I need data to flow in a timely manner to keep my mill running. If a problem arises, I need tools to figure out what is wrong, so the failed component (or errant rule) can be located and rectified.
Getting coherent log data out of a Cisco network, in my opinion, requires a lot (400 hours? per year) of training in Cisco classrooms. And personnel dedicated to network support.
Or I can put in dedicated IO networks (Profibus, Controlnet, Devicenet, Modbus Plus, and all the old ways) and I can troubleshoot them, one at a time, isolated.
Fixing an IO network is, compared to fixing an ethernet network, a piece of cake.
Right now, our over-worked but pretty well trained IT guys, can't tell me why it sometimes takes 2 minutes to open a 5K text file from our head office via Lotus Notes. I am quite technical on control systems, but not on ethernet - I already have a job.
With Rockwell saying that 60% of their business is Ethernet-based, we can only assume that there are a lot of people out there still using proprietary protocols. Any idea if we will ever see across-the-board Ethernet, Al?
Agreed; a great article. I think the most important element of the rise of Ethernet is that it's going to force vendors towards commonality, at least as far as intercommunications are concerned. OTOH, this won't eliminate vendor lock-in as much as one might suppose, because there are other proprietary elements involved in, for example, the tools chain used to program your PLCs. Writ large, we have a battle for control of the factory between the high-end (i.e., expensive), high-value vendors, and the low-cost, buy it online and do it yourself world.
Focus on Fundamentals consists of 45-minute on-line classes that cover a host of technologies. You learn without leaving the comfort of your desk. All classes are taught by subject-matter experts and all are archived. So if you can't attend live, attend at your convenience.