Almazny test using TinySA #67
Reference in New Issue
Block a user
Delete Branch ":doc_improve"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
also closes #16
Please reencode the BMP screenshot into PNG. Minor, but still a waste of space and bandwidth.
The minry testing should also be using tinysa to skip changing out instrument.
@@ -112,6 +112,33 @@ After running `artiq_sinara_tester`:### With Almazny### With Almazny (ARTIQ 8+)@@ -115,0 +129,4 @@After running `artiq_sinara_tester` with Almazny installed, use TinySA Ultra to check the frequencies:1. Connect the TinySA Ultra's "RF" port to the Almazny output SMA ports.We should mention the use of an attenuator for input protection
I think the maximum output for almazny was about 0~1 dBm, TinySA could take +6 dBm at 0db internal att and 20 at 30 db internal att. Do you think external att is needed?
But it does mention "best measurement" at below -25 dBm: TinySA spec
Have you used any attenuation in your measurement? If not and the TinySA didn't get damaged then it's probably fine; on the other hand HackRF/BladeRF were more sensitive and they could take Almazny output w/o protection.
I already tried no attenuation, works fine.
I also tried a 15dB attenuator to see if it actually improve measurement accuracy, result: hard to tell, but I think not much, confirmed not much compression at high input power.
That's fine then - just so the testing equipment doesn't get damaged. For assembly testing accuracy or resolution isn't as important as seeing if the board works (signal present, no major noise). For datasheet measurements, it's of course another story.
IMO, adding an external att is best practices when plugging in any RF signal to a SA. Just like adding a DC block. You never know if the amp is working correct or not during testing.
Minor grammar mistake:
@@ -115,0 +133,4 @@2. Turn on the TinySA Ultra and set it to "Spectrum Analyzer" mode.3. Set the frequency range to cover the expected output (e.g., 6.8 GHz to 7.5 GHz).4. If the marker is not on the peak, click "Marker"->"Search Marker"->"Peak Search" to find the peak signal.5. Repeat 1-4 for other channelsae187cbf02toee67df6001LGTM, but the commit message needs to be fixed