开云体育

OSError: cannot write mode RGBX as PNG

So, Python conglomeration differences...
Sure enough, newer Python breaks RGBX...
Breakage among Python versions is breathtaking;
hate M$, but they generally consider backward compatibility.

RGBX avoided adding wasted xFF byte to each pixel in np.array.

screenV.py is reverted to RGBA:


G:\>py --version
Python 3.6.6
G:\>pip freeze
certifi==2019.9.11
numpy==1.17.3
Pillow==6.2.1
pipenv==2018.11.26
pyserial==3.4
virtualenv==16.7.5
virtualenv-clone==0.5.3

Rather than try to match yours, 64-bit Python 3.8.0 was installed

=================================================
G:\>py --version
Python 3.8.0
G:\>pip install --upgrade pip
Collecting pip
Using cached
0c6f96af8ce16cfbc1cb06bedf8e9164ce5551ec1/pip-19.3.1-py2.py3-none-any.whl
Installing collected packages: pip
Found existing installation: pip 19.2.3
Uninstalling pip-19.2.3:
Successfully uninstalled pip-19.2.3
Successfully installed pip-19.3.1
G:\>pip install pyserial
Collecting pyserial
Using cached
07414e2a01a7c88bb3915cbe3c8cc06e209f59c30/pyserial-3.4-py2.py3-none-any.whl
Installing collected packages: pyserial
Successfully installed pyserial-3.4
G:\>pip install numpy
Collecting numpy
Downloading
d7f7e9dd9ce36cdc34d199ccae0ab37ed6a13b85/numpy-1.17.3-cp38-cp38-win_amd64.whl (1
2.7MB)
|████████████████████████████████| 12.7MB 3.3MB/s
Installing collected packages: numpy
WARNING: The script f2py.exe is installed in 'G:\Gateway\my\VS\Shared\Python38
_64\Scripts' which is not on PATH.
Consider adding this directory to PATH or, if you prefer to suppress this warn
ing, use --no-warn-script-location.
Successfully installed numpy-1.17.3
G:\>pip install pillow
Collecting pillow
Downloading
f24516cbae85d581058f2bac635fc82e4bd6c2bf/Pillow-6.2.1-cp38-cp38-win_amd64.whl (2
.0MB)
|████████████████████████████████| 2.0MB 819kB/s
Installing collected packages: pillow
Successfully installed pillow-6.2.1

G:\>pip freeze
numpy==1.17.3
Pillow==6.2.1
pyserial==3.4
G:\>py screenV.py py38

Updating both cmd.exe and MSYS2 environments is always fun..
$ pip freeze
numpy==1.17.3
Pillow==6.2.1
pyserial==3.4
$ python --version
Python 3.8.0
$ py screenV.py msys

Kurt,
I only had the briefest of looks, but three is an error/typo on the top
right of the first table. A value of -186 ps is given, but I assume that
you mean -1.86 ps

On Mon, 28 Oct 2019 at 15:25, Kurt Poulsen <kurt@...> wrote:

Hi All

I have last week on 24-10-2019 received the NanoVNA-H from Alibaba.com
shipped on 23-10-2019 so within one day to DK via DHL.
It is the version in the Giftbox and already housed in a plastic casing.
Pretty nice unit. As promised by Hugen it is delivered with the new low
loss SMA female female adaptor from now on, and the loss is extremely small
being 0.02dB at 900MHz as an fantastic improvement compared to the previous
delivered lossy SMA female female adaptor. The male Short, Open and load
adaptors is unchanged.
So I stopped reading new males on the NanoVNA-user.io, and used the time
since then to totally characterize the supplied kit together with the
NanoVNA-H and have the pleasure to share the findings in attached document.
I have not tested my new data together with the NanoVNA-H and Rune’s
NanoVNA-saver as I have important works now delayed due to this (very time
consuming) work and hope you guess will do me the favor and try it out ?
(I need a break)

Kind regards

Kurt




--

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

New to VNAs, I picked up a NanoVNA after a fellow ham showed one around at a hamfest. (I think I got "lucky" and got a good one.) I've been following my nose, learning as I go, and studying various technical VNA web sites. I came to wonder why all the NanoVNAs that I see advertised come with at /most/ one short, one open, one load test fixture. It seems to me that we /need/ 2 of each to do a decent cal...or is what we are doing actually a valid, but "incomplete" cal...we have actually only calibrated Port 1 (Ch0), and I am not sure about the implications of that. There are no instructions with my device, so I have been reading docs and messages here.

One of the issues that I see as hams do various "tests" and "demos" is that those activities seem to be not well understood by those executing them or those reading|observing them. Because those activities are presented with a modicum of authority, they are repeated around the ham community, leading to confusion (I observe).

