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: Bad Coax...feedback requested
You might try rapping the connectors on the ends of the line and check for any changes in S11 or S21 response. S21 loss should be less then -0.5 dB @ 30 MHz for 350' of 1.25" hardline.
If connectors are good and cable has not taken a lightning strike in its past life you should be more than 20 dB return loss on S11. |
Re: errors of "error" models
John Ackermann N8UR
I hesitate to jump into this, but...
toggle quoted message
Show quoted text
The "correction coefficients" that professional VNAs apply to compensate for, e.g., fringing capacitance in the opens, are not just electrical measurements of selected components.? Things like fringing capacitance are not flaws in the standards, but inevitable results of the physical realization of the electrical concept of an "open". The coefficients do not come from electrical measurement of some "gold" standard.? Instead, they are derived from the physical characteristics of the standards, which are manufactured with extremely tight mechanical tolerances.?? From these characteristics the coefficients can be determined by using fundamental equations like the capacitance formula more accurately than is possible by electrical measurements.? (And of course they are sanity-checked electrically as well.)? So, the coefficients are not really correcting for "imperfections", but are instead acknowledging at a fundamental level the properties of physical objects, to improve the mathematical models of those objects being used in the correction equations. John ---- On Jan 5, 2020, 11:04 PM, at 11:04 PM, Gary O'Neil <n3go@...> wrote:
Hi Jeff; |
Re: SMITH CHART TUTORIAL
Hey Allison,
toggle quoted message
Show quoted text
Thanks for the hints. Any idea on the referenced books? Thanks, Adrian On Sun, Jan 5, 2020 at 4:19 PM aparent1/kb1gmx <kb1gmx@...> wrote:
KV5R, |
Re: First PCB pictures of the V2
Hi Gabriel,
toggle quoted message
Show quoted text
MiniCkts and Toko will build whatever you want - it all boils down to how much you're willing to pay... ...and yes, for a short manufacturing run like this, it's not worth it. Unless... If you can show them how the directivity is improved, maybe they will come out with a standardized part - who knows. Just a thought. Great work there ! Regards, Larry On Monday, January 6, 2020, 5:22:04 a.m. GMT-5, Gabriel Tenma White <owowowowo123@...> wrote:
はぁ (ha), that did the trick. I did the surgery on only one leg so there is still some imbalance, but the directivity improved from 8dB to 16dB, on par with the performance with tuning (see attached). Don't think I'll ever convince TOKO or mini-circuits to build baluns vertically like this though, and it won't fit in the shield can anymore, so I think the tuning will stay for now. |
Re: Bad Coax...feedback requested
I missed what was actually being tested....
toggle quoted message
Show quoted text
Also, if one is testing cables themselves, is there a finite distant limit? BR Tim K4SHF On Mon, Jan 6, 2020 at 6:28 AM Dana Whitlow <k8yumdoober@...> wrote:
Robert, |
Re: First PCB pictures of the V2
Good to hear that better symmetry is a solution. The problem with tuning as you do now is that it is frequency dependent. Maybe you can try to increase the pcb trace length to compensate for the length difference? You'd probably need to build a specific test pcb for that. I'll study the schematics and get back to you. I'm developing ideas to make a V3 like you (full 2-port, 6 GHz at least, filtered output signals, adjustable signal levels, >100 dB dynamic range, programmable DC bias on RF ports to investigate, 7 inch display, etc.) Lack of time is the main problem. My V3 would be more performance optimized than cost optimized.
toggle quoted message
Show quoted text
Op 6-1-2020 om 11:21 schreef Gabriel Tenma White: はぁ (ha), that did the trick. I did the surgery on only one leg so there is still some imbalance, but the directivity improved from 8dB to 16dB, on par with the performance with tuning (see attached). Don't think I'll ever convince TOKO or mini-circuits to build baluns vertically like this though, and it won't fit in the shield can anymore, so I think the tuning will stay for now. |
Re: Bad Coax...feedback requested
Robert,
It would be desirable if you could also measure the transmission through the cable, including both magnitude and phase versus frequency. Plus any info you have about the supposed characteristic impedance and velocity factor of the cable. Extend the lower frequency limit down to 50 kHz as well. A second set of equivalent plots but with the nano's scan set for a span of about 10 MHz and a center frequency well up in the VHF regime (~150 MHz would be fine) might also be pretty informative. These should also include the scan of the termination that you're using by itself. The overall shape of the plot is somewhat consistent with two point reflections of roughly equal magnitude, separated in round-trip time by a bit under 500 nsec. However, the deteriorating overall return loss at increasing frequency is not really consistent with that simple model. But if your connections to the hard line were a bit crude, creating added impedance bumps at the two ends, the curve I've seen so far would be better-explained. Could you also send a photo showing exactly how you are physically interfacing to the hard line from the small cable environment? What I've seen so far suggests a cable whose impedance is not really 50 ohms, combined with some other issue such as (perhaps) impedance bumps at the two ends. The period of ~2 MHz seen in the S11 plot is not consistent with a physical length of 350 ft- in fact it's off by almost a factor of 2 if one assumes a VF of 0.67. Dana K8YUM |
Re: F303 and 4" LCD for next generation NanoVNA
#circuit
#flash_size
#improvement
#enclosure
#battery
On Sun, Jan 5, 2020 at 08:57 PM, <hugen@...> wrote:
English translation with the help of "Microsoft Translate" ….. Please forgive me for replying in Chinese. The GD32F303's cheaper price and faster speed are very attractive, but we chose the STM32F303CCT6 because the general community is more familiar with its use. Thanks to the application of the stm32f303 in Mr Takahashi's (edy555) centsdr project, AA 6KL was able to quickly migrate the STM32F303CCT6, while maintaining a high degree of software compatibility with the current version of NanoVNA. This even allows users to use the new MCU and 4-inch LCD screen, with simple modifications, on the current board, which is the feature that was most requested. We all have our own jobs, and only our spare time to devote to development, transplanting the GD32F303 requires more effort. Even if the current version of STM32F303CCT6 is not perfect, choosing a MCU more familiar to the community can attract more enthusiasts. Your SAA project looks great and should upend many people's previous perceptions of cost and performance. Just as with edy555's original release of the NanoVNA, it is hoped that this project will attract more young people to study RF, and provide enthusiasts with more practical tools. AA6KL further refines the NanoVNA's development with the launch of the NanoVNA-H with stenet32F303CCT6 and 4-inch displays, in the hope that more enthusiasts will be involved in the community. Hugen Hope not too much was lost in translation. - Herb |
Re: First PCB pictures of the V2
はぁ (ha), that did the trick. I did the surgery on only one leg so there is still some imbalance, but the directivity improved from 8dB to 16dB, on par with the performance with tuning (see attached). Don't think I'll ever convince TOKO or mini-circuits to build baluns vertically like this though, and it won't fit in the shield can anymore, so I think the tuning will stay for now.
|
Re: Bad Coax...feedback requested
On Mon, 6 Jan 2020 at 00:28, Robin Midgett <K4IDC@...> wrote:
I've calibrated my NanoVNA & connected it to an approximate 350' length ofThe S11 plot is attached...not pleasing at all. Can anyone on the list say what the cause may be? VNA measurements require phase stables cables. The ones I use for microwave use (upto 26.5 GHz) are 24” long and cost $5000 a pair. The changes in phase you will observe with very long cables is going to be much higher than short cables of the same quality. Flexing, temperature changes are really going to screw you up with long cables. When I do critical measurements I try to eliminate cables completely. Measurements of my VNA calibration standards sold in kits are made There are some ways to test cables for their suitability for VNA use. I will add some details later on my website under the FAQ section. There are other issues too, but they might not be relevant on the NanoVNA. As the frequency of the source is swept, the detector looks for that frequency. If there’s a very long cable, by the time the reflection is seen back at the VNA, the source has changed frequency and its detector is then looking for higher frequency than what it receives. The solution on some VNAs is to slow the sweep speed down. Since the NanoVNA does sweep that fast, it is unlikely to be the problem. Reducing the span to the absolute minimum you can get away with might help, as the frequency shift between each point will be much lower. What’s the temperature stability of your load like? If you take a load from room temperature and change its temperature much, it is likely to change in value. I have ideas, but I don't want to sway anyone's opinion.. I wonder if any of your ideas are the same as mine! Dave, 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 |
Re: First PCB pictures of the V2
Hi Gabriel,
toggle quoted message
Show quoted text
As an experiment, you could try to make a more symmetrical balun by placing the core vertically over the pcb and making sure the wires have equal length. Another request, could you publish the schematics in pdf? I'd like to study them and give some feedback. I don't use gEDA, I stick with KiCAD, Pulsonix, Ultiboard and Altium. Happy 2020!, Reinier Op 6-1-2020 om 08:40 schreef Gabriel Tenma White: I just tried the TC1-1-13M on two units. With a balanced (symmetrical) bridge circuit (like the one in v2_0) the directivity is not good, around 8 to 10dB up to 3GHz, but just out of curiosity I tried it on a new unit (v2_2) that has the 0.3pF tuning, and the directivity graph turned out nearly identical as before with the old balun (TOKO 617DB-1023=P3), with 17dB worst directivity. Looking at the pictures it seems to have the same physical asymmetry as the 617DB-1023=P3 (see attached), but the good news is this tuning seems to be applicable to more than one manufacturer's baluns, so I can have a second source just in case. |
Re: Bad Coax...feedback requested
From: Robin Midgett
I've calibrated my NanoVNA & connected it to an approximate 350' length of coax with a known good dummy load on the opposite end. The S11 plot is attached...not pleasing at all. Can anyone on the list say what the cause may be? I have ideas, but I don't want to sway anyone's opinion.. Attachments: 350_ coax with dummy load.png: /g/nanovna-users/attachment/9185/0 ============================== Robin, You might try a TDR plot and see whether there is an obvious discontinuity? Cheers, David -- SatSignal Software - Quality software for you Web: Email: david-taylor@... Twitter: @gm8arv |
Re: F303 and 4" LCD for next generation NanoVNA
#circuit
#flash_size
#improvement
#enclosure
#battery
For an N connector, the seller must have an adapter option with a calibration kit.
My counterpart. It is very convenient to work. And the BNC option should be similar. It solves many technological problems in production. (Apologies for bad English from Uncle Gogl.) |
Re: F303 and 4" LCD for next generation NanoVNA
#circuit
#flash_size
#improvement
#enclosure
#battery
Please forgive me for using Chinese reply.
请原谅我直接使用中文回复。GD32F303更便宜的价格和更高的运行速度真的很吸引人,但是我们还是选择了社区更加熟悉的STM32F303CCT6,得益于高桥先生centsdr项目上stm32f303的应用,AA6KL 很快完成了STM32F303CCT6的移植,与当前版本的nanovna保持了高度的软件兼容性,用户甚至可以在当前的电路板上通过简单的修改使用新的MCU和4寸的液晶屏,这正是这个社区需要的。我们都有自己的工作,仅在业余时间开发,移植新MCU需要更多的精力,即使当前STM32F303CCT6版本也还不完善,选择一个社区更加熟悉的MCU可以吸引更多的爱好者。 您的厂础础项目是一个非常了不起的项目,应该会颠覆很多人之前的对成本和性能的看法。正如别诲测555最初发布狈补苍辞痴狈础时候那样希望通过这个项目吸引更多的年轻人关注射频,也广大爱好者提供更加实用的工具。 AA6KL 正在进一步完善它的开发,采用STM32F303CCT6和4英寸显示器的NanoVNA-H很快会推出,希望社区能有更多的爱好者参与。 胡根 |
Re: errors of "error" models
Hi Jeff;
Per my post: @ Gary O'Neil - /g/nanovna-users/message/9184 I don't find any source of disagreement in your posts: @ Jeff Anderson - /g/nanovna-users/message/9178 @ Jeff Anderson - /g/nanovna-users/message/9181 I will also confess that I overstated a Hackborn quote which modified its more accurate interpretation. He didn't dismiss anything, but rather makes the statement that all of the errors and uncertainties in the system are measured and remembered. By that inexcusable but excellent example of my inability to make and defend my point; I will attempt instead to understand your understanding of the process, and search for where the two will hopefully converge. After several reads and re-reads of your and Erik's posts; I think you two may be on the same page. Your post, and another by Dr. Kirby: @ Dr. Kirby - /g/nanovna-users/message/9183 hint at a possible disconnect in "my" understanding, which may be linked to a vagueness in the use of jargon, or more pathetically, my lack of understanding of the jargon in use. The way I am interpreting your posts, I see the use of the terms calibration, characterization, and correction. You also identify the noise and imperfect characterizations of the standards as not being corrected by the error correction process.... referring to a Hand quote. You also make reference to HP and Keysight quotes... both of which I agree with as being correct. To my point; any statement that the "accuracy" of something (anything) used for the purpose of improving the accuracy of the measurement must itself be accurate cannot be argued. It is made true by the way it is stated and/or presented. Clearly there is no argument that even with the highest of quality in the standards, at some upper limit of frequency, the manufacture of standards sets to the exacting dimensional tolerances required to guarantee that the reference plane remains constant becomes unachievable, significant rotational errors occur and corrections for the known and well defined imperfections are needed in the calibration in order to make meaningfully accurate measurements. So my lack of understanding seems to lie in the question being what's the point of attempting to model imperfect standards of uncertain accuracy, and using that model to corrupt the ability of the algorithm to accurately measure and remember all of the system errors and uncertainties with uncertain guesses at what the ones that are measured have been characterized to be? Are not the errors that manifest themselves as problematic, only problematic because they result from differences in the location of their respective reference planes? the uncertainties of the parasitic reactance properties associated with each of the standards are measurable, and thus they will be "measured and remembered". As such, they are all present and accounted for in the calibration. Characterization of the standard reference plane location (degrees per GHz) would seem to be a more precise and accurate manner to compensate (not calibrate) for their respective rotational offsets without compromising the integrity of the calibration algorithm. After that; how precise does the rotational compensation need to be in order to sufficiently orient the regions of infinity to the VNA user such they are presented with the most accurate measurement the VNA is capable of providing? This brings up yet another question. If the devices are "measured and remembered" as the math clearly dictates, what would cause a short and an open (defined as such) to appear anywhere other than the locations -1 and 1 without biasing the algorithm to place them differently? If they are intentionally placed at a different location, what is the justification for doing so, since this would seem to create a need to compensate for the induced post calibration offset errors ? -- 73 Gary, N3GO |
Re: Bad Coax...feedback requested
Thanks Dave, I'll try that soon..hopefully tomorrow evening.
toggle quoted message
Show quoted text
On Sun, Jan 5, 2020 at 06:47 PM, David Eckhardt wrote:
|
Re: Alibaba ordering
Thanks for the follow-up Chris. I ordered on Friday and pretty much followed the same procedure although I have not communicated with her since I sent the payment because they were already well into the weekend at that point. I chose the DHL shipping option so I hope to see some sort of tracking info tomorrow.
|
to navigate to use esc to dismiss