MADAR III Data Probe – Under the Covers

In my last post I described the MADAR project and the effort to create a worldwide network of sensor nodes to detect UFOs. This post is for the techies who might be more interested in what’s actually going on under the covers with the device itself.

Support the Project

Before I jump in, a few thoughts about my effort to dissect the MADAR probe.

First, it’s a closed project, and I do respect that the director made the decision not to share the hardware or software specifications. A fair amount was probably invested in the engineering and I can understand the desire to preserve any IP.

Second, there’s a mention on the MADAR site that the technology is patented, so fair warning to anyone who wants to recreate one of these devices on their own. The reality is that even if someone managed to build one, a significant part of the project’s value is in having a distributed network of sensors across the globe. In my opinion, it’s just easier to support the project and join the network versus trying to reinvent the wheel.

Now that the PSA is out of the way, let’s jump into the hardware.

MADAR III Probe – The Hardware

Central to the project is the MADAR III Probe. Under the covers, it’s a small single board computer bundled with a tiny 3-axis magnetometer and mounted in a 3-D printed case. When you order the device, you’re asked for location information and it’s mailed to you preconfigured. You just plug it into an ethernet port and it starts to collect EM readings and sends to a server in a central location.

When I opened the case I was surprised to find a Raspberry Pi. It looked to be a 3 Model B+ (which I later confirmed with a cat of /proc/cpuinfo.)

Mounted on the Pi is a daughter board that connects directly to the 40 pin GPIO header. Soldered on the board appears to be 1 or possibly 2 sensors, a relay and a push button switch.

The website documentation is light on the sensor details and the chips themselves are a bit of a mystery because the stamped manufacturing IDs aren’t visible. I’m fairly certain that one is a tiny 3-axis magnetometer because of the data collected. From some additional digging (which I’ll explain later) my guess is that it’s either a QST or Honeywell sensor.

I’m assuming that the second chip is some type of barometric pressure sensor as there’s a mention on the site that this data is available as well.

I’m unaware of any single sensor that can do both, and given that both chips have a similar form-factor, I’m speculating that the second might be a combination 7-axis gyroscope with an integrated altimeter similar to this one. This is a total guess though because although barometric pressure is mentioned, it doesn’t appear to be one of the data points that’s actually exported from the device.

MADAR III Daughter Board – Front
MADAR III Daughter Board – Back

The relay provides a way to wire up an optional external device that can provide an audible alert if the magnetometer detects a field change above the typical background threshold (I.e. Alert! Aliens are overhead!). Your queue to run outside to see if something’s up.

The push button switch presumably just resets the relay to silence the alarm.

Given that the sensors were a bit opaque my next step was to try to logon to the device itself to get for more info.

MADAR III Probe – The Software

Did I mention there’s no login provided? First step was to gain shell access to the device itself. Luckily with physical access to the Pi SD card, it’s relatively straight forward to boot into single user mode and create a login.

Once logged in I discovered a controlling script (compiled in C) named madar_node along with supporting files under the /home/pi user directory. The script is configured to run continually with a second watchdog script called watch.sh that makes sure it’s always running.

The madar_node script takes readings from the magnetometer every minute and sends the data to a central server for reporting. Here are the fields that are collected:

FieldDescription
Node IdX digit unique node ID
Event Typestatus, alert, alertStat, alertStart, alertEnd
Compass (Degrees)Compass heading (0-359)
mGamagnetic field milliGauss
Avg. Ambient mGaAvg Ambient milliGauss
ThresholdmGa threshold for alert status. (I’m not sure how this is calculated, but individual nodes appear to have different values.)
Accel/PressureUnsure of this one. Many magnetometers have a builtin accelerometer, but the pressure is a mystery. The value collected from my node appears to be acceleration only.
DateYYYY-MM-DD
Time%H:%M:%S

Collected sensor data is sent to a server IP that’s referenced in a madar.conf file in the /home/pi directory. The same output is also sent to statusLog.txt in this format:

status,174,0.00,203.48,1.00,2021-10-17,22:00:18,578.41
ack

