20181117, updated 20220419

The first thing one sees when first viewing the MADAR site is the MADAR Map. On that map are light blue registration dots representing the numbered nodes. The sample node used in this series is 114 at Santa Claus, Indiana. If you use the MADAR site to access the spreadsheets for any node you will see the last readings. See example below. The last 9 readings in the sample below are one minute apart, the newest at the top. That's what a normal spreadsheet will show. When on alert the second column will say alert and the lines will be one-second apart!!!!!

Node Id Event Type Compass (deg) mGa Avg. Ambient mGa Threshold Accel/Pressure Date Time
114 status 119.11 2.62 777.4 27 0.99 2022-04-19 21:57:19
114 status 118.43 0.38 777.4 27 0.98 2022-04-19 21:56:19
114 status 120.84 0.38 777.4 27 0.97 2022-04-19 21:55:19
114 status 119.15 7.88 777.4 27 0.99 2022-04-19 21:54:19
114 status 120.76 6.38 777.4 27 0.99 2022-04-19 21:53:19
114 status 118.96 2.62 777.4 27 0.99 2022-04-19 21:52:19
114 status 119.19 5.62 777.4 27 0.99 2022-04-19 21:51:19
114 recal 0 0 0 27 0 2022-04-19 21:50:20
114 status 117.7 6.75 774.27 27 0.99 2022-04-19 21:50:19

Anyway, on the MADAR Map if you left click on any node dot you will see the pop-up. The sample below is for node 114.

Sample of Pop-Up

This is the node number that we assigned and is the permanent number for that particular device at that location. 

The codeword "status" indicates he last reading was normal and the device is not running on alert. If on alert the codeword would be "alert" and the dot would turn red. And if you had the "sound on" box checked you would hear an audible klaxon if any dot in the world goes on alert.

This is the compass "heading". When someone mounts a MADAR device in a certain location the onboard compass is always pointing north but the heading depends on the orientation. So in this case 120.84 degrees is the normal for that device.

The 0.38 milligaus reading is a real number that is very important.
Our magnetometer reads the earths magnetic field while most hand-held sensors filter this out as you are usually looking for something other that the earth's field.

In the sample it is 27 milligaus (and many times during discussions) this may be described as "shield" or trigger" or "limits" settings, but in reality this is a settings we select for the unit's threshold. We set devices at 30 before shipping so that we can tweak them once they are online at the right coordinates. If the device is plagued with excessive "hits" or if the device fails to show any alerts for periods too long, this number may need to be adjusted by our Tech Support. In some cases the device may have to be moved slightly to a new location. Experience has proven that thresholds of 20-25 have a much better chance of getting a real anomaly.

Here the number is 777.4 This term would require an extensive explanation, so suffice it to say that if the AA is high it means the local field is problematic and will probably mask any effort to detect a real anomaly. As a rule and with experience it has come to be accepted that a reading in excess of 950 milligaus is too high.  In some cases the I-board was too close to the onboard computer, but most of the time the device was just too close to electronics. That's why we recently updated our software so that ops can set up their devices on wifi instead of an Ethernet cable and move them to other locations without wiring/wall issues.

StdDev is as a calibration tool to help find a quiet location.  The higher the deviation the noisier the location. Currently this reading is based on the last 400 mGa data transmissions of the node. This is not ideal and we will be changing that to the average field reading that will be sent back to the server with the new node software. This reading will NOT tell you if you have an abnormally high background reading but it will tell you if it jumps around too much.

Formerly for barometric pressure, we chose to utilize the onboard acceleration sensor. This may turn out to be a valuable piece of equipment to use to determine if a device was bumped or if a UAP affects acceleration readings. It is something we are watching very closely.

The location of the Node is precisely set at the exact coordinates from the exact address. For example, Boise, Idaho has two devices but miles part and two different node numbers. MAKE SURE WE HAVE YOUR EXACT COORDS.

I1.40RBU is NOT the version of the MADAR-III DataProbe device, but the version of the software currently ON the device. All of the devices running today have the new I-board and not the original Q-chip, and are running with the latest software version. The upcoming updates from the server should change the version number upon reboot. 

This shows the last reading logged on the pop-up. The date and time is in Universal Time Code and should be current with any of your other devices using that format. If the time is off on the pop-up, please refresh your screen. If it is still off, the node may have shut down.

Anyone interested in direct participation in either Project MADAR or Project MATCH is  certainly welcome. Please contact me at:

Fran Ridge

Information on MADAR and how to order the MADAR-III DataProbe can be found at: