![]() ![]() Second, you can trigger the data logger to only log an entry whenever the counter changes. By monitoring the counter for missing or duplicate entries, you can easily detect problems in your data tables when problems occur. If you simply add a simple counter and increment it every time your datestamp (or whatever you want to log) changes, you get two things. ![]() I spent days trying to do it that way and eventually out of desperation came up with a much easier way. You can attempt to use the DISTINCT SQL command to try to eliminate duplicates, but.let me just say good luck with that. If you are measuring "things" like in a discrete manufacturing process, if you simply start logging date stamps on a regular basis, you'll get a huge table but your interest is only in logging when things change. This is great for continuous processes but lousy if you aren't measuring "stuff" like gallons per minute or tons per hour. It automatically logs data on a time interval, say once a minute. By default, the data logger is always set up great for processes. I'm also going to highly recommend that you add a counter along with your date stamp. It's just that how to put it together gets a little confusing. ![]() I'm going to go out on a limb here and assume that first you've managed to start logging SOMETHING. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |