Updated 15 Feb 2018
This short paper is provided mainly for the quick and proper set-up of the MADAR-III DataProbe. Separate papers will go into more detail about how the DataProbe works, why it works, how to use the data,  how to set up wifi and an "ADT" panel for additional equipment for use with the newer MADAR-III-B.

Be advised that these devices can't be transferred or sold to someone else without us knowing it because they are specifically programmed for the owner and the exact location in latitude and longitude.

The first thing you need to do is obtain an appropriate length Ethernet cable. If possible, pick a location in your room that will be several feet away from electronics. You will need an AC outlet within 5' of the device or a small extension cord, and an Ethernet cable in the neighborhood of 5-6 feet long or longer. (One owner ran his 25' away!) You can locate a good "quiet" spot by tuning a transistor radio to the left end of the AM dial. Walk around the room and listen to what you can pick up! You will be amazed.
If you would place an EM meter over your device it could read between zero and 1.5 milligaus and that would be great. A reading showing an RF greater than that, or a "noisy" AM radio signal, will lessen your chance of detecting a change in the earth's geomagnetic field. It is not as complicated as it sounds and we'll get you there.

The equipment that you have in and near your room will vary depending on your lifestyle. You may have a number of devices located in your home or office, some of them plugged into your router and may not be in a high RF or EM area. Some may be near computers, monitors, printers, other appliances, maybe even near LED lights which might be turned on only occasionally (closet LED lights) and produce intermittent RF. The point is, the E-M or RF loop can mask the low geomagnetic field and make detection of an anomaly next to impossible. Once you determine you have an issue, you need to move your device out of that loop.  But sometimes it only takes inches, not feet. Setting your limits shield high enough to "cover" a high EM or RF loop will lesson your signal to noise ratio and your device will give you a blue light a lot longer than others on the network. You don't want to put duck tape on a mouse trap.

When your DataProbe arrives, carefully place the device flat down on the floor or shelf you selected and make sure the device and the wires won't be jogged. The slightest movement could trigger the device. Connect your Ethernet cable to your router and then to the device in the Ethernet socket on the right side of the device. On the front of the device, on the left hand corner, you will notice a very small cell-phone-like female jack. Plug the very small male connector into this jack, then
plug the adapter into the nearest 110 VAC outlet. Do not move the device from here on in.  At this stage don't worry about orientation. You are powering up a plug and play device and the unit is connecting to the MADAR Server.

The red LED on the corner opposite the Ethernet jack is the PSI (power status indicator) and should be on and steady all the time. If it blinks, this indicates the device isn't getting the 3 amps it needs to operate properly. Care should be taken to make sure that other adapters you might have lying around don't get mixed up with this particular one.
The LED that is blinking near the Ethernet jack is normal and shows data transfers.

On your computer go to:

MADAR Site Map

Disregard the user and password prompts for now and scroll down the MADAR Display like the one above. Using your mouse you can drag the image of the U.S. up, down, left and right. Using the "+" and "-" at the upper left you can zoom in and out as you wish. Getting the whole U.S. in view is very helpful but when looking at your area it might be a tight situation with nearby nodes and you may want to pump it up a little. By now your device should be online and you should see a light blue dot at your geographic coordinates. The server has automatically given you your "Node Number". By left-clicking on ANY node you can see the "pop-up" which gives THAT MINUTE'S last readings.


Note the Universal Time Code at the bottom. This pop-up changes every minute. This is Node 10. At this point you are probably wondering what the other numbers mean. And your light blue dot may turn red at any time which is alert status. We'll get to all that. But right now its important to know that your device in normal status mode is looking at the  data and displaying it every minute ON THE POP-UP and time-dating it. It is also being stored on your spreadsheet.


All the while the datalogger spreadsheet is running with the most recent alert data displayed at the top and the beginning of the event displayed at the bottom. As you can see, once your device goes into alert mode the data rate jumps to once PER SECOND.

Column 1 is the Node number.
Column 2 is the "status" mode and the actual word "status" in the column shows when the device was armed and ready. AlertStart begins an alert and is followed by "Alert" plots ramped to 1 per second. After the alert (AlertEnd) the logging slows to 1/min once again.
Column 3 is the compass heading. With our plug and play system whatever heading is displayed at status would actually be North and the normal reading.
Column 4 is the geomagnetic reading in milligaus. This is the most important reading and is the basis for the detection of an anomaly, even though we have documented over a 150 compass needle correlations.
Column 5 is the Avg. Ambient (mGa) computation. See below. *
Column 6 is the BMP or barometric pressure in inches of mercury.
Column 7 is the date in Universal Time Code
Column 8 is the time in UTC

