One more I forgot:

5.? Red power light? -- does this indicate charge state or just an indication the unit is plugged in to a power source?? Does it go off after unit is fully charged?
--

Steve Johnson

? ? ? K0OIL

I purchased an Ultra the first week it was available, but held off until today unpacking it to wait for the firmware updates to stabilize.? Anyway, I updated the firmware to latest today and have some notes that, if added to would maybe make it easier for other new users.

1. The First Use page doesn't mention the Ultra as a distinct product.? It would be good to say something like "The TinySA Ultra is an advanced model of the TinySA and the instructions below apply to it as well as the original TinySA model."? (I'm assuming here a "First Use" page dedicated to the Ultra doesn't exist.)
2. Specify how to enter the DFU mode with the Ultra. Some older files on groups.io point to a DFU mode menu item that doesn't seem to exist anymore. I suggest adding "Update the Firmware" to the list of steps following "Execute these steps: "
3. Mention that in firmware file names "tinySA4..." refers to Ultra firmware and "tinySA..." refers to firmware appropriate for the original model.
4. Mention that after a firmware update and fresh configuration the resulting config is saved automatically between power-ups. No need to redo this each time, and no need to save to the SD card or one of the Preset save slots.
--

Steve Johnson

? ? ? K0OIL

Please remember the tinySA has a 30dB step attenuator so anything between -20 and 0 dB is ok
--

The trace colours are orthogonal to the bands. The bands are separated with vertical blue lines

Would it be possible to use two alternating colors for the trace so that the bands can be seen more easily?

--

W0LEV

I did read your post two times trying find something related to my question. I see your point… but did you forget or by accident send to early and forgot the answer to thread question? Just checking..

Martin,

thank you for your explanation :)
73,

Another suggestion, as a workaround for a shrinked display issue with multiple bands, might be just to implement a double-click on screen to expand/collapse back the band of interest to full screen/ splitted display.
This might solve the screen size limitations

On Sun, Feb 26, 2023 at 09:48 AM, hwalker wrote:

?Given the limited real estate at the bottom of the screen, perhaps you could get rid of the START, per/div, and STOP annotations and replace them with centered annotations for each band (i.e., 9.9 - 10.1MHz | 19.9 - 20.1MHz in your example) when using the multi band scanning mode.? Between centered band annotations and frequency markers placed by the user, the display should be easier to interpret without becoming too cluttered.

Good suggestion
?
--

On Sun, Feb 26, 2023 at 09:05 AM, Terry Perdue wrote:

Your example display seams hard to interpret - especially since the frequency per division readout will be wrong. The display of even just four bands simultaneously would be confusing.?

开云体育

On 25/02/2023 16:36, Isidro Berniol wrote:

Hello,
Acrobat is a big and ugly tool.
PdfXchenge? Viewer ist much more easy, aller, faster, and better in any acpect I know.
All the Best,
Isidro

Thanks, I will take a look.

David
--
SatSignal Software - Quality software for you
Web:
Email: david-taylor@...
Twitter: @gm8arv

Yes. I first tried a transformer and it worked, but not as well as the emitter-follower. ?I wound a 10:1 turns-ratio autotransformer on a rectangular core, one of those with a pair of long cylindrical holes in them. ?The ferrite was #43 mix, 1" x 0.75" x 0.375". ?It worked pretty well from 1 to 3.5 MHz. ?Beyond that range there was either too little iron or too much capacitance. ?

I see four options:

1. Equal amount of display points for each active band
2. Amount of display points relative to band span share versus total band span.
3. Amount of display points relative to band span/RBW share versus total band span/RBW, this gives equal information over total span.
4. Manual setting of the % of display points per band

I prefer not to implement all options......
2 and 4 are my favourite as 2 is already implemented and 4 covers any crazy use case people can think of.
--

On Sun, Feb 26, 2023 at 05:08 AM, Erik Kaashoek wrote:

Till now I'v give each band the display points equal to its share of span. When each band has a different RBW (which is possible to implement) the amount of points will have to be split base on span AND RBW to ensure equal information density in each segment/band

Erik,
? Does that mean that if 3 bands are selected then a complete sweep will be performed for each band, but the final composite display will consist of the top 450/3 points for each band?

Herb

Till now I'v give each band the display points equal to its share of span. When each band has a different RBW (which is possible to implement) the amount of points will have to be split base on span AND RBW to ensure equal information density in each segment/band
--

On Sun, Feb 26, 2023 at 02:47 AM, Erik Kaashoek wrote:

....This will allow the usage of a low RBW to scan the relation between strong signals and very weak signals such as harmonics without having a very long sweep time

? ?The mult-band scanning looks very useful Erik.? I expected it to be under the "FREQUENCY" menu, but the "MEASURE" menu also works.? Any chance in the future of also adding the option of manually specifying the RBW for each band? Some test standards require multiple frequency bands with different RBW's for each band (i.e., 30-200MHz @ 10kHz RBW and 200-1000MHz @ 100kHz). Being able to display the continuous 30 -1000MHz range using multiband scanning at the specified RBW's would be a neat feature.

Herb

开云体育

This is how it will look.



This will allow the usage of a low RBW to scan the relation between strong signals and very weak signals such as harmonics without having a very long sweep time
--

All in one sweep is under development