Hello everyone,
I want to share an idea that might be interesting for people working on Pulse Induction (PI) metal detectors, especially hobby builds.
This is not a finished project or a specific implementation, but more of a concept that anyone can experiment with or improve.
Problem we all face
Most hobby PI detectors today are still quite limited in one area:
poor target discrimination
false signals caused by soil or mineralization
inconsistent behavior between different builds
heavy reliance on audio interpretation and user experience
Even when the detector works, interpreting the signal correctly is often the hardest part.
Core idea
Instead of focusing only on “detect or not detect”, the idea is to add a layer that tries to interpret the signal itself.
The PI decay signal contains information, but usually we only use it in a very simple way.
The proposal is to:
extract a small set of meaningful characteristics from the decay response
instead of using the full raw waveform
and then interpret those characteristics in a smarter way
This interpretation layer could be implemented using simple algorithms or very small machine learning models (TinyML), depending on the builder’s preference.
General system concept
Coil → Analog front-end → Microcontroller → Feature extraction → Interpretation layer → Output
The key point is that the “intelligence” is not in the analog part, but in how the signal is described and interpreted digitally.
Data and learning idea
Another interesting direction (if someone wants to explore it) is the idea of building a shared dataset from hobby PI builds.
This could include:
different coil designs
different environments and soil conditions
different targets
Instead of storing full waveforms, the dataset could focus on extracted features plus the known outcome.
This could later be used to train a simple model externally and deploy it back to microcontrollers.
Front-end discussion
One important open question is the analog front-end design.
Since everything depends on the decay signal quality, the front-end must be:
stable
clean enough for analysis
not overly processed
suitable for digital sampling
There are different existing approaches in hobby designs, and it would be interesting to understand which type of front-end works best for preserving useful signal information.
Open questions
I would like to hear opinions from experienced builders on:
Is feature-based interpretation of PI signals actually useful in practice?
Can it realistically improve discrimination, or are limitations mostly physical?
Would a shared dataset from hobby builds be meaningful or too inconsistent?
What kind of front-end design best supports digital interpretation?
Final note
This is not a defined project, just an idea that might be worth exploring by anyone interested in improving PI detector signal interpretation. If someone finds it useful, feel free to adapt it, modify it, or ignore parts of it completely
I want to share an idea that might be interesting for people working on Pulse Induction (PI) metal detectors, especially hobby builds.
This is not a finished project or a specific implementation, but more of a concept that anyone can experiment with or improve.
Problem we all face
Most hobby PI detectors today are still quite limited in one area:
poor target discrimination
false signals caused by soil or mineralization
inconsistent behavior between different builds
heavy reliance on audio interpretation and user experience
Even when the detector works, interpreting the signal correctly is often the hardest part.
Core idea
Instead of focusing only on “detect or not detect”, the idea is to add a layer that tries to interpret the signal itself.
The PI decay signal contains information, but usually we only use it in a very simple way.
The proposal is to:
extract a small set of meaningful characteristics from the decay response
instead of using the full raw waveform
and then interpret those characteristics in a smarter way
This interpretation layer could be implemented using simple algorithms or very small machine learning models (TinyML), depending on the builder’s preference.
General system concept
Coil → Analog front-end → Microcontroller → Feature extraction → Interpretation layer → Output
The key point is that the “intelligence” is not in the analog part, but in how the signal is described and interpreted digitally.
Data and learning idea
Another interesting direction (if someone wants to explore it) is the idea of building a shared dataset from hobby PI builds.
This could include:
different coil designs
different environments and soil conditions
different targets
Instead of storing full waveforms, the dataset could focus on extracted features plus the known outcome.
This could later be used to train a simple model externally and deploy it back to microcontrollers.
Front-end discussion
One important open question is the analog front-end design.
Since everything depends on the decay signal quality, the front-end must be:
stable
clean enough for analysis
not overly processed
suitable for digital sampling
There are different existing approaches in hobby designs, and it would be interesting to understand which type of front-end works best for preserving useful signal information.
Open questions
I would like to hear opinions from experienced builders on:
Is feature-based interpretation of PI signals actually useful in practice?
Can it realistically improve discrimination, or are limitations mostly physical?
Would a shared dataset from hobby builds be meaningful or too inconsistent?
What kind of front-end design best supports digital interpretation?
Final note
This is not a defined project, just an idea that might be worth exploring by anyone interested in improving PI detector signal interpretation. If someone finds it useful, feel free to adapt it, modify it, or ignore parts of it completely

Comment