[Discuss-gnuradio] simple mod-demod combinations doesn't work

[MarkO]

Hi everyone,

I currently use GRC 3.7.9.1 and only its In-Tree-Modules.
PC:  Lenovo Laptop W530
CPU: Intel i7-3610QM with 8GB RAM
OS:  Ubuntu 16.04 64 bit

I tried to create some easy examples of different modems. My first goal is
to modulate ASCII- or WAV-files, add some noise, demodulate the data stream
and save or hear the expected result. Maybe I am wrong, but i expect an
lossless connection in GRC if I directly connect an modulator to its
appropriate demodulator - particularly when i use the default values.

The issue is, even without added noise it's not possible to get an lossless
connection in software.

My Flow-Graph looks like this:

Wav File Source --> Float to Char --> QAM Mod --> Throttle --> QAM Demod -->
Pack K Bits --> Char to Float --> Audio Sink

I use [Float to Char] to reduce data and get a byte-stream. Of course this
loss of data isn't reconstructable.
But the incoming signal at the [Audio Sink] sounds extreme noisy and clips
massively.
It is also a little bit random how bad it is - at one start i can hear what
song it is, at the next start it's just noise.

I think i can say that the Problem is the mod-demod part:
  --> QAM Mod --> Throttle --> QAM Demod --> Pack K Bits -->
because this:
  Wav File Source --> Float to Char --> Char to Float --> Audio Sink  
works pretty well.

I attached the GRC file with the different modems to this thread. Of course
only one Mod-Demod string can be active at a time.
The results are commented with [Notes] in the GRC file. I also tried every
modulation with reduced data rate (usage of down- and upsampling).

I would be deeply greatful if someone may explain me my fallacy or how it
would just work - especially for the QAM modulation mentioned at the
beginning.

Regards,
Markus

different_MODEMs_audio_test.grc
  



--
View this message in context: 
http://gnuradio.4.n7.nabble.com/simple-mod-demod-combinations-doesn-t-work-tp61674.html
Sent from the GnuRadio mailing list archive at Nabble.com.

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Paid Project: Need a gnuradio BPSK/QPSK receiver for satellite modem data

[Dan CaJacob]

Hi Chris,

I've been using GNURadio for sat comm like this for a while, as have
others.  It's a great tool for the job!  To be frank though, this is more
than a $500 hit job.  Good luck in your search.

- Dan

On Fri, Oct 7, 2016 at 5:45 PM Chris Cook  wrote:

> I have a project that requires a gnu radio receiver that can receive,
> demodulate, and decode BPSK and QPSK data coming from a satellite modem.
> The modem also has FEC that will need to be handled.
>
> I can provide remote access to our lab machine that has a USRP connected
> to our modem for testing.
>
> I am willing to pay $500 USD for a solution.
>
> Please let me know if you’re interested and we can move the conversation
> offline.
>
> Thank You,
> Chris
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
-- 
Very Respectfully,

Dan CaJacob
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] UHD/gnuradio on CentOS 7 install problems

[Marcus Müller]

Hi Chad,

So, I've went ahead and built a refreshed uhd RPM for CentOS 7. I really
haven't had a chance to test it (and it's getting all kinds of late
around here), but if you'd like to try yourself:

https://gist.github.com/133daf964cdf947587bc6bcd303b85aa

The binary file you're looking for is probably
uhd-3.10.0.0-5.el7.centos.x86_64.rpm ; things are still uploading, so
please have another couple of minutes patience; the -devel package, as
usual, contains the headers etc.

Best regards,
Marcus

