-
Hi, I love this software but there doesnt seem to be a "callibrate" function --- or am I missing something ?? I have a small DC offset on channel 2 and I was always able to fix it with the calibrate function in the original software. Is there a way of doing this under OH ?? Best regards, |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
RTFM :) |
Beta Was this translation helpful? Give feedback.
-
Re RTFM - fair comment ;-)
I looked at the instructions for installing the calibration
program and I have python3 and fetched the libusb dll, but the
instructions for "prepare Hantek6022API:" are only for linux
and I don't have a linux box - so how do I do this last stage.
Dave
On 08/10/2021 18:45, Martin wrote:
RTFM :)
The program uses offset/gain values from a config file - if this
doesn't exist it takes the values from the EEPROM, either the
factory offset calibration values or offset and gain values that
you can create with an extra calibration program. The
self-created values allow even sub-sample offset correction (due
to oversampling).
More detailed info can be found in the firmware repo.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
[
{
***@***.***": "http://schema.org",
***@***.***": "EmailMessage",
"potentialAction": {
***@***.***": "ViewAction",
"target": "#230 (comment)",
"url": "#230 (comment)",
"name": "View Discussion"
},
"description": "View this Discussion on GitHub",
"publisher": {
***@***.***": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]
|
Beta Was this translation helpful? Give feedback.
RTFM :)
The program uses offset/gain values from a config file - if this doesn't exist it takes the values from the EEPROM, either the factory offset calibration values or offset and gain values that you can create with an extra calibration program. The self-created values allow even sub-sample offset correction (due to oversampling).
More detailed info can be found in the firmware repo.