-
Notifications
You must be signed in to change notification settings - Fork 156
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.
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
Wrong gain settings for SainSmart DDS120 #39
Comments
@msiegert Please check how the scope behaves without *.conf file in place. |
Sorry, but I can't test this right now. My DDS120 is in Japan (had to leave it there to monitor CAN bus communication on a prodction tool I am working on). I bought a LOTO OSC482 as a replacement since the DDS120 seems to be end of life/out of stock. But despite the fact that the USB PID/VID are the same as the DDS120, the configuration is somewhat different from the DDS120 and I had to patch the firmware and OpenHantek6022 a bit to get it to work. I am not sure how to merge my changes to OpenHantek6022 since those will break support for the DDS120... |
Ok, no problem, I've just removed your 1.18 : 1.21 correction if there is no conf file and therefore adjusted the specification values accordingly, so it should give a +- 5% accuracy for 1st time users - only offset has to be adopted individually. |
I'll see if I can find a differentiation parameter between the OSC482 and the DDS120 as soon as I get the DDS120 back, but this will be a while. There is some hope, the OSC482 is detected as: OSC482: by my Macbook. So we should be able to use the name and/or the manufacturer to distinguish between the DDS120 and the OSC482 |
This report from eevblog tells us:
Proposed solution: Change these lines:
OpenHantek6022/openhantek/src/hantekdso/models/modelDDS120.cpp
Line 34 in c365d9b
OpenHantek6022/openhantek/src/hantekdso/models/modelDDS120.cpp
Line 35 in c365d9b
to:
Also adapt
OpenHantek6022/openhantek/src/hantekdso/models/modelDDS120.cpp
Line 51 in c365d9b
The text was updated successfully, but these errors were encountered: