Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

Compile error - The reference information is inconsistent

Created by: smiffy at: 9/22/2014 4:40 PM (13 Replies)

Rating (8)

Thanks 22

Result pages:: |; 1 | 2; |

14 Entries

Entries per page: 10 | all

9/22/2014 4:40 PM	Rate (0)
smiffy Platinum Expert Joined: 1/17/2007 Last visit: 12/5/2024 Posts: 1548 Rating: (538)	Keep getting the "The reference information is inconsistent. The block cannot be compiled." for some STL code. I have checked the code I cannot see anything wrong with it. The error does not give me any additional information as to the cause of the error or what line of code is at fault. Anyone got any ideas? I have tried copying the code to another block and compiling it again, but I get the same error. The code uses a UDT. I have tried compiling the UDT again but that doesn't help either.
	Last edited by: smiffy at: 9/22/2014 4:41 PM Programming today is the race between software engineers building bigger and better idiot proof programs, and the universe producing bigger and better idiots. So far, the universe is winning...
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users Jelle_BE

9/22/2014 5:01 PM	Rate (0)
0_Einstein Diamond Expert Joined: 7/7/2010 Last visit: 1/17/2025 Posts: 15541 Rating: (2465)	smiffy Keep getting the "The reference information is inconsistent. The block cannot be compiled." for some STL code. I have checked the code I cannot see anything wrong with it. The error does not give me any additional information as to the cause of the error or what line of code is at fault. Anyone got any ideas? I have tried copying the code to another block and compiling it again, but I get the same error. The code uses a UDT. I have tried compiling the UDT again but that doesn't help either. Without screenshots of the problems, I'll just toss out random thoughts for things that resulted in this type of problem in the past. Portal often details how an existing system datatype is structured. It makes us think we need to create that same structure and create our own structure with the same layout and use that UDT for something going to a Siemens instruction block, like for T_PARAM. You must use the existing datatype - even though the drop-down selectors do not show them in the pick-list. Push the "I believe" button and move on. Portal often has problems that are documented in obscure ways and the errors we see are really only capable of being diagnosed by Siemens Support by sending them our projects. Happened to me recently. They sent me the pdf that explained the problem, but nothing in the documentation anywhere would have pointed me to the document, nor once completely memorized and understood realize they were related. So, that said, my suggestion: Support Request
	science guy
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users smiffy

9/22/2014 5:16 PM	Rate (0)
smiffy Platinum Expert Joined: 1/17/2007 Last visit: 12/5/2024 Posts: 1548 Rating: (538)	Thanks for the replay huggy. The UDT that I have defined is my own design and not a copy of a system one, and it is used in other blocks in the same project and they compile fine. In fact I have 7 blocks all using the same UDT and 2 out of the 7 fail with the inconsistent reference information error. There is little difference between the one that are ok and the ones that fail. I cannot see any reason for the errors. I will raise a SR. That will be my 4th in one calendar week, all for TIA Portal issues. That speaks volumes about the quality of the product and its supporting documentation. Need I say anymore?
	Programming today is the race between software engineers building bigger and better idiot proof programs, and the universe producing bigger and better idiots. So far, the universe is winning...
Suggestion To thank Quote Answer

9/22/2014 5:32 PM	Rate (1)
smiffy Platinum Expert Joined: 1/17/2007 Last visit: 12/5/2024 Posts: 1548 Rating: (538)	I did a search in google and came across this thread of this forum. https://www.automation.siemens.com/tf/WW/en/Posts/91968#T547048 I followed @James Brauer advice and copied the network and deleted the old network and it then compiled fine. So the EXACT same code copied into a new network compiles with no changes. Why? Another bug I guess. I suppose I could raise an SR to tell them about it. But my experience with this is that they simply tell me that what I have done is the workaround and have a nice day. I have raised many SR's pointing out improvements / bugs / documentation errors and they just go into a black hole. How do we as users improve the product if we don't have a way a reporting issues to the developers? If I were a developer (and I have been in the past) and someone broke my compiler, I would insist on seeing the code and get to the bottom of why it had happened. No only for quality purposes, but for a interest / curiosity and professional pride point of view.
	Programming today is the race between software engineers building bigger and better idiot proof programs, and the universe producing bigger and better idiots. So far, the universe is winning...
Suggestion To thank Quote Answer
This contribution was helpful to 9 thankful Users Fernando Rosa Kurt Pidpa l.alvarez Nick - Maskine T_Ebrahem AutoGen_5951090 TerminalBuzz AsianJimmer ardakaraca

9/22/2014 5:45 PM	Rate (0)
0_Einstein Diamond Expert Joined: 7/7/2010 Last visit: 1/17/2025 Posts: 15541 Rating: (2465)	I completely understand and agree. The push-back I most often get for requesting the process be pushed up further is that once it actually gets to someone at Siemens development HQ, they say "it will be in a future SP, update, or full release" -- in other words, they already knew of the problem, which is why the work-around was already known (my guess/assumption). On the rare instance where I was the first to report it, I heard repeatedly the problem could not be repeated, so I emailed them my project AGAIN and said I used ENGLISH without any DEUTSCH support at all. Then they found the problem and it has since been fixed. There are problems going way back from V10.5 still in the portal related to some conversions that happen automatically to the hardware which affect software - which affect hardware --- infinite loop that is simply aborted and not reported. Like PLC timeout fault that is handled internally but never announced perhaps... Anyhow, I have seen lots of instances where creating a second PLC exactly like the one I have, copy/pasting everything and suddenly it just works.
	science guy
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users smiffy

6/18/2015 7:04 PM	Rate (4)
jwomacks Posts: 1 Rating: (4)	I was having the same issue, with no actual errors. I was successful in resolving the issue by first cutting the logic corresponding to the defined Network. I compiled the block without the Network code and it compiled without any issues. I then went back and inserter another Network in the desired location and pasted the required logic. After Re-Compiling the Block there were no more issures. I feel there is a bug in the Compiler, and this little trick allowed the compiler to not complain any more. Hope this works for you! Have a great day
jwomacks Posts: 1 Rating: (4)
Suggestion To thank Quote Answer
This contribution was helpful to 5 thankful Users smiffy 0_Einstein Fernando Rosa lavdixit JanMa

12/4/2015 2:05 PM	Rate (0)
g_miasa Posts: 1 Rating: (0)	Thanks, The cut rungs, delete network and insert new network then paste works.
g_miasa Posts: 1 Rating: (0)
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users 0_Einstein

4/3/2016 5:46 PM	Rate (1)
Derick81 Posts: 13 Rating: (1)	Thank you, had same problem in a really simple network. Did a cut and paste into the same block and it fixed it.
Derick81 Posts: 13 Rating: (1)
Suggestion To thank Quote Answer

5/18/2017 11:19 AM	Rate (1)
Kurt Pidpa Advanced Member Joined: 7/19/2007 Last visit: 3/4/2024 Posts: 33 Rating: (7)	Same thing here : "reference information is inconsistent" after migration from 300 to 1500 and replacement of 300/FB41 with 1500/CONT_C in the header of a FB. Cut network > Recompile > Paste network did the thing. Bug still present in version V14 Update 1. Thank God there is this forum where users can help each other

Suggestion To thank Quote Answer

10/10/2018 8:34 AM	Rate (0)
AutoGen_300508 Posts: 1 Rating: (0)	I have had same error message "The reference information is inconsistent. The block cannot be compiled." I have solutioned with download a void main program and after i have downloaded again the origenal program (the program that I want use).
AutoGen_300508 Posts: 1 Rating: (0)
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on