开云体育

the command set for the NanoVNA-F overlapped the NanoVNA

I call BS on that, based on a long career in embedded software development.

If NanoVNA-F wants Rune's support,
then they should AT LEAST provide him one, FREE.

Any more suggestions?

[ I do not have but am investigating cheap Android tablets
for Web-Client (e.g. refurb Lenovo Tab 4, Android 7.1) ]

WebUSB wants Chrome Browser version >= 65 for Android >= 4.1



Your S7 Edge should have Android >= 6, so should support new enough Chrome.

Google reportedly disabled webusb in 2018


Chrome for Android has some settings @ chrome://flags
Perhaps webusb is disabled there..

Some Android devices default browser was NOT Chrome.

For some reason, edy555_bugfix wouldn't run correctly on my device. In particular, when I hit "back" during calibration, the menu disappeared from the screen. Then when I touched the screen that same menu came back leading to an endless do-nothing-loop. I reinstalled 300_ch and everything works normally.

One can never have too many different adapters ?

Any one need 10 female to female connectors that I just ordered without
looking first! :-)) :-))

Roy
WA0YMH

On Tue, Oct 1, 2019, 4:41 PM Jbammi via Groups.Io <jbammi@...>
wrote:

Mike thanks for your Tips for new Users doc.
Small comment: I think you mean to recommend a male to female sma adapter
and not a female to female sma adapter, since the connection on the NanaVNA
is female, you plug the male end of the male to female adapter into the
female socket, and then the other end of the adapter presents to right
gender - female -- to plug in the cal standards or the device under test
etc.

73 de k1jbd
bammi

Mike thanks for your Tips for new Users doc.
Small comment: I think you mean to recommend a male to female sma adapter and not a female to female sma adapter, since the connection on the NanaVNA is female, you plug the male end of the male to female adapter into the female socket, and then the other end of the adapter presents to right gender - female -- to plug in the cal standards or the device under test etc.

73 de k1jbd
bammi

Hi Rune;

I've been following your NanoVNA Saver development with much interest, and I support your wise decision to throttle back on adding features so you can focus on making sure you don't have any bugs lurking in what already exists. I've spent most of my time sorting through the firmware posts in search of which is the most bug free, which is getting supported, and is attempting to enhance performance and/or add meaningful features. I'm still not certain I'm on the right path, but I am now concentrating my focus on edy555 as the baseline reference. His 0.1.1 release seems to behave well, but things became unstable when I installed his 0.2.2 release after having tried a 2.1 GHz version (by Cho I think?).







--
73

Gary, N3GO

Rune,

So, here is a bit more detective information to the issue I have reported with newer firmware and nanoVNA-Saver 0.0.12.

PC software: nanoVNA-Saver 0.0.12
Firmware version: edy555 version 0.2.2
Sweeping 80 MHz to 120 MHz in 2 scans produces the attached .s2p file named FMStop-2scan.s2p. I do see issues discussed below in this data.
Sweeping 80 MHz to 120 MHz in 1 scan produces the attached .s2p file named FMStop-1scan.s2p. I don't see any issues with this data.

For the S21 data the amplitude of the first 20 samples of the second scan are very similar (magnitude difference of < 0.015 dB) to the first 20 samples of the 1st requested scan. The same kind of similarity exists between the first 20 samples of S11; however, the differences are slightly larger (<0.119 dB.) I discovered this by converting the reported data into magnitude in dB using 10*log10(sqrt(real^2 + imaginary^2)). Since the data is not identical but very close in amplitude, I think this means that an additional scan was initiated in the nanoVNA firmware over the frequencies from the first scan (80,000,000 Hz to 83,781,075 Hz); however, they were attributed to the first 20 frequencies (100,099,408 Hz - 103,880,483 Hz) in the second scan requested. The remaining samples of the second scan appear to be correctly attributed to the frequencies (104,079,488 - 119,999,808) in the second scan based on the single scan results in the file FMStop-1scan.s2p. I hope this is clear enough to follow.

I am not very familiar with the commands to control the nanoVNA from the PC interface. You are obviously much more familiar than I. Since the frequencies are correctly reported as those you requested, I think this points to a timing issue in the firmware. Is there a way to stop scanning after every scan and then restart it once new frequencies are loaded? Could this approach avoid the timing issue? Is there some way to know that the scan has completed rather than waiting a specific amount of time?

Could this type of synchronization issue could be what causes occasional errors in all of the firmware? I suspect some errors could be related; however, I don't think all that I have seen could be this issue.

I really don't have any idea about the differences between the firmware from hugen and edy555; however, there does seem to be some timing difference when it comes to reporting data from the device to the PC interface. Through no fault of their own, they probably have not worried about the timing of things happening in firmware as it relates to the PC interface.

