override mesa openGL versions

[milahu]

add the --forceSL150 flag to ignore the openGL Shader Language version reported by

glxinfo | grep -i "shading language"

this has the same effect as running

MESA_GL_VERSION_OVERRIDE=3.2 MESA_GLSL_VERSION_OVERRIDE=150 OpenHantek

http://www.mesa3d.org/envvars.html

MESA_GL_VERSION_OVERRIDE
changes the value returned by glGetString(GL_VERSION) and possibly the GL API type.
Mesa may not really implement all the features of the given version. (for developers only)

MESA_GLSL_VERSION_OVERRIDE
changes the value returned by glGetString(GL_SHADING_LANGUAGE_VERSION). Valid values are integers, such as "130".
Mesa will not really implement all the features of the given language version if it's higher than what's normally reported. (for developers only)

related issues are #221 and #236

[milahu]

added Signed-off-by: Milan Hauth <milahu@gmail.com> to commit message, DCO check should pass

[Ho-Ro]

Please check #277!

[milahu]

thanks ....
new mission: add DSO-2250 support to OpenHantek6022
the interface runs fine, thanks to version 120 shader code

[Ho-Ro]

new mission: add DSO-2250 support to OpenHantek6022

It could happen if someone sponsors me a DSO-2250.

There's no point in developing for a device if I don't have a test facility. I only own a DSO-6022BE; the experience I gained with the 6022BL (which uses only minimally different ports) and the DDS-120 (which has a little more variation) from other users has confirmed me in this - no development if the target hardware is not available!
Same goes for a non-existent target OS; I develop on Debian and can compile and test in real also on the RPi. The compilation for Windows and MacOS (I don't own either) is done for me by the CI providers Travis and AppVeyor - no testing possible. The translation for FreeBSD in qemu runs on my machine, testing is also not possible due to the virtualized USB.

[milahu]

It could happen if someone sponsors me a DSO-2250.

i could publish my USB port online, but the latency would be terrible
naah, im already working on the code, its mostly just cut-and-paste

• switch between control and bulk commands, depending on model
• restore code for handling bulk commands?
• disable calibration stuff for DSO2250
• get fixedSampleRates for DSO2250?
• allow to set "record length" (20.5 kS, 1.05 MS, roll, etc)

[Ho-Ro]

I would choose this branch as the starting point for your fork, because after that I only worked with regard to the 6022 series and also often removed the device independence of the software when necessary.

[davhak]

In my case with Voltcraft 5200A the signal is not shown as well.
Does anyone aware of a working commit for 5200A?

[henrik1g]

It could happen if someone sponsors me a DSO-2250.

i could publish my USB port online, but the latency would be terrible
naah, im already working on the code, its mostly just cut-and-paste

Did you have success on getting the 2250 to work ?

I also own one with similar problems. (No data shown with latest openhantek)
With latest openhantek and the MESA_GL_VERSION_OVERRIDE=3.2 MESA_GLSL_VERSION_OVERRIDE=150 enviroment workaround some data is shown but only on the very left side of the graph. Unusable.
openhantek6022 works nicely in demo mode on ubuntu 20.10.
openhantek6022 at "last_legacy_support" shows some data but unusably cramped on the very lefthand side of the graph, like with the version workaround above.

If you got the 2250 running would you share your work? Thank =)

[milahu]

Did you have success on getting the 2250 to work ?

i ended up using pulseview, cos i needed a logic analyzer

iirc, my dso 2250 worked with openhantek

can you run windows with the original hantek software?
there you also can calibrate the scope, maybe that helps

or switch to a lower frequency?

[henrik1g]

AtM I'm running the original software in VirtualBox (I have no Windows System). This works without a problem.

my dso 2250 worked with openhantek

When (i.e. what version/commit of openhantek) was that? If it was the recent one. This sounds like pure OpenGL problem... What OpenGL Version did you run it under? Thanks for the quick reply ! Henrik

[milahu]

When (i.e. what version/commit of openhantek) was that?

it worked with the latest version, see #236 (comment)
that was one year ago, on arch linux

bad news: cannot reproduce on my current system : /
the interface just hangs ... updates like once every 10 seconds
but shows no data, not even for the math channel

but pulseview works, just without the live scope / FFT view

[henrik1g]

Thank you for the info! I will try pulseview =) Am 18.05.21 um 15:41 schrieb milahu:

…

When (i.e. what version/commit of openhantek) was that? it worked with the latest version, see #236 (comment) <#236 (comment)> that was one year ago, on arch linux bad news: cannot reproduce on my current system : / the interface just hangs ... updates like once every 10 seconds but shows no data, not even for the math channel but pulseview works, just without the live scope / FFT view — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#319 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAZCVDOWCMYPS7EW7EVH3PDTOJVCBANCNFSM4PEUCTEA>.