Can two different remote controls on the same site trigger each other?
A clash is prevented not by frequency but by each transmitter-receiver pair's own identity code. Response lag in a busy band is congestion, not a clash.
No, one will not operate the other's machine. What prevents a clash is not that the frequencies are different but that each transmitter-receiver pair is paired with its own identity/address code; devices sharing the same band do not accept each other's code. If a large number of devices in the same band transmit simultaneously, however, the range and the response time can drop. That is not a clash but channel congestion, and its symptoms are different.
The mechanism that prevents a clash: the identity code
On industrial wireless remote controls every command carries the identity information of the transmitter. The receiver processes only the commands belonging to the identity taught to it and ignores the rest. That is why two different sets working on the same site do not operate each other's machine. The same holds for two sets using the same band, and even the same frequency; whether it is 433 MHz or 868 MHz does not change the result, what distinguishes them is not the band but the code.
Within the framework of the international standard for wireless remote control systems, the prevention of unauthorised use and of unintended operation together with data integrity and error detection are counted among the basic requirements; that is, a unique identification per pair is the general expectation in this field. How the code is taught to the receiver is explained under the pairing heading.
The real limit: channel congestion
Physical capacity, on the other hand, is limited. When a large number of devices using the same band transmit simultaneously:
- The response time can lengthen,
- The effective range can shorten,
- Commands may have to be sent again.
The duty cycle limits defined for short range devices exist for exactly this reason; every device is prevented from occupying the band continuously.
From symptom to cause
| Symptom | Likely cause | First check |
|---|---|---|
| The wrong machine is moving | Not a clash; the same transmitter may have been taught to two receivers, or the operator may have picked up the wrong device | Compare the labels and the pairing records |
| The command sometimes goes through and sometimes does not | Band occupancy or a nearby source of interference | Switch the other sets off and try again |
| The range drops only on the busy shift | Channel congestion | Move the receivers and the antennas further apart |
| No command goes through at all | Nothing to do with a clash; supply, pairing or antenna | Work through the checklist from the start |
Frequent mistakes on site
- Two remote controls of the same model left unlabelled. The devices are identical to one another; the mix-up is not technical but human.
- Receivers and antennas mounted right next to each other. Leave physical distance between the receivers of separate machines.
- Teaching the spare remote control to a second receiver as well, just in case. That means a single key concerns two machines at once.
- Not deleting a lost device from the receiver memory. The steps for securing the receiver when a remote control is lost are separate.
Where this assurance is not enough
- The identity code prevents the wrong device from operating the machine, but it does not prevent the right remote control being used at the wrong moment; the measures that prevent unintended operation are a separate topic.
- The wired emergency stop circuit has to stay reachable under all conditions.
- The cause of an intermittent response is not always congestion; in an intermittent response fault the supply and the antenna are questioned as well.
If more than one set is working on site, separate the receivers and the antennas from each other, give each set a clear label and set up a colour or number system that stops operators confusing which remote control belongs to which machine. When you commission a new set, leave the other machines de-energised and try that set on its own first; if a problem comes up, you will not have to hunt for its source.
The full topic: Wireless Crane Remote Control Selection Guide