开云体育

Hi Rune,
when you raise a nice fat pig from a small pig, there will always be someone who does not like why they are not smart enough. :? :?

It was just a joke, sorry.

73, Gyula

same seller i ordered, fake tracking number which never showed any progress. But before the last day of delivery (Novemebr 19) I was not able to issue a? dispute and claim a refund . I did this on November 20. Seller responded, but I insist on a refund. So lets see what happens.

Henning Weddig

Am 25.11.2019 um 06:27 schrieb biastee via Groups.Io:

and hugen79 a couple of hours ago!
here..

edy_555 release...
0.5.1-20191123 couple of days ago
Here..

Hey dr op 5QR5.

Okay. That explains a lot :).

But: I think a "X" for load last .cal file would be okay. A textbox can show the filename of last .cal file.

What do you think?

Hello DE8MSH,
Thank you for your comments and your suggestions!

Currently, NanoVNA-Saver has no interaction with the calibration on the
NanoVNA itself. The application assumes that you have a calibration on the
NanoVNA covering at least the span of frequencies read - in order to put
the readings in the expected span of values, or at least close to that span.

The calibration you can do in NanoVNA-Saver is a further calibration to
refine the accuracy and to allow more than 101 data points, and it is not
saved on the NanoVNA, but it is possible to save it as files (I use the
extension ".cal").

The NanoVNA firmware does not offer a way to write calibration data to it.
It does allow triggering the short/open/load/isolation/through functions
for calibration on the device, but this is not currently utilized by
NanoVNA-Saver.

I am looking into running the NanoVNA in uncalibrated mode, and purely
handling the calibration in NanoVNA-Saver, in order to save the step of
calibrating the NanoVNA itself for those users who purely use it when
connected to a computer.

NanoVNA-Saver does not currently load the previous calibration. This is a
deliberate design choice, as the calibration is heavily dependent on what
cables, connectors etc. are used with the NanoVNA, and I would rather not
load any calibration than load a wrong calibration and display completely
erroneous data. So currently, NanoVNA-Saver by default shows the same data
as is displayed on the NanoVNA itself.

I hope these comments explain some of the reasons why things currently are
as they are. :-)
--
Rune / 5Q5R

Only non-inductive resistors are needed around the GHz, which must be soldered to the connector and cut off excess feet. The calibration on the images is appropriate for the shortwave. Calibrations made in China are tools that can be used for example ebay sellers are likely to have fallen out of quality control, so sell for that and that.
The measuring point should always be the same as the calibration point.


Gyula, HA3HZ

The nanoVNA-Saver does not automatically load previously saved data, but you can create a lot of calibration data yourself and download it as a calibration data before use.
You can comment on the saved data and read it after loading.
Hardware can do limited things due to its limited memory.
This is expanded by the nanoVNA-Saver.
Successful use.


Gyula, HA3HZ

Many thanks, Oristo, I really appreciate your work.
Thank you all for the valuable information.
This group is a real gem!

73 Ady YO2NAA

Hello, I thougt abiut that too for a while.

IT would be ideal if SaverSw would be extended such that it could recall all four Cal Data in the nanaovna decice.

I am using different fixtures, all calibrated individually and stored in nanovna decice and again also in SaverSw.

Once I change fixture I need to recall the corresponding Calibration Data in SaverSw AND in the naoanvna device.
This is doable, but it would be great if one could combine that all via SaverSw.

Don't know if there is a USB command available in nanaovna device for recalling a individual Cal data-set ?

Hey dr ops.

When I calibrate NanoVNA with NanoVNASaver and save the data, will it be loaded automaticaly if I start NanoVNASaver again?
And: Is there a transfer between NanoVNASaver and NanoVNA save slot 0?
If not: Can we have a "save to NanoVNA slot 0" button?
If not: Why not?

:)

73 de DE8MSH

I also ordered from dowjors3236, but, have been unsuccessful in getting a refund.

