DIY Zoning: Data Acquisition |  |
- Installation: Easy Way (RPM)
- Configuration Considerations
- Installation: Hard Way (compiling from source)
- Next Step
Installation: Easy Way (RPM)
RPMs relevant to data acquisition (available here) are:
- dz-common - Java code common for all the modules.
- dz-dac - the Data ACquisition module.
The first thing to do after you've installed these RPMs is to run the dz_dac_wizard tool - the DAC configuration wizard. It will create the configuration for the DAC.
When you are done with the configuration, you may run the DAC script: dz_dac.
Configuration Considerations
Please refer to DAC section of the Configuration Guide.
Installation: Hard Way (compiling from source)
Please keep in mind that your feedback is sought, and your requests are honored - you'll have to try really hard to come up with something extraordinary. Therefore, if you have a problem, just tell me about it.
Compilation instructions for the "hard way" will not be provided - if you need them, you're not ready (hint: there's a very detailed INSTALL file in the top directory of the source tree). I've tried really hard to make the build process very, very thorough and reliable. Some of the configure script options are documented below. However, should it fail, like I said above, your questions will be answered and requests will be honored.
Configure time options
The first step in compiling the software is running the ./configure script. You can specify the options on the command line, or create the permanent configuration options file. Two locations for it are recognized: global (in /usr/share/dz/configure-options), and/or local (configure-options file in the project top level directory). Below is an example of a configuration options file:
--prefix=/opt/vt/dz
--with-1wire-port=/dev/ttyS0
--disable-JRobin
--enable-rrdtool
You can get the full list of options by running
./configure --help
Some of the options are intended to customize the application to the runtime environment (there are usually sensible defaults for them), and some are intended to provide a configuration.
Next Step
By this time, dz_dac is busy collecting the temperature data for you. Time to see what's there: Visualization.
