开云体育

Earlier today I released NanoVNA-Saver 0.2.0:


Release notes:
New feature: Zooming
This release adds the ability to "zoom" on the frequency-based charts: Use
your mouse's scroll wheel to zoom in and out - or hold the control button
and drag a box on the chart to zoom into.

New chart type: Group Delay
Group delay can now be displayed as a chart, and can also be enabled for
the marker data display for both S11 and S21.

New chart type: Permeability
A new chart, R/ω & X/ω, is available for determining permeability
characteristics of toroids. Thanks to David, F4HTQ, for requesting and
helping out with this.

Logarithmic Y-scale:
The VSWR and Permeability charts now have the option of having the Y-scale
shown as Linear or Logarithmic.

Changes to markers:

Now able to display Group Delay for S11 and S21
Markers can be filled or "hollow"
Markers can be shown centered, or with the point at the tip
Markers can be locked from mouse control by selecting the radio button next
to "Show/Hide data"
Time-delay reflectometry:

Min/max impedance values can be manually set
There's a movable marker to measure distance in the TDR chart
New scaling function for values:
Holger Müller, DG5DBH, contributed new code to show values more correctly,
using SI-prefixes. David Hunt provided further changes to avoid losing
precision when displaying frequencies for sweep settings.

Also included: Several bug fixes!

As ever, I look forward to hearing about any feedback, suggestions and bugs!
Thank you very much to all the kind testers, many of whom were recruited on
these very mailing lists!
--
Rune / 5Q5R

Perhaps a way to drag/move that zoomed in display would be great, it seems to at times just move out of view when zoomed in.

Hi,
a drag function is definitely on the list for a future version! Thanks for
the feedback!

--
Rune / 5Q5R

On Tue, Nov 12, 2019 at 05:35 AM, Rune Broberg wrote:

As ever, I look forward to hearing about any feedback, suggestions and bugs!
Thank you very much to all the kind testers, many of whom were recruited on
these very mailing lists!

Rune,
since I now know that you are an actual coder / developer , I like to ask / give a feedback if as "not recently experienced person" is allowed.
1. What is your development tool ? ( In few words , do not want to take too much of your time ).
2. I understand that NanoVNA is "an embedded processor " hardware. As of today I do not own one, I started with "cloning" software - my choice. I am making progress going that direction.

Along that line - real technical question - how can I add standard ANSI C "includes " ? Perhaps C++ I/O ( cout ) includes so I can trace the code flow using I/O to standard console? For debugging purposes - not to be included in final code to flash to NanoVNA memory.

3. Related to above point #2 – example code . How can I print this code output to standard I/O file / console ? (Besides makefile I do not see other ways to option the compilation / linking - no such options in Eclipse Egit )

// test access
int a = 3;

#ifdef DEBUG

chsnprintf("Test print ",10,"%d2", a );

#endif


4. Here is a minor feedback – just warning by make


z@z-desktop:~/git/NanoVNA-H-GIT$ make
Compiling main.c
main.c: In function 'hard_fault_handler_c':
main.c:2189:1: warning: stack usage computation not supported for this target
}
^
Linking build/ch.elf
Creating build/ch.hex
Creating build/ch.bin
Creating build/ch.dmp

text data bss dec hex filename
92904 5028 11544 109476 1aba4 build/ch.elf
Creating build/ch.list

Done

Hi Vaclav,
for NanoVNA-Saver I use PyCharm - which is Python specific, and not usable
for the firmware development side of things. On Windows, I might choose
something like Visual Studio Code with a fitting set of plugins for
developing for the NanoVNA. On Linux I use vim and make and things like
that ;-)

I don't think there's any way to print anything to a standard console - the
only way to run the code is on the device itself, and that does not have a
standard console. You *might* be able to make something that prints to the
serial port, and then listen in to that; or using a hardware debugger for
the microcontroller.

I hope you find a good development environment for your project!
--
Rune / 5Q5R

On Tue, 12 Nov 2019 at 15:42, vaclav_sal via Groups.Io <vaclav_sal=
[email protected]> wrote:

On Tue, Nov 12, 2019 at 05:35 AM, Rune Broberg wrote:

As ever, I look forward to hearing about any feedback, suggestions and

bugs!

Thank you very much to all the kind testers, many of whom were recruited

on

these very mailing lists!

Rune,
since I now know that you are an actual coder / developer , I like to ask
/ give a feedback if as "not recently experienced person" is allowed.
1. What is your development tool ? ( In few words , do not want to take
too much of your time ).
2. I understand that NanoVNA is "an embedded processor " hardware. As of
today I do not own one, I started with "cloning" software - my choice. I am
making progress going that direction.

