Slave network controller DeviceNet™

DeviceNet™ uses CAN (Controller Area Network) for its data link layer and CIP™ (Common Industrial Protocol) for the upperlayers of the network. DeviceNet supports multiple communication hierarchies and message prioritization, and can be configured to operate in a master-slave or a distributed control architecture using peer-to-peer communication to perform actuator process control and feedback data retrieval. The ODVA (Open DeviceNet Vendor Association) registered Limitorque Electronic Data Sheet (EDS) description file is used to configure the actuator parameters for supreme control system performance. DeviceNet Group 2 Server implementation Broad application flexibility via support for multiple communication hierarchies and message prioritization including Master-to-slave communication Standard polled I/O connection, standard bit strobed I/O connection, standard change of state/cyclic I/O connection offered Bus powered network Greater reliability and reduced downtime assured by cyclic redundancy checking (CRC), auto retries, and bus-powered network interface that allows alarm information to be communicated when actuator loses main power Complies with EMC requirements to European Directive 2004/108/EC and vibration/seismic requirements to Machinery Directive 2006/42/EC Network Protocol DeviceNet utilizes the Common Industrial Protocol (CIN) over a Controller Area Network (CAN) defining an application layer which covers a number of actuators Network Service Can be fitted to either MX or QX