Unable to connect to HDS2102S

[nickaftera]

I've tried both the release version 0.1.2 and the unpacked one from this comment: #5 (comment)

An error is returned when application is launched, I assume it cannot connect to the device.

I couldn't install the driver from the repo (said the usual "there was an issue when installing this driver"), so I've done it with Zadig 2.9. I had the manufacturer driver installed before this and just installed the WinUSB one over, I think this should not be an issue?

[seritools]

Hi, could you let me know your firmware version?

Also please check out the test version from over here: #6 (comment)

Generally, OWON changes random small things between firmware/hardware revisions, some of which are hard to work on without the appropriate hardware at hand.

[nickaftera]

V6.0.4 is what is shown in "System -> About" section, though I'm not sure whether it is hardware or firmware version. I'm also puzzled by their website where I'm trying to see firmware at the download center, and it asks me to "enter your firmware version"...

The test version from the archive you've pointed to connects to the device and doesn't show the error. I'll continue testing this one.

I'd have built the .exe from sources, but that requires installing the whole Rust toolchain with MSVC and SDK, so I was trying to check for the already built apps first.

[seritools]

though I'm not sure whether it is hardware or firmware version. I'm also puzzled by their website where I'm trying to see firmware at the download center, and it asks me to "enter your firmware version"...

it's both -- the major version number is effectively the hardware revision, the others are software revisions. they ask for your current firmware version to only let you download the FW for the correct hardware revision, hence why i'm on V1.5.1 with no upgrade in sight :)

[nickaftera]

I'll continue using this thread for other debug issue if you don't mind.
I've switched the trigger to Single (on oscilloscope; the button in the app didn't react in any way), and then an error started appearing each time there is a mouse move or keypress over the waveform:

AcquireSignalData

Caused by these errors (recent errors listed first):
  1: DeserializeSignalHeader(source2: Some(Error("unknown variant `SINGle`, expected one of `AUTo`, `NORMal`, `SINGlE`", line: 1, column: 589)))
  2: expected value at line 1 column 1

[seritools]

pushed a new commit to main that should accept that spelling. switched to linux on my main machine, so no test build right now.

i'll get around to making this project multiplatform at some point, and get an msvc-based crosscompile running as well