Re: Newbie NanoVNA question regarding calibration
You recalibrate device after?
|
Re: Newbie NanoVNA question regarding calibration
Linux was released in 1991, RH came a few years later.
toggle quoted message
Show quoted text
On Tue, 30 Aug 2022 at 03:44, TE Dukes <tdukes@...> wrote: Thanks for the info. Never been one to go with the latest and the
greatest. Been running RedHat Linux since about 1991. I always go with
'stable'.
|
Re: Newbie NanoVNA question regarding calibration
Thanks for the info. Never been one to go with the latest and the greatest. Been running RedHat Linux since about 1991. I always go with 'stable'.
toggle quoted message
Show quoted text
-----Original Message----- From: [email protected] < [email protected]> On Behalf Of Siegfried Jackstien Sent: Monday, August 29, 2022 9:31 PM To: [email protected]Subject: Re: [nanovna-users] Newbie NanoVNA question regarding calibration hmm ... as far as i know the version from dislord is more actual (12 days old) and displord also is making new fw fro nanovna v2 (and some other clones,brothers,sisters, cousins) version from oen duffy is 209-od12 ... version from dislord is 210 (mod by dislord) i think that you will have less compatibility problems if you use fw and pc soft from same guy (and if not you have only one person to ask for a change or to write issues in github) greetz sigi dg9bfc ps .. if you want newest fw join the beta test group /g/nanovna-beta-testAm 30.08.2022 um 00:51 schrieb Roger Need via groups.io: On Mon, Aug 29, 2022 at 02:47 PM, Siegfried Jackstien wrote:
1.0.69 for your H4 is outdated
as is nano vna app (displord version 210 is most actual)
you find it here
A-App.exe
I prefer the latest NanoVNA app fork by Owen Duffy. He incorporates some of DiSlord's changes and fixed the "info" parameters so they now work correctly when you hover over the data.
Roger
|
Re: Newbie NanoVNA question regarding calibration
What I'm wanting to do is to check a dupexler I have coming in the next week or so to make sure its tuned close the frequencies I requested.
I know this is not the ideal way to do it but I don't have $12K for a Tektronic VNA.
Attached are the pics.
Thanks, really appreciate the help!!
toggle quoted message
Show quoted text
-----Original Message----- From: [email protected] < [email protected]> On Behalf Of Roger Need via groups.io Sent: Monday, August 29, 2022 8:47 PM To: [email protected]Subject: Re: [nanovna-users] Newbie NanoVNA question regarding calibration On Mon, Aug 29, 2022 at 04:12 PM, TE Dukes wrote: Yes, I did both calibrations.
I just now updated the fw and the app. Its still doing the same. Do
you think my nanovna may be bad? What are you measuring? Try the 50 ohm load and post a screenshot Then connect the two ports with a cable and post a screenshot. Roger
|
Re: Newbie NanoVNA question regarding calibration
hmm ... as far as i know the version from dislord is more actual (12 days old) and displord also is making new fw fro nanovna v2 (and some other clones,brothers,sisters, cousins) version from oen duffy is 209-od12 ... version from dislord is 210 (mod by dislord) i think that you will have less compatibility problems if you use fw and pc soft from same guy (and if not you have only one person to ask for a change or to write issues in github) greetz sigi dg9bfc ps .. if you want newest fw join the beta test group /g/nanovna-beta-testAm 30.08.2022 um 00:51 schrieb Roger Need via groups.io:
On Mon, Aug 29, 2022 at 02:47 PM, Siegfried Jackstien wrote:
1.0.69 for your H4 is outdated
as is nano vna app (displord version 210 is most actual)
you find it here
I prefer the latest NanoVNA app fork by Owen Duffy. He incorporates some of DiSlord's changes and fixed the "info" parameters so they now work correctly when you hover over the data.
Roger
|
Re: Newbie NanoVNA question regarding calibration
On Mon, Aug 29, 2022 at 04:12 PM, TE Dukes wrote: Yes, I did both calibrations.
I just now updated the fw and the app. Its still doing the same. Do you think
my nanovna may be bad? What are you measuring? Try the 50 ohm load and post a screenshot Then connect the two ports with a cable and post a screenshot. Roger
|
Re: Newbie NanoVNA question regarding calibration
Hello,
Yes, I did both calibrations.
I just now updated the fw and the app. Its still doing the same. Do you think my nanovna may be bad?
I have expanded the frequency range to 460Mhz to 470Mhz and the S11 graph is a flat line between my markers where I want to test. With it being off on the 460Mhz end, will that cause a bad reading?
A new screen shot is attached.
Thanks!!
toggle quoted message
Show quoted text
-----Original Message----- From: [email protected] < [email protected]> On Behalf Of Roger Need via groups.io Sent: Monday, August 29, 2022 6:48 PM To: [email protected]Subject: Re: [nanovna-users] Newbie NanoVNA question regarding calibration Your screenshot shows that you are using calibration in the App and not on the NanoVNA itself. Did you calibrate in the NanoVNA app? If not then you have to calibrate in the app or change the selection to VNA. Roger
|
Re: Newbie NanoVNA question regarding calibration
On Mon, Aug 29, 2022 at 02:47 PM, Siegfried Jackstien wrote:
1.0.69 for your H4 is outdated
as is nano vna app (displord version 210 is most actual)
you find it here
I prefer the latest NanoVNA app fork by Owen Duffy. He incorporates some of DiSlord's changes and fixed the "info" parameters so they now work correctly when you hover over the data. Roger
|
Re: Newbie NanoVNA question regarding calibration
Awesome!! I did not know they were outdated. I did see the NanoVNA App, but only saw the 1.0.69 version in the files section. Are the fw files in a new location?
Thank you!!
toggle quoted message
Show quoted text
-----Original Message----- From: [email protected] < [email protected]> On Behalf Of Siegfried Jackstien Sent: Monday, August 29, 2022 5:47 PM To: [email protected]Subject: Re: [nanovna-users] Newbie NanoVNA question regarding calibration 1.0.69 for your H4 is outdated as is nano vna app (displord version 210 is most actual) you find it here and new fw?? i add to this mail :-) hth dg9bfc sigi Am 29.08.2022 um 22:18 schrieb tdukes@...: Hello,
Just got my NanoVNA H4, have upgraded the firmware to DiSlord's v1.0.69 and using the NanoVNA App v1.1.208 by OneOfEleven. Reason for doing so was to be able to get more than 101p.
After going thru the calibration, my S11 line starts out up and down (technical term), then goes to a flat line. Is that normal? Shouldn't it be flat all the way across? Attached is a screen shot to help what I'm trying to say, make better sense.
Thanks!!
|
Re: Newbie NanoVNA question regarding calibration
Your screenshot shows that you are using calibration in the App and not on the NanoVNA itself.
Did you calibrate in the NanoVNA app? If not then you have to calibrate in the app or change the selection to VNA.
Roger
|
Re: Newbie NanoVNA question regarding calibration
1.0.69 for your H4 is outdated
as is nano vna app (displord version 210 is most actual)
you find it here
and new fw?? i add to this mail :-)
hth
dg9bfc sigi
Am 29.08.2022 um 22:18 schrieb tdukes@...:
toggle quoted message
Show quoted text
Hello,
Just got my NanoVNA H4, have upgraded the firmware to DiSlord's v1.0.69 and using the NanoVNA App v1.1.208 by OneOfEleven. Reason for doing so was to be able to get more than 101p.
After going thru the calibration, my S11 line starts out up and down (technical term), then goes to a flat line. Is that normal? Shouldn't it be flat all the way across? Attached is a screen shot to help what I'm trying to say, make better sense.
Thanks!!
|
Newbie NanoVNA question regarding calibration
Hello,
Just got my NanoVNA H4, have upgraded the firmware to DiSlord's v1.0.69 and using the NanoVNA App v1.1.208 by OneOfEleven. Reason for doing so was to be able to get more than 101p.
After going thru the calibration, my S11 line starts out up and down (technical term), then goes to a flat line. Is that normal? Shouldn't it be flat all the way across? Attached is a screen shot to help what I'm trying to say, make better sense.
Thanks!!
|
A comparable tool to S11.exe is now in my NanoVNA toolbox:
The tools are easy to modify because most of them are written in python.
|
Re: Unable to connect to serial port on Linux installation.
The problem with that is that on a lot of Linux distros, devices are created by udev at boot, so this will typically revert on restart of the system. The proper solution is to add the user to the group for the tty devices (not sure on this dist - "dialout" on some . . . it can be found via ls -lia /dev/tty<whatever>), and then the fix will be persistent.
toggle quoted message
Show quoted text
On August 29, 2022 3:55:25 AM CDT, p.pacaud@... wrote: For me : Ubuntu 22.04 nanovna saver 0.2.2
1)plug nanovna
2)in a term
sudo chmod o+rw /dev/ttyACM0
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
|
Re: I think I have killed another NanoVNA :(
Hi Tim,
I tried connecting to the NanoVNA using a USB cable, and it seems to work OK. I can do a scan and get the Smith chart to populate. Both NanoVNA-QT / NanoVNA seems to work fine. I am pretty confident that the issue lies with the ribbon cable, or the connectors of the ribbon to the board / LCD, as the LCD lights up, just doesn't display anything on it.
Had a play with it this morning. I took the case off and reseated all of the panel ribbon cables. I tried putting it into dfu (hold down toggle switch while powering on) and rebooted and still the same. I think I have got it into DFU mode, as a drive appeared on my Linux laptop, but "dfu-util -l" shows nothing. I copied the updated firmware over to the disk and rebooted, I now get a different boot sound when starting.
I have just ordered a v2, but would still like to get this working.
|
Re: Unable to connect to serial port on Linux installation.
For me : Ubuntu 22.04 nanovna saver 0.2.2
1)plug nanovna
2)in a term
sudo chmod o+rw /dev/ttyACM0
|
In PJ the variations according to the frequency of the values of the six columns of data. 4 faults are clearly identified visually. We note that the fault is generally concomitant on two columns. In fact it is of the OpenR and OpenI type; it is the open measure that is wrong. The problem is that we are behind the filtering of nanovan-saver which tried to solve the problem but that only mitigated it and, suddenly, it is more difficult to detect than if we had access to the raw measurements.
This is the algorithm in naonovna-saver
--
F1AMM (Fran?ois)
|
Whether you do the calibration on a single port or on both, there are errors in the .cal file. To put it simply, we will say that these are parasites that generate false measurements. The real cause is unknown to me and it doesn't really matter. Either way, there will be mistakes.
The .cal file can be corrected by hand. I enter this file into Excel and, by arithmetic operations, I can locate errors. In the same column, a value is not independent of the preceding and the following; it is therefore quite easy to detect and locate abnormal values. It is then possible to replace the erratic value by an interpolation of the value before and the value after. So far I have never encountered two consecutive false errors in the same column. It can be assumed that, in this case, the algorithm proposes to carry out a new calibration. By hand, we are not sure to have identified all the faults. It's tedious and unreliable.
It would be necessary to develop an algorithm performing this detection and replacement. With Excel, I make line-to-line comparisons, for example by comparing the difference in value between two lines with a threshold. When a value (in a column) is false on line N, it causes a doubt on lines N-1 and N+1.
The notion of fixed threshold is never satisfactory in a good algorithm; this threshold, if there is a threshold, must be adjusted dynamically. The values ??follow pseudo sinusoidal curves since it is the frequency which varies from line to line; this property must be exploited.
The problem of processing the first and last lines of the file arises.
We perceive that there is, either in the box, or in nanovna-saver, a filtering based, at least in part on an average. Measurement faults are not marred by noise; they are very false (erratic). It follows that taking into account an average value, somewhere, to eliminate measures does not work well.
One of the difficulties is that it is a question of correcting the .cal file which is the result of a processing parameterized by
Number of measurements to average
Number to discard
I don't even see which parameters would be the most effective to facilitate post processing.
73
--
F1AMM (Fran?ois)
toggle quoted message
Show quoted text
-----Message d'origine----- De la part de alan victor dimanche 28 ao?t 2022 16:27
|
Re: I think I have killed another NanoVNA :(
You might see if you can see it via USB, and if you can get it into DFU mode and reload it. Bad software can cause that as well.
toggle quoted message
Show quoted text
On August 28, 2022 1:34:50 PM CDT, Gordie 2M0IRR <2m0irr@...> wrote: It appears I may have killed my 2nd NanoVNA. Last time, I let the battery voltage drop too low, and in my effort to repair, I managed to snap some of the connectors off.
This time, I had a display show until I plugged the charger in, now the panel lights but no text.
I have left it on charge, and the wee red light is blinking. Pull the plug out, no sign of a blue light. I hear the startup sound and can see the panel light, but nothing on the display.
I will leave it to charge overnight, just in case it is a voltage issue.
Any ideas?
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
|
I think I have killed another NanoVNA :(
It appears I may have killed my 2nd NanoVNA. Last time, I let the battery voltage drop too low, and in my effort to repair, I managed to snap some of the connectors off.
This time, I had a display show until I plugged the charger in, now the panel lights but no text.
I have left it on charge, and the wee red light is blinking. Pull the plug out, no sign of a blue light. I hear the startup sound and can see the panel light, but nothing on the display.
I will leave it to charge overnight, just in case it is a voltage issue.
Any ideas?
|
Roger Need
Ho-Ro
