DatLab error messages

From Bioblast
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
Bioblasts - Richard Altmann and MiPArt by Odra Noel
MitoPedia     Terms and abbreviations     Preprints and history     MiP and biochemistry     Concepts and methods     MitoPedia: SUIT     MitoPedia: O2k



MitoPedia

DatLab error messages

Description

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

DatLab error: Connection error

DatLab error messages connection.PNG

This message appears in DatLab when the software is 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 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 O2k-Main Unit 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 regularly takes more than 10 min for cooling. The error message simply informs the user that a prolonged stabilization time will be required. Delete the Event with the error message.
  2. When aiming for a low experimental temperature (i.e., < 6 °C) and the error message is repeatedly shown several times, the room temperature may be too high in relation to the low set temperature, and the Peltier power may be insufficient. Reducing the room temperature may solve the problem.
  3. The O2k-Peltier Temperature Control may have a temporary connection failure. Switch off the O2k, restart it after a few minutes and connect it to DatLab (with the intended temperature). If the problem persists, please contact our technical support.





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 O2k-Main Unit 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 may be temporarily disabled. Switch off the O2k, restart it after a few minutes and connect it to DatLab (with the intended temperature). If the problem persists, please contact our technical support.







DatLab error: Line has wrong length

DatLab error messages line.png

This message appears while recording 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(s).

Actions

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


DatLab error: Controller Watchdog Reset was detected.

DatLab error messages watchdog detected.png

This message appears while recording a file with DatLab, when there is an interruption in the USB-connection and it 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 port).
  2. Switch on the O2k-Main Unit only after the USB is connected to the already switched on PC.
  3. Avoid disturbing the USB-connection to the PC during use.







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

DatLab error blob cache not released.png

This message appears at the beginning of recording a file with DatLab, when there is a conflict creating a DLD file. It can be caused by several factors, but with native error 20150 the probable cause is a storage problem (temporarily disconnected or slow network connection) or a virus scanner 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. A computer upgrade 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 while recording 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



DatLab error: ROM CRC check failed on following measurement channels: O2L; O2R; AmpL;AmpR;pXL;pXR;

DatLab error ROM CRC check.png

This message appears at the beginning of recording a file with DatLab.

Actions

Click on 'Ok' to remove the error message from DatLab.
  1. Check if the channels listed in the error message are being recorded.
    1. If not, restart the program to observe if the problem persists.
    2. If the the channels did not connect, restart the O2k-Main Unit and DatLab.
  2. Check if your PC specifications meet the DatLab minimum requirements

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








DatLab error: Komponente mit der Bezeichnung mnSysProtMenu0 existiert bereits.

DatLab error MnSysProtMenu0.png

'Komponente mit der Bezeichnung mnSysProtMenu0 existiert bereits' or 'Component with the name mnSysProtMenu0 already exists' appears when trying to load instrumental DL-protocols using DatLab.

Actions

Click on 'Ok' to remove the error message from DatLab.
  1. If restarting DatLab is possible.
    1. Close the program and restart a new file.
  2. If restarting DatLab is not possible.
    1. When loading a new instrumental DL-Protocol ('Protocols' > 'Run DL-Protocol / Set O2 Limit'), click on SUIT instead;
    2. Load the instrumental DL-Protocol by accessing manually the corresponding folder for the instrumental DL-Protocols. The default location is 'C:\DatLab\DL-Protocols\Instrumental'.
    3. Apply the DL-Protocol to the corresponding chambers.




DatLab error: Internal communication error on following measurement channels

DatLab error Internal communication error.png

This message appears in DatLab when the O2k-Main Unit is not able to connect with the O2k-Core.

Actions

Click on 'Ok' to remove the error message from DatLab.
  1. Close the program and switch off the O2k-Main Unit.
  2. Switch on the O2k-Main Unit.
  3. Connect DatLab and check if the measurement channels are connected.

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







DatLab error: Cannot read from file

DatLab error cannot read from file.png

This message appears when trying to close a DLD file or closing the DatLab program. This is caused when there is a temporary connection issue with the file directory. To prevent this error, please avoid recording files in folders that require constant internet connection (such as cloud services or private network servers).

Actions

Click on 'Ok' to remove the error message from DatLab.
  1. If you want to save changes made in the DLD file, click on 'Save as...' to save manually select the file directory.
  2. If the message persists, open the Task Manager (Ctrl+Shift+Esc) and click on 'End Task' to forcefully close DatLab.





MitoPedia O2k and high-resolution respirometry: DatLab