FAQs on DeviceNet

Technical Questions 1.

What is DeviceNet?
A low-cost communications network used to link control devices within a network An open network standard allowing any company to develop DeviceNet devices without paying royalties A byte level bus system with open protocol and specifications A simple, networking solution to reduce wiring costs, installation time, and downtime DeviceNet technology allows for simple devices to interchange while allowing complex devices to interconnect DeviceNet systems can read a motor starters load current, change the drives deceleration rate, and adjust sensitivity of sensors, among other capabilities

2.

What are the advantages of using DeviceNet?

Open protocol Open chip set Very broad product range Having many product vendors leads to more competition, lower prices, and a higher quality product Open DeviceNet Vendor Association (see ODVA section) DeviceNet is optimized for machine control The perfect balance between network speed and data throughput Operates in real-time and is deterministic while responsive to data acquisition requirements Intelligent devices run on the network They provide diagnostic feedback to the control system The device features lead to a decrease in downtime and production costs DeviceNet allows for devices to be changed without powering down the system DeviceNet has analog capabilities

3.

How does DeviceNet differ from non-CAN based buses?

Only bus with truly open protocol, all others have one or more aspects closed, such as who controls the specifications CAN error checking capabilities are the industries best: CRC, automatic retries, acknowledgments, and data link error detection DeviceNet offers multiple control interfaces, PLC, iPC, DCS and others, which give customers the best product for their control needs The DeviceNet communication protocol features Peer-to-peer data exchange where DeviceNet devices produce and consume messages Master/slave operation is a subset of peer-to-peer Devices may behave as the client or server or both A DeviceNet network has a maximum of 64 nodes (MAC IDs) which support 4096 I/O and an unlimited number of I/O with fragmentation DeviceNet vendor support is very strong

4.

Why buy DeviceNet?

Best price to performance ratio of the buses Being able to swap devices while the network is powered results in no downtime for device repair and replacement Inexpensive CAN chips- currently 15 chip manufacturers ODVA Only truly open network It is designed around peer-to-peer and change of state Advanced diagnostics

5.

Why buy Cutler-Hammer DeviceNet?

Components are our core business Cutler-Hammer does not have existing systems to protect in the automation market Cutler-Hammer provides native DeviceNet devices and adapters for concentration of devices to DeviceNet.

6.

What are the core benefits of a DeviceNet system?

Cost savings Installation costs (installation time, programming time, debug time, and hardware) drop 40 percent Set up and commissioning time decreases dramatically resulting in big savings Because of the dramatic decrease in downtime and the enhanced functionality of the intelligent devices, productivity increases and life cycle cost savings go down 30 to 40 percent Reduced component costs Reduced wiring time Reduced start up time Reduced debug time Reduced field installation time Reduced panel (floor) space Enhanced diagnostics Reduced downtime Plug and play interoperability Vendor interchangeability Reduced panel (floor) space Reduced overall system cost Easy expansion

7.

What is CAN (Controller Area Network)?

Bosch developed the CAN chip for the automotive industry to replace wire harnessing in 1987 CAN technology reduces expensive wiring in control systems Ideal for control with its high speed, real-time, and low cost features CAN operates at the data link layer, layer 2, in the ISO/OSI standard Error free message delivery to all stations with detection and retry High reliability in harsh environments System collapse from overload is not possible with CAN Non-destructive Bit-wise Arbitration

8.

What is Non-destructive Bit-wise Arbitration?

A highly effective data collision avoidance method It allows for maximum data throughput because with data collisions, one message always gets through while the second backs off and waits This ensures no bus memory is used without transmitting useful information All outstanding transmission requests are processed in the order of their importance to the overall system

9.

How does CAN operate?

It allows any bus device to broadcast a message packet over the bus A maximum 8 data bytes transmitted per message, fragmentation is possible Each nodes unique 11-bit identifier defines the message priority rating The identifier with the lowest binary number has the highest priority Content-oriented addressing scheme The priority rating resolves conflicts when more than one device simultaneously initiates a message All network devices receive messages, and based on their priority rating, determine whether or not to act on the information

10. What are the strongest CAN advantages?

Proven technology Used in various markets for the last several years Has a high bit rate and excellent ability to detect errors Its noise immunity makes it highly reliable, and it is highly durable because it is shock, vibration, and heat resistant Simple wiring scheme allows easy installation and reduction in costs Consumer and commercial demand drive costs down; over 10 million chips were shipped in 1996 Low cost technology keeps system cost down Tremendous vendor support