On 07.10.2016 20:16, Marcus Müller wrote:
>
> So, I just tried building UHD through pybombs, which had its
> strangenesses, but worked out.
>
> Which also means that you should be able to install it from source
> manually without pybombs. I'm currently doing a pybombs --prefix
> /home/gruser/prefix install gnuradio, after having removed
> apache-thrift from
> /home/gruser/.pybombs/recipes/gr-recipes/gnuradio.lwr; I'll report back.
>
> Best regards,
>
> Marcus
>
>
> On 07.10.2016 18:09, Marcus Müller wrote:
>>
>> Hi Chad
>>
>>> Is it the consensus of the group is that UHD/gnuradio is not installable
>>> on CentOS 7?
>> No. It should be. In fact, I've built it once, but that was a while
>> back, but I don't remember UHD giving me much trouble.
>>
>> I'll try again later today, please stand by.
>>
>> Best regards,
>> Marcus
>>
>> On 07.10.2016 17:53, Chad Spooner wrote:
>>> All I really need in the short term is UHD on CentOS 7.
>>>
>>> Is it the consensus of the group is that UHD/gnuradio is not installable
>>> on CentOS 7? I haven't seen any suggestions about the python-zmq
>>> problem below.
>>>
>>> Chad
>>>
>>>
>>> On Wed, 2016-10-05 at 10:34 -0700, Chad M. Spooner wrote:

 Martin, Marcus: Thanks for the helpful replies.

 All: I think I messed up on subscribing to the mail list by
 selecting Digest, and I've tried to undo that. For now, I have to
 reply to the Digest I got this morning.

 I updated the recipes as suggested, and did a new installation. The
 first error was that somehow QT 4 was not in my (root's) path, QT
 3.3 was, so I fixed that. (The symptom was that 'qmake' was not
 found by the installer.)

 Then I did another install and got to the point where the installer
 wants to install python-zmq:

 checking whether g++ supports C++11 features with -std=c++11... yes
 ./configure: line 17775: syntax error near unexpected token `QT,'
 ./configure: line 17775: ` PKG_CHECK_MODULES(QT, QtCore >= 4.3,
 QtNetwork >= 4.3, have_qt=yes, have_qt=no)'
 PyBOMBS.Packager.source - ERROR - Configuration failed after
 running at least twice.
 PyBOMBS.Packager.source - ERROR - Problem occurred while building
 package apache-thrift:
 Configuration failed
 PyBOMBS.PackageManager - WARNING - Optional package apache-thrift
 failed to install.
 PyBOMBS.install_manager - INFO - Installation successful.
 PyBOMBS.install_manager - INFO - Installing package: liblog4cpp
 00549 kB / 00549 kB (100%)
 Configuring: (100%)
 []
 Building: (100%)
 []
 Installing: (100%)
 []
 PyBOMBS.install_manager - INFO - Installation successful.
 PyBOMBS.install_manager - INFO - Installing package: zeromq
 02084 kB / 02084 kB (100%)
 Configuring: (100%)
 []
 Building: (100%)
 []
 Installing: (100%)
 []
 PyBOMBS.install_manager - INFO - Installation successful.
 PyBOMBS.install_manager - INFO - Installing package: python-zmq
 PyBOMBS.Packager.source - WARNING - Cannot find a source URI for
 package python-zmq
 PyBOMBS.install_manager - ERROR - Error installing package
 python-zmq. Aborting.

 Chad

 On 2016-10-05 09:00, discuss-gnuradio-requ...@gnu.org wrote:

> Send Discuss-gnuradio mailing list submissions to
> discuss-gnuradio@gnu.org 
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> or, via email, send a message with subject or body 'help' to
> discuss-gnuradio-requ...@gnu.org
> 
>
> You can reach the person managing the list at
> discuss-gnuradio-ow...@gnu.org
> 
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Discuss-gnuradio 

[Discuss-gnuradio] Paid Project: Need a gnuradio BPSK/QPSK receiver for satellite modem data

[Chris Cook]

I have a project that requires a gnu radio receiver that can receive,
demodulate, and decode BPSK and QPSK data coming from a satellite modem.
The modem also has FEC that will need to be handled.

I can provide remote access to our lab machine that has a USRP connected to
our modem for testing.

I am willing to pay $500 USD for a solution.

Please let me know if you’re interested and we can move the conversation
offline.

Thank You,
Chris
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Polyphase Clock Sync for Bursts

[Garver, Paul W]

So is that what the time_est tag in corr_est_cc is for? The idea being 
correlate against the preamble to generate an initial timing estimate for the 
clock recovery to lock quickly? 

PWG
> On Oct 7, 2016, at 3:37 PM, Sylvain Munaut <246...@gmail.com> wrote:
> 
>> Does anyone have insight into how to do burst timing recovery
>> with PF clock sync block? I’ll also note it appears that the M clock sync
>> block experiences a similar problem.
> 
> Both blocks are meant for continuous signal and will take a "while" to lock.
> 
> Usually for bursts, you have a sync sequence to correlate to to get an
> initial valid alignement.
> 
> Cheers,
> 
>Sylvain

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] UHD/gnuradio on CentOS 7 install problems

[Anon Lister]

For what it's worth, I have both working fine on a c7 box here, I did it
from source though, not through pybombs. I had to build a couple packages,
such as boost, but it definitely can be done, at least as of a few months
ago.

On Oct 7, 2016 11:55 AM, "Chad Spooner"  wrote:

