Brick Motor & Sensor System Route Checker
Compare Power Functions, Powered Up/LPF2 and NXT/EV3 connection families before reusing a motor, light or sensor. Software functionality remains separate.
Open tool →Brick electronics · offline connection planning
Map the component, the port and the command.
Plan LEGO motor/sensor reuse, Powered Up port assignments, Power Functions IR addresses and remote/app control paths. No hardware connection required.
Powered Up Port Assignment Planner
Build a named Powered Up hub port worksheet, compare physical and program assignments, catch duplicate sockets and check a scoped two-motor program pair.
Open tool →Power Functions IR Channel & Output Planner
Map Power Functions receiver channels and red/blue outputs, distinguish independent groups from intentional broadcast, and print an eight-address control map.
Open tool →Brick Remote, App & Program Path Selector
Separate PF infrared, Powered Up remote, original app and already-installed program routes. Identify the missing receiver, runtime or supported control program.
Open tool →Different decisions, not one repeated verdict
Component reuse, physical/program port ownership, IR broadcast addresses and human control routes are separate tasks. A correct plug family cannot fix a duplicate program port; an extra hub port cannot give two PF receivers independent commands on the same address.
Try an error you can actually resolve
Example: choose Technic 88012, then compare the distance sensor physically plugged into C with the default program setting D. Four tasks can fit four sockets and still have an incorrect map. Change that program selection to C; for a Pybricks DriveBase, separately identify two different rotation-sensing motor rows.
Offline planning, explicit limits
No Bluetooth scan, motor control, firmware change, power budget or exhaustive model database. LEGO is a trademark of the LEGO Group, which does not sponsor, authorize or endorse this site.