Continue to Site

Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

why byte parity verification is still needed when package CR

Status
Not open for further replies.

machael

Member level 2
Joined
Nov 4, 2004
Messages
44
Helped
0
Reputation
0
Reaction score
0
Trophy points
1,286
Activity points
457
eia709_2.jpg

It is a description of PHY package format of a power line communicaiton protocal.

As figure6.11, each byte in NPDU has 1 parity bit on Bit9, and fixed "0" and "1" on Bit10 and 11. However, the shole package has 2 bytes CRC16 bytes at the end of the package.

Now please, why the bit parities is needed since the CRC16 can make sure the correct of all the data? whe the receiver find that the parity bit is not correct when it is receiving, should it quit the next receiving action?

Because maybe the error bit is only the parity bit itself, so I don't think quit receiving is wise. But, if the crc is the final judgement of the validity of the package, the parity bit is nonsese. So why?

p.s. what is the useage of the fixed "01" bits? symbol timing recovery? if the sampling and judgement of the receiver is not "01", what should PHY receiver do?

Thanks a lot!
 

Status
Not open for further replies.

Similar threads

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top