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. -- Tim Wescott Control system and signal processing consulting www.wescottdesign.com
Data stream demodulation -- Tutorial and Books
Started by ●October 13, 2013
Reply by ●October 13, 20132013-10-13
Tim Wescott <tim@seemywebsite.please> writes:> 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.Tim, If you're asking for basic data comms books, I would suggest the following. --Randy @BOOK{couch, title = "{Digital and Analog Communication Systems}", author = "{Leon~W.~Couch}", publisher = "Prentice Hall", edition = "fifth", year = "1993"} @BOOK{sklar, title = "{Digital Communications}", author = "{Bernard~Sklar}", publisher = "Prentice Hall P T R", edition = "second", year = "2001"} -- Randy Yates Digital Signal Labs http://www.digitalsignallabs.com
Reply by ●October 14, 20132013-10-14
On Monday, October 14, 2013 5:16:27 AM UTC+13, 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. > > > > -- > > Tim Wescott > > Control system and signal processing consulting > > www.wescottdesign.comOrdinary equalization or blind?
Reply by ●October 14, 20132013-10-14
On Mon, 14 Oct 2013 01:20:29 -0700, gyansorova wrote:> On Monday, October 14, 2013 5:16:27 AM UTC+13, 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. >> >> >> >> -- >> >> Tim Wescott >> >> Control system and signal processing consulting >> >> www.wescottdesign.com > > Ordinary equalization or blind?Blind. -- Tim Wescott Control system and signal processing consulting www.wescottdesign.com
Reply by ●October 14, 20132013-10-14
On Sun, 13 Oct 2013 14:20:17 -0400, Randy Yates wrote:> Tim Wescott <tim@seemywebsite.please> writes: > >> 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. > > Tim, > > If you're asking for basic data comms books, I would suggest the > following. > > --Randy > > @BOOK{couch, > title = "{Digital and Analog Communication Systems}", > author = "{Leon~W.~Couch}", > publisher = "Prentice Hall", > edition = "fifth", > year = "1993"} > @BOOK{sklar, > title = "{Digital Communications}", > author = "{Bernard~Sklar}", > publisher = "Prentice Hall P T R", > edition = "second", > year = "2001"}Sklar on order from Goodwill via Amazon -- $15 plus $4 shipping. -- Tim Wescott Wescott Design Services http://www.wescottdesign.com
Reply by ●October 16, 20132013-10-16
Wireless Digital Receiver Design: Synchronization In Wireless Communications Systems Mohamed K. Nezami http://www.amazon.com/Wireless-Digital-Receiver-Design-Synchronization/dp/1884932614 Useful simulink models http://electronix.ru/forum/index.php?showtopic=23652 _____________________________ Posted through www.DSPRelated.com
Reply by ●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.Hi Tim, I like the following book, for beginners. (It's especially helpful for those readers who have Matlab software). The book's fairly gentle from a mathematical standpoint, and a good "stepping stone" before looking at more advanced books. The book is: "Software Receiver Design" by Johnson, Setares, and Klein. http://www.amazon.com/Software-Receiver-Design-Digital-Communication/dp/0521189446/ref=sr_1_1?s=books&ie=UTF8&qid=1382525686&sr=1-1&keywords=johnson+sethares [-Rick-]
Reply by ●October 23, 20132013-10-23
>Useful simulink models >http://electronix.ru/forum/index.php?showtopic#652WTF %( strange replacement of link h*t*t*p://electronix.ru/forum/index.php?showtopic=23652 _____________________________ Posted through www.DSPRelated.com
Reply by ●October 23, 20132013-10-23
>>Useful simulink models >>http://electronix.ru/forum/index.php?showtopic#652 > >WTF %( >strange replacement of link>h*t*t*p://electronix.ru/forum/index.php?showtopic=23652=23 http://goo.gl/jisDqs _____________________________ Posted through www.DSPRelated.com
Reply by ●October 23, 20132013-10-23
>>>Useful simulink models >>>http://electronix.ru/forum/index.php?showtopic#652 >> >>WTF %( >>strange replacement of link > >>h*t*t*p://electronix.ru/forum/index.php?showtopic=23652 > >=23 > >http://goo.gl/jisDqsAdmin, why "= 2 3" = #? _____________________________ Posted through www.DSPRelated.com
