Skip to the content
2 layers45 × 172 mmPh portable refrigerator v2 hw, the printed circuit board in 3D

Ph portable refrigerator v2 hw

Blackcastus/ESP32_A7670

To make it easy for you to get started with GitLab, here's a list of recommended next steps.

Size
45 × 172 mm
Copper layers
2
Thickness
1.6 mm
Parts
188
Nets
213
Pads
704
Tracks, vias
1,567, 521
Pours
5
Routed
Yes
KiCad
KiCad 7 (file 20221018)
Created
9 Jun 2023
Updated
10 Jun 2023

Overview

Ph portable refrigerator v2 hw is an open-source printed circuit board by Blackcastus, from the Blackcastus/ESP32_A7670 repository on GitHub. It is a 2-layer board of 45 × 172 mm with 188 parts on 213 nets, routed with 1,567 tracks and 521 vias.

It is built around the ESP32-WROOM-32, MAX485ED and NEO-M8M, with the CP2102-GM, TPS5430DDAR and AMS1117-3.3 among its other parts. Its parts include 66 resistors, 48 capacitors, 13 transistors, 12 diodes and 11 ICs. It belongs with the ESP32 boards of this library.

Main components

9

README

Hardware/power_v2/README.md

ph_portable_refrigerator_hw

Getting started

To make it easy for you to get started with GitLab, here's a list of recommended next steps.

Already a pro? Just edit this README.md and make it your own. Want to make it easy? Use the template at the bottom!

Add your files

text
cd existing_repo
git remote add origin https://gitlab.com/phuonghai_rd/ph_portable_refrigerator_hw.git
git branch -M main
git push -uf origin main

Integrate with your tools

Collaborate with your team

Test and Deploy

Use the built-in continuous integration in GitLab.


Editing this README

When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to makeareadme.com for this template.

Suggestions for a good README

Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.

Name

Choose a self-explaining name for your project.

Description

Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.

Badges

On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.

Visuals

Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.

Installation

Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.

Usage

Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.

Support

Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.

Roadmap

If you have ideas for releases in the future, it is a good idea to list them in the README.

Contributing

State if you are open to contributions and what your requirements are for accepting them.

For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.

You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.

Authors and acknowledgment

Show your appreciation to those who have contributed to the project.

License

For open source projects, say how it is licensed.

Project status

If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.

Parts

