https://forge.codesys.com/forge/talk/CODESYS-V2/thread/752cbf8a69/2020-02-27T20:53:03.193000ZRecent posts to Wishlist for IEC 61131-3:20132020-02-27T20:53:03.193000Z2020-02-27T20:53:03.193000ZStrucchttps://forge.codesys.com/u/strucc/https://forge.codesys.combc99457821b8384f3eda1246ff6d56f739f27c48

<div class="markdown_content"><p>Sry,I can't see your email address,<br/> Mine is pop at eik dot bme dot hu...</p></div>

2020-02-27T20:53:01.788000Z2020-02-27T20:53:01.788000Zspfeifhttps://forge.codesys.com/u/spfeif/https://forge.codesys.com8e3b83a0f58ea6bda1eb55757bf06c02d6ddac17

<div class="markdown_content"><p>Hmm seems I don't get emails anymore from the forum when their are new posts. Need to check settings.</p> <p>Strucc you mean a book? Although I am serious I guess I need a kick in the but to get moving? Are you saying you are still interested?</p> <p>If so you can contact myself via email and we can see were it goes?</p></div>

2020-02-27T20:52:57.766000Z2020-02-27T20:52:57.766000ZStrucchttps://forge.codesys.com/u/strucc/https://forge.codesys.com6917d97b5e77ed7e746195df6c9eac3e7a764589

<div class="markdown_content"><p>Any news about this?</p></div>

2020-02-27T20:52:56.352000Z2020-02-27T20:52:56.352000Zspfeifhttps://forge.codesys.com/u/spfeif/https://forge.codesys.comcab2fcebfed03658a80861f49037703fdb3ad3e4

<div class="markdown_content"><p>shooter your in. Now we just need a starting point.</p></div>

2020-02-27T20:52:52.387000Z2020-02-27T20:52:52.387000Zshooterhttps://forge.codesys.com/u/shooter/https://forge.codesys.com587aae345cda737deb5c43025b2b252547891aae

<div class="markdown_content"><p>I like to participate when writing a book on 61131-3<br/> special when it is done on codesys.</p></div>

2020-02-27T20:52:50.980000Z2020-02-27T20:52:50.980000Zspfeifhttps://forge.codesys.com/u/spfeif/https://forge.codesys.com9cda17ad5c07e56daf67963ec7baab14e3e73d14

<div class="markdown_content"><p>One good place to start is a manual for best practices for IEC61131 for coding conventions like naming conventions,Layout conventions, Commenting (V23 doesn't support // as apposed to (<em> </em>)) , language guidelines. This would almost boil over into some guidlines for naming conventions for automation like the use of En (Enable), Permit vs Interlock etc.. You understand, you get my drift. This way you can almost aid in some self documentation just by looking at the input / outputs of a FB. Do I hold this input TRUE all the time or only on rising edge? These questions can almost be answered at the FB interface. Anyway I would love to follow some standard that helps EVERYONE make it a bit more clear. I maybe crazy but just a thought.</p></div>

2020-02-27T20:52:47.024000Z2020-02-27T20:52:47.024000ZStrucchttps://forge.codesys.com/u/strucc/https://forge.codesys.com9e6b05c4d5ba8439df748a425426419c1e19e277

<div class="markdown_content"><blockquote> <p>spfeif: No you don't have to... 'cause it's going to be me who write that book <br/> (ok, if you have the title and the publisher, I'm happy to contribute the rest of it )</p> </blockquote> <p>Anyway... Beside researching the next generation of controllers and programming languages, we should spend more time, to disperse this knowledge. And in fact, for us, involved in the "academic" sphere, it's a challenge as well...</p> <blockquote> <p>spfeif: did you learn from books? The last book I bought in my practice was the one with the camel at the cover. Yes, I like perl. And camels. That time it was a value. And I feel the same, there is a strong vacuum for explaining the <em>practical application</em> of the educated programming skills. But a book is not really an answer... today... We should start a wiki page, or... something compatible with g***gle. It's a strange - and a bit sad - but still something to learn to live with.... Tomorrow's programmers are not going to be IT professionals... just today's children, with a slightly different approach... and instincts... </p> </blockquote> <p>This is a bit off-topic. (just as the effect behind the birth of CoDeSys: at a point people just suddenly realized, that PLCs are a kind of computers... and why not to use them as computers? The language seems to go trough the already known (r)evolution. WTF??!!! PLCs parsing XML??? Why not? Then... we need the right instruments to do this...)</p></div>

2020-02-27T20:52:45.603000Z2020-02-27T20:52:45.603000Zspfeifhttps://forge.codesys.com/u/spfeif/https://forge.codesys.comee7d2ec00282ee482dca8d0d2025c5d09754d4f5

