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: Antenna simulation result different from experiment with NanoVNA
What Er did you use for the PCB Material?Unless it is very expensive material where the plot the Er by frequency, you really don't know the Er.
toggle quoted message
Show quoted text
It is industry standard to measure the Er at 1 kHz.Typically they list the Er for fiberglass PCB material.(Yea, the call it FR4, but you have not been able to buy real FR4 for the last 10 years.? The spec for FR4 calls for a Bromide anti-flammability that has been banned)Er is listed as 4.4, but as you go up in frequency Er drops.? At 2.4 GHz it is typically in the 3.8-3.9 range.? ? Personal experience in making thousands of 2.4 GHz patch antennas.? Kent WA5VJB On Thursday, September 1, 2022 at 05:31:26 AM CDT, Diane BONKOUNGOU <dianebonk2@...> wrote:
Hello everyone, I used OpenEMS software for my simulation and I got simulation results that are very different from my experimental result, I have a PCB antenna whose resonant frequency is around 2.4GHz. I design the same thing on OpenEMS but the simulation gives me a resonant frequency of around 2.66GHz. Such a difference of 0.2GHz is important in RF, isn't it?? Knowing that the frequency range of Bluetooth Low Energy is 2.4-2.5GHz. I have calibrated very well my NanoVNA and my experiment result must be good. I know that because I tested the Texas instrument PCB IFA antenna and I get the same result as in their Datasheet. Can you recommend a free tool for antenna simulation? I have searched but I can only find OpenEMS based on the FDTD method. The others are professional and paid tools for PCB trace antenna simulation. Best regards. |
Re: Antenna simulation result different from experiment with NanoVNA
On 01/09/2022 11:31, Diane BONKOUNGOU wrote:
Hello everyone,Can you upload the file and I'll have a look The dielectric constant you chose might differ from the real one depending on the material. There are also issues in getting the mesh riggt. I have a couple of PCB antennas for 1.3, 2.3 and 3.4GHz which are ok on the nanoVNA , I was planning to model. them . They seem to have a stripline matching section which might be tricky to model accurately. Brian -- Brian |
Antenna simulation result different from experiment with NanoVNA
Diane BONKOUNGOU
Hello everyone,
I used OpenEMS software for my simulation and I got simulation results that are very different from my experimental result, I have a PCB antenna whose resonant frequency is around 2.4GHz. I design the same thing on OpenEMS but the simulation gives me a resonant frequency of around 2.66GHz. Such a difference of 0.2GHz is important in RF, isn't it? Knowing that the frequency range of Bluetooth Low Energy is 2.4-2.5GHz. I have calibrated very well my NanoVNA and my experiment result must be good. I know that because I tested the Texas instrument PCB IFA antenna and I get the same result as in their Datasheet. Can you recommend a free tool for antenna simulation? I have searched but I can only find OpenEMS based on the FDTD method. The others are professional and paid tools for PCB trace antenna simulation. Best regards. |
Re: Anything for Windows 7?
I moved from Windows XP Pro 32 bit to Windows 10 64 bit, starting october last year.
It was definitely not a painless transition. I installed W10 on a new computer, and had to run with both in parallel for three months, while slowly learning to tame that crazy overactive beast W10 is, moving over my software, data, and part of the hardware, and search for replacements for many programs that would not run on W10. Only around Christmas I could finally stop using the old computer. But it was not possible to transfer everything to W10. In the end I installed a virtual machine with Win XP 32 bit on the W10 system, and I have to use that to do some tasks. For example, everything related to my Garmin GPS requires the old Windows, because neither Garmin nor anyone else ever released 64 bit drivers for the line of older GPS receivers. And I had to replace many programs by different ones. For example, AutoCAD. Of course modern AutoCAD works on W10,but is way too expensive, and the old version I had will definitely NOT run on W10. So, NanoCAD to the rescue. Same thing with many other programs. And some features, even hardware, simply went to waste. Instead of my excellent old Soundblaster Audigy with the kX-Project driver, now I'm stuck with a crummy integrated audio "solution" that only offers basic functionality and gets digital interference. Instead of five RS-232 ports now I have just one, and so on. I gained access to modern software, but lost access to old and very useful software and hardware. So I can very well understand the reluctancy to "upgrade" to W10. The backward compatibility problems are obvious and severe. For me the trigger to move away from Win XP was that all current web browsers no longer supported XP, and that many modern websites don't run in older browsers. I got locked out of many web services that I really need. And moving to Win 7 as an interim step would only have delayed the inevitable. But for somebody who currently is using Win7, the most sensible thing to do is to stay in Win7 as long as circumstances allow. About virtual machines: It's important to know that one can easily run a 32 bit virtual machine on a 64 bit real machine and OS, and what's far less known, it's also possible to run a 64 bit virtual machine on a 32 bit main operarting system! That's what I was doing to run some modern software, before switching to W10. The limit is given by RAM: 32-bit Windows only handles somewhat more than 3GB, so a virtual machine running in 32 bit Windows can hardly get more than 2GB or so of RAM, and that's very limiting in a 64 bit virtual machine. I have no trouble using the NanoVNA on W10, through NanoVNA App, but I haven't tried yet updating its firmware from the new system. The last update was done using my old Windows XP computer. I will handle that like I have been handling all other transition problems: When I need to do something, I just try if it works, and if it doesn't, I start looking for solutions, drivers, newer software, tricks, etc.. |
Re: Newbie NanoVNA question regarding calibration
Hi Roger,
Mine is marked HW version 4.3 MS on the back. I used NanoVNA-H4-MS_20220831.dfu from Hugen's github page. Thought that was the version that was on it when I got it since the description on Amazon said updated 2022 version. Glad I installed the 'wrong' one, LOL! Really appreciate your help!! Maybe if I had mention I had the MS version it would have been easier to fix the issue. Thanks!!!! |
Re: FS: NanoVNA-H4
#nanovna-h4
Please PM me.
On Wed, Aug 31, 2022 at 12:39 PM Randy <wrmoore47@...> wrote: NanoVNA-H4 for sale. Bought from R&L Electronics 4/2020. Used a couple ofHOGALLEN aka Gary A. Smith 2150 East 575 North St. George Utah 84790 435 272-7077 |
Re: FS: NanoVNA-H4
#nanovna-h4
On Wed, Aug 31, 2022 at 12:39 PM Randy <wrmoore47@...> wrote:
NanoVNA-H4 for sale. Bought from R&L Electronics 4/2020. Used a couple ofHOGALLEN aka Gary A. Smith 2150 East 575 North St. George Utah 84790 435 272-7077 |
FS: NanoVNA-H4
#nanovna-h4
NanoVNA-H4 for sale. Bought from R&L Electronics 4/2020. Used a couple of times back then and not since. Contains all original cables/connectors/cal loads/etc. In original, nice box. Just powered it up and charged the battery and it seems to be working fine. Version v.0.5.0. I haven't followed this device on-line, so don't know what the current version is. No manual or instructions were included, but lots of info on this group and on YouTube. $50 including shipping in US. PayPal preferred. If you need more pix or have questions, just ask.
Tnx es73, Randy, KS4L |
Re: Anything for Windows 7?
F1AMM
You haven't done it but I think your page can interest a lot of people
toggle quoted message
Show quoted text
-- Fran?ois -----Message d'origine-----De la part de HA3HZ 31 ao?t 2022 09:05 |
Re: Newbie NanoVNA question regarding calibration
On Wed, Aug 31, 2022 at 05:40 AM, TE Dukes wrote:
Glad you got it working. A few questions. 1. What Hugen version are you running now? 2. Did you use the NanoVNA-H4-MS or NanoVNA-H4-SI version? The SI version is for the original clock chip which is hard to get now. The MS version is for the Chinese clone clock chip which Hugen is using in recent production. There is a label on the back of Hugen's H4 which has an M for the Chinese version clock chip. Roger Roger |
Re: nanovna-saver for the mac
Georgina Joyce
Hello,
Have you not listened to my podcast on this? The Windows and the Mac binaries are just that. You put them where you like. Of course, on the Mac /Applications is where you typically drop your applications so what is wrong in doing that with NanoVNA Saver? You also need to be patient. As Saver on Windows and on the Mac load a terminal window and the number people on the NanoVNA Users list who are jut too inpatient. Wait and it will load. You can find my podcasts on CQ Blind Hams or on www.spencerweb.net/downloads/ 73 On 31 Aug 2022, at 00:15, Jim Lux <jimlux@...> wrote:Georgina Call: M0EBP DMR ID: 2346259 Allstar: 52178 Locater: IO83PS |
Re: Newbie NanoVNA question regarding calibration
Got it working !!!
I had decided to send this back to Amazon and try another in case I may have gotten a bad one. I flashed the 'original' Hugen FW back but must have used a newer version by mistake. Everything is working and I can do more than 101p. Don't understand why one FW works and another doesn't. On Hugen's github, it mentions synchronizing with DiSlord FW. IDK but it is working!! Thanks!!!!!!! |
Re: Newbie NanoVNA question regarding calibration
Hi.
toggle quoted message
Show quoted text
It looks like you are having the dreaded Clock Generator instability around 300MHz. You can see the spurs around 300 and 600MHz on the yellow traces in your photos. The basic design of the NanoVNA severely overclocks the 5351 Clock Gen chip which is only specced to 200MHz max. Some chips just can't make it to 300MHz, especially the Chinese knockoffs. Go into your configuration and look for something called THRESHOLD. It will be 300MHz at present. Change this to 280MHz. Clear all your existing calibration data and recalibrate. This should fix your problem. I have a Deepelec unit so I can't give you the exact menu steps for your unit. There is a Menu Map available elsewhere on this group, just follow the path to the THRESHOLD item. Good luck....Bob VK2ZRE On 31/08/2022 4:50 am, TE Dukes wrote:
HA!! Didn't know I could do that!! |
Re: DiSlord v1.2.0 instability even though MS5351 clock-generator is selected (MS-3.6 HW version)
Hugen,
toggle quoted message
Show quoted text
Is this a problem with the SI version chips? Thanks, Mike N2MS On 08/31/2022 2:01 AM Hugen <hugen@...> wrote: |
Re: Anything for Windows 7?
Hi Leif,
I'm still using the win7-32 bit version, as are you. I think a lot of people are like that, they just don't talk about it. The article about NanoVNA on my website therefore appeared after my testing on win-xp and win7. I like the detailed descriptions, based on which the operation can be repeated. -- Gyula HA3HZ ( ) |
Re: DiSlord v1.2.0 instability even though MS5351 clock-generator is selected (MS-3.6 HW version)
This is because DiSlord's firmware uses the 3rd harmonic at 600MHz, and the VCO frequency division factor is set to 6, which requires the VCO of the MS5351 to be locked at 1200MHz, but not every MS5351 can lock to 1200MHz well . I properly adjusted the MS5351's division settings and updated the firmware, I hope it works for you.
|
Re: Anything for Windows 7?
F1AMM
why not use w10?? ... most if not all software for w7 should also workFor me, it's very simple I have a Windows Seven Pro version and I have a Windows XP virtual machine on it. When migrating from 7 to 10, can't reinstall this Window XP VM and I need it for some mapping software and an old Agfa scanner that hasn't been updated. So I came back to Seven Pro -- F1Amm (Fran?ois) -----Message d'origine-----De la part de Siegfried Jackstien mardi 30 ao?t 2022 20:47 |
to navigate to use esc to dismiss