Activity for aliazzz
-
aliazzz posted a comment on discussion Engineering
Can you post a HOW TO on this topic? The reason for this AFAIK this "feature" is not part of the current toolchain anymore? So I hope you can write a short manual for us all, as I still haven't found time to figure things like this out on my own because of time and other priorities. You would do me and I think more more people a big favour ;-)
-
What brand of hardware are you running?
-
Problem found: The Codesys Automation Server (CAS) PLC was configured to be synchronised in the background... Turning synchronisation off did the trick.
-
MqttSparkplugB/trunk/unittest.project
-
Problem found: The Codesys Automation Server proiject on the PLC was configured to be synchronised... Turning synchronisation off did the trick.
-
Problem found: The Codesys Automation Server proiject on the PLC was configured to be synchronised... Turning synchronisation did the trick.
-
If you have cracked your problem, would you mind posting/sharing your solution here? Thanks
-
If you have cracked your problem, would you mind posting/sharing it here? Thanks
-
MqttSparkplugB/trunk/unittest.project EDIT: Posted a devicelog for analysis
-
Hi I have installed Codesys V3.5.16.0 x64 with ControlWin x64. Whenever I download a project to the runtime the download works but the runtime will NOT allow me to start (The play button keeps greyed out). uninstalling / reinstalling of CODESYS did not help(!) I allready tried this. If logs etc are needed to diagnose this I am happy to post them. hoping to hear from you
-
MqttSparkplugB/trunk/unittest.project
-
Hi I have installed Codesys V3.5.16.0 x64 with ControlWin x64. Whenever I download a project to the runtime the download works but the runtime will NOT allow me to start (The play button keeps greyed out). unistalling / reinstalling of CODESYS did not help (!) I allreadytried this. If logs etc are needed to diagnose this I am happy to post them. hoping to hear from you
-
Hi there! You are cordially invited to use (test drive) the latest version of the "CfUnit Release Candidate 5". With your help, we can let the software get mature faster and limit the amount of bug fixes needed after the official public release. We bring the pain forward so we can enjoy the gain sooner. We highly encourage you to use an RC and if you stumble upon something unexpected, please share your findings so we may improve the software faster. Currently serving RC5 Improved stability and wider...
-
You are (from what I understand) trying to describe an array of pointers to your elements instances but i have difficulties in understanding your writing, so I could misinterpret it. (* pointers are *dangerous* when not initialised correct *) Collection : ARRAY [0..31] OF POINTER TO DataExchange; (* I am not sure on this ^ statement! it could also be a pointer to DWORD ?=> check ). Always initialise the array of pointers in the beginning of your code and continously update them. This might be tedious...
-
You are (from what I understand) trying to describe an array of pointers to your elements instances but i have difficulties in understandiong your writing, so I could misinterpret it. (* pointers are *dangerous* when not initialised correct *) Collection : ARRAY [0..31] OF POINTER TO DataExchange; (* I am not sure on this ^ statement! it could also be a pointer to DWORD ?=> check ). Always initialise the array of pointers in the beginning of your code and continously update them. This might be tedious...
-
Sorry for my bad statement and thanks for your answer. => okay I guess? You are (from what I understand) trying to describe an array of pointers to your elements instances but i have difficulties in understandiong your writing, so I could misinterpret it. ( pointers are dangerous when not initialised correct ) Collection : ARRAY [0..31] OF POINTER TO DataExchange; (* I am not sure on this ^ statement! it could also be a pointer to DWORD as adresses are mostly DWORDS) ( Always initialise the array...
-
LOL, I think you understand my issue as you write : sorry, but I can't see this message at all. I can't see what has been posted neither, but the email I received from cForge tells me there has been posted something (?) Therefore I am very confused about what is going on and I thought I'd inform admins on it. I hope this wont happen too much. If so, I'll keep a better track of what happened. To be honest, the thread is kind of a "mess". Lets close this issue and I keep an eye out for as if it happens...
-
Structs are NOT Types! Apparently you want a Struct of your own type which is achieved like this: Exchange : ARRAY [0..31] OF DataExchange; Usage Exchange[0].Data1 := a; Exchange[0].Data2 := b; Exchange[0].Data3 := c; .. .. Exchange[31].Data1 := x; Exchange[31].Data2 := y; Exchange[31].Data3 := z; Offcourse 0..31 and a,b,c,x,y,z are illustrative. Regards, Aliazzz
-
Try this out; Declaration Exchange : ARRAY [0..31] OF DataExchange; Usage Exchange[0].Data1 := a; Exchange[0].Data2 := b; Exchange[0].Data3 := c; .. .. Exchange[31].Data1 := x; Exchange[31].Data2 := y; Exchange[31].Data3 := z; Offcourse 0..31 and a,b,c,x,y,z are illustrative. Regards, Aliazzz
-
This forum is loaded on this topic: https://forge.codesys.com/forge/talk/CODESYS-V2/thread/e75cc2ca73/?limit=250#3940
-
This forum is loaded on this issue: https://forge.codesys.com/forge/talk/CODESYS-V2/thread/e75cc2ca73/?limit=250#3940
-
That is the standard/normal/vanilla symbolic way of coupling IO... In general there are 2 vanilla flavours (there are way more options but those aren't exactly vanilla anymore); 1 Declare variables in your IO point and reference that variable in your POU (program, FB, Func, whatever) 2 Declare variables in your POU and couple them to an IO point. PS: I never use hardcoded IO adresses in my code (%I, %Q, %M etc) .
-
Hi there! You are cordially invited to use (test drive) the latest version of the "CfUnit Release Candidate 5". With your help, we can let the software get mature faster and limit the amount of bug fixes needed after the official public release. We bring the pain forward so we can enjoy the gain sooner. We highly encourage you to use an RC and if you stumble upon something unexpected, please share your findings so we may improve the software faster. Currently serving RC5 So, whats new in CfUnit v1.1.0.0?...
-
Hi there! You are cordially invited to use (test drive) the latest version of the "CfUnit Release Candidate 5". With your help, we can let the software get mature faster and limit the amount of bug fixes needed after the official public release. We bring the pain forward so we can enjoy the gain sooner. We highly encourage you to use an RC and if you stumble upon something unexpected, please share your findings so we may improve the software faster. Currently serving RC5 So, whats new in CfUnit v1.1.0.0?...
-
Currently serving RC5 Hi there! You are cordially invited to testdrive the latest version of the "CfUnit Release Candidate". With your help, we can let the software get mature faster and limit the amount of bugsfixes needed after an official public release so we bring the pain forward and we can enjoy the gain sooner. We highly encourage you to use an RC and if you stumble upon something unexpected, please share your findings so we may improve the software faster. Currently serving RC5 So, whats...
-
Bump
-
Hi there! You are cordially invited to testdrive the latest version of the "CfUnit Release Candidate". With your help, we can let the software get mature faster and limit the amount of bugsfixes needed after an official public release so we bring the pain forward and we can enjoy the gain sooner. We highly encourage you to use an RC and if you stumble upon something unexpected, please share your findings so we may improve the software faster. Currently serving RC5 So, whats new in CfUnit v1.1.0.0?...
-
Hi there! You are cordially invited to testdrive the latest version of the "CfUnit Release Candidate". With your help, we can let the software get mature faster and limit the amount of bugsfixes needed after an official public release so we bring the pain forward and we can enjoy the gain sooner. We highly encourage you to use an RC and if you stumble upon something unexpected, please share your findings so we may improve the software faster. Currently serving RC5 So, whats new in CfUnit v1.1.0.0?...
-
Hi there! You are cordially invited to testdrive the latest version of the "CfUnit Release Candidate". With your help, we can let the software get mature faster and limit the amount of bugsfixes needed after an official public release so we bring the pain forward and we can enjoy the gain sooner. We highly encourage you to use an RC and if you stumble upon something unexpected, please share your findings so we may improve the software faster. Currently serving RC5 So, whats new in CfUnit v1.1.0.0?...
-
On using the RC versions of CfUnit
-
On using the RC versions of CfUnit
-
Hi there! You are cordially invited to testdrive the latest version of the "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...
-
updated verifier and library to RC5 to fix ticket #43, #44 and #46
-
Verifier adjusted for RC5
-
RC5 fixes Ticket n.o: #43, #44 & #46
-
That is the standard/normal/vanilla way of coupling IO... In general there are 2 vanilla flavours (there are way more options but those aren't exactly vanilla anymore); 1 Declare variables in your IO point and reference that variable in your POU (program, FB, Func, whatever) 2 Declare variables in your POU and couple them to an IO point. PS: I never use hardcoded IO adresses in my code (%I, %Q, %M etc) .
-
That is the standard/normal/vanilla way of coupling IO... In general there are 2 vanilla flavours (there are way more options but those aren't exactly vanilla anymore); Declare variables in your IO point and reference that variable in your POU (program, FB, Func, whatever) Declare variables in your POU and couple them to an IO point. PS: I never use hardcoded IO adresses in my code (%I, %Q, %M etc) .
-
Contributing to CfUnit
-
Cantributing to CfUnit
-
Cantributing to CfUnit
-
Tags older than v1.0.0.0 are not distributed anymore
-
deleting EULA, see trunk for license
-
commit of LICENSE.html, LICENSE.md and CONTRIBUTION.md
-
Maybe you should check out this store example: https://store.codesys.com/io-mapping-tool.html It enables you to graphically map IO to an FB 'on the fly' or do it programmatically. Plus this example is open-source, so if you want to know how it works or modify it for your own needs you can do that. Good luck
-
I use the MQTT client, it uses very similair design under the hood ;-). So far it works as expected for me. However, have you tried the example(s) provided with this library? If not, be sure to check those out!
-
ps the comment is as follows; "Hi, What type of CODESYS version are you running (IDE) it is a brand-labelled version of ... "