> All I really need in the short term is UHD on CentOS 7.
>
> Is it the consensus of the group is that UHD/gnuradio is not installable
> on CentOS 7? I haven't seen any suggestions about the python-zmq
> problem below.
>
> Chad
>
>
> On Wed, 2016-10-05 at 10:34 -0700, Chad M. Spooner wrote:
>
> Martin, Marcus: Thanks for the helpful replies.
>
> All: I think I messed up on subscribing to the mail list by selecting
> Digest, and I've tried to undo that. For now, I have to reply to the Digest
> I got this morning.
>
> I updated the recipes as suggested, and did a new installation. The first
> error was that somehow QT 4 was not in my (root's) path, QT 3.3 was, so I
> fixed that. (The symptom was that 'qmake' was not found by the installer.)
>
> Then I did another install and got to the point where the installer wants
> to install python-zmq:
>
> checking whether g++ supports C++11 features with -std=c++11... yes
> ./configure: line 17775: syntax error near unexpected token `QT,'
> ./configure: line 17775: ` PKG_CHECK_MODULES(QT, QtCore >= 4.3, QtNetwork
> >= 4.3, have_qt=yes, have_qt=no)'
> PyBOMBS.Packager.source - ERROR - Configuration failed after running at
> least twice.
> PyBOMBS.Packager.source - ERROR - Problem occurred while building package
> apache-thrift:
> Configuration failed
> PyBOMBS.PackageManager - WARNING - Optional package apache-thrift failed
> to install.
> PyBOMBS.install_manager - INFO - Installation successful.
> PyBOMBS.install_manager - INFO - Installing package: liblog4cpp
> 00549 kB / 00549 kB (100%)
> Configuring: (100%) [=
> ===]
> Building: (100%) [=
> ===]
> Installing: (100%) [=
> ===]
> PyBOMBS.install_manager - INFO - Installation successful.
> PyBOMBS.install_manager - INFO - Installing package: zeromq
> 02084 kB / 02084 kB (100%)
> Configuring: (100%) [=
> ===]
> Building: (100%) [=
> ===]
> Installing: (100%) [=
> ===]
> PyBOMBS.install_manager - INFO - Installation successful.
> PyBOMBS.install_manager - INFO - Installing package: python-zmq
> PyBOMBS.Packager.source - WARNING - Cannot find a source URI for package
> python-zmq
> PyBOMBS.install_manager - ERROR - Error installing package python-zmq.
> Aborting.
>
> Chad
>
> On 2016-10-05 09:00, discuss-gnuradio-requ...@gnu.org wrote:
>
> Send Discuss-gnuradio mailing list submissions to
> discuss-gnuradio@gnu.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> or, via email, send a message with subject or body 'help' to
> discuss-gnuradio-requ...@gnu.org
>
> You can reach the person managing the list at
> discuss-gnuradio-ow...@gnu.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Discuss-gnuradio digest..."
>
>
> Today's Topics:
>
>1. Replacement for packet encoder/decoder (Damindra Bandara)
>2. Re: Block Thread question (Marcus M?ller)
>3. Re: Block Thread question (Garver, Paul W)
>4. Re: Fwd: Correlation Estimator in 3.7.10 (devin kelly)
>5. Re: Fwd: Correlation Estimator in 3.7.10 (Steven Knudsen)
>6. UHD/gnuradio on CentOS 7 install problems (Chad M. Spooner)
>7. Re: UHD/gnuradio on CentOS 7 install problems (Marcus M?ller)
>8. Re: UHD/gnuradio on CentOS 7 install problems (Martin Braun)
>
>
> --
>
> Message: 1
> Date: Tue, 4 Oct 2016 12:40:10 -0400
> From: Damindra Bandara 
> To: discuss-gnuradio@gnu.org
> Subject: [Discuss-gnuradio] Replacement for packet encoder/decoder
> Message-ID:
> 

Re: [Discuss-gnuradio] Polyphase Clock Sync for Bursts

[Sylvain Munaut]

> Does anyone have insight into how to do burst timing recovery
> with PF clock sync block? I’ll also note it appears that the M clock sync
> block experiences a similar problem.

Both blocks are meant for continuous signal and will take a "while" to lock.

Usually for bursts, you have a sync sequence to correlate to to get an
initial valid alignement.

Cheers,

Sylvain

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] Polyphase Clock Sync for Bursts

[Garver, Paul W]

 I want to use the polyphase clock sync block to match filter and clock sync on 
a bursty signal. The pulse shape is basically square, but from our discussion 
[1], providing RRC taps works pretty well.  I have snippets (~20k samples) of 
the signal from an energy detector, which contain the burst plus a little noise 
/ other signals on either side. When I set the file source to repeat, the 
output of the polyphase clock sync block looks beautiful. However, if I only 
run for a single loop through the file, the output isn’t correct. I’ve tried 
increasing the gain, which appears to give nice output on the second file 
repeat instead of the 3rd or 4th, but still that’s not good enough. Does anyone 
have insight into how to do burst timing recovery with PF clock sync block? 
I’ll also note it appears that the M clock sync block experiences a similar 
problem.

PWG

[1] https://lists.gnu.org/archive/html/discuss-gnuradio/2016-10/msg4.html
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] UHD/gnuradio on CentOS 7 install problems

[Marcus Müller]

So, I just tried building UHD through pybombs, which had its
strangenesses, but worked out.

Which also means that you should be able to install it from source
manually without pybombs. I'm currently doing a pybombs --prefix
/home/gruser/prefix install gnuradio, after having removed apache-thrift
from /home/gruser/.pybombs/recipes/gr-recipes/gnuradio.lwr; I'll report
back.

Best regards,

Marcus


