My (biased) recommendation is to use FactorySQL (I was involved in designing the software and still do some contract work for Inductive Automation) and log data to an SQL database. Kepware, Matrikon, and Software toolbox offer similar products. All are OPC clients. Advantages using a database over a spreadsheet are:
1. Designed for lots of data - Excel supports 64k rows, I think
2. Can query the data and have indexes (including getting a .CSV dump to open in Excel). It's particularly hard to do analysis across files in spreadsheets.
3. Support backing up/maintaining the data
4. Scalable.
The bigger problem than the storage format is the fact that Excel sucks as a program to do the datalogging (if you expect it to always run). A program that runs as a windows service and is designed to always log works much more seamlessly. The DDE link in between is worse yet.
So an application designed to log to spreadsheets could be fine. If your requirements are minimal, not likely to expand, or only for legal requirements, then spreadsheets are ok.
Inductive Automation is currently developing a free, datalogging version of FactorySQL. I don't know what kind of limitations to expect, maybe 30 tags or so. FactorySQL currently doesn't log to .CSV, but they're programming in support since customers ask for it. I think it's a bad idea in most cases, but that's beside the point.
SMOKE said:
This logs data only correct. You cant use it to read?
surferb has been in the middle of all these topics. What is the best way to send and recive data. OPC, SCADA ???