doc update, add windows driver license info

Signed-off-by: Martin <[email protected]>

CHANGELOG

@@ -1,3 +1,4 @@
+2024-01-08 (1b56a17): use static fftw, usb and z libs
 2024-01-01 (e6d863d): next build system update
 2024-01-01 (7f9eb94): build system update
 2023-12-31 (3b12af2): prepare next release 3.4

README.md

@@ -133,11 +133,11 @@ If you make small changes to the local source code, it is sufficient to call `ma
 
 ## Install Prebuilt Binary Packages
 * [![Downloads of latest release](https://img.shields.io/github/downloads/OpenHantek/OpenHantek6022/latest/total?color=blue)](https://github.com/OpenHantek/OpenHantek6022/releases/latest)
-Download Linux (Ubuntu 2004 LTS), Raspberry Pi (Debian stable), FreeBSD (12.1), macOS (Big Sur 11.6) and Windows (Visual Studio 2019) packages for your convenience from the [Releases](https://github.com/OpenHantek/OpenHantek6022/releases) page.
+Download Linux (Ubuntu 2204 LTS), Raspberry Pi (Debian stable), FreeBSD (12.1), macOS (12.7) and Windows (MINGW / MSVC2022) packages for your convenience from the [Releases](https://github.com/OpenHantek/OpenHantek6022/releases) page.
 * [![Downloads of latest devdrop](https://img.shields.io/github/downloads/OpenHantek/OpenHantek6022/devdrop/total?color=lightblue)](https://github.com/OpenHantek/OpenHantek6022/releases/tag/devdrop)
 If you want to follow ongoing development, packages built from a fairly recent commit are available in the rolling
 [devdrop release](https://github.com/OpenHantek/OpenHantek6022/releases/tag/devdrop).
-*Unstable* does not mean that the program will crash, but that individual features or elements of the GUI may still change.
+Individual features or elements of the GUI may still change.
 * For RPi4 see also [issue #28](https://github.com/OpenHantek/OpenHantek6022/issues/28).
 * These binary packages are built on stable operating system versions and require an up-to-date system.
 * As I develop on a *Debian stable* system my preferred (native) package format is `*.deb`.

docs/WinDriverLicense.md

@@ -0,0 +1,44 @@
+### Message exchange about windows driver license on eevblog.com
+
+---
+
+####From: horo
+####Signed WinUSB drivers for the Hantek 6022BE/BL
+####Sent to: ViktorEEV on: December 02, 2020, 08:04:09 am
+
+Hello Viktor,
+
+you provided signed Hantek driver for use with Windows.
+I would like to include your files into my project OpenHantek6022
+and I do not want to violate your copyright - do you have any objections?
+
+Martin
+
+---
+
+####From: ViktorEEV
+####Re: Signed WinUSB drivers for the Hantek 6022BE/BL
+####Sent to: horo on: September 16, 2022, 12:52:24 am
+
+Hello,
+
+sorry for the late reply.Hello, sorry for the late reply.
+That is no problem, they are more or less intended for OpenHantek.
+
+I added 'updated' drivers on the 6022BE thread:
+https://www.eevblog.com/forum/testgear/hantek-6022be-20mhz-usb-dso/msg4418107/#msg4418107
+
+---
+
+####From: horo
+####Re: Signed WinUSB drivers for the Hantek 6022BE/BL
+####Sent to: ViktorEEV on: September 16, 2022, 09:52:03 am
+
+Thank you Viktor,
+
+Your update is now in OH6022.
+https://github.com/OpenHantek/OpenHantek6022/commit/b0da1cd8cd425cc2c2c947ceb344c23c3d103d06
+
+Martin
+
+---

docs/developer_info.md

@@ -190,6 +190,8 @@ In `Roll` mode the latest sample values are always put at the end of the result
 this rolls the displayed trace permanently to the left.
 The conversion uses either the factory calibration values from EEPROM or from a user supplied config file. 
 Read more about [calibration](https://github.com/Ho-Ro/Hantek6022API/blob/main/README.md#create-calibration-values-for-openhantek).
+* `MathChannel::calculate()`
+   creates a MATH channel from the data samples of CH0 and/or CH1. This third channel can be displayed and also be used as a trigger source.
 * `searchTriggeredPosition()`
     * Checks if the signal is triggered and calculates the starting point for a stable display.
     The time distance to the following opposite slope is measured and displayed as pulse width in the top row.
@@ -219,9 +221,6 @@ becomes true again. The reused samples are emitted at lower speed (every 20 ms)
 
 
 * PostProzessing calls all processors that were registered in `main.cpp`.
-  * `MathchannelGenerator::process()`
-    * which creates a third MATH channel as one of these data sample combinations: 
-      `CH1 + CH2`, `CH1 - CH2`, `CH2 - CH1`, `CH1 * CH2`, `CH1 AC` or `CH2 AC`.
   * `SpectrumGenerator::process()`
     * For each active channel:∘
       * Calculate the peak-to-peak, DC (average), AC (rms) and effective value ( sqrt( DC² + AC² ) ).
@@ -230,10 +229,12 @@ becomes true again. The reused samples are emitted at lower speed (every 20 ms)
       * Calculate the autocorrelation to get the frequency of the signal:
         * Calculate power spectrum |F(ω)|² and do an IFFT: F(ω) ∙ F(ω) ⎯∘ f(t) ⊗ f(t) (autocorrelation, i.e. convolution of f(t) with f(t))
         * This is quite inaccurate at high frequencies. In these cases the first peak value of the spectrum is used.
+      * Calculate the power dissipation on a defined impedance that can be 1..1000 Ohm (optional).
       * Calculate the THD (optional): `THD = sqrt( power_of_harmonics / power_of_fundamental )`
+      * Detect the musical note plus deviation in cent of the signal (optional). Can be used e.g to tune an instrument.
   * `GraphGenerator::process()`
     * which works either in TY mode and creates two types of traces:
-      * voltage over time `GraphGenerator::generateGraphsTYvoltage()`
+      * voltage over time `GraphGenerator::generateGraphsTYvoltage()` plus optional histogram.
       * spectrum over frequency `GraphGenerator::generateGraphsTYspectrum()`
     * or in XY mode and creates a voltage over voltage trace `GraphGenerator::generateGraphsXY()`.
     * `GraphGenerator::generateGraphsTYvoltage()` creates up to three (CH1, CH2, MATH) voltage traces.