I don't think so. ctrlport-monitor works fine.

On Wed, Jun 25, 2014 at 7:19 PM, Douglas Geiger <
[email protected]> wrote:

> How did you install GNURadio? The error suggests to me that performance
> counters were not enabled at compile time. There is some information about
> enabling performance counters on the wiki page:
> http://gnuradio.org/redmine/projects/gnuradio/wiki/PerformanceCounters
>
>  Good luck,
>   Doug
>
>
> On Wed, Jun 25, 2014 at 7:48 AM, Shashank Sinha <[email protected]>
> wrote:
>
>> I was trying to use gr-perf-monitorx while running Bastian's gr-ieee80211
>> project. I was encountering the following error :
>>
>> {
>>     unknown =
>> /home/harsha_sdr/.Repos/gnuradio/gnuradio-runtime/include/gnuradio/rpcserver_ice.h:119:
>> IceUtil::IllegalArgumentException: Ctrlport Key called with unregistered
>> key (ofdm_preamble0::output % full)
>>
>> I read about the possible reason for the error and updated
>> gnuradio-runtime.conf . It now stands as
>>
>> [DEFAULT]
>> verbose = False
>>
>> # The maximum number of messages a block will store up before pruning
>> # the queue by popping messages from the front.
>> max_messages = 100
>>
>>
>> [LOG]
>> # Levels can be (case insensitive):
>> #       DEBUG, INFO, WARN, TRACE, ERROR, ALERT, CRIT, FATAL, EMERG
>> log_level = debug
>> debug_level = emerg
>>
>> # These file names can either be 'stdout' to output to standard output
>> # or 'stderr' to output to standard error. Any other string will
>> # create a file in which to output the logging information. An empty
>> # string or no value here will ignore this level of configuration
>> # completely.
>> log_file = stdout
>> debug_file = stderr
>>
>> # Used for advanced configuration of the logger
>> #log_config = /usr/local/etc/gnuradio/gr_log_default.xml
>>
>>
>> [PerfCounters]
>> on = True
>> export = True
>> clock = thread
>> #clock = monotonic
>>
>> [ControlPort]
>> on = True
>> edges_list = True
>> config = # /usr/local/etc/gnuradio/ctrlport.conf
>>
>>
>> I am stilling facing the error , even after making the changes as
>> suggested on the Control Port usage page. Can someone explain what is going
>> wrong ?
>>
>> _______________________________________________
>> Discuss-gnuradio mailing list
>> [email protected]
>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>
>>
>
>
> --
> Doug Geiger
> [email protected]
>
_______________________________________________
Discuss-gnuradio mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Reply via email to