Welcome to our new forum
All users of the legacy CODESYS Forums, please create a new account at account.codesys.com. But make sure to use the same E-Mail address as in the old Forum. Then your posts will be matched. Close

EXP file not being imported.

PJE
2018-05-01
2018-05-01
  • PJE

    PJE - 2018-05-01

    We've just started using a new commenting format which places line comments, for example ( Line Commment ) , before each line rather than at the end to allow online visualization of the code with embedded variables in Codesys 3 to work better, but when used in Codesys V2.3 these new files are exported but not imported at all!!! It just states Import Complete.

    If I export a POU, delete it and then import it back the POU remains missing. I've tested this on V2.3.9.42 and V2.3.9.56.

    It may be that our comments look like the added comments that Codesys adds int the EXP file, and it's confusing the import.

    (* @NESTEDCOMMENTS := 'Yes' *)
    (* @PATH := '\/FN/PRG Blocks\/Misc' *)
    (* @OBJECTFLAGS := '0, 8' *)
    (* @SYMFILEFLAGS := '0' *)
    (* +--------------------------------------------------------------------------------------------+ *)
    (* | State Machine Variables and Constants                                                      | *)
    (* +--------------------------------------------------------------------------------------------+ *)
    (* Full State Machine Update *) FUNCTION StateMC_Update : BOOL
    (*                           *)
    (* === In/Out Variables ==== *) VAR_IN_OUT
    (* Full State Machine Struct *)      tS         : tStateMC;
    (*                           *) END_VAR
    

    Any help would be appreciated, as we use Mecurrial, together with these EXP files are part of our new development scheme.

     
  • PJE

    PJE - 2018-05-01

    Update:

    We've found the issue. If there's a comment before the FUNCTION xxxxx : yyyy or similar then the import fails. Removing the comment from my previously failing import on FUNCTION StateMC_Update : BOOL line allows the import to work correctly.

    Obviously, with our overzealous use of start of line comments it may be very easy to add the comment by mistake.

     

Log in to post a comment.