3/9/2018 51686 - RSNetworx for DeviceNet: Advanced Mapping feature

RSNetworx for DeviceNet: Advanced Mapping feature

51686 | Date Created: 04/30/2008 | Last Updated: 01/11/2018
Print
Access Level: Everyone

Question
What is Advanced Mapping?
Why and when would I use Advanced Mapping?
What are the limitations of Advanced Mapping?
Why are only four segments available when using Advanced Mapping?
How do I use Advanced Mapping?
How do I manually map I/O in the scanner card?

Answer
Advanced Mapping allows you to break a DeviceNet node's input and/or output data into four segments and allows
you to map these segments independently anywhere in the data table.

These segments can be as small as one bit and as large as is required.

Only four segments are possible. This is a limitation of DeviceNet itself, not the RSNetworx software.

All DeviceNet scanners support Advanced Mapping.

Normally you would use Advanced Mapping when you have limited space and want to map only a portion of a
node's available data table. You can also use Advanced Mapping if you require certain data at a certain location in
your processor's DeviceNet data table because you have existing ladder logic that you do not want to alter.

As an example, let's say you have a 16-input discrete Block I/O module with 2 words of input data, 32-bits total.
The first word of input data is a status word and the second word is a 16-bit representation of the 16 individual
inputs.

In the interest of saving space you only want to map the data, not the status. First of all you would add the node to
your scanner's scanlist using RSNetworx for DeviceNet. In the upper-left corner of the Scanlist tab there is a
checkbox that says "Automap on add", you would un-check this checkbox before adding the node to your scanlist.

Once you have added the node to the scanlist you would click the Input tab. There you would select the node in
the top portion of the window and click the Advanced button. This brings up the Advanced Mapping window.

In the Advanced Mapping window you will see your four data segments at the top of the window with the following
columns:

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/51686#51686 1/3
3/9/2018 51686 - RSNetworx for DeviceNet: Advanced Mapping feature

Map Message Offset Memory Offset Bit Length

Map 1, 2, 3 or 4. These are your four available segments.

Message will either be Change of State (COS), Polled or Strobed depending on what this particular node
supports.

Offset - This first offset column shows where the data is being mapped from in the node's data table. This data
comes from the selection you make below in the Map From box. It will show a byte #, a colon and then the bit #.

Memory will be a selection you make depending on which Memory file you want the node's data mapped in.
Some scanners have multiple selections. The 1747-SDN, for example, would allow you to select between
Discrete and M-Files. Some, like the 1756-DNB, have only one selection.

Offset - This second offset column shows where the data is being mapped in the Scanner's data table. It will be
represented by a word (or dword) #, a colon, and then the bit #. This data comes from the selection you make
below in the Map To box.

Bit Length is the number of bits in this particular segment.

Our example Block I/O module has 32-bits of data total in it's Input data table. We only want to map the second
16-bits which contain the data. This will require using only one segment.

First we need to fill in the proper information in the Map From box. The Map From box contains entry fields for
Message, Byte and Bit. Message is the same as described above. Usually you will just leave the Message
setting at its' default. The entry fields for Byte and Bit are how you specify where in the data table

Imagine the Block I/O's input data table as follows:

Byte 0 - lower 8 bits of status Byte 1 - upper 8 bits of status

Byte 2 - lower 8 bits of input data Byte 3 - upper 8 bits of input data

We want to start mapping at Byte 2, skipping the first two bytes of data so we would enter a 2 into the Byte field.

We would enter a 0 into the Bit field because we want to start mapping at Byte 2, bit 0.

In the Map To box there are entries for Memory, Word (or DWord) and Bit. Memory is the same as described
above. You will enter the appropriate Word and Bit where you want to map the data in the Scanner's Input data
table. We are mapping 16-bits of data. We can map it to Word 10, Bit 3 or anywhere we choose.

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/51686#51686 2/3
3/9/2018 51686 - RSNetworx for DeviceNet: Advanced Mapping feature

Below the Map To box there is an entry for Bit Length. This is where you will enter the number of bits you will
map in this segment. We'll choose 16-bits.

In this example we will have mapped the second 16-bits of our Block I/O module's Input data to Word 10, Bit 3 of
our Scanner's Input data table. This will cause the Block I/O's Input to occupy bits 3 through 15 of Word 10 and
bits 0 through 2 of Word 11.

Our segment will look like this in the Advanced Mapping window:

Map Message Offset Memory Offset Bit Length

1 Polled 2:0 Discrete 10:3 16

DISCLAIMER
This knowledge base web site is intended to provide general technical information on a particular subject or
subjects and is not an exhaustive treatment of such subjects. Accordingly, the information in this web site is not
intended to constitute application, design, software or other professional engineering advice or services. Before
making any decision or taking any action, which might affect your equipment, you should consult a qualified
professional advisor.

ROCKWELL AUTOMATION DOES NOT WARRANT THE COMPLETENESS, TIMELINESS OR ACCURACY OF

ANY OF THE DATA CONTAINED IN THIS WEB SITE AND MAY MAKE CHANGES THERETO AT ANY TIME IN
ITS SOLE DISCRETION WITHOUT NOTICE. FURTHER, ALL INFORMATION CONVEYED HEREBY IS
PROVIDED TO USERS "AS IS." IN NO EVENT SHALL ROCKWELL BE LIABLE FOR ANY DAMAGES OF ANY
KIND INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS PROFIT OR DAMAGE, EVEN
IF ROCKWELL AUTOMATION HAVE BEEN ADVISED ON THE POSSIBILITY OF SUCH DAMAGES.

ROCKWELL AUTOMATION DISCLAIMS ALL WARRANTIES WHETHER EXPRESSED OR IMPLIED IN

RESPECT OF THE INFORMATION (INCLUDING SOFTWARE) PROVIDED HEREBY, INCLUDING THE IMPLIED
WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, AND NON-
INFRINGEMENT. Note that certain jurisdictions do not countenance the exclusion of implied warranties; thus, this
disclaimer may not apply to you.

This page is best viewed in Internet Explorer 11, Edge, Firefox 41, Chrome 46, Safari 9 or newer.

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/51686#51686 3/3