|
Re: tg
A tracking Generator is possible to be build but not for low span and resolution. Whenever I go below 1Mhz span I see chopping of the trace even if the external source and the IF are within a few khz. I don't see this with the original. I have not had time to look at the LO output to see if it is a steady swept signal or if it is chopped /? stepped.?
John |
|
Re: New ULTRA FW release: Improved font and touch cal
¿ªÔÆÌåÓýHi The problem for when the menu system not access able after a touch calibration, is most probably when the upper left corner has been clicked twice (shaking fingers, or bouncing pointing device) then the jog wheel is the only tool to recover a proper touch calibration Kind regards Kurt ? ? Fra: [email protected] <[email protected]> P? vegne af pe1hwo ? Thanks Martin |
|
Re: New ULTRA FW release: Improved font and touch cal
Erik. I did the update and really had the problem with the touch, now we have to use the jog to access the menu and calibrate the touch. this is no problem for me, just letting you know.
?
Another thing. now that we have a big screen, the big number mode has a lot of space left over, wouldn't it be interesting for you to take advantage of this space and include the frequency as well? |
|
Re: #tinysa Power Reading
#tinysa
On Wed, Dec 14, 2022 at 10:12 AM, G8HUL wrote:
Most Pas are not 50 ohm, they are designed to give a specified power 'into* a 50 ohm load. Jeff,
?
That's right, impedance matching is necessary for sources that can only deliver a small amount of electrical power and whose power is to be passed on as comprehensively as possible. Such weak sources are, for example, antennas. With linear sources and sinks, in the best case only half of the available power is actually radiated; the efficiency is then 50 %. The other half is lost as power dissipation in the internal resistance of the source.
Electrical energy sources, e.g. a power station, but also a large PA - whether audio or high frequency - are therefore not designed for power matching, but for voltage matching (i.e. low source resistance); their nominal power would therefore be exceeded long before any (theoretical) power matching.
?
Martin
? |
|
Re: Which branch to use to compile the same firmware as Erik is releasing?
Erik,
The build instructions will build a version "v0.1-602-gb87733e" based on the deprecated "master" branch.
The most important info to be on track with your development is to type git checkout V4.3?before running make?(to build tinySA) or TARGET=F303 make?(to build tinySA4 aka. Ultra. Funny fact - at the moment you can set TARGET to every nonempty string to get the Ultra, also TARGET=F072 builds the Ultra version, see also my ). BUT this will give a different version name "v1.2-658-g65f6118" (the g65f6118 correctly refers to the last commit on branch V4.3, but the v1.2-656 is out of order). See also?.? My Q'n'D fix is to do this once after cloning: ? ? git tag -d v1.3
? ? git tag -a -m v1.3 v1.3 12a96bb This matches your versioning and gives?v1.3-558-g65f6118 (at the time of my writing, you haven't pushed your latest commit 9ebab38, which is the base for??- have you?). EDIT: I saw your two new commits, now GitHub is in front of your download page at version?v1.3-560-g88121a2. (real work in progress) I hope this sheds some light on the mysteries of creating your own versions. Martin |
Ho-Ro
Wander Lucio
John Cunliffe W7ZQ
Kurt Poulsen