Wireless charging looks like a one-way street: power crosses an air gap from the transmitter coil in the floor to the receiver coil on the vehicle. But nothing actually happens until the two sides talk to each other. Before a single watt flows, the charger and the vehicle run a handshake — they recognize each other, agree on the charge command, and then broadcast status back to the fleet for the whole session.
That conversation is what this guide covers: the 2.4G link that connects the transmitter and receiver, the CAN and RS485 ports that carry the charge command from the vehicle, and the exact pinouts you need to wire. Everything here comes from the LS300-A60 3kW system and LC180-A30 1.5kW system datasheets.
Three Layers of Communication in a Wireless Charging Session
An industrial wireless charger communicates on two distinct layers, and both systems share the same architecture:
| Layer | Who talks | What it carries |
|---|---|---|
| 2.4G radio link | Transmitter controller ↔ receiver controller | Recognition and charging control between the two halves of the system |
| CAN / RS485 | Charger ↔ vehicle BMS / fleet controller | The charge command and set voltage from the vehicle, plus live status back to the fleet |
On both the LS300-A60 and the LC180-A30, the communication method between transmitter and receiver is a 2.4G radio link, and the communication protocol exposed to the outside world is CAN / RS485. The transmitter side of the LC180 also offers LAN.
The 2.4G Link: How Transmitter and Receiver Recognize Each Other
Each controller carries an SMA antenna port for a 2.4G antenna. When the receiver coil approaches the transmitter coil, the two controllers establish a wireless link and run what the datasheet calls multi-machine recognition — the system figures out which vehicle just docked and confirms it is the right one. On the LC180-A30, that recognition completes in under 10 seconds.
This is why the system needs no start button and no external boot signal. The vehicle docks, the 2.4G link comes up, and the charger is ready the moment it is in range. If the vehicle drives away and the link breaks, communication drops and charging stops automatically — the charger does not keep pushing power at an empty pad.
A useful mental model: the 2.4G link is the wireless charger's presence detection. The CAN/RS485 port, next, carries the actual business decision.
CAN and RS485: The Ports That Talk to the Vehicle and the Fleet
Once the link is up, the system enters a standby state and waits — for a CAN command from the vehicle. The charger does not decide the target voltage on its own. The vehicle's BMS sends the charging command and the set voltage, and only then does power start to flow. No external boot signal is needed; the vehicle simply docks and issues the command.
During the session the charger keeps the fleet informed. It broadcasts a CAN frame with output voltage, output current, temperature, and coupling degree, so a host computer or fleet system can see in real time exactly what is happening at the pad.
If something goes wrong, the same port is the diagnostic path: the datasheet troubleshooting guide tells you to check the CAN packets reported by the host computer or the receiver to identify the specific fault.
The Ports You Actually Wire: Pinouts and Connectors
This is the part an integrator reaches for first — which connector carries what signal, and what color wire goes where.
LS300-A60 transmitter controller — the 485/CAN port is an RJ45 connector:
| Pin | Signal | Description |
|---|---|---|
| 1 | 485+ | RS485 A |
| 2 | 485− | RS485 B |
| 3 | CANH | CAN_H bus line (dominant high) |
| 4 | CANL | CAN_L bus line (dominant low) |
| 5–6 | N/A | Unused |
| 7 | +12V | Auxiliary input, 12 V positive |
| 8 | GND | Auxiliary input, 12 V negative |
A separate RJ45 "burn" port on the transmitter is for firmware updates and debugging only — it is not enabled in normal operation.
Receiver controllers (LS300-A60 and LC180-A30) — both expose the 485/CAN COM port on a 5-pin M12 male connector with the same pinout:
| Pin | Signal | Description | Wire color |
|---|---|---|---|
| 1 | 485+ | RS485 A | Brown |
| 2 | 485− | RS485 B | White |
| 3 | CAN_GND | RS485 & CAN ground | Blue |
| 4 | CANH | CAN_H bus line (dominant high) | Black |
| 5 | CANL | CAN_L bus line (dominant low) | Gray |
LC180-A30 transmitter controller — in addition to 485/CAN, the transmitter side supports LAN (a standard RJ45 network port for TCP/UDP debugging), and the 485/CAN debug interface is available on a USB connector. Its receiver uses the same 5-pin M12 COM port shown above.
The Charging Conversation, Step by Step
Both datasheets describe the same control logic. Here is the full sequence in the order it happens:
- The receiver coil docks onto the transmitter coil.
- The 2.4G link comes up between transmitter and receiver, and multi-machine recognition completes (under 10 seconds on the LC180).
- The system enters a standby, "rechargeable" state and waits for a CAN command from the vehicle — no boot signal needed.
- If the output port voltage is at or below the set voltage minus 1.2 V, charging begins — on the LC180 the current rises to the set value in under 20 seconds.
- Throughout the session the charger broadcasts a CAN frame with output voltage, current, temperature, and coupling degree.
- Constant-current charging tops up the pack, then constant-voltage charging finishes the curve, and charging completes.
The indicator lights give a running read on which step you are in. On both systems, a yellow light is steady when the 2.4G communication link is established (the rechargeable state) and blinks once output current reaches 5 A. A green light is steady in standby, and a blinking red light means a fault — check the CAN packets to find out which one.
What to Check Before You Wire the Communication Ports
- Connector type on your vehicle's controller — the receiver COM port is a 5-pin M12 male on both systems; the LS300 transmitter's 485/CAN port is an 8-pin RJ45 connector with a different layout. Do not assume they are wired the same.
- Wire colors — on the M12 COM port, brown is RS485 A, white is RS485 B, blue is the shared ground, and black and gray are CANH and CANL.
- CAN topology — pin 3 is the shared RS485 and CAN ground; follow your CAN bus rules for termination and node wiring.
- Antenna connection — the 2.4G link depends on the SMA antenna being connected on both controllers. A missing or broken antenna appears as a 2.4G communication failure, not a wiring fault.
- Charging distance — the coil gap must stay within the rated range (20–45 mm for the LS300, 10–30 mm for the LC180), or both the 2.4G link and power transfer degrade.
- 12 V auxiliary input on the LS300 transmitter — pins 7 and 8 of the RJ45 port provide the 12 V auxiliary supply; the receiver's 12 V auxiliary output is non-isolated and not recommended for customer use.
Conclusion
Communication is the part of a wireless charging system you cannot see, and it is the part that makes everything else automatic and safe. The 2.4G link handles recognition, CAN/RS485 carries the charge command and live status, and the whole loop runs without a human in it — dock, recognize, command, charge, report.
If you are integrating a wireless charger into an AGV, AMR, or forklift fleet and need to match the communication ports to your vehicle's BMS, send ONEPOINTECH your BMS protocol and wiring requirements. We can match you to an LS300-A60 3kW system, an LC180-A30 1.5kW system, or a custom build that speaks your fleet's language.
Need a recommendation? Email info@onepointech.com with your battery spec, BMS protocol, and fleet architecture — our engineering team will help you pick the right wireless charging solution.