11. What is ODVA?

Open DeviceNet Vendor Association An independent, non-profit corporation comprised of hardware and software companies who make products, development tools, or provide services for DeviceNet 170 members as of July 1997 ODVA publishes a DeviceNet product catalog three times a year Three membership levels open to all interested companies Executive sits on both the Board of Directors and the Technical Review Board Regular 2 elected representatives sit on the Technical Review Board Associate can not sit on either board, but as all members can, they can participate in SIGs Special Interest Groups (SIGs) and the Technical Review Board control DeviceNet specifications

12. Who started DeviceNet and ODVA?

ODVA began when the specifications were transferred to them in April 1995 ODVA was founded by Allen-Bradley, Cutler-Hammer, OMRON and Hitachi ODVA has always been a vendor association Allen-Bradley played an integral role in DeviceNet, but many companies, such as Cutler-Hammer, have advanced, and continue to improve, DeviceNet technology

13. Why are all these vendors (competitors) working together?

The vendors believe when DeviceNet becomes a dominant worldwide standard, they will have fewer costs by supporting fewer networks Vendors know DeviceNet lowers system installation costs which drives demand up, and the vendors win because they sell more products

14. What products and services does ODVA offer?

ODVA provides DeviceNet product conformance testing (see conformance testing question) Product Catalog contains many pages of products and services Cabling components Controllers I/O blocks Developers tools Motor controls Network configuration software PC-based control software Pneumatic valves Training See the ODVA Product Catalog for many other available products

15. If I buy a DeviceNet system today will it work with the products I buy 1-3 years from now? in 5-10 years?
ABSOLUTELY YES Any single member can veto a specification enhancement which is not backward compatible The ONLY way to obsolete or orphan a DeviceNet product is for all ODVA members to agree

16. What is an open network?

The term open is used subjectively to describe each automation system An open network is one with all specs, protocol, and hardware open for vendors to contribute to; also, an open network has no license fee Nearly all networks are closed in at least one way, whether one part of the protocol or specs are controlled or products, mainly chips, are only available from one vendor

17. Is DeviceNet a truly open network?

Yes. DeviceNet is an open, licensed protocol Fifteen manufacturers produce the CAN chip Open protocol and hardware No license fee DeviceNet specifications and updates are available for a nominal fee Conformance testing available for a minimal cost

18. How does DeviceNet licensing work?

When you purchase DeviceNet specifications, you may use them to design and manufacture products. This gives you licensing rights, but all products must abide by DeviceNet specs.

19. Where can I get the DeviceNet specifications?

The specifications can be purchased from ODVA for $250. The DeviceNet protocol specifications are described in a 2 volume, 1,000 page document or in a CD-ROM version.

20. Where can I get additional information?

Locate ODVA on the World Wide Web at www.odva.org or reach ODVA by telephone at 1-954-340-5412. Cutler-Hammers DeviceNet information is located on the Web at www.cutlerhammer.eaton.com and by phone at 1-800-231-1145

21. What is conformance testing?

Conformance testing ensures DeviceNet product interchangeability ODVA has developed conformance test software package to assist product developers in meeting these requirements. ODVA has also set up independent test labs in three locations to verify DeviceNet product conformance: University of Michigan, University of Warwick in Coventry England, ASTEM RI in Kyoto, Japan. Testing products at ODVA test labs provides a strong sense of security for the users Products may be pretested before being sent to the testing site ODVA publishes a list of products which passed the tests. Today, however, the notice is in the product literature and not on the product itself. ODVA does not have to test the products 10 recommended conformance testing steps Purchase conformance testing software from ODVA Attend conformance testing training Test device in-house Create the conformance test software input file Complete the independent conformance test request form Deliver device for testing Conformance testing Distribute results Publish results (ODVA) Company advertises successful test completion

22. What DeviceNet products are offered?

Bar code R/F, ID systems Cabling components Interface card Controllers Software Developer training Developer tools User training Operator interface I/O blocks Industrial PCs Drives Starters Pneumatic valves Sensors Motion Control Programmable Logic Controllers

23. What are DeviceNets primary industries and applications in these industries?
Automotive Conveyors Test machinery Transfer lines Paint lines Assembly automation Material handling Conveyor systems Palletizers Stacking cranes Packaging Conveyors Machine and tool Mills Drills Transfer lines Turning centers Stamping presses Machining centers Food and beverage

