¿ªÔÆÌåÓý

  1. Tinysa
  2. Messages
Expanded Topics Messages Polls
Date
Re: New FW release: Small updates

 

¿ªÔÆÌåÓý

Hello Erik,

Is it necessary to do a Clear All when doing a Calibration on the Ultra?

Regards...Bob VK2ZRE

On 21/12/2023 3:10 am, Erik Kaashoek wrote:

New FW release
Version V1.4137
Ultra Only

Changes:
- Correct the version number inconsistency
- Small change to calibration routine.
- Small extension of selftest.

--
For more info on the tinySA go to

Re: New FW release: Small updates

 

I like this. Makes me want to do my next upgrade in Linux. :) Thank you.

NB The reason I don't use Linux for upgrades now is simply a convenience of laziness. Most of my toys are in the same room as the Windoze box where I do most of my web surfing. They only walk to the shack/lab when I need them there for a task.

73

-Jim
NU0C

On Fri, 22 Dec 2023 12:10:06 -0800
"Akai Moto via groups.io" <akai.moto@...> wrote:

bash script to retrive whatever bin is there in DFU folder.
This for SA4 only, but you can mod it to get from the SA folder too by taking out the "4"

This assumes the DFU folder holds whatever the latest bin is. If you want dfu and hex files too, then just make a loop for bin dfu hex, etc.

#!/bin/bash
RESULT="`wget -qO- -e robots=off | sed -e 's/<[^>]*>//g' | grep bin | awk -F '\\.bin' '{print $1".bin"}'`"
Link="
wget -e robots=off $Link






--

73

-Jim
NU0C
Re: New FW release: Small updates

 

Quick note about filenames and update utilities.

The app does not care about filename, because you have to select it, so that's the file it pushes in.

dfu util however uses filename as arg, so it needs to match the actual filename you wish to push (dfu util has to "find" the file, etc). In the dfu bat file it uses default name of "tinySA.bin"

I have several tiny devices, and the app didn't work on all of them, but dfu util does, so I stick with dfu util.
Re: New FW release: Small updates

 

bash script to retrive whatever bin is there in DFU folder.
This for SA4 only, but you can mod it to get from the SA folder too by taking out the "4"

This assumes the DFU folder holds whatever the latest bin is. If you want dfu and hex files too, then just make a loop for bin dfu hex, etc.


#!/bin/bash
RESULT="`wget -qO- -e robots=off http://athome.kaashoek.com/tinySA4/DFU/ | sed -e 's/<[^>]*>//g' | grep bin | awk -F '\\.bin' '{print $1".bin"}'`"
Link="http://athome.kaashoek.com/tinySA4/DFU/"$RESULT
wget -e robots=off $Link
File /Utilities/upd_ultra uploaded #file-notice

Group Notification
 

The following files and folders have been uploaded to the Files area of the [email protected] group.

By: Zilvinas, LY2SS <zilvinas.atkociunas@...>

Description:
This bash script for Linux automatically fetches .bin file for TinySA Ultra from update server and updates firmware on device using dfu-util. Use it at your own risk.
Re: #console_commands, possible BUG on the text command.

  

Erik, thanks for the clarification, I thought I might be doing something wrong. 

Note, the menu command works to save screen when AUTONAME is enabled.

Thanks you,
Toni
Re: #console_commands, possible BUG on the text command.

 

For now the MENU and TEXT commands won't work for text entry such as file names, it does work for data entry.such as levels or frequencies.
Will add this disclaimer to the wiki
--
For more info on the tinySA go to https://tinysa.org/wiki/
Re: New FW release: Small updates

 

Maybe it would be enough to make a soft link on the server to the actual files.
Re: #console_commands, possible BUG on the text command.

 

Syntax is OK, let me check
--
For more info on the tinySA go to https://tinysa.org/wiki/
#console_commands, possible BUG on the text command.

 

Setting filenames to save screens to the SDcard after the menu command does not work.??

Script example:?
menu 9 6
text SCREENEXAMPLE?

nothing is done.?Is this syntax usage of the text command correct?
Toni


?
?
Re: New FW release: Small updates

 

On 22/12/2023 08:56, Zilvinas, LY2SS wrote:
Dear David,

How to automatically (bash/wget) fetch file from the server when it's name
changes with every release then?
Good point I always do manual updates.

There's (usually) just one copy of the files at that URL, so download all the
files (or just the .bin or whatever) into a local archive directory, check if
you now have either a more recent one or one with a higher version number (sort
by name?), and use that?

tinySA4_v1.4-126-gad1d783.bin
tinySA4_v1.4-128-ge95e79c.bin
tinySA4_v1.4-129-g95d48eb.bin
tinySA4_v1.4-134-g3c20a9c.bin
tinySA4_v1.4-137-g1806825.bin

Keeping a few archive versions allows you to go back if needed.

Cheers,
David
--
SatSignal Software - Quality software for you
Web:
Email: davidtaylor@...
Twitter: @gm8arv
Re: New FW release: Small updates

 

Dear David,
How to automatically (bash/wget) fetch file from the server when it's name changes with every release then?
Re: New FW release: Small updates

 

On 22/12/2023 05:10, Zilvinas, LY2SS wrote:
(since topic is about updates)
I would like to ask if it is possible to make an general name f.e. latest.bin
latest.dfu etc in the server.
This would be very easy to get update scripted on client side.

p.s. Thank you for the great tool!
I see no need for that. The TinySA app accepts the full file name as
downloaded. I always use the .bin.

David
--
SatSignal Software - Quality software for you
Web:
Email: davidtaylor@...
Twitter: @gm8arv
Re: TinySA Ultra does not show expected voltage level (different from signal generator)

 

