RAKwireless · Design sources

WisMesh Pocket V2

A starting point for your own build.

Reference materialRevision needs review

Catalogue-linked files and nearby design dependencies. The paths may cover multiple revisions; compatibility has not been established.

Download build brief

0 pinned files · 0 repositories. We have not built and tested a reproduction from these files.

What’s published

Source evidence, piece by piece

Editable schematic: Needs review
Editable PCB: Not recorded
Bill of materials: Not recorded
Fabrication files: Not recorded
Enclosure: Not recorded
Firmware source: Not recorded
Build instructions: Needs review

The design files

2 references

Showing 2 of 2 references

RAK4631 core-module schematic diagram (reused inside Pocket V2)images.docs.rakwireless.comSchematics · External reference
WisMesh Pocket V2 Getting Started guidedownloads.rakwireless.comDocumentation · External reference

Before you build

Know the gaps.

Editable circuit schematic not verified.
Editable PCB layout not verified.
A complete bill of materials has not been verified; the catalogue chip list is not a BOM.
Ready-to-manufacture Gerbers and drill files have not been verified.
A complete matching enclosure design has not been verified.
Firmware source and flashing instructions need review.
Assembly and test instructions have not been reviewed.
Hardware-specific licence scope has not been reviewed. A firmware or repository licence alone does not establish it.
Compatibility between board, enclosure and firmware revisions has not been reviewed.

Rights & attribution

Licence scope needs review

Published files alone do not establish permission to reproduce a design. Follow each source’s licence.

For your agent

Start with the evidence.

Keep the build brief with your project. It includes source revisions, licences, open questions and space for your own build log.

Source manifest (JSON) Connect through MCP

Keep the original sources.

Downloads with a record of origin

Full repository archives can include other device revisions. Git submodules and large-file storage objects may need separate downloads. Preserve upstream licence and attribution files.