开云体育

Also, you can try to setup START and STOP frequency in the STIMULUS menu, if PLL icon disappears after that, it means that your configuration has invalid frequencies and it's recommended to cleanup configuration settings.

thanks for the info, I did not think I would be the only one
Thanks Dave 2E0DMB

On Sat, Nov 2, 2019 at 05:01 PM, KE8CPD wrote:

Not sure what the PLL means in this firmware but that is the first time seeing
it.

This PLL icon means that si5351 failed to setup some frequencies during sweep.
There are two possible reasons:
1) bad configuration settings (it may store invalid frequencies for the sweep)
2) bad quality of si5351 which cannot work at 300 MHz

First try to cleanup configuration settings.
You can do it with "clearconfig 1234" command from PuTTY console.

If it doesn't help and PLL icon is still there, it means that your si5351 chip cannot work at 300 MHz.
You can fix it by reduce threshold frequency below 300 MHz and use saveconfig command to save that change.
It means that working range will be less than normal si5351.
Also, you can replace si5351 with a good one in order to fix that.

the load I got happens to have bad contact internally too, reacts when shaking or knocking at the table. Recommend use of better SMA-Loads for calibration.
See RF-Parts or other dealer

Hi My 50 ohm cal load failed that I got in the kit,
has anyone had this happen to them ?
Thanks Dave 2E0DMB

On Fri, Nov 1, 2019 at 11:19 PM, hb9 iiu wrote:

Same for me Maurizio
Di you find something in the meantime?
Daniel HB9IIU

Hi , now I upgraded to 3.0.1 , but the problem is still present. I think is not possibile to have more than 101 points.
And sweep cmd , not allow to set step size , but agin number of points.
Now I very busy , next week I will try again .
Maurizio IZ1MDJ

I use the device to process data via Python
So, what is the firmware developer like the most at the moment?

QRP has 'scanraw' command, which is more powerful than edy555 'scan'

On Sat, Nov 2, 2019 at 08:01 AM, KE8CPD wrote:

Not sure what the PLL means in this firmware but that is the first time seeing it.

-------------------------------------------------------------------------------------
QRP's 0.4.2 firmware includes a hardware check for the si5351. It tests if your NanoVNA will operate reliably above 300 MHz. The PLL symbol means that his firmware test has determined that your si5351 may have reliability problems above 300 MHz.

- Herb

Just got my money back from the last bogus eBay listing at $19.95!

Roy
WA0YMH

Hi KE8CPD -

Not sure what the PLL means in this firmware
but that is the first time seeing it

That is also the first time I have seen it, but it explains your crazy plot.
QRP added a check for those clock chips which cannot do 300MHz.

The workaround is set 'threshold' from USB shell to some value less than 300000000.

#70: facupov : a 64-bit working maxima under windows in 2 cases

Hello,

Allow us, please, to inform you that after hard days-and-nights
of many-many trials-and-errors, including tedious searching for
the lemmas below (e.g. in [1]-[3]), we just succeeded to install
in two 64-bit Windows systems in our PC of an AMD CPU, a Working
64-bit Maxima, but with the cost of disabling the whole DEP
(Data Execution Prevention) Protection in these Windows systems
-
* That * Is * You * Have * Been * Warned *
-
as follows:

- - - - - - (c) gin&pez@arg (cc-by-4.0) 2019 : start - - - - - -

I/II : w7p64

(1) Run as Administrator:

| wmic OS Get DataExecutionPrevention_Available

the right reply is:

| DataExecutionPrevention_Available
| TRUE

if not, then STOP trying - FAILURE.

(2) Run as Administrator:

| BCDEDIT /SET {CURRENT} NX ALWAYSOFF

(3) Restart

(4) Run as Administrator:

| wmic OS Get DataExecutionPrevention_SupportPolicy

the Right Reply is:

| DataExecutionPrevention_SupportPolicy
| 0

if not, then STOP trying - FAILURE.

(5) Run:

| E:\maxima-5.43.0\bin\lispselector.bat

Select : CLISP

(6) Run Xmaxima

the Right Response is:

| Lisp CLISP 2.49 (2010-07-07)

if it is, then : SUCCESS

if not, then:

(7) Run:

E:\maxima-5.43.0\bin\lispselector.bat

Select : SBCL

(8) Run Xmaxima

the Right Response is:

| Lisp SBCL 1.4.14

if not, then stop trying : FAILURE

if it is, then : SUCCESS.

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

II/II : wxpp64&sp2

(1) Create a desktop shortcut icon for cmd.exe
Mouse Right Click on cmd.exe icon
Select: Run as...
(o) Current user (...)
[v] Run this program with restricted access