I intend to keep pointing folks to these pages...we need a central place where vetted information can be presented.

One of my questions is this: if I cal with only one set of short and load fixtures, then is the through valid? And does it really matter at frequencies below, say 600 MHz? Most of the stuff that I do as a ham does not seem to need super precision. OTOH, I want to use this device in the best way possible, just as I do all my gear, including test gear. I've ordered a 2nd NanoVNA from hugen (or so I hope), and it will come with a 2nd set of cal fixtures.

--
On the banks of the Piscataqua
Rich NE1EE

Hi All

I have last week on 24-10-2019 received the NanoVNA-H from Alibaba.com shipped on 23-10-2019 so within one day to DK via DHL.
It is the version in the Giftbox and already housed in a plastic casing. Pretty nice unit. As promised by Hugen it is delivered with the new low loss SMA female female adaptor from now on, and the loss is extremely small being 0.02dB at 900MHz as an fantastic improvement compared to the previous delivered lossy SMA female female adaptor. The male Short, Open and load adaptors is unchanged.
So I stopped reading new males on the NanoVNA-user.io, and used the time since then to totally characterize the supplied kit together with the NanoVNA-H and have the pleasure to share the findings in attached document.
I have not tested my new data together with the NanoVNA-H and Rune’s NanoVNA-saver as I have important works now delayed due to this (very time consuming) work and hope you guess will do me the favor and try it out ? (I need a break)

Kind regards

Kurt

On Sun, Oct 27, 2019 at 09:38 PM, <bryburns@...> wrote:

What version (year or ...) of Matlab are you using?

Runs here on both R2018b and R2015a.

- Jeff, k6jca

I like the idea, though I think that the installed 450 will work fine for me...I have a 2000 mAh pack that I carry for "everything else", and I have used it with this and to recharge it. I noted that there seem to be several Motorola BT61 batteries, as high as 1100+ mAh, and that it looks as if some soldering to the battery is needed. I also think that the wires (mine terminate in a PCB plug similar to this...)

...don't need to be quite so large for so few mA. This BT61 idea would be my go to.
--
On the banks of the Piscataqua
Rich NE1EE

Oristo, if you want to change colors in firmware, you can do it with "color" command introduced in NanoVNA-Q v0.4.2 firmware:

for example, if you want to change tracks color, just use the following command:

color 0 0xFF0000