On 07.10.2016 18:09, Marcus Müller wrote:
>
> Hi Chad
>
>> Is it the consensus of the group is that UHD/gnuradio is not installable
>> on CentOS 7?
> No. It should be. In fact, I've built it once, but that was a while
> back, but I don't remember UHD giving me much trouble.
>
> I'll try again later today, please stand by.
>
> Best regards,
> Marcus
>
> On 07.10.2016 17:53, Chad Spooner wrote:
>> All I really need in the short term is UHD on CentOS 7.
>>
>> Is it the consensus of the group is that UHD/gnuradio is not installable
>> on CentOS 7? I haven't seen any suggestions about the python-zmq
>> problem below.
>>
>> Chad
>>
>>
>> On Wed, 2016-10-05 at 10:34 -0700, Chad M. Spooner wrote:
>>>
>>> Martin, Marcus: Thanks for the helpful replies.
>>>
>>> All: I think I messed up on subscribing to the mail list by
>>> selecting Digest, and I've tried to undo that. For now, I have to
>>> reply to the Digest I got this morning.
>>>
>>> I updated the recipes as suggested, and did a new installation. The
>>> first error was that somehow QT 4 was not in my (root's) path, QT
>>> 3.3 was, so I fixed that. (The symptom was that 'qmake' was not
>>> found by the installer.)
>>>
>>> Then I did another install and got to the point where the installer
>>> wants to install python-zmq:
>>>
>>> checking whether g++ supports C++11 features with -std=c++11... yes
>>> ./configure: line 17775: syntax error near unexpected token `QT,'
>>> ./configure: line 17775: ` PKG_CHECK_MODULES(QT, QtCore >= 4.3,
>>> QtNetwork >= 4.3, have_qt=yes, have_qt=no)'
>>> PyBOMBS.Packager.source - ERROR - Configuration failed after running
>>> at least twice.
>>> PyBOMBS.Packager.source - ERROR - Problem occurred while building
>>> package apache-thrift:
>>> Configuration failed
>>> PyBOMBS.PackageManager - WARNING - Optional package apache-thrift
>>> failed to install.
>>> PyBOMBS.install_manager - INFO - Installation successful.
>>> PyBOMBS.install_manager - INFO - Installing package: liblog4cpp
>>> 00549 kB / 00549 kB (100%)
>>> Configuring: (100%)
>>> []
>>> Building: (100%)
>>> []
>>> Installing: (100%)
>>> []
>>> PyBOMBS.install_manager - INFO - Installation successful.
>>> PyBOMBS.install_manager - INFO - Installing package: zeromq
>>> 02084 kB / 02084 kB (100%)
>>> Configuring: (100%)
>>> []
>>> Building: (100%)
>>> []
>>> Installing: (100%)
>>> []
>>> PyBOMBS.install_manager - INFO - Installation successful.
>>> PyBOMBS.install_manager - INFO - Installing package: python-zmq
>>> PyBOMBS.Packager.source - WARNING - Cannot find a source URI for
>>> package python-zmq
>>> PyBOMBS.install_manager - ERROR - Error installing package
>>> python-zmq. Aborting.
>>>
>>> Chad
>>>
>>> On 2016-10-05 09:00, discuss-gnuradio-requ...@gnu.org wrote:
>>>
 Send Discuss-gnuradio mailing list submissions to
 discuss-gnuradio@gnu.org 

 To subscribe or unsubscribe via the World Wide Web, visit
 https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
 or, via email, send a message with subject or body 'help' to
 discuss-gnuradio-requ...@gnu.org
 

 You can reach the person managing the list at
 discuss-gnuradio-ow...@gnu.org
 

 When replying, please edit your Subject line so it is more specific
 than "Re: Contents of Discuss-gnuradio digest..."


 Today's Topics:

1. Replacement for packet encoder/decoder (Damindra Bandara)
2. Re: Block Thread question (Marcus M?ller)
3. Re: Block Thread question (Garver, Paul W)
4. Re: Fwd: Correlation Estimator in 3.7.10 (devin kelly)
5. Re: Fwd: Correlation Estimator in 3.7.10 (Steven Knudsen)
6. UHD/gnuradio on CentOS 7 install problems (Chad M. Spooner)
7. Re: UHD/gnuradio on CentOS 7 install problems (Marcus M?ller)
8. Re: UHD/gnuradio on CentOS 7 install problems (Martin Braun)


 --

[Discuss-gnuradio] CCSDS 27 implementation specifics

[Hrishikesh Shelar]

Hi all,

I was taking a closer look into the CCSDS 27 blocks and noticed that the
polynomials may be wrong?

The viterbi.c code says NASA code which has the polynomials 0x6D and 0x4F.
However CCSDS is ordered 0x4F followed by 0x6D with an inversion on the
0x6D output. I see that the butterfly cells are hard coded to the NASA
code. Would the fix be to recompute those ACS metrics and recompile that
block?

Also I think the viterbi algorithm as coded cannot perform node
synchronization. When I created a flow graph feeding the CCSDS 27 Encoder
into the CCSDS 27 Decoder adding a delay of 1 causes the output to fail (or
be erroneous). Is this expected?

Thanks!
Hrishi
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] UHD/gnuradio on CentOS 7 install problems

[Marcus Müller]

Hi Chad

> Is it the consensus of the group is that UHD/gnuradio is not installable
> on CentOS 7?

No. It should be. In fact, I've built it once, but that was a while
back, but I don't remember UHD giving me much trouble.

I'll try again later today, please stand by.

Best regards,
Marcus

