Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Implausible values in spectrum readout on TEK MSO68B #395

Closed
robot-army opened this issue Dec 18, 2021 · 5 comments
Closed

Implausible values in spectrum readout on TEK MSO68B #395

robot-army opened this issue Dec 18, 2021 · 5 comments

Comments

@robot-army
Copy link

image
@robot-army
Copy link
Author

Oops, hit send too quickly!

There are implausible values (-3601484742656 dB, etc) in the spectrum readouts on multiple channels being read from the 'scope.
IMG_20211217_172723

The screen on the scope looks like the attached (potatocam) photo.

Sorry, something went wrong.

@robot-army
Copy link
Author

running with --debug:

$ ./glscopeclient.exe --debug
GetConsoleScreenBufferInfo() failed (6);
Warning: glscopeclient works best with the OMP_WAIT_POLICY environment variable
set to PASSIVE
Detecting CPU features...
    * AVX2
    * FMA

    Warning: AVX2/AVX512 detected but disabled on MinGW64/GCC (see https://githu
    b.com/azonenberg/scopehal-apps/issues/295)
OpenCL support: not present at compile time. GPU acceleration disabled.

Connecting to SCPI oscilloscope at 192.168.25.101:4000
Installed options:
* BW6-10000 (unknown)
* LIC6-DEMO (unknown)
Context: OpenGL 4.2 compatibility profile
    GL_VENDOR                   = NVIDIA Corporation
    GL_RENDERER                 = GeForce GTX 770/PCIe/SSE2
    GL_VERSION                  = 4.2.0 NVIDIA 376.51
    GL_SHADING_LANGUAGE_VERSION = 4.20 NVIDIA via Cg compiler
    Initial GL error code       = 0
    GL_ARB_gpu_shader_int64     = supported
Requested rendering backend: OpenGL
Using rendering backend: OpenGL
        Warning: Socket read failed (errno=0, No error)
        Warning: Timeout, attempting to recover

Sorry, something went wrong.

@azonenberg
Copy link
Collaborator

There's a been a lot of work on the MSO6 driver over the past year or so, is this fixed?

@robot-army
Copy link
Author

robot-army commented Mar 9, 2023 via email

@azonenberg
Copy link
Collaborator

Closing for now, will reopen if anyone else has the same issue then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@azonenberg @robot-army