开云体育

I've been trying to keep up with this firehose, but it's challenging as I can't recall where I read various things.

Would those familiar with various FW versions write a short summary describing them and where the repositories are? Rather than try to describe all of them, just describe the ones you know about and the build procedures you know about. I've created a "Firmware" folder for this in the "Files" section.

I've soldered a connector for an ST-Link to my nanoVNA and am ready to get serious about working on the FW. I'd like to work on Linux as I'm a Unix guy Someone commented they'd written a summary of building the FW on Ubuntu, but it's not in the Files section. If you wrote that, please put it in the folder I created.

My initial focus is going to be to implement an SWR & TDR only FW version that will allow using them as a fully portable unit for testing feedlines and tuning antennas. I have both an HP 8753B and a Tek 11801 & SD-24, so I'm well equipped for this. In addition I have 30+ years of professional experience in seismic DSP and R&D working on scientific software, most of which centered on solutions of the wave equation. So *very* familiar territory except for the jargon and some minor changes to the equations.

Hugen offered a couple of times to provide a unit with an STM32F303CCT6, but I've gotten no response asking to buy one and I saw mention he had cancelled orders. So for now I'm going to try to do this on the existing HW using the STM32F072CBT6 by ripping out other features.

I expect that OEMs will migrate over time towards the '303, but if I can make an '072 unit do just SWR and TDR, the field day box will be a great place for your old unit when you upgrade.

Have Fun!
Reg

BTW It's all Dave Kirkby's fault ;-) He talked me into buying one.

I am discussing with the AA6KL9 to build a new firmware using the STM32F303CCT6. If all goes well, it can be provided later. To replace the mcu directly on the current hardware, you need to add a 1.5K resistor to the VCC on the USBDP Pin. The DFU mode of the STM32F303 requires an external 8M crystal to use USB, but STM32F072 does not need it, so you need to use SWD to update the firmware. You need to prepare an ST-Link or DAP-Link.
BTW: The new STM32F072-based NanoVNA firmware already supports TDR.

Thank you!

Hugen

My NanoVNA is using the STM32F072 processor and I've successfully installed the V0.1.1 release.That firmware version has issues when running standalone. Is there a compatibility issue between the F303 and F072 that would cause the errors in the cals and display data? See posts #2623 and #2644. I have seen no responses from anybody testing this code, so I'm wondering if the intent is that it only be used in PC mode and bundled with Rune's NanoVNA Saver GUI.

--
73

Gary, N3GO

Hi Reg,
The instructions were listed by forum member DMR.
Do a search for 'dmr' and 'linux' and I think you'll find it otherwise, I grabbed a copy but it's on my work PC so if I don't see it in the firmware section tomorrow, I'll stick a copy there. (You're 5 hours ahead of me)
Look here:
/g/nanovna-users/message/1508

Cheers
Larry

On Thu, 19 Sep 2019 at 01:43, <hugen@...> wrote:

I am discussing with the AA6KL9 to build a new firmware using the
STM32F303CCT6. If all goes well, it can be provided later. To replace the
mcu directly on the current hardware, you need to add a 1.5K resistor to
the VCC on the USBDP Pin. The DFU mode of the STM32F303 requires an
external 8M crystal to use USB, but STM32F072 does not need it, so you
need to use SWD to update the firmware. You need to prepare an ST-Link or
DAP-Link.
BTW: The new STM32F072-based NanoVNA firmware already supports TDR.

Thank you!

Is there any chance of a larger screen with a connector on so it can be
replaced if damaged? How about some connectors that allow one to use
external switches?
The NanoVNA is amazing for the price, but I believe many people would pay
more money for better product. A larger screen, and the ability to use
better quality external components would be the most obvious improvements.

--
Dr. David Kirkby,
Kirkby Microwave Ltd,
drkirkby@...

Telephone 01621-680100./ +44 1621 680100

Registered in England & Wales.
Company number 08914892.
Registered office:
Stokes Hall Lodge,
Burnham Rd,
Althorne,
Chelmsford,
Essex,
CM3 6DT,
United Kingdom

I pulled edy555 release 0.1.1 and merged with my scan command extension

/g/nanovna-users/files/NanoVNA%20PC%20Software

Contains an experimental TDR functionality and 1500MHz as upper limit

Maybe it would fit better in the Firmware section? ;-)

