diff --git a/draft/boards/JuiceBoxZero.png b/draft/boards/JuiceBoxZero.png new file mode 100644 index 0000000..ffaae32 Binary files /dev/null and b/draft/boards/JuiceBoxZero.png differ diff --git a/draft/overlay/JuiceBoxZero.md b/draft/overlay/JuiceBoxZero.md new file mode 100644 index 0000000..5d60f76 --- /dev/null +++ b/draft/overlay/JuiceBoxZero.md @@ -0,0 +1,48 @@ + +#JuiceBox Zero + +JuiceBox Zero is designed specifically for the Raspberry Pi Zero to let you power it from a battery. It’s the simplest way to properly power your Pi Zero with a battery. It is the only battery management board in this form factor that requires no code. With JuiceBox Zero, you get the best solution for instant Pi Zero portability. It comes with an on/off switch, status indicator LED and Pi Zero Camera mount built right in! + +Battery and Raspberry Pi Zero not included. All you need to get started is your JuiceBox Zero, a Raspberry Pi Zero or Zero W, a stacking or non-stacking header connection, and a JST‑compatible, single‑cell lithium‑ion battery + +* Compatible with any 3.7 to 4.2V Lithium-Ion or Lithium-Polymer battery with a JST PH connector, 1A Current Output and 1A Charge rate +* The simplest uninterruptable power supply solution +* Requires a 5V micro USB power supply, and can draw up to 2A. +* Smart power supply selection: it can charge the battery and power the Raspberry Pi at the same time +* Compatible with both Raspberry Pi Zero and Pi Zero W models. Possibly suitable for powering other Pi models (depends on application) +* Integrated on/off switch +* Charge/power status indicator LEDs +* No programming neecessary +* Low power deep-sleep state with wake on interrupt/calendar event +* Compatible with any single cell LiPo or LiIon battery witha JST, PH connector (check out Adafruit's batteries!) diff --git a/draft/overlay/template.md b/draft/overlay/template.md deleted file mode 100644 index 3479bd9..0000000 --- a/draft/overlay/template.md +++ /dev/null @@ -1,67 +0,0 @@ - -#my add-on board - -Use this section to provide additional information such as features, technical parts, install requirements, etc. Please keep this section to the point and avoid copy/paste of marketing blurb - the board's extended description should be primarily neutral and technical. - -The overlay itself uses the following fields, some of which are mandatory, as noted below: - -MANDATORY -* name: the board name as it will appear at pinout.xyz -* class: the class the overlay falls in, 'board' is the most common (use that if in doubt). -* type: the typical applications of the board, i.e 'lcd' (use 'other' if in doubt). If multiple types apply, use a comma separated list (for example, 'adc,motor'). The keywords submitted will be used to filter boards on the site so don't include anything but tags that are relevant to the key functionality of the board. -* formfactor: the board's form factor. Valid values are Custom, HAT and pHAT. Note that an EEPROM is required for HAT specs, use Custom if that is not the case. -* manufacturer: the manufacturer's name. -* description: a description of what the add-on board provides. -* url: the main URL for the product providing detailed technical information about the board. -* pin: an array of the pins used. Do not specify power or EEPROM pins as part of the array! - -DESIRABLE -* pincount: the header pin count, typically 26 or 40 but shims/custom boards are acceptable. -* eeprom: whether the board includes an eeprom (required by 'HAT' specs!). -* power: the supply logic required by the board. Valid values are 'external', '3v3', '5v' and '3v3,5v'. -* i2c: if the board uses i2c, a list of the bus address(es) and device(s) identification. - -OPTIONAL -* image: a top-down image of the board as png with transparency or appropriate placeholder (see image template in board directory). -* github: github repository address. -* buy: URL where the board can be purchased.