Forum Replies Created
- Roger January 11, 2023 at 9:08 am in reply to: GNU Radio with BB60C
It looks like an outdated version of the Signal Hound BB60 GNU Radio module is being used. This could be either because the repository was cloned before GNU Radio 3.9 support was added in August 2022, or because the 3.7 maintenance branch is being used (maint-3.7). Swig is not used in 3.9, and those swig directories and makefiles do not exist in the current codebase.
To solve this, you can clone the current repository, pull the latest changes, or if your repo is up to date, checkout the master branch.
Let me know if you continue to have issues.
RogerRoger July 2, 2019 at 1:19 pm in reply to: API saGetSweep value units
The min and max arrays populated by saGetSweep_32f are 32-bit floating point numbers, not ints. So, use ct.c_float instead of ct.c_int in your array initializations.
RogerRoger April 15, 2019 at 11:57 am in reply to: LabVIEW App using Signal Hound VI's not working – Resource not found
I just replied to your email with some suggestions. Let me know what works and I will update it here.
RogerRoger November 1, 2018 at 9:56 am in reply to: Error compiling Linux sample code
Unfortunately I have not been able to reproduce the issue you are having, and the debug message is too general to point me to anything specific.
The fact that you are receiving the exact same error message on two completely different systems, one of which is the same that we test on (18.04 LTS), suggests to me that the issue lies somewhere in your configuration or installation process. In debugging I would focus on peculiar commonalities shared by your two environments.
Let me know if you get any more specific debugging feedback, or if you want to share output that shows your exact process / command sequence.
RogerRoger September 5, 2017 at 8:58 am in reply to: Interference hunting
That is correct, the Event List contains events that occurred during the last sweep.
Currently, all events are logged in realtime, so an ongoing event is logged repeatedly, after each sweep, with an increasing duration. This is to ensure the accuracy of the log at any given time, and to safeguard the data in the event of an accidental system shutdown. However, we have decided to change this functionality, in favor of having an ongoing event logged only once, either when the signal disappears or logging ends, with its final duration. This change will be in the next Spike update.
Let me know if you have more questions about interference hunting mode.
RogerRoger March 24, 2017 at 2:38 pm in reply to: About LavView vision API to measure Channel power question?
Hi Yu Ching,
I have created a new LabVIEW example for computing channel power. It is a modification of the continuous sweep example.
Let me know if you have any questions about it.
Attachments:You must be logged in to view attached files.