Skip to content

A possible solution to the "module 'tempest'" error #38

@XieyangSun

Description

@XieyangSun

Hi,
I noticed that some issues mentioned that gr-tempest was successfully installed and compiled, but when running the example grc, there would be an error such as 'no module tempest' or other similar errors #10 . Although at the beginning, I also manually added the pythonpath following the instructions of others, it still couldn't solve all the errors reported.

Later, I checked the .py file generated by grc and found, as mentioned in #15 , that the automatically generated code would have an extra line of "import tempest". It is possible to manually delete this line and then execute it through the Python command line. However, it seems rather cumbersome (when running on GNU Radio, new.py code will always be regenerated).

I investigated the part of the code that caused the repeated import of tempest, and it seems to be due to the file grc/tempest_image_source.block.yml. My solution is to change "imports: import tempest" on Line 6 to "imports: from gnuradio import tempest", which will fix the issue.

In my subsequent experiments, running grc on gnuradio could operate normally and capture the eavesdropping scene. No similar errors occurred again.

I haven't tested all the grc examples provided by gr-tempest, but most of the issues that previously caused errors can be fixed in this way.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions