<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="http://can-wiki.info/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="http://can-wiki.info/feed.php">
        <title>CAN Wiki - can_higher_layer_protocols</title>
        <description></description>
        <link>http://can-wiki.info/</link>
        <image rdf:resource="http://can-wiki.info/lib/exe/fetch.php?media=wiki:dokuwiki.svg" />
       <dc:date>2026-04-17T06:03:39+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="http://can-wiki.info/doku.php?id=can_higher_layer_protocols:arinc825&amp;rev=1534885733&amp;do=diff"/>
                <rdf:li rdf:resource="http://can-wiki.info/doku.php?id=can_higher_layer_protocols:canaerospace&amp;rev=1534885734&amp;do=diff"/>
                <rdf:li rdf:resource="http://can-wiki.info/doku.php?id=can_higher_layer_protocols:canmd&amp;rev=1565080436&amp;do=diff"/>
                <rdf:li rdf:resource="http://can-wiki.info/doku.php?id=can_higher_layer_protocols:canopen_faq&amp;rev=1534885734&amp;do=diff"/>
                <rdf:li rdf:resource="http://can-wiki.info/doku.php?id=can_higher_layer_protocols:canopen&amp;rev=1611250689&amp;do=diff"/>
                <rdf:li rdf:resource="http://can-wiki.info/doku.php?id=can_higher_layer_protocols:canopenextendedidusage&amp;rev=1534885734&amp;do=diff"/>
                <rdf:li rdf:resource="http://can-wiki.info/doku.php?id=can_higher_layer_protocols:devicenet&amp;rev=1534885734&amp;do=diff"/>
                <rdf:li rdf:resource="http://can-wiki.info/doku.php?id=can_higher_layer_protocols:duplicate_mac_id&amp;rev=1534885734&amp;do=diff"/>
                <rdf:li rdf:resource="http://can-wiki.info/doku.php?id=can_higher_layer_protocols:energybus&amp;rev=1534885735&amp;do=diff"/>
                <rdf:li rdf:resource="http://can-wiki.info/doku.php?id=can_higher_layer_protocols:iso_bus&amp;rev=1534885735&amp;do=diff"/>
                <rdf:li rdf:resource="http://can-wiki.info/doku.php?id=can_higher_layer_protocols:j1939&amp;rev=1534885735&amp;do=diff"/>
                <rdf:li rdf:resource="http://can-wiki.info/doku.php?id=can_higher_layer_protocols:main&amp;rev=1565080498&amp;do=diff"/>
                <rdf:li rdf:resource="http://can-wiki.info/doku.php?id=can_higher_layer_protocols:mil_can&amp;rev=1534885735&amp;do=diff"/>
                <rdf:li rdf:resource="http://can-wiki.info/doku.php?id=can_higher_layer_protocols:nmea2000&amp;rev=1546173346&amp;do=diff"/>
                <rdf:li rdf:resource="http://can-wiki.info/doku.php?id=can_higher_layer_protocols:sds&amp;rev=1534885736&amp;do=diff"/>
                <rdf:li rdf:resource="http://can-wiki.info/doku.php?id=can_higher_layer_protocols:vscp&amp;rev=1534885736&amp;do=diff"/>
                <rdf:li rdf:resource="http://can-wiki.info/doku.php?id=can_higher_layer_protocols:what_is_wrong_with_rtr&amp;rev=1534885736&amp;do=diff"/>
                <rdf:li rdf:resource="http://can-wiki.info/doku.php?id=can_higher_layer_protocols:xanbus&amp;rev=1601285306&amp;do=diff"/>
                <rdf:li rdf:resource="http://can-wiki.info/doku.php?id=can_higher_layer_protocols:xdd_example&amp;rev=1534885736&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="http://can-wiki.info/lib/exe/fetch.php?media=wiki:dokuwiki.svg">
        <title>CAN Wiki</title>
        <link>http://can-wiki.info/</link>
        <url>http://can-wiki.info/lib/exe/fetch.php?media=wiki:dokuwiki.svg</url>
    </image>
    <item rdf:about="http://can-wiki.info/doku.php?id=can_higher_layer_protocols:arinc825&amp;rev=1534885733&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-08-21T21:08:53+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>arinc825</title>
        <link>http://can-wiki.info/doku.php?id=can_higher_layer_protocols:arinc825&amp;rev=1534885733&amp;do=diff</link>
        <description>ARINC Specification 825 - The General Standardization of CAN for Airborne Use

