Screen Capture 16bit BMP from ULTRA
I do not know much about this topic, but I have been trying to share ULTRA (or NANOVNA) screen shots via email with some friends.?? The images never appear they just see the filename.
I have come to the conclusion that it may be due to the fact that the standard for BMPs is 24bit (I do not know that for sure).? If I send a 24bit BMP everything works as expected.
Any thoughts??? Has anyone else successfully shared their ULTRA Screenshots via email?
Thanks
Rich
|
My suggestion is to first put the rig on battery, then cut power at the mains panel. ? Then, while listening on the frequency you note the RFI on, see if it is there. ?If it isn¡¯t, turn on breaker by breaker until it reappears. ?This way you can narrow down the offending area in your home. ?Then you can target that area with your SA or receiver.?
My bet is wall warts/switching power supplies (the wiggling freq is typical) or Ethernet from a router. ?
73
K2PI
|
Re: tinySA_remote.py - Python tool for remote control of the tinySA from the PC
On Sun, Jan 29, 2023 at 10:06 AM, Ho-Ro wrote:
I think it it the other way round :) - The old firmware doesn't allow remote control, but you could try a firmware update that also provides other useful functions.
Thanks Martin. My Nano VNA is still original, 0-950MHZ or so, I never did any firmware upgrades. It worked well, so I left it alone ;-) 73 de Andy
|
Re: tinySA_remote.py - Python tool for remote control of the tinySA from the PC
On Sun, Jan 29, 2023 at 11:06 AM, Ho-Ro wrote:
The old firmware doesn't allow remote control,
The error message is now clearer:
'capture error - does the device support the "capture" cmd?'
I also added better device type detection (name and screen size) - GitHub updated:
|
Hi Martin. As it started before Christmas.... Has anyone still got their Christmas lights on?
Cheers Ian/MI5AFL?
|
On Sat, Jan 28, 2023 at 10:20 PM, Martin wrote:
Maybe in the near field this could be true, but that diminishes fairly quickly.
I should have clarified this point with a bit more detail. What I meant to say was that it is rare to have a situation where only the H or E field component exists. In most cases you are likely to be in the far field of EM radiation, so it is a mixture of both, and even if an antenna favours one or the other, it doesn't really matter. Regards, Martin
|
On Sun, Jan 29, 2023 at 09:07 AM, martinbradford2001 wrote:
I would prefer to pay Mirfield ?150 and know that I can easily send it back to them if there is a problem!
Hi Martin, Yes understood. Good luck with your interference hunting. One tip. Wear a high Viz jacket if you are walking around the neighbourhood with an antenna and box of tricks. No one pays any attention to you :-) Regards, Martin
|
Re: tinySA_remote.py - Python tool for remote control of the tinySA from the PC
On Sat, Jan 28, 2023 at 08:16 PM, Andy G0FTD wrote:
Normal I think, since your software is not for the old Nano VNA ;-)
I think it it the other way round :) - The old firmware doesn't allow remote control, but you could try a firmware update that also provides other useful functions.
|
On Sat, Jan 28, 2023 at 10:20 PM, Martin wrote:
...
It's odd that the dipole is not picking up the interference as much as the loop. Have you tried rotating the loop to see if you can null it out ? Looking through the loop would then give you the direction of the likely source. If you have enough space, try moving the loop, see if you can obtain another null. If the source is local you shouldn't have to move it too far to be able to get a decent cross bearing and resolve the 0/180 degree ambiguity.
...
Regards,
Martin
I've done nothing yet apart from a quick experiment with the Xiegu to see it that would help to search for it. I cannot easily rotate the loop without relocating it - it is pinned to a garden fence and it is just moderately thick wire, so has no rigidity of its own. I was hoping that a tinySA would give me sufficient information to target my experiments better - it's quite cold and wet out there at the moment and I really don't want to spend a long time mucking about without some assurance that it's going to solve the problem! Fortunately, I only really need the loop on 40m where the noise floor on the doublet is S9 or worse. On the higher frequency bands, the doublet does quite well. I'll wait for the tinySA Ultra to come back in stock, then order one from the UK distributor. These low cost Chinese devices are good value if you get a working example, but they can be quite high maintenance and I would like to have the reassurance of a local distributor for support. If you guys had told me that a ?45 basic tinySA would do the job, I might have taken the risk, but the Ultra is a fair bit over ?100 even ordered direct from China - I would prefer to pay Mirfield ?150 and know that I can easily send it back to them if there is a problem! Martin (G8FXC)
|
Re: TinySA Ultra Serial control
|
Re: TinySA Ultra Serial control
You can use sweep center {freq} and sweep span {width}
--
Klaus, DL5KV
|
TinySA Ultra Serial control
Hello,?
I would like to control the tinySA ultra for measuring the power value(peak) at 868MHz?via serial commands. How to set the start and stop frequency? Or is there a command to set center frequency and span? Is it the sweep command?sweep [(start{867M})|({stop(869M)} [0])] ??
Thanks and Regards
Sanjeev
|
The following files and folders have been uploaded to
the Files area of the [email protected] group.
By: David Massey <wd4owa@...>
Description:
Latest updates and additions to the TinySA Ultra Menu-Tree Chart documents (Visio and PDF files). A big thanks to Kurt Poulsen for his assistance in the new additions and text corrections in this latest release!
|
Most likely the loop is much closer to the noise source or the noise source is almost pure vertical polarization and the loop which is probably vertical can hear it while the dipole can¡¯t. ?I have witnessed a 20 meter beam not hear power line noise that was heard at S9 over the noise floor with a vertical which was just amazing. ?There are other possibilities but the above are the most likely.
Don wd8dsb
|
>
>My understanding is that loop antennas respond to the magnetic component of the EM wave and dipoles respond to the >electric component.
>
Maybe in the near field this could be true, but that diminishes fairly quickly.
Loops tend to have better common mode rejection than dipoles, and this often the reason they appear to be less prone to pick up interference. It is not often that you are presented with a pure magnetic or electric EM field, and ?you have to be pretty close to the source for this to be the case.
It's odd that the dipole is not picking up the interference as much as the loop. Have you tried rotating the loop to see if you can null it out ? Looking through the loop would then give you the direction of the likely source. If you have enough space, try moving the loop, see if you can obtain another null. If the source is local you shouldn't have to move it too far to be able to get a decent cross bearing and resolve the 0/180 degree ambiguity.
Beware of re-radiation of noise from conductive objects such as overhead wires and street lamps, as these can often lead you down a false trail.
Regards,
Martin
|
email is bouncing, hope this works
Mike C. Sand Mtn GA
|
Martin
My understanding is that loop antennas respond to the magnetic component of the EM wave and dipoles respond to the electric component.? In your case, I'm not sure if the distance to the source of the interference is a factor.??
Your neighborhood power distribution transformer might be at fault.? If you can rig up a small loop with a portable radio receiver, you should be able to triangulate and narrow down the search area.
Regards,
Jim
Logic: Method used to arrive at the wrong conclusion, with confidence.? Murphy
-----Original Message-----
From: martinbradford2001 <martin.a.bradford@...>
To: [email protected]
Sent: Sat, Jan 28, 2023 11:28 am
Subject: Re: [tinysa] Sensitivity?
On Sat, Jan 28, 2023 at 04:58 PM, Jim Higgins wrote:
Look into LED traffic lights. In the USA, the LEDs are in rows and a row or
...
73 de Jim, KB3PU
Hmmm, don't have any traffic lights within a radius of close to a mile... Given the very significant difference in levels between my two antennae (both of which have a similar radiation pattern), I'm thinking that it must be something very local and pretty low power. I have a doublet resonant roughly on 20m at about 30 feet close to the house which I use for transmitting and a low-noise small loop which is strictly RX only and mounted at the end of the garden. The RFI is strong on that loop, but barely measurable on the doublet. Apart from this specific RFI, the loop remains the lower noise of the two. Martin (G8FXC)
|
Re: tinySA_remote.py - Python tool for remote control of the tinySA from the PC
On Sat, Jan 28, 2023 at 06:15 PM, Ho-Ro wrote:
The error is: "-d dev/ttyACM0", must be "-d /dev/ttyACM0"
But no need to use the -d unless your device is at an unusual port, e.g. on a mac.
Just use:
sudo python3 nanovna_remote.py -z2
What's your system, how did you install?
On Debian (or another system based on Debian, e.g. Mint or Ubuntu) you can simply type "make deb" and "make debinstall" that installs also the correct udev rule that allows user access to the USB serial port - no need to run as root which is always a bad thing.
Hi Martin, I realised my mistake soon after posting, the leading / for the comport was missing. To be honest this test was part of a something I abandoned many months ago on my Linux Mint 20.3 machine. I was curious to see if it worked with the old original Nano VNA (not H), but alas it doesn't. I just get an error about the screen size. $ sudo python3 nanovna_remote.py capture error - wrong screen size? Normal I think, since your software is not for the old Nano VNA ;-) Anyway, I shall be purchasing a Tiny SA soon, so the effort will not be wasted. Hopefully I can make it work on my Raspberry Pi3B+ too. Vy 73 de Andy
|
Re: tinySA_remote.py - Python tool for remote control of the tinySA from the PC
On Sat, Jan 28, 2023 at 06:41 PM, Andy G0FTD wrote:
sudo python3 nanovna_remote.py -d dev/ttyACM0 -z2
Traceback (most recent call last):
? File "/usr/local/lib/python3.8/dist-packages/serial/serialposix.py", line 322, in open
??? self.fd = os.open(self.portstr, os.O_RDWR | os.O_NOCTTY | os.O_NONBLOCK)
FileNotFoundError: [Errno 2] No such file or directory: 'dev/ttyACM0'
So, am I using incorrect comport syntax, if so what format should I use.
Andy, The error is: "-d dev/ttyACM0", must be "-d /dev/ttyACM0" But no need to use the -d unless your device is at an unusual port, e.g. on a mac. Just use: sudo python3 nanovna_remote.py -z2 What's your system, how did you install? On Debian (or another system based on Debian, e.g. Mint or Ubuntu) you can simply type "make deb" and "make debinstall" that installs also the correct udev rule that allows user access to the USB serial port - no need to run as root which is always a bad thing. ? Otherwise you should install also the file "60-nano-tiny.rules" into "/etc/udev/rules.d". Martin
|
Thanks Isidrio - but they are quoting the same delivery date as my local supplier...
Martin G8FXC?
|
Harv K2PI
Ho-Ro
Mike C.