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: NanoVNA-Saver 0.2.0
Hi John,
toggle quoted message
Show quoted text
my experiments in this field have been very limited - the feature was added with the encouragement of David F4HTQ. He submitted to me an S2P file of a measurement of a toroid, and a curve shape: He believed this could be approximated as R/¦Ø and X/¦Ø, so I implemented it, and managed to create the following graph: [image: image.png] Which seemed to fit quite well, even though the units aren't exactly the same. So, for now, all I know how to do is: Given a permeability chart from a manufacturer, replicate the same curve shape vs frequency using the NanoVNA. I hope it's useful ;-) -- Rune / 5Q5R On Wed, 13 Nov 2019 at 01:22, John AE5X <ae5x@...> wrote:
Now that the capability is there in the software, how would one use the |
Re: NanoVNA-Saver 0.2.0
Hi Tom,
toggle quoted message
Show quoted text
scaling of the input fields and avoiding "overflow" is on the todo list. :-) User interface design isn't my strong point, and I probably have a strong habit of testing the software with my preferred settings - 8pt font, for example - and never really looking at what other users might set it up as. Having it run on at least 3 different operating systems doesn't help that ;-) But, I am going to look into it, both scaling the interface as the font size changes, and organising the layout to make the most of a limited screen size. I hope you continue to enjoy using the software! -- Rune / 5Q5R On Tue, 12 Nov 2019 at 20:35, Tom VA7TA <tma.7ta@...> wrote:
Hi Rune, |
Re: NanoVNA-Saver 0.2.0
STM32CubeIDE is based on eclipse and allows debugging with with the stm
serial jag device which can be gotten cheaply as Chinese clones from ebay. There are several YouTube tutorials on the software. I just started using it yesterday and have built the normal led blink program and single stepped through it on a ST demo board based on the stm32f051c8t6 device. Good luck with your project and let the group how you proceed. On Tue, Nov 12, 2019, 11:22 PM vaclav_sal via Groups.Io <vaclav_sal= [email protected]> wrote: On Tue, Nov 12, 2019 at 09:33 AM, Oristo wrote:well. |
Re: NanoVNA vs. NanaVNA-Saver
#calibration
Hi Barry,
I don't know that you would need to do the whole copy around thing. I haven't tried it, but I think it would work fine selecting a calibration slot, slot 1 for example, and then using NanoVNA-Saver with the device with that calibration active in the calibrated range. *However*: My personal preference is to have Cal 0 be full span, and then making a calibration within NanoVNA-Saver, using the calibration assistant, with the "Segments" count set to perhaps 10 or even 20 - which gives you 1010 or 2020 data points for the calibration. This calibration can be full span, or for the range you are interested in. You can then save this, or any other calibration you make, as files which you can name more intuitively than "cal 0", "cal 1" etc. ;-) It's worth noting, that any calibration in NanoVNA-Saver is in reference to the particular calibration done on the NanoVNA: So if you re-calibrate your NanoVNA, your NanoVNA-Saver calibration ceases to be valid, and may give incorrect readings. -- Rune / 5Q5R On Tue, 12 Nov 2019 at 01:26, Barry Jackson via Groups.Io <G4MKT= [email protected]> wrote: On 08/11/2019 15:18, Nick wrote: |
Re: Nanovna-Saver 0.2.0 MAC
Hello Dana,
toggle quoted message
Show quoted text
thanks for the heads up! :-) -- Rune / 5Q5R On Wed, 13 Nov 2019 at 03:40, Dana Shtun <ve3dss@...> wrote:
The latest version seems to be working just fine on my mac. |
Re: NanoVNA-Saver 0.2.0
vaclav_sal
On Tue, Nov 12, 2019 at 09:33 AM, Oristo wrote:
Silly questions. Can it be added to Eclipse IDE as "plug-in" ?? But it woudl make more sense , KISS, to use it as standalone IDE, right? It woudl be easier to have both "running" and just switch between them as necessary. I am just looking for real debugger IDE and STM32CUBEIDE seems to be the ticket. |
Re: Now at Walmart
vaclav_sal
Stay far away from this 3rd party seller. There are typos all throughout their company info and their shipping policy looks strange and has many spelling mistakes as well.
Wow, now we judge products by spelling errors. Never mind that Wally's business model put many establishment where queens English was practiced out of business, employs senior citizens etc. How shallow can your get? I am ordering mine from guess who? |
Re: Now at Walmart
Stay far away from this 3rd party seller.? There are typos all throughout their company info and their shipping policy looks strange and has many spelling mistakes as well.?
On Tue, 12 Nov 2019 at 8:12 PM, DuWayne Schmidlkofer<duwayne@...> wrote: I was browsing for something else when this link popped up. -- DuWayne? KV4QB |
Re: DFUseDemo
I never had to use Zadig in Windows 10 64bit to use DFUseDemo. This is probably a problem by you. Put your Hardware Device Manager window on and examinate following. Try uninstalling Zadig (actually a USB driver) until it no longer appears in Hardware Devive Manager window. This may have to be done multiple times. In the View menu, put the option "show hidden devices", you will see them grayed out in the list, and see if there is an earlier installation of Zadig (Zadig itself is not visible, but 'USB lib device' or something similar - i have not the exact names, but don't delete the 'Universal Serial-Bus Controllers'!) delete or uninstall all gray drivers until they are gone. The Wiki Files contains the manual of DFUseDemo and its installation. Follow it carefully. I test it again here, and you don't need Zadig. If you connect the Nano, with the boot button pressed, a "STM Device in DFU Mode" will first appear in Hardware Device Manager (with a yellow triangle). If you wait 20 seconds, the driver is automatically loaded in Windows, and the "STM Device in DFU Mode" is added to the list "Universal Serial-Bus Controllers". If you turn the Nano off, "STM Device in DFU Mode" will remain in the list, but then turn gray.
on1bes |
DFUseDemo
I am running Windows10 Home 64 Bit, and had DFUsDemo running OK
After a firmware update (Erics Version 2.3) suddenly DFUSE Demo no more sees my NanoVNA-H . Windows devicemanager shows the the device in DFU mode as "STM32 Bootloader" and when I run Zadig I can select "STM32 Bootloader" and install the drivers. In the device manager I see for "STM32 bootloader" these drivers : WinUSB.sys, WdfCoinstaller01011.dll and WinUSBcoinstaller2.dll are these correct ?? I uninstalled and re-installed DFUseDemo, whatever i do, nothing helps. So now I can no more.update the firmware ! Is there anyone who can help to solve this problem ? Many thanks in advance Jos |
Re: coax fatigue
#test-jig
On Tue, Nov 12, 2019 at 09:37 AM, WB2UAQ wrote:
" Just wish it could measure higher impedances more accurately " ----------------------------------------------------------------------------------------------------------- An HP8753 would not have helped you to measure higher impedances, I used one for years in my workplace and once you got too far off of 50 ohms the accuracy declined. In general, I believe that is true with all VNA's with a 50 ohm input impedance. The HP8753 also started at 300 kHz which meant my company had to purchase a second VNA for lower measurements. I'd love to own a HP 8753 but I also know I can't afford the maintenance costs that would eventually be required. - Herb |
Re: coax fatigue
#test-jig
Hi I'm a newbie when it comes to the NANOVNA but over the years I have been involved with many different aspects of radio both amuter and professional.
SMA connectors are not intended for repeated connection and reconnection, there is little or no strain relief with SMA connectors, use good quality connectors and cable, use large radius no sharp bends in test environment. When the integrity of a connection is of concern (SMA connectors on NANO) and the connectors have to be connected or reconnected many times, for example in testing and re testing/integration it is common to fit additional sacrificial connectors to those on the unit (I have). This is to prevent damaging the connector's and can be replaced and still preserving the integrity of the main connector. -- Raymond G8KPS |
Re: coax fatigue
#test-jig
I am thinking that the point of putting the nano in an enclosure is to stabilize the
poor isolation, not necessarily to eliminate it. But when the nano's leak is stabilized, the ISOL CAL should then enable good correction. This assumes that what goes outside the enclosure is done with good quality cables (at least with respect to leakage) that are terminated. It would probably help to terminate the ends in items that roughly duplicate the impedances that the DUT will provide, although this is admittedly not very practical in most cases. BTW, SMA(M) cables that are left dangling with nothing connected can exhibit wildly variable leakage from the ends. The center pin is coupled capacitively to the nut, whose contact to the main body of the connector can range from only fair to non-existent, depending on how it is laying (i.e., on what forces are acting on the nut and from what directions, etc). RF leakage of this kind leads to RF currents on the outside of the cable, which can resonate at various frequencies. radiate to nearby cables that are similarly indisposed, etc. So even if you can't spare good terminations, at least screw each cable end onto something that is well-shielded for the isolation CAL step. Dana |
to navigate to use esc to dismiss