HMIST6500 periodic trigger broken

[Sbracke]

Has anyone encountered problems with the Periodic trigger in the globalscripts section of the HMI ?

I have a program with a 1 second periodic trigger and noticed that after a certain amount of time this trigger stopped working.

To test it i wrote a test program that counts a number every 1 second and after 4294967 seconds (around 50 days) the number doesn't update anymore. After a reboot of the screen the trigger starts working again.

i am running the latest firmware and program with EOTE V3.2 SP2

At the moment i reboot my hmi's every month to prevent this error from occurring but this is not ideal.

On an unrelated note: the Labels you get to choose from to post on this forum make very little sense.

[Bastian_Schmitz]

Hello,

Till yet I did not see a problem like described. 

Which datatyp did you use to count the values. 

Your maximum number looks really simular to the maximum possible value of UDINT/1000 

I did not think that these is random.

Did you have some screenshots of you script.

[LeTomas]

Hi @Sbracke ,

I am not sure why you are trying to count 50 days in seconds 🤔 maybe if you can explain to us what you are trying to do we can come up with something.

In the next link you can find an example of how to count time in the HMI:

https://schneider-electric.box.com/s/6026ssi7j99p4us8hnb1qe2aw2ob5s8v

Link project 

Probably you can use something similar in your code to avoid that behaviour.

Best regards,

LeTomas

[Sbracke]

Here are some screenshots:

globalscriptsvariables

This error also occurs when there isn't a counter for the total amount of seconds. My first test had only had the 2 log integers.

I added the total counter to see if the error occurred at a " standard number". And as you said, this appears to be the case.

but since the script specified to loop my counter value and it is a 1000x difference from the maximum. it seems more likely that in the firmware there is a problem with the periodic trigger after the UDINT maximum in miliseconds

[Sbracke]

@ LeTomas:

I'm not trying to count the time in seconds. This was just a test to see when the error occurs.

In my actual production program the periodic trigger is used to copy one variable to a second variable every second. 

this program also stops working after a certain amount of time.