CODESYS - the IEC 61131-3 automation software

Welcome to the official CODESYS Forum by 3S-Smart Software Solutions GmbH | A member of the CODESYS Group
Deutsche Version English version russian version 
It is currently Mon May 20, 2019 11:54 pm

All times are UTC+01:00




Post new topic  Reply to topic  [ 2 posts ] 
Author Message
PostPosted: Tue May 01, 2018 3:03 pm 
Offline

Joined: Sun May 13, 2012 5:16 pm
Posts: 28
We've just started using a new commenting format which places line comments, for example (* Line Commment *) <Code>, 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.

Code:
(* @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.


Top
   
PostPosted: Tue May 01, 2018 3:57 pm 
Offline

Joined: Sun May 13, 2012 5:16 pm
Posts: 28
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.


Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic  [ 2 posts ] 

All times are UTC+01:00


Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Limited