On 07.10.2016 17:53, Chad Spooner wrote:
> All I really need in the short term is UHD on CentOS 7.
>
> Is it the consensus of the group is that UHD/gnuradio is not installable
> on CentOS 7? I haven't seen any suggestions about the python-zmq
> problem below.
>
> Chad
>
>
> On Wed, 2016-10-05 at 10:34 -0700, Chad M. Spooner wrote:
>>
>> Martin, Marcus: Thanks for the helpful replies.
>>
>> All: I think I messed up on subscribing to the mail list by selecting
>> Digest, and I've tried to undo that. For now, I have to reply to the
>> Digest I got this morning.
>>
>> I updated the recipes as suggested, and did a new installation. The
>> first error was that somehow QT 4 was not in my (root's) path, QT 3.3
>> was, so I fixed that. (The symptom was that 'qmake' was not found by
>> the installer.)
>>
>> Then I did another install and got to the point where the installer
>> wants to install python-zmq:
>>
>> checking whether g++ supports C++11 features with -std=c++11... yes
>> ./configure: line 17775: syntax error near unexpected token `QT,'
>> ./configure: line 17775: ` PKG_CHECK_MODULES(QT, QtCore >= 4.3,
>> QtNetwork >= 4.3, have_qt=yes, have_qt=no)'
>> PyBOMBS.Packager.source - ERROR - Configuration failed after running
>> at least twice.
>> PyBOMBS.Packager.source - ERROR - Problem occurred while building
>> package apache-thrift:
>> Configuration failed
>> PyBOMBS.PackageManager - WARNING - Optional package apache-thrift
>> failed to install.
>> PyBOMBS.install_manager - INFO - Installation successful.
>> PyBOMBS.install_manager - INFO - Installing package: liblog4cpp
>> 00549 kB / 00549 kB (100%)
>> Configuring: (100%)
>> []
>> Building: (100%)
>> []
>> Installing: (100%)
>> []
>> PyBOMBS.install_manager - INFO - Installation successful.
>> PyBOMBS.install_manager - INFO - Installing package: zeromq
>> 02084 kB / 02084 kB (100%)
>> Configuring: (100%)
>> []
>> Building: (100%)
>> []
>> Installing: (100%)
>> []
>> PyBOMBS.install_manager - INFO - Installation successful.
>> PyBOMBS.install_manager - INFO - Installing package: python-zmq
>> PyBOMBS.Packager.source - WARNING - Cannot find a source URI for
>> package python-zmq
>> PyBOMBS.install_manager - ERROR - Error installing package
>> python-zmq. Aborting.
>>
>> Chad
>>
>> On 2016-10-05 09:00, discuss-gnuradio-requ...@gnu.org wrote:
>>
>>> Send Discuss-gnuradio mailing list submissions to
>>> discuss-gnuradio@gnu.org 
>>>
>>> To subscribe or unsubscribe via the World Wide Web, visit
>>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>> or, via email, send a message with subject or body 'help' to
>>> discuss-gnuradio-requ...@gnu.org
>>> 
>>>
>>> You can reach the person managing the list at
>>> discuss-gnuradio-ow...@gnu.org
>>> 
>>>
>>> When replying, please edit your Subject line so it is more specific
>>> than "Re: Contents of Discuss-gnuradio digest..."
>>>
>>>
>>> Today's Topics:
>>>
>>>1. Replacement for packet encoder/decoder (Damindra Bandara)
>>>2. Re: Block Thread question (Marcus M?ller)
>>>3. Re: Block Thread question (Garver, Paul W)
>>>4. Re: Fwd: Correlation Estimator in 3.7.10 (devin kelly)
>>>5. Re: Fwd: Correlation Estimator in 3.7.10 (Steven Knudsen)
>>>6. UHD/gnuradio on CentOS 7 install problems (Chad M. Spooner)
>>>7. Re: UHD/gnuradio on CentOS 7 install problems (Marcus M?ller)
>>>8. Re: UHD/gnuradio on CentOS 7 install problems (Martin Braun)
>>>
>>>
>>> --
>>>
>>> Message: 1
>>> Date: Tue, 4 Oct 2016 12:40:10 -0400
>>> From: Damindra Bandara >> >
>>> To: discuss-gnuradio@gnu.org 
>>> Subject: [Discuss-gnuradio] Replacement for packet encoder/decoder
>>> Message-ID:
>>> 

Re: [Discuss-gnuradio] UHD/gnuradio on CentOS 7 install problems

[Chad Spooner]

All I really need in the short term is UHD on CentOS 7.

Is it the consensus of the group is that UHD/gnuradio is not
installable
on CentOS 7? I haven't seen any suggestions about the python-zmq
problem below.

Chad


On Wed, 2016-10-05 at 10:34 -0700, Chad M. Spooner wrote:
> > > > > > > > > 
> Martin, Marcus: Thanks for the helpful replies.

> All: I think I messed up on subscribing to the mail list by selecting Digest, 
> and I've tried to undo that. For now, I have to reply to the Digest I got 
> this morning.

> I updated the recipes as suggested, and did a new installation. The first 
> error was that somehow QT 4 was not in my (root's) path, QT 3.3 was, so I 
> fixed that. (The symptom was that 'qmake' was not found by the installer.)

> Then I did another install and got to the point where the installer wants to 
> install python-zmq:

> > > > > > > > > > > > > > > > > > > > > > > checking whether g++ supports 
> > > > > > > > > > > > > > > > > > > > > > > C++11 features with -std=c++11... 
> > > > > > > > > > > > > > > > > > > > > > > yes
./configure: line 17775: syntax error near unexpected token `QT,'
./configure: line 17775: ` PKG_CHECK_MODULES(QT, QtCore >= 4.3, QtNetwork >= 
4.3, have_qt=yes, have_qt=no)'
PyBOMBS.Packager.source - ERROR - Configuration failed after running at least 
twice.
PyBOMBS.Packager.source - ERROR - Problem occurred while building package 
apache-thrift:
Configuration failed
PyBOMBS.PackageManager - WARNING - Optional package apache-thrift failed to 
install.
PyBOMBS.install_manager - INFO - Installation successful.
PyBOMBS.install_manager - INFO - Installing package: liblog4cpp
00549 kB / 00549 kB (100%)
Configuring: (100%) 
[]
Building: (100%) 
[]
Installing: (100%) 
[]
PyBOMBS.install_manager - INFO - Installation successful.
PyBOMBS.install_manager - INFO - Installing package: zeromq
02084 kB / 02084 kB (100%)
Configuring: (100%) 
[]
Building: (100%) 
[]
Installing: (100%) 
[]
PyBOMBS.install_manager - INFO - Installation successful.
PyBOMBS.install_manager - INFO - Installing package: python-zmq
PyBOMBS.Packager.source - WARNING - Cannot find a source URI for package 
python-zmq
PyBOMBS.install_manager - ERROR - Error installing package python-zmq. Aborting.

> Chad

> On 2016-10-05 09:00, discuss-gnuradio-requ...@gnu.org wrote:

> > > > 
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 

Re: [Discuss-gnuradio] problem with a fresh pybombs build

[Jason Matusiak]

Hi Marcus, The reason I went with sudo was because it was erroring out 
if I didn't:

$ pip install -I --user pybombs
Collecting pybombs
  Using cached PyBOMBS-2.2.0.tar.gz
Complete output from command python setup.py egg_info:
/usr/lib/python2.7/distutils/dist.py:267: UserWarning: Unknown 
distribution option: 'entry_points'

  warnings.warn(msg)
/usr/lib/python2.7/distutils/dist.py:267: UserWarning: Unknown 
distribution option: 'install_requires'

  warnings.warn(msg)
usage: -c [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
   or: -c --help [cmd1 cmd2 ...]
   or: -c --help-commands
   or: -c cmd --help

error: invalid command 'egg_info'


Command "python setup.py egg_info" failed with error code 1 in 
/tmp/pip-build-FJfz9W/pybombs/



___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] problem with a fresh pybombs build

[Marcus Müller]

Hi Jason,

the --user flag installs into a user directory suitable for the user
calling pip – by using sudo, that user is root; recommendation: remove
this install again, and then run the same command without sudo :)

Best regards,

Marcus


On 07.10.2016 16:59, Jason Matusiak wrote:
> Alright, after some mucking about I may have made a bit more
> progress.  running: sudo pip install -I --user pybombs
>
> nets me:
> Collecting pybombs
> Collecting PyYAML (from pybombs)
> Collecting requests (from pybombs)
>   Using cached requests-2.11.1-py2.py3-none-any.whl
> Collecting six (from pybombs)
>   Using cached six-1.10.0-py2.py3-none-any.whl
> Collecting future (from pybombs)
> Collecting setuptools (from pybombs)
>   Using cached setuptools-28.2.0-py2.py3-none-any.whl
> Installing collected packages: PyYAML, requests, six, future,
> setuptools, pybombs
> Successfully installed PyYAML-3.12 future-0.15.2 pybombs-2.2.0
> requests-2.11.1 setuptools-28.2.0 six-1.10.0
>
> But it didn't put it into ~/.local/bin nor any other place in my
> path.  I see it installed in /usr/local/bin again.
>
> On 10/07/2016 10:18 AM, Koslowski, Sebastian (CEL) wrote:
>> Looks like its clashing with you first attempt. Maybe remove that first.
>> Also, if you do install with --user you need to add $HOME/.local/bin to
>> your PATH variable.
>>
>> Sebastian
>>
>> On 10/07/2016 04:09 PM, Jason Matusiak wrote:
>>> Running pip install --user pybombs
>>> returns:
>>> Collecting pybombs
>>> Requirement already satisfied: PyYAML in
>>> /usr/local/lib/python2.7/dist-packages (from pybombs)
>>> Requirement already satisfied: requests in
>>> /usr/local/lib/python2.7/dist-packages (from pybombs)
>>> Requirement already satisfied: six in /usr/lib/python2.7/dist-packages
>>> (from pybombs)
>>> Requirement already satisfied: future in
>>> /usr/local/lib/python2.7/dist-packages (from pybombs)
>>> Requirement already satisfied: setuptools in
>>> /usr/local/lib/python2.7/dist-packages (from pybombs)
>>> Installing collected packages: pybombs
>>> Successfully installed pybombs
>>>
>>> But if I type pybombs on the command line, I get:
>>> bash: /usr/local/bin/pybombs: No such file or directory
>>>
>>> On 10/07/2016 09:39 AM, Koslowski, Sebastian (CEL) wrote:
 Python usually doesn't look for packages in /usr/local/
 That can be changed, of course.
 However, maybe you should consider installing pybombs somewhere else.

 For example,
   pip install --user pybombs
 or
   pip install --user PATH_TO_YOUR_PYBOMBS_CLONE_OR_TARBALL
 should work nicely.

 Sebastian

 On 10/07/2016 03:07 PM, Jason Matusiak wrote:
>>> ls -lh /usr/local/bin/pybombs
>>> My suspicion is that pip for some reason didn't set the executable
> flag
>>> on the pybombs program file. If that's the case, you can fix
>>> that by
>>> sudo chmod a+x /usr/local/bin/pybombs
> That was indeed my first issue.  I don't know that I would blame pip
> for it just yet (we use a wonky version of sudo here at work). 
> Once i
> made the fix though, I get the following error:
> $ pybombs recipes add gr-recipes
> git+https://github.com/gnuradio/gr-recipes.git
> Traceback (most recent call last):
> File "/usr/local/bin/pybombs", line 11, in 
>   load_entry_point('PyBOMBS==2.2.0', 'console_scripts',
> 'pybombs')()
> File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py",
> line 542, in load_entry_point
>   return get_distribution(dist).load_entry_point(group, name)
> File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py",
> line 2568, in load_entry_point
>   raise ImportError("Entry point %r not found" % ((group,
> name),))
> ImportError: Entry point ('console_scripts', 'pybombs') not found
>
> That last line sort of makes me feel like it isn't aware of pybombs.
> Should all of this work with 16.04 (my only change from before)?
>
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
>
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] problem with a fresh pybombs build

