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

Difference between revisions of "DatLab error messages"

From Bioblast
Line 128: Line 128:
::::# Unstable power supply.
::::# Unstable power supply.
::::# Problem in the hardware of the [[Oroboros O2k]] main unit.
::::# Problem in the hardware of the [[Oroboros O2k]] main unit.
=== Actions ===
:::: Click on 'Ok' to remove the error message from [[DatLab]]. Restart the program to observe if the problem persists.
::::# Check if your PC specifications meet the [[DatLab| DatLab minimum requirements]]


In case of continued error message, please contact our [https://www.oroboros.at/index.php/o2k-technical-support/ technical support]
In case of continued error message, please contact our [https://www.oroboros.at/index.php/o2k-technical-support/ technical support]

Revision as of 13:10, 14 January 2021


high-resolution terminology - matching measurements at high-resolution


DatLab error messages

Description

Common DatLab error messages and according actions and solutions are listed here.





MitoPedia O2k and high-resolution respirometry: DatLab 



DatLab error: Connection error

DatLab error messages connection.PNG

This message appears in DatLab when the software was not able to connect with the O2k-Core.

Actions

  1. Check if the O2k is switched on.
  2. Check if the proper communication port was selected and it is connected.
  3. Check if there is no other program using the same communication port.
  4. Check if your PC specifications meet the DatLab minimum requirements

In case of continued failure to connect, please contact our technical support




DatLab error: Average block temperature over past 10 min has not reached set temperature

DatLab error messages Peltier 10min.png

This message appears in DatLab when the block temperature of the OROBOROS O2k has not reached the set temperature within the past 10 min.

Actions

Click on 'Clear errors' to remove the error message from the O2k status line. Select 'Layout' > 'Standard layouts' > '01 Calibration show Temp' (including a graph with plots of temperature and Peltier power). The oxygen signal cannot stabilize without temperature stability.
  1. When cooling from room temperature to a lower temperature (e.g., 4 Β°C), it takes regularly more than 10 min for cooling. The error message provides merely information on the fact that a prolonged stabilization time will be required. Delete the Event with the error message.
  2. When aiming at a low experimental temperature (i.e., < 6 Β°C) and the error message is shown repeatedly several times, the room temperature may be too high in relation to the low set temperature, and the Peltier power may be insufficient. Cooling the room temperature may solve the problem.
  3. The O2k-Peltier Temperature Control may have an electronic defect. To confirm, switch off the O2k and repeat the procedure.
  4. If the O2k-Peltier Temperature Control has an electronic defect, the O2k-Main Unit has to be sent to the electronics workshop of OROBOROS for service.




DatLab error: Block temperature does not increase while heating with full power

DatLab error messages Peltier power.png

This message appears in DatLab when the block temperature of the OROBOROS O2k has not reached the set temperature despite the application of the Peltier's full power.

Actions

Click on 'Clear errors' to remove the error message from the O2k status line. Select Layout > Standard layouts > 01 Calibration show Temp (including a graph with plots of temperature and Peltier power).
  1. The O2k-Peltier Temperature Control is temporarily disabled. To confirm, switch off the O2k and repeat the procedure.
  2. If the O2k-Peltier Temperature Control has an electronic defect, the O2k-Main Unit has to be sent to the electronics workshop of OROBOROS for service.







DatLab error: Line has wrong length

DatLab error messages line.png

This message appears during recording of a file with DatLab, when a signal line has not been transmitted properly from the O2k to DatLab. One or several data points in all plots are missing. The calculated oxygen flux may show a disturbance caused by the missing data point.

Actions

Click on 'Clear errors' to remove the error message from the O2k status line.
If this error occurs frequently, then
  1. Check if the data recording interval is set to a value which is too low for the capacity of your computer used for recording with DatLab. At a data recording interval of 2s such error messages should not occur (or only exceptionally).
  2. Too many programs may be active at the same time.
  3. The computer may be too slow for processing the signals and handling DatLab. An upgrading of the computer may be necessary.


DatLab error: Controller Watchdog Reset was detected.

DatLab error messages watchdog detected.png

This message appears during recording of a file with DatLab, when there is an interruption in the USB-connection and automatically resets.

Actions

Click on 'Clear errors' to remove the error message from the O2k status line.
If this error occurs frequently, then
  1. Test different USB ports of the PC (this could be caused by a faulty USB entry).
  2. Switch on the Oroboros O2k only when the USB is connected to the already switched on PC.
  3. Avoid removing the USB-connection from the PC.







DatLab error: Blob cache not released - Native error: 20150

DatLab error blob cache not released.png

This message appears at the beginning of the recording of a file with DatLab, when there is a conflict creating a DLD file. It can be caused by several factors, but on native error 20150 the probable cause is a problem with the storage (temporarily disconnected or slow network connection) or a virus scanner is blocking the DLD file while DatLab is still recording.

Actions

Click on 'Ok' to remove the error message from DatLab. Restart the program to observe if the problem persists.
  1. Check if your PC specifications meet the DatLab minimum requirements
  2. Check if your your virus scanner is blocking the creation/reading of DLD files.
  3. Check the location of your saved files. It is not recommended to record your files directly to a server since the DLD file is rewritten every time a new data point is collected. This could overload the data traffic of your server.
If this error occurs frequently, then
  1. The computer may be too slow for processing the signals and handling DatLab. An upgrading of the computer may be necessary.


DatLab error: Zugriffsverletzung bei Adresse 0040551C in Modul 'DatLab7.exe'. Lesen von Adresse 0000003E

DatLab error messages Zugriffsverletzung.png

This message appears during recording of a file with DatLab, when there is a problem with the hardware of the PC, possibly unrelated to DatLab. 'Zugriffsverletzung' or 'General protection fault' can be caused by several factors, unfortunately it is not possible to determine a single cause for this error message.

Possible causes:
  1. Hardware problems with the PC.
  2. Third-party programs conflicting with DatLab.
  3. Network problem.
  4. Unstable power supply.
  5. Problem in the hardware of the Oroboros O2k main unit.

Actions

Click on 'Ok' to remove the error message from DatLab. Restart the program to observe if the problem persists.
  1. Check if your PC specifications meet the DatLab minimum requirements

In case of continued error message, please contact our technical support