Allen Bradley 1761-NET-DNI DeviceNet Interface NEW

Contact: Miya

Job Title: Sales Manager

Skype: live:miyazheng520

Email: sales@amikon.cn

Tel: 86-18020776792(Whats App )

QQ :2851195450

Brand Name                 AB

Product reference      1761-NET-DNI

The 1761-NET-DNI DeviceNet Unit by Allen-Bradley is a DeviceNet interface that provides peer-to-peer messaging communication. The DeviceNet 1761-NET-DNI interface is a standalone, DIN-rail or panel mounted, intelligent DeviceNet-to-DF1 protocol-conversion device that allows existing DF1 devices communicate on a DeviceNet network.

This DF1 device receives enclosed DF1 messages from a DeviceNet unit and it also exchanges I/O data with the master device.  
The 1761-NET-DNI has various features. The most crucial of these are the explicit messaging features and the ability to program other machines through a DeviceNet I/O.
For safety precautions, this unit needs to be mounted in an enclosure when operated. It can be mounted in a horizontal or a vertical position. The 1761-NET-DNI is flexible and needs no spacing except as necessary for DIN rail latch movement. 
This unit is equipped with a single DeviceNet connection point with a single RS-232 port. Both these ports are isolated from each other. The 1761-NET-DNI requires a power source of 24V DC to operate and it needs an operating temperature of 32-140 degrees Fahrenheit to function effectively. 
The main functions of the 1761-NET-DNI are to collect and receive the data from the connected DF1 device and then to send it to the Master unit connected to the DeviceNet network. The 1761-NET-DNI monitors the output data acquired from the master connection and it allows sending and receiving messages across the DeviceNet network. 

The capabilities of each individual device determine what level of messaging is supported. The types of messaging supported are: • I/O Assembly Messaging (DNI responds) • PCCC encapsulated DeviceNet Messaging (peer-to-peer) • Explicit Assembly Messaging (DNI initiates, DNI Series B Only) See Explicit Messaging (DNI Series B Only) on page 77 for more information. I/O Assembly Messaging Two conditions must be met to access the I/O assemblies. • Data Enable (DNI Series A) or I/O Scan Enable (DNI Series B) must be enabled. • The DF1 Device must be servicing the Heartbeat. See DF1 Heartbeat on page 43 for information on using the Heartbeat. The following sections describe additional conditions based on the DNI Series. DNI Series A DNI Series A supports explicit messaging to the master I/O assemblies over DeviceNet at a minimal level. If the DNI is not owned by a DeviceNet master, the DNI responds to explicit messaging gets and accepts explicit messaging sets to the master I/O assembly. If the DNI is owned by a DeviceNet master, it responds to gets, but cannot accept sets. In either case, the data size must be 16 words, even if the I/O size is smaller. See page 65 to address DNI Series A assemblies. DNI Series B DNI Series B provides the above described functionality, except the data size is equal to the configured I/O size. Additionally, DNI Series B can respond to explicit messages over DeviceNet to its explicit I/O assemblies whether it is owned by a DeviceNet master or not. See page 66 to address DNI Series B assemblies. DNI Series B can also perform get/set services with its new DeviceNet messaging capability. See page 77 for Explicit Messaging (DNI Series B Only).

Programmable Controller Communications Commands (PCCC) DeviceNet Messaging/ DF1 (peer-to-peer) Allen-Bradley controllers with RS-232 ports communicate via PCCC messaging. The DNI encapsulates the PCCC messages to allow PCCC messaging to operate over DeviceNet. This is an open, non-proprietary protocol that can be implemented by anyone who needs to exchange information with an Allen-Bradley controller. The DNI is capable of receiving the DF1 protocol, and sending or receiving it over DeviceNet. This enables any existing Allen-Bradley device that is capable of DF1 communications to an Allen-Bradley controller to use the DNI to communicate over DeviceNet. For DNI Series A, the only stipulation is that the device has to be capable of entering a destination node address (For DNI Series B, this stipulation has been removed with the addition of the DF1 Substitute Address parameter.). The DNI uses the DF1 destination node address that is embedded in the DF1 packet to determine where on DeviceNet it needs to send the information. This DF1-to-DeviceNet capability lets you configure a peer-to-peer network. By programming standard ladder logic message instructions, with the destination address the same as the destination DNI (when not using DNI Series B address substitution), the message is routed across DeviceNet by the DNI. The following diagram illustrates the types of messaging

Local Access to a DeviceNet Network PCCC/DF1 messaging allows programming devices to connect to a DeviceNet network, and upload/download/monitor and even edit programs if the controller attached to the destination DNI supports that functionality. Rockwell Software RSLogix 500/RSLinx (version 2 and higher) users can connect directly to the DeviceNet network using a KFD, PCD, or PCI interface

OTHER RECOMMENDATION

Our Advantages:

If you have any question pls do not hesitate to contact us.We can supply all kind of the automation parts,if you want to purchase parts pls send the parts model to my mail, I will prompt reply you as I receive the mail.Hope anyone inquire from us.    Waiting for your inquiry.