🎨 Fritzing-Parts: MT6701 Magnetic Encoder Guide

A precision workflow for creating high-quality custom components in Fritzing. This guide documents the exact XML edits and Inkscape settings required to bypass common SVG rendering bugs.

Pro-Tip: A .fzpz file is just a renamed .zip archive. Rename it to access the raw .fzp metadata and SVG source files directly for manual editing.
Downloads
Open-Source MT6701 Part & Full Documentation at GitHub
MT6701 Fritzing Part Preview MT6701 Final Fritzing Render

Quick-Fix Troubleshooting

If your custom part looks "broken" upon import, refer to these common XML/SVG fixes:

SymptomLikely CauseFix Action
Giant/Tiny TextInkscape px unitsDelete "px" from font-size in XML Editor
Black Text OnlyHardcoded fill valueRemove specific fill line in XML tree
Single-Sided PCBIncorrect LayeringNest copper1 group inside copper0
Invisible PartMissing Layer IDMatch top-level group ID to .fzp definition

Advanced Technical Workflow

Creating professional parts requires a 4-stage technical cycle to ensure manufacturing accuracy:

1. XML Metadata (.fzp)

Define pin mappings and internal Buses. If your part has multiple GND pins, linking them in the .fzp file ensures they share the same net in Fritzing.

2. PCB Layer Nesting

For dual-side connectivity, the SVG structure must follow a specific hierarchy: <g id="copper1"> (Top Layer) containing <g id="copper0"> (Bottom Layer). This allows Fritzing to recognize through-hole pads correctly for manufacturing.

Solving the Inkscape Rendering Engine Bugs

Modern Inkscape versions output data that Fritzing's older rendering engine often misinterprets. Use the following logic to sanitize your files:

Recommended Tools: Use FritzingCheckApp to validate your SVGs before import. It automatically detects missing layer IDs and non-standard XML tags.