keyword: 12V 1A EU adapter
KRECO | Starlink & SatNet Power FAQ Series — Article 11
Short answer: Starlink Standard 4 X (formerly the Gen 3 Standard kit) uses a ~150W proprietary single-connector DC brick that plugs ONLY into Router 3 via its barrel jack. Router 3 then injects 56–57V DC proprietary passive PoE (pins 1236+ / 4578-) into the dish cable to power the V4 dish. Therefore Router 3 is the dish's PoE source and gateway — it must ALWAYS stay connected and powered. If Router 3 is switched off, unplugged, faulty, or removed, the dish receives no PoE and reports POE_INSUFFICIENT, fails to boot, or reboots in a loop. Router 3 cannot be reverse-powered from a third-party PoE injector or from Starlink's Advanced Power Supply (APSU) — current flows Router 3 → dish, never backward — so Router 3 always needs its own independent supply (original Starlink brick or a compatible replacement). To use a third-party router: keep Router 3 powered and connected to the dish, run Ethernet from a Router 3 LAN port to the third-party router's WAN/Internet port, power the third-party router from its own PSU (Router 3 LAN ports are data-only, no PoE output), and enable Bypass Mode in the app: Settings → Advanced → Bypass Mode → On.
| Item | Specification / Notes |
|---|---|
| AC Input | 100–240V ~ 2.5A, 50–60Hz (same as Standard 4) |
| Original Power Brick | Proprietary single-connector DC brick, ≈150W (official replacement spec); connects ONLY to Router 3 via barrel jack — not directly to the dish |
| Router 3 Role | Receives DC from the brick; injects 56–57V DC proprietary passive PoE (1236+ / 4578-) into the dish cable; also acts as gateway/router |
| Dish (Terminal) | V4 phased array, IP67, average 75–100W, idle ≈20W, +10–20W with Snow Melt |
| Power / Data Path | Brick → Router 3 → (56–57V PoE) → Dish. Reverse powering is impossible — the dish / third-party injector cannot power Router 3 |
| Router 3 LAN Ports | 2 latching RJ45, data-only, NO PoE output; used to connect a third-party router in Bypass Mode |
| Reason | Explanation | If Router 3 Loses Power |
|---|---|---|
| 1. It is the dish's PoE source | The dish's 56–57V proprietary PoE comes entirely from Router 3 — there is no second power path | Dish gets no PoE → POE_INSUFFICIENT / fails to boot / reboots in a loop |
| 2. It is the Starlink network gateway | Handles dish control, authentication, firmware and app management; remains a bridge/gateway even in Bypass Mode | Link drops; app shows dish offline; third-party router gets no WAN |
| 3. It cannot be reverse-powered | Current flows Router 3 → dish only. Third-party PoE injectors, DC-DC converters and the APSU cannot reverse-feed Router 3 | Even with third-party power on the dish side, Router 3 still needs its own independent supply (original brick or compatible module) |
Conclusion: On Standard 4 X, Router 3 can never be removed or unplugged from the system. It is not an optional Wi-Fi hotspot — it is the power and networking hub of the entire kit.
| Item | Standard 4 (Router Mini) | Standard 4 X (Router 3) |
|---|---|---|
| Power Supply | 195W dual-port PoE brick UTP-253L (57V, 1.75A × 2) | ≈150W single proprietary DC brick → Router 3 only |
| Router | Router Mini: dual-band Wi-Fi 6, 2×2, ≈120 m² | Router 3: tri-band Wi-Fi 6, 4×4 MU-MIMO, ≈297 m², 2 latching LAN |
| Can the dish be powered independently of the router? | YES — PoE brick Port A feeds the dish directly; Router Mini is optional and can be omitted entirely | NO — must be fed by Router 3; Router 3 cannot be omitted |
| Connecting a third-party router | Omit Router Mini; plug third-party router into PoE brick Port B; no Bypass needed (but the third-party router needs its own PSU — Starlink PoE is proprietary and will not power it) | Keep Router 3 powered and connected to the dish; cable Router 3 LAN → third-party router WAN; must enable Bypass Mode |
| Third-party router power | Own PSU (Port B is data only; Starlink proprietary PoE does not reverse-feed) | Own PSU (Router 3 LAN ports are data-only, NO PoE output) |
What Bypass Mode is: when enabled, Router 3 disables its own Wi-Fi broadcast, NAT and DHCP server and becomes a transparent bridge, handing the Starlink WAN connection to your third-party router for routing, firewall, VPN and VLANs. Important: Router 3 must still be powered and connected to the dish — Bypass Mode does NOT remove it from the power chain.
Enable path (may vary slightly by app version):
Starlink App → Settings → Advanced → Bypass Mode → toggle On
Some versions place it under: Settings → Router → Bypass Mode. If you cannot find it, update the Starlink app and Router 3 firmware first.
Correct wiring and setup steps:
What to expect after enabling: the third-party router's WAN port receives the IP assigned by Starlink (typically a CGNAT 100.x.x.x private address — no public IPv4 by default). The app may show a "Bypass Mode" status. Some Router 3-dependent features (guest network, certain stats) become limited.
How to revert: toggle Bypass Mode → Off. Router 3 re-enables its own Wi-Fi, NAT and DHCP and resumes full router operation.
KRECO Group — an IEC 60601 medical & industrial power manufacturer since 2008 (Equity Code 891359, Medical Reg. 20200118#, FIME Silver Sponsor) — is developing Starlink-compatible OEM/ODM power solutions under the iPSKRE Power Ecosystem, with dedicated designs for Standard 4 X's Router 3 architecture:
Inquire Now: sales@kreco.com.cn | iPSKRE Power Ecosystem | Starlink-compatible Router 3 / DC-DC / passive PoE OEM/ODM supply (Standard 4 / 4 X / Mini) under development.
Based on Starlink official Specifications & Help Center (Standard 4 X / Gen 3: ~150W proprietary brick to Router 3; Router 3 feeds the V4 dish via 56–57V proprietary passive PoE, pins 1236+ / 4578-; Router 3 tri-band Wi-Fi 6, ~297 m², 2 latching LAN; Bypass Mode under Settings → Advanced) and 2026 configuration references. App menu names may vary by firmware version. Router 3 must remain powered in all cases; third-party power modifications may affect Starlink warranty — keep all original parts.