Device Bridging...
Your ZIP file won't open...for me?
However, you should have more than one DNT network file here...
This type of configuration for distributed I/O uses what is known as Device Bridging where the main DeviceNet scanner determines the I/O size for any adapter nodes in its scanlist by Bridging the two required DNT network files...
You should have a DNT network file for the 1769-ADN distributed I/O network where you add your module as a node to the network under the 1769-ADN and then add it to the 1769-ADN's scanlist, mapping it's I/O data. You then download the updated scanlist into the 1769-ADN adapter. This DNT network file will just have the 1769-ADN and any nodes that are in its scanlist. The 1769-SDN is not present here. This is known as an "internal" network where the adapter is communicating with its I/O modules. Internal DeviceNet networks may also be referred to as "Subnets".
Then you should have a main DNT network file where you have the 1769-SDN scanner and all the nodes within its scanlist and their mapped data. This file will just have, among other nodes, your 1769-ADN adapter and will not contain the 1769-ADN's scanlist nodes. This is known as an "external" network where the scanner is communicating with higher level nodes i.e. adapters, drives, etc.
The internal network file should be linked to the external network file using Device Bridging. This is done in the external network file under the properties for the 1769-ADN adapter.
For the 1769-ADN properties in the external network file you select the "Device Bridging" tab and associate the internal network file. Reading this file tells the 1769-SDN what I/O size the adapter is configured for and populates its I/O size parameters automatically. This is then downloaded to the 1769-SDN scanner.
This Device Bridging should already have been done from the original configuration. But it does not automatically update itself...
If you have successfully added the input module to the 1769-ADN scanlist, and have downloaded the new scanlist into the adapter, and have saved the internal network file (DNT), then the 1769-SDN scanner's scanlist will have to be updated in the external network file to reflect the changes within the internal network file i.e. the 1769-ADN's new I/O size.
To update the 1769-ADN I/O size in the 1769-SDN scanner's scanlist in the external network file, you need to refresh the information that it reads from the internal network file via Device Bridging. To do this you open the properties for the 1769-SDN scanner and go to the "Scanlist" tab. Here you select the 1769-ADN adapter instance in the list and hit the "Edit I/O Parameters" button at the bottom (or double-click on the 1769-ADN). Here you should see the current I/O size in bytes for the 1769-ADN. Hit the "Restore I/O Sizes" button at the bottom and the new I/O size will be read in from the updated internal network file. You should now see the I/O size parameters updated.
Once the 1769-SDN scanner has updated the I/O size for the 1769-ADN adapter in the external network file, this must be downloaded into the 1769-SDN scanner before the new module's data can reach the backplane i.e. controller.
This is an offline update first in the external network file, by hitting the "Restore I/O Sizes" button, followed by a download of the new scanlist into the 1769-SDN scanner.
All of that can be done when you already have the DNT files I've mentioned. If you do not have them, or do not have one of them, then you must go Online to the network to Upload the actual configuration and then save it as a DNT file. This can entail uploading from both the external network level and the internal network level and saving the two separate DNT files.
For adding the new module, if you have the internal network file you can Offline add it to the internal network by selecting it from the Hardware Catalog. Then you add it to the adapter's scanlist and then go Online and download the scanlist into the adapter. If you don't have the internal network file, but you have the module physically added and you do an Online Upload to build the network file, it should automatically detect it and then it will be available to add to the adapter's scanlist before downloading it.
Offline you can also update the scanner's scanlist using "Restore I/O Sizes" before downloading.
Either way, whether configuring all this for both the external network (scanner) and the internal network (adapter), you will have to be Online at some point to download both updated scanlists.
The MDD file is not important. It is a saved RSNetWorx MD (Maintenance and Diagnostics) file from a previous analysis of the network.
The above can seem a bit confusing until you following it as your doing it. So I've also made a few screenshots from an example configuration I have here. This is using a 1769-SDN scanner and a 1734-ADN POINT I/O adapter, while adding another POINT I/O input module under the 1734-ADN...
This is the External Network file showing the adapter's I/O size with an input size of 7 bytes before adding the input module...
This is the External Network file showing the adapter's Device Bridging associated with the Internal Network file (filename slightly obscured)...
This is the Internal Network file showing the adapter's scanlist and mapped input data before adding the input module...
This is the Internal Network file as we're about to add the input module (Offline)...
This is the Internal Network file showing the input module added and the adapter's scanlist before and after...
This is the Internal Network file showing the adapter's input size after adding the input module...
This is the External Network file showing the updated adapter I/O size with an input size of 8 after using Restore I/O Sizes...
After updating either the adapter's or the scanner's scanlist you need to download to them or perform a full network download and save the DNT files as you go.
The next step would be figuring out where in the controller tags the new data has mapped into via the scanner's 90 words, but that's for another day, and relatively simple work out.
As Ron said, it can be quirky and depending on the previous setup, not all of the above might be exactly how you'll end up doing it, but it will be close for the most part.
Regards,
George