The protocol is based on CAN Aerospace.

The principles are well described at ARINC_825.
On newer trends CiA informs at “ Increasing use of CAN in aerospace”.</description>
    </item>
    <item rdf:about="http://can-wiki.info/doku.php?id=can_higher_layer_protocols:canaerospace&amp;rev=1534885734&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-08-21T21:08:54+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>canaerospace</title>
        <link>http://can-wiki.info/doku.php?id=can_higher_layer_protocols:canaerospace&amp;rev=1534885734&amp;do=diff</link>
        <description>CAN Aerospace

The CANaerospace protocol, originally developed by Stock Flight Systems in Germany has been standardized by NASA as a next generation general aviation bus within the Advanced General Aviation Experiments (Agate) program in 2001.

	*   CAN Aerospace Home</description>
    </item>
    <item rdf:about="http://can-wiki.info/doku.php?id=can_higher_layer_protocols:canmd&amp;rev=1565080436&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-08-06T08:33:56+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>canmd</title>
        <link>http://can-wiki.info/doku.php?id=can_higher_layer_protocols:canmd&amp;rev=1565080436&amp;do=diff</link>
        <description>What is CAN-MD®?</description>
    </item>
    <item rdf:about="http://can-wiki.info/doku.php?id=can_higher_layer_protocols:canopen_faq&amp;rev=1534885734&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-08-21T21:08:54+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>canopen_faq</title>
        <link>http://can-wiki.info/doku.php?id=can_higher_layer_protocols:canopen_faq&amp;rev=1534885734&amp;do=diff</link>
        <description>Which Standards are available?

CanOpenStandards -- since 2005 they are all available for free, simply download at CiA] Web site.

Current version of the CiA 301 document is 4.2

What is the Electronic Data Sheet EDS

Electronic Data Sheets are used to describe CANopen or</description>
    </item>
    <item rdf:about="http://can-wiki.info/doku.php?id=can_higher_layer_protocols:canopen&amp;rev=1611250689&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2021-01-21T17:38:09+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>canopen</title>
        <link>http://can-wiki.info/doku.php?id=can_higher_layer_protocols:canopen&amp;rev=1611250689&amp;do=diff</link>
        <description>CANopen

CANopen is the internationally standardized (EN 50325-4) CAN-based higher-layer protocol for embedded control systems. The set of CANopen specification comprises the application layer and communication profile as well as application, device, and interface profiles. CANopen provides very flexible configuration capabilities. These specifications are developed and maintained by</description>
    </item>
    <item rdf:about="http://can-wiki.info/doku.php?id=can_higher_layer_protocols:canopenextendedidusage&amp;rev=1534885734&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-08-21T21:08:54+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>canopenextendedidusage</title>
        <link>http://can-wiki.info/doku.php?id=can_higher_layer_protocols:canopenextendedidusage&amp;rev=1534885734&amp;do=diff</link>
        <description>Using 29bit extended IDs for CANopen

The CiA recommendation (and who would ignore CiA recommendations?) is TO NOT use the 29-bit identifiers at all. Also,  there is no specification on how 29-bit IDs could be used.



Use the same numerical Id&#039;s, use 4 bit function code and 7 bit for node Id, and use the full range of 29 bit for PDO only. There are other places in the CANopen protocol where node id must be specified, e.g. the NMT protocol, where only 7-bits are available.</description>
    </item>
    <item rdf:about="http://can-wiki.info/doku.php?id=can_higher_layer_protocols:devicenet&amp;rev=1534885734&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-08-21T21:08:54+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>devicenet</title>
        <link>http://can-wiki.info/doku.php?id=can_higher_layer_protocols:devicenet&amp;rev=1534885734&amp;do=diff</link>
        <description>DeviceNet

