Differential probe X200 X500 X1000 support about openhantek6022

[Ho-Ro]

Hi @v8karlo,
A quick'n'dirty solution is to change line 22 of openhantek/src/docks/VoltageDock.cpp to
#define ATTENUATION 500
and line 62 from
b.attnCheckBox = new QCheckBox(tr("x10"));
to
b.attnCheckBox = new QCheckBox(tr("x%1").arg( ATTENUATION );
I will introduce the 2nd change later into the master branch and make the 1st define selectable via cMake call.
I've already thought and discussed the solution with a drop-down list instead of a single checkbox, but there are so many different probe gains that we would get a huge list, while 95% of all probes are just X1 and X10. (I just added 200 and 500 to my former wish list of 1, 2, 4, 5, 10, 20, 50, 100, 1000... :) )
Another reason is that the Hantek6022 (a low-cost device for beginners and hobbyists) comes with X1/X10 probes and the user interface should supports this without creating further confusion. If I have the need for an X100 probe or even a differential probe, then I am an experienced user and can easily convert the values in my head.
BTW: How was it done in former times?

[v8karlo]

Thank you for your answer!
My differential probe is HT8100 Hantek 50/500, and I have current probe hantek 10/100. All of those values are Hantek.
Even Hantek is for beginners, I made more than few quite professional jobs with it.

Problem arise when I use differential probe with current probe which I do a lot for math graph.

I can do the old way and calculate, but when using math graph it is far easier if attenuation is of correct value and faster and less errors. In a hurry I can make fatal errors in calculating right readings in my head. Which happened before.
After 6-7 hours of working is easy to make this simple kind of errors while calculating attenuation factors in my mind with 2 different sets of attenuations.

I am not C++ programmer, but C# mostly. I will try your solution anyway.

May I suggest possible solution?
Remove checkBox X1 and checkBox X10.
Put the textBox where user can type value for his probe per channel and button UpdateValue.
(Or without button automatically update using type event of textBox, so only textBox is needed).
When button UpdateValue is pressed, software read value from textBox and use that value in calculations.
That way every user can define attenuation value for his own probe type per channel.
Yes, user has to manually enter the attenuation value when changing probes, but it solves all types of probes depending which one user uses.

At the end, which is easier and most of all safer? (I made lots of errors in past calculating old way.)
To manually enter attenuation value once or to manually calculate value for current probe and value for differential probe and then do the math for power graph every time user use this 2 probes together? Which can be daily at least 200 times at my job, and user can make errors easily in a hurry.
I personally will be glad to enter attenuation value manually every time than make mistakes in calculating attenuation factors old way ever again, which costed me time and money.

No need for long drop down list with lots of values. Let the user type correct attenuation value.

Thank you in advance. Sorry for long comment. I had to explain my reasons.
This software is gem for eyes after struggling with Hantek software. Very good work!

[Ho-Ro]

closed by #50 & #51