Archiving Time Dependent Smoothing Time Change from Vision

[chandra]

Hellow Everyone,


Is it possible to change the Time-Dependent Smoothing Time from VISION? please find attached image for more information.

If it is possible if I change the Smoothing time form VISION frequently(once in an hour) how it will affect on Archiving process?
is it affect on instantly or it will take time?

[leoknipp]

Modifying configs is possible using a dpSet() on the configs + attribute you want to change.
Which attributes are existing is described in the WinCC OA documentation: Reference tables --> Data point configs.
Depending on the config you want to add you have to set then several of the attributes. Sometimes it is necessary to use a detail number (_config.detail number._attribute) to be able to set all attributes.

If the settings are changed the new settings will be used when the next value is archived.

Why do you want to change the config every hour?

Best Regards
Leopold Knipp
Senior Support Specialist

[chandra]

Actually, Custmor requirement is like they want to define an Archiving time for some particular DPE's in VISION it will differ based on a test on the machine and they want to monitor those Archived values in a table format and as well as in Trend format.

Is there any table control for showing Archived values?

[leoknipp]

With the Event Screen (System Management --> Diagnostics --> Event Screen) you can read historical values and show them in a table.

Best Regards
Leopold Knipp
Senior Support Specialist

[a_labropoulos@akatt.gr]

Hello,
I would like to record in the database a value from a dp element every day at 00:00:10 regardless of whether its value has changed or not, is this possible? I tried setting :archive..archive to true but it didn't work.

[leoknipp]

Normally in WinCC OA values are only archived when they are changed. At the _archive config you cannot define that the value shall be saved at a fixed time.
Your requirement can be fulfilled by using a statistical function which is calculated in a 24 hour interval with a sync time of 00:10.

From a reporting point of view it does not make sense to save a value (in a cyclic interval) which was not changed.
When you want to know which (archived) value was valid for a specific time using the function dpGetAsynch() you will get the result, independent of the fact when the value was changed.

Best Regards
Leopold Knipp
Senior Support Specialist