|
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?
Hi Lane,
toggle quoted message
Show quoted text
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:
My version:HEX2DFU tinySA.hex -out tinySA.dfu 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
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?
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. |
|
Re: tg
Thanks Eric,
You saved me some time there, I don't need a tracking generator for the ultra it would have been something to play with to see if it can be done nothing more. I build one for my R3465 that spans 10Khz to 8ghz but I find I use my VNA a lot more than the tracking generator.I have plenty of commercial gear to do what I need to do in my hobby shop or as my wife calls it my dungeon lol. And plenty of other project to kill time with. John |
|
Re: Oscilloscope needed if I have TinySA and NanovVNA?
Each is a different tool for different tasks and all three complement each other. IMO every bench should have at least one scope. In the past I have used a 2235 daily and found it to be a decent tool. I have also used some of the low end Tektronix digital scopes. From my experience the digital scopes are great for digital but I prefer analog scopes for looking at analog signals. The digital scopes I used tended to have a little bit of lag from the processing which annoyed me. Analog scopes are near instantaneous. I'm sure recent digital scopes are much faster, so YMMV as they say. I have a Tektronix 468 on my bench at the moment.
73 -Jim NU0C On Wed, 14 Dec 2022 15:53:03 -0800 "Steve Johnson" <cascadianroot@...> wrote: I'm just getting started in the hobby of experimenting with RF devices. I already have a NanoVNA and a TinySA Ultra (not out of the box yet though). In setting up my radio bench, what do you experts say about the need for an oscilloscope also? Will the devices I have cover most common needs or will I at some point wish for an oscilloscope also? |
|
Re: A round of applause!
¿ªÔÆÌåÓýTo show you how far we have come, I must show this picture again.? This is a spectrum analyzer I built for INTELSAT while I was working at COMSAT Labs in Maryland, circa 1970. Please note that there is a spectrum analyzer within a spectrum analyzer.? We built two of these monsters to measure satellite EIRP.? The computer was an HP 2116B with a whopping 16K of real ferrite core memory. Erik, you could do this with a TinySA now. ? Kind Regards, Dave Dave Reiser, WA3TRS ? From: [email protected] <[email protected]>
On Behalf Of K3RWN
Sent: Wednesday, December 14, 2022 6:18 PM To: [email protected] Subject: Re: [tinysa] A round of applause! ? AGREED!? Fantastic piece of equipment, both of them.? The ULTRA is great and filled with features I never thought possible! Thanks Erik! Rich On 12/14/2022 17:28 PM, THE BOSS via groups.io wrote:
|
W5CDT
Ho-Ro
Jim Allyn - N7JA
John Cunliffe W7ZQ
Jim Shorney
DAVE REISER WA3TRS