The script operates in the following way:

  1. Every minute data is collected and the mGa value is compared to the threshold.
  2. If the threshold is not breached, a “status” event is written to the log with the collected sensor values.
  3. If the threshold is breached, the script goes into overdrive. An “alertStart” event is written to the log, 3 additional “alert” events are written immediately to the log, and then data is collected every second for 3 minutes as an “alertStat” event.
  4. After 3 minutes an “End Fastscan” messages is written to the log and then normal one minute data collection resumes.

The madar_node script appears to be a compiled C program. This makes it difficult to get any additional info on how the sensor data is actually collected and calculated. However, using a binary editor I was able to get some additional info from some print statements.

I found a comment within a function that determines whether a QST or Honeywell chip is present. This provided an additional clue to what the sensor might be. For Honeywell, my guess is a HMC5883L 3-Axis digital compass.

Historical data collected by all the nodes are publicly available on the MADAR site. Unfortunately, the reporting is limited in that you can only view the data in a table. There’s no export option or ability to create graphs or charts. To get around this I have my own custom setup (using Splunk) so that I can export the data locally and do my own analysis.

Magnetometers and UFOs

You might be wondering what my thoughts are about the validity of using a magnetometer for UFO detection. I discussed this at length in my previous post, but I thought I’d add some additional color here.

First, for such a small form factor the magnetometer is MUCH more sensitive than I would have imagined. Placing the device anywhere near other electronic equipment greatly impacts the readings. Also, I noticed that just opening a draw of tools 3′ away from the device was enough to send the monitoring script into an alert state.

I ultimately mounted my device on a small shelf in the rafters of my garage to eliminate as much EM noise as possible. This is easily 20′ away from the nearest electronic device and there is very little variability in the electromagnetic field at this location.

Overall, my biggest concern with the project design is the proximity of the sensor to the Raspberry Pi itself. I wouldn’t be surprised that under certain circumstances that the Pi could generate an EM field that would influence the sensor.

Concerns aside, I’ve been collecting data long enough now that I’ve become comfortable with the range of readings and the consistency. This is why when an anomaly does happen it’s a bit of a head scratcher. This is an example of one a few months ago. Like mentioned in my earlier post, I have my very own WOW signal.

I’ve seen many misunderstandings on social media about what this device does and how it operates. With this post and the last, I’ve tried to make the case that there’s merit to this project and hopefully more people will join as a result.

If you liked this content make sure to share on social media!

Hunting UFOs with the MADAR III

If you’ve seen my latest posts you know I’ve spent some quality time wading through the NUFORC UFO sightings database. One thing I’ve learned after analyzing over 98,000 sightings reports spanning almost three decades is that we haven’t learned much of anything about the true nature of UFOs.

What we have is a crap ton of witness testimony. What we don’t have is very much corroborating evidence.

Sure, we do have some intriguing photos, but in today’s digital age, anything can be faked.

Perhaps it’s time for a better approach, and this is why I support the Madar project.

Probable Hoax Photo from Belgium UFO Wave

The MADAR Project

If you haven’t heard of it, the Madar effort is an ambitious attempt to create a worldwide network of sensors that set out to detect the physical traces of UFO activity. As of this writing there are 150 nodes on the network, with the majority located in the continental US.

US MADAR Node Map. Real-time updates can be found here.

The project was conceived by life long UFO researcher and author Fran Ridge. The origins trace back to 1970 with the Madar I and has grown more technically sophisticated over time.

The current iteration is the Madar III data probe, an affordable device that allows anyone to participate in a network that monitors for UFO activity 24/7.

Why MADAR?

Crowd sourcing a network of sensor nodes provides a clever way to corroborate physical anomalies with other sighting reports from the same or nearby locations that might have occurred at the same time.

It also provides a way to alert the node “operators” that an anomaly is occurring in realtime. This way actions can be taken to document the sighting. As in actions I mean like running outside and taking photos.

You might be wondering at this point how exactly does a MADAR node detect UFOs?

Scanning the skies

That’s a good question and where a degree of buy-in is needed in support of the central premise of this project.

Can We Detect UFOs?

Here’s the issue. UFO believers typically fall into one of two camps:

