AnyScan209: A Free Mobile App for Real‑Time 2D/3D Magnetic Mapping

[AnyScan209]

There is a depth indicator in the 3D menu, but it only shows the signal scale from 0 to 1024 — meaning the minimum to maximum response based on the scan.
If the scan input is a height‑based scan, then depth can be calculated.

But in magnetometer mode, real depth cannot be calculated directly. Determining depth requires field experience and geophysical knowledge. For example, a small piece of iron at only 0.5 m underground can create a magnetic field strong enough to look like a 25‑meter cavity.

So the AnyScan209 device only shows the real measured values. Actual depth, geological layers, or cavity size cannot be reliably calculated from magnetometer data alone. These require field investigation and geophysics.
Even many software tools that “show depth” are mostly formal and often not accurate.

I prefer to be honest about this rather than give unrealistic expectations.



And despite all these limitations, most ground surveys are still done with magnetometers.
Why?
Because anomalies caused by human activity — cavities, tunnels, mines, buried structures, disturbed soil, and metallic objects — can be detected very clearly in magnetic maps. With the knowledge and experience of a geophysics specialist, these magnetic anomalies can be interpreted, processed, and classified.

A magnetometer gives you the map of the magnetic field, not the depth.
The real depth depends on your geophysical knowledge, your ability to model the anomaly, and your field experience.
That is why two people looking at the same magnetic scan can reach completely different conclusions — one wrong, one correct.

So the device shows the real magnetic data, but the true depth comes from your understanding of geophysics, not from the instrument itself.

[Nikolatech]

in essence, if the cube is 30 cm and there are 3 of them, that is 90÷138=1.53 m, would it be considered approximate

[AnyScan209]

How to Interpret Magnetic Anomalies and Estimate Depth in Magnetometer Surveys


Magnetometers do not measure real depth directly. They only measure the intensity of the magnetic field, and the interpretation depends heavily on the operator’s knowledge, field experience, and understanding of soil behavior. Still, by analyzing the shape of the anomaly, you can get a rough idea of whether a target is shallow or deep.

1. Shallow Anomalies

Shallow targets usually show:

• Sharp, narrow peaks
• Steep gradients
• Strong dipole pattern (positive and negative close together)
• Small anomaly width

Interpretation: Often indicates a small or medium metallic object at shallow depth (30 cm to ~1.5 m).

2. Deep Anomalies
Deep targets typically show:

• Wide, broad peaks
• Smooth, slow gradients
• Dipole poles farther apart
• Large anomaly width

Interpretation: Often corresponds to cavities, tunnels, disturbed soil, or large deep objects.
A Key Field Rule

• Sharp = shallow
• Wide = deep

This is interpretation, not measurement.

3. Important Geophysical Notes

Natural magnetic particles in soil


If you pass soil through a magnet, you will see tiny magnetic particles. Over long periods, these particles become aligned (polarized) by the Earth’s magnetic field (north–south).
Disturbed soil creates anomalies


When soil is:

• excavated
• refilled
• mixed
• compacted
• or otherwise disturbed

its natural magnetic alignment is broken. This creates a magnetic anomaly that a magnetometer can detect.
In areas without iron-rich stones


If the ground contains no iron-bearing rocks, magnetic anomalies become more predictable. In such environments, anomalies often point to:

• cavities
• tunnels
• old excavations
• disturbed soil layers

This makes interpretation easier and more reliable.

4. Real Magnetic Physics (Explained Clearly)

Every magnetic object — even a small piece of iron — creates magnetic field lines around itself.

Here is how these lines behave: Closer to the source

• Field lines become dense and tightly packed
• Magnetic intensity increases sharply
• The anomaly appears strong and compressed

Farther from the source

• Field lines spread out and weaken
• Magnetic intensity decreases smoothly
• The anomaly appears wide and stretched

This is why a magnetometer cannot directly tell you the depth:

• A small shallow object can produce a strong, tight anomaly
• A large deep object can produce a similar-looking anomaly

The device only sees field strength, not distance.

