Skip to the content
2 layers45 × 15.8 mmModule NanoSIM, the printed circuit board in 3D

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

Size
45 × 15.8 mm
Copper layers
2
Thickness
1.6 mm
Parts
3
Nets
7
Pads
21
Tracks, vias
29, 28
Pours
1
Routed
Yes
KiCad
KiCad 7 (file 20221018)
Created
9 Jun 2023
Updated
10 Jun 2023

Overview

Module NanoSIM 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 × 15.8 mm with 3 parts on 7 nets, routed with 29 tracks and 28 vias.

Its parts include 2 connectors and 1 capacitor.

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

3
QtyValueFootprintReferences
1100nFCapacitor_SMD:C_0805_2012MetricC1
1Conn_01x06_PinConnector_PinHeader_1.27mm:PinHeader_1x06_P1.27mm_HorizontalJ2
1SIM7100-6-1-15-00-A_REVCLib_Hien:microSIM_CardJ1

More from Blackcastus/ESP32_A7670

2
  • 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.

    188 parts

Similar boards

  • 2 layers40 × 30 mmBlinky, the printed circuit board in 3D

    Blinky

    earthtojake/text-to-cad

    Design physical products with AI

    3 parts26kMIT
  • 2 layers51.9 × 16 mmPassive2-rpi non standard adapter, the printed circuit board in 3D

    Passive2-rpi non standard adapter

    hzeller/rpi-rgb-led-matrix

    Controlling up to three chains of 64x64, 32x32, 16x32 or similar RGB LED displays using Raspberry Pi GPIO

    3 parts4.4kGPL-2.0
  • 2 layers16.3 × 16.3 mmSensor, the printed circuit board in 3D

    Sensor

    scottbez1/splitflap

    DIY split-flap display

    3 parts4.2k
  • 2 layersSub, the printed circuit board in 3D

    Sub

    atopile/atopile

    Design circuit boards with code! ✨ Get software-like design reuse 🚀, validation, version control and collaboration in hardware; starting with electronics ⚡️

    3 parts4kMIT
  • 2 layers85 × 30 mmDual stomp, the printed circuit board in 3D

    Dual stomp

    torvalds/GuitarPedal

    Linus learns analog circuits

    3 parts2.5kGPL-2.0
  • 2 layers124.5 × 33.7 mm172319-1 connector, the printed circuit board in 3D

    172319-1 connector

    rusefi/rusefi

    rusefi - GPL internal combustion engine control unit

    3 parts1.2k
  • 2 layers10.5 × 83 mmProgrammingAdapter, the printed circuit board in 3D

    ProgrammingAdapter

    stuartpittaway/diyBMSv4

    Version 4 of the diyBMS

    3 parts1.1k
  • 2 layers21.2 × 51.3 mmPico reset, the printed circuit board in 3D

    Pico reset

    hackclub/sprig

    🍃 Learn to code by making games in a JavaScript web-based game editor.

    3 parts1.1kMIT

Questions

How big is the Module NanoSIM PCB?

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

What parts does the Module NanoSIM use?

3 parts. 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 Module NanoSIM KiCad files?

From the Blackcastus/ESP32_A7670 repository on GitHub, at the commit this page was made from: the board is Hardware/Module_NanoSIM/Module_NanoSIM.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 Module NanoSIM design in my own project?

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