and uncheck it to:

[ ] Run this program with restricted access

(2) In this Command Window run:

| wmic OS Get DataExecutionPrevention_Available

the Right Reply is:

| DataExecutionPrevention_Available
| TRUE

if not, then stop trying - FAILURE

(3) Select:

|Start|Settings|Control Panel|System|Advanced|
|Startup and Recovery|Settings|Edit|

go to the line of this wxpp64&sp2 system in boot.ini
and add the switch:

| /NOEXECUTE=ALWAYSOFF

(4) Restart

(5) Mouse Right Click on cmd.exe icon
Select: Run as...
(o) Current user (...)
[v] Run this program with restricted access
uncheck it to:
[ ] Run this program with restricted access

(6) In this Command Window run:

| wmic OS Get DataExecutionPrevention_SupportPolicy

the Right Reply is:

| DataExecutionPrevention_SupportPolicy
| 0

if not, then stop trying - FAILURE

(7) Download and install gnuplot 5.0.7 64-bit [1]
on your system disk "X" at:

| X:\Program Files\gnuplot

(8) Download and install 64-bit maxima-5.43.0 [2]
on your system disk "X" at:

| X:\maxima-5.43.0

but take into account, please, that * t h i s * Maxima also
installs the 64-bit gnuplot 5.2.7 at your system disk "X" at:

| X:\maxima-5.43.0\bin\gnuplot

(9) Copy the whole:

| X:\Program Files\gnuplot

over:

| X:\maxima-5.43.0\bin\gnuplot

(10) Run:

| E:\maxima-5.43.0\bin\lispselector.bat

Select : SBCL

(11) Run Xmaxima

the Right Response is:

| Lisp SBCL 1.4.14

if it is, then: SUCCESS

if not then:

(12) Run:

| E:\maxima-5.43.0\bin\lispselector.bat

Select : CLISP

(13) Run Xmaxima:

the Right Response is:

| Lisp CLISP 2.49 (2010-07-07)

if not, then stop trying - FAILURE

if it is, then : SUCCESS.

- - - end : (c) gin&pez@arg (cc-by-4.0) 2019 - - - - - - - - - -

References:

[1] -, "Installation of Maxima in Windows":


[2] MS Support, "How to determine that hardware DEP is available
and configured on your computer":

Last Updated: Apr 17, 2018

[3] Rajesh Babu Ramachandran, "How To Enable or Disable DEP In
Windows XP, Vista or windows 7?":


[4] maxima-clisp-sbcl-5.43.0-win64.exe:


[5] gp507-win64-mingw.exe:


Sincerely,

gin&pez@arg

:70#

I flashed the attached firmware and took a screen capture. Please see attached.

Not sure what the PLL means in this firmware but that is the first time seeing it.

Just ordered one for fun at $15.99... ref 254398992632

Just to see what user think is the best currently available firmware.
I use the device to process data via Python because the first one I received had a faulty screen (strap was actually not soldered to the board....)
Its to tune a magnetic loop antenna.....
So, what is the firmware developper like the most at the moment?

This is indeed how I started...

On 02/11/2019 11:13, Barry Jackson via Groups.Io wrote:

On 01/11/2019 22:48, QRP RX wrote:

On Fri, Nov? 1, 2019 at 07:46 PM, Barry Jackson wrote:

I notice that some .dfu firmware files that I have seen are in the 80kB to
100kB plus so the 16kB looks wrong to me.

16 kB is a page size. It means data chunk size which controller can accept for flashing.
So, software needs to split 80-100 kB firmware to 16 kB data chunks and send it one-by-one.

Thanks for your reply,
However I am not trying to upload to the vna, I am trying to download the existing firmware for backup.
The dfu-util man page says:-
"
-t, --transfer-size? SIZE
Specify the number of bytes per USB transfer. The optimal value is usually determined automatically so this option is rarely useful. If you need to use this option for a device, please report it as a bug.
"
Which is why I did not specify a -t option.
If I do, the max limit seems to be 4096, but the resulting file size is still only 16k.
What am I missing?
Barry
G4MKT

OK, I was missing the start address.

###############################################################
[baz@localhost Original]$ dfu-util -a 0 -s 0x08000000 -U original.bin -vv
dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to

Opening DFU capable USB device...
ID 0483:df11
Run-time device DFU version 011a
Claiming USB DFU Interface...
Setting Alternate Setting #0 ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 011a
Device returned transfer size 2048
DfuSe interface name: "Internal Flash "
Memory segment at 0x08000000 64 x 2048 = 131072 (rew)
Limiting upload to end of memory segment, 131072 bytes
Poll timeout 72 ms
Poll timeout 72 ms
Upload [=========================] 100% 131072 bytes
Upload done.
[baz@localhost Original]$
#############################################################

