DeviceNet doesn't automatically generate tags associated with the network nodes like EtherNet/IP and ControlNet do.
There are two intermediate steps: The DeviceNet Scanner's Scanlist configuration, and the mapping of that Scanlist data into the I/O tables of the Scanner.
You need the *.DNT file from RSNetworx to see where in the 1756-DNB's data table the connection from the PowerFlex 40 drive is mapped.
It's probably at the very beginning of the scanlist, so you could proceed as though they were, or you could go through the DeviceNet Tag Generator.
One of the important things to remember is that the 1756-DNB's I/O table is composed of DINT elements (32 bits wide), while the PowerFlex 40's I/O words are INT (16 bit). Therefore typically both the Control and Reference words fit into a single DINT in the Output data table, and the Status and Feedback words fit into a single DINT in the Input data table.
This makes it a perfect opportunity to learn about how the COP instruction works with different sized arguments.
Use a COP of length 2 to copy the Input data table from the 1756-DNB's Module:I.Data[0] element to an INT[2] array tag.
Use a COP of length 1 to copy the Output data table from an INT[2] array tag to the 1756-DNB's Module:O.Data[0].
You'll find the meaning of each bit in the Control Word for the PowerFlex, as well as a description of the reference units, in the user manual.