TM172 task time

[otrotabi]

I start a new topic but this is actually continuing this previous post (https://community.se.com/t5/HVAC-and-Pumping-Forum/Application-cycle-time-is-greater-than-2000-ms/td...) dealing with task time using PIDAdvance.

Following @FedericoM  ´s advice, I decided to exclude all my programs from the current build, keeping only the one that actually shows me task time, and later adding programs one after the other until I found the guilty one. I also cleared HMI´s program.

Much to my surprise, task time is about 5 secs, so there´s something wrong here I think either regarding what information sysTskTmdMaxExeTime is giving or how to make use of it.

Just to make sure I was doing it properly, I started a new project from scratch and results are basically the same.

The pictures are from a running TM172PDG28R.

[FedericoM · Accepted solution]

Hi,

the execution time of your project is: 4,7ms, unit measure of this variable is microsec

[otrotabi]

Ok. That´s a relief. 

Then I still need to find out why PIDAdvance complains about the 2000 msec task time. I will figure it out.

Regards

[FedericoM]

It might happen during an application update

[otrotabi]

Now that you mention it, it was usually the case and probably the best explanation. I was not using PIDAdvanced´s alarm and decided to include it as an alarm after that issue appeared.

Anyway I did move PIDAdvance FB to a program running as a background task in case that helps.