Re: NanoVNA-H version 0.4.0-3 compiled on November 25, 2019
Can someone that has installed 0.4.0-3 do a S11 measurement of a 25 ohm
resistor from 1 to 900MHz? Using
Setting 2dB/div
|
Re: NanoVNA-H version 0.4.0-3 compiled on November 25, 2019
Can someone that has installed 0.4.0-3 do a S11 measurement of a 25 ohm
resistor from 1 to 900MHz? Using
|
Re: NanoVNA-H version 0.4.0-3 compiled on November 25, 2019
On Mon, Nov 25, 2019 at 04:41 AM, Larry Rothman wrote:
Si5351 default 8mA output;
During the "Chasing ghosts" series it was discovered that 8mA creates non-linearities. Can someone that has installed 0.4.0-3 do a S11 measurement of a 25 ohm resistor from 1 to 900MHz? -- NanoVNA Wiki: /g/nanovna-users/wiki/homeNanoVNA Files: /g/nanovna-users/filesErik, PD0EK
|
Re: NanoVNA-H version 0.4.0-3 compiled on November 25, 2019
QRP and Oristo wrote:
"it has larger font, so it cannot show full frequency and measured value result and cut-off part of the value"
"4 calibration SAVE areas instead of 5. On the other hand, Hugen maintains code inline that is neither in edy555 nor QRP firmware, so presumably more responsive.
Other space was cleared in previous release (4.0) by
eliminating shell commands: DUMP, SCANRAW, COLOR"
===========================================================
QRP / Oristo, thanks for the responses.
I assume the frequency and measured values are only truncated on the screen and are still transferred at full value when connected to a computer. That trade-off will work for people who desire the larger font size and for most of their work only need a couple of digits of precision on the display.
The 4 save locations versus 5 also seems to be an acceptable trade-off for larger font size.
DUMP and SCANRAW commands, I believe, were primarily used during the developmental and debugging of the original NanoVNA and are depreciated and no longer useful. The COLOR command might be missed by those users that have problems with the default screen colors.
It looks like future firmware developments are going to require more give and take to address the dwindling flash memory space available.
- Herb
|
Re: NanoVNA-H version 0.4.0-3 compiled on November 25, 2019
Hi Herb - If the AA version now has 4 traces then,
other than a larger font size,
what differs it from the "ch" version? 4 calibration SAVE areas instead of 5. On the other hand, Hugen maintains code inline that is neither in edy555 nor QRP firmware, so presumably more responsive. Other space was cleared in previous release (4.0) by eliminating shell commands: DUMP, SCANRAW, COLOR .. but I guess those may be also eliminated in Hugen's non-AA version
|
Re: NanoVNA-H version 0.4.0-3 compiled on November 25, 2019
On Mon, Nov 25, 2019 at 03:29 PM, hwalker wrote:
If the AA version now has 4 traces then, other than a larger font size, what
differs it from the "ch" version?
it has larger font, so it cannot show full frequency and measured value result and cut-off part of the value
|
Re: NanoVNA-H version 0.4.0-3 compiled on November 25, 2019
On Mon, Nov 25, 2019 at 04:41 AM, Larry Rothman wrote:
" ¡. Note large font on 4 traces now."
=================================================
If the AA version now has 4 traces then, other than a larger font size, what differs it from the "ch" version?
- Herb
|
Re: NanoVNA software developers wanted
#hacking
Why not just but a RaspberryPi Zero-W for $10US from Adafruit
and use it as a USB Host to WiFi bridge?
1) power and integration, given the goal of a BLE VNA sensor 2) toggling Pi Wi-Fi off/on between VNA scans could be problematic; as would leaving it on. 3) "(BLE support is still in the works, software-wise)"
|
Re: NanoVNA software developers wanted
#hacking
Everyone keeps talking about (relatively) expensive solutions to get? a wireless connection from the NanoVNA.
Why not just but a RaspberryPi Zero-W for $10US from Adafruit and use it as a USB Host to WiFi bridge?
In fact, with some programming, you could remotely command it to scan and store data locally on its SD card.
So - let's get programming.....
...Larry
On Monday, November 25, 2019, 7:27:08 a.m. GMT-5, Oristo <ormpoa@...> wrote:
> ...PCB version of NanoVNA-H to V3.4...easy to DIY Bluetooth connection
The recently announced (for ~ US$20) Arduino NANO 33 BLE claims USB host support:
Based on Nordic nRF52480 (which cannot natively implement USB host),
this may be a minimal hardware prototype for Bluetooth LE via USB with existing nanoVNAs,
except that dedicating the Arduino NANO 33 BLE USB port to host may be too disruptive,
so perhaps prototyping by a USB host shield may still be more expedient:
Cheap USB Host Shields are typically DuinoFun clones, e.g.
|
Re: NanoVNASaver -- save points?
Hi Rune,
Again, I would like it very much when "uncalibrated" or? the description of the active calibration-file is shown in the MAIN window, to avoid confusion while working.
Jos
Op 25-11-2019 om 09:26 schreef Rune Broberg:
toggle quoted message
Show quoted text
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. :-)
|
Re: NanoVNA-H version 0.4.0-3 compiled on November 25, 2019
Hugen's updates from today's NanoVNA-H firmware release:
1.The absolute value of the linear format is displayed;??
2.Si5351 default 8mA output;??
3.The AA version shows 4 traces.??
Note large font on 4 traces now.
toggle quoted message
Show quoted text
On Monday, November 25, 2019, 4:52:48 a.m. GMT-5, Dean Smith <bardezbiker@...> wrote:
and hugen79 a couple of hours ago!
here..
|
Re: NanoVNA software developers wanted
#hacking
...PCB version of NanoVNA-H to V3.4...easy to DIY Bluetooth connection The recently announced (for ~ US$20) Arduino NANO 33 BLE claims USB host support: Based on Nordic nRF52480 (which cannot natively implement USB host), this may be a minimal hardware prototype for Bluetooth LE via USB with existing nanoVNAs, except that dedicating the Arduino NANO 33 BLE USB port to host may be too disruptive, so perhaps prototyping by a USB host shield may still be more expedient: Cheap USB Host Shields are typically DuinoFun clones, e.g.
|
Re: Simple way to produce calibration standards
#calibration
Your standards could be significantly improved as follows:
Short: Don't use wires, too much added inductance. instead use braid or a thin piece of sheet copper (with hole) pushed down flush against connector body and soldered all around.
Open: Long center pin makes for added uncertainty of reference plane location. Instead, cut off the center pin flush with the connector body.
Load: Resistors floating off the connector body adds inductance. Instead, trim center pin to short stub (~1 mm), and solder down the resistors laying right against the connector body, preferably turned over with the coated side facing the connector body.
Dana (K8YUM)
|
Re: NanoVNASaver -- save points?
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:
toggle quoted message
Show quoted text
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
|
NanoVNA-H version 0.4.0-3 compiled on November 25, 2019
and hugen79 a couple of hours ago!
here..
|
edy_555 release...
0.5.1-20191123 couple of days ago
Here..
|
Re: NanoVNASaver -- save points?
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?
|
Re: NanoVNASaver -- save points?
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
toggle quoted message
Show quoted text
On Mon, 25 Nov 2019 at 06:39, <de8msh@...> wrote: 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
|
Re: Simple way to produce calibration standards
#calibration
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
|
Oristo
Gyula Molnar