Embedded Networking with CANopen
By Olaf Pfeiffer
[ Selecting a Protocol | HLP | Overview | Device Profiles | EDS | PDO | NMT | Implementing ]
CANopenIA |
| MyAcademy FREE online training on CAN and CANopen |
| < Previous Page | Next Page > |
Higher Layer CAN protocols
A variety of standardized higher layer protocols are available based on CAN. Today, the most significant ones are DeviceNet and CANopen. DeviceNet was developed for factory automation and is strongest in the arena of material handling. Although it offers a very high level of off-the-shelf plug-and-play product availability, there is a price to pay: DeviceNet does leave only minimal room for customization, optimization and other tweaking of the network. For all applications where customization is desired, CANopen is the better alternative.
CANopen
The basic idea behind CANopen is simple: CANopen standardizes the way the communicated data is structured and exchanged. In addition several Device Profiles for CANopen are standardized and new ones get constantly added. Device Profiles specify the data sets and communication models supported by modules such as Generic I/O, Encoders, Drives, etc. The way the CANopen standards work, it also supports building off-the-shelf modules for plug-and-play system configurations, however it leaves plenty freedom for customizing nodes and communication paths. This allows manufacturers of devices with internal Embedded Networking to take advantage of off-the-shelf components where suitable, and still be able to tweak the system for optimized price/performance of the system to be able to keep a competitive edge.
| < Previous Page | Next Page > |
[ Selecting a Protocol | HLP | Overview | Device Profiles | EDS | PDO | NMT | Implementing ]
Copyright © 2001 Circuit Cellar. All rights reserved.
ESAcademy, 2000
All materials
provided 'as is'
see Disclaimer