Xerox “093-563” — IOT not ready after power cycle (VersaLink/AltaLink/WorkCentre)

We’ll get past **093-563 — IOT not ready**. Quick triage so I target the right path:
• Model family: **VersaLink** (B/C series), **AltaLink**, or **WorkCentre**?
• What happened just before the error: **power outage**, **firmware update**, jam cleared, or moved the device?
• Front panel shows: **UI Not Ready**, **Device Not Ready**, **warm-up loop**, or specific **IOT/ESS communication** messages?
• Any add-ons: finisher, fax kit, extra trays, card reader (YSoft/SafeQ), USB devices?

Understood. **093-563** means the **IOT (engine)** didn’t come ready for the **ESS/controller** after boot. Common causes:
• **Low-voltage power supply (LVPS/SMPS)** rail sag after power events.
• **IOT-ESS communication** hiccup (harness, connectors, NVRAM state).
• A **door/interlock** not detected (ADF/DF or left cover), so engine never transitions to **Ready**.
• Corrupt **NVM** or **HDD/SSD** causing modules to time-out.
We’ll start with safe power and interlock checks, then run engine tests and, if needed, do a controlled **NVM/diagnostic boot** and **firmware reload**.

Step 1 — Known-good power & interlocks
1) Plug the printer **directly into a wall outlet** (no UPS/surge strip). Xerox specifically warns that strips can starve current and prevent **Ready** state.
2) Power **off**, wait **60–90 s**, then power **on**.
3) Open/close all doors and trays firmly. On AltaLink, make sure the **document feeder top & left covers** are fully seated — these interlocks can cause **UI not ready** symptoms.
4) Remove external accessories (USB card readers, USB drives) for this test.
Tell me if **Ready** appears or if it still shows **093-563**.

Step 2 — Engine/Controller quick tests
• From **CWIS → Status/Alerts**, check if any **doors/consumables** read “Open/Not Installed”.
• If you can access **Diagnostics/Service Mode**, run **IOT readiness/engine** tests (fans, motors). Listen for fuser and main motor spin-up.
• Power off, then reseat the **IOT-ESS harness** connectors you can safely access (controller to engine).
• If a finisher/extra tray is attached, boot once with those **disconnected** to eliminate accessory faults.
If nothing changes, we’ll do an **NVM reset of engine counters** and check the storage device.

Yes. A corrupt **NVM block** or failing **HDD/SSD** can stall IOT readiness after power loss.
Step 3 — Safe recovery path
1) In Diagnostics, perform a **Software Reset** (non-destructive). If available, clear **fault history** and retry.
2) Run **HDD/SSD test/initialize** (this wipes job logs/spool; keep address books if possible).
3) Update to the **latest firmware** via **USB** or CWIS (**alt-boot/forced upgrade**) to refresh IOT/engine modules and certificates.
4) If the panel still shows **093-563**, proceed to a **targeted NVM reset** for engine ready state (model-specific). I’ll guide exact codes in chat to avoid wiping calibration unnecessarily.

Solid! Best practices to prevent **IOT not ready** recurrences:
• Keep the device on a **dedicated wall outlet**; avoid shared strips/UPS that limit inrush current.
• Ensure **doors/interlocks** (ADF, left cover, finisher) fully seat; mis-detected interlocks often mimic IOT faults.
• Schedule **firmware** updates during low use; never cut power mid-update.
• If you use fleet software or card readers (**SafeQ/Terminal Professional**), confirm they’re **model-compatible** and updated — stale add-ons can hold the UI in **Not Ready**.
• If symptoms return after clean power and firmware, suspect **LVPS/SMPS** or controller board; those require parts diagnostics.

Largely yes. On **AltaLink C81xx**, Xerox notes **UI Not Ready** can be caused by **ADF covers** not seated. Close the **document feeder top & left covers**, then power cycle. If the UI comes Ready but engine doesn’t, it’s still an **IOT readiness** path.

Summary: For **Xerox 093-563 — IOT not ready**, verify **clean power**, **interlocks**, and **accessories** first. Then test engine readiness, run **Software Reset**, **HDD/SSD test/init**, and perform a **firmware reload**. Persisting faults point to **IOT-ESS comms** or **LVPS/SMPS**. Want step-by-step for your exact model? Open the chat.