¿ªÔÆÌåÓý

  1. Tinysa
  2. Messages
Expanded Topics Messages Polls
Date
Re: Clip on youtube with tinysa ULTRA on 10 gHz

 

It works well at this frequency, if you have a known amplitude source you can use it, see how much lower the Tiny is reading and then do an offset in the external gain section. You can then save the setup as one of the presets. I did that with a known 0dbm signal (at work) on 10.368 Ghz and now it reads as 0dbm signal.(my signal offset is 31db)? In a span of 5Mhz the dynamic range with? a little tweaking of the settings can reach ~50db. Not too shabby. I use high pass filters between my equipment at home and the tiny at 10Ghz this prevents some of the crud on lower frequencies from overloading the mixer.

A short note, if you use a lower frequency source and use one of the harmonics to either cal the 5Ghz step or look at higher harmonics use a high pass filter to prevent the fundamental from overloading the input of the TinySA and thus give you a wrong reading / signals that are not really there. Mini Circuits makes some small high pass filters that come for different microwave frequencies and can sometimes be found for pennies on e-bay.?
Re: A round of applause!

 

I have really been pleased with both the TinySA and TinySA Ultra that I'm constantly
using them instead of my larger lab equipment. Great job Eric!!!

On Thu, Dec 15, 2022 at 8:36 AM W5CDT <charlie.texas@...> wrote:
The fact that the TinySA can do channel power measurements is amazing.? I have a TEK 492 which is a great ¡°mid-80¡¯s¡± machine but it cannot make channel power measurements which are so important for wideband signals and noise figure measurements. ?

Kudos to Eric and his team!

-Charlie?



--
Dennis, N5VRP
n5vrp.satx@...
Near Hemphill, Texas
Re: Which branch to use to compile the same firmware as Erik is releasing?

 

