comment created by a user, but I cannot see it under the ticket
updating CfUnit Trunk to RC4
updated verifier to RC4
Allo, bitte posten sie diesen frage im English ;-)
IECStringUtils
Added compiled library (RC4) to trunk
see https://forge.codesys.com/tol/iec-snippets/snippets/6
Logmanager
LogManager by @lmdejong PROGRAM LogManager VAR POU_ERROR: BOOL; ManagerState: INT:=0; ErrorAtState: INT:=0; State_eError: FILE.ERROR; hFile: FILE.CAA.HANDLE; filop: FILE.Open; filcl: FILE.Close; filwr: FILE.Write; hDir: FILE.CAA.HANDLE; fildop: FILE.DirOpen; fildcl: FILE.DirClose; fildcr: FILE.DirCreate; LOG30: TBLOG; LOG76: TBLOG; LWD: ARRAY [0..MaxID-1] OF TBTEST; sTarget: STRING; sFileName: STRING; TestID: UINT; xFileExists: BOOL; udiFileSize: UDINT; szFileSize1: FILE.CAA.SIZE := 0; udiCmpError:...
PROGRAM LogManager VAR POU_ERROR: BOOL; ManagerState: INT:=0; ErrorAtState: INT:=0; State_eError: FILE.ERROR; hFile: FILE.CAA.HANDLE; filop: FILE.Open; filcl: FILE.Close; filwr: FILE.Write; hDir: FILE.CAA.HANDLE; fildop: FILE.DirOpen; fildcl: FILE.DirClose; fildcr: FILE.DirCreate; LOG30: TBLOG; LOG76: TBLOG; LWD: ARRAY [0..MaxID-1] OF TBTEST; sTarget: STRING; sFileName: STRING; TestID: UINT; xFileExists: BOOL; udiFileSize: UDINT; szFileSize1: FILE.CAA.SIZE := 0; udiCmpError: UDINT; j: UINT; sData:...
PROGRAM LogManager VAR POU_ERROR: BOOL; ManagerState: INT:=0; ErrorAtState: INT:=0; State_eError: FILE.ERROR; hFile: FILE.CAA.HANDLE; filop: FILE.Open; filcl: FILE.Close; filwr: FILE.Write; hDir: FILE.CAA.HANDLE; fildop: FILE.DirOpen; fildcl: FILE.DirClose; fildcr: FILE.DirCreate; LOG30: TBLOG; LOG76: TBLOG; LWD: ARRAY [0..MaxID-1] OF TBTEST; sTarget: STRING; sFileName: STRING; TestID: UINT; xFileExists: BOOL; udiFileSize: UDINT; szFileSize1: FILE.CAA.SIZE := 0; udiCmpError: UDINT; j: UINT; sData:...
Thanks for posting this! Would you mind if I submit this into the code snippet corner? As this seems a good snippet for it
Would you mind correcting this typo so we can c/p your solution? That would be awesome!
Hi, You should check out the following: projects, applied design patterns, design patterns for Ladder logic, In that project you will find various design patterns for smart ladder logic solutions! You'll find timer ld patterns there too. Don't forget to thumb up if it helped you
Hi, You should check out the following: projects, applied design patterns, design patterns for Ladder logic, In that project you will find various design patterns for smart ladder logic solutions! You'll find times ld patterns there too. Don't forget to thumb up if it helped you
Hi, You should check out the following: projects, applied design patterns, design patterns for Ladder logic, In that project you will find various design patterns for smart ladder logic solutions! Don't forget to thumb up if it helped you
Hi, You should check out the following: projects, design patterns, patterns for Ladder logic, In that project you will find various design patterns for smart ladder logic solutions!
binary of CfUnit.library
deleted
testresults.xml
Added various WSTRING tests
RC4: Fixed a bug for STRING/WSTRING size assertion
Hi There! You are cordially invited to testdrive the latest "CfUnit Release Candidate". We would like to ask you if you would like to share your personal test experiences with us, both on the framework and the software, as this will improve the framework. Let's share use-cases and usage experiences so we can learn or get inspired. If you find anything unexpected, do not hesitate and let us know so we can solve the issue accordingly. RC means the software is expected to behave fully functional but...
Hi There! You are cordially invited to testdrive the latest "CfUnit Release Candidate". We would like to ask you if you would like to share your personal test experiences with us, both on the framework and the software, as this will improve the framework. Let's share use-cases and usage experiences so we can learn or get inspired. If you find anything unexpected, do not hesitate and let us know so we can solve the issue accordingly. RC means the software is expected to behave fully functional but...
Hi There! You are cordially invited to testdrive the latest "CfUnit Release Candidate". We would like to ask you if you would like to share your personal test experiences with us, both on the framework and the software, as this will improve the framework. Let's share use-cases and usage experiences so we can learn or get inspired. If you find anything unexpected, do not hesitate and let us know so we can solve the issue accordingly. RC means the software is expected to behave fully functional but...
Hi There! You are cordially invited to testdrive the latest "CfUnit Release Candidate". We would like to ask you if you would like to share your personal test experiences with us, both on the framework and the software, as this will improve the framework. Let's share use-cases and usage experiences so we can learn or get inspired. If you find anything unexpected, do not hesitate and let us know so we can solve the issue accordingly. RC means the software is expected to behave fully functional but...
Hi There! You are cordially invited to testdrive "The Latest CfUnit Release Candidate". We have made available RC5, it contains various fixes provided by you, the community. See [cfunit:code:r388] This means the software is expected to behave fully functional but misses some documentation and might still receive small fixes until it gets it's official release. Offcourse this public release will be announced in due time also. So, whats new in CfUnit v1.1.0.0 ? Many improvements and bugfixes over v1.0.0.0,...
Home
Home
Home
Home
Home
Hi There! You are cordially invited to testdrive "The Latest CfUnit Release Candidate". We have made available RC5, it contains various fixes provided by you, the community. This means the software is expected to behave fully functional but misses some documentation and might still receive small fixes until it gets it's official release. Offcourse this public release will be announced in due time also. So, whats new in CfUnit v1.1.0.0 ? Many improvements and bugfixes over v1.0.0.0, 100% backward...
At the next release the .package will include all referenced libraries, at penalty of a bigger .package size (60+ MB) and thus a longer installation time. All dependencies will be included, thus the lacking of any libraries will be solved by design.
To be honest I never used HMI SL as Webvisu works very well for my type of projects. Maybe you try out a DEMO for it?
Building an IO list can take some while: I had over 18000 IO in a project once...
Copy/pasting into the mapping can be done but works a bit awkward. Just try tinkering with selections and shift and you'll manage.
Here you go. I'll add all referenced libs in the .package on next release. PS it is a CODESYS lib
Here you go. I'll add all referenced libs in the .package on next release.
Send us a .projectarchive so we can check.
Is your issue resolved?
Maybe you have better luck posting this question under the forum, see menu " CODESYS Talk".
Which runtimes are supported?
Jenkins or Drone integration?
Running a test over multple PLC cycles
On using the RC versions of CfUnit