Good work!

--
Rune / 5Q5R

Done

This is the latest version of the edy555 that includes the TDR feature. I have modified the touchscreen calibration value before compiling and can be used directly with the 2.8-inch NanoVNA.

Using the cho45’s web interface can use nanoVNA very good on the phone , I think this is a very good expansion screen scheme. I'm also trying a 3.5-inch LCD, maybe working with the STM32F303 to create a new NanoVNA, and I want to be as consistent as possible with the NanoVNA for better community support. NanoVNA-F is a very good project to use a larger LCD, but it uses the expensive MDK compiler.

Thank You！

hugen

Hi Hugen,
this sounds very good! Are you looking at expanding the
frequency/measurement range by a change of components as well?

I'm happy to hear that you will stay consistent with the NanoVNA, but any
necessary improvements to the commands will, of course, be quickly
implemented by the application developers. :-)

--
Rune / 5Q5R

Hello Erik,
Thank you for adding your extension to the Hugen nanoVNA version 0.1.1.

It would be nice to fill out in the "version window" the version number,
e.g.: 0.1.1 + scan, 1500MHz

Then you could look up what version is actual flashed.

I am working mainly with MacOS.
In case you use the program "dfu-util" on Linux or MacOS for flashing, the USB vendor ID is 0000 in your .dfu file, and you cannot flash.
Error message: dfu-util: Error: File ID 0483:0000 does not match device (0483:df11 or 0483:df11)

In this case I have to transfer your .dfu file to Windows, use DfuFileMgr.exe to convert your file to .hex,
and convert it back to format .dfu with entering the USB vendor ID: DF11.
Then copy it back to MacOS and use dfu-util for flashing.

Therefore it would be also nice to add the USB vendor ID : DF11 to your .dfu file.

73, Rudi DL5FA

I agree and was going to put forth the same request as Rudi just did:

On Thu, Sep 19, 2019 at 02:39 PM, <reuterr@...> wrote:

Hello Erik,
Thank you for adding your extension to the Hugen nanoVNA version 0.1.1.

It would be nice to fill out in the "version window" the version number,
e.g.: 0.1.1 + scan, 1500MHz

Then you could look up what version is actual flashed.