Column 5 on the spreadsheet and displayed on the pop-up is the Avg. Ambient (mGa) reading and needs some additional comment. The ambient reading is only valid for nodes running the new software which hopefully will be all of them once the issues are worked out.  Any node running the old software will only show 0.  The Ambient reading has been part of the node software for the last 2 versions at least.  It is used as the average normal reading of the background magnetic field.  The row in the table labeled mGa is the result of subtracting the current field reading from the average ambient reading (unsigned number).  This should normally be a low number if no disturbances are in the area.  In other words the mGa will indicate the variance from what is normal for that node and location.  If the mGa jumps beyond the trigger setting (deviation), this indicates an anomaly.  The mGa reading is NOT the current magnetic field reading.  It ONLY indicates the variance in milligauss from the norm.  Everybody's "normal" will be different depending on their location and background noise.  While the old nodes currently calculate and use the ambient background reading they do not transmit this value to the server.  The new software will.  This was needed, we believe, to help verify that the node is setup in a quiet location and the sensor is working properly.

Getting to and staying "light blue" on the live MADAR Map is what you want to do and where you want to be most of time. Then, when an anomaly occurs, the device will go to "alert status" and you will be sent an alert email and hear an audible "beep" every 10 seconds on your computer. (There may be others already on alert status and your pc audio may have to be muted during those times). Use the easily accessible "Sound On" box at the upper right of your screen. The default setting is "OFF".

If you have the updated model the relay switch will close when the device goes into Alert and the bright blue indicator light we mentioned earlier will come on.

If you have a "red board" very often, it could be a "noisy" location for your device or the limits settings (referred to as "trigger") may be too low.  Even orientation can be a factor! In any case your limits or "trigger" may have to be raised. The devices are originally programmed and shipped at a medium level of 30 to help us tweak the system until you get it right. If your limits are higher than what we would recommend we will ask you to move your device to a better location. We keep a Tech Support Log to record your status and history. If your device is running properly but you are not getting "hits",
we can lower your limits remotely and reboot your device. We cannot reboot the device remotely if it is in alert mode and YOU may be asked to reboot. All you have to do is unplug the device from the wall outlet, wait 10-15 seconds, then replug.  The new device has an LSDS or button to do "a legal shut down" and is highly suggested for the new model.

If all else fails and you still have a nagging "red board" we may ask you to rotate your device a little. But at this point we want to make it clear that your device determines its location and normal local (ambient) field. Bumping it may set it off or a magnetic source near it may trigger it, but once it is left alone it should settle back to normalcy. Rotating it will trigger it but it won't be able to regain stability on its own. If that happens our Tech Support will get you through that as well. Using the LSDS as mentioned earlier is a good remedy for many issues, but always wait several minutes and refresh your screen so that the proper UTC is displayed at the upper right.


We're still working on a text alert for your cell phone but right now you can rely on the email alert which provides a written printout of your anomaly. If you have the new model you may have an alert signal as part of your ADT instruments for gathering additional data. During an alert you don't want to turn anything off EXCEPT the nagging beeper or siren.

In your application at the time of purchase you gave us your physical address, email address, and phone numbers. The physical address or the location where the device will be placed is important, so make sure the PayPal and site location you gave are the same. The same is true with the email address that PayPal displays. We all often have several emails for various types of business or traffic. Thought should be given to which email address should be used for email alerts and which should be used for information and routine communication. It is not easy for us to change this after the device is programmed and in the field. Land-line numbers are not used much so far by MADAR ops but cell phone numbers for text alerts will require accurate numbers. We're not there yet but as soon as we remedy the cell providers or Google-Group issues this will be an important step forward.

We are glad to have your device online and part of the world-wide MADAR System. For over half a century there was only one complicated MADAR that took up two rooms and cost thousands of dollars. The MADAR-III DataProbe is smaller than an I-Pad, gathers much more data, and is an affordable device now being used in many states and several foreign countries.

The MADAR-III-B has a LSDS or legal shutdown switch on the top of the device.
* The red LED is the powerv status indicator and must stay on at all times. If it doesn't, the device is not getting enough power and the power adaptor is in need of replacement.
* The green light next to the red light should flicker during boot.  If it doesn't, that means the SD Card either isn't seated properly or it is corrupted.
* In blue LED is the Video Alert Signal indicating the relay is closed and the optional ADT is powered up.
* Pressing the LSDS button for approximately 2 seconds will cause the node to reboot. (Earlier models had to be unplugged, wait 10-15 secs, replug).
* Pressing the LSDS button for approximately 5 seconds (the green light will blink) and cause the node to shut down. 
* The screwdown terminals (on the front of the device) below the switching tower (right above them) are for running a set of 18 gauge coated/braided copper wires. No need to run these wires unless you are going to use the optional ADT panel. (Auxiliary Data Tasking)

Fran Ridge

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