This page may meet Wikipedia's criteria for speedy deletion. The given reason is: It is blatant advertising for a company, product, group or service that would require a substantial rewrite in order to become an encyclopedia article. (CSD G11) If this page does not meet the criteria for speedy deletion, or you intend to fix it, please remove this notice, but do not remove this notice from pages that you have created yourself. If you created this page and you disagree with this page's proposed speedy deletion, please explain why on its talk page, after adding: - {{hangon}}
to the top of the article. This will alert administrators to your intention, and may permit you the time to write your explanation. Administrators, remember to check what links here, the page history (last edit), the page log, and any revisions of CSD before deletion.
Maintenance use only: {{subst:spam-notice|pg=Devicenet}} ~~~~ The speedy deletion of this page is contested. The person placing this notice intends to dispute the speedy deletion of this article on its talk page, and requests that this page not be deleted in the meantime. Note that this request is not binding, and the page may still be deleted if it is considered that the page unquestionably meets the speedy deletion criteria, or if the promised explanation is not provided very soon.
Overview
DeviceNet is one of the many industrial protocols based on the CAN (Controller Area Network) technology. It is an open protocol originally developed by Allen-Bradley (now known as Rockwell Automation) in early 90's.
DeviceNet is an application layer protocol based on the CAN protocol, which was originally developed by Bosch for the automotive industries.
DeviceNet is now maintained by the Open DeviceNet Vendors Association (ODVA), which is now working hard to bring DeviceNet, ControlNet, and EtherNet/IP back under the same roof, i.e. called the CIP (Common Industrial Protocol, which was originally knwon as Controls and Information Protocol).
Technical Snapshot DeviceNet protocol was derived from the Allen-Bradley's ControlNet protocol. It is designed specifically to cater for the CAN based network.
DeviceNet adopts the object-oriented algorithm by defining profile for each device, which is known as "device profile". Each device profile contains a minimum of four required objects, namely Identity, Message Router, DeviceNet, and Connection object. Besides, behaviour-related objects, such as digital input point object, were defined to achieve the compatibility, interchangeability, and interoperability of the protocol.
Although it supports peer-to-peer connection, most DeviceNet devices work in the master-slave manner, where the master scanner is usually a PLC or SoftPLC, due to simplicity in design and practical reason.
DeviceNet supports up to 64 nodes per logical network.
DeviceNet supports three baud rates, i.e. 125, 250, and 500 Kbps, which limits the network length to 500, 250, and 100 metres respectively. A not-so newly defined flat cable limits the length to only 75 metres at 500 Kbps.
Object IDs 001. Identity
002. Message router
003. DeviceNet
005. Connection
.. [to be added]
| 
Feeds |
Contact