https://forge.codesys.com/forge/talk/CODESYS-V2/thread/beee10da85/2020-02-27T21:18:00.078000ZRecent posts to Task Events2020-02-27T21:18:00.078000Z2020-02-27T21:18:00.078000Zadvantexhttps://forge.codesys.com/u/advantex/https://forge.codesys.comccd0e8a567f1f0a62173ac2b2e4e786f65428b72

<div class="markdown_content"><p>Well that didn't work.</p></div>

2020-02-27T21:17:58.592000Z2020-02-27T21:17:58.592000Zadvantexhttps://forge.codesys.com/u/advantex/https://forge.codesys.com391345ce346434707046ecbc83ddcd26b91b234f

<div class="markdown_content"><p>Thanks Roland, I will try this.</p></div>

2020-02-27T21:17:57.163000Z2020-02-27T21:17:57.163000ZRolandWagnerhttps://forge.codesys.com/u/rowa/https://forge.codesys.comb159143214fcb7b628662e011f95b422c9019cad

<div class="markdown_content"><p>In fact all tasks will be called in simulation mode. But due to the simulation the task behaviour concerning the interval time causes the highest priority task always "to win".</p> <p>Try to "detune" the lower priority tasks by some ms, then it should work.</p></div>

2020-02-27T21:17:53.129000Z2020-02-27T21:17:53.129000Zadvantexhttps://forge.codesys.com/u/advantex/https://forge.codesys.com6fd547fc89f1f6a064188c834a460c707613de84

<div class="markdown_content"><p>It would seem that in simulation mode, the only user created task that actually runs is the highest priority task. No other task seems to be called unless they are 'CoDeSys' tasks like Visualisations etc.</p> <p>I do have a work-around for this but it involves adding further code to the program.</p> <p>I would have thought that if CoDeSys provide a simulation mode in the program it would at least function correctly or have I overlooked something here?</p> <p>Is this just with Wago devices?</p> <p>Does anyone using other devices have this problem?</p></div>