Calibration for scope channels is not getting applied

[mi-hol]

PROBLEM DESCRIPTION

Completed calibration but starting a new measurement it is not applied for scope channels but for Multimeter it is applied.

This happens since at least commit 4077c1c on Apr 16, 2025

REQUESTED INFORMATION

Please make sure you have performed every step and checked the applicable boxes before submitting your issue. Thank you!

• Verified with latest published Labrador version verified with 572b557-installer.exe

• Searched the problem in the Troubleshooting Guide

• Searched the problem in the docs

• Searched the problem in issues

• [x Searched the problem in discussions

• Hardware the software is running on:

  • "System Type: x64-based PC" )
  • Operating System (OS) Build Version: OS Name: Microsoft Windows 11 Pro
    OS Version: 10.0.22621 & "OS Configuration: Standalone Workstation"

• Labrador Git hash: 4077c1c (from menu "Help/About Espotek Labrador)

TO REPRODUCE

Steps to reproduce the behavior:
i.e.:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

EXPECTED BEHAVIOUR

A clear and concise description of what you expected to happen.

SCREENSHOTS

ADDITIONAL CONTEXT

Add any other context about the problem here.

(Please, remember to close the issue when the problem has been addressed)

[mi-hol]

Issue exists down to Windows "Labrador Christmas Update 2017"
Hardware: Backer's Edition Batch2 with firmware 7.2 (applied via LabraScope)

[mi-hol]

Hardware: Backer's Edition Batch2 with firmware 7.2 (applied via LabraScope)

Seems to be the wrong firmware!
Confirmation required!!

[EspoTek]

Wait, what's going on here?

[mi-hol]

@EspoTek I did the firmware recovery manually & calibrated afterwards, but scope CH1 & CH2 have still an offset of 1.6 to 1.7V

Updated:
How can I create a log file with more information for troubleshooting?
Or in other words trigger the debug messages like below on Windows

int winUsbDriver::flashFirmware(void){
    qDebug() << "\n\n\n\n\n\n\n\nFIRMWARE MISMATCH!!!!  FLASHING....\n\n\n\n\n\n\n";

PS C:\Program Files\EspoTek\Labrador\1.0.20\firmware> .\dfu-programmer atxmega32a4u flash labrafirm_0007_01.hex --force
0%                            100%  Programming 0x3000 bytes...
[>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>]  Success
0%                            100%  Reading 0x8000 bytes...
[>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>]  Success
Validating...  Success
0x3000 bytes written into 0x8000 bytes memory (37.50%).

[mi-hol]

https://runebook.dev/en/docs/qt/qdebug

Why it happens
The QDebug macros are conditionally compiled. In a release build (when QT_NO_DEBUG_OUTPUT is defined), the code is simply omitted.

The fix
If you need some logging to persist even in a release build, QDebug isn't the right tool. Instead, you should use qInfo(), qWarning(), or qCritical(). These functions are designed for logging that you'll want to see in a deployed application. They can also be redirected to a file or another logging system, which is a big plus.

root cause in Windows build action

      - name: Build Labrador
        working-directory: Desktop_Interface
        shell: cmd
        run: |
          qmake -config release

[mi-hol]

Completed calibration but starting a new measurement it is not applied for scope channels
scope CH1 & CH2 have still an offset of 1.6 to 1.7V

@EspoTek Chris could you please shed some light on the purpose of the hardcoded values 1.65 and 3.3 in function https://github.com/mi-hol/Labrador/blob/master/Desktop_Interface/mainwindow.cpp#L1456 ?

void MainWindow::readSettingsFile(){
    settings = new QSettings();
    int connectionType = settings->value("ConnectionType", QSETTINGS_DEFAULT_RETURN).toInt();
    double calibrate_vref_ch1 = settings->value("CalibrateVrefCH1", 1.65).toDouble();
    double calibrate_vref_ch2 = settings->value("CalibrateVrefCH2", 1.65).toDouble();