Wireless information sending and baud rate

Click For Summary

Discussion Overview

The discussion revolves around the challenges of maintaining clock synchronization in wireless communication, particularly in the context of baud rate and data transmission. Participants explore different communication protocols and their implications for one-way information transfer.

Discussion Character

  • Technical explanation, Conceptual clarification, Debate/contested

Main Points Raised

  • One participant notes that both sides in a communication need a clock to stay in sync, questioning how this is achieved in wireless settings where direct communication may not be possible.
  • Another participant explains that asynchronous protocols allow for close time synchronization without perfect alignment, suggesting that a long pulse can signal the start of a transmission.
  • It is mentioned that synchronous protocols rely on a clock generated by a bus master, which may not be feasible in wireless communication.
  • A suggestion is made to transmit a clock signal over a separate channel or to convert synchronous data to asynchronous for wireless transmission.
  • Another participant introduces Manchester coding as a method used in simpler wireless datalinks to embed a clock in the data stream, acknowledging the trade-off in bandwidth but highlighting its reliability.

Areas of Agreement / Disagreement

Participants express varying levels of understanding and propose different approaches to the problem, indicating that multiple competing views remain regarding the best method for achieving clock synchronization in wireless communication.

Contextual Notes

The discussion does not resolve the complexities of clock synchronization and the specific conditions under which different protocols may be applied. Limitations regarding the assumptions of each protocol and the practical implications of their use in wireless settings are acknowledged but not fully explored.

bassplayer142
Messages
431
Reaction score
0
I understand how a baud rate can be set by a clock and the data can be shifted through a line. Both sides need a clock to keep in sync. How would this be achieved if you are using wireless. Would both sides need to communicate back and forth because I can't see how a clock could be set on both sides if both sides can't communicate.

I am only interested in moving information in one direction.
 
Engineering news on Phys.org
bassplayer142 said:
I understand how a baud rate can be set by a clock and the data can be shifted through a line. Both sides need a clock to keep in sync. How would this be achieved if you are using wireless. Would both sides need to communicate back and forth because I can't see how a clock could be set on both sides if both sides can't communicate.

I am only interested in moving information in one direction.

Well, it really depends on the communications protocol you're using. If you're using an asynchronous protocol (like RS-232 serial, or USB, or Ethernet--IEEE802.3) you know that you won't maintain perfect time synchronization, but you can keep it close enough for short bursts (a few hundred KB, for instance). As long as you know when a transmission happens (say, with a really long high pulse), and the transmission speed (say, 9600 baud) and you've got a decent clock crystal, you can receive packets of data without having to transmit a clock.

If, on the other hand, you're using a synchronous protocol (e.g. I2C or SPI), you rely on a clock being generated by the bus master.

Generally, most wireless protocols are asynchronous. If you needed to wirelessly transmit a clock, and have multiple channels available, and your wireless transmission speed was much faster than your wired protocol, you can use one channel to transmit the clock and one to transmit the data. Or you can come up with some way of transmitting both on the same channel.

But it's probably easier to change synchronous data to asynchronous (say, with a micro) transmit it wirelessly, and then convert it back from asynchronous to synchronous on the receiver end. Or just not use synchronous in the first place.
 
Still a little out of my league! But thanks for the information.
 
Wifi (802.11) uses a more complex scheme but simple wireless (or infrared) datalinks use Manchester coding http://en.wikipedia.org/wiki/Manchester_code to embed a clock in the data stream.
It costs you in terms of bandwidth but is very reliable and simple to implement.
 

Similar threads

  • · Replies 5 ·
Replies
5
Views
2K
Replies
9
Views
6K
Replies
6
Views
3K
  • · Replies 67 ·
3
Replies
67
Views
5K
  • · Replies 3 ·
Replies
3
Views
4K
Replies
3
Views
3K
  • · Replies 3 ·
Replies
3
Views
2K
  • · Replies 4 ·
Replies
4
Views
3K
  • · Replies 2 ·
Replies
2
Views
2K
  • · Replies 3 ·
Replies
3
Views
2K