Error "HMI0018", upgrading from 24.04LTS to 25.0LTS

Hi again,
While now the Modbus_TCP 16 is out now I’ve come across the following.
„HMI0018: Building HMI page ‚Trends‘: The data logger session ‚ChartyChart‘ and chart ‚Chart2‘ contains variables from idle task (use cyclic task variables only).“ (Got multiple of these „Errors“)
This error was not present in 24.04LTS and this error shouldn’t be there. Nothing in the changelog (to my knowledge) notes that something has changed in how the data is handled.
I’m trying to find a solution for this (not a workaround, as it will probably break in the future) or I’ve goofed up in the first place and only now It says that I goofed up haha.
For reference charts behave like they should be.
With kind regards, Michiel

So I was fiddling around with the program and settings, figuring out why not make it anew. So I did, this is what I found (see screenshot attachments). To my understanding this hints to a bug…
Can I get an confirmation on the matter?
For now I’m gonna switch back to 24.04LTS again…
Task and Events page
mgnKBgIgib.pngData Logger Sessions
PLCNENG64_6SijntoynL.pngVariable in JustaTest
PLCNENG64_r2QstU3uwY.pngSettings Chart1
PLCNENG64_fVfPqpWGOq.pngError Message
PLCNENG64_3JgtWLTAjk.png

I get the same:
(all tasks are cyclical)
image.png

Hi again,</p>While now the Modbus_TCP 16 is out now I’ve come across the following.</p>„HMI0018: Building HMI page ‚Trends‘: The data logger session ‚ChartyChart‘ and chart ‚Chart2‘ contains variables from idle task (use cyclic task variables only).“ (Got multiple of these „Errors“)</p>This error was not present in 24.04LTS and this error shouldn’t be there. Nothing in the changelog (to my knowledge) notes that something has changed in how the data is handled.</p>I’m trying to find a solution for this (not a workaround, as it will probably break in the future) or I’ve goofed up in the first place and only now It says that I goofed up haha.</p>For reference charts behave like they should be.</p>With kind regards, Michiel</p>

Can you send us the project? This way we can figure out what the bug excactly is. You can send it to support@phoenixcontact.nl.

Hi
Question: Are All tasks cyclic? I’m able to reproduce this error message by simple adding a non cyclic task (that does absolutely nothing)
For example: my event task runs the NewProgram (does nothing as you can see) but still generate the same error message even thought the test is a cyclic taks.
image.pngimage.png
Best regards

Hi [@fluxmodel</a></p>Question: Are All tasks cyclic? I’m able to reproduce this error message by simple adding a non cyclic task (that does absolutely nothing) </p>For example: my event task runs the NewProgram (does nothing as you can see) but still generate the same error message even thought the test is a cyclic taks.</p>[https://forum.plcnext-community.net/uploads/G3AL4AK01I8Q/image.png</a></p>[https://forum.plcnext-community.net/uploads/RRSXR4174QK6/image.png</a></p>Best regards</p>

Hi,
No - i was mistaken in my prev post.
I have two event tasks (exception and stop) - but their variables was not connected to the graph in any way.<
It’s good news that you have recreated the issue :slight_smile:

Hello &
The error message you’re encountering typically appears if there is any task type other than a cyclic task configured in the ESM. This happens regardless of where the recorded variable is used.
I’ve verified that this issue has been addressed in the upcoming Hotfix 2025.0.1, which is expected to be released within the next two weeks.
Best regards,
Ruben,
Phoenix contact NL

Thank’s for the update, Ruben

Thanks for the update I will close the topic =)