6/15/2023 3:54 PM | |
Joined: 2/1/2023 Last visit: 11/29/2024 Posts: 7 Rating: (0) |
In Desigo Insight, we were able to create On-Line and Off-Line Trend Views. The On-Line Trend Views were used to view data points which may not have associated TLOs defined at PX level. When setting up the view you could set the view to continually save. This saved the collected data into the database. However, when the Trend View was closed down the saving of data stopped. The next time the Trend View was opened, it would again collect and save data whilst the view was open. In CC we don't have that option. When a Trend View is created and run, the data appears only on the graph. When you come to close the View, you are asked if you want to save the view, and everything about the save process refers to the View, not the data. However, the act of saving the view, also creates TLOs on the server for Online datapoints. These TLOs now collect data until the related series is removed from the Trend View, when you are given the option to delete the TLO as well. This creates quite a lot of traffic that is not required. The TLOs are getting the data depending on the COV setting of the associated data point. When a trended object is removed from the view, you are prompted to also stop collecting the data on the Server, which if you do so deletes the TLO on the server. The series disappears from the View, but if you don't then save the view, the removed points are still there the next time you open the View, and the points start to be trended on the View. The question is, can we create a Trend View which when saved DOESN'T create a TLO for online objects, or is there a way of stopping the TLOs from collecting data until the view is re-opened? ------------------------------------------------------------------------------------------ |
Last edited by: Jen_Moderator at: 06/28/2023 09:15:06New subject after splitting |
|
8/31/2023 3:50 PM | |
Joined: 2/1/2023 Last visit: 11/29/2024 Posts: 7 Rating: (0) |
Lorenzo, Apologies for my late reply, but thank you for your help. Dave |
Follow us on