开云体育

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 Barry,
I don't know that you would need to do the whole copy around thing. I
haven't tried it, but I think it would work fine selecting a calibration
slot, slot 1 for example, and then using NanoVNA-Saver with the device with
that calibration active in the calibrated range.

*However*: My personal preference is to have Cal 0 be full span, and then
making a calibration within NanoVNA-Saver, using the calibration assistant,
with the "Segments" count set to perhaps 10 or even 20 - which gives you
1010 or 2020 data points for the calibration. This calibration can be full
span, or for the range you are interested in. You can then save this, or
any other calibration you make, as files which you can name more
intuitively than "cal 0", "cal 1" etc. ;-)

It's worth noting, that any calibration in NanoVNA-Saver is in reference to
the particular calibration done on the NanoVNA: So if you re-calibrate your
NanoVNA, your NanoVNA-Saver calibration ceases to be valid, and may give
incorrect readings.

--
Rune / 5Q5R

On Tue, 12 Nov 2019 at 01:26, Barry Jackson via Groups.Io <G4MKT=
[email protected]> wrote:

On 08/11/2019 15:18, Nick wrote:
> Thanks Rune. I did not understand the relationship between device
cals and nvna-s cals.
>
> Please allow me to check my understanding.
>
> Let's say I want to measure a ferrite choke from 1 to 50MHz. I set
up the cables and do a device cal over that frequency range using an
appropriate cal kit. I save that cal to say C0.
>
> With C0 selected on the device, I repeat the cal on nvna-s using the
same frequency range, same cables, same cal kit and save it to cal_0.cal.
>
> I can then measure my choke over the same frequency range using
nvna-s with as many data points as I like using multiple segments.
>

Yes

> Let's say I then want to measure a UHF filter over the range 100MHz
to 900MHz. Obviously I cannot use C0 and cal_0.cal. So I set up with
different cables and a different cal kit. I do a device cal over that
frequency range and save it to C1.
>

No. According to my understanding from Rune. On connection nvna-s reads
cal data from Memory 0 only, so unless your calibration originally
covered the whole of the frequency range and was saved to C0 then as far
as I understand that would not work.

> With C1 selected on the device, I repeat the cal on nvna-s using the
same frequency range, same cables, same cal kit and save it to cal_1.cal..
>
> I can then measure my filter over the same frequency range using
nvna-s with as many data points as I like using multiple segments and
save the results to s*p files.
>
> What if I then want to measure the filter over a restricted frequency
range, say 400 to 500MHz?
>
> Or a VHF filter with the same the cables and connectors from 100MHz
to 200MHz?
>
> Do I need a new pair of cals in either of these cases? (I would say
not.)

I would say that unless you make a full span course cal and use that
from C0 then you would need to save manual cals for the other ranges and
store them in C1..C3 and copy them to C0 before disconnecting from the
nvna and reconnecting to pick up each new cal from C0.

Maybe Rune can clarify whether or not I have misunderstood his comments
in



Barry
G4MKT

Hello Dana,
thanks for the heads up! :-)

--
Rune / 5Q5R

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.

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

Stay far away from this 3rd party seller. There are typos all throughout their company info and their shipping policy looks strange and has many spelling mistakes as well.

Wow,
now we judge products by spelling errors.

Never mind that Wally's business model put many establishment where queens English was practiced out of business,
employs senior citizens etc.

How shallow can your get?

I am ordering mine from guess who?

The latest version seems to be working just fine on my mac.
Just remember with Catalina, the latest Python isn’t working completely
so use an older version.

Dana VE3DS
Toronto Canada
where its going - 15C tonight

Wow! Bright lights, movie stars.

- Herb

Stay far away from this 3rd party seller.? There are typos all throughout their company info and their shipping policy looks strange and has many spelling mistakes as well.?



On Tue, 12 Nov 2019 at 8:12 PM, DuWayne Schmidlkofer<duwayne@...> wrote: I was browsing for something else when this link popped up.

--
DuWayne? KV4QB

I was browsing for something else when this link popped up.

--
DuWayne? KV4QB

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... :-)

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

Don't look too far. The chips can be found on Ebay. Search string: 10 PCS IP5305 SOP-8 IP 5305 IC CHIP
on1bes Herman

