Cookies help us deliver our services. By using our services, you agree to our use of cookies. More information

Difference between revisions of "O2k-Open Support"

From Bioblast
Line 16: Line 16:
Usually it is best to follow a general trouble shooting procedure, relating to a large variety of apparent technical problems. This is especially true for problems that may have different causes or are vague in their description. For example, "unstable signal", "no signal", "slow response" fall within this category.  The general O2k-Troubleshooting process described below will help to locate most hardware problems.  
Usually it is best to follow a general trouble shooting procedure, relating to a large variety of apparent technical problems. This is especially true for problems that may have different causes or are vague in their description. For example, "unstable signal", "no signal", "slow response" fall within this category.  The general O2k-Troubleshooting process described below will help to locate most hardware problems.  
    
    
: '''Cost Estimation Repair'''
: '''Cost Estimation Repair''': Kindly note that a cost estimation for repair of the O2k main unit due to an electronic/mechanical defect can only be given after inspection of the O2k by the workshop in Austria. Once a cost estimation has been provided, the repair is carried out after the customer’s consent. For shipment of the O2k, please refer to the detailed shipping instructions on this troubleshooting site.
 
: Kindly note that a cost estimation for repair of the O2k main unit due to an electronic/mechanical defect can only be given after inspection of the O2k by the workshop in Austria. Once a cost estimation has been provided, the repair is carried out after the customer’s consent.  
 
For shipment of the O2k, please refer to the detailed shipping instructions on this troubleshooting site.
   
   
== General O2k-Troubleshooting process ==
== General O2k-Troubleshooting process ==



Revision as of 08:59, 15 July 2013

O2k-Troubleshooting helps to localize and resolve technical problems encountered with the OROBOROS Oxygraph-2k in a very fast and cost effective approach.

  • 1. Distinction between application problems and technical hardware problems:
An application problem can frequently be diagnosed on the basis of analysis of DatLab files recorded during O2k-calibration and instrumental background tests. By resolving such application problems, proper instrumental performance is obtained and a hardware problem is then excluded.
If an application problem or software problem (DatLab) can be excluded, the instrumental component causing the technical hardware problem has to be localized in Step 2.
  • 2. Technical trouble shooting: Localization of the hardware component causing the technical problem. Specific diagnostic tests are described under 'O2k-Troubleshooting' which help to identify any defective instrumental component.
  • 3. Distinction between hardware problems that can be solved by user-service and hardware problems that require replacement of a technically defective part:
The OroboPOS (polarographic oxygen sensor) requires user-service at intervals. Such user-service may solve specific technical problems.
If user-service is not an option to solve the technical problem, the diagnostic tests help to take an important decision in Step 4.
  • 4. Distinction between hardware defects which can be solved by replacement of a defective spare part in contrast to electronic or mechanical problems which can be solved only by service of the Oxygraph-2k in the workshop of OROBOROS INSTRUMENTS.
Some specific potential problems, e.g. a non-functioning Peltier unit, can be detected directly by a single observation followed by specific instructions for this case, which then can be solved only by electronic service of the Oxygraph-2k in the OROBOROS workshop.

Usually it is best to follow a general trouble shooting procedure, relating to a large variety of apparent technical problems. This is especially true for problems that may have different causes or are vague in their description. For example, "unstable signal", "no signal", "slow response" fall within this category. The general O2k-Troubleshooting process described below will help to locate most hardware problems.

Cost Estimation Repair: Kindly note that a cost estimation for repair of the O2k main unit due to an electronic/mechanical defect can only be given after inspection of the O2k by the workshop in Austria. Once a cost estimation has been provided, the repair is carried out after the customer’s consent. For shipment of the O2k, please refer to the detailed shipping instructions on this troubleshooting site.

General O2k-Troubleshooting process

To evaluate and diagnose hardware problems, instrumental tests are performed in the absence of any experimental sample, using an aqueous medium for which any microbiological contamination can be excluded. Experimental test runs containing a biological sample is generally not suitable for technical troubleshooting.

  1. Perform an OroboPOS 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 Locating a problem page. This also involves several more POS sensor tests.

Specific problems that do not require a sensor test

DatLab error messages

Other problems that do not require a POS sensor test

How to find O2k-Troubleshooting and technical service information in Bioblast

  • You can use the standard Wiki search function in the right upper corner of most pages.
  • Pages in the O2k-Catalogue will frequentyl include a list of technical service pages related to the described component.
  • Use the list below to locate pages relevant to your problem.

All Technical Service and O2k-Troubleshooting Pages

The query description has an empty condition.



Template:Troubleshooting