<div class="markdown_content"><p>I agree. One thing from a development standpoint is how would we know to look in a library named CAA_ListAndTree? That is one issue. Finding things that can be useful without wasting days figuring it out. All the 3s examples are so basic they need deeper level examples for us to learn from. But again 3s I think expects the OEM who implemented CoDeSys onto their target to support you, which by the time the support gets to the end user of that product (myself) no-one can answer any questions. I had the exact issue come up as Strucc mentioned just last month. I tried to use Pragmas but it didn't seem to work well. I too wanted test code or unit testing to do position control. I wrote my test FB that when commanded acts like a VFD drive that responds to velocity and encoder feedback. But I have to add all that code into the project. At least I could not find a solution that was elegant. I was hoping for at least setting a global variable to turn on/off testing. What's hard is if you are already using software from a 3rd party and they are not using at least interfaces from V3 then I'm not sure at compile time I can change one FB for another like </p> <p>If define (DEBUG = 1) then<br/> FB := TEST_FB;<br/> else<br/> FB := Third_Party_FB;<br/> end_If</p> <p>Especially into FBD since you have to enter a FB instance on the screen before compile time.</p> <p>I really do need to write a book in ENGLISH on CoDeSys since there is nothing out there.</p></div>

2020-02-27T20:52:44.186000Z2020-02-27T20:52:44.186000ZStrucchttps://forge.codesys.com/u/strucc/https://forge.codesys.coma9a79c59ea4d26c19c8e90a6bde5cdad94efd9f8

<div class="markdown_content"><p>Thanks for the reply.</p> <p>Regarding conditional compilation / defines:<br/> I don't see a (n external) reason, that it shouldn't work in the project tree. (I know, it's documented) <br/> Example:<br/> A library implements complex automation tasks. Debugging and logging features are useful, but in a real application they are resource consuming. Would be nice, to be able to build a debugging version of the project, and after the development simply turn that flag off. Similar with simulation options: For example, code is added to the FB to allow process simulation ... a PID controller in simulation mode should use the simulation time rate for example... But, this code should be excluded from the production application. Also... On multi-platform projects, one might imagine a library with slightly different implementations... But still relying on a common code basis.</p> <p>Regarding CAA_ListAndTree - The documentation /example was missing, I was playing with that, but ended up to implement something similar. However, in the future I'd be very happy to avoid that, I think the value of my code depends on it's well focused functionality. In this case, I think it's also important to see the implementation background (how much memory does a list entry take, what resources are used, etc...). </p> <p>Also... As a library developer, I'd be very happy to see more recommendations (I know the old CAA material, and the new document released with SP2). <br/> More exactly: what libraries to rely on in the future? (Yes, in general use CAA<em>, try to avoid SysLib</em>) For example in V2, I did a dynamic memory "wrapper" library, as SysLibMem was not available on some platforms. So, I ended up by writing a similar library relying on a simple static byte array, pointers, etc. Would be nice to know, and clearly understand, what is the minimal set of libraries one can build a library on. </p> <p>In general: we all know that * everything * can be done, even with CoDeSys V2. There are some really nasty tricks, one can even enjoy them ... But what we are aiming, is the "art of programming" - to be able to write compact, easy to understand, reusable code. I'm really happy to see recent CoDeSys developments, not only concerning the language, but replying business needs, like javascript based web visu. </p> <p>I'd be glad to discuss these in detail, and within the framework of our current project we are on the way to establish this kind of communication with 3S. Please drop me a mail to pop (at) eik dot bme dot hu.</p> <p>(I didn't find a way to write personal messages here)</p></div>

2020-02-27T20:52:40.203000Z2020-02-27T20:52:40.203000ZAnonymoushttps://forge.codesys.com/u/*anonymous/https://forge.codesys.com849cc59684511ddc534917ad241d9e67347b39df

<div class="markdown_content"><p><em>Originally created by:</em> Bernhard Werner</p> <p>at the moment, I can't give you a date for the missing features.<br/> But you can be sure, that we will eventually implement all of these features.</p> <p>You should not mix up CODESYS and the standard. Pragmas for example are only mentioned in the standard,<br/> that they do exist, and any semantics of pragmas are implementation dependant.<br/> In fact, you can set a define in the "Compiler defines" of the Build options of an application, and use it in your code<br/> like this</p> <div class="codehilite"><pre><span></span>{<span class="k">IF</span> <span class="nv">defined</span><span class="ss">(</span><span class="s1">'</span><span class="s">something</span><span class="s1">'</span><span class="ss">)</span>} <span class="o">//</span> <span class="k">do</span> <span class="nv">this</span> {<span class="k">ELSE</span>} <span class="o">//</span> <span class="k">do</span> <span class="nv">that</span> {<span class="nv">END_IF</span>} </pre></div> <p>but you can't use that define in the interface, and you can't use it in the project tree.<br/> Concerning Collections: have you checked the CAA_ListAndTree.library?<br/> Generics as in C# would be a great thing, but not for the near future. <br/> Be sure, we will continue to implement new functionality, we currently released the static analysis,<br/> and we are working on UML-integration. We are planning a profiling option...</p> <p>Bernhard Werner</p></div>