188
QtyValueFootprintReferences
121kResistor_SMD:R_0805_2012MetricR1, R2, R10, R15, R16, R17, R18, R26, R38, R45, R46, R47
9100nFCapacitor_SMD:C_0805_2012MetricC3, C5, C16, C26, C40, C42, C44, C45, C49
910kResistor_SMD:R_0805_2012MetricR5, R7, R11, R12, R20, R21, R22, R58, R59
94.7KResistor_SMD:R_0805_2012MetricR13, R19, R39, R49, R53, R55, R62, R63, R64
810uFCapacitor_SMD:C_0805_2012MetricC1, C6, C15, C18, C22, C29, C41, C43
722RResistor_SMD:R_0805_2012MetricR28, R29, R33, R40, R41, R42, R43
6C1815Package_TO_SOT_SMD:SOT-23Q1, Q3, Q5, Q8, Q10, Q11
5100nFResistor_SMD:R_0805_2012MetricC4, C12, C14, C25, C38
410uFResistor_SMD:R_0805_2012MetricC11, C13, C28, C39
410uFResistor_SMD:R_2010_5025MetricC2, C7, C9, C10
4C1815_SOT23Package_TO_SOT_SMD:SOT-23Q2, Q7, Q12, Q13
3100uFCapacitor_Tantalum_SMD:CP_EIA-6032-15_Kemet-UC20, C31, C47
310KResistor_SMD:R_0805_2012MetricR48, R51, R52
31KResistor_SMD:R_0805_2012MetricR37, R67, R69
31uFResistor_SMD:R_0805_2012MetricC23, C24, C30
322pFResistor_SMD:R_0805_2012MetricC32, C33, C34
3blueLED_SMD:LED_0805_2012MetricD6, D7, D13
2100RResistor_SMD:R_0805_2012MetricR3, R6
210nFResistor_SMD:R_0805_2012MetricC8, C27
218pFResistor_SMD:R_0805_2012MetricC36, C37
2470RResistor_SMD:R_0805_2012MetricR60, R61
247KResistor_SMD:R_0805_2012MetricR65, R66
25.1KResistor_SMD:R_0805_2012MetricR56, R57
27pFResistor_SMD:R_0805_2012MetricC17, C21
2D_TVSDiode_SMD:D_SMAD10, D11
2FuseLib_Hien:Fuse_SMD_1812F1, F2
2SS3x_SMADiode_SMD:D_SMAD1, D3
2SolderJumper_2_OpenJumper:SolderJumper-2_P1.3mm_Open_Pad1.0x1.5mmJP2, JP3
110KCapacitor_SMD:C_0805_2012MetricR4
110RResistor_SMD:R_0805_2012MetricR34
110kCapacitor_SMD:C_0805_2012MetricR25
110k1%Resistor_SMD:R_0805_2012MetricR9
110pFCapacitor_SMD:C_0805_2012MetricC48
1120RResistor_SMD:R_0805_2012MetricR54
1120R/1%Resistor_SMD:R_0805_2012MetricR24
114.7456 MHzCrystal:Crystal_HC49-4H_VerticalY2
115uHInductor_SMD:L_Bourns_SRR1260L2
11N4007_T7Diode_SMD:D_SOD-123FD12
11N4148_T4Diode_SMD:D_SOD-123D9
11uFCapacitor_SMD:C_0805_2012MetricC19
12.2KResistor_SMD:R_0805_2012MetricR50
122RCapacitor_SMD:C_0805_2012MetricR27
122uHResistor_SMD:R_0805_2012MetricL3
1240R/1%Resistor_SMD:R_0805_2012MetricR23
12SC1815-HFPackage_TO_SOT_SMD:SOT-23Q9
132.768Crystal:Crystal_DS26_D2.0mm_L6.0mm_HorizontalY1
133pFCapacitor_SMD:C_0805_2012MetricC46
14.7kResistor_SMD:R_0805_2012MetricR31
1400RResistor_SMD:R_0805_2012MetricR36
147kResistor_SMD:R_0805_2012MetricR30
14k7 1%Resistor_SMD:R_0805_2012MetricR14
15.1VDiode_SMD:D_SOD-123D4
1680RResistor_SMD:R_0805_2012MetricR8
1810RResistor_SMD:R_0805_2012MetricR32
1AMS1117-3.3Package_TO_SOT_SMD:SOT-223-3_TabPin2U3
1AO3400APackage_TO_SOT_SMD:SOT-23Q6
1AO3400APackage_TO_SOT_SMD:SOT-23-3Q4
1Buzzer-DeviceBuzzer_Beeper:Buzzer_12x9.5RM7.6BZ1
1CP2102-GMLib_Hien:CP2102U11
1Conn_01x03_PinConnector_JST:JST_EH_S3B-EH_1x03_P2.50mm_HorizontalJ14
1Conn_01x04Connector_JST:JST_EH_S4B-EH_1x04_P2.50mm_HorizontalJ12
1Conn_01x06_PinConnector_PinHeader_1.27mm:PinHeader_1x06_P1.27mm_HorizontalJ3
1Conn_02x08_Odd_EvenConnector_PinSocket_2.00mm:PinSocket_2x08_P2.00mm_Vertical_SMDJ7
1DS1307Z+_SMDPackage_SO:SOIC-8W_5.3x5.3mm_P1.27mmU4
1ESP32-WROOMLib_Hien:MODULE_ESP32-WROOM-32U1
1ExtraConnector_PinHeader_2.54mm:PinHeader_1x04_P2.54mm_VerticalJ13
1ExtraConnector_PinHeader_2.54mm:PinHeader_1x03_P2.54mm_VerticalJ10
1GPSLib_Hien:Antenna_RFAE1
1Header_4P_2.54mmLib_Hien:Header_4P_2.54mmJ8
1L600RInductor_SMD:L_0805_2012MetricL1
1M7Diode_SMD:D_SMAD8
1MAX31865_TQFNPackage_DFN_QFN:QFN-20-1EP_5x5mm_P0.65mm_EP3.35x3.35mmU6
1MAX485Package_SO:SO-8_3.9x4.9mm_P1.27mmU10
1MIC29302WUPackage_TO_SOT_SMD:TO-263-5_TabPin3U5
1NEO-M8MLib_Hien:XCVR_NEO-M9N-00BU7
1REDLED_SMD:LED_0805_2012MetricD5
1SC16IS750IBS,128Lib_Hien:QFN50P400X400X100-25NIC1
1SIM_COM_A7670Lib_Hien:SimCom_A7670U8
1SolderJumper_3_Bridged12Jumper:SolderJumper-3_P2.0mm_Open_TrianglePad1.0x1.5mmJP1
1TPS5430DDARPackage_SO:SOIC-8-1EP_3.9x4.9mm_P1.27mm_EP2.29x3mm_ThermalViasU2

