<?xml version="1.0" encoding="UTF-8"?><xml><records><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">M. Farsi</style></author><author><style face="normal" font="default" size="100%">K. Ratcliff</style></author><author><style face="normal" font="default" size="100%">Manuel Bernardo Barbosa</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">An introduction to CANopen</style></title><secondary-title><style face="normal" font="default" size="100%">Computing &amp; Control Engineering Journal</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">1999</style></year></dates><number><style face="normal" font="default" size="100%">4</style></number><publisher><style face="normal" font="default" size="100%">IEE</style></publisher><volume><style face="normal" font="default" size="100%">10</style></volume><pages><style face="normal" font="default" size="100%">161-168</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">&lt;p&gt;CANopen is a truly open protocol that has not been developed by one company alone. Several working groups, consisting of many different device manufacturers and end-users, have co-operated to produce the CANopen standards, now under the supervision of the CAN in Automation organisation. CANopen has been produced as a result of EU funding. This article gives an overview of some of the fundamental concepts of CANopen communication and of CANopen implementation.&lt;/p&gt;
</style></abstract><issue><style face="normal" font="default" size="100%">4</style></issue></record></records></xml>