Some people believe the extraterrestrial hypothesis (ETH) that proposes that UFOs are best explained as being physical spacecraft occupied by extraterrestrial life or unmanned probes from other planets visiting earth.

And then there’s the interdimensional hypothesis (IDH) that suggests that UFOs involve visitations from other realities that coexist separately along side our own.

The two theories are not mutually exclusive, but if UFOs turn out to be interdimensional in nature, they’re sure going to be a heck of a lot harder to detect.

If you buy into ETH and that UFOs are physical spacecraft (and therefore obey the laws of physics) then there should be a detectable trace of their existence.

But here’s the enigma with ETH and the gathering of evidence: As our sophistication with surveillance technologies has increased, we haven’t seen a corresponding increase in the number of UFO sightings.

For example with smartphones, everyone essentially has a camera in their pocket at all times. It’s hard to reconcile why there hasn’t been an explosion in documented (as in photographed) sightings in the last decade.

Number of UFO Sightings Reported to NUFORC 2006-2021 (Source: NUFORC Dataset)

Also, our military surveillance technologies have never been more advanced. While we do have the occasional, albeit reluctant admissions by militaries (like the US Department of Defense) that some radar detected events can be classified as “unidentified aerial phenomena”, you would imagine that the frequency of reports would match pace with our technological advancements.

On the other hand, think of the challenges of blanketing our airspace with radar coverage. For example, in the continental US alone there’s over 3 million square miles to protect. That’s a lot of airspace, and perhaps that does leave an opening for a novel approach.

Exploring A New Approach

Perhaps we need a distributed type of coverage that’s better suited for the phenomenon.

This is the void that the MADAR project attempts to fill. Packaged with the MADAR probe is a sensitive 3 axis magnetometer. This gives it the ability to detect a sudden change in the ambient magnetic field and/or compass heading in proximity to the device.

3 Axis Magnetometer Chip

All the MADAR nodes are networked and take sensor readings every few minutes. When the magnetometer detects an abrupt change over the typical background threshold, an alert is sent to a central server.

This novel approach serves a few purposes. First, the device can be configured to send an alert to the owner so that a local observation can be made. Second, the centralized alerting provides a way to automate the reporting of the anomaly to a nationwide UFO sightings database (like the NUFORC). Lastly, it enables correlation of sensor data with unrelated nearby sightings reports or even anomalies reported at the same time across different MADAR nodes.

The Evidence

At this point you’re probably wondering about the validity of the detection approach itself (looking for magnetic anomalies to detect UFOs.) Skepticism here is warranted.

There is at least some evidence that seems to suggest that UFOs can influence electronics and compass readings. A strong enough magnetic field could have that effect. Whether the MADAR sensor is sensitive enough to detect a field change with the range needed to detect a UFO overhead is subject to debate. That would have to be an uber-strong magnetic field. And of course you have to be willing to buy into ETH and that there’s something physical happening that can even be detected.

I can tell you first hand however that I have seen readings from my own MADAR node that I cannot explain. My own WOW signal if you will. Huge magnetic field changes with no appreciable cause – unrelated to weather or local environment. Unfortunately, these have occurred in the middle of the night and I’m not invested enough to run outside in my pajamas with binoculars and a phone.

Magnetic field reading from my Madar III probe – 9/1/2021

The Madar website reports evidence collected from over 500 EM cases with 144 that involve compass deviations. As a participant on the mailing list, I’ve seen mention of a few correlations with actual witness sightings. Perhaps there is something there.

Ultimately my position on the project is that it’s an ambitious step forward in UFO research. By attempting to collect real scientific data from a geographically distributed array of sensors and then correlate to unrelated sightings reports, it provides a way to bolster witness testimonies.

I have definite reservations about using a magnetometer as the primary UFO detection method, but the project opens the door for future efforts using different technologies that can build upon the core premise.

As my readers know, at Enigmatic Devices we like to peak behind the curtains of interesting projects like this. If you’re interested in a deep dive into the technology under the covers with the MADAR III, make sure to check out my next post.

If you’ve enjoyed this content make sure to share on social media!