Due to an ever-increasing number of NanoVNA firmware developers providing binaries on this forum (I think it's up to 5 now) and building different variations and/or experimental versions, I (and others) have a request to make of those same developers:

Please use the NanoVNA's boot-up central message field to provide at least the developer's forum name along with their version number (or date) and possibly included options.

All Nano F/W versions I download are archived and labeled with the developer name, date, F range and any other options along with any sub-version numbers if updates come out.
It could be automated through the make file for convenience.

How do the developers (you know who you are) feel about this?

73
Larry

If you are modifying the FW *please* maintain a file in the Firmware folder with release notes and version information along with the location of the source repository.

If you make comments such as "TDR is now in the FW" *please* state which version. This has turned into an Abbott and Costello skit.

I had asked about a post about instructions for building the FW on *Linux*, not Windows. The search feature doesn't produce anything useful. The maddening part is I'm pretty sure I thanked the person who did that, but I cannot even find a list of my own posts.

I've downloaded both the ST development tools and the Gnu tools onto a Debian 9.3 system, but I'm now so confused about who has done what that I'm reluctant to actually do *anything*. I don't want to reinvent the wheel. and unsure about whether the version that came on my unit is buggy and needs fixing to use the command line console.

I'd like to see if I can improve the dynamic range at higher frequencies with some DSP. Depending upon the nature of the situation, I think it might be possible to pick up 20-30 dB improvement.

But at the moment I'm completely befuddled by "Who's on First".

Also, if you're quoting and commenting inline *please* delimit the quotes from your own comments. There have been a number of posts I gave up trying to figure out. They looked as if there were 3 or more authors.

Reg

Yeah, sorry about the window link, I was half asleep at the time.
DMR has mentioned a Linux how-to in this thread.

/g/nanovna-users/topic/33072199#1507
I think it's about the 4th post in.

It mentions using cygwin on windows but you'll get the gist of it.
Search for posts by forum member Lapo as he also is building in a Linux environment.

Cheers
Larry

Hi Reg,
Ohan made a guide. I'm not certain the SSH keys are required, but it's all
there:



--
Rune / 5Q5R

On Fri, 20 Sep 2019, 00:35 Reginald Beardsley via Groups.Io, <pulaskite=
[email protected]> wrote:

If you are modifying the FW *please* maintain a file in the Firmware
folder with release notes and version information along with the location
of the source repository.

If you make comments such as "TDR is now in the FW" *please* state which
version. This has turned into an Abbott and Costello skit.

I had asked about a post about instructions for building the FW on
*Linux*, not Windows. The search feature doesn't produce anything useful.
The maddening part is I'm pretty sure I thanked the person who did that,
but I cannot even find a list of my own posts.

I've downloaded both the ST development tools and the Gnu tools onto a
Debian 9.3 system, but I'm now so confused about who has done what that I'm
reluctant to actually do *anything*. I don't want to reinvent the wheel.
and unsure about whether the version that came on my unit is buggy and
needs fixing to use the command line console.

I'd like to see if I can improve the dynamic range at higher frequencies
with some DSP. Depending upon the nature of the situation, I think it
might be possible to pick up 20-30 dB improvement.

But at the moment I'm completely befuddled by "Who's on First".

Also, if you're quoting and commenting inline *please* delimit the quotes
from your own comments. There have been a number of posts I gave up trying
to figure out. They looked as if there were 3 or more authors.

Reg

On Fri, 20 Sep 2019 at 07:09, Rune Broberg <mihtjel@...> wrote:

Hi Reg,
Ohan made a guide.

This sentence

“Flash by setting the device to DFU boot, either in software or by short of
pins, then:”

could usefully be expanded. I don’t know how to do either

Dave
--
Dr. David Kirkby,
Kirkby Microwave Ltd,
drkirkby@...

Telephone 01621-680100./ +44 1621 680100

Registered in England & Wales.
Company number 08914892.
Registered office:
Stokes Hall Lodge,
Burnham Rd,
Althorne,
Chelmsford,
Essex,
CM3 6DT,
United Kingdom

Hi David.

I've updated the post with instructions, on the opposing side of the SMA connectors CH0 and CH1, there are two pins on the PCB labelled VDD and BOOT0.
They need to be shorted with the powered off state, then with those shorted power on the device.

Sorry for the confusion.

Ps. I included the ssh key part as I could not "git submodule update --init --recursive" without a one.

Kind Regards
Ohan Smit
ZS1SCI

Ps. I included the ssh key part as I could not "git submodule update
--init --recursive" without a one.

Interesting! I had the same issues, and instead finally resolved it by

editing the .submodules file:

- replace the 3rd line with "url =
- add a new line to the end of the file

Finally type "git submodule sync", and then "git submodule update --init
--recursive" works correctly.

I prefer your fix!

Rgds,
Dave

Found a UI bug in latest Sept 18th TDR version firmware from Erik in the filles section:

- select Display -> Transform -> Velocity Factor
- click on the small keyboard image icon at the lower right corner
- display is no longer responsive to touch input and top row of on-screen keyboard partially blanks (attempt to show something?)
- press the Jog switch < or > function and full onscreen keyboard and touch input returns. Jog switch Enter has no effect.

This is repeatable on the velocity screen.

Regards,
Larry