Data Transmission: Constructing Digital Circuits & Clock Pulses

  • Thread starter Thread starter ws0619
  • Start date Start date
  • Tags Tags
    Data Transmission
Click For Summary
SUMMARY

This discussion focuses on constructing digital circuits for data transmission, specifically addressing the implementation of start and stop bits for 7-bit data, the importance of scrambling data, and increasing clock pulses during transmission. The Manchester (NRZ) coding technique is highlighted as a previous method used, emphasizing the need for synchronization between sender and receiver clocks through continuous clock pulse streams. Additionally, the necessity of a parity bit for error checking and ensuring even or odd transitions in the data stream is discussed.

PREREQUISITES
  • Understanding of digital circuit design principles
  • Familiarity with Manchester (NRZ) coding
  • Knowledge of data transmission protocols
  • Basic concepts of clock synchronization in digital systems
NEXT STEPS
  • Research the implementation of start and stop bits in serial communication
  • Learn about data scrambling techniques and their impact on transmission
  • Explore methods for increasing clock pulse frequency in digital circuits
  • Study error detection mechanisms, focusing on parity bits and their applications
USEFUL FOR

Electronics engineers, computer scientists, and anyone involved in designing or optimizing digital communication systems will benefit from this discussion.

ws0619
Messages
53
Reaction score
0
Hi!
I would like to construct a digital circuit as like how computer transmit data.

My problem is how can I make start bit and stop bit for my 7 bits data?and how can the receiver knows that that is start bit and not the data?(I confuse at this part)

While sending data, how can I scrambling the data?And actually does this scrambling process important in sending data?

To make the sending data clear, I want to increase the clock pulse between the data during sending.How can I do it?

Thanks!
 
Engineering news on Phys.org
I have used the Manchester (NRZ) code in the past. This Wiki mentions the code, but some
http://en.wikipedia.org/wiki/Self-clocking_signal
more elaboration is required. Before the data is sent, a sufficient number of clock cycles must be sent to permit the receiver time to synchronize its clock to the sending clock. Usually, the clock pulse stream is continuous. Second, you need a parity bit at the end, not only as a parity check, but also to make sure that the total number of transitions in the data stream is always even (or odd).
Bob S
 
Bob S said:
I have used the Manchester (NRZ) code in the past. This Wiki mentions the code, but some
http://en.wikipedia.org/wiki/Self-clocking_signal
more elaboration is required. Before the data is sent, a sufficient number of clock cycles must be sent to permit the receiver time to synchronize its clock to the sending clock. Usually, the clock pulse stream is continuous. Second, you need a parity bit at the end, not only as a parity check, but also to make sure that the total number of transitions in the data stream is always even (or odd).
Bob S

And here is a wiki article to give you some reading to do...

http://en.wikipedia.org/wiki/Data_transmission

.
 

Similar threads

  • · Replies 2 ·
Replies
2
Views
1K
  • · Replies 8 ·
Replies
8
Views
2K
  • · Replies 5 ·
Replies
5
Views
2K
Replies
1
Views
2K
  • · Replies 11 ·
Replies
11
Views
3K
  • · Replies 15 ·
Replies
15
Views
2K
  • · Replies 8 ·
Replies
8
Views
2K
Replies
20
Views
3K
  • · Replies 2 ·
Replies
2
Views
3K
  • · Replies 15 ·
Replies
15
Views
4K