I never had to use Zadig in Windows 10 64bit to use DFUseDemo. This is probably a problem by you. Put your Hardware Device Manager window on and examinate following. Try uninstalling Zadig (actually a USB driver) until it no longer appears in Hardware Devive Manager window. This may have to be done multiple times. In the View menu, put the option "show hidden devices", you will see them grayed out in the list, and see if there is an earlier installation of Zadig (Zadig itself is not visible, but 'USB lib device' or something similar - i have not the exact names, but don't delete the 'Universal Serial-Bus Controllers'!) delete or uninstall all gray drivers until they are gone. The Wiki Files contains the manual of DFUseDemo and its installation. Follow it carefully. I test it again here, and you don't need Zadig. If you connect the Nano, with the boot button pressed, a "STM Device in DFU Mode" will first appear in Hardware Device Manager (with a yellow triangle). If you wait 20 seconds, the driver is automatically loaded in Windows, and the "STM Device in DFU Mode" is added to the list "Universal Serial-Bus Controllers". If you turn the Nano off, "STM Device in DFU Mode" will remain in the list, but then turn gray.
on1bes

I am running Windows10 Home 64 Bit, and had DFUsDemo running OK
After a firmware update (Erics Version 2.3) suddenly DFUSE Demo no more sees my NanoVNA-H .
Windows devicemanager shows the the device in DFU mode as "STM32 Bootloader" and when I run Zadig I can select "STM32 Bootloader" and install the drivers.
In the device manager I see for "STM32 bootloader" these drivers : WinUSB.sys, WdfCoinstaller01011.dll and WinUSBcoinstaller2.dll are these correct ??
I uninstalled and re-installed DFUseDemo, whatever i do, nothing helps.
So now I can no more.update the firmware !
Is there anyone who can help to solve this problem ?
Many thanks in advance
Jos

On Tue, Nov 12, 2019 at 09:37 AM, WB2UAQ wrote:

" Just wish it could measure higher impedances more accurately "

-----------------------------------------------------------------------------------------------------------

An HP8753 would not have helped you to measure higher impedances, I used one for years in my workplace and once you got too far off of 50 ohms the accuracy declined. In general, I believe that is true with all VNA's with a 50 ohm input impedance.

The HP8753 also started at 300 kHz which meant my company had to purchase a second VNA for lower measurements. I'd love to own a HP 8753 but I also know I can't afford the maintenance costs that would eventually be required.

- Herb

Hi I'm a newbie when it comes to the NANOVNA but over the years I have been involved with many different aspects of radio both amuter and professional.
SMA connectors are not intended for repeated connection and reconnection, there is little or no strain relief with SMA connectors, use good quality connectors and cable, use large radius no sharp bends in test environment.
When the integrity of a connection is of concern (SMA connectors on NANO) and the connectors have to be connected or reconnected many times, for example in testing and re testing/integration it is common to fit additional sacrificial connectors to those on the unit (I have). This is to prevent damaging the connector's and can be replaced and still preserving the integrity of the main connector.

--
Raymond G8KPS

I am thinking that the point of putting the nano in an enclosure is to stabilize the
poor isolation, not necessarily to eliminate it. But when the nano's leak is stabilized,
the ISOL CAL should then enable good correction.

This assumes that what goes outside the enclosure is done with good quality
cables (at least with respect to leakage) that are terminated. It would probably
help to terminate the ends in items that roughly duplicate the impedances that
the DUT will provide, although this is admittedly not very practical in most
cases.

BTW, SMA(M) cables that are left dangling with nothing connected can exhibit
wildly variable leakage from the ends. The center pin is coupled capacitively
to the nut, whose contact to the main body of the connector can range from only
fair to non-existent, depending on how it is laying (i.e., on what forces are acting
on the nut and from what directions, etc). RF leakage of this kind leads to RF
currents on the outside of the cable, which can resonate at various frequencies.
radiate to nearby cables that are similarly indisposed, etc. So even if you can't
spare good terminations, at least screw each cable end onto something that is
well-shielded for the isolation CAL step.

Dana

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

Why would you want to ever disable this?

When trying to evaluate / improve upon firmware calibration
by experiments with uncorrected data on hosts, e.g.
/g/nanovna-users/message/6696
/g/nanovna-users/message/6609
/g/nanovna-users/message/6600
/g/nanovna-users/message/6595
/g/nanovna-users/message/6484