On 22/12/2023 02:31, Bob Ecclestone wrote:

I think if Erik just annotates "V" to "Vrms", then there is no confusion as to
which "volt" the instrument is displaying.
Agreed - that's all that's needed.

David
--
SatSignal Software - Quality software for you
Web:
Email: davidtaylor@...
Twitter: @gm8arv
Re: New FW release: Small updates

 

On Thu, Dec 21, 2023 at 11:20 PM, Akai Moto wrote:
Just use dots "v1.4.137", no need to use the dash.
This mixed format comes directly from the git --describe command, which is the most correct versioning b/c it increments the part after the dash with every commit, no need to do it manually (with the danger of forgetting etc.) in an extra edit.
Re: New FW release: Small updates

 

(since topic is about updates)
I would like to ask if it is possible to make an general name f.e. latest.bin latest.dfu etc in the server.
This would be very easy to get update scripted on client side.

p.s. Thank you for the great tool!
Re: TinySA Ultra does not show expected voltage level (different from signal generator)

 

¿ªÔÆÌåÓý

Hi,
I know you are closing this subject Erik, but I think we need to make a couple of things clear here.

The relationship between Vrms, Vavg, Vpeak, Vp-p is very dependant on waveform.
For a pure sine wave, for Vpeak multiply Vrms by [root 2] and for Vp-p multiply Vrms by [2 x root 2].
For a squarewave, for Vpeak, multiple Vrms by 2.0 and for Vp-p multiply by 4. And Vaverage also equals Vrms.

So trying to correlate a peak-peak voltage reading on a scope compared to a spectrum analyser is very difficult, if not impossible.
In the case of a square wave, we have the classic diminishing odd harmonics.
So which harmonic do you want to correlate exactly with the scope reading? The fundamental you say. So what happens to all the extra "volts" due to the harmonics?
Can you (the operator) determine the harmonic distortion of a waveform on a scope. Unless it is gross, I certainly can't.

I think if Erik just annotates "V" to "Vrms", then there is no confusion as to which "volt" the instrument is displaying.
It is then up to the operator to interpret, and manipulate, that reading as they see fit.

Erik has already included a lot of measurement capability into this instrument that we once had to pay gazzillions of extra dollars for from the Big Guys.
Channel Power is just one that comes to mind.

So lets not get too carried away requesting semantic features and use these instruments as their design dictates.
A scope measures voltage relative to time, a spectrum analyser measures power relative to frequency.

Whether we are hobbyists or professional engineers, it is up to us to interpret the measurements we make.
Occasionally, both groups will misinterpret the results. That is our fault, not the instruments fault.

Just my 2 cents(rms) worth:-)

Cheers...Bob VK2ZRE


On 22/12/2023 8:24 am, Erik Kaashoek wrote:

[Edited Message Follows]
[Reason: Stupid auto correct]

Let's close this subject.
I will consider adding Vpp as one of the units if it fits in the various output fields
--
For more info on the tinySA go to

Re: TinySA Ultra does not show expected voltage level (different from signal generator)

 

That's interesting. From my personal perspective, not saying you are right or wrong, in 40+ years of working with RF I have never measured any kind of volts with a SA. Even probing circuits with a HP high impedance active probe it was still dB. All of my RF generators are calibrated in dB and RMS volts. The only place I use P-P is when it is called out in circuit diagrams or voltage charts, and then the tools of choice are a scope or a milliVolt meter. Which are typically the instruments specified for the reference reading if they are specified at all. It is worthy of note that a 50 Ohm input impedance SA will likely read differently than a high impedance scope.

I see that Erik is going to accommodate your request. Happy measuring! :)

73

-Jim
NU0C

On Thu, 21 Dec 2023 22:04:08 +0100
Ma?l H?rz via groups.io <mh-nexus@...> wrote:

I am curious, what is your use case for measuring P-P with a spectrum
analyzer?
Just like you mentioned yourself:

P-P is easy to measure and not dependent on waveform purity but does
not translate easily to power in a scope if not a pure sine wave.
With a spectrum analyzer you always have a sine wave at the
fundamental frequency of a complex wave.
Main reason: Vpp is easy to measure (and see) on scopes.

A simple use case is looking at the output of a generated signal at a
desired frequency and seeing if the different instruments agree and get
a feeling how they correlate, visually. Some simple signal generator
chips specify their output in terms of Vpeak/Vpp. Yes, you could convert
it to dBm, but sometimes Vpp is just more "direct".

Similarly, you might want to look at an oscillator and see quickly how
close its Vpp is compared to the fundamental frequency shown on the
spectrum analyzer. You can then dig deeper to find out the causes, such
as overlayed noise/distortions etc, and see what other frequency
components exist. But first you can have a first high level impression
how much your signal reaches its expected output level.

Or you might have a sine wave that is split up with a directional
coupler, and compare outputs easily on the scope and on the spectrum
analyzer (and their respective power levels). I don't need to
characterize the full frequency spectrum/harmonics/other frequency
components always. Often simple sine waves are enough for many experiments.








--

73

-Jim
NU0C
Re: TinySA Ultra does not show expected voltage level (different from signal generator)

 

Erik,

While you¡¯re in such an accommodating mood (!), I wonder if you¡¯d consider adding the Ham Band shading feature to the Ultra, preferably with a CONFIG choice of band plan to match all the countries where the device is sold. (I think it would only take three.) I¡¯m sure many users are hams, and would find this feature very handy.
Re: TinySA Ultra does not show expected voltage level (different from signal generator)

 

We assume the SA4 is running the latest fimware v1.4-137 , and re-calibrated ?
6001 - 6020 of 19778