>On Sun, 13 Oct 2013 11:16:27 -0500, Tim Wescott wrote:
>
>> I'm working with a customer to design a system. The preferred
>> development model seems to have settled into one where I do all the
>> heavy lifting mathematically, and they implement the algorithms that I
>> cook up.
>>
>> Their software guy is willing, but we both think he'd benefit from a
>> tutorial or three, and perhaps a book on basic data communications.
>>
>> Does anyone have any recommendations? At the moment I'm kinda thinking
>> that I want something that presents in the following order:
>>
>> * NRZ data, and what it means * Filtered NRZ data * Data clock
>> synchronization * equalization
>>
>> Clearly there's a big jump from "this is filtered NRZ data" to data
>> clock synchronization, and another one to equalization -- I'm thinking
>> that the material doesn't need to give a full understanding of how to
do
>> these last two, but should give enough information so that he at least
>> feels that he's got a road map to what he's doing.
>>
>> TIA.
>
>Thank you all. I got a copy of Sklar, and liked it well enough to
>recommend it to my customer. It may not be the best of all possible
>books, but it looks more than sufficient (and the formal work on Turbo
>Codes is new to me, so I have some fresh reading for myself!)
>
>--
>
>Tim Wescott
>Wescott Design Services
>http://www.wescottdesign.com
>
>
Tim, the best reading on Turbo codes I have found till now, even better
than William Ryan, is from Todd Moon's book Error Control Coding, 2005.
Just start reading from Turbo Codes chapter. It can't get simpler than
that, although I must admit that reading from two different sources must
help.
The thing I don't like about Sklar is some unnecessary separation between
baseband and passband transmissions, and very superficial treatment of
synchronization topic. I have figured out that the best beginner's book for
learning Digital Communications is Michael Rice's Digital Communications -
A Discrete Time Approach, 2008 or 09. Concise and to the point.
_____________________________
Posted through www.DSPRelated.com
Reply by Eric Jacobsen●October 23, 20132013-10-23
On Wed, 23 Oct 2013 15:21:03 -0500, Tim Wescott
<tim@seemywebsite.really> wrote:
>On Sun, 13 Oct 2013 11:16:27 -0500, Tim Wescott wrote:
>
>> I'm working with a customer to design a system. The preferred
>> development model seems to have settled into one where I do all the
>> heavy lifting mathematically, and they implement the algorithms that I
>> cook up.
>>
>> Their software guy is willing, but we both think he'd benefit from a
>> tutorial or three, and perhaps a book on basic data communications.
>>
>> Does anyone have any recommendations? At the moment I'm kinda thinking
>> that I want something that presents in the following order:
>>
>> * NRZ data, and what it means * Filtered NRZ data * Data clock
>> synchronization * equalization
>>
>> Clearly there's a big jump from "this is filtered NRZ data" to data
>> clock synchronization, and another one to equalization -- I'm thinking
>> that the material doesn't need to give a full understanding of how to do
>> these last two, but should give enough information so that he at least
>> feels that he's got a road map to what he's doing.
>>
>> TIA.
>
>Thank you all. I got a copy of Sklar, and liked it well enough to
>recommend it to my customer. It may not be the best of all possible
>books, but it looks more than sufficient (and the formal work on Turbo
>Codes is new to me, so I have some fresh reading for myself!)
Sklar's book is good. I have the first edition which does not
include the TC stuff, but he wrote some published tutorials on the
topic that were pretty good. There are a lot of good tutorials on
the topic, including a good one by William Ryan that is oft-cited.
Dr. Sklar and I took a CE course at UCLA on Turbo Codes together along
with some other interesting people in the late 90s. He's a good guy.
I had a copy of his first edition already at the time and wished I'd
had it with me to get autographed. ;)
On Sun, 13 Oct 2013 11:16:27 -0500, Tim Wescott wrote:
> I'm working with a customer to design a system. The preferred
> development model seems to have settled into one where I do all the
> heavy lifting mathematically, and they implement the algorithms that I
> cook up.
>
> Their software guy is willing, but we both think he'd benefit from a
> tutorial or three, and perhaps a book on basic data communications.
>
> Does anyone have any recommendations? At the moment I'm kinda thinking
> that I want something that presents in the following order:
>
> * NRZ data, and what it means * Filtered NRZ data * Data clock
> synchronization * equalization
>
> Clearly there's a big jump from "this is filtered NRZ data" to data
> clock synchronization, and another one to equalization -- I'm thinking
> that the material doesn't need to give a full understanding of how to do
> these last two, but should give enough information so that he at least
> feels that he's got a road map to what he's doing.
>
> TIA.
Thank you all. I got a copy of Sklar, and liked it well enough to
recommend it to my customer. It may not be the best of all possible
books, but it looks more than sufficient (and the formal work on Turbo
Codes is new to me, so I have some fresh reading for myself!)
--
Tim Wescott
Wescott Design Services
http://www.wescottdesign.com
WTF %(
strange replacement of link
h*t*t*p://electronix.ru/forum/index.php?showtopic=23652
_____________________________
Posted through www.DSPRelated.com
Reply by Rick Lyons●October 23, 20132013-10-23
On Sun, 13 Oct 2013 11:16:27 -0500, Tim Wescott
<tim@seemywebsite.please> wrote:
>I'm working with a customer to design a system. The preferred
>development model seems to have settled into one where I do all the heavy
>lifting mathematically, and they implement the algorithms that I cook up.
>
>Their software guy is willing, but we both think he'd benefit from a
>tutorial or three, and perhaps a book on basic data communications.
>
>Does anyone have any recommendations? At the moment I'm kinda thinking
>that I want something that presents in the following order:
>
>* NRZ data, and what it means
>* Filtered NRZ data
>* Data clock synchronization
>* equalization
>
>Clearly there's a big jump from "this is filtered NRZ data" to data clock
>synchronization, and another one to equalization -- I'm thinking that the
>material doesn't need to give a full understanding of how to do these
>last two, but should give enough information so that he at least feels
>that he's got a road map to what he's doing.
>
>TIA.