¿ªÔÆÌåÓý

Date
Tune a duplexer #features #file-notice
Can you use the TinySA Ultra to tune a duplexer?
By Anthony Dunn · #9602 ·
Re: Antenna Replacement? #tinysa #ultra
The short antenna doesn¡¯t work well below 10 MHz since the antenna¡¯s impedance is so much higher than the 50 ohm analyzer input Z. It¡¯s not practical to use a resonant antenna at low frequencies
By Richard Place · #9601 ·
Re: Marker 2 fq change #bug_report
Is all OK now? -- For more info on the tinySA go to https://tinysa.org/wiki/
By Erik Kaashoek · #9600 ·
Re: Marker 2 fq change #bug_report
I was still in the phase noise measurement mode what I'am did before, I just reconfigured the markers... Istv¨¢n
By Istv¨¢n · #9599 ·
Re: Antenna Replacement? #tinysa #ultra
Simply put, the dips in the green curves indicate the frequency at which the antenna is well matched. The frequency of the yellow curve is optimal where it is as close as possible to the centre of the
By Ho-Ro · #9598 ·
Re: File Notifications #file-notice
Excellent, David. Thanks a lot! -- -- 73! R4HDC
By R4HDC · #9597 ·
Re: File Notifications #file-notice
Thanks David,? great job. Mike C. Sand Mtn GA
By Mike C. · #9596 ·
Re: Spectrum segmented limit lines or mask #feature_request #ultra
It's possible. Not sure when -- For more info on the tinySA go to https://tinysa.org/wiki/
By Erik Kaashoek · #9595 ·
Re: Spectrum segmented limit lines or mask #feature_request #ultra
Erik, Thanks for detailed explanations! Would it? be possible to add some real-time spur events monitoring, something like generating a short audio beeps on audio output jack in case when a spur
By AlexSpb · #9594 ·
Re: Marker 2 fq change #bug_report
Thanks, I can replicate -- For more info on the tinySA go to https://tinysa.org/wiki/
By Erik Kaashoek · #9593 ·
Marker 2 fq change #bug_report
Hi Erik, the settings shown in the picture FW 1.4-40 start 0 stop 800Mhz (RBW:300 - just because slow down the scan..) - set 500 Mhz frequency to the marker 2 - after first scan, the marker 2 jump to
By Istv¨¢n · #9592 ·
Re: Antenna Replacement? #tinysa #ultra
Hello George, I can't really follow your logic, Let's say for instance you bought three tinasa, one goes faulty, are you really going to wreck a good one to repair the faulty one? Doesn't make much
By Kenneth Greenough · #9591 ·
Re: Spectrum segmented limit lines or mask #feature_request #ultra
Its already available. You can create something like this: using this trace table by enabling trace table which converts the selected trace into a frozen trace with the data coming from the table --
By Erik Kaashoek · #9590 ·
Re: Spectrum segmented limit lines or mask #feature_request #ultra
I also would like level limits o the display, since I purchased the Tinysa Ultra for EMC pre-compliance checks Mike
By Mike Ward · #9589 ·
Re: Display request
Will be in the next release -- For more info on the tinySA go to https://tinysa.org/wiki/
By Erik Kaashoek · #9588 ·
Re: Spectrum segmented limit lines or mask #feature_request #ultra
See TRACE/CALC/TRACE TABLE -- For more info on the tinySA go to https://tinysa.org/wiki/
By Erik Kaashoek · #9587 ·
Display request
Hello Erik. Very nice additions in every new version, thanks! Can you please make the 'preset' > 'store'?? show the frequencies already filling the slots (and not only store1 to store4). It helps in
By josephlevy · #9586 ·
Spectrum segmented limit lines or mask #feature_request #ultra
Hi, Erik, There had been a feature proposed earlier for TinySA to add a (segmented) limit lines on a display, which might be useful in case one needs to perform some spurs level limit tests (similar
By AlexSpb · #9585 ·
Re: #ultra #firmware_update #ultra #firmware_update
No, the new FW uses a new magic number as some of the internal data structure changed making the stored presets incompatible. -- For more info on the tinySA go to https://tinysa.org/wiki/
By Erik Kaashoek · #9584 ·
Re: TinySA ULTRA LEVEL CAL -> Signal Level incorrect #ultra
Masahiro-san Thanks for the excellent feedback. I will send this info to manufacturing for future improvements. The non zero leveloffset values are either in the firmware of measured during
By Erik Kaashoek · #9583 ·