Hi 灿若星辰970,

I am not sure where you want to query the data. But at least you can check the db files located at "C:\Data record". Your tag logging segments should be in a path like "HMI_RT_1_TLG1234", where "HMI_RT_1" is the name of your HMI in the project, "TLG" stands for tag logging and "1234" is an internally created ID.

Kind regards
Stefan

Hi 灿若星辰970,

Yes, if configured properly, the trend control should display the logged tag values. However, since you are reporting problems, I would check the database files first.

Kind regards
Stefan

Hello 灿若星辰970

have you checked the SQLite files as suggested by Stefan?

Are there files in this directory? do you get some error messages or Systemalarms in Alarm View that something with the tag logging does not work?

Check if there is still enough space on your C partition

Bye Murof

Hi 灿若星辰970,

If the system alarm says that TagLogging is not working, it will not restart by itself. Depending on your device version, the StartTagLog system function may be available, but I doubt it would help.

So you would probably have to restart the whole runtime. But to be honest, since there must have been a reason why the logging stopped, it is very likely that it will stop again eventually.

Maybe the reason that caused the problem in your case has already been fixed in a newer version. So you should check if you have installed the latest update for the runtime. It might help to see some reason when using TraceViewer, but for that you should run TraceViewer in the background for a long time and configure it to store unlimited traces. Within TraceViewer I would filter the Application column for WCCILdata, WCCILpmon and WCCILtlg.

But to be honest, reading the trace logs is not easy and in many cases it will point to a problem that needs to be fixed by development. So it might be better to contact technical support.

Kind regards
Stefan