Trigger tag is actually presented on the second picture above. It is an Int (coming from PLC logic) and values what I am giving to Trigger tag are around 10-20, the upper limit is 100.

In HMI tags-->each Tag Properties-->Settings)  both tags (trigger and for logging) needs to be set as  Cyclic continuous?  In Historical data --> Logging tags Acquisition mode what should be set for logging tag?

In Event: Change on exceeding (for triggering tag): which and what are the orders of functions which needs to be set?

Greetings,

I have set as requested below:

In Historical data -> logging tags --> Acquisition mode is 'on demand'.

Both (for logging and triggering) tag properties are set a 'Cycle continuous'.

The function LogTag is tested on: when Trigger tag is greater than 42. (I have changed upper limit)

The function LogTag is tested also on: Events --> Value change where only function 'LogTag'  and the tag I want to log are specified.

Current value of trigger tag, as Integer coming from PLC, is 44.

Please take a look at the picture attached.

Sorry for all these troubles, but still not luck :(

Greetings,

version 15.0. update 4 (step7 prof/winCC adv)

Yes, HMI is rebuilt, recompiled (right click HMI-- compile--software (rebuild all)).

I have done it again and tested. Now trigger tag is 48, no value in txt report (log).

I am testing all this on PLCSIM and WinCC RT simulator, not on the real hardware.

Do trigger and logging tags need to be in some special cycling interrupt OB inside PLC or they can stay in Main OB (OB1)?

If necessary and possible I can send the project simplified file?!

:(

Hi,

In addition to above stepwise procedure also in "Historical data" under "Data logs" the column "Enable logging at runtime" needs to be enable (specified) and then I am getting report done as needed.

The only issue is when this Enable logging at runtime is active I will get also logging when HMI starts, which I can disregard....

If I disable this "Enable logging at runtime", no luck with report.

Also, If I disable this "Enable logging at runtime" and have order of system functions under Tag Event-->Value change like this: OpenAllLogs and Log Tag, I will get the same as attached.

If you have some idea how to avoid initial (Runtime start) logging this will be even better.

Hope to hear from you further.

Hi, 

AutoGen_6098795

Hi,

In addition to above stepwise procedure also in "Historical data" under "Data logs" the column "Enable logging at runtime" needs to be enable (specified) and then I am getting report done as needed.

The only issue is when this Enable logging at runtime is active I will get also logging when HMI starts, which I can disregard....

If I disable this "Enable logging at runtime", no luck with report.

Also, If I disable this "Enable logging at runtime" and have order of system functions under Tag Event-->Value change like this: OpenAllLogs and Log Tag, I will get the same as attached.

If you have some idea how to avoid initial (Runtime start) logging this will be even better.

Hope to hear from you further.

open all logs is not starting the logging, yet. You also have to use the system function StartLogging(Log_type, Log), if you don't want to start logging with the runtime. But maybe even then there might be an entry when starting. 

Regards,

Frink

Greetings,

you were right. During Runtime startup the upper limit value of this trigger tag was 0 and trigger tag was also 0. So this activated initial logging, during RunTime startup. When I have changed upper limit value to 1, and started RunTime again, it works.

Thanks for all the help!