Will this supply run this module?

Pick a module and a power mode, add the peripherals on the same supply, and say what rail and what PSU you have. The engine holds the rail against the published input voltage window of the board it plugs into — the carrier when you name one, the module when you do not — the power mode against the vendor's maximum module power, and the supply against the sustained node power times a peak factor. It returns FIT, FIT WITH RISKS, NEEDS VALIDATION or NO FIT, with the PSU wattage to buy, the module's power presets and whether powering it over PoE is something the vendor actually documents.

01 · Define the node

Module & power

Module

Loading module registry…

Power mode

Select a module first

Module power

Peripherals

None

5 W

10 W

25 W

Supply

DC rail

5 V

12 V

19 V

24 V

PSU

Not chosen

30 W

65 W

90 W

150 W

DC supply

PoE

Advanced

Peak factor

1.2

1.5 (default)

2.0

Developer kit

Use the bundled adapter

Custom rail

Select a module to continue

03 · How this works

Four checks, one arithmetic step

Input voltage holds the rail against the published window of the board it plugs into: the carrier when you name one, because the carrier regulates the rail down to the module, otherwise the module itself. Both windows are always reported. Module power holds the power mode's watts against the vendor's maximum module power. PSU sizing is the only arithmetic: sustained module power plus peripherals, times a peak factor, against the supply you have or the developer-kit adapter the vendor ships — with neither, the check is UNKNOWN and the result states the wattage to buy. PoE powered device answers whether powering the node over PoE is something the vendor documents at all.

Sourced specifications, labelled estimates

Every voltage window, power ceiling, adapter figure and PoE statement comes from the vendor datasheet or design guide, quoted and linked. The 1.5 peak factor is a class E engineering default and is labelled as such in every result. A figure the vendor does not publish is UNKNOWN, which is why the Thor modules come back NEEDS VALIDATION on the voltage check: no class A source states their input window.

Full rules, the class E default and what invalidates a result: methodology. Raw dataset: datasets/module-power-input.json. Related: Jetson power modes lists every preset; Thermal Feasibility Checker asks whether the enclosure can carry that power away; PoE Node Planner sizes the switch on the camera side.

04 · FAQ

Why is a 12 V rail a failure on an Orin Nano but fine on the developer kit?

The Orin Nano module's VDD_IN is a 4.75–5.25 V rail; the developer kit's carrier board takes 9–20 V at its DC jack and regulates it down. The rail you enter is judged against the board it plugs into: the carrier when you name one, the module when you do not. Both windows are shown either way.

Where does the 1.5 peak factor come from?

It is an engineering default (class E) for inrush and workload peaks above the sustained module power a power mode describes. A power mode is an average envelope, not a ceiling; a supply sized exactly to it browns out on a transient. Override it in Advanced when you have measured your own peak.

Can I power a Jetson over PoE?

No Jetson module documents an integrated IEEE 802.3 powered-device implementation. The Orin Nano developer-kit carrier exposes a PoE header, but it explicitly requires an external converter from the 38–60 V PoE rail down to the module's input window, so the engine reports that path as needing validation rather than as a documented feature. For every other module the answer is a plain no.

Why is the PSU check UNKNOWN?

Because you have not told it what supply you have and the platform is not a developer kit with a published adapter wattage. The result still states the wattage to buy — the sustained node power times the peak factor, rounded up — so the check becomes a purchase, not a guess.