i would like to start with a friendly hello to the team :
are there any plans to support the hantek 4 channel units dso3064 and dso3064a ... i have one of them and use mostly kubuntu machines ... there is no room on my workbench and now i would have to place a schlepptop on it in addition
i took the code on github and didn't find any .pro qt project file, so i found an older one and started with it initially, it mostly compiled and so i used the .pro file on the current project and kept on working with it
the 3000 series doesn't load any firmware at startup and it took me a while to figure this out .... they update the firmware through a usb-host port which my early 3064 unit doesn't have ... i don't care about new firmware since it works right now
long story short : did some qt work in the last 2 years as well as some usb stuff, but i'm not an expert ... added some code to device and style files to partially recognize the new dso 3064, but that's about it.
wireshark shows some usb communication, but no action on the display ... also i didn't really try to fully implement the new device since i don't know all properties ... just gave it a try
a few comments if allowed ... your guys code prints some usb debug info to qt-creator (wasn't really aware of this ability or forgot it since i didn't use qt all the time), but if anyone runs it stand alone, cause they don't know qt and the ide, i believe they're out of luck
finally after i spent hours of going through the code in debug mode and google info help i figured out why i need the udev for usb permissions reason ... it slipped by me especially after i discovered i don't need to load firmware ... to overcome i added my independent debug console and you guys can have my code if interested and use it ... every one of my qt projects has this buffered debug console and i couldn't live without it
sorry, but i didn't spend the time to figure out where and when
"message = tr("Couldn't open device %1: %2").arg(deviceAddress, Helper::libUsbErrorString(errorCode));"
this would show up ... i never saw it pop up anywhere and any ... maybe i didn't look hard enough, especially without qt-creator always by your side
one would assume, that maybe to expand from 2 to 4 channels couldn't be that hard unless there is a mayor design mess in the hantek protocols i would be really interested in possibly contributing to it, but i would need maybe some write-up or similar about how this communication works or some initial help or whatever it might take for me to avoid finding it out the hard way to chew through unknown code to reverse something which is known to you guys, just the basics, i understand that u didn't work with the 3000 series yet
i'm a hw guy with mostly firmware work for the last 30 years, did some c++builder, qt and android since 2014 and now retired by age, but not by earned finances ... quite often u need more than 2 channels and hantek offers an affordable solution within less than $ 500 ... yeah it's not 200 MHz or more, but mostly it's not the speed, but the need for more channels and hantek provides a nice solution ... for $ 700 u can get a whole bunch of probes and current clamps, and for the money any clamp is a 100 % improvement over not having one, even it's not the greatest
i'm not the hithub expert even i had to use it in one of my scrum based slavery contract assignments in the past ... i can also be reached at [email protected]
sorry that i didn't follow the wireshark package details and the application output debug details, but i'm also working on some automotive sw designs of my own and try to supplement my income once they're production ready
i would be looking forward to maybe some working together to expand the current design to 4 channel support ... the gui part is not the issue, the usb package details or more the communication portion to the device is too hard and time-consuming to reverse from the existing code
cheers Klaus
openhantek.zip