OpenHantek / OpenHantek6022

OpenHantek6022 is a DSO software for Hantek USB digital signal oscilloscopes 6022BE / BL. Development OS is Debian Linux, but the program also works on FreeBSD, MacOS, RaspberryPi and Windows. No support for non-Linux related issues unless a volunteer steps in!
GNU General Public License v3.0
858 stars 152 forks source link

Readme needs an update #334

Closed munching closed 1 year ago

munching commented 1 year ago

Hi,

"USB Access" section, "Windows" department seems to contain some outdated info. There is no "driver" folder in the binary distribution neither is there a file named "OpenHantek.inf"

Also it would be very nice to have some additional info for complete beginners like me: what exactly does loader, openht and sigrok do? Not how to install them but rather why to install them? It's unclear, do I need loader, loader + one of the two or all three.

Another concerning point is that it was mentioned that at some point something is written to scope's firmware. Does this mean if I install the OpenHantek drivers and use the scope it will render the scope unusable with original software (on another PC with original driver & software)?

Thanks

Ho-Ro commented 1 year ago

"USB Access" section, "Windows" department seems to contain some outdated info. There is no "driver" folder in the binary distribution neither is there a file named "OpenHantek.inf"

The README reflects the current state of the repo - available in the unstable release (the name does not mean that the program is not stable and will crash, but that newly introduced features are still possibly being adjusted and may change slightly in look and feel). See also this section of the Readme. If you look into the zip you'll notice that there's a driver folder: image Content of the driver folder: image

Also it would be very nice to have some additional info for complete beginners like me: what exactly does loader, openht and sigrok do? Not how to install them but rather why to install them? It's unclear, do I need loader, loader + one of the two or all three.

The processor in the Hantek is an EzUSB device from Cypress. It contains a bootloader that is active at power-up (with its own USB identifier - Loader) and loads the application program for OpenHantek6022 from the PC into RAM via USB. When the Hantek is switched off or unplugged, the RAM content is lost, so it must be loaded once each time it is powered on. After that the bootloader is inactive and the application program (the firmware, also with its own USB identifier - OpenHantek) communicates with the PC. So that Windows can communicate with the bootloader (Loader) and the program (OpenHantek), the driver supports both variants, if you also use sigrok, then this program loads a different firmware, which in turn has a third USB identifier (Sigrok). These three identifiers are supported by the driver, which you only have to load once.

Another concerning point is that it was mentioned that at some point something is written to scope's firmware. Does this mean if I install the OpenHantek drivers and use the scope it will render the scope unusable with original software (on another PC with original driver & software)?

As above, the driver is installed on the Windows PC to make the Hantek hardware known to your PC, while the firmware is written (not by the driver, but from the OpenHantek6022.exe) into the RAM of the Hantek - it has to be uploaded with each power up of the device - you cannot brick your Hantek.

This is also written in the User Manual (p.3), linked on top of the Readme.

image

munching commented 1 year ago

Hi @Ho-Ro Thank you for the explanations. I didn't realize the readme refers to the unstable, was looking at the latest stable build. I also have another issue to report regarding the UI but as there was mentioned, windows-related issues are not accepted :( This is easily replicated in demo mode using specific screen resolution.

Ho-Ro commented 1 year ago

Just open a new issue, but I cannot promise support because I do not use Windows and have no Windows PC to test. But if this is a general issue also other users should be able to reproduce and debug. As I said: No support for non-Linux related issues unless a volunteer steps in!