Autodatalogger Completed v1.0
SRLM
Posts: 5,045
I've finally completed my first major PASM work. This is an autodatalogger program: feed it a series of variables, set it loose, and it will quietly log the variables in the background. It uses the Parallax Datalogger USB thumb drive interface, which allows the data to be read easily on any computer as a txt file.
For legacy purposes, here is the old thread.
For the complete documentation (including benchmarks), open up the file.
Things I've learned about the Datalogger (that don't seem to be documented):
1. Flow control is essential. No ifs or buts: your program will not work without it, even at 9600 baud.
2. When changing the speed, a delay is required after receiving a reply. I found 1/16th of a second to be the minimum.
3. Speeds differ based on the USB drive used. If your Datalogger code is too slow, try a different USB drive.
4. When a critical failure occurs (power loss or drive removed), all data up to the last close is lost.
5. When a new line is required in a txt file, a CR and LF is required, not just one or the other.
6. Opening and closing a file requires lots of time and can halve the effective data rate.
Anyway, I've added pretty much everything that I think it needs. The one thing that isn't implemented right now is logging of negative numbers, but that may (or may not) come in the future. Does anybody have any requests or suggestions for improvements?
Version 1.0 attached below.
Post Edited (SRLM) : 9/1/2009 3:03:17 AM GMT
For legacy purposes, here is the old thread.
For the complete documentation (including benchmarks), open up the file.
Things I've learned about the Datalogger (that don't seem to be documented):
1. Flow control is essential. No ifs or buts: your program will not work without it, even at 9600 baud.
2. When changing the speed, a delay is required after receiving a reply. I found 1/16th of a second to be the minimum.
3. Speeds differ based on the USB drive used. If your Datalogger code is too slow, try a different USB drive.
4. When a critical failure occurs (power loss or drive removed), all data up to the last close is lost.
5. When a new line is required in a txt file, a CR and LF is required, not just one or the other.
6. Opening and closing a file requires lots of time and can halve the effective data rate.
Anyway, I've added pretty much everything that I think it needs. The one thing that isn't implemented right now is logging of negative numbers, but that may (or may not) come in the future. Does anybody have any requests or suggestions for improvements?
Version 1.0 attached below.
Post Edited (SRLM) : 9/1/2009 3:03:17 AM GMT
