Dated 6 May 2022
This is part 1 of 2, a quick set-up guide to help you properly install a MADAR site.
Part Two is "About MADAR" and is an expanded version to explain in more detail what you need to do and why. Most of the time the quick set-up will work fine and not require further tweaking. This paper will get you through possible local issues in the proper order.

Figure 1 - The MADAR DataProbe Device

Basically you are looking for a good E-M quiet place in the room, a place near your router and an a/c outlet, then place the MADAR device down flat.

If you ordered your DAS/speaker from Amazon and have it now, plug it in to one of the USB ports on the MADAR device. If you don't have it yet, skip that portion of the set and go to the next step.

Next, run the appropriate length of Ethernet cable (not supplied) from the device to your router. Then run the power adapter cord from the device and plug it in the nearest outlet.  In most cases you will be up and running and with good numbers. Here is how you find out. Go to your computer and the

Figure 2- MADAR Site Map

When you have the MADAR map in front of you, go to your "node dot", and left-click on it.  But for an example we use the Boise, Idaho site 111. Here is what the pop-up looks like.

Figure 3 - The Pop-Up of Boise, Idaho node 111

As you can see on line 6 the Average Ambient in milligaus is 507.093. This is a good reading. The lower that number, the better are your chances of picking up real anomalies. As that number increases, especially If over 900 milligaus, there is too much stray E-M in the room from numerous devices. The AA is a fairly constant reading and doesn't fluctuate like the field reading in line 4 since it is the sum of the local E-M radiation. We'll work with you to help you get the AA down, but first we want you up and running.

The only way to reduce the AA is to move the device to a more E-M quiet spot in the room, or even an adjacent room, upper or lower floor. But, inches can make the difference. Many Ops have have found that inches really worked. However, some Ops were unable to accomplish this within their designated space with longer Ethernet lines and had to go to wifi, and that was very successful. The point being, over time you should strive to get the AA as low as possible because it will improve your chances of detecting a real anomaly, and that's what we all want to do.

Node Id Event Type Compass (deg) mGa Avg. Ambient mGa Threshold Accel/Pressure Date Time
111 status 122.15 1.5 498.15 30 1.01 2022-05-04 16:28:19
111 status 124.13 1.5 498.15 30 1.02 2022-05-04 16:27:19
111 status 128.22 4.5 498.15 30 1 2022-05-04 16:26:18
111 status 126.59 3 498.15 30 1 2022-05-04 16:25:18
111 status 121.23 2.25 498.15 30 1 2022-05-04 16:24:19
111 status 125.66 4.5 498.15 30 1 2022-05-04 16:23:18
111 status 126.1 1.5 498.15 30 1.01 2022-05-04 16:22:18
Figure 4 - The spreadsheet
The spreadsheet is another way to look at your data. Again we use the Boise, Idaho node. Notice how small the field readings are in column 4 compared to the Average Ambient readings in column 5. (Column 3 is your compass heading. We'll deal with that later).

If you are able to get numbers similar to the ones above, you are up and running and should be good to go. The default threshold is 30 milligaus shown in line 6. When the field reading (line 4) gets to 30 or above, your MADAR will go into alert mode.  Then, what you want to do is have us lower that shield to 25, and eventually 20 if possible. The lower the better. We can't stress that enough.

A MADAR should trigger about once a month at least. This may be a real anomaly, a false alarm by you bumping the device, or a systemic error we call a "10:25 or 11:25" alarm. Depending on your time zone these "10:25 or 11:25" errors will occasionally crop up. For us here at MADAR Operations if we get an alert at 5:25 am, that's 11:25 UTC, and we don't even bother to go into alert procedures. But even those turn out to be a good periodic test and will set off your DAS alarm.  (More on the DAS later)

If a MADAR node does not trigger in 60 days we get an automated server notification telling us we need to lower the node's shield a small amount. If the device triggers too often, the opposite happens and we have to raise the shield a little. If the threshold gets above 30 the device must be moved slightly because it will not be able to detect a real anomaly.

Finally, if for some reason the node goes offline for more than a few hours we get a NOL notice, meaning the device is Not Online. We then contact the operator and have him/her check to see if the power adapter or the Ethernet line has been disconnected, or if they lost their internet connection.

This then is the simple basic set-up instruction sheet. A more-detailed version is available and is called "About MADAR".

Fran Ridge
(812) 490-0094
Information on MADAR and how to order the MADAR-III DataProbe can be found at: