Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- Nanovna-Users
- Messages
Search
Re: New topic for test new nanoVNA features
#nanovna-h
#nanovna-h4
#beta
#test
Trace on/off stored in calibration settings, so need save it in old, or new calibrstion slot.
About freeze, i think it come from fast band switch (in most cases on switch 300MHz). |
Re: Firmware and PC application stability
#stability
#nanovna-h4
#nanovna-h
#specifications
On Thu, Aug 6, 2020 at 06:45 AM, Jim Lux wrote:
If it goes on for 6 months with only binary, and there's significant changes in functionality, with no source release - then start asking about whether the author is living up to the spirit and intent of GPL. ========================================== Seems the developer should have wider latitude as to how and when he releases his source. DiSlord and OneOfEleven would sometimes release multiple beta binaries in a single day. All were experimental and not ready for distribution. If the user thinks GPL is not being followed they always have the option of not participating in the in the developer's project. Since they are paying nothing, they shouldn't think they can demand anything. - Herb |
Re: Firmware and PC application stability
#stability
#nanovna-h4
#nanovna-h
#specifications
Agree with Jim.100%
toggle quoted message
Show quoted text
We should not mix community assistance for a developer's Alpha testing using binaries with the GPL requirements. It is easily solved for the purists with DiSlord doing his development and release Alpha level binaries for those of us that want to test with him. Once he is certain of stability or confirmed the goal of the alpha release, he can move it to a stable, stepped version Beta version for true beta testing by the community and publish that source code on Github. Regards RandMental -----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Jim Lux Sent: 06 August 2020 15h59 To: [email protected] Subject: Re: [nanovna-users] Firmware and PC application stability #stability #nanovna-h4 #NanoVNA-H #specifications On 8/6/20 2:57 AM, igor-m wrote: On Wed, Aug 5, 2020 at 05:58 PM, DiSlord wrote:I'm not sure I agree, Igor-M - collaborative development often involves beta testers, and this forum provides a convenient mechanism to make untested betas available.When you distribute the 1.0.XX binaries (like here on this forum or on cqham.ru or vrtp.ru) you shall provide the source code on your github too. Given that the source does get regularly updated, I don't think this violates the spirit of open source - otherwise a *group* of developers would have to keep their internal development hidden. Why not use public fora as a means of communication. I think that's a strawman - Why don't you wait 6 months, and then complain about how there's still a stream of bug-free binaries, with no source.Or i must add on my github every my test option?Yes. Otherwise one can distribute "test" or "beta" binaries for next 10years without providing source code. And the "open-source" project bites the dust. Open source is wonderful, but there are plenty of open source projects that are 80% complete (the vast majority of projects developed by grad students, for instance - got the degree, no need to do bug updates any more, and anyway I have a real job that actually pays me now) Let's focus our "why isn't source available" on pernicious evils - manufacturers who build custom versions for their products and have NEVER released source. yes it's open source - but I don't see a huge number of people stepping up to make changes. From what I see, there's a few folks grinding on the software, and dozens weighing in with testing, feature requests, etc.Or ... i should support code? But sorry for this need a lot of time,Nobody can ask you to support the code, this is an open source project. I'm not sure what axe you're grinding here, Igor-M? I think you're setting an artificial "intellectual purity" bar to participate in software development. I think OneofEleven and DiSlord are doing good work, and should keep it up, in what ever release strategy they care to do. They say that it's a hobby for them, and let's let that be for now. If all of a sudden, you start seeing ads in trade magazines for DiSlord VNAs next to Anritsu and Keysight, then you can start complaining about GPL. |
Re: Firmware and PC application stability
#stability
#nanovna-h4
#nanovna-h
#specifications
On 8/6/20 2:57 AM, igor-m wrote:
On Wed, Aug 5, 2020 at 05:58 PM, DiSlord wrote:I'm not sure I agree, Igor-M - collaborative development often involves beta testers, and this forum provides a convenient mechanism to make untested betas available.When you distribute the 1.0.XX binaries (like here on this forum or on cqham.ru or vrtp.ru) you shall provide the source code on your github too. Given that the source does get regularly updated, I don't think this violates the spirit of open source - otherwise a *group* of developers would have to keep their internal development hidden. Why not use public fora as a means of communication. I think that's a strawman - Why don't you wait 6 months, and then complain about how there's still a stream of bug-free binaries, with no source.Or i must add on my github every my test option?Yes. Otherwise one can distribute "test" or "beta" binaries for next 10years without providing source code. And the "open-source" project bites the dust. Open source is wonderful, but there are plenty of open source projects that are 80% complete (the vast majority of projects developed by grad students, for instance - got the degree, no need to do bug updates any more, and anyway I have a real job that actually pays me now) Let's focus our "why isn't source available" on pernicious evils - manufacturers who build custom versions for their products and have NEVER released source. yes it's open source - but I don't see a huge number of people stepping up to make changes. From what I see, there's a few folks grinding on the software, and dozens weighing in with testing, feature requests, etc.Or ... i should support code? But sorry for this need a lot of time, and thisNobody can ask you to support the code, this is an open source project. I'm not sure what axe you're grinding here, Igor-M? I think you're setting an artificial "intellectual purity" bar to participate in software development. I think OneofEleven and DiSlord are doing good work, and should keep it up, in what ever release strategy they care to do. They say that it's a hobby for them, and let's let that be for now. If all of a sudden, you start seeing ads in trade magazines for DiSlord VNAs next to Anritsu and Keysight, then you can start complaining about GPL. |
Re: Useful frequency range of NanoVNA H-4?
By the way, I used the NanoVNA as an SWR meter on 1296 MHz. It worked fine.
I looked at the SWR of my antennas for 222, 432, 902 and 1296 MHz. I had originally tuned these antennas with an SWR bridge and a transmitter. Now I see the adjustments are a little off for all of them except the 902 antenna. Now all I need to do is re-tune them using the NanoVNA. The NanoVNA agrees exactly with my AA-600 SWR meter for SWR across 5 to 30 MHz with my MFJ 1796 vertical antenna. Zack W9SZ On Tue, Jul 21, 2020 at 2:17 PM Zack Widup via groups.io <w9sz.zack= [email protected]> wrote: I thought I'd use my NanoVNA H-4 to tweak a 3-pole helical filter for 1296<> Virus-free. www.avast.com <> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> |
Re: Firmware and PC application stability
#stability
#nanovna-h4
#nanovna-h
#specifications
On 8/6/20 3:24 AM, DiSlord wrote:
Ok. I stop public binaries.This is getting into the classic bike shed painting exercise - If you want to make available binaries of test versions for someone to test (not actually "releases", per se) without the matching source code, then I suppose it's "technically" a GPL violation (IANAL and all that). I think that the *intent* of GPL is satisfied by making source available for major *releases*. In theory, DiSlord could arrange a group of beta testers, set up a private distribution channel, and send binaries (without source) back and forth and not get the GPL knickers in a twist. This would be no different from a group of developers at a company all working on various pieces of a product. But why bother. Yes, I understand "thin edge", "camel's nose", "slippery slope" arguments. Ultimately, though, the question is whether *meaningful* source code releases are occurring (and I think they are). I would say that this kind of (IMNSHO) bickering is why open source has a reputation for being a PITA. Be open about what you're doing. Publish binaries for test that are useful Publish source for releases If it goes on for 6 months with only binary, and there's significant changes in functionality, with no source release - then start asking about whether the author is living up to the spirit and intent of GPL. |
Re: Firmware and PC application stability
#stability
#nanovna-h4
#nanovna-h
#specifications
DiSlord and OneOfEleven thanks so much for your contributions that have moved the NanoVNA a step forward. A few bad actors always seem to mess things up for the majority.
With all the recent demands on your time, primarily from one or two sources, I figured at some point you would wonder if its worth the effort. Some people don't seem to realize you both have other lives besides your voluntary coding activities. Again, thanks for your many contributions and helping us to better understand the capabilities of the NanoVNA. - Herb |
Re: Dreaming a new option for nanoVNA
On 8/6/20 12:30 AM, OneOfEleven wrote:
On Wed, Aug 5, 2020 at 04:27 PM, Piero Tognolatti wrote:I think separating the "instrument functions" (on the nanoVNA) and the "data collection funtions" (on the Pi) is actually how you want to do it. Focus on instrument capability, not data logging. There's myriad different data logging applications, and most of them will not want "snapshot ever N seconds" - often, there will be other things that need to happen (external configuration of the unit under test). |
Re: Firmware and PC application stability
#stability
#nanovna-h4
#nanovna-h
#specifications
@DisLord and @OneOfEleven
It is unfortunately significant nowadays that many users are using free software but constantly ask for new features and also complain about this and that. You can't please everyone! But I want to say as many of us: please stay and go ahead! You did excellent work in the last month/weeks and we ALL do have advantages from your work. The community and also the little VNA's need people like you! Don't let such users put you under pressure and loose the fun! We all will be very sad if you both will leave... Don't go! Chris |
Re: Firmware and PC application stability
#stability
#nanovna-h4
#nanovna-h
#specifications
Those of you that have cloned the repository, please provide the links to
toggle quoted message
Show quoted text
your copies. On Thu, 6 Aug 2020 at 12:42, DiSlord <dislordlive@...> wrote:
I delete my NanoVNA git, and cleanup all provided binaries from this forum |
Re: NanoVNA firmware user interface mod
#mods
On Thu, Aug 6, 2020 at 09:40 AM, Jos Stevens wrote:
============================================================ Yes. Because unfortunately it was disabled. We hope it will be for a short time. They are important jobs. |
Re: NanoVNA firmware user interface mod
#mods
Thank you Igor, I got an 404 Error on Github !
toggle quoted message
Show quoted text
Op 6-8-2020 om 14:35 schreef Igor Jobim: Unfortunately OneOfEleven disabled his collaborations on Github. |
Re: NanoVNA firmware user interface mod
#mods
Archives are today's collaborations. The latest update.
|
Re: Dreaming a new option for nanoVNA
David,
The writing to the SD card is every few seconds which will do nothing to prematurely wear out the device. I use an SD card in my dashcam that is written to regularly and it's been good for 3 years now Besides, you don't put a 128gb part in the Nano, you use a small capacity card that costs $2 ... Larry On Thu, 6 Aug 2020 at 6:46 AM, David J Taylor via groups.io<david-taylor@...> wrote: I've added the ability to auto save to SD card every 'n' seconds for those that have SD cards on their nano's. The option is in the "SD CARD" menu. A setting of '0' seconds disables auto save. You can find the NanoVNA-H firmware (and windows software to upload the firmware) in the "Release" folder here .. I can't do H4 firmware because I don't have a H4 to test with. =========================== Good way to take the life out of the SD card!? But I hope you only save when a change is detected? Cheers, David -- SatSignal Software - Quality software for you Web: Email: david-taylor@... Twitter: @gm8arv |
Re: NanoVNA firmware user interface mod
#mods
Unfortunately OneOfEleven disabled his collaborations on Github.
This is the last file FW and SW. 73 !! |
Re: NanoVNA firmware user interface mod
#mods
Hi Dave,
toggle quoted message
Show quoted text
Thank you ver, very much? Dave , I went there and foud nanovna.exe, but I cannot download the binairy, I'm directed to the soutce files, I'm just learning how to do in Github. I will see hhow to mange.. Jos Op 6-8-2020 om 14:07 schreef Dave_G0WBX via groups.io: It's located here Jos .. |
Re: Firmware and PC application stability
#stability
#nanovna-h4
#nanovna-h
#specifications
I fully support this content, please DiSlord and OneOffEleven stay for the good willing community, please please .
toggle quoted message
Show quoted text
Op 6-8-2020 om 13:59 schreef CT2FZI:p @OneOfEleven and @DisLord, |
Re: Firmware and PC application stability
#stability
#nanovna-h4
#nanovna-h
#specifications
Igor,
DiSlord and others post interm releases on the forums in order to have members conduct tests and provide feedback.? This is a hobby for him, not a business. DiSlord updates his GitHub repo every few weeks which is fine for everyone on the forum except maybe 2-3 members out of 6880 members! You are free to fork DiSlord's software and develop and test your own improvements and release them on the forum...so? Have patience.? ... Larry On Thu, 6 Aug 2020 at 5:57 AM, igor-m<mikki@...> wrote: On Wed, Aug? 5, 2020 at 05:58 PM, DiSlord wrote: When you distribute the 1.0.XX binaries (like here on this forum or on cqham.ru or vrtp.ru) you shall provide the source code on your github too. It does NOT matter whether those binaries are called "final" or "beta". For example - with "1.0.14" beta binary the community has to be able to build the "1.0.14 beta" out of the source code on your github. Or i must add on my github every my test option?Yes. Otherwise one can distribute "test" or "beta" binaries for next 10years without providing source code. And the "open-source" project bites the dust. Or ... i should support code? But sorry for this need a lot of time, and thisNobody can ask you to support the code, this is an open source project. HTH |
Re: New topic for test new nanoVNA features
#nanovna-h
#nanovna-h4
#beta
#test
Hi DiSlord
is it normal that the on / off configuration of the traces is not saved? When I browse the menus I often have freezes with version 1.0.13 and 1.0.14. it is not systematic. This often happens with the "Version" menu I have never seen this before with version 1.0.11 |
Re: Firmware and PC application stability
#stability
#nanovna-h4
#nanovna-h
#specifications
Very well expressed, and you have my 100% agreement!
toggle quoted message
Show quoted text
I can see NO non-compliance with the GPL in the way that beta testing has been conducted via this forum, and NO need to change behaviour in any way. PLEASE continue, guys. Mike - M0MLM On 06/08/2020 12:59, CT2FZI wrote:
@OneOfEleven and @DisLord, |
to navigate to use esc to dismiss