Almazny test using TinySA #67

Merged
mwojcik merged 3 commits from :doc_improve into master 2026-01-16 17:11:56 +08:00
Contributor
No description provided.
bukehu added 1 commit 2026-01-16 13:05:39 +08:00
bukehu added 1 commit 2026-01-16 13:05:57 +08:00
Collaborator

also closes #16

also closes #16
Collaborator

Please reencode the BMP screenshot into PNG. Minor, but still a waste of space and bandwidth.

Please reencode the BMP screenshot into PNG. Minor, but still a waste of space and bandwidth.
morgan reviewed 2026-01-16 13:26:23 +08:00
morgan left a comment
Member

The minry testing should also be using tinysa to skip changing out instrument.

The minry testing should also be using tinysa to skip changing out instrument.
@@ -112,6 +112,33 @@ After running `artiq_sinara_tester`:
![Mirny GQRX example](../img/mirny_gqrx.png)
### With Almazny
Member

### With Almazny (ARTIQ 8+)

`### With Almazny (ARTIQ 8+)`
bukehu marked this conversation as resolved
@@ -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.
Member

We should mention the use of an attenuator for input protection

We should mention the use of an attenuator for input protection
Author
Contributor

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

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](https://tinysa.org/wiki/pmwiki.php?n=TinySA4.Specification)
Collaborator

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.

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.
Author
Contributor

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.

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.
Collaborator

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.

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.
Member

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.

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.
Collaborator

Minor grammar mistake:

channel 0 output SMA ports.

Minor grammar mistake: > channel 0 output SMA port**s**.
bukehu marked this conversation as resolved
@@ -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.
Member

5. Repeat 1-4 for other channels

`5. Repeat 1-4 for other channels`
bukehu marked this conversation as resolved
bukehu added 1 commit 2026-01-16 15:42:45 +08:00
bukehu added 1 commit 2026-01-16 16:02:22 +08:00
bukehu requested review from morgan 2026-01-16 16:03:16 +08:00
bukehu added 1 commit 2026-01-16 16:48:43 +08:00
bukehu added 1 commit 2026-01-16 16:54:18 +08:00
bukehu force-pushed doc_improve from ae187cbf02 to ee67df6001 2026-01-16 17:06:14 +08:00 Compare
Member

LGTM, but the commit message needs to be fixed

LGTM, but the commit message needs to be fixed
mwojcik merged commit b2b3e765bd into master 2026-01-16 17:11:56 +08:00
Sign in to join this conversation.
No Reviewers
No Label
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sinara-hw/assembly#67