Inquiry About Component Order and Block Diagram for gr-iridium GNU Radio Module

[yangyaxun]

I am currently working on a project involving the gr-iridium GNU Radio module. First and foremost. I am reaching out to seek your expertise and clarification on a couple of points:

Operational Order of Components:
Specifically, I am trying to comprehend the sequence in which the following components operate within the gr-iridium flowgraph:
fft_channelizer_impl.cc
tagged_burst_to_pdu_impl.cc
Based on my analysis, it appears that fft_channelizer_impl.cc processes the incoming IQ samples first, channelizing them into multiple frequency bands, and subsequently, tagged_burst_to_pdu_impl.cc converts these channelized bursts into PDUs for downstream processing. Could you please confirm if this understanding is correct? Additionally, if there are any nuances or additional steps involved in their interaction, I would greatly appreciate your insights.

Comprehensive Block Diagram:
To enhance my understanding of the overall architecture and data flow within the gr-iridium module, I would like to request a complete block diagram of the module as implemented in the GNU Radio API. This visual representation would be invaluable in mapping out the interactions between various components and ensuring that I am aligning my development efforts with the intended design.

Thank you very much for your time and consideration. I look forward to your response.

[Kekorepeleco]

I can't speak for the people at the MUCCC, and I can't provide a block diagram, but this video might be helpful if you're looking to understand more about how gr-iridium works.

[yangyaxun]

Thanks for your response and providing the information.
Actually my biggest question is why the "d_channels" parameter is set to "d_channels(decimation + 1)" in fft_channelizer_impl.cpp function. And how to set the proper value of "decimation". Thanks again !

[Sec42]

That question is actually answered in the above linked video starting at around 38:20 or so.