The code for figuring out dependencies (expr_utils.py) is failing here,
I believe. That has been reported before and is on the list to be
rewritten (not very high prio though). In the meantime moving all the
probes to the end sounds like a good workaround (even though I usually
dislike
Hi
On 11/29/2016 07:37 PM, sumitstop wrote:
I have my custom build 802.11g transmitter connected to gr-ieee 802.11
receiver. Receiver decodes my data correctly and wireshark connector shows
that it is receiving valid packets with all the fields. gr-ieee 802.11 dumps
the decoded data in .pcap
Hi,
On 11/29/2016 10:09 PM, sumit kumar wrote:
Yes its strange ! Initially I thought some issue with my transmitter,
but wireshark doesn't show activity for gnuradio also.
I'm afraid I don't get it.
I think you should make sure to
- tune to the correct frequency/channel
Hello,
I have my custom build 802.11g transmitter connected to gr-ieee 802.11
receiver. Receiver decodes my data correctly and wireshark connector shows
that it is receiving valid packets with all the fields. gr-ieee 802.11 dumps
the decoded data in .pcap format and I see them by piping to
USRPs have a feature that will toggle GPIOs based on their Tx/Rx state.
Your device (if it's not a USRP) might have something similar.
Cheers,
M
On 11/28/2016 03:11 PM, Dan CaJacob wrote:
> This is possible. You'd write a custom block to do this. You could
> even do a simple POC with a python
This was really good information Seth, thanks. I tried the steps
Nicolas previously mentioned and I had the same problem. I ran your
commands and I see gnuradio-companion under the "disabled components" list.
Looking further up in the output, the thing I see different from your
list is that
I think you need a python-devel package installed. Exact name will be
distro dependent.
Philip
On 11/29/2016 09:34 AM, Jason Matusiak wrote:
> This was really good information Seth, thanks. I tried the steps
> Nicolas previously mentioned and I had the same problem. I ran your
> commands and I
