NanoVNA not detected

[neilkatin]

I tried to run the app today (both the official one and a local installation build from your source).

Chrome (version 74) reports "No Compatible Devices Found" when I try to connect.

The "no devices matched" console.log() statement also gets printed (nanovna.js line 31).

I'm sure this works for you. I made sure my NanoVNA is configured; it has the correct vendor/product codes (0483:5740).

I confirmed I can communicate with the VNA via the NanoVNASharp program.

Are you running a special version of the firmware with changes to the USB driver to allow it to work with webusb? I wasn't able to convince ms windows 10 to use the WebUSB driver with my nanovna.

Or perhaps you're running macos, where things 'just work'?

(for reference: the google page for configuring windows devices for webusb)

[neilkatin]

An update: the app 'just works' on macos.

The device is detected on linux, but throws an uncaught deserialization error during the initial connection:

Uncaught (in promise) Error
deserialize @ comlink.ts:90
fromWireValue @ comlink.ts:288
async function (async)
connect @ script.js:187
created @ script.js:545
async function (async)
created @ script.js:534
invokeWithErrorHandling @ vue.js:1863
callHook @ vue.js:4214
Vue._init @ vue.js:4996
Vue @ vue.js:5072
(anonymous) @ script.js:95

[cho45]

In short, WebUSB is very experimental feature.

• Windows requires replacing driver. https://zadig.akeo.ie/ is useful.
• Ubuntu requires additional permission setting.

If I understand the steps well, I will add to README.

[cho45]

Readme updated.

Added Ubuntu instruction with disabling cdc_acm driver udev rule: https://github.com/cho45/NanoVNA-WebUSB-Client/blob/master/etc/99-nanovna.rules.

Added Windows instruction with zadig.

[hugocoolens]

I tried it out with a nanovna-v2 in Mint 19.2 as follows:
Enabled flag: chrome://flags/#enable-experimental-web-platform-features
gpasswd ⁻a myusername dialout
gpasswd -a myusername uucp
(logged out and logged in)
Copied 99-nanovna.rules to your /etc/udev/rules.d
and executed the following commands:
udevadm control --reload-rules
udevadm trigger
browsed with chromium-browser: https://cho45.stfuawsc.com/NanoVNA/
plugged in nanovna-v2
selected CDC-ACM_Demo (ttyACM0)
failed to open serial port
Strange enough the following is shown then:
CDC-ACM_Demo (ttyACM0) (paired)

What is going wrong?

kind regards,
Hugo

[akhepcat]

I'm also having a problem with my NanoVNA not being seen by the web interface.

If i disable the udev rule, i can see /dev/ttyACM0 in the list, but selecting it brings up errors about not being able to set baudrate.

Enabling the udev rule again means I no longer see the serial port in the list, so I don't know what to connect to, and the interface doesn't seem to either.