by PaulP » Wed Feb 28, 2007 1:55 pm
by PaulP
Wed Feb 28, 2007 1:55 pm
They all suffer the same problem. Bluetooth has byte gaps and latency problems. This can cause data problems on those robots that have a very strict timing protocol.
If your robot doesn't have a strict timing then it may work.
Any system that waits for a byte to arrive before txing to the receiver and re-transmitting will have this problem. All packetised systems work this way, Radio Telemetry, Bluetooth and WiFi all wait for a full byte or even a packet to be assembled.
Older radio systems that dont work on Packets used a form of Frequency shift keying (FSK) similar to how a telephone modem works. This used to transmit bit by bit and only had the delay of 1 data bit.
If any of these are available in a miniaturised package then they would be ideal for all robots because there is almost zero delay in transmission
Again though, most 2.4 Ghz RF systems implement packets. In most cases they are much more versatile.
Anything that says 802.x will do this.
They all suffer the same problem. Bluetooth has byte gaps and latency problems. This can cause data problems on those robots that have a very strict timing protocol.
If your robot doesn't have a strict timing then it may work.
Any system that waits for a byte to arrive before txing to the receiver and re-transmitting will have this problem. All packetised systems work this way, Radio Telemetry, Bluetooth and WiFi all wait for a full byte or even a packet to be assembled.
Older radio systems that dont work on Packets used a form of Frequency shift keying (FSK) similar to how a telephone modem works. This used to transmit bit by bit and only had the delay of 1 data bit.
If any of these are available in a miniaturised package then they would be ideal for all robots because there is almost zero delay in transmission
Again though, most 2.4 Ghz RF systems implement packets. In most cases they are much more versatile.
Anything that says 802.x will do this.