it will change TRACE 0 color to red (web color #FF0000)

color 1 0x00FF00

will change TRACE 1 color to green (web color #00FF00)

color 2 0x0000FF

will change TRACE 2 color to blue (web color #0000FF)

color 3 0x808080

will change TRACE 3 color to gray (web color #808080)

color -1 0xFFFFFF

will change grid color to white (web color #FFFFFF)

Also, you can check current color values just by executing color commands with no arguments.

You can play with it, at any time you can revert colors back just with power off and power on.

If you want to store selected colors permanently, you're needs to use menu CONFIG => SAVE

Enjoy! :)

Use a flat, metal-encased cellphone battery like I did.
You'll get 2X the run-time with an 800mAH and it sits flat against the back of the device.
The Nano's battery charger has no problems charging the battery.

/g/nanovna-users/attachment/223/0/Battery-PCB-MiscShields.jpg

Yes
The serial library is rather different
Apart from having to modify the nanoVNA command files the rest should work.....

Has anybody tried this with Octave? (Matlab open source "clone")

On Sun, Oct 27, 2019 at 05:36 AM, Oristo wrote:

perhaps because different Python conglomeration

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

My Python conglomeration:

python --version

Python 3.7.4

pip freeze

future==0.17.1
ipython==7.8.0
ipython-genutils==0.2.0
matplotlib==3.1.1
numpy==1.17.1
pandas==0.25.1
Pillow==6.1.0
PyQt5==5.13.0
PyQt5-sip==4.19.18
pyserial==3.4
scikit-rf==0.14.9
scipy==1.3.1

- Herb

To bulky

El lun., 28 oct. 2019 a las 0:46, sanjeevi (<sanjeevirao@...>)
别蝉肠谤颈产颈ó:

Oristo wrote,

" … Updated script documents that without affecting results"

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

The updated script generates the following exception for me:

PS C:\Users\Owner\Downloads\NanoVNA> python screenV.py foobar
Traceback (most recent call last):
File "C:\Program Files\Python37\lib\site-packages\PIL\PngImagePlugin.py", line 799, in _save
rawmode, mode = _OUTMODES[mode]
KeyError: 'RGBX'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "screenV.py", line 73, in <module>
Image.frombuffer('RGBX', (320, 240), xBGR, 'raw', 'RGBX', 0, 1).save(str(sys.argv[1])+'.png')
File "C:\Program Files\Python37\lib\site-packages\PIL\Image.py", line 2088, in save
save_handler(self, fp, filename)
File "C:\Program Files\Python37\lib\site-packages\PIL\PngImagePlugin.py", line 801, in _save
raise IOError("cannot write mode %s as PNG" % mode)
OSError: cannot write mode RGBX as PNG


- Herb

Why?
The Microsoft Office suite has supported Open Document Format since 2007.

On 28 October 2019 at 00:06 N9KDY <n9kdy@...> wrote:


Nan wrote:

Take note that the file was originally created in Open Document Format and needs to be converted to XL

Or you COULD just go to the site, download
the libreoffice suite, install it, open the file in open document
format, and get on with things without kowtowing to or contributing
money to the Microsoft Evil Empire in any way. It ain't perfect, but
it's a good start.

Yeah, I'm one of those.

Monopolies, especially monopolies that provide shoddy crap which is NOT
to standard or up to snuff for real end-user use, give me a major case
of the pip. Add in built-in spy-ware and I'm really not going to go there.

I used to be Tier-3 manager for a univerity HELL desk for IT support
(Yes, HELL. I lost the "P" the first week, it turned into another "L"
almost immediately.) and relied for my paycheck on the fact that
WinBLOWS (You prefer WinSUCKS?) was broken from the get-go. Nothing has
gotten better in the latest iterations of the garbage provided from the
Redmond Consortium. It's still "Not Ready For Prime Time." 340,000
viruses, trojans, and zero-day exploits can't all be wrong.....

Between BSD and Linux, and they're a LONG WAY from perfect, I can at
least read the source and perhaps figure out and fix whatever idiocy is
going on. (But systemd shouldn't be allowed to happen to any piece of
poor, unsuspecting, hardware.)

--
Wes Will
N9KDY

Nigel A. Gunn, 1865 El Camino Drive, Xenia, OH 45385-1115, USA. tel +1 937 825 5032
Amateur Radio G8IFF W8IFF and GMRS WRBV701, e-mail nigel@... www

Hi Herb -

On my set-up you are 1 for 2:

I'll live with that and just now determined:

Image.frombuffer('RGBA',..)
.. expects np.array in ABGR sequence,
which at least explains shift values.
Updaed script documents that without affecting results

I used it to help build this 2 bay, circularly polarized 450 MHz antenna. Each bay tuned for frequency and impedance. 75 ohm matching stubs tuned. And then the final tweaking of the two paralleled 100 ohm bays to get a 49.7 ohm resonant antenna at 450 MHz.

The NanoVNA was invaluable for each step of the process.

Now on to pattern testing. It should give me 0 dB gain and be unaffected by the polarization of the distant reference antenna. We shall see.............


WA8TOD

I did the same way using MFJ analyzer. I even found out exact technical details for building measuring adapters:



I did not do the same with NanoVNA yet, but I see no reason that is should not work.

You can also connect trap to hot ends of both CH0 and CH1 and do S21 measure without need for coil adapter. It worked for me when I was unable to detach trap from antenna.


--
73,

YT9TP, Pedja

hello hans, tnx for reply. i intend to do the same with the nanovna, different versions of published trap designs

Hi Sanjeevi,

I tested my 7.050 MHz W3DZZ trap resonance frequency like this:

1 turn of wire, wound around the trap coil is connected to CH0.
You will see the resonance. Then bring the wire turn away as
much (or little) as you can, as long as you still see the resonance.
(That is the smallest possible coupling). Bring the marker to that
resonance and read the frequency.

I actually did that with my AA-600, but it will work just as well with
the NanoVNA.

The principle of measuring by just enough coupling is old. It already
was done, when we long ago used a grid dip meter for it while listening
to it's signal on a freq. calibrated receiver. In that case the winding was
formed similar to a figure '8' : One ring around the grid dip coil, the other,
separated by several cm of twisted wire, around the trap.

There are other possibilities, but this works.

73, Hans
DJ7BA


-----Ursprüngliche Nachricht-----
Von: [email protected] <[email protected]> Im Auftrag von sanjeevi
Gesendet: Montag, 28. Oktober 2019 06:54
An: [email protected]
Betreff: [nanovna-users] has anybody tested hf traps

how to test hf traps




--
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.

Hi Wayne,
It's good to hear that you found a workable solution. I would *still* very
much like the answers to the questions I posed above, as I need to figure
out why the application size changed, to avoid any further problems.

--
Rune / 5Q5R