I am redoing the part of the application that datalogs. It will be spiffy when done. :)
My question though is what do you want to be able to log? Obviously the time the data was taken, and the value for each sensor, but anything else?
Printable View
I am redoing the part of the application that datalogs. It will be spiffy when done. :)
My question though is what do you want to be able to log? Obviously the time the data was taken, and the value for each sensor, but anything else?
Is there really anything else to log? ;)
Yea, it's ususally easier or better to add everything while your doing a section/function than it is to go back and add it latter...
Besides all the sensor value's, min, max, and avg, I think that should cover just about everything...
Teaser picture :p
http://img396.imageshack.us/img396/1995/teaserhq7.jpg
It is not done yet. I would say 50% functional. But the main stuff is there. Obviously the dates are incorrect. :D as they were just random testing numbers.
Logs will now be stored in *.xml format and easily readable in Flash, through a *.xsl guide, or any webpage. Say hello to remote logging. ;)
Unfortuneatly, because of the way FF reads xml files, I have not been able to get it to work. I need to remove all the whitespace in the xml i believe, but for now, it is all done through ActiveX. The sucky part of this, is that ActiveX is only available on Microsoft Internet Explorer. Not FF. So as of now this does not work in FF, but as it is my browser of choice, I will eventually get it to work. I have never worked with xml reading before. Also it is all javascript run so you need java. Since I think it is a good assumption most of your PCs dont run php/mysql servers locally, I had to do it all "client" side which means javascript.
I have a few more ideas up my sleeve... Stay tuned.
Opinions and criticism welcome.
Sounds cool, looks cooler =]
I was just thinking, exporting to .csv would be nice too so users could play with the numbers manually in excel or something =]
Well the reason for xml was that I thought all Office products can read xmls quite readily as well as pretty much anything nowadays...
ill think about adding in a comma seperated output file. The thing is, the more read/write cycles to the harddrive, the more time per iteration, more cpu cycles, slower. Now I am not worried for any of my machines, but I am not too sure about how much a m10k can handle.
Well anyways, I'm off to bed.
Keep the suggestions rollin'! :lol:
Add an option to either output csv or xml, or an option to spit out csv values from the xml after the fact with a lil button, so only those people that want it can use it =] Of course, make a way to spit it out without having to press it, via a window message command or something, in case we wanna automate it ;)