24. Who are/will be DeviceNets biggest or most typical users?

Automotive plants Food processing Packaging Warehousing and distribution centers Pharmaceuticals Integrated circuit fabrication

25. What topologies does DeviceNet use?

DeviceNet uses the trunk and branch topology.

26. What is the effect on the bus system when the number of I/O expands from 64 nodes?
There is no measurable change when expanding the bus size.

27. Does DeviceNet continue to operate during network failure?

DeviceNet may continue to function, but it will not operate The controller puts the system in a user determined state and continues once the problem has been fixed The I/O can be fixed while the system is running

28. How does the bus length relate to the data transfer rate?
As the bus length increases, the data transfer rate must decrease, and visa versa. At 1640 ft (500 m), DeviceNet operates at 125 Kbaud At 820 ft (250 m), 250 Kbaud At 328 ft (100 m), 500 Kbaud

29. What physical media is used?

Two shielded twisted pairs of wire, one for data communication and one pair for power Predetermined cable drop points allow for the easy wiring connections Node removal without powering down or severing trunk cable Adjustable power configurations

30. What diagnostics does DeviceNet support?

Network level diagnostics: communication errors, lost messages, buffer overruns, transmittal errors, incorrect connection, and more At this level the diagnostics tell what happened, whether a node went down or a wire is not working Device level diagnostics are in the device itself At this level diagnostics answer questions such as whether or not the device works or if it needs maintenance

31. What is the difference between DeviceNet protocol and DeviceNet network?
DeviceNet protocol The application layer (protocol) for the CAN chip technology network Protocol refers to the "language" spoken over the network Protocol deals with aspects such as message length and composition DeviceNet network A combination of protocol and the electrical and physical media requirements The network standard defines aspects such as the voltage levels of the bus, the maximum run lengths for the cables, cable size, and electrical requirements

32. Does DeviceNet incorporate network management?

The scanner cards monitor network actions When using an iPC interface, the iPC controls the network

33. What are the CAN error checking capabilities?

Below are five errors CAN technology detects in networks. CRC (Cyclic Redundancy Check) errors occur when the CRC 16-bit value, recalculated by the receiving node, does not match the transmitted value An acknowledgment error happens when the transmitting node does not detect a dominant bit value in the Ack Slot (Acknowledgment Slot) A form error results from an invalid bit value being detected in a predefined value area Bit errors occur when a transmitting node compares the bus level with the level it transmitted and the two are not equal Stuff errors happen when a node detects six consecutive bit values

34. How does DeviceNet define messaging?

Message ID identifies a message within a message group Source MAC ID is where the transmitting node puts its assigned MAC ID Destination MAC ID is the receiving nodes MAC ID Message groups Provide a communication system where access to transmission time is distributed Allows the user to prioritize message types Design a system which takes into account CANs limited filtering capabilities I/O messages are composed of connection IDs and associated data The meaning of the I/O message is implied by the associated connection ID The consuming application is assumed to have knowledge of the intended I/O message use Explicit messaging uses the CAN data field frame to carry DeviceNet information

35. What is explicit messaging, and do Cutler-Hammer devices support it?

Explicit messaging uses the CAN frame data field to carry DeviceNet defined information The explicit message data field includes: Message header Entire message body When the explicit message is greater than 8 bytes, it must transfer to a fragmented message which includes: Message header Fragmentation protocol Message body fragment Explicit messaging is part of DeviceNet Messaging Protocol, therefore, Cutler-Hammer devices support it

36. What is Polled I/O?

Poll messages transfer any amount of I/O data between a master and its Polled slaves. The Poll Command is an I/O message the master transmits Messages are point-to-point, meaning the command is directed to a specific slave Master must send a command to each slave to be polled The Poll Response is an I/O message the slave transmits to the master when the command has been received

37. What is Change of State I/O?

Change of State messages move any amount of I/O data between a master and slave using cyclic production triggers. Data production can be acknowledged or unacknowledged. Both the master and slave can transmit change of state messages The message is directed towards a specific node, therefore it operates in point-to-point The acknowledge message is the response to the change of state message

38. What is Bit-Strobe I/O?

Bit-Strobe messages rapidly transfer small amounts of I/O data between a master and its Bit-Strobed slaves. The Bit-Strobe Command is an I/O message the master transmits Messages have multi-cast capabilities which means multiple slaves can receive and react to the same Bit-Strobe Command The Bit-Strobe Response is an I/O message the slaves transmit back to the master after receiving the Command