[Koslowski, Sebastian (CEL)]

Looks like its clashing with you first attempt. Maybe remove that first.
Also, if you do install with --user you need to add $HOME/.local/bin to
your PATH variable.

Sebastian

On 10/07/2016 04:09 PM, Jason Matusiak wrote:
> Running pip install --user pybombs
> returns:
> Collecting pybombs
> Requirement already satisfied: PyYAML in
> /usr/local/lib/python2.7/dist-packages (from pybombs)
> Requirement already satisfied: requests in
> /usr/local/lib/python2.7/dist-packages (from pybombs)
> Requirement already satisfied: six in /usr/lib/python2.7/dist-packages
> (from pybombs)
> Requirement already satisfied: future in
> /usr/local/lib/python2.7/dist-packages (from pybombs)
> Requirement already satisfied: setuptools in
> /usr/local/lib/python2.7/dist-packages (from pybombs)
> Installing collected packages: pybombs
> Successfully installed pybombs
>
> But if I type pybombs on the command line, I get:
> bash: /usr/local/bin/pybombs: No such file or directory
>
> On 10/07/2016 09:39 AM, Koslowski, Sebastian (CEL) wrote:
>> Python usually doesn't look for packages in /usr/local/
>> That can be changed, of course.
>> However, maybe you should consider installing pybombs somewhere else.
>>
>> For example,
>>  pip install --user pybombs
>> or
>>  pip install --user PATH_TO_YOUR_PYBOMBS_CLONE_OR_TARBALL
>> should work nicely.
>>
>> Sebastian
>>
>> On 10/07/2016 03:07 PM, Jason Matusiak wrote:
> ls -lh /usr/local/bin/pybombs
> My suspicion is that pip for some reason didn't set the executable
>>> flag
> on the pybombs program file. If that's the case, you can fix that by
> sudo chmod a+x /usr/local/bin/pybombs
>>> That was indeed my first issue.  I don't know that I would blame pip
>>> for it just yet (we use a wonky version of sudo here at work).  Once i
>>> made the fix though, I get the following error:
>>> $ pybombs recipes add gr-recipes
>>> git+https://github.com/gnuradio/gr-recipes.git
>>> Traceback (most recent call last):
>>>File "/usr/local/bin/pybombs", line 11, in 
>>>  load_entry_point('PyBOMBS==2.2.0', 'console_scripts', 'pybombs')()
>>> File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py",
>>> line 542, in load_entry_point
>>>  return get_distribution(dist).load_entry_point(group, name)
>>> File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py",
>>> line 2568, in load_entry_point
>>>  raise ImportError("Entry point %r not found" % ((group, name),))
>>> ImportError: Entry point ('console_scripts', 'pybombs') not found
>>>
>>> That last line sort of makes me feel like it isn't aware of pybombs.
>>> Should all of this work with 16.04 (my only change from before)?
>>>
>>> ___
>>> Discuss-gnuradio mailing list
>>> Discuss-gnuradio@gnu.org
>>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>
>


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] problem with a fresh pybombs build

