Ok I got the time working now. So now you can select the time (down to the tenth of a millisecond) to start the textual and graphical display as well as the time (again tenth of a millisecond) to stop the display.
I think everything is pretty much done. Any suggestions? I just need to configure the program to output the correct XML format now :lol:.
Here is the newest shot:
Slick... Very slick!
Very interesting I have a project coming up i want to work on for work that has
data logging if you want to see if you can accomodate.
i need to count and stamp when the inputs are active
so for DI 1 count how many times it was pressed at what time and how long
I have 9 inputs i need to count eventually.
the project will go much deeper then that but that is one part
also how many time the button was pressed in each hr of every day.
It is for monitoring a piece of machinery when we would like to know how often it was used
what time of day is busiest, what is the life expectancy of the machine at the current rates,
is the equipment being misused my the user all kinds of data if possible. Then later i would
like to add a camera to monitor the equipment to see what something breaks and how it
happened. This will give the maintenance people alot of info to fix it when it breaks down.
anything else you can think of would help to
data file size and utility:
Is there a maximum amount of data that can be stored for any one sensor?
Will it 'roll' to keep recent values in event max file size is reached?
Can data be cleared for just one sensor? For a given timeframe?
Is it always going to be working, or must it be turned on prior?
What about hitting record and having it permamently save to file the last few minutes (or similar) of data? Turning on could possibly be triggered by an input (i.e. when braking, it knows to store rotor temperature for a set time or duration of the braking, stuff like that, for 'black box' functionality, or for parents keeping an eye on childrens driving habits: when they go too fast, it starts recording, or data saves in the even of a theft)
Sorry I didnt respond to this sooner I just saw it. Also, logging must be turned on and then it logs until it is turned off. You can create an other button to start/stop the logging.
I will try to find a way to store x amount of data points in memory without creating huge bogged down systems because for every sensor it is storing like 1000 data points in RAM! I will see what I can do.
The reason I dug up this post is because I am now finalizing the logging, and well I am now adding a lot more. :D It is never finished lol.
I know someone mentioned they wanted comma seperated lists... I just realized that Excel opens XML files natively. I think any version over 2003 does! So you can just open open the log file directly. So in that case, a comma seperated list seems unneccessary... What do you think?
Also do you prefer 1 consolidated log as in the new version, or multiple logs spread out in different files in a structural/folder layout? I like the single file, but I am not sure if it can get too large that way. I need to add some protection for that.
I'm cool with one log, based on the number of sensors any one installation will have, especially if the data can be chooped up with respect to time, kinda like you mentioned.
How are you differentiating each 'recording'? Is there a field with a unique identifier for a recording instance, or something like that?
I dont think that should be too much of a problem. (Famous last words <cough>y2k</cough> :lol:)
Ok, testing the size of the data and I am now satisfied with it. :)
It turns out to be 470bytes per data point.
So some figures:
1 hour worth of recording at 1Hz: 1.6Mb (temperature or something)
60 seconds at 180Hz: 4.8Mb (performance testing)
1 full day at 1 data point a minute: 116Mb
I dont think that is too bad. Expecially for all the data stored. I think I am going to actually take some repetitive data out, so it is "back to the basics" with it. Or I'll just add another option in the skin file :lol:
So I think those sizes are reasonable, no?