Along that line - real technical question - how can I add standard ANSI C
"includes " ? Perhaps C++ I/O ( cout ) includes so I can trace the code
flow using I/O to standard console? For debugging purposes - not to be
included in final code to flash to NanoVNA memory.

3. Related to above point #2 – example code . How can I print this code
output to standard I/O file / console ? (Besides makefile I do not see
other ways to option the compilation / linking - no such options in
Eclipse Egit )

// test access
int a = 3;

#ifdef DEBUG

chsnprintf("Test print ",10,"%d2", a );

#endif


4. Here is a minor feedback – just warning by make


z@z-desktop:~/git/NanoVNA-H-GIT$ make
Compiling main.c
main.c: In function 'hard_fault_handler_c':
main.c:2189:1: warning: stack usage computation not supported for this
target
}
^
Linking build/ch.elf
Creating build/ch.hex
Creating build/ch.bin
Creating build/ch.dmp

text data bss dec hex filename
92904 5028 11544 109476 1aba4 build/ch.elf
Creating build/ch.list

Done

This is a little off topic however I reply to the question on firmware
development enviroment. I am using the free STM32CUBEIDE from ST Micro the
Mc manufacture to build some SDR control code for a home project and it
seems to work well.

On Tue, Nov 12, 2019, 7:42 AM vaclav_sal via Groups.Io <vaclav_sal=
[email protected]> wrote:

On Tue, Nov 12, 2019 at 05:35 AM, Rune Broberg wrote:

As ever, I look forward to hearing about any feedback, suggestions and

bugs!

Thank you very much to all the kind testers, many of whom were recruited

on

these very mailing lists!

Rune,
since I now know that you are an actual coder / developer , I like to ask
/ give a feedback if as "not recently experienced person" is allowed.
1. What is your development tool ? ( In few words , do not want to take
too much of your time ).
2. I understand that NanoVNA is "an embedded processor " hardware. As of
today I do not own one, I started with "cloning" software - my choice. I am
making progress going that direction.

Along that line - real technical question - how can I add standard ANSI C
"includes " ? Perhaps C++ I/O ( cout ) includes so I can trace the code
flow using I/O to standard console? For debugging purposes - not to be
included in final code to flash to NanoVNA memory.

3. Related to above point #2 – example code . How can I print this code
output to standard I/O file / console ? (Besides makefile I do not see
other ways to option the compilation / linking - no such options in
Eclipse Egit )

// test access
int a = 3;

#ifdef DEBUG

chsnprintf("Test print ",10,"%d2", a );

#endif


4. Here is a minor feedback – just warning by make


z@z-desktop:~/git/NanoVNA-H-GIT$ make
Compiling main.c
main.c: In function 'hard_fault_handler_c':
main.c:2189:1: warning: stack usage computation not supported for this
target
}
^
Linking build/ch.elf
Creating build/ch.hex
Creating build/ch.bin
Creating build/ch.dmp

text data bss dec hex filename
92904 5028 11544 109476 1aba4 build/ch.elf
Creating build/ch.list

Done

I am using the free STM32CUBEIDE from ST Micro the Mc manufacture
to build some SDR control code for a home project and it seems to work well.

I guess STM32CubeMX integration and STM support
are main claims to fame for STM32CUBEIDE,
which otherwise is another customization of ECLIPSE?/CDT IDE.

NanoVNA uses ChibiOS, which has a dedicated ECLIPSE?-based IDE,
namely ChibiStudio, and a utility for converting CubeMX output for ChibiOS


... which is already done for nanoVNA source, then STM32CUBEIDE seems
for ChibiOS firmware a step backwards from ChibiStudio

Hi Rune,

Many thanks again for your ongoing development of nanoVNA-Saver - fabulous work!

I am not sure if I should waste your time reporting this as it is not a significant issue....just apple polishing.

I noticed when I first start version 0.2.0 that the Center, Stop and Span frequency info within "Sweep Control" section overflows the window widths. At startup it displays 9 digits as shown below. Once I enter new sweep control frequencies it displays normally. However Center still overflows just a little. I have my sweep Stop set at 850M and the Center is showing 425.025MHz which just exceeds the window width by about a half digit. With initialization the data is about twice as wide as the window width with the most significant digits hidden from view then it reverts to normal upon receiving a new manual frequency entry.

Initialization displayed data:

SPAN 849.949952MHz
STOP 849.999952MHz
CENTER 425.024976MHz

Hope this feedback is useful.

--
Best Regards,
Tom
VA7TA

