Cross referencing specific member of RSlogix 5000

unsaint32

Member
Join Date
Oct 2012
Location
minneapolis
Posts
365
I have a UDT tag that has about 30 members. I want to cross reference just one member of it. When I right click on a specific tag member to cross reference it, I get the list of all members for the tag.

For example, can I cross reference just a DN member of a timer?
 
In your example you can cross reference but it will still show the timer. The Reference column will show the extension. You can double click to sort the reference column to align the extensions.
 
In your example you can cross reference but it will still show the timer. The Reference column will show the extension. You can double click to sort the reference column to align the extensions.

Sometimes, the reference column does not show the extension. Other times, it does. I didn't spend time to investigate why. But when I asked my coworker about it, he told me to use "Find all" if I want to find instructions that use a specific member. So, that's what I am gonna do. Thank you for your input though.
 
You can cross reference just the individual member - depending on how you get to the cross reference window, you may have to manually add it to the end of the cross reference "search" field.

However, this will not only return an explicit reference to just that element - it will also return any logic that may act on that element in an indirect manner.

To take your example of cross referencing a timer done bit. If you do this, you will get a list of everywhere the Timer.DN bit is used on an XIC, XIO, or whatever other creative instruction you have addressed using the Timer.Dn bit. But, you will also get the rung that has the TON or RTO instruction on it as well. Why? Because even though your Timer.DN bit is not explicitly addressed on this rung, the TON instruction uses the .DN bit internally, and has the power to modify it.

You will see the same concept if you cross reference a member of an AOI - you'll always come up with the rung containing the actual AOI itself as well, for the same reason.

The same holds true for a UDT - if there is any operation that acts on your UDT as a whole, the element you're cross referencing is relevant to that logic. It makes sense when you think about it - if I want to see where this data comes from, I need the cross reference to find a COP instruction acting on the whole UDT, not just a MOV instruction moving one specific value into that particular element. Likewise if I'm trying to see all the places the data goes, if there's a blanket COP instruction copying my whole UDT to somewhere else, I want to find that too.
 

Similar Topics

Hi, I have a very old machine I am trying to fix. The PLC is an FA-2 Junior and I am able to connect to it and monitor the code using WinLDR...
Replies
11
Views
2,563
All of these processes are taking all day to run. When doing the same operation in a stand alone intouch application it only take a few minutes to...
Replies
0
Views
1,572
Hi all, Just wondering if anyone can tell me how to find all instances of an input (or any other tag for that matter) anywhere in a Step 7 v5.5...
Replies
4
Views
9,765
HI guys, I have a project where I need to set a SD based off of 2 variables. Speed and Differential pressure. I have a table that has the...
Replies
11
Views
5,865
Hi, I'm needing to convert some screens from RSView to Cimplicity. The screens need to be virtually identical, with all functionality included on...
Replies
1
Views
3,339
Back
Top Bottom