5. Research, Expertise, and Collaboration

Many studies have been done on magnetic surveys, and the best approach is:

• Consult a geophysics specialist
• Share your own field experiences with others
• Compare results and interpretations

When knowledge and real-world data are combined, the conclusions become far more scientific and accurate.

6. The Real Ratio: Software vs. Experience
In practical fieldwork:

• 5% = device + software
• 95% = experience, geophysics knowledge, soil understanding, and field interpretation

A magnetometer only provides raw magnetic data. Correct interpretation depends almost entirely on the operator.

[ivconic]

...But in magnetometer mode, real depth cannot be calculated directly. Determining depth requires field experience and geophysical knowledge...

Of course.
But there are some manufacturers of such equipment that add "depth measurement" to their applications and this introduces general confusion to most lay clients.
I do several different magnetometer/gradiometer projects and I often have trouble explaining to people that this is practically impossible in instant field work, as most amateur "archaeologists" normally practice.
Such depth assessments do more harm than good.

[etznab]

Does anyone know about DIY built-it magnetometer? That I can be used with this app AnyScan209

Thanks

[Omerta 1312]

Nice application, and I specifically use it with the EPE magnetometer (I have added a Bluetooth HC-06) to transfer data to my own application that I created. So, our friend’s application does have nice graphics, but it still needs some work. I didn’t like that it doesn’t accept negative values such as -25 / -50 / -100. On my magnetometer it only reads positive values, and these must be above 512 for the graph to show that there is a target; otherwise nothing appears.

Can you improve this without setting a fixed zero point at 512, and make the application read all values? Instead of 0 to 1024, you could set -1024 as the maximum negative, 0 as the center (the zero reference), and +1024 as the positive, so that the application reads all values correctly.

For example, in a test I did from 20 nT to 400 nT on a metallic object, you could barely see it on the graph. To see it clearly, the nT value had to be above 550 for the target to appear clearly. If you improve these things, it will be a very good application.

[latcakir]

Nice application, and I specifically use it with the EPE magnetometer (I have added a Bluetooth HC-06) to transfer data to my own application that I created. So, our friend’s application does have nice graphics, but it still needs some work. I didn’t like that it doesn’t accept negative values such as -25 / -50 / -100. On my magnetometer it only reads positive values, and these must be above 512 for the graph to show that there is a target; otherwise nothing appears.

Can you improve this without setting a fixed zero point at 512, and make the application read all values? Instead of 0 to 1024, you could set -1024 as the maximum negative, 0 as the center (the zero reference), and +1024 as the positive, so that the application reads all values correctly.

For example, in a test I did from 20 nT to 400 nT on a metallic object, you could barely see it on the graph. To see it clearly, the nT value had to be above 550 for the target to appear clearly. If you improve these things, it will be a very good application.

I believe that increasing sensitivity by adding a calibration range on the microcontroller, measuring in a narrow range over 12 bits, and then comparing this measurement with the map() function in the Arduino will achieve your goal.

[latcakir]

Is it compatible with the visualizer data structure?

[latcakir]

Hello. I want to connect external data to my Arduino via Bluetooth, but the data isn't changing. The sensor data values change when the internal sensor menu is selected.

[latcakir]

Dear friend. I've got it working. Thanks for sharing.

//------------------------------------
// Arduino Example
//------------------------------------
#include <SoftwareSerial.h>
SoftwareSerial BTSerial(10, 11); // RX | TX


int sendButton = A0; // Send button (digital input)
int adcPin = A1; // ADC input
int value = 0;

const int LED_PIN = 13; // Kart üzerindeki dahili LED


void setup() {

BTSerial.begin(9600);
// Çıkış pinlerini ayarla
pinMode(LED_PIN, OUTPUT);
pinMode(sendButton, INPUT);
Serial.begin(9600);
}

void loop() {

value = analogRead(adcPin); // 0–1023
if (digitalRead(sendButton) == HIGH) {
Serial.println(value);
BTSerial.println(value);
delay(2000); // 1 seconds
}
}