Got questions? You’ve come to the right place.
Hopefully you’ll quickly find the answers you seek on this page. For manuals, application notes, and unanswered technical support questions contact our support team using the form at the bottom of the page.
The eosAC comes standard with a 30 m / 100ft cable and the same length of gas tubing. This length corresponds to the maximum tubing length recommended by Picarro.
The eosAC is compatible with the Los Gatos Research (LGR) Ultraportable Greenhouse Gas Analyzer (UGGA) and the following Picarro gas analyzers: G2131-i, G2132-i, G2201-i, G2301, G2308, G2401, and G2508. eosAC chambers are connected to the gas analyzer using the eosMX or eosMX-P multiplexer.
The eosAC hardware and software are designed for easy integration with the LGR UGGA gas analyzer. Application note #AN0007 walks through setting up your system.
The eosAC hardware and software are designed for easy integration with your Picarro gas analyzer. Application note #AN0003 walks through setting up your system. Once the Windows-based autochamber software is unzipped on your desktop, you are ready to start scheduling chamber measurements.
The slow speed eliminates pressure effects.
Align the tab and push gently to seat the connector, then maintain light pressure while tightening. Be careful not to force the connector, as it may bend the pins.
These ports allow additional sensors, such as soil moisture or temperature probes, to collect data alongside the flux measurements. Data from all sources is collected and processed by the eosAC software, eliminating the need for recombination.
The autochamber is water and dust resistant. However, the unit should never be operated while immersed in water.
Clicking on an empty part of the screen will refresh the display. If this does not resolve the problem, try changing the X-axis plotting type (Measurements, Timestamp, etc). You should also check that at least one of Show Lines or Show Symbols is checked in the Plotting Options window. If the problem remains, restart the Chamber Data Processor Software.
The majority of processing time occurs when the data is being fit to linear and exponential forms. If the chamber concentration data is particularly unusual, this can increase the fitting time significantly. Once the measurements have been imported, inspect measurements visually (via the Measurement Settings window) to ensure that the data is correct. In addition, the estimation of flux fitting errors/sensitivities can be very time consuming. If you have increased the error reps value beyond the default 3 (Chamber/Analyzer Settings window), try reducing this value to decrease processing time. If you have turned on symbol plotting from the Visual Options window, disabling this feature can increase plotting speed, and plots can be temporarily hidden entirely from the Hide Plots checkbox.
Ensure that the analyzer root path has been set correctly by choosing Analyzer Data Path from the Data menu and navigating the the proper directory. One or more folders indicating year (e.g. “2014”, “2015”) should be visible when clicking OK from the pop-up window. Double check the time-frame in which the measurements occurred and/or try expanding the data interval. Ensure that the Analyzer Local Time option has been set to correspond with the analyzer clock setting at the time the data was recorded. If you are processing data on a separate computer, check to see that all of the relevant FRMonitor_0000.log files are present. Finally, note that very short chamber measurements (typically < 45 s) will be dropped.
Gas flows into the chamber from the soil surface, while atmospheric air enters through side membranes into a separate cavity. The difference between these two concentrations over time is compared with the known (“forced”) diffusivity of the FD membrane, resulting in a value for the soil flux rate.
Traditionally, flux measurements are performed using accumulation chambers. This method leads to a build-up of high concentration gas within the chamber, which can perturb the soil profile and lead to biased estimates of the flux rate. The forced diffusion method greatly reduces the concentration build- up – avoiding the biasing effects of lateral diffusion without the high energy demands or complexity of typical dynamic systems.
The current model measures CO2.
The eosAC has no external moving parts, its sealed body is thick acetal plastic, and it can operate in a broad range of temperatures.
The eosFD only requires a 12 V DC power supply, and is often paired with a high-capacity battery and solar panel for extended deployments. See Application Note #AN0008 for further information on sizing solar power.
You connect to the eosFD using the eosLink-FD software, a Windows computer, and the supplied serial extension cable and USB-Serial converter.
No, the eosFD has an internal datalogger that can store up to 65536 measurements (over seven months at the fastest, five minute frequency).
None, it is not connected to anything else. You can deploy any number of eosFD devices over any area. (Just remember where you put them!)
Heavy duty acetal plastic.
First, try refreshing the connection through the Connection menu. Ensure that the COM port set in the software matches the one used by the data cable (the Windows Device Manager may be useful for identify the eosFD COM port). If the problem persists, try unplugging the data cable from the USB port, waiting several seconds, and then plugging it in again (remember to refresh the connection or close and relaunch eosLink-FD). Connecting through a different USB port on your computer may also help. If the problem is still not resolved, try a different data cable if available (additional data cables can be ordered from Eosense). If the problem still occurs, please contact Eosense for additional guidance.
Contact Eosense Support before attempting any repairs.
The eosFD membrane may have become damaged, or the CO2 sensor calibration may have drifted unexpectedly. Contact Eosense Support to see if recalibration is required.
Double check that enough time has elapsed that the measurement frequency has been met. If the problem persists, please contact Eosense.
Reset the eosFD clock using eosLink-FD and then disconnect the FD from power. Reconnect the eosFD and check the system time (from the defaults in the Set Time and Date window). If the problem persists, please contact Eosense Support.
3 metres / 10 feet of water.
We recommend weekly in situations where it suffers frequent disturbance, but in quiet areas many devices have been accurately deployed for months at a time without recalibration.
The eosGP has been tested from -20 C to 50 C / 32 F to 104 F.
Please ensure that the power supplied to the eosGP is between 5 V DC and 24 V DC.
Ensure that the gas probe is connected to power and that a session has been started (via the Start button in eosLink-GP). Check that the correct COM port has been selected under Options|COM port. If the problem persists, exit eosLink-GP, disconnect and then reconnect the USB data cable, then re- launch eosLink-GP.
Ensure that the gas probe is connected to power. Open the device manager from the Control Panel in Windows and reconnect the USB data cable. If no connections show up under Ports (COM & LPT), please contact Eosense Support for further instruction.
In environments which have higher than normal levels of salt or other ions, the eosGP socket and/or cable may oxidize or discolour. This will not affect the measurement performance, but will shorten the lifetime of the sensor. In these types of environments we recommend attaching the cable to the eosGP probe and then lightly coating the metal components with silicone grease (i.e. high vacuum grease). Coating with silicone grease is also advisable in waterlogged soils.
The S.E. voltage wires output ~ 0 V to ~ 5 V signals that correspond to the current CO2 and temperature readings in the sensor. These outputs can be monitored as an alternative to receiving digital data. If the eosGP is powered independently of the device which is logging the S.E. voltages, then the S.E. voltage may change with varying power supplies even if the gas concentration or temperature has not changed. It is critical that the device which is logging the S.E. voltages and that providing the power for the eosGP have the same ground. For example if using a commercially available data logger to log the S.E. voltage, also use the ~ 12 V power supply port that exists on the data logger.
The eosGP sensor requires a stable power supply with minimal noise in order to achieve the lowest possible noise on concentration and temperature measurements. When using the GP, ensure that the power supply is of high quality or that the power supply variation is buffered with an in-line battery or other power smoothing device. If you are unsure about your power supply setup please contact Eosense Support.
Eosense makes all efforts to ensure accurate calibration, including periodic checks against NIST traceable standards, however calibrations may vary from individual laboratory standards. There are several reasons for this, including long term sensor drift, changes in atmospheric pressure (sensors are calibrated at sea-level) and variation in gas supplier analysis techniques. We highly recommend that users concerned with comparing eosGP results with other laboratory and field instrumentation re-calibrate eosGP sensors using the same standards, and/or cross calibrate all instruments.
It is currently designed to attach up to 12 eosAC autochambers to LGR and Picarro analyzers.
It should be protected the same as the gas analyzer.
While in use the eosMX-P interface panel should be protected from rain, dust, etc. However, when sealed for transportation the eosMX-P is fully weatherproof.
Any non-toxic or corrosive gases can be processed.
This error indicates that the executable is missing the (hidden) system files. This happens when the .exe is moved from its original position in the software folder. To resolve this problem, keep the executable in the same folder as it was downloaded in (or re-extract the .zip file and use that as the new software folder).
Please ensure that the power supplied to the multiplexer and that the power switch is set to on. Check that the Control USB cable is connected to your analyzer or PC. If the problem persists, check the Device Manager to see whether or not the device has been correctly detected by the computer.
Check which multiplexer port the autochamber is connected to. Click the Refresh Chambers button if the autochamber was connected after the start-up routine completed. Check that the USB data cable is connected to your analyzer or PC. If the problem persists, check the Device Manager to see whether or not 12+ serial connections are present.