Slashdot Mirror
Datalogging Using Open Source?
trd79 asks: "I am responsible for setting up a system to monitor various parameters on a factory production line (mainly chemical flow rates and temperatures).
I am currently using a datalogger from dataTaker and using their software (on a WinXP box) to graph the data in real time and download the data from the logger at the end of a shift. I would like to make the system more robust and reduce the need for user intervention. Does anyone know of open source data acquisition systems which are able to interface to popular datalogger brands? The ability to produce real time plots of the data during logging would be an advantage. Buying a new logger would not be a problem."
"I don't really want to have to rely on the current XP system, as I don't believe it will survive being left on its own on the factory floor for long. Automation is key, as the line operators often forget to start/stop/download the logger. I would be interested to know if anyone have set up similar systems and if so, how well it worked."
Isn't this the way new Open Source projects are started?
As long as you have documentation on the data structures coming out of the datalogger, you could probably build your own.
Disclaimer: I haven't actually used a datalogger before, but I have looked at documentation for one or two.
This is slashdot, what do you expect?
Key problems:
"I don't know how to setup windows XP so it runs reliably"
"The existing/included datalogging sw requires user interaction"
First of all - data logging companies make expensive hardware, and supply software to suit the user's needs. If your current company cannot provide sw that requires no user intervention (ie, has triggers based on time, events, etc) then I suggest you talk to other equipment makers. You will undoubtedly get a response. This solves the second problem.
If you have no experience in setting up windows XP so it runs reliably, then find someone who does, or find a data logging company that has software for your OS of choice. Contrary to popular belief (especially here) XP is very reliable. Do a bare minimum install, enable the firewall, and don't let people use it as a general computer. Just as with linux, don't load anything on it you don't need.
Open source is not a solution to these two problems any better than closed source is. Is there another problem that you haven't explained? -Adam
fucking lazy bastards, i swear. /.
r oups/dataloggers.htm
why dont you put in some fucking time on google before you post on ask
http://www.pine-environmental.com/
http://www.sixnetio.com/html_files/products_and_g
http://www.q330.com/
http://www.capgo.com/Products/Software.html
I run a business in Industrial Automation, and have written some substantial data logging, plotting, and reporting systems for clients due to the fact that it's not easy to find products that do what they need (or can do it at an affordable price). Sound's like you're running into that same wall. Most of my programming is middleman code between PLCs and SQL Server or Oracle, with the occasional logging to Access or a Text file.
:) If you have any more specific questions, ask away!
Unfortunately I can't share my projects due to NDAs. I don't have any open source projects of note to point you toward either, the Industrial world is closed to the extreme. It's a bitch sometimes just getting communications protocol info for a device. Anyway, like the old saying goes- "If you want something done right, do it yourself". I noticed the manufacturer of your device has an ActiveX control available to help you create your own software, so you're one step ahead already! You should download it and code away... It's not hard to find sample code on the web that shows how to write to a db/file format of your choice. The same goes for plotting data points.
Finally, if that XP Computer is not in an enclosure try to get it off the production floor. If you don't have Ethernet capability in your device, run a couple hundred meters of shielded twisted-pair wire and communicate over RS-485 from the saftety of an office. If you have a lot of these boxes floating around, try to create several runs of a few devices each back to a RS-485 multiport card/box to keep the 485 network snappy (try ConnectTech if you don't know where to start). I did a power monitoring system for a particle accelerator just like that in the late 90's and it is still in use today.
Sorry I couldn't be of more help
Urge to post... fading... fading... RISING!... fading... fading... gone.
According to a datataker forum post in response to a question about the DT515 Linux:
/dev/ttyS0") to capture the ASCII data.
The dataTaker transmits and receives simple ASCII commands. You can use any simple terminal program to program and recive data from a Datataker data logger.
Wonder if this would work for the DT80. If you connect using a serial cable you can use the Linux cu command (something like "cu --parity=none -s 115200 -l
From there you can probably pipe into gnuplot
Always happy to help anyone move to Linux.
I am not sure if this is entirely what you are looking for but MRTG is an open source SNMP monitor. It may work in your situation if the logger supports snmp. It can be a ittle tricky to use so recomend looking for configuration tools or the configuration file help on the MRTG website. On the plus side it will create 5 real-time graphs updated every x minutes for each variable you monitor, going all the way back to daily averages for the year. It works on windows xp and is easily migratable because it is written in PERL.
Enjoy and i hope it works
I wrote a pretty good article on how to do this for Circuit Cellar awhile back. You have to buy the article, but a summary and all of my source code are available online here:
http://www.nyx.net/~smanley/palmadc
The code isn't the greatest, but it will get you started. The article is also linked to, and isn't TOO out of date.
The AVR has a open-source compiler based off GCC, the schematics are there, the palm stuff is open source.. it doesn't get much easier than that. You need a very basic opamp buffer and away you go.
I haven't had time to update my site in a long while, but if you contact me, I can send you the information you need to get started with a PCB based around that project. It was all built with open source tools, and I don't mind sharing.
Perhaps if a few people email me I can justify another run of PCBs.
..don't panic
Gnuplot is pretty flexible, open source, works on Windows XP, and you can interface to it easily from C code, as well as other languages. The code is a bit of a mess, but I've made a few changes to implement backbuffering for real-time plotting. That way you can easily do 50 fps, without screen flicker. Of course you do have to write the interface code yourself, to grab the data from the hardware, and push it out to the plot. In my experience all hardware vendors provide decent libraries for talking to the device. On the low end Measurement Computing works fine, and on the high end you might look at National Instruments.
Take a look at www.abacus4.com. Sorry we're not open source, but we are cheap, and would probably do this job for you in a nice, simple way.
ABACUS4 is a process control and SCADA system which runs under the Linux Operating system on industrial PC hardware using a large range of industrial process I/O subsystems.
We can supply anything between the system software alone, up to a complete turnkey packaged system.
Contact me if this is interesting to you. Good luck!
Sorry, nothing profound to put here! (http://www.abacus4.com/
The ability to produce real time plots of the data during logging would be an advantage. Buying a new logger would not be a problem.
In the open source world, I would look for small tools which satisfy your need when setup together in concert.
For producing real time plots, my choice would be RRDtool:l /
http://people.ee.ethz.ch/~oetiker/webtools/rrdtoo
cheers.
Well, if your requirements aren't too beefy (technical term) try labjack. They have kernel drivers for the cheaper model ($119) and the pricier one ($399) uses ethernet and works over TCP/IP. There are links to Perl/Java/.NET/MATLAB interfaces, among others, on their site. The cheaper U12 model support a dozen analog inputs, 20 digital I/O, and 2 analog out. The pricier model has PWM output and support for various timers and whatnot.
http://www.labjack.com/labjack_u12_downloads.html
Modbus is an open protocol, you can get the specs at this website. I don't know if there is an open source data acquisition program, but if there is one, it's very likely that Modbus is supported. If there's not such a project, I am sure you can find code on the net to communicate to Modbus devices