https://forge.codesys.com/forge/talk/Engineering/thread/21f213adbb/2020-02-27T14:07:42.686000ZRecent posts to Using the same variables for recipes and communication2020-02-27T14:07:42.686000Z2020-02-27T14:07:42.686000ZAnonymoushttps://forge.codesys.com/u/*anonymous/https://forge.codesys.com57b2310c46d665810549239fe2d932c6acd017db

<div class="markdown_content"><p><em>Originally created by:</em> scott_cunningham</p> <p>You should be able to use the same variables for the recipe values and to send those values over the communication channel. However, you may want to use a set of temporary variables for loading your recipe to preview it or alter it before going "live" with the values. Otherwise, a user cannot change his mind (the old recipe values are lost as soon as you load one).</p> <p>It may be seen as duplication or wasteful, but I prefer to define an array specifically for the communication channel and create one Program that is called every PLC scan that maps program variables to/from the array (especially for Modbus). That way, I am sure of my data order (data<span>[1]</span>, data<span>[2]</span>, etc) while still using descriptive variables in my code (CmdSpeed, ActSpeed, FeedRate, etc).</p></div>

2020-02-27T14:07:42.377000Z2020-02-27T14:07:42.377000Zrazmishttps://forge.codesys.com/u/razmis/https://forge.codesys.comd32d64bc1acb8a0fcede0289a04a1ee3e47e6cfa

<div class="markdown_content"><p>In my project I have many parameters that needs to be in a recipe and also to be transferred via communication (Ethernet/IP) to slave devices.<br/> Is it OK to use the same variables for both the recipe and the communication or should I use two different sets of variables (one for the recipe and one for the communication)?</p></div>