DeviceNet is a CAN based Higher Layer Protocol (HLP) managed by the Open DeviceNet Vendor Association ODVA http://www.odva.org

A technical overview is given on the ODVA web site at inline:http://www.odva.org/Home/ODVATECHNOLOGIES/DeviceNet/DeviceNetTechnologyOverview/tabid/72/Default.aspx

Read what CiA is telling us about it inline:http://www.can-cia.org/index.php?id=48&amp;0=

A presentation given by Don Pieronek at the 4th ICC in Berlin</description>
    </item>
    <item rdf:about="http://can-wiki.info/doku.php?id=can_higher_layer_protocols:duplicate_mac_id&amp;rev=1534885734&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-08-21T21:08:54+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>duplicate_mac_id</title>
        <link>http://can-wiki.info/doku.php?id=can_higher_layer_protocols:duplicate_mac_id&amp;rev=1534885734&amp;do=diff</link>
        <description>DeviceNet Duplicate MAC ID Protocol Summary

In the following explanation Dup MAC Request/Response means a Duplicate
MAC ID  Request/Response message at the same MAC ID as the node being described.

Power-up

	*  Transmit Dup MAC request message
	*  Wait 1 second (listening for replies - see 1 below)</description>
    </item>
    <item rdf:about="http://can-wiki.info/doku.php?id=can_higher_layer_protocols:energybus&amp;rev=1534885735&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-08-21T21:08:55+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>energybus</title>
        <link>http://can-wiki.info/doku.php?id=can_higher_layer_protocols:energybus&amp;rev=1534885735&amp;do=diff</link>
        <description>EnergyBus

The EnergyBus standard is created by the EnergyBus e.V. - http://www.energybus.org

A new EnergyBus Booklet (3/2013) gives an overview about the latest EnergyBus standard as well as the listed EnergyBus members. Questions about common service on electric bikes are answered.

Partners are the CAN in Automation e.V. -</description>
    </item>
    <item rdf:about="http://can-wiki.info/doku.php?id=can_higher_layer_protocols:iso_bus&amp;rev=1534885735&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-08-21T21:08:55+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>iso_bus</title>
        <link>http://can-wiki.info/doku.php?id=can_higher_layer_protocols:iso_bus&amp;rev=1534885735&amp;do=diff</link>
        <description>ISO 11783 (or ISO Bus or ISOBUS) is a communication protocol for the agriculture industry based on the SAE J1939 protocol (which includes CANbus) . Wikipedia.</description>
    </item>
    <item rdf:about="http://can-wiki.info/doku.php?id=can_higher_layer_protocols:j1939&amp;rev=1534885735&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-08-21T21:08:55+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>j1939</title>
        <link>http://can-wiki.info/doku.php?id=can_higher_layer_protocols:j1939&amp;rev=1534885735&amp;do=diff</link>
        <description>J1939 / ISObus

A general description can be found on Wikipedia J1939. All Standards are available at the  Society of Automotive Engineers SAE  store.

	*  A Comprehensible Guide to J1939 (Englisch, 128 pages, 2008), Wilfried Voss, ISBN-13: 978-0976511632
	*   J1939 Introduction by Kvaser</description>
    </item>
    <item rdf:about="http://can-wiki.info/doku.php?id=can_higher_layer_protocols:main&amp;rev=1565080498&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-08-06T08:34:58+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>main</title>
        <link>http://can-wiki.info/doku.php?id=can_higher_layer_protocols:main&amp;rev=1565080498&amp;do=diff</link>
        <description>CAN Higher Layer Protocols

This page summarizes all other higher layer protocols using CAN. 

If no other information are worth to be collected here the links are going directly to other web sites.

	*   ARINC 825
		*   CAN Aerospace
		*   CAN-MD® proprietary protocol for sensor applications by</description>
    </item>
    <item rdf:about="http://can-wiki.info/doku.php?id=can_higher_layer_protocols:mil_can&amp;rev=1534885735&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-08-21T21:08:55+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>mil_can</title>
        <link>http://can-wiki.info/doku.php?id=can_higher_layer_protocols:mil_can&amp;rev=1534885735&amp;do=diff</link>
        <description>Standard for the implementation of CANbus within the military vehicles community.