The 169 most common of 188 parts.

More from Blackcastus/ESP32_A7670

2
  • 2 layers45 × 15.8 mmModule NanoSIM, the printed circuit board in 3D

    Module NanoSIM

    Blackcastus/ESP32_A7670

    To make it easy for you to get started with GitLab, here's a list of recommended next steps.

    3 parts

Similar boards

  • 2 layers77.5 × 48 mmWeatherStation, the printed circuit board in 3D

    WeatherStation

    Gleb-Vlasov/WeatherStation

    WiFi-connected weather station on a custom ESP32 PCB — BME280 sensor, modular display, USB-C. Built from scratch in KiCad.

    46 partsMIT
  • 2 layers93 × 63 mmControl board hw, the printed circuit board in 3D

    Control board hw

    nhantt92/Timer-RTC-STM32-Tm1638

    Timer-RTC-STM32-Tm1638

    127 parts6
  • 2 layers115.8 × 48.3 mmRV Fan, the printed circuit board in 3D

    RV Fan

    silverchris/opentasticfan

    55 parts
  • 4 layers70 × 50 mmTimekeeper, the printed circuit board in 3D

    Timekeeper

    liam-tirpitz/TickTock

    A custom ESP32-based clock platform driving WS2812B/NeoPixel LED displays. Firmware and PCB are display-agnostic, supporting any addressable LED clock with minimal adjustments.

    57 parts
  • 4 layers130 × 105 mmHomeDeck, the printed circuit board in 3D

    HomeDeck

    Kilan777/HomeDeck

    Jarvis HomeDeck: a Raspberry Pi CM4 carrier board and voice-assistant software for a 7-inch smart display (KiCad hardware, generated from Python, plus the Python/JS assistant)

    228 parts1
  • 4 layers91.6 × 84.4 mmSDU V1, the printed circuit board in 3D

    SDU V1

    bruinformula/sdu-pcb

    Suspension Data Unit

    237 parts
  • 2 layers100 × 85 mmESP32 MediaCarrier routed, the printed circuit board in 3D

    ESP32 MediaCarrier routed

    xmyoot/esp32-media-carrier

    ESP32 multimedia carrier board with 7–24 V DC buck regulator, 3.2 W Class-D I2S audio amp, WS2812 LED ring driver, and SPI TFT display header

    97 partsMIT
  • 2 layers76 × 95.8 mmSupervisor, the printed circuit board in 3D

    Supervisor

    kaminaris/GigaESC

    97 parts47

Questions

How big is the Ph portable refrigerator v2 hw PCB?

It measures 45 × 172 mm and has 2 copper layers, 1.6 mm thick.

What parts does the Ph portable refrigerator v2 hw use?

188 parts, built around the ESP32-WROOM-32, MAX485ED, NEO-M8M and CP2102-GM. The full list of its parts is on this page, with links to each part's symbol and footprint where PCBKit's library has them.

Where can I download the Ph portable refrigerator v2 hw KiCad files?

From the Blackcastus/ESP32_A7670 repository on GitHub, at the commit this page was made from: the board is Hardware/power_v2/ph_portable_refrigerator_v2_hw.kicad_pcb and its schematic Hardware/Module_NanoSIM/Module_NanoSIM.kicad_sch. PCBKit opens the board in the browser, with nothing to install.

Can I use the Ph portable refrigerator v2 hw design in my own project?

Its repository states no licence, so its author keeps all rights: ask Blackcastus before reusing the design.