O2k-Open Support

A good trouble shooting process helps to localize and resolve any problems encountered with the oxygraph as fast and as cost effective as possible. Many problems can be located easily on a particular component that can be serviced or - if necessary - replaced by the user, avoiding to ship the entire oxygraph. A few problems , e.g a non functioning Peltier unit , can be detected directly by a single observation followed by specific instructions for this case. However, usually it is best to follow a general procedure regardless of the initial observed problem. This is especially true for problems that may have different causes or are vague in their description. "Unstable signal", "no signal", "slow response" all fall within this category. The general trouble shooting process described below will show and locate most hardware problems.

General Troubleshooting Process

To find hardware problems all uncertainties implied by a biological experiment have to be eliminated. A Datlab file obtained with actual biological material is not suitable for trouble shooting purposes.

1. Perform a Sensor Test and analyze its results
2. Locate the problem utilizing the two chamber approach of the O2k by strictly following the procedure described on the Switching components page. This also involves several more sensor tests.

Specific Problems that do not require a Sensor Test

DatLab Error Messages

• DatLab Error Message: Block temperature: ERROR: Average block temperature over past 10 min has not reached set temperature

• DatLab Error Message: Line has wrong length: ERROR: Line has wrong length: This message appears when a signal line has not been transmitted properly from the Oxygraph-2k to DatLab 4.

Other Problems that do not require a sensor test

• Problems related only to the pX channel or the additional amperometric channel
• jumping or blocked stirring bar
• high oxygen flux at closed chamber

All Technical Service and Troubleshooting Pages

Service The query description has an empty condition.