News Center

What is the difference between CAN and DeviceNet?

The CAN specification provides a robust communication channel with built-in error detection and limiting. DeviceNet uses the CAN standard as the basis for higher-level communication protocols. DeviceNet is often referred to as the CAN application layer protocol. The main goal of the DeviceNet specification is to allow interconnection and interchange between DeviceNet devices from different vendors. To achieve this goal, DeviceNet defines the following:



CAN Physical Layer - Defines a single standard for CAN physical connections. The standard used is High Speed CAN (ISO 11898-2). The specification also includes bus supply voltage, number of devices that can be connected, allowed connector types, cable length and baud rate.



CAN Data Link Layer - Specification remains unchanged. Standard CAN controllers such as the Intel 82527 can be used with DeviceNet devices.



Application Layer - The main contribution of the DeviceNet specification is the way data is organized and transferred between devices. DeviceNet specifies the object model that the device needs to implement. This way, all devices provide a consistent interface to the rest of the network, hiding the internal details of the device.



On the application programming side, developers writing applications using NI-XNET will be manipulating frames and will need detailed knowledge of other devices on the network to be able to address them using quorum IDs. This is sufficient for small "closed" networks, such as automotive networks, where the main goal is a fast and extremely reliable communication network.



The DeviceNet specification provides a way to detect devices on a network and route messages from one node to another. In this case, the DeviceNet driver is able to communicate with any DeviceNet-compliant device. This allows functionally identical devices from different vendors to be interchangeable.



Premier Cable offers many combinations of molded cables, field wired connectors, and panel mount receptacles, and DeviceNet accessories to meet your specific requirements.



Passive distribution box with M12 I/O 8-way

DeviceNet T Connector 2 Port

DeviceNet CANopen data network Sensor Junction Blocks

Junction box for CAN-bus system

Related News

What is a terminal block used for?

While there are many factors to consider when designing an overall system, terminal blocks are an optimal solution for complex electrical system connections. With a variety of color options and configurations, Premier Cable’ terminal blocks offer a range of options to meet your design challenges.

CANBus Applications

CAN-bus has been widely used in various automation control systems. For example, CAN-bus has incomparable advantages in various fields such as automotive electronics, automatic control, smart buildings, power systems, and security monitoring.

Introduction to M12 connector pin coding

M12 encoding types are A encoding, B encoding, D encoding and X encoding. A-code, B-code and X-code are some of the earliest developed and longest-available M12 connectors. The latest M12 coding types currently under development are K coding for AC and L coding for PROFINET DC.

Cables – What are the correct cable sizes for an NMEA 2000 network?

The three different sizes of NMEA 2000 certified DeviceNet standard cabling are "micro," "mid," and "mini."

What are the advantages of NMEA 2000?

The Premier Cable Starter Kits provide everything you need to get to create a basic NMEA 2000 network from scratch.

The role of DeviceNet terminal resistor

DeviceNet_network is a fieldbus network protocol based on Controller Area Network (CAN). In the DeviceNet network, the terminal resistor plays the role of compensation and protection for signal transmission. The function of the terminal resistor is to eliminate signal reflection and interference and ensure the signal transmission quality.