Where can I find more help on the OpenPlcCodeViewByFCCall function?

0
I have done some searches but found nothing besides the basic Portal help file.   Attached is the fault I get when I try to use it. The Trace Viewer log is attached. There is no remedy for 3302 in the Portal help.   Also shown is how I configured it. I know I put the multi-instance name in for UDT path which is probably what is wrong, but I’m not sure what else to put there.   This is an important feature for our customer in order to choose WinCC Unified as it’s on a lot of their Comfort faceplates. I understand LAD in the code viewer is a new feature as of Upd1 so hopefully someone has some experience with it. Thanks.
asked
1 answers
0

Error 3302 ("No block was found at which this UDT is used") suggests the Code Viewer cannot resolve the supplied UDT instance back to a specific block call chain.

Looking at your screenshots, I would be suspicious of the User data type instance parameter rather than the FC call itself.

In the example, instVAC11 appears to be a multi-instance inside LMove_Valve1To8PosPD [FB165]. The Code Viewer function typically needs to identify where the UDT instance is actually declared and used in the call hierarchy. If the instance is nested or multi-instanced, passing only the instance name may not provide enough information for the viewer to locate the owning block.

I would try two things:

  1. Test with a simple UDT instance that is declared directly in a DB or FB interface rather than as a multi-instance.
  2. Verify what Siemens means by "UDT path" in the latest documentation. In some cases the function expects the complete symbolic path rather than only the instance name.

Another clue is that the code viewer opens the correct block (FB4050) but then immediately reports 3302. That suggests the FC call can be resolved, but the UDT lookup cannot.

If this is a new feature introduced in Update 1, there is also a chance you're running into a limitation where multi-instance UDT references are not yet supported by the lookup used by OpenPLCCodeViewByFCCall.

Based on the screenshots, I would investigate the multi-instance configuration first, because the error specifically mentions the UDT usage lookup rather than the FC, PIN, or screen object path.


answered