TTD log configuration error
I recently tried to configure around 400 direct OPC logs(30s data collection Direct log) and that leads to a slow Operator workplace(800xA for Advantmaster).
Then I deleted all 400 logs to make the operator layer faster.
I came to know that 800xA for advantmaster having TTD(Time Tagged Data) log configuration option (log stored in controller). I would like to verify the procedure to finalize the TTD log configuration.
1. Verify the TTD source service groups are operational (Service state)
- Navigate to TTD Node configuration synchronize view
- Click on Upload. This will create log template and log configuration aspect based on controller TTD log configuration.
- If need to extend the log, then modify the uploaded log template.
Let me know anything else to be done to use the TTD logs from controller?
While trying to upload the log configuration via sync view got the timeout error, attached
While trying to access the controller view got the attached error.
How to finalize the TTD logs ?
Voted best answer
For your information only regarding the use of OPC logs in combination with AC 400 controllers. which is OK to use and very common today because of its larger flexibility
in subscription rate changes and history time scope.
When using OPC logs together with Ac 400 you must stick to the AC 400 subscription rules. 1, 3 or preferably 9 seconds update rates only.
Subscription rates higher than 9 seconds are forbidden as they will load the RTA board and the Controller more than 10 times more compared to a 1, 3 or 9 sec
normal cyclic subscription, as we have to emulate a cyclic subscription by using demand subscriptions.
Regarding the use of TTD logs in the AC 400 controller.
First of all you have to dimension for and create TTD logs in the controller.
If already created you cannot change the times_pf (number of samples) per log after you have created the log.
If you try to do so with FINS & GINS you may stall the controller.
Once the log(s) are created the times_pf value is impossible to change as this log will allocate its needed memory size from free space in system at the very first
diconfig after you have created the TTD logs.
The only possibility to reconfigure TTD logs is via a new source code reload of the complete controller, with new larger times_pf value and changes sample rates.
You must also have enough AC450 "free space in system" else the TTD tasks will abort when diconfig.
Sum size of the TTD log element must be less that AC450 free space in system the first time you start the controller w Diconfig, after creating TTD logs in Ac450.
The controller must be prepared (dimensioned) for the TTD tasks to be able to startup and accept download of any TTD log configuration.
You can try to ACT DCTA100 (a startup task that wakes the other three and then stops itself) if you see system messages like 10 19 after the ACT, your config is no good. Probably in need of DIMDB...
OPC logs are OK too, but as Jan-Erik writes, stay on 1, 3 or 9 cyclic rates only with 9 being the most lean. A "slow" 30 second log will drain several time more CPU load than a 9 second log - read the AC400 Performance Guideline, 3BSE042621 on ABB Library and you will learn why.