Updated 2 Sept 2020, updated 7 Feb 2021
This instruction manual is provided mainly for the quick and proper set-up of the MADAR-III DataProbe, but includes the DAS, which is the alarm box for the alert team. Separate
papers will go into more detail about how they all work, why they are needed, how to use them and the data, etc.

* MADAR-III DataProbe (Brochure)
* MADAR DAS (Delayed Alarm System)

Before your DataProbe arrives, you need to obtain an appropriate length of Ethernet cable that will reach from the device to your router. Extra footage will not hurt anything, but typically 5-6 feet may be enough. Some operators have runs as high as 25' or more. You can always run an extension cord for the power adapter but the location you select to place the MADAR unit will probably be near a wall AC outlet. Most walls have two outlets these days.

If you also purchased a DAS (Delayed Alarm Signal), make sure you obtain a couple of 9-volt batteries or the 110 vac to 9 vdc cable.

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. If possible, pick a location in your room that will be several feet away from electronics.  You need to locate a good "E-M quiet" spot by 
tuning a transistor radio to the left end of the AM dial, or use an E-M meter. Walk around the room and listen to what you can pick up! You will be amazed. It is not as complicated as it sounds and we'll get you there. Your data spreadsheet will tell us how you are doing and what we need to do once you are online.

The set-up in most cases is simply plug and play. No computer is really needed. A desktop or laptop or IPad will suffice to look at the data or the MADAR Map, etc., but the dataProbe will be doing its job regardless. Some tweaking in the positioning might be required, but, before we get into the set-up there are three things to be aware of:

1) Daily NOL (Not OnLine) reports
Before, and while your MADAR DataProbe is being installed at your location, you will receive daily NOL notifications. Once you are online the notifications will cease. IF your unit goes offline for any reason. This is an automatic email to you, and also an NOL Report to the MADAR Operations Center here at Newburgh, Indiana to make sure the network is running at optimum capacity. Please ignore them while your unit is on its way to you and allow 24 hours for them to persist after you get your DataProbe plugged in.

2) Red registration dot on MADAR Map
During set-up or normal operation, the unit may be bumped, or for a number of other reasons go into alert mode. You'll get an alert email, a text message on your cell phone, and your blue LED on the dataProbe will come on. You'll also have your light blue registration dot on the Display Map turn "red". If this happens you need to do a system reboot. More on that later.

3) Alert notifications
Anytime your magnetometer field readings reach and/or exceed your threshold, your unit will go into alert mode. If you have an alarm panel or DAS connected you will be alerted with a loud sonalert beeping signal.

1) These devices are programmed for a specific latitude and longitude and assigned to only one person who is licensed to operate it.
2) They cannot be moved to another location without us knowing it.
3) This device is NOT a Field Unit.
4) If you move from your current location, please notify us ASAP and give us your new street address or any other changes such as email or phone. If we program a move, your node number will have to be changed since the data history of the node goes with the location and owner. If you choose not to set up or operate the device, this is your choice, but within a specified period of time it will be deactivated from the server and no refunds can be made.
5) If you bump the device or think you may have set it off send us a notice or "alibi" email so we'll not process it as a credited hit.


Green relay terminal and set screws at upper right.
Hole recessed into enclosure with light blue Legal Shutdown Switch (LSDS). To reboot the device safely, place the end of a paper clip in the opening and depress the switch quickly. To safely shut down the device while you move it to another location (etc.) depress the switch for at least 5 seconds.

Has only the SD Card slot for the 16 gigabyte hard drive.

RJ45 Ethernet Jack on left
Four USB ports stacked on the right (DO NOT USE!!!)

Left: jack for power adapter
Right: HDMI (not in use at this time)

When your DataProbe arrives, carefully place the device flat down on the surface 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 on its power cord into this jack, then
plug the adapter into the nearest 110 VAC outlet or surge protector.  Do not move the device from here on in.  DO NOT WORRY ABOUT ORIENTATION. You are powering up a plug and play device and the unit is connecting to the MADAR Server. Within minutes it will tell the MADAR server it is alive and well and it will know its environment. If something causes that environment to change, the MADAR DataProbe will go into action.

Important, you should mark or make sure that you do not use any other power cord on this device. The world is now flooded with similar power cords.

The red LED on the right 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 green LED that is blinking near the Ethernet jack is normal and shows data transfers. This tells you that you are connected to the internet.

On top of the DataProbe and to the upper right is the exposed top of the relay. When MADAR goes into alert the relay contacts close, so anything connected and using this "dry" switch will also be activated. At the same time, the blue LED comes on. The alert period, plus an additional 180 seconds, is logged on the server.

The actual alert period has been shown and proven to be MUCH longer than mentioned above. At one location the "apparent alert" lasted just seconds but the UFO sighting lasted at least ten minutes. Ops and teams should consider all alerts to be at least 15 minutes or more.

Once connected to the server you should be running with two of the three LEDs lit. The blue LED SHOULD NOT BE ON.

You don't have to, but as a courtesy drop me a short email telling me you are online.

Frequently-Asked Questions


If you have an I-Pad Ap go to the MADAR Map. If you are using your computer, get on your browser and go to
then drag the link to your pc for easy desktop access.

You can also track what is going on with the new Ipad AP.

Once you're onsite take a look at your part of the world map and check out your blue dot.

MADAR Site Map

Disregard the user and password prompts 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 displays your "Node Number". By left-clicking on ANY node you can see the "pop-up" which gives THAT MINUTE'S last readings.

When there is an alert ANYWHERE you hear an audible "beep" every 60 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".


Note the Universal Time Code at the bottom. This pop-up changes every minute. The sample above is from Node 10. At this point you are probably wondering what the other numbers mean. It is important to know when your device is in normal status mode. It is also being stored on your spreadsheet.


10 alertStat 152.78 24 599.17 27 29.84 2020-02-24 16:13:29
10 alertStat 151.06 24 599.17 27 29.84 2020-02-24 16:13:28
10 alertStat 150.15 24 599.17 27 29.84 2020-02-24 16:13:27
10 alert 151.26 35.25 599.17 27 29.84 2020-02-24 16:13:26
10 alertEnd 152.73 24 599.17 27 29.84 2020-02-24 16:13:26
10 alert 152.76 35.25 599.17 27 29.84 2020-02-24 16:13:25
10 alert 151.47 35.25 599.17 27 29.84 2020-02-24 16:13:24
10 alertStart 151.6 35.25 599.17 27 29.84 2020-02-24 16:13:23
10 alertStat 151.92 25.5 599.17 27 29.84 2020-02-24 16:13:22

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. The alert here lasted 3 secs and the alert phase lasted an additional 180 seconds (alertStat) followed by that many lines (180) and reverting to normal "status" or "ambient" field readings.

Column 3 is the compass heading. The compass is pointing north so the device is oriented in a direction determined by its placement. There is no need to rotate the device to have it in a north or "0" heading.

Column 4 is the geomagnetic field 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 threshold set for that device. This is adjustable but should not exceed 30.

Column 7 is the BMP or barometric pressure in inches of mercury.

Column 8 is the date in Universal Time Code. To convert to local time go to

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 valid for nodes running the new software which as of this date is 100%. Any node running the old software in the past will only show "0" in the data during that period only.  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.

We keep a tech support log (Node Report) to record your status and history. If your device is running properly but you are not getting "hits",
we will 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. The new device has an LSDS or button to do "a legal shut down" and is highly suggested for the new model.


If we have your cell phone number you will receive an alert notification on that device.

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 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 over a hundred locations in the U.S. and foreign countries.

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