Industrial Networking
 

DeviceNet Introduction
 

DeviceNet™ Unplugged
A View “Under the Hood” for End Users
Page 1 of 21 | « previous page | next page » | last page

SYNOPSIS
This paper presents an operational description of DeviceNet™, a low-level industrial application layer protocol for industrial automation applications. DeviceNet connects simple industrial devices (sensors and actuators) with higher-level devices such as Programmable Controllers. Built on the standard CAN (Controller Area Network) physical communications standard DeviceNet uses CAN hardware to define an application layer protocol that structures the task of configuring, accessing and controlling industrial automation devices.

This paper is intended for the DeviceNet user who desires a deeper understanding of DeviceNet. It is intended to provide much more information than is typically found in a DeviceNet network overview but much less than the several hundred page DeviceNet specification. This paper can also provide a starting point for developers considering adding DeviceNet communications to their product.*

Note that an abstract of a 200+ page specification is by definition incomplete. Some aspects of the technology are admittedly only lightly covered while others are not covered at all. Topics judged to provide the most insight into DeviceNet operation or clear up common misconceptions received priority.
 
DEVICENET - A QUICK OVERVIEW
DeviceNet is an application layer protocol. What does that mean? One way to look at it is that the term “Application Layer” implies that DeviceNet deals more with application data than a lower level or non-application layer protocol. For example, a link layer protocol is designed simply to move some bytes from point A to point B. It has no interest and conveys no inherent information regarding the contents of the message. Because DeviceNet is an application layer protocol its messages do convey information. A DeviceNet explicit message has specific information in specific bytes of a message. There is a byte for a Class number, a byte for a service code and so on.

Now, if DeviceNet is an application layer protocol, what are the lower protocol layers that transport it’s messages? That’s the content of the next section.

Solutions:

» Altivar 31 DeviceNet Slave
» Instant DeviceNet chip
» Custom Solutions
» DeviceNet Master DLL
» ASCII to DeviceNet Gateway
» DeviceNet Valve Control
» DeviceNet Embedded Gateway
» DeviceNet Serial Gateway
» DeviceNet NetBurner
» DeviceNet Flow Control
» DeviceNet Slave Source Code
» DeviceNet Master
» NetSilicon DeviceNet Master
» NetSilicon DeviceNet Slave
  
 

* Developers should also see the reference section where additional information on developing DeviceNet products is identified.
 

More Information
     
  » I need to DeviceNet-enable
My Product
  » I have a Networking Question
  » I want this file in PDF Format
  » I need to Find a DeviceNet Product
     
For Your Immediate Needs Call:

John Rinaldi
Networking Project Manager
1-800-249-1612
1-414-453-5100
     
RTA, Inc. - The Industrial Networking Home for DeviceNet, EtherNet/IP, Ethernet Drive,
Modbus, PROFInet CBA, PROFInet IO and other networks.

(c) 2007 Real Time Automation, Inc. - Networking in 30 Days or Less

www.industrialethernetsolutions.com
Page 1 of 21 | « previous page | next page » | last page
top of page
 
By John Rinaldi
Real Time Automation, Inc.
2825 N. Mayfair Rd. Suite 11
Wauwatosa WI 53222
(414) 453-5100 (V)
(414) 453-5125 (F)
www.rtaautomation.com
© Real Time Auomation, Inc. All Rights Reserved. | http://www.rtaautomation.com