So, armed with this backup, I felt more confident to try to upload your (QRP) firmware.

#############################################################
[baz@localhost NanoVNA]$ dfu-util -a 0 -D NanoVNA-0.3.0m.dfu
dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to

Match vendor ID from file: 0483
Match product ID from file: 0000
Opening DFU capable USB device...
ID 0483:df11
Run-time device DFU version 011a
Claiming USB DFU Interface...
Setting Alternate Setting #0 ...
Determining device status: state = dfuERROR, status = 10
dfuERROR, clearing status
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 011a
Device returned transfer size 2048
DfuSe interface name: "Internal Flash "
file contains 1 DFU images
parsing DFU image 1
image for alternate setting 0, (1 elements, total size = 87457)
parsing element 1, address = 0x08000000, size = 87449
Download [=========================] 100% 87449 bytes
Download done.
done parsing DfuSe file
[baz@localhost NanoVNA]$
##############################################################

Seems to be working fine so far. Phew!!

Barry
G4MKT

links to the Wiki and FILE sections in the forum signature

I use the main page to quickly find links to even my own pages.
FWIW, I expect (and try to help) Wiki main page to be mostly up-to-date,
but necessarily brief.

Other pages and links are for more detailed information,
but less likely frequent updates, lacking feedback and fewer contributors.

GitHub documentation has yet no pull requests,
thankfully, since I have not yet successfully processed any test pull request..

I contemplate a substantial rewrite to /g/nanovna-users/wiki/shellcommands
because format is hard to edit and information is neither more helpful nor timely than

/g/nanovna-users/files/NanoVNA_Console_Commands_Oct-30-19.pdf

.. which has the disadvantage of link changes when updated.

There is no such thing as a free lunch =)

---8<---Corte aqui---8<---


---8<---Corte aqui---8<---


Em sáb, 2 de nov de 2019 às 10:12, Don via Groups.Io <donald_s_58103=
[email protected]> escreveu:

Looks like this was a scam after all. The negative feedback is now pouring in with buyers complaining of fake tracking numbers and never receiving the product. "If it is too good to be true...." applies here.

On Sat, Nov 2, 2019 at 07:41 AM, Nick wrote:

With BAV99 2 diodes and a fully charged battery set vbat_offset to 1000 and
VBAT reads 4210mV on Version screen.

I didn't know why you liked the BAV99 until I just looked them up. Nice!
Puzzled because the BAV99 data sheet says VF=0.7V max @ 1mA, and we are well below that...so I'd expect much less than 0,7V offset. Yet you report 4.2V for a 1V offset. On the whole, I really like the approach.

WRT the comment re pads on the PCB, the 16K resistor would go across the D2 pads, and a 100K from D2- to gnd. I have not looked specifically at what to do, but recall from my earlier peeks at the PCB that there seem to be plenty of places to tie the 100K to gnd in the area.

WRT "sufficient vbat_offset", it would be zero, so no problem.

The point is that software would have to be modded from (what I think is) the current
Actual = measured + sufficient vbat_offset, a form of linear equation of y=1*measured + sufficient vbat_offset
to a form of linear equation of y=slope*measured + sufficient vbat_offset. where users would then have to enter both a slope and offset.

ISo why resistors? Because the diode approach leaves is either sourcing special diodes such as the BAV99 or the SD103AWS, whereas the resistor approach seems more convenient. Maybe not.

If I try the resistors, I'll just put in vbat_offset=1000mV, and live with the increasing (small) error as voltage drops. Theoretically, at 3V, I'd be expecting 2.25V, but I'll see 2.00...because I think of the indication as something general, I am mot too fussy about accuracy. Same goes for any behaviour we might put into the VNA based on battery voltage...if it makes the choice a little early, that's OK. The voltage regulator shuts down at 3V, so any action we consider in the future needs to be safely above the. Meanwhile, the battery symbol is just a rough gas gauge.

Meanwhile, I was expecting the new battery to be 8+ lines high (based upon something QRP mentioned, but I forget), so it will be interesting to see how it relates to battery voltage...looks to be maybe 10 lines now.
My car has something like this
***
**
*

****
***
**
*
and they are grey to start, then as the values rise, what ever is lit turn from red > yellow > green. So I always have at least a red dot at the bottom, then it goes from there But I admit that the battery outline is very recognizable.

--
On the banks of the Piscataqua
Rich NE1EE