Cross Reference is not showing correctly

I believe your problem may be two issues. The one is the difference between COP and CPS instruction. The COP instruction can be interrupted while the CPS disables interrupts, does the copy and then re-enables interrupts. But, excessive use of the CPS instruction can cause significant issues especially when used with movement of large memory blocks. So, CPS should be used only when it is required.

Your other problem has to do with your length. You believe you are moving 4-bytes in to a DINT. But, the length term defines the number destination items. Therefore, you are moving 16-bytes starting at TC_20:I:Data[0] into 4 consecutive 32-bit memory locations starting with Data_In.Firmware_Version. I believe you can correct this problem by changing length to 1.

As a test, if you are interested, I believe if you move rung 0 to the end of this group of COPs, you will discover may more issues.

In order to help you more, I would need to see you UDT organization.
 

Similar Topics

All - I don't know much about PLC5, I am more from ControlLogix. Can someone answer this: So I am looking at a N262:10 tag with offset 2...
Replies
3
Views
1,152
Hello brothers and sisters of PLCTalk.net, I am working with a PLC5/40 program which uses RSLogix 5, and am wondering if there is a way to export...
Replies
1
Views
1,326
What does it mean when you click on right click on a tag in a run and the "cross reference" option does not exist? Ive noticed sometimes its...
Replies
10
Views
1,861
Hello Gentleman, I would like to display the cross reference along with DT at the end of the interruption point in pic#2 exactly as they are...
Replies
3
Views
1,464
Hi All, I would like to look into some logic which was made in Honeywell DCS TotalPlant. So I have already found a valve which I am interested...
Replies
0
Views
1,310
Back
Top Bottom