More information on  MilCAN.org</description>
    </item>
    <item rdf:about="http://can-wiki.info/doku.php?id=can_higher_layer_protocols:nmea2000&amp;rev=1546173346&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-12-30T12:35:46+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>nmea2000</title>
        <link>http://can-wiki.info/doku.php?id=can_higher_layer_protocols:nmea2000&amp;rev=1546173346&amp;do=diff</link>
        <description>NMEA 2000

NMEA 2000 is a communication protocol based upon the SaeJ1939 Controller Area Network standard from the  National Marine Electronics Association to interconnect various electronic units onboard ships and smaller recreational and commercial vessels.

NMEA 2000

The development of this  standard began in 1994. It was released in 2001
The standard  NMEA 2000(R) is a low-cost serial data network operating at 250 kbits/s based on CAN substituting NMEA0183.</description>
    </item>
    <item rdf:about="http://can-wiki.info/doku.php?id=can_higher_layer_protocols:sds&amp;rev=1534885736&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-08-21T21:08:56+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>sds</title>
        <link>http://can-wiki.info/doku.php?id=can_higher_layer_protocols:sds&amp;rev=1534885736&amp;do=diff</link>
        <description>Smart Distributed System (SDS)

One of the early CAN protocols for intelligent sensors and actuators, developed by  Honeywell.</description>
    </item>
    <item rdf:about="http://can-wiki.info/doku.php?id=can_higher_layer_protocols:vscp&amp;rev=1534885736&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-08-21T21:08:56+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>vscp</title>
        <link>http://can-wiki.info/doku.php?id=can_higher_layer_protocols:vscp&amp;rev=1534885736&amp;do=diff</link>
        <description>Very Simple Control Protocol

VSCP - the Very Simple Control protocol is what the name implies a very simple protocol for control and automation. VSCP uses CAN as it least common denominator but work also over other lower level protocols such as TCP/IP.</description>
    </item>
    <item rdf:about="http://can-wiki.info/doku.php?id=can_higher_layer_protocols:what_is_wrong_with_rtr&amp;rev=1534885736&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-08-21T21:08:56+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>what_is_wrong_with_rtr</title>
        <link>http://can-wiki.info/doku.php?id=can_higher_layer_protocols:what_is_wrong_with_rtr&amp;rev=1534885736&amp;do=diff</link>
        <description>Why using RTRs is not advised in CANopen?

RTR means Remote Transmission Request - a CAN frame requesting another node to send a requested frame.

CiA, especially the Special Interest Group CANopen is not recommending using RTR Messages. You may ask: why?</description>
    </item>
    <item rdf:about="http://can-wiki.info/doku.php?id=can_higher_layer_protocols:xanbus&amp;rev=1601285306&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2020-09-28T09:28:26+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>xanbus</title>
        <link>http://can-wiki.info/doku.php?id=can_higher_layer_protocols:xanbus&amp;rev=1601285306&amp;do=diff</link>
        <description>Xanbus

Xanbus is a proprietary CAN based protocol developed by  Xantrex.
The protocol is based on  J1939 with inverter specific PGNs which are unique to 
Xantrex products. These PGNs are only available to qualified Xantrex customers.

Xanbus is a  Schneider Electric SA  trademark.

 Xanbus System Installation Guide</description>
    </item>
    <item rdf:about="http://can-wiki.info/doku.php?id=can_higher_layer_protocols:xdd_example&amp;rev=1534885736&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-08-21T21:08:56+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>xdd_example</title>
        <link>http://can-wiki.info/doku.php?id=can_higher_layer_protocols:xdd_example&amp;rev=1534885736&amp;do=diff</link>
        <description>The XML Device Description Files (XDD) are the next generation of the CANopen EDS files.

The following example shows a way to a value structure description for a UNSIGNED32 value:

At first we have to define a PDO_COB_TYPE data type in dataTypeList.</description>
    </item>
</rdf:RDF>
