Hi Josh,
I've figure out the problem. I didn't check this:
https://github.com/guruofquality/grextras/commit/075bf6ec7e9f8169d9dee59fb9e74d13146b6ddb
where you changed this:
- pmt::pmt_dict_add(value_dict, TIME_KEY, timestamp);
+ value_dict = pmt::pmt_dict_add(value_dict, TIME_KEY, timestamp);
Hi Josh,
You mentioned that:
"the code to add a key/value actually returns a new dictionary and doesnt
change the old ones.
I know this pmt stuff is crazy. Why didnt we just use std::map? :-)"
I'm confused with this, because I created the dictionary and added the
values. However, when I've chec
Hi Josh,
Now it is running. Also, I add some lines into the uhd_amsg_source.cc file
for debugging purposes:
Just ordinary prints to see when the message is post and what kind of
message:
std::cout << std::endl << "interruption"< wrote:
> Hi Josh,
>
> I've changed the .xml file. Also, I've check
On 10/10/2012 07:16 PM, Jose Torres Diaz wrote:
> Hi Josh,
>
> I am very keen on this block (UHD_AMSG_SOURCE), because I saw that you post
> a dictionary downstream in this example. Thus, I would like to analyze how
> it works. I've tried to replicate your code in a different block, but I
> have
On 10/10/2012 06:35 PM, Jose Torres Diaz wrote:
> Hi Josh,
>
> I've changed the .xml file. Also, I've checked the new top_block.py file
> and it is generated as follows:
>
> self.extras_uhd_amsg_source_0 =
> gr_extras.uhd_amsg_source(uhd.device_addr="172.17.3.140"
>
> However, it is still comp
Hi Josh,
I am very keen on this block (UHD_AMSG_SOURCE), because I saw that you post
a dictionary downstream in this example. Thus, I would like to analyze how
it works. I've tried to replicate your code in a different block, but I
have some issues with the dictionary.
Here is my summary:
*Issue
Hi Josh,
I've changed the .xml file. Also, I've checked the new top_block.py file
and it is generated as follows:
self.extras_uhd_amsg_source_0 =
gr_extras.uhd_amsg_source(uhd.device_addr="172.17.3.140"
However, it is still complaining when I run the flow graph:
File "/home/asrpuser/Desktop/J
On 10/10/2012 06:09 PM, Jose Torres Diaz wrote:
> Hi Josh,
>
> Do you mean to change in the top_block.py?. I did this, but when I run
> again the top_block.py, it changes back to:
>
> gr_extras.uhd_amsg_source(device_addr="add=172.17.3.140")
>
> even if I try:
>
> gr_extras.uhd_amsg_source(uh
Hi Josh,
Do you mean to change in the top_block.py?. I did this, but when I run
again the top_block.py, it changes back to:
gr_extras.uhd_amsg_source(device_addr="add=172.17.3.140")
even if I try:
gr_extras.uhd_amsg_source(uhd.device_addr="add=172.17.3.140")
Thanks again Josh,
Regards,
Jose
On 10/10/2012 05:51 PM, Jose Torres Diaz wrote:
> Hi All,
>
> I'm checking the functionality of the block "UHD AMsg Source" using the
> USRP N210. The device is correctly detected as you can see:
>
> uhd_find_devices
> linux; GNU C++ version 4.6.1; Boost_104601; UHD_003.004.003-221-g9d6f9492
>
10 matches
Mail list logo