@Tom VA7TA
Did you change "Display setup / Font / Font size" with too large font?
73, Lucio

Now that the capability is there in the software, how would one use the NanoVNA to check a toroid's permeability? New territory for me... :-)

On Tue, Nov 12, 2019 at 06:48 AM, Rune Broberg wrote:

I don't think there's any way to print anything to a standard console -

I was afraid of that.
That makes (C) code debugging little more complex than expected.
I'll work on that.
Thanks

On Tue, Nov 12, 2019 at 09:33 AM, Oristo wrote:

I am using the free STM32CUBEIDE from ST Micro the Mc manufacture
to build some SDR control code for a home project and it seems to work well.

Silly questions.
Can it be added to Eclipse IDE as "plug-in" ??

But it woudl make more sense , KISS, to use it as standalone IDE, right?

It woudl be easier to have both "running" and just switch between them as necessary.

I am just looking for real debugger IDE and STM32CUBEIDE seems to be the ticket.

STM32CubeIDE is based on eclipse and allows debugging with with the stm
serial jag device which can be gotten cheaply as Chinese clones from ebay.
There are several YouTube tutorials on the software. I just started using
it yesterday and have built the normal led blink program and single stepped
through it on a ST demo board based on the stm32f051c8t6 device. Good luck
with your project and let the group how you proceed.

On Tue, Nov 12, 2019, 11:22 PM vaclav_sal via Groups.Io <vaclav_sal=
[email protected]> wrote:

On Tue, Nov 12, 2019 at 09:33 AM, Oristo wrote:

I am using the free STM32CUBEIDE from ST Micro the Mc manufacture
to build some SDR control code for a home project and it seems to work

well.

Silly questions.
Can it be added to Eclipse IDE as "plug-in" ??

But it woudl make more sense , KISS, to use it as standalone IDE, right?

It woudl be easier to have both "running" and just switch between them as
necessary.

I am just looking for real debugger IDE and STM32CUBEIDE seems to be the
ticket.

Hi Tom,
scaling of the input fields and avoiding "overflow" is on the todo list.
:-) User interface design isn't my strong point, and I probably have a
strong habit of testing the software with my preferred settings - 8pt font,
for example - and never really looking at what other users might set it up
as. Having it run on at least 3 different operating systems doesn't help
that ;-)

But, I am going to look into it, both scaling the interface as the font
size changes, and organising the layout to make the most of a limited
screen size.

I hope you continue to enjoy using the software!
--
Rune / 5Q5R

Hi John,
my experiments in this field have been very limited - the feature was added
with the encouragement of David F4HTQ. He submitted to me an S2P file of a
measurement of a toroid, and a curve shape:




He believed this could be approximated as R/ω and X/ω, so I implemented it,
and managed to create the following graph:

[image: image.png]

Which seemed to fit quite well, even though the units aren't exactly the
same.

So, for now, all I know how to do is: Given a permeability chart from a
manufacturer, replicate the same curve shape vs frequency using the NanoVNA.

I hope it's useful ;-)

--
Rune / 5Q5R

Hi Rune,
thanks for the great software update!
Would it be possible to show in the log scaled frequency mode the vertical grid lines logarithmically like 0.1 MHz, 0.2 MHz,...0.9 MHz, 1 MHz,...10 MHz,...100 MHz,...900 MHz? I think, that would give one a much better overview of the frequency axis.

Best regards
Norbert, DG1KPN

Hello Norbert,
I've put it on the list for a future release. I don't immediately know how
to do it nicely, but I think it's an important feature, so I'll certainly
try to work on it. :-)

--
Rune / 5Q5R

Rune,
While verifying a cable that I just constructed, I noticed that you had implemented a second marker in the TDR graph. Thanks a lot! Its nice to be able to mark other anomalies, in addition to the peak, and get a readout of where they occur. The attachment shows the TDR graph with a second marker showing the minor discontinuity caused by the BNC "bullet" at 0.3 meters.

The phase delay graph is telling me something, just not sure how to interpret it ; )


- Herb

@Rune Broberg

forgive me Rune, maybe it has already been said a million times but I still have doubts.
Let's say I have the nanoVNA turned on "Recall 4".
I connect NanoVNA-Saver to the device and the program synchronizes to the same frequency range as the device.
What else does NanoVNA-Saver read from the NanoVNA? calibration values? other?
thanks and congratulations for the excellent program.
73, Lucio I0LYL

Hi Rune,

Thanks a lot for this fantastic software. The newly added TDR markers are very useful when dealing with roof antennas. :-)

Great job.
Thanks again

Jean