[Jason Matusiak]

Running pip install --user pybombs
returns:
Collecting pybombs
Requirement already satisfied: PyYAML in 
/usr/local/lib/python2.7/dist-packages (from pybombs)
Requirement already satisfied: requests in 
/usr/local/lib/python2.7/dist-packages (from pybombs)
Requirement already satisfied: six in /usr/lib/python2.7/dist-packages 
(from pybombs)
Requirement already satisfied: future in 
/usr/local/lib/python2.7/dist-packages (from pybombs)
Requirement already satisfied: setuptools in 
/usr/local/lib/python2.7/dist-packages (from pybombs)

Installing collected packages: pybombs
Successfully installed pybombs

But if I type pybombs on the command line, I get:
bash: /usr/local/bin/pybombs: No such file or directory

On 10/07/2016 09:39 AM, Koslowski, Sebastian (CEL) wrote:

Python usually doesn't look for packages in /usr/local/
That can be changed, of course.
However, maybe you should consider installing pybombs somewhere else.

For example,
 pip install --user pybombs
or
 pip install --user PATH_TO_YOUR_PYBOMBS_CLONE_OR_TARBALL
should work nicely.

Sebastian

On 10/07/2016 03:07 PM, Jason Matusiak wrote:

ls -lh /usr/local/bin/pybombs
My suspicion is that pip for some reason didn't set the executable

