Real-time logs data from the Datalog (if specified) and fills in around that logged data with Live data from when the trend window opened. If so, perhaps try changing it to Poll historical data. See if it is set to Real-time data server. Open the trend configuration and look at the General tab. Typically this results in data being missed, not a shutdown of the datalog itself. What can sometimes happen with this tool is it can be requesting Live Data along with historical data from the data log. For the moment let's assume you are using the normal trend tool. FactoryTalk View SE added a new type of trend a few versions back. Is there a defined secondary backup location that is local to that PC so if we do lose communications we can log locally until comms are restored?Īs for trends. If it is remote, is there a possibility that we are occasionally losing communications with that location. It is possible we are just overloading the communications.Īlso, I would look at where the data is being logged. I would take a look at all datalogs that are running, how many tags they are logging, and how often they are being logged. Unless as mentioned, too much data is being requested and it is choking the system. Displaying a trend shouldn't impact logging. Appreciate your help.ĭatalogging is a task that runs in the background. I already datalogoff and on then change the path. It seems that it suddenly stops at showing trends. I need your help with my factory talk se.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |