|
|
GET CAN IN GEAR
KENNETH J. KORANE To help their customers meet demands for higher throughput, ensure operator safety, and keep up with proliferating environmental regulations, manufacturers of off-highway equipment are taking a serious look at Controller Area Network (CAN) serial communications networks. Electronic control systems based on CAN provide fast closed-loop, real-time performance with excellent reliability. Developed by Bosch and Intel for the automotive industry, standard CAN microchips are widely available, inexpensive, and designed to withstand the harsh electrical and physical environment of a car. These attributes make CAN networks attractive for industrial machines. For instance, since the 1980s it has been used on the factory floor for numerous process and motion controllers, and discrete manufacturing production lines. Interest is now migrating to mobile equipment.
CAN BASICS CAN is a standard communications protocol (ISO 11898) that connects actuators and "intelligent" sensors in a serial network, coordinated by a host computer. On the machine, the information network interconnects every device - each with its own microcontroller - establishing a common communication path between them and the host. The network architecture has advantages compared with a standard design where every component is connected directly to a central processor. The primary benefit is serial networks have fewer wires. This reduces failures due to poor connections and broken wires, cuts the cost of wires and connectors, and can substantially reduce installation expenses. CAN networks also use digital technology that takes advantage of computers and microcontrollers. A digital controller's superior ability to store data and perform calculations makes it practical to add higher-level capabilities, such as automating machine tasks or optimizing fuel efficiency. CAN is also fast - 1 Mbyte/sec for a 40-m bus length. It also contains robust error-detection software and immediately retransmits if a message is corrupted. Finally, Intel, Motorola, NEC, Philips, and Siemens, among others, offer commercially available, low-cost microprocessors with built-in CAN controllers.
ENHANCING PERFORMANCE The use of CAN on mobile equipment is still in its infancy. One reason is simply that many designers are still learning how to use it. "CAN represents a new technology requiring a lot of rethinking," says Lars-Berno Fredriksson, president of Kvaser AB, Kinnahult, Sweden. CAN opens up options previously out of the systems designer's reach, he says. "But, unfortunately, you do not recognize the possibilities until you have gained some experience in the technology." As the basic understanding of CAN grows and the first CAN design tools appearing on the market, Fredriksson predicts a sharp growth in CAN systems over the next decade. According to Andrew Martin, product manager for mobile controls at Vickers, Troy, Mich., major equipment manufacturers have a number of development programs underway but few systems are in the field. Nonetheless, the company is marketing a new control valve that can be driven with CAN bus technology. Part of the reason, says Martin, is that future mobile controls will be very similar to those on automobiles, where devices located throughout the car send information to a central processor. "We see a similar direction for the mobile-vehicle control architecture, such that everything on the machine - fuel-injection control, steering, braking - will all be controlled from a central processor. Our valve fits in with that control philosophy," says Martin.
The controller also brings added intelligence to the machine because the CAN-bus system simplifies getting data from remote locations. "Obviously, you can get information from a sensor whether you're on a bus or not," he says, "but now the valves can report back, tell you where they are and what they're doing, and the I/O modules can provide higher level information. So we get diagnostic capabilities that let you know if a valve malfunctions, a benefit that you don't have with a traditional control scheme." Because the MMC 1000 is a machine-level controller, it also takes in information from other sensors on the machine, reading engine rpm, oil temperature and pressure, and the like. Last and most significantly, says Shetty, machine functions can be automated. One example involves monitoring demand on a trencher. As the draw on horsepower from trenching increases, the controller slows the vehicle, maintaining a constant speed on the trenching wheel and preventing system overload. This produces a consistent depth and straightline cut, rather than allowing the operator to bog down the machine and have to back up and restart. It also reduces hydraulic pressure spikes, so components last longer. Automating tasks now lets less-skilled personnel do what once required highly trained operators, while improving the speed and productivity of the machine. The higher-level controller can also improve safety, such as ensuring that a manlift cannot operate outside a predetermined, safe envelope. In terms of costs, Parker's experience proves that on complex machines such as rock drills and large manlifts, the savings on plumbing and wiring offset the cost of implementation. In smaller, less-complicated mobile equipment, added functionality typically increases costs. "But in today's marketplace, users want and need features that improve the performance of their machines, so they're willing to pay the price," says Shetty.
PROTOCOL DEBATE Part of the reason few CAN systems for mobile equipment are on the market is that there is no standard, higher-level protocol. CAN takes care of the low levels of a communication protocol but a network also requires higher-layer protocols, such as DeviceNet or SDS (Smart Distributed System) used on industrial systems. For a designer to assemble a system from various manufacturers' off-the-shelf components, a fully open higher-level protocol is needed. Such a standard, universally accepted protocol for mobile equipment appears to be a ways off. In the meantime, options abound. For example, researchers at Vickers found 31 different CAN protocols currently in use, with none emerging as the front-runner for a global standard. Their solution, says Andrew Martin, was to develop hardware that supports virtually any protocol, and program it based on customer requirements. "We're using SAE 11939 because the first customer that came along asked for it," says Martin, adding that this standard appears to be the best, at the moment, for North America. Sauer-Sundstrand, which currently supplies CAN-based systems for paving machinery, takes another approach, according to Dick Heiser, an engineering manager at the company's Electrohydraulics Div. in Minneapolis. l They use their own proprietary protocol, called S-Net. The reason, says Heiser, is that scant information on protocols was available when they began development work, forcing them to develop their own.
Another candidate for a mobile-hydraulics protocol is CAN Kingdom, supported by the CAN Hydraulic Users Group (CANHUG). CAN Kingdom takes a different approach than J1939. The software of each module contains protocol primitives that a system designer can use to build a final protocol. The advantage of CAN Kingdom not being a protocol but a set of protocol primitives, says Lars-Berno Fredriksson, president of Kvaser, is that especially for real-time systems, the system designer can choose the topology and bus-access management best suited for the application. Although CAN is specified as the master protocol, the final protocol can be of another type, for example a logical slotted ring or a token bus, depending on the system designer. CAN Kingdom also allows DeviceNet, SDS, and J1939 nodes on the same network. According to Fredriksson, there is an important difference between the principles behind J1939 and CAN Kingdom. With the latter, a network is tailor-made to the needs of the machine system. With J1939 (as with other conventional protocols such as DeviceNet and SDS), the qualities of the network are given and the machine must be designed according to the requirements of the network. Until the dust settles and a single standard emerges, the variety of available protocols may be a hurdle to systems development as manufacturers follow different courses. "Proprietary CAN systems with proprietary modules are relatively simple to design," says Fredriksson. "Designing systems with modules from different vendors can be difficult, especially if high-speed data handling and fast, error-free machine response is required." As appeared on pages 50-53 in the September 12, 1996
issue of Machine
Design |