I have a freshly built GR 3.8.1.0-rc1 and GRC 3.8.1.0 on rPi.
A simple flowgraph of ZMQ PULL Message Source feeding a Message Debug
gives the following errors:
```
Executing: /usr/bin/python3 -u /home/pi/GRdev/msg_test.py
libEGL warning: DRI2: failed to authenticate
qt5ct: using qt5ct plugin
/home/pi/.gnuradio/prefs/vmcircbuf_default_factory: No such file or
directory
vmcircbuf_createfilemapping: createfilemapping is not available
gr::vmcircbuf_sysv_shm: shmat (2): Invalid argument
gr::vmcircbuf_sysv_shm: shmat (2): Invalid argument
gr::vmcircbuf_sysv_shm: shmat (2): Invalid argument
```
/home/pi/.gnuradio/prefs/vmcircbuf_default_factory contains:
gr::vmcircbuf_mmap_shm_open_factory
---
Barry Duggan KV4FV
On 2020-02-18 09:18, Michael Dickens wrote:
> GR's ZMQ should work across threads, processes, and networks; between
> GR
> and non-GR so long as the packet formatting is correct. I've used ZMQ
> between GR within a network, never done this between GR and non-GR
> though
> ... so maybe this is an aspiration rather than guarantee? - MLD
>
> On Mon, Feb 17, 2020 at 9:07 PM Barry Duggan <barry@dcsmail.net> wrote:
>
>> Hi,
>>
>> I would like to use one of the ZMQ source blocks (such as ZMQ PULL
>> Message Source) to communicate with a separate Python process. I have
>> been able to use various Python examples to test between processes,
>> but
>> when I try to use a GRC block, it fails. Are there restrictions which
>> prohibit data exchange outside the gnuradio realm?
>>
>> Thanks for your help.
>> --
>> Barry Duggan KV4FV
>>
>>
>
> --
> Michael Dickens
> Ettus Research Technical Support
> Email: support@ettus.com
> Web: https://ettus.com/
No comments:
Post a Comment