title: Device Configuration

Device Configuration

Pin layout ” shield standards” are another advantage in keeping things simple. For example, if you stack a TT Caernarfon Castle  on a Lolin S2 Mini , all the user needs to know (and specify in their “configuration”) is that they are using a Caernarfon Castle. Then they can use the NeoPixel / StemmaQT / IR receiver / servos provided with that board without having to care about what pins are needed to work with them. Internally, the framework has a “shield definition”, and each type of (supported) controller which is compatible with that shield has a mapping to associate the actual pins used. So if the swap out the S2 Mini with a Lolin S3 Mini  or a LilyGo T-OI Plus , everything still “just works” without any changes to their project code (although they do have to install the framework and copy their project config over - “magic” only goes so far…)