Martin,
Following your instructions I believe I have successfully compiled the latest tinySA4 firmware binary (as of today: Dec 15/2022), loaded into the tinySA ULTRA and confirmed correct operation.
Executed the Self test, then the Level Calibration, both passed.
The version display screen is clear/clean with no artifacts.
Here is what I see with my compiled version of firmware: (using 11.2.1 GCC compiler):
CONFIG->VERSION:
tinySA4_v1.3-564-g47a9cbc? ? ? ? ? ? ? ?(newer version just pulled form github....)
Compiler: GCC 11.2.1 20220111
HW Version: V0.4.5.1(168)? ? ? ? ? ? ? ? ?(slightly different than Erik's version?)

Here is what I see with Erik's v1.3-563 version of firmware:
The version display screen has some artifacts (extra dots, etc.)
CONFIG->VERSION:
tinySA4_v1.3-563-g1da836e? ? ? ? ? ? ? ?(version downloaded from http://athome.kaashoek.com/tinySA4/DFU/)
Compiler: GCC 7.2.1 20170904
HW Version: V0.4.5.1(167)? ? ? ? ? ? ? ? ?(slightly different than my compiled version?)

Both firmware compiles/version appear to be working OK.
If this makes sense to you, I will start a document that describes how to compile the tinySA/tinySA ULTRA firmware from the latest code obtained from Github.

Regards
Lane
VE7IHL
Re: TinySA Ultra screen misaligned

 

Aha. My bad. I should have simply opened it up before commenting.
Re: New ULTRA FW release: improved touch defaults and marker->Ref level

 

On 14/12/2022 21:08, Clyde Lambert wrote:
Hello Martin,
Could you please send me a link to your latest FW for the TinySA.
I must have missed your notice of the update.
Thank you,
Clyde KC7BJE
It's in the Wiki.

David GM8ARV
--
SatSignal Software - Quality software for you
Web:
Email: david-taylor@...
Twitter: @gm8arv
Re: Which branch to use to compile the same firmware as Erik is releasing?

 

Thanks for the info Martin!
I will try this out today and let you know...

Lane
Re: Clip on youtube with tinysa ULTRA on 10 gHz

 

I am active on 10 GHz and have so much equipment for that band that I would have no trouble with a signal source. My transverter with a phase-locked LO is accurate to 50 Hz at 10368.100 MHz. I'm also working on a low power (~100 mW) beacon for that band.

Hopefully when I get a little more money accumulated I can get one of these new TinySA units.

Zack W9SZ


On Thu, Dec 15, 2022 at 3:15 AM pe1hwo <pe1hwo@...> wrote:
Thanks, last week i did try the same with this:


Waveguide opening and black stamp on the back tells me X band.
I measured a nice curve when increasing the voltage.

But I could not find a trace with my homemade probe.
Will try again.

Sold my NOS 2k25's years ago.

Re: and a small discone antenna

 

Thanks Mario, this teflon cable started out with an sma connector on each end, i removed the nut and was left with a strong gold plated body which
was made to fit and soldered inside the cone with a minimal amount of teflon separating the disk, the clearcoat also acted? a bit like glue.
This was not the first discone i have made and builds on small improvements from previous models'
A quarter wavelength on 10 ghz is 6 mm so the junction is important to keep small and the rg400 cable has some flexibility.
TinySA-app CSV to Shure Wireless Workbench conversion #csv #tinysa

 

Hi!? I'm a sound engineer and wireless microphone frequency coordinator.? ?I recently bought a TinySA for generating scans for my use in the field.? This is a neat and very powerful device and will make a nice addition to my portable kit!? ? I have created a Windows Powershell 7 script which translates the CSV outputted by TinySA-app into a CSV format that is useable in the Shure Wireless Workbench frequency coordination workspace.

?

If you want to give it a try, check out the readme and enter your file locations into the scripts. You will also need to install Windows Powershell 7.
Re: Clip on youtube with tinysa ULTRA on 10 gHz

 

Hi I have just ordered the ultra and it has now been sent,?
I did not know that it went this high in frequency?
Thanks Dave?

On Thu, 15 Dec 2022, 13:25 Mario Vano AE0GL, <mvano@...> wrote:
Nice! The link is fine here...

I wish I had one of these in the 70s when I was using similar 10ghz gunn transceivers for transit vehicle beacon projects!

M

Re: A round of applause!

 

The fact that the TinySA can do channel power measurements is amazing. ?I have a TEK 492 which is a great ¡°mid-80¡¯s¡± machine but it cannot make channel power measurements which are so important for wideband signals and noise figure measurements. ?

Kudos to Eric and his team!

-Charlie?
Re: Which branch to use to compile the same firmware as Erik is releasing?

 

On Wed, Dec 14, 2022 at 08:24 PM, Lane Wilson wrote:
Hopefully this explains a bit of what I have done, and what I am doing.
I am just learning Git, and how to compile the tinySA firmware
Thanks a lot, Lane, for taking Your time to explain all this stuff in detail!
While it seems a bit too complicated for me at the moment (the learning curve is too steep), but I think it might be a good idea to add all the explanations provided here by You & Ho-Ro to a separate TinySA Wiki page (or elsewhere) )
With best regards,
Alex
Re: Which branch to use to compile the same firmware as Erik is releasing?

 

Hi Lane,

just some thought and ideas as a starting point:


On Thu, Dec 15, 2022 at 01:59 AM, Lane Wilson wrote:
I am trying to understand this, what is the best method to get the V4.3 branch to match Erik's current (latest) code?
I do all the git / GitHub stuff on the command line, the easy cold-start is:

git clone?
cd tinySA
git checkout V4.3
git pull
git submodule update --init --recursive

now you're almost ready to start, this would build the latest firmware, but with a wrong version number - dunno why, neither does Erik.
The Makefile uses the command "git describe" to get a version number like "v1.3-nnn-gxxxxxxx", where "v1.3" is the latest tag, "nnn" is the number of commits since this tag and "xxxxxxx" is the unique git commit hash. Without my hack it gives a wrong nnn, but xxxxxxx is correct, but the short version on the left margin is "1.3nnn".

My fix is (do this once)
git tag -d v1.3
git tag -a -m v1.3 v1.3 12a96bb

Now also the nnn is in sync with Erik.

For tinySA you can type:?
make
For tinySA Ultra type:
TARGET=F303 make

This should produce the *.bin *.hex and *.elf in directory build. Your toolchain 11.2 is quite new, I use 8.x and Erik's builds are still on 7.x, so it should work without an issue.

Do you need to add a tag that points to the latest commit hash? (g1da836e) ?
No, but with every new version that Erik puts on GitHub you should do a new
make clean
git pull

and you can start again.

If you want to make your own changes etc. you should create a new branch with
git checkout -b MyNewFeature
and you will be already on your new branch.

Maybe all this can be done also with TortoiseGit, I never used it - I'm an old guy who is used to the command line.
I do all my daily work on Linux (Debian stable) and have no Windows PC at home, so one or the other differences may exist.
But the Makefile should work also for Windows, because Erik's development setup is also Win.

If you need a *.dfu version of the FW you can look at my tinySA development branch on GitHub?https://github.com/Ho-Ro/tinySA/tree/Ho-Ro_devel , it is currently not in sync with Erik, but the Makefile builds also a *.dfu in addition to *.bin. *.hex and *.elf
I provide the sourcecode fot hex2dfu which compiles on windows if you have the gcc in your path. Erik has also a precompiled binary:

Maybe my and his version are a little different in syntax, but?
Erik's version:
HEX2DFU tinySA.hex -out tinySA.dfu
My version:
hex2dfu -i tinySA.hex -o tinySA.dfu

My favorite for firmware update is dfu-util, Erik provides a standalone windows binary:

dfu-util -d 0483:df11 -a 0 -s 0x08000000:leave -D tinySA.bin

This program uses libusb for access, so you need to create/load a driver with the tool Zadig, usage is quite easy, google is your friend.
Maybe a windows hacker can also provide a signed *.inf file for the dfu-util access, I got this from some helpful guys for one of my other projects, that is a native Linux program but also compiles and runs on MacOS and Windows:



As I'm currently on the road I have no access to my development system, so the git commands above are not tested but typed from my memory.
I will review my text and together with your findings we can possibly put a simple tinySA-hacker-howto either here or on GitHub.

What is the easiest way to find out where (and which branch) the latest code is ?
The development branch is currently "V4.3" since quite a long time, unfortunately Erik's default branch is still on "master". So you should always look at?


Happy hacking
Martin
Re: Clip on youtube with tinysa ULTRA on 10 gHz

 

Nice! The link is fine here...

I wish I had one of these in the 70s when I was using similar 10ghz gunn transceivers for transit vehicle beacon projects!

M
Re: and a small discone antenna

 

I built and tested several similar antennas similar to this one a few years back for use with Wireless microphone receivers. I used the NanoVNA for gain/SWR testing them (the TinySA didn't exist yet). They're almost impossible to get wrong!

I highly recommend the discone as an ?easy to build (other than the usual cautions about cutting your fingers!) and high performance wide band antenna. I still use a larger one in my attic crawl space for spectrum monitoring down to 50mhz and as a secondary transmitting antenna for local VHF/UHF repeater access...

The only tricky bit is getting the insulator/mounting point right - I never found a solution for this that was strong and easy to build repeatably - mine all ended up being "artisanal" one-off objects made out of scrap parts. Did you find a good solution for this?

M
Re: TinySA Ultra screen misaligned

 

On Thu, Dec 15, 2022 at 02:18 AM, KESAHZ wrote:
I am thinking the jogwheel is snagging the screen and pushing the right side down.
The jog wheel is on the back side of the PCB and the display on the front side so they can not touch.
The PCB is fixed in position with the 4 case screws so it can not move.
It is possible the jog wheel is touching the case. Loosening the 4 case screws a bit may help.
?
--
For more info on the tinySA go to https://tinysa.org/wiki/
Re: TinySA Ultra screen misaligned

 

My 2 week old TinySA developed this issue after a few uses. Is it just me or is it caused by using the jogwheel? I noticed that when selecting an option by pressing down on the jogwheel sometimes (when it is not fully returned to center, I think) it seems to give some resistance and you have to press down harder to get a response. I am thinking the jogwheel is snagging the screen and pushing the right side down. I haven't opened mine up yet so this is still a theory.
Re: A round of applause!

 

Really impressed by the TinySA family, unthinkable just a few years ago, and totally grateful for the involvement and quick support response. Congratulations Erik & team for your ingenious development and thank you very much for the happiness you have brought to hobbyists and professionals by providing us with affordable and reliable tools.

Thanks Erik!


P.S..Also, let's not forget the credit to the "hidden people never mentioned" who managed to create the little chips it is based on to get the job done.
Re: Clip on youtube with tinysa ULTRA on 10 gHz

 

Thanks, last week i did try the same with this:


Waveguide opening and black stamp on the back tells me X band.
I measured a nice curve when increasing the voltage.

But I could not find a trace with my homemade probe.
Will try again.

Sold my NOS 2k25's years ago.
Re: Oscilloscope needed if I have TinySA and NanovVNA?

 

¿ªÔÆÌåÓý

For troubleshooting and repair I prefer a fast reacting scope, like my old Tek 465. Also for its overload stability.

For adjustments, serial digital measurements and documentation I prefer my Picoscope.? In no way a scope can beat a PC based system in this fields. Including higher trace resolution, multiple traces in time and frequency domain, serial data timing and content analysis.

When doing measurements on live circuits I prefer my Tek THS720 handheld scope, because of its isolated channels.


All the Best,

Isidro



Am 15.12.2022 um 07:42 schrieb Jim Allyn - N7JA:

I'd go with the Siglent.? I have a Siglent SDS1104X-E.? Only 100 MHz, but four input channels.? I considered getting the 200 MHz version, but most of the time if I need to look at something above 100 MHz, the spectrum analyzer is my tool of choice, not the oscilloscope.? I also have a Siglent spectrum analyzer (besides a couple of tinySAs and a tinySA Ultra on order) and a Siglent function/arbitrary waveform generator.? When I bought these pieces of equipment I also looked at the Rigol and others in the same price range and concluded Siglent is definitely the way to go.

By the way, these oscilloscopes will also function as a spectrum analyzer by doing a Fast Fourier Transform on the captured data.? My 1104 is only 100 MHz analog bandwidth, but I am able to observe RF signals past 250 MHz in spectrum analyzer mode.? Sensitivity drops off above 100 MHz, of course, but 250 MHz signals are still easily displayed.
11101 - 11120 of 19631