Inconsistent LPM data for Module 1,01,02 Block 12455 FC 45, output 3: GlobalIRef (Module 1,03,04)
These messages cover situations where IREF text exists on an off-module input, but the reference text is already used as a local OREF reference.
This can arise in a conversion from WinCAD when the text on a local reference is the same as that needed on a global OREF required by an import block. Before Composer, the text on the import function code was not looked at.
The use of the same reference text in both a local reference and a global one is not valid. It would not be allowed in Composer, but can be imported. There may be no problem with the logic, but it is not robust. Either local or global reference should be made unique. As it is, there is no robust connection by way of Composer, because the text cannot be resolved.
--Parsing file E:\EBY45EB.CLD... No legal LPM match found for IREF **1AOIK CB CLSD on output 1.
In the example, it is possible that the real problem is that the DI/B import block, which is restricted to Loop 2 PCU 30, should actually be replaced with a DI/L block that can import by exception report from Module 2,20,04 Block 6839. Examination of the logic is required to find out how to resolve the problem.
This message is likely to show an error in the system configuration. It should be reviewed. The issue raised may be in unused logic or graphics, or have other realities that make it a non-issue.
Please contact us for help resolving your error messages.
DBDOC ©1996 - 2019 G. Michaels Consulting Ltd., all rights reserved. All other trademarks and registered trademarks are the property of their respective holders. Website source largely available under the terms of the AGPLv3.