Cronus Zen controller not recognised: waiting for controller and dead pads
A Cronus Zen controller not recognised is usually a bad cable, the wrong port (A1 or A3), the wrong Output Protocol or a pad that console rejects on A1.
When the Cronus Zen does not recognise a controller, the cause is usually the cable, the pad sitting in the wrong port, an Output Protocol set for a different console, or a pad that console will not accept on A1. Players describe two symptoms: the Zen never picks the pad up (often searched as "waiting for controller"), or the pad lights up and the console ignores it. Both come down to the list below, and the cable comes first.
What A1 needs, per console
| Console | On A1 | Your play pad | Source |
|---|---|---|---|
| Xbox Series X/S, Xbox One | An Xbox controller for that console, by USB: official, or a licensed model on Cronus's list | A1, or A3 for crossover | Cronus's Xbox pages |
| PS5 (all models) | The Zen Link module; with the bypass, the DualSense itself | With Zen Link, a front port by USB; Cronus's troubleshooting page names A2 or A3 | Cronus's PS5 and Zen Link pages |
| PS4 | A DualShock 4, by USB; for crossover it must be a DualShock 4 v2 (CUH-ZCT2) | A1, or A3 for crossover | Cronus's PS4 page |
| Nintendo Switch | Nothing; Cronus says no AUTH controller is needed | Switch pads by Bluetooth; other USB pads on A3 | Cronus's Switch page |
| PC | Unofficial; Cronus supports only licensed console controllers, not PC-only ones | A1 | The PC page in Cronus's older guide |
Cronus's older guide says unlicensed Xbox, PS4 and Switch controllers are not compatible; its current Controller page adds that an unlisted controller has not been tested, which does not mean it will not work. If your A1 device is not what the table names for your console, that is the answer, and nothing below will change it.
1. The pad's cable
The cable between the pad and the Zen must carry data. Charge-only cables light the pad and send nothing. Swap it for a cable you know syncs data and plug it firmly into the port the table names. Cronus's matched setup then says that after a few seconds the controller powers on and syncs with the Zen. For an Xbox pad that does not, Cronus's fix is to unplug both of the Zen's USB cables with the pad still attached, wait a few seconds, plug them back in, and hold the pad's Xbox button if it stays off.
2. The port
On Xbox and PS4 the controller that matches the console goes in A1, not A3. Cronus requires it there whenever any crossover device is used, because the Zen reports to the console as whatever is on A1. A pad on A3 with A1 empty has nothing to stand behind it. The authentication controller explains why A1 is special. Other controllers, mice and keyboards go on A3, and A2 when you need a second device. On PS5 the layout is different: Zen Link in A1 and the pad in a front port, or with the bypass the DualSense in A1; PS5 setup. On Switch, Cronus says no AUTH controller is needed on A1.
3. The pad type
On PS4, a DualShock 4 v1 (CUH-ZCT1) works for play but Cronus says it will not work as the AUTH controller for crossover; you need a v2. On Xbox, Cronus warns that some Xbox One and Series X|S controllers share a name while only one of the pair is supported, and tells them apart by the Series model's extra Capture button. Cronus's older guide warns that connecting an unsupported controller can trigger an E3 error code, which an unplug and replug clears; its current troubleshooting page treats E3 codes as corrupted or missing firmware, fixed by bootloader recovery. If you are unsure, put an official pad for the console on A1 to rule this out.
4. The Output Protocol
Cronus has you set the Output Protocol in Zen Studio's Device panel before setting up a controller: Xbox One X/S for Xbox, PlayStation 4/5 for PS4, Nintendo Switch for Switch; for PS5 it points to its PS5 pages, and its current Zen Link setup has no protocol step. Cronus's older guide adds that Auto usually works and that a hard reset sets it back to Auto. Connect PROG to a Windows PC, open the Device panel, set it, then reconnect to the console.
5. Power
The Zen and everything plugged into it draw power from the port on the other end of the CONSOLE/PC cable. Cronus names the front USB ports of a PS4 Pro as too weak for the Zen, and recommends a powered USB hub with a 5 V auxiliary power input, which it says helps prevent pairing failures and PS5 disconnections. Plug the Zen's CONSOLE/PC cable directly into the console (a rear port on a PS4 Pro) or into a powered hub. Cronus also notes the controller might not charge through the Zen, so start a wireless pad fully charged. Ports and cables.
6. The slot
If the console shows a controller connected but input does nothing or does the wrong thing, a script on the active slot may be changing it. Slot 0 means no script is loaded. Change slot with the P1 button until you reach 0. If the pad now works, the slot's script is the problem; Script not working.
7. Power cycle
Cronus's recovery for a crashed Zen is to unplug every USB cable from it for at least ten seconds, then reconnect. This does not touch programmed slots or firmware. Keep the hard reset (P1 and P2 held while connecting) for when that fails: Cronus says it erases every script stored on the Zen, so back up M&K profiles and keep copies of your scripts first; Script slots and memory.
8. Test the pad without the Zen
Cronus's own advice is that the best cable test is to plug the controller straight into the PC or console and see if it is detected. If it works there, the pad and cable are fine and the problem is in steps 2 to 7. If it does not, the pad or its cable has a fault, and no amount of Zen troubleshooting will help.
9. Cronus's controller test on a PC
Cronus's older guide publishes a controller test that checks the firmware, ports, Zen Studio and cables in one pass; its current guide has no equivalent page:
| Step | Do | Expect |
|---|---|---|
| 1 | Connect both CONSOLE/PC and PROG to a Windows PC (testing only, not play) | Zen Studio detects the Zen |
| 2 | Tap the Zen's reset button, wait five seconds, plug the controller into A1 | The controller turns on while pairing |
| 3 | Device panel: set the Output Protocol (XBOX ONE X/S, or PLAYSTATION 5 or 4) | Joypad and console icons light up |
| 4 | Press F3 for Device Monitor and press buttons | Inputs show in real time |
| 5 | Unplug PROG, tap reset | Xbox pad: RGB LEDs solid green. PlayStation pad: LEDs stay off |
| 6 | Open gamepad-tester.com | Windows reads the controller |
If the controller passes here and fails on the console, the console side is the problem: cable, port, power or Output Protocol.
10. The Zen
A Zen that fails with two known data cables, two supported pads and a direct console connection may have a failed A1 port. Try the pad in A3 with a different pad in A1 to see whether A1 specifically is dead. A dead port is a warranty case; Cronus's error pages describe the warranty route.
The second pad on A3
| Symptom | Cause | Fix |
|---|---|---|
| A3 pad does nothing on Xbox or PS4 | No matching controller on A1 | Put the console's own controller on A1 (DualShock 4 v2 on PS4) |
| Xbox pad will not pair wirelessly | Needs the Xbox Wireless Adapter; Cronus's older guide says the controller's sync button will not work | Adapter on A3, plug the pad into A2 by cable for a few seconds, then unplug; the adapter's LED turns solid white |
| DualSense will not pair, or loses features, over Bluetooth | Cronus lists DualSense Bluetooth as limited (no adaptive triggers, rumble, gyro or mic), pairs it with Create and PS, and lists it as USB only on Switch | Use it by USB on A3 |
| Wired headset silent | Cronus says there is no 3.5 mm audio over a Bluetooth controller connection | Connect the pad by USB |
| Bluetooth pad drops in and out | Corrupt pairings, which Cronus says can cause disconnections | Clear the Zen's Bluetooth pairings (Clear BT Devices, or clear Bluetooth in Zen Studio Live) on firmware 2.3.2 or later, which fixed clearing; Bluetooth pairing problems |
If it worked yesterday
Nothing on the Zen changes on its own. A console update, a pad firmware update through the console, a swapped cable, a hard reset that put the Output Protocol back to Auto, or a moved plug did. Retrace the last change, then start from step 1. Cronus Zen not detected is the same approach for the case where the PC or the console cannot see the Zen at all.
Quick reference
| Symptom | Most likely cause | First fix |
|---|---|---|
| Zen never picks the pad up | Charge-only cable | Data cable, firmly in the right port; tap reset, or the Xbox power cycle |
| Still nothing with a good cable | Pad in A3 with A1 empty, or an unlisted pad | The console's own controller on A1 |
| Pad lights, console ignores it | Output Protocol, or a script on the active slot | Set the protocol; slot 0 |
| Pad pairs, then drops | Power, or a flat battery | Direct port or powered hub; charge the pad |
| Works plugged straight into the console, not via the Zen | Cable, port, protocol or power | Steps 1, 2, 4, 5 |
| Crossover fails on PS4 | DualShock 4 v1 on A1 | DualShock 4 v2 on A1 |
| Fails on two pads, two cables, direct | A1 port fault | Test the pad in A3; warranty |
Frequently asked
- Why does the Zen say waiting for controller?
- Usually nothing on A1 that the console accepts: a charge-only cable, the pad in A3 with A1 empty, or an unlisted pad. Swap the cable first, then tap the Zen's reset button; for an Xbox pad, unplug and replug both of the Zen's cables with the pad attached.
- The pad lights up but the console ignores it. Why?
- The pad is powered but not paired, the Output Protocol in Zen Studio is set for a different console, or a script on the active slot is changing the input. Check the cable, set the Output Protocol, and test on slot 0.
- My second controller on A3 does not work.
- On Xbox and PS4, Cronus requires a matching controller on A1 whenever a crossover pad is used; on PS4 it must be a DualShock 4 v2. Fix A1 first, then check the A3 pad is wired or its adapter is set up.
- Could the controller itself be broken?
- Cronus's own test is to plug the controller straight into the PC or console. If it works there, the problem is the cable, the port, the settings or the Zen's power; if it does not, it is the pad.
- Which pad does the PS5 need?
- With Zen Link, the module goes on A1 and the pad in a front port by USB. With the bypass, the DualSense goes on A1. Cronus lists the DualSense and DualSense Edge (CFI-ZCP1) for PS5, and says any supported controller works.
- Does the pad need its own firmware updated?
- Cronus's guide does not list pad firmware as a cause. If everything else checks out, plugging the pad straight into the console and accepting any update the console offers is a cheap thing to rule out.
Something on this page wrong or out of date? Report a correction