The most significant improvements in ontrol systems may be achieved by using the modern concepts.
This paper briefly introduces the standardized CANopen system management process, which makes the CANopen systems easier to be managed than the traditional systems based on the discrete I/O. The main benefits of the management process can be seen in the improved serviceability – faster troubleshooting times and unified configuration and application SW download procedure. The same improvements can be seen also in the system assembly, because the tasks are same. The only difference is that in the assembly line the assembly order can be optimized. The use of intelligent sensors and actuators significantly improves not only the control performance but also the performance of design and maintenance of the control systems. The use of standardized interfaces especially improves the efficiency of the control system service, maintenance and generation changes. Therefore, possibly higher components prices should be understood rather as investments than additional costs.
This article shows hands-on case examples how the presented system integration challenges can be solved with standard CANopen devices according to device profiles for general-purpose I/O-devices (CiA-401) and hydraulic drives (CiA-408). The main conclusion is that commitment to CANopen actually enables not only the required approaches, but also manufacturer and device independence with large number of interchangeable devices. Another significant result is that the lowest level applications can be implemented just by integrating standardized devices, without application software project.
In this article, we present a new method for describing CANopen network topology. A new format using GraphML, an XML-based graph format, is introduced. By using a subset of GraphML along with CANopen-specific new elements and attributes, topology of single as well as multiple CANopen networks can be captured in a well established graph format with existing tool support. The new format is specified in a manner that allows CANopen design applications to adopt it while providing a mechanism for fallback in unsupported software. Methods for extending the format to contain other CAN- and CANopen-specific data as well as transforming the GraphMLbased network structure to other formats are described. Finally, the implications of the introduced method and format are discussed.
Ask more information
By sending the form below, we will contact you.
Tilaa Cloudfield uutiskirje ja saat ensimmäisenä tietoa uusista tuulistamme! Lähetämme muutaman uutiskirjeen vuodessa.