When I first complained to eBay customer service, they directed me to PayPal because the item's "buyer's protection" is supposed to be handled by the latter. Unfortunately, PayPal's website didn't have a record of the transaction. When I contacted eBay again, they gave me a transaction id for reporting to PayPal's customer service. However, PayPal claimed the transaction id is invalid. After many rounds of to & fro with PayPal customer service (talking to different persons each time), finally, they finally agreed to manually open a dispute for me. That was 2 weeks ago, but I haven't heard from them since.

Another issue is that eBay's deadline for filing a dispute (45 days from purchase) ends before the delivery window.
Chin-Leong, 9W2LC

i installed the Play store on my fairly newish Kindle Fire8
which then let my install the NanoVNA .apk right from the Play store
works a treat
did some repeater work the other day with the setup
really nice to be able to save the graphs as well as the touchstone files
and upload them to google drive

For those that want to experiment

Application note started: /g/nanovna-users/wiki/port-extension-and-de-embedding

Greetings. I use 'screen protectors' on both my 2.8" VNA and my new 'F' model. NO issues.
I started using these a long time ago on my 'smartphone' and have used them on my Icom 7300, 7610, 9700 and Kenwood TS-890 radios, NEVER any issues.
I usually buy the 'tablet' size and cut them to fit. After a couple of tries, it becomes very easy. YES, there is a 'learning curve'.....

ron
N4UE

The BNC calibration standards are not nearly as good as the SMA ones.
There is more stray capacitance and series inductance in BNC because of the
bigger size. I made BNC calibration standards and they work ok, but the
error is definitely much greater above 400 to 500 MHz.

On Sun, Nov 24, 2019 at 1:55 PM Bob Albert via Groups.Io <bob91343=
[email protected]> wrote:

Why not use ordinary BNC hardware with an adapter? Maybe not good all
the way to 900 MHz but fine for casual use.
Bob
On Sunday, November 24, 2019, 10:35:34 AM PST, Daniel Marks <
profdc9@...> wrote:

I was not very satisfied with the quality of the calibration standards I
ordered off of ebay, so I made my own out of PCB edge mount male SMA
connectors as shown here:




The picture is attached. It is simple. One of them is unmodified for the
open, you solder a wire between the center conductor and two PCB edge
mounts for the short, and use two 0805 or 1206 100 ohm resistors, soldering
the resistors from the center pin to the edge mounts.

A pack of 5 of the connectors cost me under $2 on ebaay.

Why not use ordinary BNC hardware with an adapter?? Maybe not good all the way to 900 MHz but fine for casual use.
Bob

I was not very satisfied with the quality of the calibration standards I ordered off of ebay, so I made my own out of PCB edge mount male SMA connectors as shown here:



The picture is attached. It is simple. One of them is unmodified for the open, you solder a wire between the center conductor and two PCB edge mounts for the short, and use two 0805 or 1206 100 ohm resistors, soldering the resistors from the center pin to the edge mounts.

A pack of 5 of the connectors cost me under $2 on ebaay.

I am using Hugen's latest AA FW but have also checked with QRP's latest. I am
under the impression that the format LINEAR is equal to rho, the absolute
value (modulus) of gamma (S11),
and that the formats REAL and IMAG are the real- and imaginary parts of gamma.
What bothers me is that in both Hugen's FW and QRP's FW the sign of format
LINEAR is negative, whereas I expect that an absolute value is positive per
definition. Have I got it wrong? Please help me.

CH0 LINEAR is displayed on device as positive small values with QRP 0.4.3 firmware.
Need to set e.g. REFERENCE POSITION 1 and SCALE/DIV .001x1

I am using Hugen's latest AA FW but have also checked with QRP's latest. I am under the impression that the format LINEAR is equal to rho, the absolute value (modulus) of gamma (S11),
and that the formats REAL and IMAG are the real- and imaginary parts of gamma. What bothers me is that in both Hugen's FW and QRP's FW the sign of format LINEAR is negative, whereas I expect that an absolute value is positive per definition. Have I got it wrong? Please help me.
Regards/Torbjorn