Here is another observation: When I continuously collect a single 101-point scan, I don't observe this issue because the first 20 samples will be nearly the same since their is no frequency change from scan to scan; however, the data may be from a different scan than the current one which does not matter.

I hope this is helpful. Thanks for considering this information.

--
Bryan, WA5VAH

I have webusb working on desktop (W10)in chrome.

I had no success with my samsung S7 edge, connects to nanovna wasn't OK.
The tip over here in the forum to use a usb hub (not powered) got the
nanovna recognized with the nanovna ChibiOS/RT virtual comport.
Aldo the webclient software gives nice graphics but didn't control the
Nanovna.
Any more suggestions?

73's
Erik ON8DC

David,
The NanoVNA-F developers announced a few days back that the command set for the NanoVNA-F overlapped the NanoVNA and; therefore, should run nanovna-saver with only small changes to the code. Rune, inquired about the nature of the code changes and they kind of backed off. At this point they are delivering a product without a document describing the command set (unless you want to dig through the C code) or a software application for capturing the data measurements. The device does come with a sandisk card, but I haven't seen any info about what the user can save to it. I hope to start seeing more info from early adopters such as yourself.

Herb

On Tue, 1 Oct 2019 at 13:44, mike watts via Groups.Io <wy6k=
[email protected]> wrote:

Certainly,
Please see the attachment.
Mike WY6K

I looked at the document quickly. One thing that struck me is the
recommendation to add SMA *female-female *adapters so one does damage the
connectors on the NanoVNA by rotating them. Do you not mean male-female
adapters, rather than female-female?

G8WRB.
--
Dr. David Kirkby,
Kirkby Microwave Ltd,
drkirkby@...

Telephone 01621-680100./ +44 1621 680100

Registered in England & Wales, company number 08914892.
Registered office:
Stokes Hall Lodge, Burnham Rd, Althorne, Chelmsford, Essex, CM3 6DT, United
Kingdom

Thanks for the info,
Dave

Hi David,
Without a NanoVNA-F to test against, I don't know that I would be able to
do much to support it. But looking at the source code for the firmware, it
shouldn't be too far from what the regular NanoVNA does.

If you use "-d" as a command line parameter, you get debugging information
from NanoVNA-Saver, and you can see what it's doing when it stops
responding in the console.

Thanks for offering to try, though! :-)
--
Rune / 5Q5R

On Tue, 1 Oct 2019 at 20:32, David J Taylor via Groups.Io <gm8arv=
[email protected]> wrote:

David,
It would interesting if you gave a review of the NanoVNA and NanoVNA-F
since
you own both devices. Especially interested in whether Rune's
nanovna-saver
app works out of the box with the NanoVNA-F.

Herb
================================

Herb,

With one brief test, 0.0.12 saver doesn't work with the v0.0.2 firmware.
It
appears to hang after a sweep is requested. I would be happy to work
off-list with Rune to resolve this.

Cheers,
David
--
SatSignal Software - Quality software for you
Web:
Email: david-taylor@...
Twitter: @gm8arv

Yes, please.? Do not contemplate a second -F group!
Mike WY6K


"... somewhere in the distance, there's a tower and a light, broadcastin' the resistance, through the rain and through the night..."

Yes, what Herb said!
Mike WY6K


"... somewhere in the distance, there's a tower and a light, broadcastin' the resistance, through the rain and through the night..."

Rune,

I greatly appreciate the information you have provided above. This is very helpful in the debugging process. I think your approach is very reasonable. I will do some more testing and get back to you on what I learn. Thanks for your great work on nanoVNA-Saver!

--
Bryan, WA5VAH

I plugged nanoVNA into a MacBook via USB 2.0 hub
and launched
from Chrome, after enabling its webUSB via the first Wiki link.
I suspect that nanoVNA behaves better via USB 2.0 than 3.0...
Web-Client behaves nicely on MacBook Chrome browser..

Chrome on iPad cannot load the Web-Client page,
and I cannot find any serial terminal console app for iOS
to test whether its USB connects to nanoVNA...

David,
It would interesting if you gave a review of the NanoVNA and NanoVNA-F since you own both devices. Especially interested in whether Rune's nanovna-saver app works out of the box with the NanoVNA-F.

Herb
================================

Herb,

With one brief test, 0.0.12 saver doesn't work with the v0.0.2 firmware. It appears to hang after a sweep is requested. I would be happy to work off-list with Rune to resolve this.

Cheers,
David
--
SatSignal Software - Quality software for you
Web:
Email: david-taylor@...
Twitter: @gm8arv

Daily Digest is what keeps me sane (?!)

W5VZB

C'mon folks - there is a NanoVNA-F group already on groups.io
Why re-invent the wheel?
I'm on it and the moderators should start telling people to use that forum for ALL -F related content.

/g/nanovna-f

'nuff said!