Brick electronics · offline connection planning
Can this motor or sensor cross LEGO system generations?
Compare Power Functions, Powered Up/LPF2 and NXT/EV3 connection families before reusing a motor, light or sensor. Software functionality remains separate.
Your setup and observations
Similar toy-brick connections can belong to different electrical and control systems. Start with the electronic family, not whether the motor mechanically fits your build.
Work through a concrete example
Example: NXT motor → EV3 brick, direct motor-running goal, identifies a documented family route. Reverse the sensor example to EV3 sensor → NXT brick and it flags the asymmetric support conflict. A PF motor-power connection does not establish readable rotation data.
Connector family first, software function second
The official City FAQ distinguishes Power Functions infrared/control wiring from Powered Up Bluetooth and its changed connectors. A direct PF-to-Powered-Up connection is not established by their shared LEGO brand. Conversely, a supported physical-family route does not prove that every app can read a sensor mode or control position.
The NXT / EV3 exception is directional
Official EV3 support lists NXT and EV3 motors as cross-compatible, and standard LEGO NXT sensors as usable with EV3. EV3 sensors are not supported by the NXT brick. Third-party sensors, driver blocks and unusual component revisions still require their exact documentation.
A working motor is not measured position
For motor position or angle feedback, verify that the exact motor has rotation sensing and that the hub/software can expose it. A basic motor-power lead does not manufacture sensor data. Lights and sensors are different component jobs, not alternative names for a motor.
Adapters are not universal generation bridges
A documented adapter route needs direction, required functions, exact endpoints and software support. This tool does not supply a pinout, resistor value, cable modification or power-source conversion. Unknown adapters remain a verification task, even if their plugs look appropriate.
A useful starting example
The default PF motor to Powered Up direct path is a system conflict. NXT motor to EV3 direct identifies a documented motor-family route; changing that component to an EV3 sensor and receiving brick to NXT demonstrates the asymmetric sensor restriction.