Revision as of 18:32, 16 May 2017

Each stack-able mCookie module uses a set of 27 pins.

The pins usually connect to a Core module's pins. Core modules provide the pins functionality. This is the reason why a Core module type is required in a build. Other modules (non-Core modules) uses / consumes / occupies a pin. This enables the Core module to control, communicate, etc with the stacked module.

When a module uses a pin, it can be thought of as consuming or occupying a pin, which would make other modules attempting to use the same pin unusable. Although, care is taken to avoid conflicts with pin usage. Sometimes pin functionalities overlap between different modules.

NOTE: Multiple Core modules on the same connected stack will interfere with each other as each will try to provide pin functionalities. DUO-V, mBattery, etc are considered the same stack because the pins will be connected across the mirrored pins.

Below is the chart which shows which pins are used for each specific module and can be used to find overlaps. If a conflict or overlap exist it is unlikely that both modules will be usable at the same time for a project. See section Known Conflicts to see a list of already known conflicts.

Examples

Example 1

• A mCookie Core module is picked as a Core module. mCookie Core provides the pins for functionality.
• A mCookie Motor is stacked

Upin27 Layout

Known Conflicts