DeviceNet

DeviceNet
Name	DeviceNet
Developer	Rockwell Automation; Open DeviceNet Vendors Association
Introduction	1990s
Based on	CAN bus
Application	Industrial automation, sensor/actuator networking
Medium	Twisted pair, fiber optics (extensions)
Topology	Bus, trunk-line drop
Data rate	125 kbps, 250 kbps, 500 kbps
Standard	ODVA specifications

DeviceNet

DeviceNet is an industrial communication network developed for interconnecting Allen-Bradley, Rockwell Automation controllers, sensors, and actuators using a common serial protocol. It provides deterministic, tokenless interaction between field devices and higher-level Programmable Logic Controllers and Distributed Control System components, emphasizing interoperability among vendors and simplified cabling for factory-floor devices. DeviceNet's design leverages the Controller Area Network arbitration and frame structure to meet real-time control requirements in automotive, packaging, and process industries.

Overview

DeviceNet was created to standardize device-level networking between manufacturers such as Allen-Bradley, Siemens, Schneider Electric, Omron, and Mitsubishi Electric while aligning with consortium-led specifications by organizations like the Open DeviceNet Vendors Association and later the ODVA. It targets device classes including programmable logic controller peripheral modules, discrete sensors from companies such as Pepperl+Fuchs, and industrial motor controllers from firms like SEW‑Eurodrive and Baldor Electric Company. DeviceNet uses a master-less peer-to-peer communication model comparable to other fieldbuses, and its market adoption intersected with competing standards like PROFIBUS, Modbus, EtherNet/IP, and Foundation Fieldbus.

Architecture and Protocol

DeviceNet's protocol stack is based on the physical and data-link fundamentals of Controller Area Network with higher-layer services defined by the ODVA. The architecture includes symbolic object models influenced by OSI model layering and implements explicit messaging and I/O messaging paradigms used in interactions with Human–machine interface terminals, supervisory systems from vendors such as Rockwell Automation and Schneider Electric, and asset-management tools like those from Honeywell. DeviceNet employs CAN message identifiers for priority arbitration similarly to implementations by Bosch in automotive systems, and it defines device classes using identity objects analogous to service-oriented descriptions in ISA standards and industrial interoperability efforts by VDE and IEC committees.

Physical Layer and Wiring

DeviceNet specifies a twisted-pair cable with a standardized 5-pin connector popularized in installations by Rockwell Automation and accessory manufacturers such as Hirschmann. The physical layer supports 125 kbps, 250 kbps, and 500 kbps rates with trunk-line/drop-line topologies, terminators at segment ends, and explicit power distribution schemes similar to those in IEC 61158 recommendations. For electrically noisy environments common in plants maintained by John Deere or Caterpillar, DeviceNet installations often incorporate shielded cabling and conduit routing practices recommended by NFPA and industrial safety programs like those from Occupational Safety and Health Administration. Cable assemblies and connectors are manufactured by suppliers such as Phoenix Contact and Weidmüller.

Network Configuration and Devices

DeviceNet networks are composed of nodes including slave I/O modules from Mitsubishi Electric, motor drives from ABB, safety devices from Pilz, and barcode readers from SICK. Configuration tools provided by vendors such as Rockwell Automation's RSLogix and Studio 5000 enable parameterization of identity, connection points, and assembly instances, paralleling configuration practices used with Siemens TIA Portal and Beckhoff engineering environments. Device profiles define object dictionaries similar to those in CANopen and establish common services for diagnostic, heartbeat, and configuration messages; major suppliers maintain conformance labs akin to those run by UL and TÜV Rheinland to validate interoperability. Network management features include node addressing, bit timing settings comparable to ISO CAN calibration procedures, and optional power budgeting for devices like solenoid valves and proximity sensors.

Applications and Industry Use

DeviceNet found extensive use in sectors dominated by companies such as General Motors, Ford Motor Company, Procter & Gamble, and Nestlé where repetitive, high-volume manufacturing favored robust device-level networks. Typical applications include palletizing cells using robots from Fanuc and KUKA, bottle-filling lines employing sensors from Baumer, and conveyor systems integrating drives from Danfoss and SEW‑Eurodrive. DeviceNet's deterministic update behavior and rugged connectors made it popular in warehousing automation by integrators like Dematic and in food-and-beverage plants following hygiene guidelines from European Food Safety Authority. Over time, many installations migrated or hybridized with EtherNet/IP and PROFINET to support higher bandwidth and integration with enterprise systems run by SAP or Oracle.

History and Development

DeviceNet emerged in the early 1990s through collaborative efforts among automation vendors including Allen-Bradley and groups such as the Open DeviceNet Vendors Association, responding to the need for standardized sensor/actuator networking during the rise of programmable controllers. Its technical roots trace to the development of Controller Area Network by Bosch in the 1980s and concurrent fieldbus standardization movements involving IEC and IEEE working groups. Standardization and certification activities were later consolidated under the ODVA, which also stewarded related technologies like EtherNet/IP. Through the 1990s and 2000s, DeviceNet was widely adopted in automotive plants operated by Volkswagen and Toyota, but as industrial Ethernet technologies advanced and companies such as Cisco and Microsoft influenced IT/OT convergence, many vendors shifted emphasis to Ethernet-based protocols while maintaining legacy DeviceNet support for installed bases. Category:Industrial communication protocols