Re: Can't update firmware
You have the wrong windows driver for use with tinysa-app.? ?Please see the document at the following link, and it will show you how to install the correct driver.? Note that tinysa-app is derived from nanovna-app, and uses the exact same update method, and will work fine once you have the correct driver in place.
/g/nanovna-users/files/Miscellaneous/DFU-mode%20Driver%20for%20Win10Win11
|
Re: Can't update firmware
On some windows systems the program fails to open the USB device when the name starts with \?\
Better use the dfu-util for upgrading.
--
Designer of the tinySA
For more info go to
|
Re: Can't update firmware
Just purchased a tinySA ultra from the Zeenko store, so it's genuine, and I can't upgrade the firmware.
?
1. Running on Windows 11
2. Have installed STM32 drivers
3. When I go into DFU mode I see a "STM32 BOOTLOADER" in Device Manager.
4. When I run tinySA-App.exe and attempt to upload firmware, I get the following message.
?
?
Any idea how to get past this?
|
Re: Can't update firmware
PS; Or you are trying to load your NanoVNA H or H4 using the software for updating the TyniSA? You either need the FW for the TyniSA instead of the NanoVNA or you need the correct software to update the NanoVNA? Either way, you appear to have the wrong FW or software. Clyde KC7BJE?
Just purchased a tinySA ultra from the Zeenko store, so it's genuine, and I can't upgrade the firmware.
?
1. Running on Windows 11
2. Have installed STM32 drivers
3. When I go into DFU mode I see a "STM32 BOOTLOADER" in Device Manager.
4. When I run tinySA-App.exe and attempt to upload firmware, I get the following message.
?
?
Any idea how to get past this?
|
Just purchased a tinySA ultra from the Zeenko store, so it's genuine, and I can't upgrade the firmware.
?
1. Running on Windows 11
2. Have installed STM32 drivers
3. When I go into DFU mode I see a "STM32 BOOTLOADER" in Device Manager.
4. When I run tinySA-App.exe and attempt to upload firmware, I get the following message.
?
?
Any idea how to get past this?
|
Locked
Re: Measure frequencies down to 500khz with tinysa?
We had to do that here at the University of Illinois, too. Back in the early 70's we were doing some ionospheric propagation studies along with the University of Houston. We flew two cesium clocks to NBS in Fort Collins CO. They sent one to us and one to the University of Houston. I was involved in it because I was studying radio science in grad school.
Zack W9SZ
Back 'in-the-day' I had to carry (transport) the 'flying clock'
from Northwest to White-House (no not that wh house) to establish
the exact 'phase' error for the ROTHR (Relocatable Over The
Horizon Radar). Why? Yeah, that's another kettle of fish to
digest. Bottom line, it had to do with the 'error' distance
between the transmitter site at wh-house and our receiver site at
NW. If you stuck your periscope out of the water 1000+ miles away
and were traveling just over 5mph, (knots) well let's just say you
now became a 'target' of interest. Yeah, Dave, then came GPS and
the gee-dunk trips were over.
Mike C. Sand Mtn GA
On 10/5/2024 12:48 PM, W0LEV wrote:
Yes.?
mHz is needed to "compete" in the FMTs.? However, we should
use correct abbreviations for the units.?
Having
once been professionally involved in precision timekeeping in
the early days of GPS, I well appreciate error bars in the
10^-14 Hz (in the lab, only).? Of course, once on orbit, we
had to correct for relativity.? Now we take GPS for granted.?
Dave
- W?LEV
Dave
- W?LEV
We all like to poke fun about this but if you ever participate
in the FMT you actually do need milliHertz precision to get
into the "green box".
On Fri, 4 Oct 2024 15:12:53 +0000
"W0LEV via "
<davearea51a=[email protected]>
wrote:
> QUOTE:? 200 mhz.
>
> 200 milliHertz?? That's the realm of earthquakes and
subsonics!? Possibly
> you mean 200 MHz, MegaHertz.
>
> Dave - W?LEV
--
73
-Jim
NU0C
--
|
Locked
Re: Measure frequencies down to 500khz with tinysa?
Back 'in-the-day' I had to carry (transport) the 'flying clock'
from Northwest to White-House (no not that wh house) to establish
the exact 'phase' error for the ROTHR (Relocatable Over The
Horizon Radar). Why? Yeah, that's another kettle of fish to
digest. Bottom line, it had to do with the 'error' distance
between the transmitter site at wh-house and our receiver site at
NW. If you stuck your periscope out of the water 1000+ miles away
and were traveling just over 5mph, (knots) well let's just say you
now became a 'target' of interest. Yeah, Dave, then came GPS and
the gee-dunk trips were over.
Mike C. Sand Mtn GA
On 10/5/2024 12:48 PM, W0LEV wrote:
toggle quoted message
Show quoted text
Yes.?
mHz is needed to "compete" in the FMTs.? However, we should
use correct abbreviations for the units.?
Having
once been professionally involved in precision timekeeping in
the early days of GPS, I well appreciate error bars in the
10^-14 Hz (in the lab, only).? Of course, once on orbit, we
had to correct for relativity.? Now we take GPS for granted.?
Dave
- W?LEV
Dave
- W?LEV
We all like to poke fun about this but if you ever participate
in the FMT you actually do need milliHertz precision to get
into the "green box".
On Fri, 4 Oct 2024 15:12:53 +0000
"W0LEV via "
<davearea51a=[email protected]>
wrote:
> QUOTE:? 200 mhz.
>
> 200 milliHertz?? That's the realm of earthquakes and
subsonics!? Possibly
> you mean 200 MHz, MegaHertz.
>
> Dave - W?LEV
--
73
-Jim
NU0C
--
|
Re: tinySA : most accurate power level
Early tinySA firmware was not very good at avoiding compression with strong input signals
It is easy to check for compression
Switch to manual attenuator mode and increase attenuation above the auto level.
If the measured power level increases there was compression.
Keep increasing attenuation till there is no longer a change of measured level
--
Designer of the tinySA
For more info go to
|
tinySA : most accurate power level
I'm building a 1kW+ HF power amplifier.? I've a 2kW homebrew dummy-load with a 60dB PAD (measured with a nanoVNA it's around 60db flat to 100MHz).? ?
?
With an IC7300 at 100% FM, 7.2MHz, the tinySA reads -10.5dBm? (As expected: 50dBm less 60db = -10dBm)? (Checking the linearity from from ICOM at 10% to 100% indicates all is working well).
?
So far, so good.
?
Inserting the AMP & LPF: there's a gain of around 12dB (after a 15dB protective PAD at the input of the AMP).? Aligned with the device specification.??
Input: 42.5dBm output 52.5dBm (i.e. -7.5dBm as measured by the tinySA)
?
When the input is increased to 50dBm, one would expect around 62dBm (1600W) at the output : assuming nothing has entered compression.
However, the tinySA reads -2.5dBm which equates to 57.5dBm at the dummy-load (560W).? The AMP is drawing 1,426W DC, the device's datasheet suggests an efficiency of around 80%.? So, one might expect the tinySA to read around 0dBm, indicating 60dBm at the dummy-load.? Checking with a thermal camera, nothing in the AMP (transformer cores) or the LPF cores appear to be getting overly hot (not 850W hot!).??
?
My question is:
Is it likely that the tinySA has become non-linear once above around -10dBm at its input?
Is there a sweet spot where the tinySA is most accurate???
?
I haven't manually configured the tinySA's input attenuator: i.e. it's in Auto mode.? Been using NanoVNA-APP with the tinySA.??
Yep, my next test is to insert a 10dB PAD between the tinySA & dummy-load (the AMP is currently off line for a completely different reason).??
?
Thanks in advance.
?
|
Locked
Re: Measure frequencies down to 500khz with tinysa?
Which is why I wrote it as "milliHertz". MilliHertz just would not be right. :) On Sat, 5 Oct 2024 16:48:46 +0000 "W0LEV via groups.io" <davearea51a@...> wrote: Yes. mHz is needed to "compete" in the FMTs. However, we should use
correct abbreviations for the units. -- 73 -Jim NU0C
|
Locked
Re: Measure frequencies down to 500khz with tinysa?
Yes.? mHz is needed to "compete" in the FMTs.? However, we should use correct abbreviations for the units.?
Having once been professionally involved in precision timekeeping in the early days of GPS, I well appreciate error bars in the 10^-14 Hz (in the lab, only).? Of course, once on orbit, we had to correct for relativity.? Now we take GPS for granted.?
Dave - W?LEV
Dave - W?LEV
We all like to poke fun about this but if you ever participate in the FMT you actually do need milliHertz precision to get into the "green box".
On Fri, 4 Oct 2024 15:12:53 +0000
"W0LEV via " <davearea51a=[email protected]> wrote:
> QUOTE:? 200 mhz.
>
> 200 milliHertz?? That's the realm of earthquakes and subsonics!? Possibly
> you mean 200 MHz, MegaHertz.
>
> Dave - W?LEV
--
73
-Jim
NU0C
|
Locked
Re: Measure frequencies down to 500khz with tinysa?
We all like to poke fun about this but if you ever participate in the FMT you actually do need milliHertz precision to get into the "green box". On Fri, 4 Oct 2024 15:12:53 +0000 "W0LEV via groups.io" <davearea51a@...> wrote: QUOTE: 200 mhz.
200 milliHertz? That's the realm of earthquakes and subsonics! Possibly
you mean 200 MHz, MegaHertz.
Dave - W?LEV -- 73 -Jim NU0C
|
Locked
Re: Measure frequencies down to 500khz with tinysa?
200Mc/min would be much neater than 3.3333333333(ad nauseam) Mc/s
though:-)
Cheers...Bob VK2ZRE
On 5/10/2024 4:27 am, rich wrote:
toggle quoted message
Show quoted text
Dog gone it, you are right.? It could be 200 Mega cycles per
minute.? Mea Culpa. ??
On 10/4/24 1:43 PM, Mike N2MS via
groups.io wrote:
Isn't
it 200 Mc/s ?
?
|
Locked
Re: Measure frequencies down to 500khz with tinysa?
Dog gone it, you are right.? It could be 200 Mega cycles per
minute.? Mea Culpa. ??
On 10/4/24 1:43 PM, Mike N2MS via
groups.io wrote:
toggle quoted message
Show quoted text
|
Re: pc control trace data?
toggle quoted message
Show quoted text
On Fri, Oct 4, 2024 at 12:58?PM hwalker via <herbwalker2476= [email protected]> wrote: On Fri, Oct 4, 2024 at 08:23 AM, Bryan Krone wrote:
Is there a way to collect the data from multiple displayed traces?
You can use the "trace {# } value" console command to retrieve the values for each trace.??
?
For example, "trace 2 value" will return 450 values for trace 2 in dBm if the default units are dBm for the tinySA Ultra.? Example return format is as below, so you will need to parse out the data values.
?
trace 2 value 0 -89.4
trace 2 value 1 -89.6
...
trace 2 value 449 -89.1
?
Herb
?
|
Re: pc control trace data?
On Fri, Oct 4, 2024 at 08:23 AM, Bryan Krone wrote:
Is there a way to collect the data from multiple displayed traces?
You can use the "trace {# } value" console command to retrieve the values for each trace.??
?
For example, "trace 2 value" will return 450 values for trace 2 in dBm if the default units are dBm for the tinySA Ultra.? Example return format is as below, so you will need to parse out the data values.
?
trace 2 value 0 -89.4
trace 2 value 1 -89.6
...
trace 2 value 449 -89.1
?
Herb
?
|
Locked
Re: Measure frequencies down to 500khz with tinysa?
And mmF (micki-micki-imikes) and mF (micki-mikes) and cps (cycles per second)........
Dave - W?LEV
Dave, are you sure that isn't 200 Mc ?? ;)?? What's this Hertz stuff
?
On 10/4/24 11:12 AM, W0LEV via
wrote:
QUOTE:?
200 mhz.
200
milliHertz?? That's the realm of earthquakes and subsonics!?
Possibly you mean 200 MHz, MegaHertz.
Dave
- W?LEV
|
Locked
Re: Measure frequencies down to 500khz with tinysa?
Isn't it 200 Mc/s ?
?
Mike N2MS
On 10/04/2024 11:28 AM EDT rich <rwe061@...> wrote:
?
?
Dave, are you sure that isn't 200 Mc ?? ;)?? What's this Hertz stuff ?
On 10/4/24 11:12 AM, W0LEV via groups.io wrote:
QUOTE:? 200 mhz.
?
200 milliHertz?? That's the realm of earthquakes and subsonics!? Possibly you mean 200 MHz, MegaHertz.
?
Dave - W?LEV
?
|
Locked
Re: Measure frequencies down to 500khz with tinysa?
It is not difficult to build your own. I have built a number of loopstick antennas using ferrite rods. I chose the Amidon Associates R33-050-750 rods.
I constructed these loops by placing a ferrite rod inside a piece of 0.5 inch pvc tubing slightly longer than the rod. I wrapped electrical tape around each end to center the rod in the tubing. Then I wound about 50 to 80 turns of wire (depending on the range I wanted) on the outside of the pvc tubing. I used some # 24 stranded wire stripped out of a length of CAT-5 cable for this. I brought the leads out to a capacitor, a 15 to 365 pF variable capacitor with any additional capacitance in parallel to cover the range needed. I used a NanoVNA to measure the inductance of the antenna I built at the frequency to be used, so I could calculate the approximate capacitance needed to tune to resonance. I have used such antennas in the range from 50 to 600 kHz. I found that they work quite well receiving WWVB and AM radio stations.
Zack W9SZ
On Sat, Aug 31, 2024 at 12:50?PM Roberth via <roberth.sjonoy= [email protected]> wrote: And what are the options if I'm not able to make my own "small loop antenna"?
|
Locked
Re: Measure frequencies down to 500khz with tinysa?
Dave, are you sure that isn't 200 Mc ?? ;)?? What's this Hertz stuff
?
On 10/4/24 11:12 AM, W0LEV via
groups.io wrote:
toggle quoted message
Show quoted text
QUOTE:?
200 mhz.
200
milliHertz?? That's the realm of earthquakes and subsonics!?
Possibly you mean 200 MHz, MegaHertz.
Dave
- W?LEV
|
Clyde Lambert
Mike C.
Jim Shorney