Start with the electronics, not the brick shape
A construction model can contain electronics from different generations. That does not make a Power Functions plug, a Powered Up/LPF2 connector and a Mindstorms connection interchangeable. Record the source component, receiving hub and function you actually need before buying a lead. A motor spinning and a program reading its angle are different outcomes.
Reuse can be asymmetric
The official NXT/EV3 table permits motors across those two families, while EV3 sensors are not supported by an NXT brick. The reverse sensor direction is supported in the documented scope. The system-route checker makes that directional distinction visible, without extending it to every app, firmware feature, light or undocumented adapter.
Check the wiring against the program
Count only external ports on the selected finite profile: City 88009, Technic 88012 or SPIKE Large Hub 45601. Give each independent active task one physical port and the port selected in its program. A sensor on C while the program reads D is a mapping error even when the total number of tasks fits. A second task cannot simultaneously own the same external socket in this worksheet.
A motor pair is not one cable
The optional DriveBase rule belongs specifically to an already-installed Pybricks runtime. Its left and right tasks need two different rotation-sensing motors and valid distinct port assignments. A basic DC motor, a light, a repeated row or an unknown component cannot silently become the second measured motor. No wheel geometry, power capacity or mechanical synchronization is inferred.
Model IR as broadcast addresses
A stock Power Functions receiver has one channel selector shared by its red and blue outputs. Two receivers using the same channel and color hear the same address. Name the intended command group on each active output: different groups sharing an address conflict; matching groups can intentionally share commands. The same name on different addresses does not automatically link them.
Choose the human control path separately
Motor-to-hub family alignment cannot prove handset-to-hub support. A PF IR handset needs the matching receiving path. City 88009 with Remote 88010 has a documented stock route; not every Bluetooth hub is assumed to have that route. A stock app and an already-installed custom runtime are different systems. Consult the exact supported app/device guide; the site never scans or pairs Bluetooth.
Keep the worksheet useful outside the browser
Copy or print preserves the named tasks, assignments, entered selections, page URL and confidence boundary. Optional blank receivers are unused; include every relevant receiver in the shared control area before interpreting a collision-free result. Workbench limits are explicit, not a certification that an omitted model or adapter works.