flag

on the pybombs program file. If that's the case, you can fix that by
sudo chmod a+x /usr/local/bin/pybombs

That was indeed my first issue.  I don't know that I would blame pip
for it just yet (we use a wonky version of sudo here at work).  Once i
made the fix though, I get the following error:
$ pybombs recipes add gr-recipes
git+https://github.com/gnuradio/gr-recipes.git
Traceback (most recent call last):
   File "/usr/local/bin/pybombs", line 11, in 
 load_entry_point('PyBOMBS==2.2.0', 'console_scripts', 'pybombs')()
File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py",
line 542, in load_entry_point
 return get_distribution(dist).load_entry_point(group, name)
File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py",
line 2568, in load_entry_point
 raise ImportError("Entry point %r not found" % ((group, name),))
ImportError: Entry point ('console_scripts', 'pybombs') not found

That last line sort of makes me feel like it isn't aware of pybombs.
Should all of this work with 16.04 (my only change from before)?

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio





___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] problem with a fresh pybombs build

[Koslowski, Sebastian (CEL)]

Python usually doesn't look for packages in /usr/local/
That can be changed, of course.
However, maybe you should consider installing pybombs somewhere else.

For example,
pip install --user pybombs
or
pip install --user PATH_TO_YOUR_PYBOMBS_CLONE_OR_TARBALL
should work nicely.

Sebastian

On 10/07/2016 03:07 PM, Jason Matusiak wrote:
> >> ls -lh /usr/local/bin/pybombs
>
> >> My suspicion is that pip for some reason didn't set the executable
> flag
> >> on the pybombs program file. If that's the case, you can fix that by
>
> >> sudo chmod a+x /usr/local/bin/pybombs
>
> That was indeed my first issue.  I don't know that I would blame pip
> for it just yet (we use a wonky version of sudo here at work).  Once i
> made the fix though, I get the following error:
> $ pybombs recipes add gr-recipes
> git+https://github.com/gnuradio/gr-recipes.git
> Traceback (most recent call last):
>   File "/usr/local/bin/pybombs", line 11, in 
> load_entry_point('PyBOMBS==2.2.0', 'console_scripts', 'pybombs')()
> File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py",
> line 542, in load_entry_point
> return get_distribution(dist).load_entry_point(group, name)
> File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py",
> line 2568, in load_entry_point
> raise ImportError("Entry point %r not found" % ((group, name),))
> ImportError: Entry point ('console_scripts', 'pybombs') not found
>
> That last line sort of makes me feel like it isn't aware of pybombs. 
> Should all of this work with 16.04 (my only change from before)?
>
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio



___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] problem with a fresh pybombs build

[Jason Matusiak]

>> ls -lh /usr/local/bin/pybombs

>> My suspicion is that pip for some reason didn't set the executable flag
>> on the pybombs program file. If that's the case, you can fix that by

>> sudo chmod a+x /usr/local/bin/pybombs

That was indeed my first issue.  I don't know that I would blame pip for 
it just yet (we use a wonky version of sudo here at work).  Once i made 
the fix though, I get the following error:
$ pybombs recipes add gr-recipes 
git+https://github.com/gnuradio/gr-recipes.git

Traceback (most recent call last):
  File "/usr/local/bin/pybombs", line 11, in 
load_entry_point('PyBOMBS==2.2.0', 'console_scripts', 'pybombs')()
File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 
542, in load_entry_point

return get_distribution(dist).load_entry_point(group, name)
File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 
2568, in load_entry_point

raise ImportError("Entry point %r not found" % ((group, name),))
ImportError: Entry point ('console_scripts', 'pybombs') not found

That last line sort of makes me feel like it isn't aware of pybombs.  
Should all of this work with 16.04 (my only change from before)?


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio