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 software developers wanted
#hacking
That is a lot of data to buffer.
On Wednesday, November 6, 2019, 12:14:38 p.m. GMT-5, Oristo <ormpoa@...> wrote: > At the minimum you may need to include some ferrite beads in the power and serial connections.Firmware should sleep Bluetooth while sweeping and pause sweeps while Bluetooth is active. |
Re: NanoVNA software developers wanted
#hacking
At the minimum you mayFirmware should sleep Bluetooth while sweeping and pause sweeps while Bluetooth is active. |
Re: NanoVNA software developers wanted
#hacking
Before adding a radio transmitter and a second microcontroller such as a
HC-05 to the NanoVNA, you may want to examine how much RFI it might introduce into the NanoVNA. My experience with my VNA, which I have connected a HC-05 to, is that it introduces a lot. At the minimum you may need to include some ferrite beads in the power and serial connections. On Wed, Nov 6, 2019 at 11:27 AM William Heller <wheller34052@...> wrote: I am a retired embedded processor engineer an can recommend the ESP32 |
Re: Chasing ghosts???
#internals
#calibration
RG-58 is just plain junk cable, and should never be used or (especially) trusted to
yield meaningful results in any measurement situation. The center conductor flops around inside the shield at the slightest provocation (even quantum fluctuations), leading to impedance variations from location to location as well as to phase variation with bending. Further, RG-58 and similar single-shielded cables often have very poor shielding integrity. Also, with just about any cable, if it is poorly made it can exhibit so-called "structural resonances" due to spatially-periodic variations in characteristic impedance arising from the manufacturing process. Normally this is a problem only with cheap cables, but in principle could occur with any. The result can be a surprisingly-sharp increase in attenuation at and beyond the resonant frequencies, even though said frequencies be far below the first "moding" frequency. Dana K8YUM |
Re: Chasing ghosts???
#internals
#calibration
And here are the results.
The first picture is with power level 3 when above 300MHz, second picture is with powerlevel is 0 for all frequencies. The noise is much higher with low power and that can be improved by running from a well regulated 5V supply. The scale of the logmag S11 is different so do not compare the angle but only if the cable loss is a straight line (which has not improved.....) So, although running at low power has a big impact as the uncalibrated jump at 300MHz is now almost gone, but this was mostly hidden by the calibration, There is maybe some impact above 600MHz. A bit less wild maybe..... -- Erik, PD0EK |
Re: NanoVNA software developers wanted
#hacking
I am a retired embedded processor engineer an can recommend the ESP32
programmed as a serial to bluetooth/WIFI adapter it is a 32 bit processor with the usual peripherals and both bluetooth and WiFi built in and do on and do small pub only costs a few do?lars. On Wed, Nov 6, 2019, 7:42 AM vaclav_sal via Groups.Io <vaclav_sal= [email protected]> wrote: Nice, but I am after adding the bluetooth externally. |
Re: T-Check for my nanoVNA - Results look excellent below 150 MHz and acceptable up to 300 MHz
Hi Rudi
Super you are on the way now. I just did a T-Check for some N cal kit work presently working on and it was below 1 % all the way. That is the magic of 12 term error correction (actually 10 term as isolation not done) Regarding the listType= lin I loaded into a text editor a s2p file I had saved long ago from the VNWA to study the header of the Touchstone file and there it was. It is just a comment line so why it had any impact I do not know I checked the Touchstone specification version 1.1 and it is not part of the specification at all. Kind regards Kurt -----Oprindelig meddelelse----- Fra: [email protected] <[email protected]> P? vegne af reuterr@... Sendt: 6. november 2019 16:34 Til: [email protected] Emne: Re: [nanovna-users] T-Check for my nanoVNA - Results look excellent below 150 MHz and acceptable up to 300 MHz ! ListType=Lin (This addition was probably not needed)Hello Kurt, This 'ListType=Lin' parameter was necessary :-) Question: where did you found that parameter 'ListType=Lin'? I looked in specification touchstone_ver2_0.pdf, and in VNWA_HELP_36.7.8.pdf and in How to perform a T-Check for a VNWA Calibration.pdf and did not found it. Now it works, see attached screen shot VNWA_nanoVNA-Saver_T-Check.png Thank you very much for this hint and you help. 73, Rudi DL5FA |
Re: NanoVNA software developers wanted
#hacking
if it would make more sense to add processor internally supporting wirelessLink added in /g/nanovna-users/wiki/Mods-and-Design-Notes |
Re: NanoVNA software developers wanted
#hacking
On Wed, Nov 6, 2019 at 10:44 AM, <hugen@...> wrote:
I think that cho45 should disable Bluetooth during nanoVNA measurements to avoid both power and interference problems. |
Re: T-Check for my nanoVNA - Results look excellent below 150 MHz and acceptable up to 300 MHz
! ListType=Lin (This addition was probably not needed)Hello Kurt, This 'ListType=Lin' parameter was necessary :-) Question: where did you found that parameter 'ListType=Lin'? I looked in specification touchstone_ver2_0.pdf, and in VNWA_HELP_36.7.8.pdf and in How to perform a T-Check for a VNWA Calibration.pdf and did not found it. Now it works, see attached screen shot VNWA_nanoVNA-Saver_T-Check.png Thank you very much for this hint and you help. 73, Rudi DL5FA |
Re: NanoVNA software developers wanted
#hacking
vaclav_sal
Nice, but I am after adding the bluetooth externally.
Like to ask if it would make more sense to add processor internally supporting wireless commodification. I have not done any research if such processor exists. Something in Raspberry Pi Zero style. |
Re: Voltage sensing diode
On Sat, Nov 2, 2019 at 11:41 AM, Nick wrote:
With BAV99 2 diodes and a fully charged battery set vbat_offset to 1000 andJust calibrated by setting vbat_offset so that the indicated voltage on the Version screen = measured battery voltage. Fully charged reading (LED1 not blinking) now 4140mV with vbat_offset set to 950. Estimated error +/-1%. The on screen charge indicator works well as the battery runs down. VBAT now < 3.7V under all charge conditions. Within Absolute maximum rating spec of 4.0V. Looking at the Fairchild data sheet a pair of 1N4148 should give similar results. |
Re: T-Check for my nanoVNA - Results look excellent below 150 MHz and acceptable up to 300 MHz
Hi Rudi
Correct about R&S T-Check, no way to get it to run on W10 Kind regards Kurt -----Oprindelig meddelelse----- Fra: [email protected] <[email protected]> P? vegne af Kurt Poulsen Sendt: 6. november 2019 12:46 Til: [email protected] Emne: Re: [nanovna-users] T-Check for my nanoVNA - Results look excellent below 150 MHz and acceptable up to 300 MHz Hi Rudi I did export a s2p file from latest version 1.5 of the NanoVNA-saver and it was imported right away in the VNWA It is in the format RI meaning real Imaginary S parameter so why you have no success with the VNWA is a big question mark I have made a note yesterday about a T-Check file with an extra S at the end of the # line but that is not the case here. I have a comment about calibration when doing a T-Check. When the two test cables are connected to the Ch0 and Ch1 it must be S11 reflection calibrate calibrated with the SMA male SOL standards connected to the female female adaptor so it constitutes a female calibration kit and in the NanoVNA-saver the female kit data entered. This way the reflection calibration plane is identical to the male SMA on the Ch0 test cable. In addition the delay of the female female adoptor must be entered in the nanoVNA-saver for thru calibration. If this methos is not followed the exist serious phase errors between the reflection and transmission measurements and a T-Check will look crazy. Did you follows those guide lines ?? I will do a test with the R&S T-Check software else as you have the VNWA it is much simpler. Import the S11 and S21 s2p file and copy S11 to S22 as well S21 to S12. The open a custom trace and in the Expression line and do a right click, then the T-Check formula is ready to be loaded and after pressing OK then set the trace to linear magnitude reference to 1 and reference position to 5 and the scale to e.g. 0.1/div which means one division equal to 10% and 0.01 equal to 1% / div Give the custom trace a Caption name as T-CHK so the trace is name accordingly. You may save the Custum trace for later use Kind regards Kurt -----Oprindelig meddelelse----- Fra: [email protected] <[email protected]> P? vegne af reuterr@... Sendt: 6. november 2019 07:08 Til: [email protected] Emne: Re: [nanovna-users] T-Check for my nanoVNA - Results look excellent below 150 MHz and acceptable up to 300 MHz On Tue, Nov 5, 2019 at 11:40 PM, Kurt Poulsen wrote: UPS about the R&S TR-Check have you tried to run in W95 compatibilityHello Kurt, After reading T-Check.pdf from you from 2010-01-31, I tried under Windows 10-64 The Installation files are from 1997. When trying to start SETUP.EXE it was not possible. Next I started the MS compatibility check, Windows 8 was recommended, and set. That does not work too. Next with administrator rights, no success. Next try was to install under Windows 7-32. That works. A test with the provided data file ZVR.S2P works. But my from NanoVNA-Saver exported, extended S2P file was not accepted. I could not figure out, what was wrong with the format. Next I tried VNWA version 36.7.8.1 after reading your text from 2014-01: How to perform a T-Check for a VNWA Calibration.pdf A test with data file ZVR.S2P works. But my from NanoVNA-Saver exported, extended S2P file was not accepted. I could not figure out, what was wrong with the format. Next I found the spreadsheet from Erik: Thread: Trying to understand the T-Check outcome of the nanoVNA /g/nanovna-users/message/3020 T-Check.xlsx (199 KB) I could not make it to work with my data file. Then I posted in /g/nanovna-users/message/6502, asking for help. Erik provided a new version of his spreadsheet T-Check.xlsx (220 KB) /g/nanovna-users/message/6505 I imported my data file T-CheckR31.S2P and it worked, see /g/nanovna-users/message/6517 I will optimise this spreadsheet to accept direct NanoVNA-Saver exported S2P files, without modification. I read, that in case of a symmetric T-Check hardware setup you could copy to fill last 4 columns: copy C2-S11Real to C8-S22Real copy C3-S11Imag to C9-S22Imag copy C4-S21Real to C6-S12Real copy C5-S21Imag to C7-S12Imag 73, Rudi DK5FA |
Re: T-Check for my nanoVNA - Results look excellent below 150 MHz and acceptable up to 300 MHz
Hi Rudi
I did export a s2p file from latest version 1.5 of the NanoVNA-saver and it was imported right away in the VNWA It is in the format RI meaning real Imaginary S parameter so why you have no success with the VNWA is a big question mark I have made a note yesterday about a T-Check file with an extra S at the end of the # line but that is not the case here. I have a comment about calibration when doing a T-Check. When the two test cables are connected to the Ch0 and Ch1 it must be S11 reflection calibrate calibrated with the SMA male SOL standards connected to the female female adaptor so it constitutes a female calibration kit and in the NanoVNA-saver the female kit data entered. This way the reflection calibration plane is identical to the male SMA on the Ch0 test cable. In addition the delay of the female female adoptor must be entered in the nanoVNA-saver for thru calibration. If this methos is not followed the exist serious phase errors between the reflection and transmission measurements and a T-Check will look crazy. Did you follows those guide lines ?? I will do a test with the R&S T-Check software else as you have the VNWA it is much simpler. Import the S11 and S21 s2p file and copy S11 to S22 as well S21 to S12. The open a custom trace and in the Expression line and do a right click, then the T-Check formula is ready to be loaded and after pressing OK then set the trace to linear magnitude reference to 1 and reference position to 5 and the scale to e.g. 0.1/div which means one division equal to 10% and 0.01 equal to 1% / div Give the custom trace a Caption name as T-CHK so the trace is name accordingly. You may save the Custum trace for later use Kind regards Kurt -----Oprindelig meddelelse----- Fra: [email protected] <[email protected]> P? vegne af reuterr@... Sendt: 6. november 2019 07:08 Til: [email protected] Emne: Re: [nanovna-users] T-Check for my nanoVNA - Results look excellent below 150 MHz and acceptable up to 300 MHz On Tue, Nov 5, 2019 at 11:40 PM, Kurt Poulsen wrote: UPS about the R&S TR-Check have you tried to run in W95 compatibilityHello Kurt, After reading T-Check.pdf from you from 2010-01-31, I tried under Windows 10-64 The Installation files are from 1997. When trying to start SETUP.EXE it was not possible. Next I started the MS compatibility check, Windows 8 was recommended, and set. That does not work too. Next with administrator rights, no success. Next try was to install under Windows 7-32. That works. A test with the provided data file ZVR.S2P works. But my from NanoVNA-Saver exported, extended S2P file was not accepted. I could not figure out, what was wrong with the format. Next I tried VNWA version 36.7.8.1 after reading your text from 2014-01: How to perform a T-Check for a VNWA Calibration.pdf A test with data file ZVR.S2P works. But my from NanoVNA-Saver exported, extended S2P file was not accepted. I could not figure out, what was wrong with the format. Next I found the spreadsheet from Erik: Thread: Trying to understand the T-Check outcome of the nanoVNA /g/nanovna-users/message/3020 T-Check.xlsx (199 KB) I could not make it to work with my data file. Then I posted in /g/nanovna-users/message/6502, asking for help. Erik provided a new version of his spreadsheet T-Check.xlsx (220 KB) /g/nanovna-users/message/6505 I imported my data file T-CheckR31.S2P and it worked, see /g/nanovna-users/message/6517 I will optimise this spreadsheet to accept direct NanoVNA-Saver exported S2P files, without modification. I read, that in case of a symmetric T-Check hardware setup you could copy to fill last 4 columns: copy C2-S11Real to C8-S22Real copy C3-S11Imag to C9-S22Imag copy C4-S21Real to C6-S12Real copy C5-S21Imag to C7-S12Imag 73, Rudi DK5FA |
Re: Chasing ghosts???
#internals
#calibration
There is evidence in the Open and Load calibration measurement of something weird happening when going into harmonics mode, it is if the ratio of the reference signal and the measurement signal suddenly changes. This could happen when one of the two involved mixers (reflection SA612) goes into overload and generates more harmonics which where not there in the real test signal.
This is easy to test by keeping the SI5351 output stable when switching to harmonics mode instead of the 10dB increase currently done. Normally the nanoVNA automatically increases the SI5351 output but when you give the : power 0 console command the automatic increase is disabled and the drive is stable and there should no longer be a signal jump at 300MHz. Will test later today -- Erik, PD0EK |
Re: Chasing ghosts???
#internals
#calibration
So I did the same coax stub comparison between the V2 and the xaVNA (see attached). The measurements agree to about 0.1dB and those ripples are either physical or artifacts of my cal kit. The coax measured is a 15cm semirigid RG405 and the cal kit is a home made SMA female SOL similar to this one: . Ignore the S21 value though, I haven't yet put on the shields on the Nano.
|
to navigate to use esc to dismiss