tech-e-80 (Customer) asked a question.

Edited April 19, 2024 at 8:01 PM
I am using the P2-CDS-622 controller with Codesys 3.5 SP20 64Bit. When I add a symbol configuration to the application and compile it, I get errors.

Here are the list of errors I am getting. I get these errors on two different PCs and it is only when I add the Symbol Configuration. If I build a standard project without the PS-CDS-622 package I do not get these errors...

 

        ------ Build started: Application: Device.Application -------

        Typify code...

[ERROR]     iecvaraccess, 4.5.0.0 (system): FB_Exit [IecVarAccess]: C0046: Identifier 'IecVarAccUnregisterInstance' not defined

[ERROR]     iecvaraccess, 4.5.0.0 (system): FB_Exit [IecVarAccess]: C0035: Program name, function or function block instance expected instead of 'IecVarAccUnregisterInstance'

[ERROR]     iecvaraccess, 4.5.0.0 (system): Initialize [IecVarAccess]: C0032: Cannot convert type 'Unknown type: 'IecVarAccRegisterInstance3(_IIecVarAccess3, ADR(result))'' to type 'POINTER TO BYTE'

[ERROR]     iecvaraccess, 4.5.0.0 (system): Initialize [IecVarAccess]: C0046: Identifier 'IecVarAccRegisterInstance3' not defined

[ERROR]     iecvaraccess, 4.5.0.0 (system): Initialize [IecVarAccess]: C0035: Program name, function or function block instance expected instead of 'IecVarAccRegisterInstance3'

        Compile complete -- 5 errors, 0 warnings

 

  • 6 answers
  • 617 views

  • FACTS_BruceL (AutomationDirect)

    Update- building a "Symbol Configuration" Object will generate errors since it is primarily targeted for OPC-UA applications (an associated Library created has OPC-UA items) and the P2CDS-622 does not support this fieldbus. The XML file is still generated though with the Tags/Variables defined in the Symbol Configuration.

     

    We will post this on the website as "Unsupported". There is no fixed planned since OPC-UA is not offered with the P2CDS-622.

    Expand Post
    Selected as Best

  • FACTS_BruceL (AutomationDirect)

    The Library "IecVarAccess" is added to the Library Manager when the "Symbol Configuration" Object is added to the project.

     

    The issue looks to be that this library has OPC-UA functions associated with it that the P2CDS-622 doe not support.

     

    What we need to verify is that even if my project does not use OPC-UA (Symbol Configuration > Settings > Support OPC UA features (unchecked) ), will a project still have compile errors if the OPC-UA Fieldbus is not supported in the CPU device (P2CDS-622).

     

    ?- what application are you using this feature for specifically?

     

    Will advise.

    Expand Post

  • tech-e-80 (Customer)

    Hi FACTS_BruceL, I am trying to export the Codesys generated .xml file to a Weintek CMT3072 HMI to build the tag import for the interface. I have used Weintek's own Codesys hardware before but I have not come across this issue yet. The support driver in the HMI is Codesys V3 Ethernet. The docs say that it uses the UDP/IP protocol, so I am not sure if the OPC UA function is needed. As a test I disabled the OPC UA feature in Codesys and executed a build command but I was still receiving the errors. Is there a possible work around to build the .xml file with the iecvaraccess excluded? Thanks for your help!

    Expand Post
    • CODESYS_V3_Ethernet

  • FACTS_BruceL (AutomationDirect)

    Thank you for the details on this! Apologize for the Build errors. Will advise as soon as we see why that Library is choking...

     

    Re. the OPC-UA inquiry, just wanted to make sure your were not trying to use this fieldbus.What you are doing should work.

     

    The problem we have is when you add "Symbol Configuration", it adds/needs that Library to generate the XML also. Remove it and no XML generated.

     

    In the meantime, I noticed even with the Build error, I do get an .XML created in the project directory with the variables of interest in the Symbol area.

     

    symboldataSo for the short term, this will generate the XML to possibly import your Tags as an interim solution.

     

    Expand Post

  • FACTS_BruceL (AutomationDirect)

    Update- building a "Symbol Configuration" Object will generate errors since it is primarily targeted for OPC-UA applications (an associated Library created has OPC-UA items) and the P2CDS-622 does not support this fieldbus. The XML file is still generated though with the Tags/Variables defined in the Symbol Configuration.

     

    We will post this on the website as "Unsupported". There is no fixed planned since OPC-UA is not offered with the P2CDS-622.

    Expand Post
    Selected as Best

  • TRieg (Customer)

    Has anyone found a workaround for this?

     

    This is the first time I've used an AutomationDirect Codesys PLC but have used other PLCs and the Weintek cMT screens but used Modbus.

    • Durallymax (Customer)

      I haven't tried it and haven't used the P2 Codesys, but according to Bruce's pinned post, it will still general the XML file which is all Weintek needs for EBPro. Then, just exclude the symbol config from your build to avoid compile errors.

       

      A nice feature with EBPro is the full symbolic support for Codesys meaning no Modbus registers.

 

Did this information resolve your issue?