A 2.4GHz car and its remote must 'bind' every time they are switched on. Get the order wrong, or switch the remote on too early, and the car sits there with a blinking light. Here is the routine, plus the fixes for the cases where the routine does not help.
If that fails, try the reverse order (remote first, then car). A few cars want the remote's trigger held while switching on. The manual — or the cartoys.pk product page — states which.
| Car light | Meaning |
|---|---|
| Fast blink | Searching for the remote — not paired yet |
| Steady | Paired, ready |
| Slow blink | Low battery on most cars |
| Off | Car is off, or its pack is completely flat |
Nearly always weak AA cells in the remote — range shrinks long before the remote stops. Replace them. On 27MHz cars, also extend the antenna fully and keep it upright; a folded antenna halves the range.
The wrist sensor pairs the same way but also needs to be held flat and still for the first three seconds after switching on, so it can zero itself. Tilt it during that window and every command will be offset. See the stunt cars range for which models use gesture control.
These do not pair — they simply share a fixed channel. If one 'stops responding', check for another 27MHz toy in the house on the same channel, and check the remote's crystal is pushed fully into its socket. The frequency guide explains why these cars interfere with each other.
If nothing above works within the first week, use the 7-day return on any RC car from cartoys.pk — a dead receiver is not something to repair at home.
Switch both off, switch the car on, then switch the remote on and wait 3–5 seconds for the car's light to stop blinking. If that fails, try remote first, then car.
Blinking on the car means it is searching for the remote and not yet paired. Blinking on the remote usually means its AA cells are low.
Only the one it shipped with, or an identical model from the same maker. Toy-grade 2.4GHz remotes are not cross-compatible between brands.