Robots often need a wireless link so a phone, laptop, or base station can send commands and receive sensor data. Bluetooth and Wi-Fi are two common choices because they are inexpensive, widely supported, and built into many development boards. Choosing the right link matters because it affects driving range, response time, battery life, and the amount of data the robot can send.
A small wheeled robot may work well with either system, but the best choice depends on the job.
Understanding Robotics: Bluetooth and Wi-Fi for Robots
Both systems use radio waves, and both commonly share the crowded two point four gigahertz band. This band is used by home routers, headphones, keyboards, microwave ovens, and many classroom devices. Radio packets can collide or be weakened by walls, people, metal shelves, and a robot's own battery.
Bluetooth reduces repeated interference by changing radio channels very quickly. Wi-Fi normally stays on one selected channel and manages access among many devices.
A command packet may therefore arrive late, arrive twice after retransmission, or fail to arrive. Good robot software treats wireless communication as imperfect rather than assuming every message is received.
The connection method changes the design of the controller. Wi-Fi often connects the robot to an existing router, which lets a laptop on the same local network communicate with it. It can instead form a direct network for use away from a router.
Most Wi-Fi robot programs use Internet Protocol addresses and send messages with either TCP or UDP. TCP checks delivery and resends missing data, which is useful for files but can add delay. UDP sends without that guarantee, so it is common for frequent drive commands where the newest command matters most.
Bluetooth requires pairing first. Bluetooth Low Energy usually exposes named data items called characteristics. A phone can read a sensor value, subscribe to updates, or write a motor command.
Wireless hardware affects the battery more than beginners often expect. Sending data needs short bursts of current, while receiving and staying connected keep the radio active. A camera stream can drain a small robot far faster than occasional temperature or distance readings.
The processor, motors, and radio share one battery, so a sudden motor load can lower voltage and make the wireless link reset. Use a suitable voltage regulator and place decoupling capacitors near electronic boards. Antenna placement matters too.
An antenna hidden beside a motor, inside a metal case, or pressed against a large battery can lose signal strength. Keep it clear and follow the board maker's antenna guidance.
Students can test a link with a simple log that records the time each command is sent and the time a reply returns. Repeating the test at different distances shows that average delay is not enough. A robot must cope with occasional long delays.
Build a timeout into the controller. If no valid command arrives for a short set period, the robot should stop its motors or enter a safe state. This is important for cars, arms, and drones.
Give each control packet a sequence number when possible, so old packets do not overwrite a newer stop command. Pair only with trusted devices and use passwords or encryption when supported.
Signal strength readings help during testing, but they do not guarantee reliable control. The best evidence comes from repeated real movement tests in the place where the robot will operate.
Key Facts
- Bluetooth is usually best for short-range robot control, often about 10 m to 30 m depending on the version, antenna, and environment.
- Wi-Fi usually offers longer range than Bluetooth, often about 30 m to 100 m indoors or nearby outdoors with a good access point.
- Bandwidth measures data rate: bandwidth = data transferred / time.
- Latency is delay between command and response: latency = receive time - send time.
- Wi-Fi generally has higher bandwidth than Bluetooth, so it is better for video, maps, and large telemetry streams.
- Bluetooth Low Energy is designed for low power, so it is often better for battery-powered robots sending small packets.
Vocabulary
- Telemetry
- Telemetry is data sent from a robot to a controller, such as battery voltage, motor speed, position, or sensor readings.
- Bandwidth
- Bandwidth is the amount of data a communication link can carry per second.
- Latency
- Latency is the time delay between sending a command or data packet and receiving it at the other end.
- Bluetooth Low Energy
- Bluetooth Low Energy is a Bluetooth mode designed to send small amounts of data while using very little power.
- Access Point
- An access point is a Wi-Fi device, such as a router, that lets wireless devices connect to a network.
Common Mistakes to Avoid
- Choosing Wi-Fi just because it is faster is wrong because high bandwidth may waste power when the robot only sends small sensor readings.
- Choosing Bluetooth for live video is wrong because many Bluetooth links do not have enough bandwidth for smooth camera streaming.
- Ignoring latency is wrong because a robot can feel hard to control if commands arrive late, even when the signal strength looks good.
- Assuming the rated range always applies is wrong because walls, motors, metal frames, antennas, and radio interference can greatly reduce real range.
Practice Questions
- 1 A robot sends 1200 bytes of telemetry 20 times per second. What bandwidth is required in bytes per second and in bits per second?
- 2 A controller sends a drive command at 2.000 s and the robot receives it at 2.045 s. What is the latency in milliseconds?
- 3 A classroom robot must run for a long time on a small battery and only reports temperature, distance, and battery voltage once per second. Should the design favor Bluetooth Low Energy or Wi-Fi, and why?