.. _adu-07e: .. |br| raw:: html
ADU-07e ======= (also `search here `_ ) Product Description ------------------------- Performance Characteristics ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The ADU-07 (Analog Digital Unit) is the core unit of the metronix multi-channel Geophysical Measurement System GMS-07. It is the result of more than 35years of metronix experience in the design and manufacture of electromagnetic geophysical instruments. The ADU-07 can be equipped with up to 10 measurement channels. The standard configuration for wide band MT and AMT consists of 5 low-frequency (LF) and 5 high-frequency (HF) channels. The type of channel-boards which are plugged-in will be detected by the system automatically. Multiple ADU-07e units can be connected to a network. Each ADU can be operated as a stand-alone system, in a network using standard Local Area Network (LAN), or as part of an array, in which each unit is synchronized by its built-in GPS controlled precision clock. An access via Wireless-LAN is available, too. The ADU-07e electronics is housed in a small (41cm x 32cm x 17cm) waterproof box only 6.5 kg in weight. In spite of the small size, it contains the complete circuitry for analog signal conditioning of up to 10 channels, 24 Bit A/D conversion and data storage as well as a very precise GPS controlled time base. Data is stored on the built-in flash-disk, on a USB pen drive, an external USB hard-disk or, via the network, on the hard-disk of the connected control computer. Either the single ADU-07e or a complete network of several ADUs can be controlled via a standard PC. This may be any (ruggedized) laptop with sufficient performance. Each ADU can be accessed and controlled by any external PC using a standard Web-browser. All metronix magnetometers like MFS-05, MFS-06(e), MFS-07(e), FGS-02, FGS-03, SHFT-02 can be connected directly to the ADU-07e. It is also possible to connect magnetometers from other companies on option. The GMS-07 system provides a high degree of flexibility for various sensor setups. Due to its scalable and modular concept it can grow with the requirements of the user. The low number of different components also simplifies the spare part requirement. Features ^^^^^^^^^^^^^^^^^^^^ * High data quality due to 24 Bit Analog/Digital conversion technology * Very low system self-noise for best results in the MT “dead band” * Wide frequency range from DC to 250 kHz. Sampling rates up to 524kHz * System can be operated as a stand-alone or as a multi-channel network system when connecting multiple ADU-07e in a Local Area Network (LAN). An integrated W-LAN module is now standard. * ADU-07e is controlled by any Web-browser without need of further software * Multiple stand-alone systems are synchronized with GPS clock accuracy. * Compatible with all metronix sensors (see note on previous page). * Automatic unattended recording mode. * Plug and Play recording mode if a USB stick with pre-programmed time schedule is inserted * Automatic detection of magnetometer type and automatic download of calibration function from sensor (Only for MFS-06e, MFS-07e and future sensors) * Automated system self-check of ADU-07e and sensors during set up. * Optional automatic input offset compensation eliminates self-potential of electrodes * Real-time data processing on option. (the capabilities of this feature will be further enhanced in future software releases). * 12 V battery powered. Only one battery is required for each ADU-07e incl. sensors. * Compact, light-weight, ruggedized and water-protected instrument design. * Low power consumption * Wide operating temperature range from -40°C to +60°C ambient temperature. * Multiple methods such as MT, AMT, EMAP, RMT, CSAMT Technical Data ^^^^^^^^^^^^^^^^^^^^^^^ .. csv-table:: :delim: | Frequency range|DC to 250 kHz Number of channels|1 to 10 per ADU-07e, multiple ADUs can be operated in a network Frequency ranges of A/D converter Boards|LF: DC – 500Hz; MF: DC -20kHz; HF: 1Hz – 250KHz Sub-bands are created by digital filtering Available A/D conversion boards|LF: 24 Bit (data rate max. 4,096 samples/sec)MF: 24 Bit (data rate max. 65,536 samples/sec) HF: 24 Bit (data rate max 524,288 samples/sec) One A/D conversion unit for each channel Input Noise|LF-ADB: 10nV/Hz @ 0.1 < f < 2kHz and gain 64 HF-ADB: 13nV/Hz @ f >1kHz and gain 32 MF-ADB: ca. 15nV/Hz @ 0.1Hz.20kHz (gain16) Input Resistance|LF-ADB: >100M MF-ADB: 10…100M HF-ADB: >10M Nominal Input voltage Range (@ gain 1)|switchable between +/- 1.25V and +/-10V (is done automatically by selection of sensor type) System computer|32 bit low-power embedded controller with Linux operating system Storage media|Internal Compact Flash-disk 8Gbyte or higher, USB-pen-drive or other external USB mass storage device Test facilities|Automatic power up self-test of all important system functions including sensors and display of result on the instrument. Automatic creation of log-file Calibration|automatic calibration Network connection|stand. twisted pair Cat5 or higher with RJ45 plugs, Wireless-LAN Synchronization|GPS synchronized clock , 30ns rms accuracy of 1pps signal, Station position is also determined and stored Connectors|{1 or 2 Network RJ45 ruggedized socket(s) 3 x Magnetometer 10-pole 4 x E-field input terminal 6-pole 1 x multi-purpose connector for 5 additional channels 1 x GND terminal 2 x input terminals for 12V battery protected against reverse polarity 1 x GPS antenna N-Type socket, 1 x WLAN antenna N-Type socket, 2 x USB2.0 Type A; 1x USB2.0 Type B { Status Display|2 lines with16 alpha numeric characters for display of status information Case|ruggedized, water-resistant plastic case Weight|appr. 6.5kg External dimensions|406*330*174mm3 Power Input|9V … 15V DC Power consumption|circa 4W – 20W depending on operation mode Operating temperature range|-40°C to + 60°C Revision Base for this Manual ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The functionality that is described in this manual is based on the following revisions of software and hardware components of the ADU-07e system: Hardware components: .. csv-table:: :delim: | Name|Description|Revision ADU-07-LF|LF analog/digital converter board|1.0 ADU-07-HF|HF analog/digital converter board|1.0 ADU-07-MF|MF analog/digital converter board|1.0 ADU-07-MDB|ADU-07 mother board (main backplane)|2.1 ADU-07-FPGA|ADU-07 FPGA and USB board (sub backplane)|1.1 ADU-07-CLK|GPS/clock board|1.0 ADU-07-CAL|board for creation of calibration signals|1.0 ADU-07-CON|Connector board |2.0 Software components: .. csv-table:: :delim: | Name|Description|Revision MCP|Master Control Program for ADU-07e operation|3.0.1.0.746 USB driver|Linux USB driver for connection of the backplane to the CPU board|3.0.1.1.118 ADU-07e Web-interface|Web configuration platform for ADU-07e operation|3.0.1.1.775 8051 software|Embedded controller software for backplane|3.0.0.1.193 FPGA image|VHDL FPGA image for backplane hardware control|3.12 (22.02.2011) USB Auto-mounter|Auto detection of connected USB mass storage devices with pre-configured job-lists|3.0.0.1.55 Overview -------------- The ADU-07e is delivered along with a GPS-antenna and two battery cables. Figure 2-1 to 2-3 show the ADU-07e and its operating elements. All operating elements are numbered and described in more detail in the next chapter. IMAGE Operating elements of ADU-07e front-panel IMAGE Operating elements of ADU-07e left side IMAGE Operating elements of ADU-07e right side Operating Elements ^^^^^^^^^^^^^^^^^^^^^^^^^^^ The ADU-07e has the following operating elements: .. csv-table:: :delim: | Number|Function 1|2 x USB Type A connector 2|1 x USB Type B connector 3|GPS Status LED 4|Recording Status LED 5|Battery Status LED 6|Button “SCROLL” 7|Button “PARAM” 8|Alpha numerical display 9|Battery connector 1 10|W-LAN antenna 11|GPS-antenna 12|Battery connector 2 13|LAN 1 (RJ45) 14|LAN 2 (RJ45, optional) 15|Ex (North) 16|Ex (South) 17|Ey (East) 18|Ey (West) 19|GND terminal 20|Hx connector 21|Hy connector 22|Hz connector 23|Multi-purpose connector 24|additional 12V input USB Type “A” Connector ^^^^^^^^^^^^^^^^^^^^^^ Underneath the lid you will find 2 USB Type A connectors for connection of USB mass storage devices such as USB memory sticks or USB hard-drives. Mass-storage devices will be recognized by the operating system automatically. USB Type “B” Connector ^^^^^^^^^^^^^^^^^^^^^^ This connector is provided for connection of an external computer to control the ADU-07e. The external computer must run with Linux operating system and the appropriate software to control the ADU-07e has to be installed. If the external computer is connected to the ADU-07e it will switch the internal CPU board automatically off-line. The external computer will then control the ADU-07e completely. This option is intended for debug purposes mainly. GPS status LED ^^^^^^^^^^^^^^ This LED shows 3 states: .. csv-table:: :delim: | LED off|No GPS synchronization or system in clock hold mode LED blink|System has detected sufficient number of satellites, but has not reached the maximum accuracy LED steady green|GPS locked and system fully synchronized If the LED is not illuminated despite the GPS-antenna is corrected properly, it may be that the antenna does not have an open view to the sky allowing the system to detect at least 4 satellites in view. In this case it may be helpful to look for another location for the antenna. If the ADU has been transferred to another location which is far away from the last one with a valid GPS lock (more than 300 km), it can take a while until the system has found a sufficient number of satellites. In this case the stored Almanac of the satellite positions is no more valid for the new location and has to be updated first. This procedure can take up to 15 minutes. It also may take a longer time if a long time span (more than 1 week) has been passed since the last GPS fix. Recording status LED ^^^^^^^^^^^^^^^^^^^^ The red LED is illuminated if a data acquisition is running. Battery Status LED ^^^^^^^^^^^^^^^^^^ In order to get a quick check of the battery voltage without a laptop connected, this LED is provided. The meaning of the different colors is: .. csv-table:: :delim: | Green|Battery good (voltage higher than 12.5V, fully charged) Yellow|Battery voltage fair (<12.5V and >11.6V) Red|Battery low (voltage < 11.6V and > 11.2V) Dark|Battery almost totally discharged (voltage <11.2V) The exact battery voltage and current are also shown on the status display and it is monitored in the log file. If the battery voltage gets low, the ADU will shut-down automatically. Alpha Numerical System Status Display ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The display shows the status of the system after self-test and many other important parameters and information. The display is switched off automatically after a period of 30 sec in case no button is pushed. Button “SCROLL” ^^^^^^^^^^^^^^^ Pushing this button will change the parameter displayed on the status display or switch the display on. Button “PARAM” ^^^^^^^^^^^^^^ Pushing this button can show more parameters. If this option is available it is indicated by an right-arrow on the right side of the second display line. Battery Connector ^^^^^^^^^^^^^^^^^ The ADU-07e is equipped with 2 battery sockets (type CA 02COM-E10SL-4S-B). This allows to either connect one or two batteries. Before the delivered battery cable can be connected, you have to unscrew the protection cap of the socket. The input voltage is 12 V nominal; the allowed voltage spans from 9V to max. 15V. The inputs are protected against wrong polarity under all circumstances. If the ADU should not work, check for wrong polarity. If the instrument shall be operated without interruption, you may use the second battery input to connect a fresh battery. After that you may disconnect the old battery from the ADU-07e for recharging. At the ADU-07e an auxiliary 3rd battery input is provided on the front-panel. Here for instance a small Gel-battery can be connected in order to provide a continuous power-supply during the system is transported to the next site without interrupting the power. This may especially be helpful when the distance between two sites is only a few hundred meters as it may be the case in small scale AMT or RMT surveys. Antenna Socket for W-LAN ^^^^^^^^^^^^^^^^^^^^^^^^ The W-LAN antenna socket allows you to connect an external antenna (if a W-LAN module is built-in). Antenna socket for GPS antenna ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The GPS-antenna which is delivered along with the ADU-07e must be connected to this socket (N-type) to get advantage to the synchronous recording mode and in order to determine the position. Socket(s) for Network ^^^^^^^^^^^^^^^^^^^^^ The network cable is connected to this socket (RJ45). The operation of the network is described in a separate chapter. E-field connectors for standard and buffered E-field cable ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ These four terminals are used to connect the standard or the buffered E-field cables. The plugs on the E-field cable have 6 pins. The center pin is the pin where the standard E-field cable has to be connected to. The labeling of the four sockets indicates the position of the electrode (N=North, E=East, S=South, W=West). In a typical arrangement the ADU is located in the center of the two E-field lines. GND Socket ^^^^^^^^^^ This socket is used to connect the grounding rod with the ADU. The grounding can be done by a steel rod or an electrode. Grounding should be done close to the ADU. Grounding of the ADU is very important as otherwise the inputs can float and may be saturated. Connector for Magnetic Field Sensors ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ On the right side of the ADU-07e you will find 3 sockets (10-pole ODU K-series) to connect the magnetic field sensor cables. Plug-in the cable connector in a way that the notches of the sockets fit with the plug and lock the bayonet Multi-Purpose Socket ^^^^^^^^^^^^^^^^^^^^ This socket provides the input terminals for 5 more channels as well as a +/-12V power supply and some control lines. Here an additional 3-axis flux gate sensor, a high frequency magnetometer or additional E-field lines can be connected. The max. input voltage range for the signal inputs is selectable by software to +/- 1.25V or +/-10V individually for each channel. Definition of Polarities ------------------------ The following polarities are defined in the ADU-07e: E-Fields ^^^^^^^^ .. csv-table:: :delim: | EX:|NORTH = Plus SOUTH = Minus EY:|EAST = Plus WEST = Minus When applying a DC voltage to the input terminals of the ADB-07 as described above, the result will be a positive output on the A/D converter. H-Fields ^^^^^^^^ The polarity of the magnetic fields is defined in a way that a positive flux change in the positive sensor direction will cause a positive output voltage on the A/D converter. The positive sensor direction of the *MFS-05, 06 or 07* sensor is given when the bottom of the magnetometer's case (the part opposite to the side with the connector) shows in these di­rections: .. csv-table:: :delim: | HX:|NORTH HY:|EAST HZ:|CENTER OF THE EARTH Installation in the Field ------------------------------ This chapter describes the setup of the ADU-07e and of the sensors in the field. Before connecting the sensors to the ADU you should choose the location where you want to position the laptop computer for system control (normally installed in the field car, in a tent or in a box together with the battery). You should consider that the optional delivered network cable has a length of 50 m. The best way to proceed is to unreel it first in di­rection to the desired location for the ADU-07e starting from the location of the laptop. This will avoid the trouble that the cable is too short after already having installed all the sensors. Of course the laptop can also be operated outside, but especially in bright sunlight this may be quite difficult. Standard 5-channel MT Setup ---------------------------- Figure 3-1 illustrates the field setup of a five channel MT station. Only a few components are required: * ADU-07e * GPS-antenna (optional, but should be used even at single site measurement to determine the exact position and time) * 3 magnetometers like *MFS-06(e)* or *MFS-07(e)* * 3 magnetometer cables * 4 electric field probes * 4 electric field cables * 1 grounding rod + cable * Network cable (for connection to laptop or network in case of configuration or data download) * Laptop (only required for non automated system setup and control) The field computer (may be any ruggedized laptop) with an Ethernet interface for RJ45 jacks and a web browser such as Internet Explorer, Mozilla Firefox or Opera browser installed. The laptop is only required to program the ADU-07e. Often it is sufficient to insert a pre-programmed pen-drive to start the measurement. A laptop is not required in this case. IMAGE Typical 5-channel MT field setup 8-channel Setup with additional Fluxgate ----------------------------------------- In this configuration the ADU-07e is used along with 2 E-field channels, 3 channels for H-field using an induction coil sensor and an additional 3-channel fluxgate sensor for a continuous low-frequency recording. IMAGE 8 Channel setup with 3 induction coil magnetometers, 2 E-field lines and additional 3-axis fluxgate sensor. Connection of the Sensors to the ADU ------------------------------------- Now you can install the sensors: 1. Plant the four EFP-06 probes into the ground as described in Chapter 3.3.2 and connect them with the input of the E-Field cable drum. 2. Connect the other end of the 50m E-cable with the appropriate input terminals of the ADU-07e. The North-probe will be connected to the terminal labeled "N" of the ADU-07e. In the same way the "S", "E" and "W" input terminals of the ADB are connected to the corresponding E-field cables. Make sure that the E-Field cables are unreeled completely and the cable is not moving in the wind. 3. Stick-in the grounding rod close to the ADU-07e and connect it with the black GND-input clamp of the ADU-07e 4. Connect one end of the magnetometer cables with the HX, HY resp. HZ magnetometer. For this purpose at first remove the magnetome¬ter's protection cap. Now push the end of the cable through the rubber flap in the middle of the protection cap. After having it connected with the socket properly, the magnetometer's protection cap is pushed over the magnetometer's head again. The exact positioning and installation procedure of the magnetometer is de¬scribed in chapter 3.3.1. It is very important to notice the hints given there in order to obtain best results. 5. Connect the plugs on the other end of the magnetometer cables with the corresponding input sockets on the ADU-07e i.e. the cable of the HX sensor with the socket labeled "HX", the cable of the HY sensor with the "HY" socket and the cable of the HZ sensor with the "HZ" socket of the ADU-07e. Installation of the Induction Coil Magnetometers ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The magnetometers MFS-05, MFS-06(e) or MFS-07(e) are normally installed as an orthogonal triple and buried into the soil. The distance between the magnetometers should be ca. 5 meters in order to avoid any cross-talk. In order to avoid interference the magnetometers should be located more than 5m apart from the ADU-07e. Before burying the magnetometer it must be connected with the cable. The protection caps should be twisted or plugged together in order to avoid getting them dirty. The magnetometer protection cap is pushed on the magnetometer's body. The end of the connector should not show out. Please take care for an exact alignment of the sensors. The bottom of their cases (i.e. the side without connector) must point exactly in the following directions: .. csv-table:: :delim: | X|magnetometer HX to the NORTH Y|magnetometer HY to the EAST Z|magnetometer HZ to the CENTER OF THE EARTH The correct direction of the sensors can be fixed using a compass and two sticks: A field helper rams the first stick into the soil according to the command of the other helper with the compass. The second stick is rammed behind the first stick. The correct alignment is found when the needle of the compass points to North for HX resp. East for HY and the sticks as well as the ring and bead sights of the compass are in line. The horizontal direction is balanced using a level. The exact vertical position of the HZ-magnetometer can also be fixed by a level. The magnetometers must be installed in a way that any movement of the sensors due to micro-vibrations is avoided. Such motion of an induction coil magnetometer in the stationary earth magnetic field would cause significant artificial noise. For this reason the hori­zontal magnetometers must be dug and covered by soil completely. We recommend a pit of 30cm depth. The vertical HZ-com­ponent should be dug-in to at least half of its length or better to 4/5 of its length. An addi­tional coverage of the HZ sensor by a kind of bucket helps to reduce wind influences. **Information:** The cables nearby the magnetometers must be fixed and may not move in the wind!! Installation of the Electric Field Probes ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ In the standard MT field setup the orthogonal electric fields EX and EY are measured. For the measurement of one electric field component two EFP-06 electrodes are used. They are dug into the soil with a distance of circa 100 m. In order to have an optimum common mode rejec­tion ratio of disturbing radio transmitters, the ADU-07e should be located in the center of the electric field dipoles. If the L-shape setup cannot be avoided you must use 4 probes in any case. The electrodes close to the ADU may NOT be connected with ground electrode because this would induce a high noise into the electric field input. The exact alignment of the probe's location must be determined using a compass and a measuring tape. The distance of the N/S and E/W dipole should be noted and must be entered in the setup menu later on. The probe location can be marked by pickets to find them faster in the field. Now dig holes of 20 cm to 30 cm depth and plant the probe into the soil. Make sure that the bottom of the probe has a good contact with the soil and cover the probes by soil com­pletely. It is important that the soil is pressed down finally in order to obtain a good con­tact. It also may help to improve the ground resistance by mixing a paste of water and soil and planting the probe into that paste. In case the soil is very dry, the grounding resistance can be diminished using some Ben­tonite which is mixed with soil around the probes and by adding some water. The Bento­nite will keep the moisture for a longer period of time. If you need to do long term measurements in a dry area, the probes should be dug in deeper (80cm). The typical probe resistance is between a few hundred Ohms to 10 kOhms. However, it might be much higher in very resistive areas as deserts etc. In this case the use of the optional buffered cables is recommended. Please also make sure that the E-field cables are not positioned too close to the magnetometers (>1m). If the probes are not used make sure that the sponge at the bottom of the protection case is covered by water and that its lid is closed. The cap can also be sealed by some isolation tape if the probe is not used for a longer period of time. The free cable end should be outside the protection case in order to avoid corrosion. The current condition of the electrodes can be checked as follows: take a new, fresh electrode and one of the electrodes which is already in use. Dig them on the ground as described above (1 pit is sufficient) and check the voltage offset between both. The voltage should be less than 30mV. Installation of Fluxgate Sensor FGS-03 (MAG03-MCES) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This fluxgate sensor is a 3 axis magnetometer. It is delivered in a plastic tube which has to be aligned vertically and dug into the soil. An arrow installed on it has to point to the North. Connect it via the delivered cable with the Multi-purpose socket (Input 1) of the ADU-07e. The ADU-07e will switch the input sensitivity to +/-10V automatically when giving the sensor name FGS-03. Use gain of 1 for the ADU. The alignment to the Magnetic North can be checked by observing the data. Hy signal must be close to zero Connection of the GPS Antenna ----------------------------- Connect the delivered GPS-antenna to the socket labeled by „GPS“. At least 4 satellites have to be in view in order to allow proper synchronization of the system. Detailed information about the status of the GPS-synchronization of the ADU-07e is provided in the status window of the web interface. Best results will be achieved if the antenna has a free view to the sky. Connection of the Battery -------------------------- When all other components have been installed and connected to the ADU-07e, the last step is to connect it to a 12V battery. This may be any 12V battery with sufficient capacity (>10Ah). The delivered battery cable is connected to one of the two sockets labeled as „BAT“. Connect the black clamp with the –pole and the red clamp with the +pole of the battery. **Information:** A connection with wrong polarity on each of the battery inputs which has been accidentally made will not cause any harm on the instrument. It will then just simply not work. After a correct battery connection it will boot up normally. Connection of the Field Laptop Computer --------------------------------------- The laptop is connected to the ADU-07e with the network cable or by a W-LAN connection. As network cable is you may use any standard network cable with RJ45 plugs. One end of this cable is connected to the socket labeled „NET“, the other end is connected to the Ethernet socket of the laptop computer. If the communication is ok and after having entered the proper network address into your browser you will be able to contact the ADU-07e. We recommend to book-mark the ADU´s address in your browser. Make sure that no proxy server is selected in your browser settings! The network parameters of your laptop have to be set in a way that it can access the 192.168.0.xxx network address room for LAN access and 192.168.10.xxx for W-LAN access. **Information:** In the latest firmware version (3p0 step 7 and higher) the WLAN adapter will do the address management automatically. Select DHCP in your adapter settings **Information:** Note, that the total length of the network cable between hubs or ADU and Laptop may not exceed 100m. Starting the Instrument ------------------------------------------- As soon as the battery voltage is applied to the instrument, the ADU will start to work. At first the Linux operating system and the system firmware are booted. This is indicated by a message on the status display. At the very first time (<1min) after the ADU-07e was powered up there will be no status display at all (Only the battery LED will glow yellow). The status display will then come up with the message “CONNECTING” followed by “BOOTING” After a while, the system will perform its self-test indicated by the blinking LEDs and the status display will show “SELFTEST”. The progress of the self-test will be also indicated in the status display. If the self-test has passed after a while, it also will be shown in the display. Please note that it is possible to shorten the time required for the self-test by selecting “Short Self-test” in the configuration menu. In this case only the most necessary tests will be performed. It is a good practice to run a long self-test at the beginning of a survey and also if some suspicious data occur. However, usually it is absolutely sufficient to run the short self-test during the ongoing survey. **Information:** Usually, the ADU should be powered up after all sensors have been connected. However, in order to save some time you may switch on the ADU before the sensors are connected. But, you have to redo the measurement of the probe resistance in order to get the correct values and you also should read-in the sensor configuration again. If you setup the ADU in an area which is located far away from the last measurement area (>300km), the time required to synchronize the GPS will be longer and may be up to 10-15 minutes as a new almanac has to be reloaded. The same applies if the ADU has not been used for a long time. **Caution:** Do not operate the instrument during a nearby thunderstorm as a direct lightning strike could hit the E-field lines. Despite the input of the ADU-07e is protected by spark gaps and protection diodes this will not guarantee a protection when a direct lightning strike hits the E-line. Especially, when the instrument is connected via the network cable major damages and personal injury may occur! **Information:** Check that the ADU-07e system has a proper grounding: The ADU-07e system needs a proper grounding, as otherwise the amplifiers do not work correctly. For long term recordings the use of an EFP electrode is recommended (instead of using a simple metal rod). Stopping the Instrument ------------------------------------------- If the instrument should be powered down to move it to another measurement site, it MUST be shut down properly, using the “Shutdown System” option on the Front-panel display (see chapter 12.1). If the shut-down sequence was initiated, the Front-panel LEDs will start to blink, just as during self-test. Once the system is shut-down completely it is safe to cut power, the LEDs will stop blinking again and the “System Status” message on the Front-panel display will show the message “Ready to Power Off”. **Caution:** Switching off the system without using the “shut-down” sequence may result in broken system disks in worst case. Even though the ADU-07e tries to repair a possible broken disk each time when booting up it cannot be guaranteed that there won’t be any problems. Quickstart ------------------------------------------- After the ADU-07e has been powered up and finished the self-test procedure it will wait for user inputs. For this purpose you have to “interact” with the system. The main possibilities to access the ADU-07e in regular operation are listed below: .. csv-table:: Different possibilities to access the ADU-07e in normal operation :delim: | Type|Description By Web-interface|The Web-interface is the main Human Machine Interface (HMI) of the ADU-07e. You will configure the hardware and start new measurements with it By Front-panel Display|The “Front-panel Display” provides a lot of system status information. Among other this comprises the GPS status messages, the battery status as well as the current system status. Additionally, there are some menu options to execute a GPS reset or to release attached USB mass storage devices. By USB Auto-mounter|By means of the USB Auto-mounter the user may start job-lists inside the ADU-07e system without need to connect a Laptop for configuration. The job-lists are simply read from attached USB mass storage devices. By Samba File Server|A connection to the ADU-07e system by means of the Samba protocol is considered to access the data directory of the ADU-07e system directly. Here you may download, or delete measurement data directly. It is available for Linux and Windows. Sometimes, it may be necessary to access the system if problems have occurred or just for system maintenance, such as software updates etc. In this case the following methods allow a more specialized access to the system. .. csv-table:: Different ways to access the ADU-07e for system maintenance purpose :delim: | SSH protocol (Secure Shell Protocol)|This type of interfacing with the ADU-07e is meant to work on the ADU-07´s Linux operating system directly. For this type of connection, the SSH (Secure Shell Protocol) is used. You need a PC with an SSH client installed. It is available on every Linux system and by a small program for Windows systems, too. see chapter for a detailed description RS 232 connection|The RS 232 connection is used for debugging purposes only. It is directly connected from a PC with serial interface to the CPU board of the ADU-07e system. By the use of this connection, you may work on the Linux operating system of the ADU-07e, even if the Ethernet connection is not working anymore. see chapter for a detailed description MySQL data base connection|A connection can be established to work on the MySQL database of the ADU-07e system directly. This connection can either be done with the MySQL console utilities and a direct execution of MySQL commands on the Shell Console, or by usage of a comfortable GUI like “PHPMyAdmin” (free software). As inside the MySQL database all status information and error messages of the ADU-07e are stored, it is a good idea to “dump” the data content of the database into a SQL file after each measurement campaign and then store it along with the measurement data. Hereby, an easy trouble shooting can be done in case a problem occurred in a measurement. see chapter for a detailed description In most cases you want to start a new measurement after system boot-up directly. In most cases the ADU-07e Web-interface will be used. To start a new measurement job the following steps should be performed: 1. **Login to ADU-07e Web-interface** To login to the ADU-07e Web-interface a normal Web-browser is needed (such as MS Internet Explorer ™, Opera™, Mozilla Firefox™ …). Connect the network cable or use the W-LAN (Do not forget to switch W-LAN on ADU on). Open a new Web-browser window and type in the URL of the ADU-07e Web-interface. The URL is printed on a sticker inside the ADU lid. As a result you should now see the “Start Page” of the ADU-07e Web-interface as shown in the following picture: IMAGE 8 index page of ADU-07e Web-interface 2. **Open the Web-interface** You may now open the Web-interface either by clicking on the **Call Target** button, if you have worked with the ADU-07e system at least once and no changes in hardware were made. Otherwise, use the **New Session** button, if this ADU-07e has never been used before or if the hardware configuration has been changed since the last time or if a new software update has been made or in case you just want to start it with the default values. 3. **Examine “Self-test” Results** As a next step the “Self-test Results” should be checked to make sure, that the system is working correctly. For this purpose the “Self-test Results” page of the Web-interface is called. It looks like the following: IMAGE “Self-test Results” page of ADU-07e Web-interface On this page it is important to check the “Init Error” and “ADB error” fields for all the single boards. Normally, all these values should be set to “0” (no error). Sometimes, single values may have values different from “0”. This may not be a real problem necessarily and can also be just significant information. In any case please check the “error number” along with the list given in chapter 22. Warnings or errors are also show at the bottom of the status window. 4. **Configure the sensor settings** As a next step you should enter the correct sensor settings for the connected sensors. This is done on the “Sensor Position” page of the Web-interface. IMAGE “Sensor Position” page of ADU-07e Web-interface As it can be seen in the picture above, you need to enter the “sensor type”, “sensor name”, “sensor serial number” and the “sensor positions” seen from the ADU-07e system for all sensors connected to each ADU-07e connector. E.g. the data for the MFS-06 coil connected to connector “Hx” on the ADU-07e system would be entered inside the box “ADU-07e connector: Hx”. Note, that if you use the new MFS07e or MFS06e sensors, this information is transferred to the ADU-07e automatically. For a detailed description of this page refer to page102 of this manual. 5. **Configure the single ADB channels** After having checked, that the system works correctly, the particular ADB (Analog / Digital Converter Boards) need to be configured according to the requirements of the measurement planned. For that purpose you best open the “Start Job” page of the Web-interface which looks as follows: IMAGE “Start Job” page of ADU-07e Web-interface On the lower section of this page you need to activate all those channels, which shall be used in the next measurement. This is done by activating the “Use For Measurement” boxes for the corresponding channels. If all the desired channels have been selected, click the button to store the values. You may configure a lot more parameters, such as gains, filters for the single channels. A detailed description of the “Start Job” page and the single parameters can be found in chapter8.3.1. 6. **Start New Job** Basically, you are now able to start the new Job by using the upper section of the “Start Job” page. IMAGE “Start Job” page of ADU-07e Web-interface On this page you need to enter the start- and stop-times for the job. Furthermore, you need to select the sampling frequency for the job. After the settings have been saved by a push on the button, you may now either press the button to start the job at the time that you have configured on the “Start Job” page or you press the button to start the job at the next possible point in time. You will find a detailed description of the “Start Job” page in chapter 8.2.1. Strategies for Setting up System Parameters ------------------------------------------- In chapter 7 you find a detailed description of all the possible setups of parameters. However, in this chapter you will get hints how to set up the parameters in an optimum way in order to obtain best results for your field measurements. The connection of the sensors has to be done as described in chapter 3. Before you program a job with the Web Interface you need to know what gain and filter settings are appropriate for this field site. We assume a standard 5 channel MT setup and that data shall be measured in a wide frequency range from 1000 sec up 10 kHz. In order to have best results, a proper check of the noise level in this area has to be done. It is important to set the gains correctly, especially for the electric fields. Generally spoken, it is preferable to set the gain on the first stage and increase the gain of the second stage only after a low-pass filtering or an offset compensation has been performed. A step by step recipe gives you a detailed description of the procedure: 1. Check whether the self-test shows zero (0) error for all channels. If yes, this is ideal. If not, check what the error number means. It is given in section 22. You will also find additional information of the error on the status info page, too. Actually, there are some “errors” which are only warnings in fact. If, for instance, the “DC level is too high for gain” you cannot use amplification but a measurement is still possible. 2. In order to test the noise level on the field site you program a job for 1 minute using the LF ADC sampling rate 2048 Hz for all channels with: .. csv-table:: :delim: | **Parameter**|**Setting** Calibration|Off Gain Stage 1|1 Offset Correction|0 Gain Stage 2|1 ADU07_LF_RF4|On ADU07_LF_4Hz|Off Chopper|0 Input Connection|0 (for standard MT setup) Use for Measurement|tick all After the job has been performed you need to check the data of all recorded channels. Usually, the data will be dominated by power-line noise. It also may have some DC offset. The maximum input voltage range for the electric field channel is +/-1.25V and for the magnetic channel it is +/-10V. You should check carefully now what the amplitude value and the offset voltage of the E-field data is. The gain setting and the offset correction has to be made according to this test measurement. Please note that by using MAPROS or TSPlotter program the shown amplitude values are always referred to the INPUT of the ADU. It is important that you leave enough headroom in case the signal gets stronger during the day. We recommend that the maximum amplitude of the amplified signal on the A/D converter is not exceeding 250mV for electric channel. **Information:** The ADU software version 3.0 or higher provides a feature of automatic gain and offset setting. If this is used, the ADU will perform the required tests by itself. A more detailed description is given in chapter 0 and 0 and **General gain settings**: the magnetometer channel will not require a gain in most cases because the coils have a built-in preamplifier. For the electric field it is desirable to reach a gain factor of 8 (input range +/- 32mV at the input = +/-250mV at the A/D converter input). Higher gains will not improve the signal quality significantly and should only be set if the signal is very low and the expected drift of the electric field is almost zero. **Example**: The measured peak to peak amplitude of the electric channel is 20mV and the signal has an additional offset of 30 mV. This would result in a positive amplitude value of 40mV and a negative amplitude of 20mV. Here the limiting factor would be the 40mV amplitude. According to this a gain of 4 could be selected which would result on 160mV on the ADC for the upper value. There would also be a possibility to compensate the measured +30 mV offset value by a negative offset compensation voltage which is fed-in after the first gain stage. The max. voltage which can be compensated here is +/-2.5V. In our example this would mean that you may amplify the first stage by 4 resulting in a signal amplitude +160mV to +80mV. Now you compensate the 30mV which has been also amplified by the first gain stage to 120 mV by a compensation voltage of -120 mV. The signal value after compensation will be +40mV to -40mV then. On the second stage you can further amplify by another factor of 4 then. The output swing on the second stage, respectively on the ADC input will be +160mV to -160mV then which provides enough headroom to the +/-2.5V limit of the ADC input. 3. Set the gain for the magnetic channel in the same way as described above. An offset compensation will not be required for Metronix induction coil sensors, but may be required for fluxgate sensors. The only difference is that the input range on the magnetic channels is +/-10V. 4. The radio filter should be set on ADU07_LF_RF4 position on standard. Only if you have very high resistivity of >10kOhm a filter such as RF2 or RF1 should be selected. Please also refer to section 9.3.3 of the manual. 5. If you want to record very low frequency data, intended for a range <4 Hz you may switch on the 4 Hz low-pass filter in the filter options. This will significantly reduce the power-line noise and allows to further amplify the signal on the second gain stage. 6. The same recipe for gain setting can be used for HF-channels. Please consider that an offset on the electric field channel can be removed after the first gain stage by a 1Hz high-pass filter. After having found the suitable parameters for the field site, the programming of jobs for different sampling frequencies can be done. Please make sure that at least one minute time difference should be left between two succeeding recording jobs. Especially when high sampling rates are programmed it can happen that the writing of the data out of the buffer takes more time than one minute (with USB1.1 and Viper CPU board). Make sure that the calibration and test signals are switched off and that the correct sensor input is selected. Select “Input 0” for sensors connected on standard inputs (N,S,E,W and Hx, Hy, Hz) and select “Input 1” for the Multi-purpose socket. Check whether you have a G4 GPS fix in order to get best timing synchronicity for multiple stations. ADU-07 Web-interface ------------------------------------------- The ADU-07e is completely controlled by its Web-interface. The Web-interface provides pages to configure the single ADB channels (Gains, Filters etc.), to examine the current system status and to start and stop measurements. The Web-interface is installed on the ADU-07e system and can be connected by a standard Web-Browser. Just type in the following URL: .. code:: http:// You will find a sticker on the ADU-07e displaying the programmed IP addresses for LAN and W-LAN access. Additionally you can find this information on the status display “System Status” by pushing the PARAM button as long as the information is shown. The programmed IP-address will also be displayed as a parameter on the status display of the ADU under “system status” **Do not forget to switch the W-LAN on if you want to use it. It is achieved with the menu entry W-LAN Control in the status display. By default the W-LAN is an open peer to peer network. The WLAN settings on the computer shall be set to automatic (DHCP).** If the connection has been established properly, the Web-interface of the ADU is opened with the following website in your browser window: IMAGE Initial screen of the ADU-07e Web-interface It is the index page of the Web-interface. The normal operation mode will be to call the Web-interface directly from the ADU-07e system by clicking on “New Session”. The Web-interface is started then and the “General – Start Job” page is shown. From here you may browse to other pages of the Web-interface. In the following chapters all the single pages are described in detail. Logically, the individual pages are subdivided into “General” pages and “ADU Special” Pages. It is possible to run the Web-interface software on a Laptop or PC, you can type in the IP address of the target ADU-07e using the field “User defined target IP”. Now, you can start the Web-interface by clicking on the Button “Call Target”. By this means it is possible to run the Web-interface on a Laptop and just exchange the xml-data with the ADU-07e. This will save CPU time and resources on the ADU-07e system. However, it requires an installation of the Web-interface software on the laptop. This method is only used in very special cases and for development. **Information:** On all pages of the Web-interface where parameters have to be entered, a “Save” button is implemented. All entered data is only stored in the ADU-07e, if the input is confirmed by clicking on the “Save” button **Information:** Normally, the ADU-07e Web-interface will store the current settings each time a new measurement is started or the settings are saved by the user explicitly. If called the next time, the last saved settings will be loaded automatically. Sometimes it may happen (for example due to connection problems) that the last stored settings are invalid. In this case the Web-interface can be reset by using the “New Session” button. Structure of the ADU-07 Web-interface ------------------------------------- After having clicked on the Link “Single ADU” or “Call target IP” you will see the “General – Start Job” page. IMAGE Page “General – Start Job” of the Web-interface Using this page as an example, the general structure of all pages of the ADU-07e Web-interface shall be described. Mainly, all pages are split into three large areas. The first one is the heading area. Here you see status information which is taken form the ADU-07e system in the network. The following information is displayed: .. csv-table:: Information shown on the “header” of the Web-interface pages. :delim: | **Value Name**|**Description** Serial Number|This entry contains the serial number of the ADU-07e system. Recording Status|This status shows, whether your ADU-07e is currently recording, or whether it is in idle mode. The following states can be seen: Idle: ADU-07e system is not recording Recording (X): ADU-07e system is recording. X measurements are currently active. Time|This field shows the present time and date of the ADU-07e system. The time information already includes the “UTC to local time” offset, which you may enter in the “General – Options” page. In this case the time is displayed in local time and not in UTC. GPS Status|Shows the current synchronization status of the ADU-07e in reference to the GPS time stamp. The following states are possible: G4 fix – fully synced: The ADU-07e is fully synchronized in reference to the GPS clock. All systems, that have this state, are synchronized to each other. No fix – not synced: The ADU-07e system does not see a sufficient number of valid satellites to get a fully synchronized state. If a G4 fix was available after power-up one time, the ADU will run with its internal TCXO with a reasonable precision so that recording with a low sample rate can be made. Even then, they will be synchronized to other ADUs. If no G4 fix was achieved at all. the ADUs can only be operated in stand-alone mode. Battery Status|Shows the current status of the battery which is powering the ADU-07e. The following states can be observed: GOOD: The state of the battery is GOOD. It is nearly full. FAIR: The state of the battery is FAIR. It may be used for another few hours, but the voltage must be observed. LOW: The battery state is low. It has to be replaced immediately. System will shut down. Diskspace|Shows the current disk usage in percent of its total space. Right on the bottom of the heading area, tabs are shown. Here you will find always one tab with name “General” and one additional tab with serial number of ADU-07 you have connected is shown. By clicking on the tab “General”, the menu items for all general pages of the Web-interface are shown. By clicking on one of the tabs “ADU-X”, the menu points for system special parameters of ADU-07e system with serial number X are shown in the menu area. Finally, the last section of all pages is the data area. In this section the real data content of the selected page is shown. All settings and parameterization of the ADU-07e is done in this area. In the following chapters, at first all General pages will be described. Afterwards, the system Special pages are described in detail, which you have to use to configure all system specific settings. The “General” ADU-07e Web-interface Pages ----------------------------------------- On the general pages of the ADU-07e Web-interface you enter general configuration settings, that belong to all ADU-07e systems in a network. You may enter the general section of the Web-interface by clicking on the “ADU-General” tab of the heading area: IMAGE Tab “ADU-General” By clicking on the “ADU-General” tab, you will enter the general section of the Web-interface. You will see the following menu entries in the menu area: IMAGE Menu entries for the General pages of the ADU-07e Web-interface All these menu entries belong to one single page of the ADU-07e Web-interface. A detailed description of each page is given in the following chapters. Page “General – Start Job” ^^^^^^^^^^^^^^^^^^^^^^^^^^ This is the first page you will see, after entering the Web-interface. It has the following structure: IMAGE Page “General – Start Job” of the Web-interface As it can be seen in the picture above, this page can be used to start a new job on the ADU-07e system. The page contains several input elements to enter the start- and stop-time of the job, define some additional parameters and eventually start the job. However, it is required to define measurement channels that shall be used. For starting a job you will usually take the page “System Specific – Start job”. Here you can enter start and stop time and you can also configure the measurement channels. The “General – Start job” page is split into three main sections. The first section is the “Configure Start / Stop-Time” section andcontains the following input elements: .. csv-table:: Input elements on page “General – Start Job - section 1”. :delim: | **Element name**|**Description** Start|Here, the start time of the new measurement job can be defined. The day, month and year and additionally the hour, minute and second, the measurement shall be started on has to be entered in the input fields. Once the correct start time has been entered, you have to confirm the entry by clicking on the button “Save”. Stop|Here the stop time of the measurement job can be defined. You have to make sure, that the stop time is later than the start time. Sample Frequency|In this field you can select the sample frequency that shall be used during the measurement job. You have the choice out of all the available sample frequencies provided by the ADB board types currently installed in your system. However, not all sampling frequencies are supported by all boards. In this case the best fitting sampling frequency will be selected by the ADU automatically and an error message is displayed. See chapter 18 (fall-back strategies) Measurement Type|The type of the measurement job can be entered here. ATS file size|This parameter allows to define a number of samples that shall be stored into one ATS data file, before it is split and a new one is created. For each new file the RUN number will be incremented. E.g. if sampling with 1024 Hz and setting the ATS file size to 16384 Samples, during the measurement consequent ATS files will be created with 16384 samples inside each file. The max. length of a file is 2GByte which represents 534,773,760 samples. Start / Stop Mode|Using this option, the measurement can be started in a special “Start/Stop” mode. This mode is used, if you want to perform HF measurements in parallel to LF measurements. If a HF measurement is started in Start/Stop mode and the sampling frequency is so high, that the measurement may cause a buffer overflow on the backplane, the ADU-07eE system guaranties, that even, if the HF measurement causes a buffer overflow, the LF measurement will still continue without being influenced. 0: normal operation mode 1: use Start / Stop mode for this measurement Data Directory|This input box allows the user to select the destination directory for the data, that is recorded with the next measurement. It can be chosen between the following directories: “/mtdata/data”: This is the default directory on the internal CF-Card. “/mtdata/usb/data1”: This is the default directory for mounting external USB mass storage devices to the ADU-07e system. It can be used to force the system to write the measurement data to the external USB device, instead of the internal CF-Card. Note: if you have not mounted a USB device nonetheless data will be written to internal flash card. The second section is meant to configure the job as “Cyclic Job”. This is done by setting the value of the “Cyclic Job” parameter to “1”.A job configured as “Cyclic Job” will automatically repeat itself with the “cycle time” that is entered for the “Granularity” parameter. The following picture shall illustrate the behavior of a cyclic job with the following parameters: * Start time: 13:00:00 * Stop-time: 13:01:00 * Granularity: 3 minutes IMAGE Cyclic jobs The “cyclic” jobs are repeated by automatically updating its start- and stop-times and re-writing the job into the “jobs” table inside the MySQL database. Therefore, a cyclic job can only be stopped by deleting the job file from the “jobs” table e.g. from the “View Jobtable” page of the Web-interface. The last section on the “Start Job” page is the section containing all the single buttons. The buttons have the following meaning: .. csv-table:: Buttons on page “General – Start Job”. :delim: | **Element name**|**Description** Save|By clicking on this button, all inputs will be saved. Start Job|By clicking on this button the Web-interface will create a new XML job description out of data configured for this measurement and write this file to the MySQL database. From there the job will be evaluated and started at the defined start time. Start Now|The measurement will be started at the next possible time. This means, that start- and stop-time are changed. The duration of the measurement will stay the same. Show XML job file|By clicking on this button the XML file that would have been written into the “jobs” table is printed into a text box on the “Start Job” page (see Figure 8 7). From there it can be used e.g. to create a “pre-configured USB mass storage device” or for debugging purposes. IMAGE XML job file shown after click on “Show XML job file” **Caution:** Due to the initialization routine of the ADB boards and the measurement hardware, the ADU-07e system needs a handling time of at least 35 seconds for each measurement! If you do not provide this lead time, the next measurement may start late, or even will not start at all. Page “General – Stop Job” ^^^^^^^^^^^^^^^^^^^^^^^^^ If you click on the menu entry “Stop Job”, you will see this screen: IMAGE Page “General – Stop Job” of the Web-interface On this page all the measurement jobs of the ADU-07e , are listed that are currently running, or that have not been started yet. You can see, on which system the measurement is running, by looking at the column “ADU-07e Serial”. Here the serial number of the corresponding ADU-07e system the measurement belongs to is shown. .. csv-table:: Input elements on page “General – Start Job”. :delim: | Element name|Description Show only running jobs|If this option is active, only the measurement jobs currently running are shown. Jobs, that have already been sent to the ADU, but whose start-time has not been reached yet, will not be shown in this table then. Stop all jobs|By clicking on this button, all measurement jobs in all ADU-07e systems within the network will be stopped. This does not only stop currently running jobs, but will delete also jobs, that have not yet started from the scheduling list of the ADU-07e systems, too. ADU-07e Serial|This column of the table shows the serial number of the ADU-07e system, this measurement belongs to. Sample frequency|In this column you can see the used sample frequency of the measurement. Used channels|This column shows which channels are used by the measurement job. Start time / Stop time|In these columns, you can see the start- and stop-time of the measurements. Running|If the measurement job displayed in this line is currently running on the ADU-07e system, an “X” is shown in this column. If the measurement is not yet started, the field is empty. Stop|By clicking on this button a running measurement job can be stopped. This action will force the Web-interface to create a “Stop Measurement” job and to write an according XML file into the MySQL database. The stop job will be executed and finally stop the measurement. **Information:** Like all jobs in the ADU-07e system, the “Stop Measurement” job needs a little lead time to be started, too. Therefore it takes some seconds after you stopped a measurement via the Web-interface until it is really stopped in the measurement hardware. Although the physical recording of data is stopped after a short time in the measurement hardware, it may happen that it takes a while to write back the buffered data to the flash disk. This especially happens if the ADU cannot write back the data in real-time during recording with a high sampling rate Page “General – Event Job” ^^^^^^^^^^^^^^^^^^^^^^^^^^ The “Event Job” page is used to configure and start so called “Event” jobs. These jobs do not start a measurement, but moreover execute certain events inside the ADU-07e system. For example, an event may be the activation or deactivation of the “Sleep Mode”. The page provides the following structure: IMAGE Page “General – Event Job” of the Webinterface As it can be seen in the picture above, the “Event Job” page is designed similar as the “Start Job” page. With the “Configure Start / Stop-Time” boxes you may enter the start- and stop-time for the event. Inside the “Configure Event Parameters” section you may enter the “Event” type and an additional “Event Parameter”. Finally, using the “Configure Cyclic Event Parameters” section you may configure the XML job as a cyclic event, too. The “Save”, “Submit Job” and “Start Job Now” buttons have the same functionality as on the “Start Job” page. Up to now, there are three different “Event” types that all refer to the newly implemented “Sleep Mode”. Using the “Sleep Mode” it is now possible to set the CPU board of the ADU-07e system to a “Suspend To RAM” state during normal operation. In this mode the ADU-07e will record data, and start all programmed measurements. Nevertheless, during the phase when the CPU board is sleeping, it is not possible to connect to the ADU-07e system anymore neither by Web-interface nor by Samba server until it woke up from sleep again. The different events for a configuration of the “Sleep Mode” are: 1. **“System Awake”** An “Event” job with the “Event Type” being set to “System Awake” will cause the ADU-07e system to be awake for the time between the jobs start- and stop-time , even if in general the “Sleep Mode” is active. 2. **“Activate Sleep Mode”** An “Event” job with the “Event Type” being set to “Activate Sleep Mode” will cause the ADU-07e system to activate the “Sleep Mode”. From the point of time, the “Event” jobs stop-time is reached, the ADU-07e´s CPU will try to go to sleep, whenever possible. It will only wake up, to execute jobs (“Measurement” or “Event” jobs), that have been programmed before the sleep mode has been activated, or if the system is woken up manually using the “Front-panel Display” menu. Therefore you have to make sure that you finished your job programming before activating the sleep mode. 3. **“Deactivate Sleep Mode”** An “Event” job with the “Event Type” being set to “Deactivate Sleep Mode” will cause the ADU-07e system to deactivate the “Sleep Mode”. The ADU-07e system will not got to sleep anymore, until the “Sleep Mode” is activated again. The following picture shall illustrate the behaviour of the ADU-07e system, if the “Sleep Mode” is used: IMAGE ADU-07e system with activated “Sleep Mode” Once, the ADU-07e has executed an event job “Activate sleep mode” it cannot be accessed via “Web-interface” or Samba server anymore. In order to avoid that the system falls into a dead lock, it will split the event job “Activate sleep mode” with its programmed start and stop time into two separate jobs internally. The first job which will be transferred to the job table is a “Deactivate sleep mode” which is going to be executed at the programmed stop time of the “Activate sleep mode event”. After that, an “Activate sleep mode” job will be transferred using the programmed start time of “Activate sleep mode” event. Additionally, a warning window will pop up requesting the user to confirm that the “Sleep Mode” shall be activated. It looks like this: IMAGE confirmation dialogue for activating “Sleep Mode” Once the “Sleep Mode” has been activated, the ADU-07e can be woken up from sleep at any time using the menu on the ADU-07e front-panel display. Please see chapter 12.2 for a detailed description. **Caution:** If the “Sleep Mode” is activated inside the ADU-07e, it will not be accessible via the Web-interface anymore, until it has been woken up from sleep again. Therefore make sure that you have: 1. programme all jobs that shall be executed during activated sleep mode 2. programme a “Deactivate Sleep Mode” job so that you have the possibility to wake up the system via the Front-panel display, BEFORE you activate the “Sleep Mode” on ADU-07e system. Besides the “Sleep Mode” functionality there are some other event jobs: 1. **“Start/Continue Moving MT rec.”** This “Event” job is used to continue the data recording, if the “MovingMT” ProcessingObject is configured as part of the processing tree. As a result data will be written to disk again. for a detailed description of the “MovingMT” processing object see chapter 0. 2. **“Stop/Pause Moving MT rec.”** This “Event” job is used to pause the data recording, if the “MovingMT” processing object is configured as part of the processing tree. As a result data will not be written to disk anymore, until it is continued by executing a “Start/Continue Moving MT rec.” Event job. for a detailed description of the “MovingMT” processing object see chapter XXX. 3. **“send status SMS”** This Event job is used to send a ADU-07e status SMS to a user’s mobile phone. For this job the destination phone number has to be entered as a parameter. This functionality is only available if the ADU-07e is equipped with the optional GSM modem. IMAGE configuration of a “send status SMS” Event job When the “Start Time” of the job is reached, the ADU-07e will send a status SMS of the following type to each phone number that is configured as “Event Parameter”: .. code:: Status SMS from ADU-07e #14; Rec. State: 0; Batt State: GOOD; Batt Volt.: 13.1V; Free Disk Space: 62.3% - 7540.5MB; GPS Sync Sate: G3Fix Status SMS from ADU-07e system Inside the SMS the single parameters give the following information: .. csv-table:: Parameters of ADU-07e Status SMS. :delim: | **Parameter Name**|**Description** Rec. State|This parameter shows the recording state. If the ADU-07e is “Idle”, the parameter is set to 0. If at least one measurement is currently active, it shows the number of active measurements. Batt. State|This parameter shows the current battery state: GOOD, FAIR, LOW Batt. Volt.|This parameter shows the current battery voltage in Volts. Free Disk Space|This parameter shows the free disk space as percentage value and in MBytes. GPS Sync State|This parameter shows the current synchronisation state of the GPS board: No Fix, G1Fix, G2Fix, G3Fix. 4. **“send automatic status SMS”** This Event job is used to send configure a list of phone numbers, that shall receive “automatic status SMS” on special ADU-07e events. For this purpose the number of phone numbers needs to be configured as “Event Parameter”: IMAGE configuration of a “send automatic status SMS” Event job After the “Start Time” of the job has been reached, the ADU-07e will send a status SMS to all phone numbers of the list above on the following events: * Job is started * Job has ended * Job is not started due to an error * System is shutting down * Battery voltage switches from GOOD to FAIR * Battery voltage switches from FAIR to LOW To stop the ADU-07e system to send “automatic status SMS” again, simply a new “send automatic status SMS” Event job containing an “empty” list of phone numbers has to be started. 5. **“start sensor detection”** This Event job is used to start the “sensor detection”. When the “Start Time” of the job is reached, the ADU-07e will try to detect the new “intelligent sensors” (MFS-06e and MFS-07e). If one of the sensor types is connected to the system, the sensor’s serial number and type is read and automatically displayed in the Web-interface. This can be useful, in case the sensors were not connected to the system during its selftest, but have been attached afterwards. 6. **“reset GPS (warm-start)”** This event job will cause a warm-start of the GPS modole 7. **“reset GPS (cold-start)”** This event job will cause a cold start of the GPS-module. It requires a reboot power cycle of the ADU. 8. **“activate W-LAN module”** With this event-job you can activate the W-LAN module. 9. **“deactivate W-LAN module”** deactivates the W-LAN module to save power. Activate and Deactivate W-LAN by event jobs may be interesting to use it in conjunction with joblist on an USB stick. 10. **“toggle GPS Dynamic Mode”** This Event job will toggle the “Dynamic Mode” of the GPS board. By default the GPS board is set to “stationary” mode. This mode guaranties very precise timing, but does not allow to move the ADU-07e system from one site to another if being powered on. The GPS board would stop working, if you do so. For use in applications where the system should be carried from one site to another being powered on (e.g. in CSAMT, where measurement time for each site is only about 1 hour), the mode of the GPS board can be toggled. In this case it is switched from “stationary” mode to “moving”. In this mode the system can be carried to the next site. Before measurements on the next site are started, it should be set back to “stationary” mode again for the duration of the measurement. The current mode can be seen on the “System Status” page: IMAGE Display of current GPS Dynamic Mode on “System Status” page This job does not have any parameters. 11. **“execute shell script”** This Event job will start a “Shell Script” on the ADU-07e Linux system. The script will be executed in parallel to the normal ADU-07e tasks, so that normal operation is not influenced by the execution of the script. As parameter this job type gets the path and name of the script to be executed along with up to 8 parameters that shall be handed over to the called script. IMAGE Parameters of “Execute Shell Script” event job **Caution:** The “Execute Shell Script” gives the user a powerful tool to execute timely triggered functionality on the system. Please take care that the script that should be execute does not overload the limited system resources (e.g. 256MByte of RAM on Geode CPU boards, 512MByte on Cortex A8 board). Therefore this functionality should only be used by experienced users with knowledge in Linux systems. Page “General – Processing Queue” ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ If you click on the menu entry “Processing Queue”, you will see the following page: IMAGE Page “General – Processing Queue” of the Web-interface It is called the “General – Processing Queue” page. Here you define the manner how the recorded data is handled. The general concept is that the recorded data sent by the measurement hardware is received by the CPU-board, furthermore processed and written to disk finally. For data processing a so called “Processing Queue” can be defined. It may consist of several “Processing Objects”, each one handling the incoming data in a defined manner. As you see in Figure 8-17, you may define a “Processing Queue” that consists of up to 5 parallel paths, each containing a maximum of six sequential “Processing Objects”. You may define purely sequential, purely parallel or combined “Processing Queues”. The following pictures shall illustrate this: IMAGE Different kinds of possible ProcessingQueue structures IMAGE Different kinds of possible ProcessingQueue structures IMAGE Different kinds of possible ProcessingQueue structures As you see in the pictures above, the measurement data will run through the “Processing Queue” from top to bottom. Therefore it is very important to have as the last “Processing Object” in at least one of the paths a “Processing Object”, that writes the data to the CF-card or USB stick (ATSWriter). Otherwise the measured data will be lost. Six different “Processing Objects” are available up to now: 1. **ATSWriter:** This object writes the incoming data to the internal CF-card or an external USB device. It uses the Metronix ATS (Advanced Time Series) format which was used in older systems, too. 2. **DigitalFilter:** This “Processing Object” performs a digital filtering of the incoming time series data. 3. **SubJobManager:** This “Processing Object” will cut the incoming time series into time slices. On its output only those parts of the time series will be available, that lay inside the previously defined time slices. 4. **OpenMT_DataInterface:** This “Processing Object” is a Socket Interface for the ADU-07e system on which it may send the recorded data in real-time to any connected client. It is available from ADU-07e product step 2on and it is part of the “OpenMT”/ “ViewMT” on-line processing software. 5. **TSStack:** This “Processing Object” is used to do a time series stacking of the recorded time series directly on the ADU-07e system. 6. **MovingMTManager:** This “Processing Object” is used to activate the “Moving MT” mode in the ADU-07e system. 7. **AutoCorr:** This “Processing Object” is used to do activate the “AutoCorr” mode in the ADU-07e system. If active, the ADU-07e will cyclically examine the recorded time series signal and automatically apply gain and DC offset correction settings of the single ADB boards to the current characteristics of the time series signal. 8. **ExecShellScript:** This “Processing Object” is used to execute a shell script at the end of each job / subjob. All these “Processing Objects” and their parameters are described in detail in the subsequent chapters. As you can see in Figure 8-17, you have to define the structure of the “Processing Queue”, that shall be used for a specific measurement. For this purpose you set the single Combo-Boxes according to the type of “Processing Object” you want to use on this position of the “Processing Queue”. If no “Processing Object” shall be used at a certain position, it is just left blank. After you configured the structure of your “Processing Queue” and saved it by clicking on the *Save* button you need to configure the parameters of the individual “Processing Objects”. Just click on the Show Processing Details button and this window will be opened: IMAGE Figure 8-19: Page “General – Processing Queue - Parameters” of the Web-interface Here you can enter all the parameters for the objects of the “Processing Queue”. The window displays the three parallel paths in succeeding boxes, each one including only the “Processing Objects” that have been configured for this path. Inside the box for each path you find the “Processing Objects” listed with all their parameters. You have to configure the parameters for each of them. Eventually, confirm your configuration by clicking on the *Save* button. Clicking on the *Show Processing Queue* button will show you the page shown in Figure 8-17 again. **Caution:** Again, please remember that the last “Processing Object” on each of the paths always has to be ATS-Writer which writes the data to the storage media. If you do not place a “ATSWriter” object to the end of a path, the data, that flows through this path is not written to disk and will be lost. Therefore, at least one “ATSWriter” object has to be defined in the upper left slot. **Caution:** The “OpenMT_Data-interface” Processing Object is only allowed to be placed in the first stage of the Processing Queue. By this means the data sent via the socket interface is unfiltered data as recorded by the system. **Caution:** The “AutoCorr” Processing Object is only allowed to be placed in the first stage of the Processing Queue. Additionally, there is only one “AutoCorr” object allowed to be configured inside the complete Processing Queue! **Caution:** The “ExecuteShellScript” Processing Object is only allowed to be placed at the bottom of each ProcessingTree, just above the “ATSWriter” Processing Object Additionally, there is only one “AutoCorr” object allowed to be configured inside the complete Processing Queue! Processing Object – ATSWriter ''''''''''''''''''''''''''''' The processing object “ATSWriter” writes the data which it receives to the storage media. The data is stored in the Metronix Advanced Time Series (ATS) file format. This “Processing Object” does not have any further parameters. Processing Object – DigitalFilter ''''''''''''''''''''''''''''''''' The processing object “DigitalFilter” provides a digital filtering of the incoming data. Presently, four types of filters can be selected: .. csv-table:: Filter types for “DigitalFilter” “Processing Object” :delim: | **Type**|**Description** mtx32x|This will activate a FIR filter and a data decimation by factor 32. E.g. : If you have sampled with 128 Hz, the resulting sampling frequency on the output of the “Digital Filter” object will be 4 Hz. Mtx8x|This will activate an 8 times data reduction. It works similar as the mtx32x filter. Mtx4x|This will activate a 4 times data reduction. Mtx2x|This will activate a 2 times data reduction. The following picture shall describe the operation of the “DigitalFilter” “Processing Object”. IMAGE Functionality of “DigitalFilter” “Processing Object” As you see in the picture above, the “DigitalFilter” will decimate the incoming data rate by the decimation factor d. **Information:** The “DigitalFilter” “Processing Object” itself will not write any data to the CF-card. Therefore you always have to connect an “ATSWriter” object to it in order to write the data to the storage media. Otherwise, data will be lost! Processing Object – SubJobManager ''''''''''''''''''''''''''''''''' The “SubJobManager” “Processing Object” splits the incoming time series into individual time series, each referring to a defined time slice. Therefore you have to configure the start- and stop times of the time slices, during which data shall be sent to the connected “Processing Objects”. The parameters are described in the following table: .. csv-table:: Parameters for “SubJobManager” “Processing Object” :delim: | **Type**|**Description** start day|This is the start day of the time slice. start month|This is the start month of the time slice. start year|This is the start year of the time slice. start hour|This is the start hour of the time slice. start minutes|This are the start minutes of the time slice. start seconds|This are the start seconds of the time slice. stop day|This is the stop day of the time slice. stop month|This is the stop month of the time slice. stop year|This is the stop year of the time slice. stop hour|This is the stop hour of the time slice. stop minutes|This are the stop minutes of the time slice. stop seconds|This are the stop seconds of the time slice. For each time slice that shall be added to the “SubJobManager” one complete set of the parameters listed above has to be entered. The “SubJobManager” object will output data during those time slices only, that are configured for it. The following picture describes the behavior of the “SubJobManager”: IMAGE Functionality of “SubJobmanager” “Processing Object” **Information:** Similar as the “DigitalFilter” “Processing Object” the “SubJobManager” will not write data to disk by itself. Therefore, it requires an “ATSWriter” object connected to it, too. Processing Object – OpenMT_DataInterface '''''''''''''''''''''''''''''''''''''''' The “OpenMT_DataInterface” “Processing Object” is used to send the recorded data on-line (in real-time) via a TCP/ IP socket interface to any client, which is connected to it. Normally, this “ProcessingObject” is part of the “OpenMT” / “ViewMT” on-line processing software from Metronix. If included in the “ProcessingQueue” the “OpenMT_DataInterface” will wait for a buffer of a certain size to be recorded, resort the data and send it to any client connected via the socket interface. For this purpose the “ProcessingObject” has the following parameters: .. csv-table:: Parameters for “OpenMT_DataInterface” “Processing Object” :delim: | Type|Description Port Number|The port number, that shall be used by the ADU-07e system to send data to the client. Input Buffer Size|The size of the data buffer used by the “OpenMT_DataInterface” to send it to the client. It will only send chunks of data of this size. Start local OpenMT Client|If this flag is true, the “OpenMT_DataInterface” will try to start an local client process of the “OpenMT” processing tool. This process will receive the data from the “OpenMT_DataInterface” and do an on-line data processing. The results will be stored in the local MySQL database. The data buffers, that are sent to the client are sorted as shown below: IMAGE Sorting of data buffer for “OpenMT_DataInterface” “Processing Object” As it can be seen in the picture above the first 4 bytes of the data buffer allways contain an unique identifier “0xAA55NNNN” as the first to bytes are fixed to the value 0xAA55, that will never occur in a real data sample on the first two bytes. The last two bytes “NNNN” of the identifier are the continous number of the data buffer, that was transmitted. This way the client may easily check, if he missed to receive some data by allways saving the number of the last data buffer and comparing it to the one of the new data buffer. Next to the identifier the data buffer contains the measurement data for the single channels. The data is sorted in the way that can be seen in the picture above because now shift between the time series of the single channels will occure, if parts of the data will be lost. If an “OpenMT_DataInterface” is configured inside your “ProcessingQueue” the structure of the on-line data processing, that shall be done by the “OpenMT” software can be configured on two new pages of the ADU-07e Webinterface. This pages are described in the following chapters. **Information:** Allways make sure to have an “ATSWriter” “ProcessingObject” configured parallely to your “OpenMT_DataInterface” because the “ATSWriter” will write the time series data to the internal CF-card, even if the connection between the “OpenMT_DataInterface” and its client will be cut. **Information:** If the connection is cut between the “OpenMT_DataInterface” and its client during an measurement, no data is able to be transmitted from the ADU-07e system to the client anymore. In this case the ADU-07e system will continue to record data and, if configured, write the data to disk by the use of an “ATSWriter” processing object. As soon as the connection is established again, the “OpenMT_DataInterface” will continue to send data to the connected client. Processing Object – AutoCorr '''''''''''''''''''''''''''' The “AutoCorr” “Processing Object” is used to adapt the gain and DC offset correction settings of the ADB boards that are used in a currently running job to the characteristics of the recorded time series signal. This shall guaranty best possible data quality and avoid overload of the ADB boards which would result in useless data, e.g. caused by strong DC drift. For this purpose the “AutoCorr” has the following parameters: .. csv-table:: Parameters for “AutoCorr” “Processing Object” :delim: | **Type**|**Description** Do Gain Switching|By the use of this flag it can be allowed / prohibited to switch gains during the running job. Do DC Offset Switching|By the use of this flag it can be allowed / prohibited to switch DC offset correction during the running job. Inhibit Time|This parameter is used to configure a minimum time between two gain / DC offset correction switching cycles. Please note that due to ADU-07e hardware design the gain switching, and especially DC offset correction cannot be executed in zero-time. As a result for each switching cycle you will see sections of invalid time series data. A gain switching cycle will produce invalid data for approximately 2 .. 3 seconds. A DC offset switching cycle will produce invalid data for 15 seconds, as in this case the ADB boards need to be stopped, reconfigured and afterwards restarted. In the mean time fill samples with value 0mV will be written to the time series data files. To be able to find these invalid data areas an ATM file is written along with the ATS data files, if the “AutoCorr” Processing Object is active. This file can be imported, e.g. into MAPROS to automatically deselect these areas for data processing. See the following figures for gain and DC offset switching cycles. IMAGE marked “Gain Switching Cycle” via ATM file in Mapros IMAGE marked “DC Offset Correction Switching Cycle” via ATM file in Mapros **Caution:** If using the “AutoCorr” Processing Object all gain and DC offset settings for the ADB channels MUST be set to their defaults (gain 1 and DC offset correction 0mV) when starting the job. Processing Object – ExecShellScript ''''''''''''''''''''''''''''''''''' The processing object “ExecShellScript” is used to start a “Shell Script” on the ADU-07e Linux system at the end of each job / subjob. The object is placed just above the “ATSWriter” object inside the single “ProcessingTrees” (see example below). IMAGE configuration of “ProcessingQueue” for use of “ExecShellScript” ProcessingObject In case of a “ProcessingQueue” configured as shown the above shell script will be executed at the end of the digitally filtered continuous job and at the end of each one of the configured subjobs. The “ProcessingObject” gets the full path and name of the “Shell Script” to be executed as parameters. Up to two parameters can be handed over to the called Shell Script. IMAGE parameters of “ExecShellScript” ProcessingObject The user defined parameters are enriched by some parameters that are handed over to the called shell script by MCP. The complete list of parameters that the called shell script will receive is shown inside the underneath table: .. csv-table:: parameters of Shell Script being called from a “ExecShellScript” Processing Object :delim: | **Parameter Nr.**|**Content**|**Description** 0|/mtdata/mcp_sys/ testShellScript1|This paramater contains the path and name of the called shell script itself. 1|/mtdata/data/ meas_2012-11-27_13-10-56|This parameter contains the pathname of the “measuremnt” directory where all ATS and XML data files of the measurememt are stored in. 2|153_2012-11-27_13-10-56_2012-11-27_13-11-56_R000_1024H.xml|This parameter contains the name of the “meas-doc” XML file that contains the complete job description of the job / subjob that caused the execution of the script. 3|153|This parameter contains the serial number of the ADU-07e. 4|R000|This parameter contains the Run Number of the job / subjob that caused the execution of the script. 5|1024H|This parameter contains the Sampling Frequency of the job / subjob that caused the execution of the script. 6|1354021920|This parameter contains the stop time of the job / subjob as UNIX timestamp (seconds since 01.01.1970 00:00:00). 7|param1|This parameter contains the first user defined parameters. 8|param2|This parameter contains the first user defined parameters. Same as for the “Execute Shell Script” Event job the shell script is executed in parallel to the MCP process. Therefore the measurement which started the shell script will not wait for its execution. The channels will be directly free for a new measurement as soon as the shell script is started. Page “General – OpenMT Processing Queue” '''''''''''''''''''''''''''''''''''''''' To configure the on-line processing of a connected “OpenMT” client a new page “OpenMT Processing Queue” is implementd inside the ADU-07e Webinterface. It may be entered from the “OpenMT_DataInterfaces” part of the “Processing Details” page and has the following style: IMAGE Page “General – OpenMT Processing Queue” As it can be seen in the picture above, the new page is build up in the same way as the configuration page for the standard ADU-07e “Processing Queue” (see chapter 8.2.3). The difference between the two pages is, that the configuration done on this page is only evaluated by an connected “OpenMT” client process. For the “OpenMT” data processing the structure is limited to a linear structure with the data flowing from top to bottom through the queue. In the example shown in the picture above, the data would be freed from any trend and offset, scaled by E-field length and window function, transformed into spectra data, scaled with the transfer functions of the connected sensors and finally be parzened and stacked up. In a last step the data will be written as “edi-xml” file to the local database or to disk. The configuration of the single parameters of the “OpenMT Processing Queue” is done by the use of the “General – OpenMT Processing Details” page that can be entered by clicking on the *Show OpenMT Processing Details* on this page and is described in the following chapter. Page “General – OpenMT Processing Details” '''''''''''''''''''''''''''''''''''''''''' To configure the on-line parameters of the “OpenMT Processing Queue” the page “General – OpenMT Processing Details” is used. IMAGE Page “General – OpenMT Processing Details” As it can be seen on the picture above, the page is build up in the same way as the “General – Processing Details” page that is already described in detail in chapter 8.2.3. The difference is that on this page the parameters for the “Processing Objects” for the “OpenMT” client process are configured. As they are mainly part of the “OpenMT” / “ViewMT” software they are described in detail in the OpenMT manual. Processing Object – TSStack ''''''''''''''''''''''''''' The “TSStack” “Processing Object” is used to do a “time series stacking” of the recording data directly on the ADU-07e system. As a result a subsequent “ATSWriter” will only write the stacked data to disk. The object has the following parameters: .. csv-table:: parameters for “TSStack” “Processing Object” :delim: | **Type**|**Description** Number of Stacks|This parameter is used to select the number of stacks that shall be stacked up before one output stack is generated for the normal “time series stacking”. Stack Length|This parameter is used to enter the length of the time series stack in samples. In normal operation this parameter is set to “0” which will cause the “Output Buffer Length” to be used as “Stack Length”. Output Buffer Length|This parameter defines the length of the output buffer of this Processing object in number of samples. In normal operation it will be set to the same size as the “Stack Length” parameter. If it is smaller than the “Stack Length” parameter, only the first “Output Buffer Length” of samples will be used. The rest will be discarded. If it is bigger than the “Stack Length” it is automatically set to the “Stack Length” as it must always be smaller or equal to the “Stack Length”. Mode|The “TSStack” object can do the “time series stacking” in “software” and “hardware” mode. In “software” mode the time series stacking will be done on the CPU board, which causes some additional CPU load. In “hardware” mode the time series stacking will be done on the “backplane” hardware directly which reduces CPU load and USB transmission load. As a result the time series stacking can be done at much higher sampling frequencies. Median Stack Length|As a robust stacking method the “TSStack” object can do an additional “Median Stacking”. If no “Median Stacking” is activated (Median Stack Length = 0), the “TSStack” “ProcessingObject” will do a simple time series stacking. Therefore it will allocate an internal stacking buffer of “Stack Length” samples. Incoming data will be added to this buffer “Number of Stacks” times. Afterwards, the contents of the “Stack Buffer” will be divided by the “Number of Stacks” and written to the “Output Buffer” for a further data processing by subsequent “ProcessingObjects”. Depending on the “Mode” flag (software or hardware) the time series stacking will be done either on the CPU board or by the hardware on the backplane. The normal “time series stacking” is good to reduce the noise, if the target signal is a periodic signal, e.g. if doing CSAMT or TEM measurements. It should not be used in normal MT, as in this case the MT data itself will be stacked away. If the “Median Stack Length” parameter is set to a value bigger than 0 an additional “Median Stacking” will be applied. In this case the “TSStack” object will allocate an additional number of “Median Stack Length” data buffers. These data buffers will be filled up with the incoming data. After all buffers are filled with data, they will be sorted in ascending order for all samples. Finally, the midst data buffer will be used as output buffer. The following picture shall describe the operation of the “Median Stacking” IMAGE Functionality of “Median Stacking” in “TSStack” “Processing Object” The “Median Stacking” is a good methodology to eliminate the influence of random noise elements, such as spikes. The outliers on the bottom and top are stacked away. Same as for the normal “time series stacking” this mode should not be used for standard MT data. Processing Object – MovingMTManager ''''''''''''''''''''''''''''''''''' The “MovingMTManager” “Processing Object” is used to execute a measurement job in the special “Moving MT” mode. The object has the following parameters: .. csv-table:: parameters for “MovingMTManager” “Processing Object” :delim: | **Type**|**Description** N/A|This object does not have additional parameters If this “Processing Object” is configured as part of the “Processing Queue” the connected “ATSWriter” object will operate in the special “Moving MT” mode. It is used for applications, where the user wants to record many sites with only short recording lengths for each site. In this case the user will start the new measurement in the same way, as for a normal measurement but includes the “MovingMTManager” in the “ProcessingQueue”. As a result the ADU-07e system will start the measurement, but will not write any data to disk. It is indicated by the three LEDs on the Front-panel which will blink. Now, the user can carry the system to the next site. On the new site location he will do a “GPS Warm Start” to re-synchronize the GPS at the new location. Afterwards, he will use the “Start Moving MT” mode button on the “Start Job” Page of the Web-interface to start writing of data to disk **Information:** Using the “USB Device - Remove” option on the ADU-07e Front-panel will have the same effect. You can toggle the recording on/off. After the desired time has passed the user can stop writing data to disk by executing the “Stop Moving MT” button on the “Start Job” page of the Web-interface . As a result the ADU-07e will stop writing data to disk which is signalled by the Front-panel LEDs starting to blink again. Now the user can move the system to the next site and start the procedure again. Example of a Complex Processing Queue ''''''''''''''''''''''''''''''''''''' This chapter explains the use of the Processing Queue by showing its operation with a more complex setup. In this example the user wants to get the following data from the measurement: 1. Long term time series using a sampling frequency of 32 Hz. 2. Within the long-term time series multiple short-term “HF” shots with a sampling frequency of 1024 Hz shall be recorded. In order to realize this application, the job is started with a sampling frequency of 1024 Hz and the desired time parameters on the “General – Start Job” page. Additionally, the Processing Queue is parameterized, as shown below: IMAGE structure of Processing Queue as an example We see here two active paths in the “Processing Queue”. The first path receives the incoming data stream with a sampling frequency of 1024 Hz, then performs a digital filtering and finally writes the filtered time series to the storage media. The second path will chop the incoming time series into time slices. These time slices refer to the high frequency shots, the user wants to record. The outgoing data will be saved in ATS files. Each of them contains the data for one time slice. Before the measurement can be started, the discrete Processing Objects must be configured as shown in the following picture: IMAGE Parameters for Processing Objects as an Example With the configuration of the Processing Objects from the pictures above, the ADU-07e system will start recording with a sampling frequency of 1024 Hz. The incoming time series will be filtered by the “mtx32x” digital filter and then will be written to the disk. As a result an ATS file with the following name will be created for each channel: .. code:: 008_V01_CXX_R001_TXX_BL_32H.ats On the second path the time series will be written to disk only during the three pre-defined time slots. This will cause the ADU-07e system to write three additional ATS files for each channel, each containing the time series for one of the time slices of unfiltered measurement data. As a result the following ATS files will be written to disk: .. code:: 008_V01_CXX_R001_TXX_BL_1024H.ats 008_V01_CXX_R002_TXX_BL_1024H.ats 008_V01_CXX_R003_TXX_BL_1024H.ats Page “General – Site Config” ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ If you click on the menu entry “Site Config”, you will see this page: IMAGE Page “General – Site Config” of the Web-interface It is the “General – Site Config” page. You may enter some additional information about the measurement to be started. The information is stored within the XML job file and also in the header of the ATS files that contain the measurement data. All this information is intended to help you during a later data processing to identify the measurement. Some of the information, such as the “Run Number” is directly used for the creation of the ATS filenames. On the right part you may enter some information about the transmitter which will be used for automatic data processing with PROCMT. Page “General – Options” ^^^^^^^^^^^^^^^^^^^^^^^^ If you click on the menu entry “Options”, you will see this page: IMAGE Page “General – Options” of the Web-interface Different parameters that refer to the functionality of the Web-interface can be entered here. Up to now, the only parameter that can be set up, is the offset from UTC to your local time. As the ADU-07e system uses the “Universal Time Coordinates” (UTC) for all time values, you would see UTC and not the local time in the time info fields of the Web-interface. To get the time information in local time, you have to select your time zone in the entry-field “Current UTC time-zone”. After you have clicked on the *Save* button, all time information will be displayed in local time. If your time zone uses daylight saving time, you additionally have to activate this by a tic. **Information:** The time offset is only active within the Web-interface. If you access the ADU-07e system directly, for example via SSH, the time values will still be displayed in UTC. The time information that is shown on the front panel display is also the current UTC time. Page “General – Load/Save” ^^^^^^^^^^^^^^^^^^^^^^^^^^ If you click on the “Load / Save” section of the menu area you will see these entries in the menu: IMAGE Page “General – Load / Save” of the Web-interface These menu entries are used to store the current settings that you made in the Web-interface. By this means the entered parameters can be automatically loaded next time when you connect the ADU-07e. Furthermore, the current configuration can be deleted and the complete Web-interface can be restarted with its default values. Page “General – Load/Save – Save Session” ''''''''''''''''''''''''''''''''''''''''' If you click on this menu entry, the current settings of the Web-interface will be saved in the connected ADU-07e. By this means you can use them next time when you connect to the system. If you click on the menu entry *Save session*, a dialogue will occur, that asks you, whether you are sure to save the settings: IMAGE When you press the *OK* button, the current settings will be saved and confirmed by the Web-interface showing the following dialogue: IMAGE **Information:** All existing data will be overwritten. Page “General – Load/Save – Load Session” ''''''''''''''''''''''''''''''''''''''''' If you connect to an ADU-07e system the first time after boot-up of the system, the Web-interface will come up with default values. By clicking on the *Load last session* entry in the menu, the previously saved session from the ADU-07e system will be restored again with all its parameters. You will be asked to confirm that you want to load the last saved session and overwrite the current settings: IMAGE A click on the *OK* button will load the last saved session. All pages in the Web-interface will show the values of this session now. A confirmation will be given with the following dialogue: IMAGE If you did not save any session before, a click on “Load Session” will initialize the ADU-07e Web-interface by its default values again. If you load the last existing session, all settings that you have entered in the Web-interface pages before will be overwritten by the settings stored in the last saved session. Page “General – Load/Save – Restart Session” '''''''''''''''''''''''''''''''''''''''''''' It may happen, that you completely miss-parameterized the Web-interface. A re-initialization can be effected by clicking on the *Restart session* entry in the menu. It will erase the current session and completely re-initialize it from the systems that are connected to the network. After you clicked on the “Restart Session” entry, the Web-interface will ask you to confirm this by showing the following dialogue: IMAGE As soon as you confirmed the question by clicking on the *OK* button, the current session is going to be erased and freshly initialized. All pages in the Web-interface will show the default values again and be confirmed by a dialogue box: IMAGE Page “General – Shutdown” ^^^^^^^^^^^^^^^^^^^^^^^^^ If you click on the “Shutdown” menu entry, you will see this screen page: IMAGE Page “General – Shutdown” of the Web-interface On this “General – Shutdown” page you have the possibility to shut down the ADU-07e by clicking on the *Shutdown* button. The Web-interface will ask you to confirm your action: IMAGE After you confirmed the question by clicking on the *OK* button, the Web-interface will create a “Shutdown” XML job and write it to the MySQL database. From there it will be executed and the system will shut down. **Information:** Once the “Shutdown” job was created and executed by the ADU-07e, you will see a corresponding message on the front panel display and all LEDs will indicate that the system is about to shut down by blinking. After the LEDs on the front panel started to blink, it will take another 30 seconds, until the systems power supply can be switched off. This time is required to shut down the Linux operating system inside the ADU-07e. The shutdown procedure cannot be aborted once you confirmed it by clicking on the *OK* button. System Specific ADU-07e Web-interface Pages ------------------------------------------- On the system specific pages of the ADU-07e Web-interface you will enter configuration data that is only valid for one single ADU-07e. This may be for instance gain-settings, filter-settings etc. You enter the system specific pages by clicking on the *ADU-8* field with the serial number of the ADU-07e system, you want to work on. Afterwards, the following page is shown: IMAGE Page “System specific – start page” of the Web-interface As you can see in Figure 8-37, in addition to the content of the data area, the content of the menu area has changed, too. Now, you see all menu entries referring to the system specific pages of the ADU-07e Web-interface. IMAGE Menu entries for system specific pages of the ADU-07e Web-interface The system specific pages of the Web-interface are grouped in three sections, * “Configuration”, * “Status” * “Management”. * “Job Lists” These sections contain further menu entries that call pages of the Web-interface directly. The initial page displayed is the “System Specific – System Status” page. The menu entries, “Startpage”, “Start Job”, “Stop Job” and “Shutdown” are identical with those on the “ADU-General” pages of the Web-interface. Therefore they won´t be explained here again. Section “System Specific - Configuration” ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The section “System Specific - Configuration” of the menu contains all menu entries used for pages, that refer to the configuration of one single ADU-07e: IMAGE Menu entries for section “Configuration” of the ADU-07e Web-interface As you can see in Figure 8-39 the “Configuration” section contains menu entries which refer to three further pages of the Web-interface. Page “System Specific – Configuration - Channels” ''''''''''''''''''''''''''''''''''''''''''''''''' After having clicked on the *Channels* entry in the menu, you will see the following page: IMAGE Page “System Specific – Configuration – Channels” of the ADU-07e Web-interface This page is used to configure individual ADB boards of the ADU-07e. You can set up gains, filters and other parameters that refer to the ADB channels and their connected sensors. The page is split up into two sections (Figure 8-40). On the bottom of the page, you recognize the section “Calibration Signal”. It contains control elements required to operate the ADU-07e’s internal calibration circuitry which delivers well defined signals at different stages of the ADB boards allowing their test and calibration. The single input elements have the following functionality: .. csv-table:: Parameters for calibration board on page “System Specific – Configuration - Channels” :delim: | **Element name**|**Description** Mode|With this selection box you can choose the operation mode of the calibration signal unit. By selecting the different modes, the calibration signal is fed into different stages of the measurement hardware. These modes are available: |CalOff: The calibration signal is completely switched off. The ADB channels will record data from the regular measurement input. |CalInt: The calibration signal is fed into the signal input of the ADB boards. The calibration signal is a square wave signal with well defined amplitude of +/-24.782 mV. |CalRef: The calibration signal is directly fed into the Analog / Digital converter ICs (ADCs) of the ADB boards here. The signal is a symmetrical square wave with amplitude of +/- 2.5V. |CalSensor: In this mode the calibration signal is fed into the sensors. It is used to record the transfer functions of the sensors. |ShortCircuit: The input of the ADB boards is short-circuited allowing noise measurements. Please note that it is not a true short-circuit but two 10k resistors from the differential inputs to Ground. Frequency|Here you select the frequency of the calibration signal. Attenuation|An additional attenuation for the calibration signal can be selected here. In most cases the operation mode for the calibration unit will be set to “CalOff” and signals from the measurement input will be recorded by the ADB board. As only one calibration board is installed in the ADU-07e system, it cannot be used in different modes or with different settings at the same time. Therefore, it is checked at measurement start time, whether the calibration board is already in use by a different measurement task. If so, the new measurement will only be started, in case it uses the calibration board in exactly the same configuration. Otherwise, the new measurement will not be started and an according error message will be added to the “System History” and the “Error Log”. Just on top of the “Calibration Board” section you find the “Channel Configuration” section. It contains all input elements to select the hardware configuration for the ADB channels. This can be gains, filters etc. As you see in Figure 8-40, the LF, MF and HF channels are listed in different tables. So for instance you may switch to the HF channels by clicking on the *Show HF-Channels* button. By clicking on the *Save* button, all settings are stored and will be available for the next measurement you will start. Furthermore, in the same area you will find the *Use AutoGain/Offset* button. Clicking on this button will use the current “AutoGain AutoOffset” settings, that are displayed on the “Self-test Results” page. The “Gain Stage 1”, “Gain Stage 2” and “DC Offset Correction” values will be updated accordingly. If clicking on the *Use AutoGain/Offset* button the following warning messages may be shown: IMAGE Figure 8-41: “Use AutoGain AutoOffset” warning message – values too old This message is shown, if the “AutoGain AutoOffset” values are older than 1 day. The “AutoGain AutoOffset” values strongly depend on the measurement site. In case the values are older than 1 day it is recommended to restart the “AutoGain AutoOffset” jobs via the “Selftest Config” page to adapt settings to the current measurement site. Nevertheless the settings for gains and DC offset correction are updated by the ones of the “AutoGain AutoOffset” values. The second warning message that may be shown is the following: IMAGE “Use AutoGain AutoOffset” warning message – system has been moved This message is shown, if the current GPS position is more than 200 meters away from the GPS position that belongs to the “AutoGain AutoOffset” values. Same as for too old values it is again recommended to restart the “AutoGain AutoOffset” jobs. The values will be updated again. By the use of the *Save AutoGain/Offset* the currently selected configuration of the ADB boards can be saved as “AutoGain/AutoOffset” settings, so e.g. a started joblist from USB stick would use these settings. Finally, in the table of the “Channel Configuration” section, you will find the following input elements: .. csv-table:: Parameters for ADB boards on page “System Specific – Configuration - Channels” :delim: | **Element name**|**Description** Value |In this field you see the channel number for which you make the settings. If you change settings in the column named “All”, the changes made apply to all channels. Use for Measurement|This checkbox is used to activate the ADB channel which shall be used for the next measurement. Type|This field displays the type of the ADB channel. You cannot make any inputs here. It is just implemented for clarification. Gain Stage 1|With this Combobox you may select a gain value for the first gain stage on the ADB boards. Gain Stage 2|With this Combobox you may select a gain value for the second gain stage on the ADB boards. Offset Correction|An offset compensation value for the ADB boards may be entered here. The value can be between +2500mV and –2500mV. It is applied to the input signal on the ADB boards behind the first gain stage. A “0” entry will switch off the offset compensation circuitry. |Note: The offset compensation is only available for the LF and MF ADB boards. Filter Type|This input element is used to select the filters that shall be used by the ADB board in the next measurement. You may select multiple filters to work parallel in the next measurement. The filters are selected by holding the “Control” key and clicking on the desired filters with the mouse. The same way they can be deselected. |Note: Some combinations of filters are not supported by the ADU-07e. If you select an invalid filter combination, the ADU-07e system will automatically select a default configuration. For a list of valid filter combinations, please refer to chapters 9.3.2 and 9.4.1. Chopper |By activating this Checkbox, the chopper amplifier in the magnetic field sensors will be activated. Chopper amplifier is switched on by entering a 1. |Note: The chopper amplifier shall be switched on for sample frequencies equal or smaller than 512 Hz. If it is forgotten, low frequency recording cannot be made! The ADU-07e Web-interface will provide a warning message if an obviously wrong chopper setting has been made and it can auto-correct this. Input Connection|With this Combobox, you may select the input that shall be used as source for the ADB boards. The following values are possible: |Input 0: In this mode, the ADB channel will use the single inputs for each channel as source. These inputs are marked with the names “Hx”, “Hy”, …. |Input 1: If this is active, the input 1 is selected. In this case the ADB boards will use the large Combi connector “IN2” as source. Used ADU-07e Connector|This is a read-only box. Depending on the ADB channel number and the current value of the “Input Connection” field for this channel it shows the name of the ADU-07e Connector which will be used as input for this ADB channel. E.g. for ADB channel 0 and the “Input Connection” value set to “0”, the used Connector will be Ex. If the “Input Connection” is set to “1” instead, the used Connector will be “IN2-0” on the Multi-Purpose Connector. Sensor Type|This is a read-only box, too. It just shows the sensor type that will be used for this ADB channel. The sensor type can be set-up on the “Sensor Position” Page (see 0). Sensor Name|This also is a read-only box just showing the sensor’s name. See 0). Sensor Serial|A read-only box which displays the sensor’s serial number. Please refer to chapter 0). As you can see in Figure 8-40, there exists an additional column named “All” in the “Channel Configuration” section of this page. Any changes to one of the elements in this table column will apply to all the channels in the table. For example if you select gain 64 for the entry “Gain Stage 1” in the “All” column, the value for “Gain Stage 1” would be set to 64 for all channels in the table. The former values are overwritten. For some values it does not make sense to set them for all channels displayed in the table. **Information:** Currently, the Web-interface does not protect you from invalid configuration for the single ADB boards Therefore you may for example start a measurement with invalid filter settings or sampling frequencies. The ADU-07e system will detect these conflicts at start of the measurement and will use default values instead. The reaction of the ADU-07e system in case of miss- parameterization is described in chapter 18. Page “System Specific – Configuration – Sensor Positioning” ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' After you clicked on the *Sensor pos.* entry in the menu, you will see this screen: IMAGE Page “System Specific – Configuration – Sensor Positioning” of the ADU-07e Web-interface This page is used to enter the configuration for the sensors. The sensors configuration consists of the following settings for each sensor: * **“Sensor Type”** The “Sensor Type” is the type of the sensor, e.g. EFD06, MFS06, …. You may only select one of the pre-configured sensor types from the according input box * **“Sensor Name”** The “Sensor Name” defines the way, the data that is recorded with this sensor shall be interpreted in a later data processing. * **“Sensor Serial Number”** The “Sensor Serial Number” is used to identify the sensor for means of back tracing. It is stored inside the “meas-doc” XML files that are stored along with the measurement data. * **“Sensor Positioning Data”** The “Sensor Positioning Data” is used for later data processing. For each sensor you find an input field like this: IMAGE Inside this input field in the heading you see the name of the ADU-07e connector in which the sensor is plugged in. In the example above, the sensor is actually connected to Connector “Ex” on the ADU-07e. As there is a total number of 10 possible Connectors for sensors on the ADU-07e (“Ex”, “Ey”, “Hx”, “Hy”, “Hz” and 5 connectors on the Multi-Purpose Connector “IN2”) you have to configure all the 10 sensors on this page. Inside the input boxes “Sensor Type”, “Sensor Name” and “Sensor Serial” you have to enter the general sensor configuration as described above. Note that if using the ADU-07e with the new “intelligent sensors” like “MFS06e” and “MFS07e” the “Sensor Type” and “Sensor Serial” will be detected automatically when booting up. If the sensors have not been connected during boot-up of ADU-07e, you can restart the sensor detection by the use of the “Detect Sensors” button. IMAGE After the sensor detection was done you need to “Reload Sensor Config” button to update the sensor information given on this page by the newly detected settings. Furthermore, you have to enter the sensor positioning information for each sensor. Below the general configuration boxes you see input boxes for the position values for the single sensors in the layout. The following coordinate system is used: IMAGE Coordinate system for “Sensor Positioning” Note, that the coordinates, Pos-X1 / Pos-X2, Pos-Y1 / Pos-Y2 and Pos-Z1 / Pos-Z2 are only necessary for the electrical field sensors, as here always one pair of electrodes is connected to one single ADB channel. The first section defines the position of the first sensor and the second section the one of the second sensor. The ADU-07e is always considered to be the center of the coordinate system. Therefore, you have to type in all coordinates relatively to the ADU-07e system (in meters). After you have entered the complete sensor positioning data for all required channels, you have to store the input by clicking on the *Save* button. **Note:** Some customers do not use position data in x, y and z coordinates but only dipole length and the azimuth. This easily can be converted into coordinates which can be entered in the ADU-07e Web-interface´s “Sensor Pos” Page. Here, the x axis always points to the north. See the following Example: IMAGE Example set-up to determine sensor pos out of azimuth :math:`\\DipoleLength = \sqrt{\left( {Y2 - Y1} \right)^{2} + \left( {X2 - X1} \right)^{2}}` :math:`\\DipoleAngle = {\mathit{\arctan}\left( \frac{\left( {Y2 - Y1} \right)}{\left( {X2 - X1} \right)} \right)}` Section “System Specific - Self-test Config” '''''''''''''''''''''''''''''''''''''''''''' The “Self-test Config” page enables to change the “Self-test Configuration”. It looks like the following: IMAGE Page “System Specific – Configuration – Self-test Config” of the ADU-07e Web-interface The page is split up into two sections. Inside the “Restart Self-tests” section you may choose a list of self-test jobs that should be started. There is the possibility to restart the self-test job that measures the probe resistance. To restart the self-test, the corresponding list can be selected with the “Choose Self-test List” box. Afterwards, the list of self-tests is restarted by clicking on the “Restart List” button. As a result the ADU-07e will go into “Self-test” operation mode and restart the self-test. The results will be displayed on the “Self-test Results” page of the Web-interface. The functionality of the single lists will be explained in the following table: .. csv-table:: Selftest Lists to be restarted :delim: | **List name**|**Description** Probe Resistance Probe Resistance (LF) Probe Resistance (MF) Probe Resistance (HF)|These lists will restart the needed self-test steps to determine the “DC Offset” and probe resistance on the single sensor inputs. After being executed, the displayed values on “System Status” menu entry on Front-panel display and on the “Selftest Results” page of the Webinterface will be updated. |Note that the first list will execute the needed self-test steps for all ADB board types. The other lists will execute the steps only for the specific ADB board types (LF, MF or HF). This may save some time. Gain Calibration (LF) Gain Calibration (MF) Gain Calibration (HF)|These lists will restart the “Gain Calibration” process for the ADB boards. The “Gain Calibration” will compute correction factors for the slightly different gains of the gain stages of the different ADB boards. This needs to be done to have 100% the same amplitude on all ADB boards. |Once the correction factors have been determined, they are written to a flash memory on the ADB boards. From there they are read each time the ADU-07e system is booting up. |Therefore the “Gain Calibration” does not need to be executed each time the system is booting up. It is recommended to redo the procedure every half year. AutoGain AutoOffset (LF) AutoGain AutoOffset (MF) AutoGain AutoOffset (HF)|This list will execute the single selftest jobs to determine the “AutoGain AutoOffset” values. Therefore they analyze the current signal on the sensor inputs and compute the best fitting values for Gain Stage 1 gain, Gain Stage 2 gain and DC offset correction for the ADB boards. |These values are stored inside the MySQL database and can be used for jobs / job-lists, either by pressing the “Use AutoGain/Offset” button on the “Channels” page of the Webinterface, or by setting the “AdaptChannelConfig” node to “TRUE” inside the “ADU07Conf” XML file. Inside the second section called “Change Self-test Configuration” you may change the configuration of the self-test procedure that is executed each time the ADU-07e system is booting up. There are three possible configurations: * **Full Self-test:** This is the default self-test configuration. In this mode all the self-test steps are executed. It is advised to execute this self-test configuration at least once a week (during a running survey) to make sure, that the hardware is still running correctly. Nevertheless, this is the self-test configuration that is most time consuming. * **Short Self-test:** If this self-test configuration is used, only those self-test steps are executed that are needed for internal calibration of the ADU-07e system. No checks for correct functionality of all hardware components, such as filters, DC offset compensation etc. are done. This configuration should be used, if the system is powered up multiple times a day to change sites, as it is much less time consuming, then the “Full Self-test”. Nevertheless the “Full Self-test” should be executed in regular intervals to make sure that all hardware components are working correctly. * **No Self-test:** This configuration will execute NO self-test steps at all. Therefore, it is the fastest one. Nevertheless, it MUST not be used in normal survey work, as NO INTERNAL CALIBRATION is done. The system is able to record data, but the LSB values are only default values. Therefore the displayed amplitudes of the data in “TSPlotter” and “Mapros” will not be precise. This configuration should only be used to tests SW updates and not for field work. Additionally, you have the possibility to activate the “Full”, “Short” or “No” selftest with additional “Wait for G3Fix”. If this is activated at the end of the self-test procedure the ADU-07e system will wait for 15 minutes, or until a “G3Fix” was gained, before the “self-test” finally ends. This mode is useful, if you want to make sure that a pre-progammed joblist is not started before a GPS fix has been achieved. *Caution:* Do not use the “No Self-test” configuration for field work as in this configuration no internal calibration is done. Section “System Specific - Status” ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The menu is structured as shown in the following picture: IMAGE Menu entries for section “Status” of the ADU-07e Web-interface As you can see in Figure 8-47 the section for “Status” of the ADU-07e system contains menu entries, that refer to 4 more pages of the Web-interface. These will be explained in detail in the following chapters. Page “System Specific – Status – System Status” ''''''''''''''''''''''''''''''''''''''''''''''' After you clicked on the *System Status* entry in the menu, you will see the following page: IMAGE Page “System Specific – Status – System Status” of the ADU-07e Web-interface The current status of the ADU-07e is displayed here. As one can see in Figure 8-48 the page is split into five main sections. These are the “Recording Status”, “System Status”, “GPS Status”, “Disk Space” and “Error List” sections. All these sections refer to the selected ADU-07e. In the “Recording Status” section you get information, whether the system is currently recording data, or whether it is in idle mode. Additionally, you can see the fill level of the buffer memory. The displayed elements have the following meaning: .. csv-table:: Parameters section “Recording Status” on page “System Specific – Status – System Status” :delim: | Element name|Description State|It shows you the current recording status of the system: |Recording (x): The system is currently recoding data. In this case the “x” will show the number of presently running measurements. |Idle: The system is idle. No measurement is active at present. |If any measurements are active, for each of them one row will be created in a chart, consisting of 6 columns as described below: Time to Next Job|This element shows the time to the next job that will be started by the ADU-07e system. It displays the time in the following format: DDD days, HH:MM:SS DDD: days till start time of next job HH.: hours MM.: minutes SS.: seconds Meas. Index|The measurement index is a unique identifier for a programmed measurement job. It is valid, as long as the measurement is active. It is also used in all messages that are written to the “System History” or “Error List”. Therefore, you can identify all messages referring to a specific job. Sample Freq.|Indicates the sampling frequency (in Hz) for a running measurement job. Buffer size|It shows you the buffer size used for this measurement (in number of samples). This buffer size is used for data processing. Every time, the ADU-07e has recorded one full buffer, it will be processed and written to the CF-card. Num. Buffers|This value shows you the number of buffers that have been recorded by this measurement till now. Used Channels|Shows you the number of the channels that are used by this measurement job. As long, as they are blocked by the current measurement job, they cannot be used by a new job. Remaining Job Time|This entry shows the remaining time of the job (time till stop-time of job is reached). It uses the same format as the “Time to Next Job” entry. Path|Indicates the destination path on the ADU-07es Linux system, the data is stored to. Act. Fill Level|{Displays you the number of samples that have already been recorded, but that are still stored in the backplane’s SDRAM buffer. Buffer Usage|This progress bar shows you the usage of the SDRAM buffer on the backplane. If you execute HF measurements, the CPU board may not be able to collect the data in real time from the backplane’s SDRAM buffer memory. The backplane buffer will run full in this case. If it reaches 100% usage, the measurement will be aborted automatically due to a buffer overflow. The buffer will be emptied and written to the Flash Disk Start/Stop Usage|This progress bar shows you the usage of the backplanes SDRAM buffer for measurements that are configured to work in “Start/Stop” mode. For these measurements, the fill level of the SDRAM buffer is lower than its maximum fill level. By this means measurements in “Start/Stop” mode will be stopped before they fill the SDRAM buffer to 100%. Therefore, other measurements running in parallel are protected from being stopped due to a buffer overflow. The next section is the “System Status” section. It contains information about the general system status, like the battery status, the current system temperature and other values. The single elements have the following meaning: .. csv-table:: Parameters section “System Status” on page “System Specific – Status – System Status” :delim: | Element name|Description Battery Status|It shows you the current status of the battery. The values are the same, as displayed in the header (see chapter 8.1) Battery Voltage|This value shows you the current voltage on the battery inputs. If two batteries are connected it displays the value of the battery with the higher voltage. Battery Current 1|This value shows you the current that is drained by the ADU-07e from battery input 1 (BAT1). This value shall help you to decide, which battery should be replaced first. Here always the battery, that provides the smaller current for the ADU-07e should be replaced first, as this probably is the one, that is most empty. Battery Current 2|This value shows you the current that is drained by the ADU-07e from battery input 2 (BAT2). Temperature|Displays the internal temperature of the system. The temperature refers to the temperature inside the ADU-07e housing. It is usually about 18°C higher than the outside temperature. The reason is that the location of the sensor is close to the CPU board (Hot Spot) Bios Date|The “Bios Date” and “Bios Time” shows you the current system time not considering the offset values that are configured on the “General – Options” page of the Web-interface. (GMT/UTC time) Bios Time|See “Bios Date” Next to the “System Status” section you will find the “GPS Status” section. It provides information about the GPS signal and the synchronization state of the ADU-07e in reference to the GPS signal. The single entries have the following meaning: .. csv-table:: Parameters section “GPS Status” on page “System Specific – Status – System Status” :delim: | Element name|Description Date|This value shows the Date as it is received by the GPS board. No calculations to local time are done. Time|See “Date” Latitude|This value shows you the Latitude of the current position of the ADU-07e system. Longitude|This value shows you the Longitude of the current position of the ADU-07e system. Elevation|This value shows you the elevation from sea level of the current position of the ADU-07e system. Satellites|This value shows you the number of satellites in good view which are used by the GPS receiver inside the ADU-07e. Sync State|This shows you the current status of the GPS connection. The values are the same, as displayed in the header (see chapter 8.1) *Information:* If you want to perform synchronous measurements with multiple ADU-07e systems, the ADU-07e has to reach the “G4 fix – fully synced” status at least once after power-on. If you want to perform synchronous high-frequency measurements it is required to have a continuous G4 fix mode on all ADUs involved. Note the G4 fix state was introduced with software 3.0 and higher. Older software will show G3 fix only. The third section of the “System Status” Page is the “Disk Space” section. It contains entries for the following values: .. csv-table:: Parameters section “Disk Space” on page “System Specific – Status – System Status” :delim: | **Element name**|**Description** Internal CF|This entry shows the current fill level of the internal CF cards data partition. The displayed progress bar shows currently used disk space with a percentage value at the end. Underneath the progress bar the free disk space is shown in MByte. MySQL Database|This entry shows the current fill level of the database partition on the internal CF disk. It is important to do a “Database Maintenance” (dump to disk and empty database) if this disk is more than 80% full. If 100% full the ADU-07e systems operation cannot be guaranteed anymore. USB-1 / USB-2|These two entries show the current fill level of any attached USB mass storage devices that are mounted to one of the two USB data directories. The display format is the same as for the other two disk space entries, with the difference, that the status shows the message “No Device Mounted”, if currently no device is mounted / attached to the ADU-07e system for the specific data directory. The last section of this page is the “Error List”. This section contains a list of messages that have been created by the ADU-07e system during operation. The latest messages are displayed on top of the list, descending with their age. In the list always one line refers to one specific message for which the following information is shown: .. csv-table:: parameters section “GPS Status” on page “System Specific – Status – System Status” :delim: | **Element name**|**Description** Timestamp|Shows you the time and date, the message was created. Component|Indicates you the component in the ADU-07e system, this message refers to. Message|This entry finally contains the message text. In difference to the “System History” where all messages, which the ADU-07e creates during its operation are shown, the “Error List” on the “System Status” page only contains those messages, that refer to some unexpected behavior of the ADU-07e system. This may be, for example, an invalid combination of filters that you configured. In such case the ADU-07e system will use fall back filter settings and add according messages to the “Error List”. The components that create the messages can be the following: .. csv-table:: Components for messages, created by the ADU-07e system :delim: | Component|Comp. Nr.|Description MCP|1|All messages that belong to the “MCP” component refer to incidents, that happen during the operation of the ADU-07e system. This can be messages that are created, if a new measurement is started or timed out. MCP_USB|2|The messages that belong to the “MCP_USB” component refer to the USB communication between CPU board and the hardware of the ADU-07e system directly. MICRO|3|The messages of the component “MICRO” refer to incidents that take place inside the microcontroller of the measurement hardware. HW_MSG|4|The messages of the component “HW_MSG” refer to incidents that are caused by general system status parameters such as battery voltage and current. For example a “Battery voltage switched to low” is created, if the battery power switches from GOOD or FAIR to LOW. GPS_MSG|5|These messages refer to incidents that are caused by GPS parameters. For example a message “GPS lost sync” is created, if the GPS status switches from “G4 fix” to “no fix”. BACK_MAIN|6|These messages refer to the status of the main backplane board. SUB_BACK|7|These messages refer to the status of the sub backplane board. CAL|8|These messages refer to the status of the calibration board. ADB|9|These messages refer to the status of the ADB boards. GPS_STATUS|10|The “GPS_STATUS” messages are written to the “System History” cyclically. They include a complete set of GPS status parameters, such as position data, sync state and number of satellites. HW_STATUS|11|The “HW_STATUS” messages are written cyclically to the “System History”, too. Same as the “GPS_STATUS” messages they contain a complete set of the system status parameters, like battery state, battery voltage, free disk space and so on. GLOBAL|12|The “GLOBAL” messages refer to incidents that cannot be allocated to one of the other components. USB_AUTO MOUNTER|13|The “USB_AUTO-MOUNTER” messages refer to the “USB Auto-mounter” that automatically detects and scans attached USB mass storage devices. CON|14|These messages refer to the status of the connector board. SENSOR|15|These messages refer to the status of the new “intelligent sensors”. USER|16|These messages are “user specific” messages. The messages are created by the user with a special “PHP Info” job. It writes new messages to the Web-interface and to the front panel display. You may for example add these messages to your job-lists in order to display messages on the “front panel display”. *Information:* Not all messages of the table above occur in the “Error List” on the “System Status” page. Nevertheless, the components are also displayed in the “System History”. Page “System Specific – Status – Selftest” '''''''''''''''''''''''''''''''''''''''''' After you clicked on the *Selftest* entry in the menu, you will see the following page: IMAGE Page “System Specific – Status – Selftest” of the ADU-07e Web-interface This page is used to display the results of the self-test procedure executed by the ADU-07e system during start-up of the system. As you can see in Figure 8-49, the page is split into three large sections. The first one is the “System Boards” section. It is used to display the self- test results of all the components except those for the ADB boards. The field “Init Error” will show an error code for the component in case an error has occurred during start-up of the ADU-07e. If the components have been initialized correctly, the value of the “Init Error” field is set to 0. The second section on this page is the “ADB Boards” section. It contains the detailed information for the self-test results of the individual ADB boards. In the chart line “Name” you can see the ADB board type that is installed in channel slot. The most important line in the chart is the entry “ADB error”. If this line shows the value 0, the self-test for the corresponding channel has been executed without any errors. If the ADB board, that is installed for this channel failed one of the self-test steps, the corresponding error code will be presented here. All the other lines show results of the further steps of the self-test procedure. Not all of them are interesting for normal operation of the ADU-07e as long as no ADB errors have occurred. Nevertheless, there are quite a few values which may be of some importance for the user even in normal operation of the system such as: .. csv-table:: Important values of the self-test :delim: | **Name**|**Description** DC Offset|This value shows you the current DC offset in Volt that was measured on the sensor inputs during the self-test procedure. If you already had your sensors connected to the ADU-07e system during the self-test, this value should be corrected by using the DC offset correction. Max Amplitude|This value shows the maximum noise amplitude on the sensor input. LF / HF LSB|This value shows the value of the LSB (Least Significant Bit) for this channel in Millivolt. It is computed by the ADU-07e system during the self-test procedure. Resistivity|This value shows the resistivity value measured on the sensor inputs in Ohm. This value is important for the electrical field sensors to check the connectivity of the sensors to the ground. A complete list of all self-test values and their meaning for the ADU-07e system can be found in chapter 23.1. *Information:* Please note, that not all error codes occurring in the line “ADB errors” are critical errors that make operation with the ADU-07e system impossible. Most of the error codes refer to results of the self-test that should be noticed by you, but do not forbid to run measurements. An example for this is the error code ADB-13 “ADU07-ADB-LF: DC level too high for gain”. This message only indicates that you should take care of the sensor’s DC offset and that the input signal could exceed the dynamic range of the ADC in case you activate a gain. Please refer to chapter 19 where a list of all messages is presented. The third section shows the currently active values for the “AutoGain AutoOffset” functionality: IMAGE “AutoGain AutoOffset” values on “System Specific – Status – Selftest” page As it can be seen in the figure above, the table of “AutoGain AutoOffset” values consists of a heading and the tabular display of all the values for the single ADB boards. The heading shows the “Date/Time” and “GPS Position” that have been valid at the point of time when the “AutoGain AutoOffset” values have been determined by the ADU-07e system. This information is important, as the values strongly depend on the current measurement site and may not be the best fitting values for the next site anymore. The values for the single ADB boards are shown in the following way: .. csv-table:: “AutoGain AutoOffset” values :delim: | Table Entry Name|Description Name|This table entry shows the name (type) of the ADB boards, the “AutoGain AutoOffset” values have been detected for (ADU07-ADB-LF, ADU07-ADB-MF or ADU07-ADB-HF). Mode|This entry shows the ADB board mode the values have been detected for. This entry is only necessary for the ADU07-ADB-MF board because this board may run in “LF” and “HF” modes, using different input circuitry and therefore different gain stages, … Filter Setting|This entry shows the filter that was used to determine the “AutoGain AutoOffset” values. This entry is necessary, as the values for the gain stages may differ in case a filter is active, or not. |E.g. if you have high 50/60Hz noise and 4Hz low-pass filter is active, the gain for the “Gain Stage 2” may have a much higher value as if no filter would be active. The 50/60Hz noise is almost completely removed from the input signal by the 4Hz low pass filter. The same applies to the use of the high-pass filters on the MF and HF boards. Any DC offset of the input signal will be removed then. Gain Stage 1|This is the recommended setting for “Gain Stage 1” for this channel in the defined node, when using the defined filter. GainStage2|This is the recommended setting for “Gain Stage 2” for this channel in the defined node, when using the defined filter. Offset Correction|This is the recommended setting for “DC Offset Correction” for this channel in the defined node, when using the defined filter. RF Filter|This is the recommended setting for the RF (radio filter) to be used for this channel. Page “System Specific – Status – Hardware Config” ''''''''''''''''''''''''''''''''''''''''''''''''' After you have clicked on the *Hardware config* entry in the menu, you will see the following page: IMAGE Page “System Specific – Status – Hardware Config” of the ADU-07e Web-interface All components that are installed inside the ADU-07e system are listed on this page. These components are detected automatically by the ADU-07e during its start-up procedure. For each hardware component you can find an extra section providing the related information. There are some entries that are available for all the hardware components, independent of their type: .. csv-table:: Important values of the hardware configuration :delim: | **Name**|**Description** GMS|The “GMS” field along with the “Type” field identifies this hardware component. The ADU-07e can tag the hardware component for example as “Main Backplane Board” … Type|The “Type” field located next to the “GMS” field is part of the unique identifier of the hardware component. Revision Main|The “Revision Main” along with the “Revision Sub” field defines the revision of the hardware component. This additional information is used to together with the “GMS” and “Type” field because different versions of a hardware component also may have a different functionality. Revision Sub|See “Revision Main” Serial Number|This is the serial number of the module. It is read by the ADU-07e system for each component during start-up of the system. Vendor|This field shows the vendor of the module. In most cases, this will be Metronix, but for some components like the CPU board, the vendor is different. These components are 3rd party products bought from Metronix and integrated into the ADU-07e system. MTX Part Number|This is the Metronix part number for the component. If you want to purchase any replacement part from Metronix, this number is required. For some of the components you will find additional information listed. It depends on the type of the module and is mainly used for debugging purposes in case problems with the ADU-07e should occur. In case you have the newer “ADU-07e” hardware it automatically detects the type of the connected sensors. This sensor information being detected during system power-up is shown here, too. IMAGE automatically detected Sensors IMAGE automatically detected Sensors As it can be seen in the pictures above, for each sensor input (connector) of the ADU-07e the detected sensor is shown along with the name of the connector on which it is currently connected to (e.g. MFS06e on connector “Hy” in pictures above.). If you do not have any of the new “intelligent sensors” like the MFS06e, MFS07e or EFD07e installed or you do not have the ADU-07e hardware the sensor information will always be set to “UNKN_E” like shown in the picture above. This is not an error and just means, that no device could be detected. You may always overwrite the automatically detected sensor configuration within the “Sensor Pos” page. IMAGE Same as on the “Sensor Pos.” page you can restart the sensor detection by clicking on the button “Detect Sensors”. Then, a few seconds later you have to press the “Reload Sensor Config” button for an update. Page “System Specific – Status – System History” '''''''''''''''''''''''''''''''''''''''''''''''' After you have clicked on the *System History* entry in the menu, you will see this page: IMAGE Page “System Specific – Status – System History” of the ADU-07e Web-interface You will find here a list of all the messages which were created by the ADU-07e during its operation. Each line in the table represents one single message. For all messages a timestamp, the priority, the component inside the ADU-07e system which caused the message and the message text itself are shown. Generally, there are two different message types. The first ones are messages with priority “info”. They just inform the user about events in the ADU-07e system. In Figure 8-53 the message *“Selftest result: OK”* is a good example for this type of message. The second type are messages with priority “exception”. They are used to inform you about erroneous or unexpected behavior of the ADU-07e system. An example for this kind of message is the notice *“invalid ADB configuration (used filters for ch4: ADU07_LF_RF_1)”*. This message for example tells that you tried to start a measurement with an invalid filter configuration for the ADB channel. It additionally shows you the fall back settings used for the measurement instead. All messages with priority “exception” are additionally displayed on the “Error list” on the “System Status” page. As the list of messages can get quite lengthy during long times of operation, only 20 messages are shown on the page all at once. You may browse through all the messages using the buttons *IMAGE*. The newest messages are always shown on top of the list. As in some cases the “System History” can be filled with a lot of “GPS” and “Hardware” status messages, the display of these messages can be suppressed by using the *Hide GPS Status* and *Hide HW Status* buttons. Clicking on the *Clear History List* button will delete all messages and clear the corresponding table in the database. *Information:* Please note that in case the system is operating for a really long time, the number of messages can become very high. As all the messages are stored in the database which resides on the CF-card of the ADU-07e it will cost disk space that could also be used to store measurement data. Therefore, it is recommended to clear the “System History” in cyclic intervals or in advance of a survey to be carried out or dump and clear the complete database. Section “System Specific - Management” '''''''''''''''''''''''''''''''''''''' The menu is structured as shown in the following picture: IMAGE Menu entries for section “Management” of the ADU-07e Webinterface As you can see in Figure 8-54 the section for “Management” of the ADU-07e system contains menu entries, that refer to 4 more pages of the Web-interface. These will be explained in detail in the following chapters. Page “System Specific – Management – DB Maintenance” '''''''''''''''''''''''''''''''''''''''''''''''''''' After having clicked on the *DB Maintenance* entry you will see this page: IMAGE Page “System Specific – Management – DB Maintenance” of the ADU-07e Web-interface You will find several operations to maintain the “MySQL” database running on the ADU-07e system. Inside the database all the jobs, messages and configurations are stored. Therefore, it is a good habit to “dump” the database to a file and store it along with the measurement data after a field survey has been finished. By this means a debugging can be done easier in case something seems to be strange with the recorded data. In order to dump the database to a file click on the button “Dump Database”. As a result the database is dumped into the following file on the ADU-07e internal CF-card: .. code:: /mtdata/log/DBDump/mcpdb07.sql It can be accessed via the “Samba” server on the “log” folder as follows: IMAGE Access to “database dump” file via “Samba” server The file can be copied from there and then be sent to Metronix for further evaluation. By use of the button “Empty Database” the MySQL database can be cleared. This will delete all jobs and messages from the database. It is advised to do this every time a new field survey is started. Hence, you have a “clean” system before starting the new measurement campaign. **Information:** If the database is cleaned, all jobs that have been programmed so far are deleted as well. Pre-programmed “job-lists” are not deleted. **Information:** The dumped database file is very helpful for Metronix, if any problems with an ADU-07e system should occur. Therefore, please dump the database and send it to Metronix by E-Mail in case support is required. You should zip the database before sending it. This will reduce the amount of data to be transferred significantly. Page “Select / Create Job-list” ''''''''''''''''''''''''''''''' This page is used to select, create or delete a job-list. It has the following structure: IMAGE Page “System Specific – Management – Select/Create Job-list” of the ADU-07e Web-interface As it can be seen inside the figure above, this page is quite simple. It only contains one “combo box” and several buttons. Inside the “combo box” all yet existing job-lists are shown. The information for this “combo box” is extracted from the “job-lists” table inside the MySQL database. The “combo box” is an “editable” element. The user may enter the name of a new job-list as a string inside this “combo box”. The name should not include any blancs. Use _ instead. * By clicking on the button “Select Joblist”, the job-list whose name is currently chosen inside the combo box will be “selected”. This means, that all further operations on the other pages (e.g. “Edit Job-list”) are done on this selected job-list. * By clicking the button “Create Joblist” a job-list, using the string entered in the “combo box” is created inside the MySQL database. This job-list is initially empty and will be selected for further editing automatically. * By clicking the button “Delete Job-list” the currently activated job-list is deleted. This includes the deletion of all the individual XML jobs stored in the job-list. Additionally, the “selected” job-list will be set to the default value “no job-list selected”. Page “Edit Job-list” '''''''''''''''''''' This page is intended to edit the parameters and contents of a job-list. It has the following structure: IMAGE Page “System Specific – Management – Edit Job-list” of the** ADU-07e Web-interface As it can be seen in the figure above, this page contains much more input elements than the “Select / Create Job-list” page. Mainly, the page is separated into three different sections: * Time settings * USB Auto-mounter settings * Job-list contents The first section (“Time Settings”) is used to define how the job-list shall be started. It contains a “combo box” called “Mode” and several input boxes to define a new start-time for the job-list. By use of the “Mode” combo box the user defines how the start- / stop-times of the single XML jobs are handled when the job-list is started. It contains three possible values that have the following meaning: * **“relative”:** If this option is selected and the “Start job-list” button is clicked, the job-list will be started at the next possible moment. This means, that all the jobs are shifted to the next possible start-time, while the internal structure of the job-list is kept. * **“absolute”:** If this option is selected and the “Start job-list” button is clicked, the job-list will be started using the original start-times of the XML jobs files of the job-list. * **“adjusted”:** If this option is selected and the “Start job-list” button is clicked, the job-list will be performed with the first job of the list starting at a time which has been entered by the user in the “New Start-time” input fields. All further jobs will be started in relation to the first jobs start time. * **“grid”:** If this option is selected and the “Start job-list” button is clicked, the job-list will be started at the next valid “Grid” start time. If, for example the “Start Time” on the “Edit Joblist” page is set to “0000-00-00 00:15:00” the joblist will be started at the next full 15 minutes of the current hour. Example: Time Now: 09:08:57 Grid Start Time: 0000-00-00 00:15:00 Resulting Job-list Start Time: today, 09:15:00 This option is originally meant to be used for surveys, where either a transmitter or a remote station is cyclically executing the same schedule and the ADU-07e shall record the joblist synchronized to the transmitter / remote stations schedule. Inside this section there exist two more buttons. The “Save” button as on all other pages, too, is used to store the current settings from the page. By the use of the “Load Defaults” button, all settings for the selected job-list are set back to the default settings. This also complies with the input elements of the next section “USB Auto-mounter settings”. The “USB Auto-mounter” section mainly contains input elements for the job-list settings needed, if the job-list is exported as a “pre-configured USB directory structure”. The settings are not of interest, if the job-lists are only used inside the Web-interface. If the job-lists are exported for use on a USB pen-drive, the values of this section are used inside the “ADU07Conf” XML file. The single positions have the following meaning: * **“Mount directory”:** With this input element the mount directory for the USB device on which the USB device shall be integrated into the file system of the ADU-07e, can be entered. This is mainly useful if you select the option “USB_TO_USB” for the “Storage Mode” parameter. In this case all recorded data is stored on the USB device itself. The job-list must have been exported to the same USB device beforehand. In most cases this parameter should be left empty if the data shall not be stored on USB (Storage Mode is set to “USB_TO_DEFAULT”). Or, it should be set to “/mtdata/usb/data” if the data should be stored on the USB device (Storage Mode is set to “USB_TO_USB”). Note, that this directory can also be accessed via the “Samba” server now. Its share name is “usb” (e.g. for Windows users: \\\\\\usb). * **“Storage Mode”:** This parameter defines the method how the data of several measurement jobs of this job-list shall be stored on disk. 1. **USB_TO_DEFAULT:** In this case all data will be stored to the internal CF-card. 2. **USB_TO_USB:** In this case all data will be stored on the USB device, if plugged in. Please note that the “Mount Directory” parameter MUST be set to a valid value in this case. 3. **USB_TO_JOB:** In this case the data of the measurements will be stored on the data directory that is defined by the “” nodes inside the XML job file. Unless manually changed with a text editor, this always will be the internal CF-card. * **“Adapt Configuration”:** If set true, all the measurement parameters of the XML job files, such as site information, and sensor configuration will be taken out of the settings of the last job that started on this ADU-07e system. When using this option, at least one job must have been started on the system previously. * **“Adapt Channel Configuration”:** If set true, the settings for “Gain Stage 1”, “Gain Stage 2” and “DC Offset Correction” of all jobs, that are part of the job-list, are overwritten with the “AutoGain AutoOffset” settings, that have been detected by the ADU-07e system automatically during execution of the “AutoGain AutoOffset” selftest jobs. . The current “AutoGain AutoOffset” settings can be observed on the bottom of the “Selftest Results” page. The sense of this functionality is to make field use of the ADU-07e system easy. By executing the “AutoGain AutoOffset” selftest jobs it shall be avoided to have to manually execute several test measurements to find the best fitting values for the current measurement site. This task shall be handled by the ADU-07e system. Afterwards the complete job-list, to be executed at the site shall easily be reconfigured with the “AutoGain AutoOffset” values in order to get best possible data quality. * **“Adapt Sensor Spacing”** If this is set true the values for the E-field spacing will be taken as defined in the ADU-07e “Sensor pos.” page. If set to false the spacing will be taken as stored in the job-list. * **“Adapt Sensor Type”** Here you can select 3 options. “NONE” will take the sensor type as written in the job list. “ALL” will take the value as defined in ADU´s “Sensor Pos.” page. “E-TYPE” will only take the recognized values of the intelligent sensors such as MFS-06e or MFS-07e and reads all other values as specified in the joblist. * **“Clean job-table”:** If this parameter is set to “true”, the old job-table will be deleted before starting the jobs of the job-list. All old jobs that possibly were left inside the job-table will be deleted. The third and last section consists of a chart that shows all the XML jobs of the job-lists. For each job of the job-list one line is created inside the table. Inside each line the following elements are shown: * **“Start-time”:** This cell contains the “start-time” of the job. * **“Stop-time”:** This cell contains the “stop-time” of the job. * **“name”:** This cell contains the name of the job. If exported to USB, the name of the job is used as file name for the XML job file. * **Button “Edit”:** If clicked, the XML job file will be read from the MySQL database and the current settings inside the “SESSION” variable will be replaced by the settings of the XML job file accordingly This mainly works as a counterpart to the “Start Job” function. If loaded for editing, the jobs configuration can be changed and finally the job can be re-written inside the job-list or it can be simply started via the “Start Job” page. By this means the user may reopen a job from the job-list and restart it and it is not required to completely reconfigure the job again when reconnecting to the ADU-07e. * **Button “Delete”:** If clicked, the job will be deleted from the job-list by removing the entry from the MySQL database. Page “Import / Export Job-list” ''''''''''''''''''''''''''''''' This page is used to export a job-list as “pre-configured” USB directory structure or to import an existing “pre-configured” directory structure as job-list into the MySQL database. It has the following structure: IMAGE Page “System Specific – Management – Import / Export Job-list” of the ADU-07e Web-interface There are two separated sections for the “import” and “export” of a job-list to /from “pre-configured” USB directory structures. For the “import” functionality, the user has to enter the name of the job-list that shall be imported into the name input field. When clicking on the “Import Job-list” button, the Web-interface will examine the existing USB directory structure on the following path on the ADU-07e system: .. code:: /mtdata/usb/Job-listImport This needs to be a defined path, as the Web-interface requires reading authorization on that directory. Nevertheless, the user may override this default value by entering a different path to the “Source Path” input field. If a valid “USB directory structure”, as defined in [2] was found inside the source directory, the Web-interface will read the “ADU07Conf.xml” file and import all XML job files of the job-list defined inside this file. These jobs are subsequently stored inside the newly created job-list of the MySQL database. The way to import a job-list from USB therefore is: * Copy the contents of the pre-configured USB device to “/mtdata/USB/JoblistImport” * Enter a name for the imported job-list on the “Import/Export Job-list” page * Click on the “Import Job-list” button on the “Import/Export Job-list” page In order to export a job-list from the MySQL database as a “pre-configured” USB directory structure, almost the same actions need to be done. Inside the combo box “name” the user has to select the name of the job-list to be exported. Afterwards, he has to click on the “Export Job-list” button. As a result the contents of the job-list will be exported to this directory: .. code:: /mtdata/USB/Job-listExport E.g. for export of the job-list “MWI_Job-list_LF_1”, the following has to be done: IMAGE Sample Job-list table to be exported .. code:: /mtdata/USB1 USB_2_USB absolute 0 TRUE TRUE ./MWI_Job-list_LF_1/JobLF1.xml ./MWI_Job-list_LF_1/JobLF2.xml Figure 8-61: exported “ADU07Conf” XML file IMAGE exported “Job-list” A job-list can easily be configured by using the Web-interface and be exported on a USB device by simple “copy and paste” procedure. The exported “Job-list” can then be copied from the ADU-07e system using the “Samba” server. The data can be found on the following share: IMAGE Sample Job-list table to be exported From there, the complete job-list can be copied on a new USB device. This USB device can be used then as “pre-configured” USB device as described in chapter 13. Page “System Specific – Management – View Job Table” '''''''''''''''''''''''''''''''''''''''''''''''''''' After a click on the *View Jobtable* entry in the menu, you will see the following page: IMAGE Page “System Specific – Status – View Job Table” of the ADU-07e Web-interface On this page you can see all entries of the “job” table in the database. This may be all old jobs, that have already been executed as well as new jobs that are currently running, or have not started yet. Each line of the table contains the detailed information for a single job. For each job its type is shown in the column “Type”. As you can see in Figure 8-64 it must not only be “Measurements”, but can also be “Shutdown System” or “Stop Measurement” jobs. For an overview about the different job types, please refer to chapter 20. Additionally, the start- and stop-times are displayed in the table. In the column “Started” an “x” informs you, that the measurement is running or has already been executed completely. A measurement is not yet started in case no “x” is set in this column. Further on, the selected sampling frequency and the active channels are shown for each measurement job entry. A click on the *Delete* button will delete a single measurement from the “job” table. By pressing the button *Clear Job Table* the complete contents of the “job” table inside the database will be deleted. In this case all jobs that haven’t been started yet are not going to start at all. **Information:** The deletion of a job from the “job” table does not stop a measurement currently running. It will just delete the corresponding entry of the “job” table. In order to stop a measurement, the “Stop Job” page has to be used. Similar as messages in the “System History”, the number of entries in this table can become quite big in case the system is used for a long time. Since all jobs require space in the database the table should be cleared routinely. Hardware Description ------------------------------------------- The ADU-07e functionality is based on the following components: * Backplane with power supply and several slots for plug-in modules * Controller module * CPU-board * LF-A/D converter modules (usually 5) * HF-A/D converter modules (usually 5) * MF-A/D converter modules * Calibration module * GPS controlled clock module * Connector board All these components are installed inside a water and shock resistant box. They are mounted on an aluminum front-panel. The bus system which is used to communicate between the CPU-board and the backplane is USB 2.0 industrial standard. This guarantees a high flexibility and eases future expansion. If a higher performance is required the ADU-07e can be controlled by an external computer instead of the internal CPU-board. The following block-diagram (Figure 9-1) shows the functionality of the ADU-07e. IMAGE Block diagram of ADU-07e The core unit of the ADU-07e is the backplane which controls the A/D boards, the USB 2.0 interface, the communication with the GPS based clock module as well as the intermediate data storage and the calibration module. It also provides the power-supply of the ADU-07e. Network -------- The network functionality is located on the CPU-Board. The speed of the network is 100 Mbit/sec max. The ADU-07e which is equipped with the GEODE CPU-board can also be equipped with an internal W-LAN adapter. The newer Cortex A8 CPU has an integrated W-LAN CPU Board --------- The CPU board is mounted on the backplane. A Compact Flash Card or µSD-card (depending on type of CPU board) is inserted on its left side. The CPU board is connected to the backplane by a 2 wire cable (power supply) and a ribbon cables (USB ports). Metronix delivers flash cards with different sizes (up to 32GB). They are already configured with the necessary system software.The CPU board is operated by a Linux operating system. IMAGE CPU Board with Geode processor and USB 2.0 used in ADU-07e IMAGE New CPU Board with ARM Cortex A8 processor **Information:** The Geode CPU board contains a Lithium backup battery. Although Metronix uses high quality batteries in its electronic circuits the batteries may get damaged, if not changed for a long time. Therefore Metronix advises the customers to check and possibly exchange the batteries once every 2 years for correct voltage and damage. The new ARM Cortex A8 board does not have a backup battery. Metronix will not take over any warranty for damages to the electronics that are caused by damaged back-up batteries. LF-ADB-board ------------ The LF-ADB-board amplifies, filters and digitizes the weak signals coming from the sensors. The first stage is the input protection and the radio filter. The LF-ADB-board is equipped with a fully symmetrical differential input. The input resistance is more than 100 MOhms for the electric channel and 20kOhm for the magnetic channel. A switchable amplifier (Gain 1, 2, 4, 8, 16, 32 or 64)) is the next stage. It follows a switchable offset compensation circuitry which allows elimination of a DC offset on the channel (i.g. caused by polarized electrodes). A second stage with a switchable gain follows this stage. The ADB-board is equipped with a highly stable 24 Bit Delta Sigma A/D converter. The sample rate is selectable by software. It can be 128Hz, 256Hz, 512Hz, 1024Hz, 2048Hz and 4096Hz. The LF-ADC has an excellent stability and can therefore be used for frequencies down to DC. The very low input noise of only :math:`\\(10\frac{nV}{\sqrt{Hz}})` (with gain 32) between 0.1Hz and 1 kHz makes the LF-ADB-Board an ideal tool to digitize the very weak signals in the MT dead band. IMAGE ADU-07-ADB LF-Analog/Digital Converter board IMAGE Block diagram of LF-ADB-board Configuration of the ADB-Board ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Each LF-ADB board has a unique serial number which is stored in an EEPROM. The system will automatically detect this. No further action is required. Technical data overview ^^^^^^^^^^^^^^^^^^^^^^^ The ADU-07-LF ADB has the following functionality, that can be used and configured via the Web-interface: .. csv-table:: configuration settings for ADU-07-LF ADB board :delim: | Component|Option in Web-interface|Values|Description Sampling Frequencies|Sampling Frequencies|128 Hz, 256 Hz, 512 Hz, 1024 Hz, 2048 Hz, 4096 Hz|Valid sampling frequencies for the ADU-07-LF ADB board. Lower sampling frequencies can be reached by digital filtering. Filters|ADU07_LF_RF_1 ADU07_LF_RF_2 ADU07_LF_RF_3 ADU07_LF_RF_4 ADU07_LF_LP_4Hz|22 pF 122 pF 6822 pF 6922 pF 4Hz Low Pass|{The radio filters are dependent on the sensor resistance. They do not have any effect, if no sensor is connected. The 4Hz low pass filter will eliminate the HF part of the input signal. Generally one of the radio filters must be active. By default, the ADU07_LF_RF_1 filter is used. All radio filters can be combined with the ADU07_LF_LP_4HZ filter. Gain Stage 1|Gain Stage 1|1,2,4,8,16,32,64|For the first gain stage these settings are possible. Gain Stage 2|Gain Stage 2|1,2,4,8,16,32,64|For the second gain stage these settings are possible. Offset Correction|Offset Correction|-2,5 Volt to +2,5 Volt|By the use of the offset compensation DAC, the probe DC offset can be compensated. It covers the complete dynamic range of the ADC of the ADU-07-LF ADB board. Radio-filters ^^^^^^^^^^^^^ This paragraph describes the function of the radio filters. The radio filters are required to avoid a biasing of the input stage of the LF-Board by nearby radio transmitters such as mobile phones, transmitters for public broadcast and other sources. The radio filter is required especially for the electric field lines. As the resistance of the probes to the ground depends on various parameters such as wetness of the soil, material of the soil etc. we have provided different radio filters which can be switched according to the requirements. They can be switched on and off using the Web-interface (section Configuration). Generally, one can state that the lower the probe resistance the higher the number of the selected radio filter has to be (RF 4 for lowest resistance). One has to be aware that a radio filter which is not set up properly can influence the phase of the measurement signal. The graph below shows this issue: IMAGE As long as the probe resistance is lower than the value given in the curve, the phase shift at a given frequency will be less than 3 degrees. The HF-ADB Board ---------------- The HF-ADB-board amplifies, filters and digitizes the weak signals coming from the sensors. The first stage is the input protection and. The ADB-board is equipped with a fully symmetrical differential input. The input resistance is more than 10 MOhms for the electric channel and 20kOhm for the magnetic channel. A switchable amplifier (Gain 1 and 8) is the next stage. It follows a switchable high-pass filter with 1Hz cut-off frequency to eliminate a DC offset on the channel (i.g. caused by polarized electrodes). It follow a second amplifier with a switchable gain (x1, x8 or x64). The ADB-board is equipped with a highly stable 24 Bit Delta Sigma A/D converter. The sample rate is selectable by software. It can be 4,096; 8,192Hz; 16,384Hz; 32.768Hz; 65,536Hz; 131,072Hz; 262,144Hz or 524,288Hz. IMAGE ADU-07-ADB HF-Analog/Digital Converter board IMAGE Block diagram of HF-ADB-board Technical data overview ^^^^^^^^^^^^^^^^^^^^^^^ The ADU-07-HF ADB has the following functionality, that can be used and configured via the Web-interface: .. csv-table:: configuration settings for ADU-07-HF ADB board :delim: | Component|Option in Web-interface|Values|Description Sampling Frequencies|Sampling Frequencies|4096 Hz 8192 Hz,16384 Hz,32768 Hz,65536 Hz, 131072 Hz, 262144 Hz, 524288 Hz|These are the valid sampling frequencies for the ADU-07-HF ADB board. Filters|ADU07_HF_HP_1HZ|1 Hz high pass filter|The ADU-07-HF ADB board only provides one filter. The ADU07_HF_HP_1HZ filter will eliminate the DC part of the input signal. Gain Stage 1|Gain Stage 1|1,8|For the first gain stage these settings are possible. Gain Stage 2|Gain Stage 2|1,8,64|For the second gain stage these settings are possible. Offset Correction|Offset Correction|N/A|The ADU-07-HF ADB board does not provide the possibility of an offset correction. **Information:** The Geode board allows a max. sampling rate of 65kHz with 5 channels and continuous recording. The new Cortex A8 board can record up to 131kHz with 5 channels continuously. The MF-ADB-Board ---------------- This special A/D converter board for the ADU-07e combines the advantages of the LF and HF board on one single module with a wide input frequency range from DC to more than 16kHz. It provides 4 different sample rates of 128Hz, 4,096Hz, 16,384Hz and 65,536 Hz. Other sampling rates can be created by applying online digital filters. In order to achieve a low input noise we have provided 2 different analog amplification paths – one for low frequency recording based on a chopper stabilized amplifier and one for the high frequency range using low-noise and high speed amplifiers. Depending on the selected sampling rate the best fitting signal path will be selected automatically. The 24 Bit Delta Sigma A/D converter provides a high stability and low temperature drift. IMAGE ADU-07-ADB-MF Analog/Digital Converter Board IMAGE Block diagram of MF-ADB-Board Technical Data Overview ^^^^^^^^^^^^^^^^^^^^^^^ .. csv-table:: Configuration settings for ADU-07-MF ADB board :delim: | Component|Option in Web-interface|Values|Description Sampling Frequencies|Sampling Frequencies|128 Hz, 4096 Hz, 16384 Hz, 65536 Hz|Valid sampling frequencies for the ADU-07-MF ADB board. Lower sampling frequencies can be reached by digital filtering. Filters|ADU07_LF_RF ADU07_LF_LP_4HZ ADU07_HP_500HZ|4700 pF 4Hz Low Pass|The radio filter is dependent on the sensor resistance. It does not have any effect, if no sensor is connected. The 4Hz low pass filter will eliminate the HF part of the input signal. The radio filter is only active at 128 Hz sampling rate. The 500 Hz High-pass filter can eliminate power-line noise and DC offset in HF mode Gain Stage 1|Gain Stage 1|1,4,16,64|For the first gain stage these settings are possible. Gain Stage 2|Gain Stage 2|1,4,16,64|For the second gain stage these settings are possible. Offset Correction|Offset Correction|-2,5 Volt to +2,5 Volt|By the use of the offset compensation DAC, the probe DC offset can be compensated. It covers the complete dynamic range of the ADC of the ADU-07-MF ADB board. It is used for 128Hz sampling frequency (LF-path) GPS based Clock-Module ---------------------- The GPS-module is located inside the small aluminum housing on the backplane. It is a 12-channel GPS-receiver which delivers the latitude, longitude and elevation information (WGS 84). This information is available in the header of the recorded data and helps to determine the position of the station. The accuracy is approximately +/-10m. The GPS module generates a precise 1 second time stamp which is used to synchronize the oscillator with GPS accuracy. The jitter of the 1 second pulse is specified by the manufacturer to +/- 30ns RMS. The leading edge of this pulse is used to start the A/D converters synchronously. **Information:** There is a small Lithium battery mounted on the clock module which has to be replaced every 2 years. It powers the real time clock on the GPS module and keeps the almanac data available during a power down of the ADU-07 Metronix does not take any warranty for damages to the electronics that are caused by damaged back-up batteries. **Information** The status display offers an option to reset the GPS-module (warm start or cold start). This may be helpful if no satellites are detected after a far-away transportation. IMAGE Clock Module The Calibration Module ---------------------- The calibration module generates a bipolar symmetric square wave signal of high precision and stability over temperature. The default amplitude of +/-2.5V can be attenuated by a factor of 8 by software command. The clock frequency of the calibration module is generated synchronously to the A/D converter’s sampling rate. The frequency is selectable by software and can be chosen from 0.125 Hz to 16,384 Hz in steps by the power of 2. IMAGE Calibration Module System Calibration ------------------------------------------- Theoretical Calibration Function -------------------------------- The following chapter provides information about the theoretical transfer function of the ADU-07e. We have to distinguish between low-frequency channel (LF-channel) and high-frequency channel (HF-channel). The values given in the time series files are 32 bit integers which have to be multiplied with the Least Significant Bit (LSB) value. During the system self-test the individual values for the LSB are determined for each channel and are stored in the header of the time series file. The result after this multiplication is the current voltage value on the input of the A/D-converter given in mV. Transfer Function of HF-Channel ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The theoretical transfer function for the HF-channel is given below: :math:`\\F_{HF - Channel} = G_{1} \cdot G_{2} \cdot F_{1} \cdot F_{2} \cdot F_{3}` with :math:`\\G_{1} = 1` or :math:`\\G_{1} = 8` depending on gain setting of first stage :math:`\\G_{2} = 1` or :math:`\\G_{2} = 8` or :math:`\\G_{2} = 64` depending on gain setting of second stage :math:`\\F_{1} = \frac{1}{1 + P_{1}}` ; :math:`\\P_{1} = i \cdot \frac{f}{7.7MHz}` if :math:`\\G_{1} \neq 1` :math:`\\F_{1} = 1` if :math:`\\G_{1} = 1` :math:`\\F_{2} = \frac{1}{1 + P_{2}}` ; :math:`\\P_{2} = i \cdot \frac{f}{7.7MHz}` if :math:`\\G_{2} \neq 1` :math:`\\F_{2} = 1` if :math:`\\G_{2} = 1` :math:`\\F_{3} = \frac{P_{3}}{1 + P_{3}}` ; :math:`\\P_{3} = i\frac{f}{1Hz}` if high-pass is switched off. :math:`\\F_{3} = 1` if high-pass is switched off. Transfer Function of LF-channel ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The formula for the transfer function of an LF-channel is as follows: :math:`\\F_{LF - Channel} = G_{3} \cdot G_{4} \cdot F_{4} \cdot F_{5} \cdot F_{6}` with :math:`\\G_{3} = 1,2,4,8,16,32,64` depending on gain setting :math:`\\G_{4} = 1,2,4,8,16,32,64` depending on gain setting :math:`\\F_{4} = \frac{1}{1 + P_{3}}` ; :math:`\\P_{3} = i\frac{f}{4kHz}` :math:`\\F_{5} = \frac{1}{1 + 1.414 \cdot P_{4} + P_{4}^{2}}` ; :math:`\\P_{4} = i \cdot \frac{f}{4Hz}` if 4 Hz Low-pass is switched on and :math:`\\F_{5} = 1` if 4 Hz low-pass filter is switched off. :math:`\\F_{6} = \frac{1}{1 + P_{5}}` ; :math:`\\P_{5} = i \cdot \frac{f}{21.2kHz}` Transfer Function of MF-channel ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The formula for the transfer function of an LF-channel is as follows: :math:`\\F_{MF - Channel} = G_{5} \cdot G_{6} \cdot F_{7} \cdot F_{8} \cdot F_{9}` with :math:`\\G_{5} = 1,4,16,64` depending on gain setting :math:`\\G_{6} = 1,4,16,64` depending on gain setting :math:`\\F_{7} = \frac{1}{1 + P_{6}}` ; :math:`\\P_{6} = i\frac{f}{x \rightleftharpoons kHz}` .. line-block:: with x = 48.1 kHz for f\ :sub:`sample` = 65536Hz; x = 15.9 kHz for f\ :sub:`sample` = 16384Hz; x = 3.7 kHz for f\ :sub:`sample` = 4096Hz; x = 159 Hz for f\ :sub:`sample` = 128Hz; :math:`\\F_{8} = \frac{1}{1 + 1.414 \cdot P_{7} + P_{7}^{2}}` ; :math:`\\P_{7} = i \cdot \frac{f}{4Hz}` if 4 Hz Low-pass is switched on (only for 128Hz sampling frequency and :math:`\\F_{8} = 1` if 4 Hz low-pass filter is switched off. :math:`\\F_{9} = \frac{P_{8}}{1 + P_{8}}` ; :math:`\\P_{8} = i \cdot \frac{f}{500Hz}` if 500 Hz High-pass is switched on (only for sample frequencies >128Hz) and :math:`\\F_{9} = 1` if 500 Hz High-pass is switched off Measurement of Calibration Function ----------------------------------- The ADU-07e has a built-in calibration facility. When the system is switched on, an automatic gain calibration is performed. The procedure is as follows: The ADU-07e has a calibration generator with a precision voltage source. The first step is to feed in the calibration signal (frequency 32 Hz, square wave, +/-2.5V) directly into the input of the A/D converters (CAL-REF). The signal is stacked and analyzed. The next step is to feed-in the 32 Hz calibration signal into the input of the channel board (gain 1, CAL-INT)) . Now the result of step one and two is compared and the deviation is calculated and then used as a correction factor for the gain. The gain calibration procedure is repeated for other gain positions and for the MF- or HF-ADC. The different stages where the calibration can be fed into the instrument are: a) directly into the A/D converter (CAL-REF) b) directly into the input of the channel board (CAL-INT) c) into the E-field lines to measure the probe resistance (CAL-Sensor) d) into a magnetometer test coil (CAL-Sensor) In the position CAL-Sensor it is possible to feed in a signal directly into the electric field probes and into the calibration coil of a Metronix magnetometer. This allows to calculate the resistance of the electric field line and to analyze the response of the magnetometer. By this means it can be checked whether the coupling of the e-probes to the soil is good enough and whether the magnetometers work properly. A description of the sensor´s response to a fed-in test-signal is given in chapter 10. The following table explains the position of the switches SW-1, SW-2 and SW-3 shown in . .. csv-table:: Position of switches on the ADB-Board for different ADU calibration modes. :delim: | **Calibration Mode**|**SW-1**|**SW-2**|**SW-3** no calibration (measurement mode)|1-3|1-2|1-3 CAL-REF (reference calibration)|1-2|don´t care|1-2 CAL-INT (ADB-calibration)|1-2|1-3|1-3 CAL-Sensor (sensor calibration)|1-2|1-2|1-3 IMAGE Simplified block diagram of the ADU-07e calibration system Pin-out of External Connectors ------------------------------------------- E-Field Connectors ADU-07e -------------------------- .. csv-table:: Pin-out of E-Field sockets for buffer cables :delim: | **Socket 6-pole ODU MiniSnap G32KON-T06QP00-000 Pin**|**Signal** 1|+12V 2|-12V 3|Sensor GND 4|Sensor GND 5|n.c. 6|Input (+ or -) IMAGE Pinning of E-Field socket (front view) **Information** Please note that you require two E-field sockets to feed in the signal (One for the plus-pole and one for the minus-pole). **Information** For standard E-field cables it is only required to connect pin Nr. 6 H-Field Connectors of ADU-07e ----------------------------- .. csv-table:: Pin-out of sockets for the H-Field Sensors of ADU-07e :delim: | Socket 10-pole ODU MiniSnap G32KON-T10QJ00-000 Pin|Signal 1|+12V 2|-12V 3|H-Chop 4|Sensor GND 5|Cal Signal+ 6|Cal Signal- 7|Input + 8|Input - 9|I2C SDA 10|I2C SCL **Note:** Pin 7 is the positive input and Pin 8 the negative input of the differential amplifier input stage. If you do not have a symmetrical output on the sensor you should connect Pin 7 to Signal Out and Pin 8 to Signal GND of your sensor. IMAGE Pinning of H-Field socket (front view) Multi-Purpose Socket of ADU-07e ------------------------------- .. csv-table:: Pin-Out of multi-purpose input socket ADU-07e. :delim: | **Socket ODU MinSnap 30 pole G33K0N-T30QF00-0000**|**Signal** 1|+12V 2|-12V 3|Sensor GND 4|Sensor GND 5|Input A + 6|Input A - 7|Input B + 8|Input B - 9|Input C + 10|Input C - 11|Input D + 12|Input D - 13|Input E+ 14|Input E - 15|Cal Signal + 16|Cal Signal - 17|n.c. 18|HCHOP CH7 19|HCHOP CH8 20|HCHOP CH9 21|I2C_SDA5 22|I2C_SCL5 23|I2C_SDA6 24|I2C_SCL6 25|I2C_SDA7 26|I2C_SCL7 27|I2C_SDA8 28|I2C_SCL8 29|I2C_SDA9 30|I2C_SCL9 IMAGE Pin-out of ADU-07e Multi-Purpose Socket (front view) Battery Sockets --------------- .. csv-table:: Pin-out of battery sockets :delim: | Socket CA 02 COM-E10SL-4S-B Pin|Signal A|+12V Battery, AWG18 B|-12V Battery, AWG18 Magnetometer Cable ADU-07e to MFS-06e/07e ----------------------------------------- .. csv-table:: Pin-out of magnetometer cable ADU-07e to MFS-06e/07e (Metronix Art.Nr. 8094-0038-xx) xx= cable length :delim: | Target Plug ODU MiniSnap S22KON-T10MJG0-7000|Origin Plug ODU MiniSnap S22KON-T10MJG0-7000|Specification 1|1|+15V twisted with SDA 2|2|-15V twisted with SCL 3|3|HCHOP \twisted 4|4|SensorGND / 5|5|CAL+ \ twisted 6|6|CAL- / 7|7|SignalOut+ \twisted 8|8|SignalOut- / 9|9|I2C SDA twisted with +15V 10|10|I2C SCL twisted with -15V Available cable length 10m,15m, 20m, 30m or 60m. Standard is 10m. IMAGE Front view (on side with pins) Cable ADU-07e to SHFT-02 ------------------------ .. csv-table:: Pin-out of magnetometer cable ADU-07e to SHFT-02 high-frequency sensor :delim: | Target Coninvers 17 pole|Origin ODU MiniSnap Series K, 30 pole S23K0N-P30PFG0-0200|Signal|Colour|Cat. 1|1|+12V|brown|\ twist 2|2|-12V|black|/ ed |||| 9|9|HX Signal|yellow|\ twist 10|10|HX GND|green|/ ed |||| 11|11|HY Signal|red|\ twist 12|12|HYGND|orange|/ ed |||| 13|13|HZ Signal |blue|\ twist 14|14|HZ GND|violet|/ ed |||| Case|Case|Screen|| Cable length 10m; IMAGE IMAGE Front view (on side with pins) Cable ADU-07e to FGS-03 ----------------------- .. csv-table:: Pin-out of magnetometer cable ADU-07e to FGS-03 flux-gate (Metronix Art.Nr. 8094-0039-20) :delim: | Target ODU MiniSnap Series K, 8 pole S22K0N-T08MJG0-700S|Origin ODU MiniSnap Series K, 30 pole S23K0N-P30PFG0-0200|Signal|Colour|Cat.| 1|1|+12V|brown|\|twisted 2|2|-12V|black|/| ||||| 3|9|HX Signal|yellow|\|twisted 4|3 and10|HX GND|green|/| ||||| 5|11|HY Signal|red|\ |twisted 6|12|HYGND|orange|/| ||||| 7|13|HZ Signal |blue|\|twisted 8|14|HZ GND|violet|/| ||||| Case|Case|Screen||| Cable length is 20m; IMAGE IMAGE Front view (on side with pins) Front-panel Display ------------------------------------------- On the Front-panel of the ADU-07e system you see the “Front-panel Display”. This display is meant to be used to give status information to the user without the need to connect with an Laptop or PC. IMAGE ADU-07e “Front-panel Display” The “Front-panel Display” provides a menu structure with entries for different functionalities. By means of the “SCROLL” button you may scroll through the different entries of the menu structure. With the aid of the “PARAM.” button you may scroll through the sub-entries of the selected menu-items and, if possible, execute the according action. The following menu items can be found within the “Front-panel Displays” menu: .. csv-table:: Entries of the “Front-panel Display” menu :delim: | Menu Point|Submenu Point|Description System Status|Main|This menu point gives the current “System Status”. This consists of the last message, that was generated by the system. |DC Offset and Amplitude|The last system status message is followed by display entries for the DC offset and maximum amplitude on the single ADB channels |IP addresses|Finally, the last three entries show the current IP addresses for the ADUs network interfaces: Eth0: normal LAN Eth1: internal use for GSM/G3 modem Eth2: W-Lan interface || Job Info|Next Job|This entry shows the time to the start of the next job in the following format: -DDD-HH:MM:SS -DDD: days -HH.: hours -MM.: minutes -SS.: seconds |Remaining Job Time|This entry shows the remaining time of the currently running jobs in the same format as the “Next Job” entry || GPS data|Overview|GPS Time and Fix Status |Longitude|Longitude |Latitude|Latitude |Altitude|Altitude |Number of Satellites and Fix Status|Number of Satellites and Fix Status || Battery Status|Overview|Battery Voltage and battery current of input 1 and 2 |Voltage|Detailed battery voltage |Current Input 1|Detailed battery current for input 1 |Current Input 2|Detailed battery current for input 2 || Temperature|-|System temperature (inside the ADU near CPU) || Shutdown Control|Shutdown ?|Execute system shutdown |Sure ?| |Shutting Down !| || Sleep Control|Allow Sleep ?|Activate / Deactivate “Sleep Mode” |Sure ?| |Sleeping !| || GPS Control|Reset (Cold) ?|Execute a “Cold Boot” of the GPS module |Sure ?| |Resetting GPS !| || |Reset (Warm)|Execute a “Warm Start” of the GPS module |Sure ?| |Resetting GPS !| || USB Device|Remove?|Prepare the USB mass storage devices to be detached |WAIT !| |Remove it !|This menu point has a second functionality: Executing this function will automatically pause / continue the writing data to disk in “Moving MT” mode. || Detect Sensors|Start ?|Restart the sensor detection in the ADU-07e system |WAIT !| |Done !| || W-Lan Control|Switch On/Off?|This menu point is used to switch on / off the W-Lan of the ADU-07e system. Depending on the current state the first entry either asks to switch the W-Lan On, or Off . The operation is acknowledged either with “success”, “failed” or “No Module”, if no W-Lan module is installed. |WAIT !| |Success / Failed / No Module| Some of the menu items, like the “Shutdown Control”, “Sleep Control”, “GPS Control” and “USB Device” will execute some actions inside the ADU-07e system. Therefore the use of this menu items is described in detail in the following chapters. “Shutdown Control” ------------------ By the use of the “Shutdown Control” menu item you may shut-down the ADU-07e system. The following procedure activates the shut-down of the system: IMAGE “Shutting Down” system via “Front-panel Display” Once, the shut-down sequence has been initialized the following will happen: 1. All currently running measurements are stopped and their data will be written to disk. 2. The Linux system will shut-down. The procedure takes about 30 seconds until the complete Linux system is shut down. Only after this time it is completely safe to power off the system. “Sleep Control” --------------- With the “Sleep Control” menu item you may activate or deactivate the “Sleep Mode” of the ADU-07e system. When the ADU-07e has been booted up, the “Sleep Mode” is deactivated initially. It can be activated using the “Front-panel display” by doing the following: IMAGE “Activating Sleep Mode” via “Front-panel Display” Now the “Sleep Mode” is activated. The ADU-07e will fall asleep (the CPU board enters “Suspend To RAM” state), whenever possible. This will drop the power consumption of the ADU-07e system drastically. The disadvantage is that the system can not be accessed via the Web-interface or Samba server anymore until the “Sleep Mode” has been deactivated again. The ADU-07e can be awakened from sleep mode by using the same “Sleep Control” entry on the “Front-panel display” that was used to activate the “Sleep Mode”. You will see that the menu entry has been toggled into a mode which allows a deactivation the “Sleep Mode”. This is achieved as follows: IMAGE “Deactivating Sleep Mode” via “Front-panel Display” As a result the ADU-07e system will be woken up from hibernation immediately and the “Sleep Mode” will be deactivated afterwards. **Information:** The “Sleep Mode” is only available on ADU-07e systems, that are equipped with the new “Lippert Cool LiteRunner (Geode)” CPU boards. The older “Arcom Viper (ARM)” CPU boards do not support the “Sleep Mode”. In this case the activation of the “Sleep Mode” via the “front-panel display” is ignored. “GPS Control” ------------- With these menu items you may execute either a GPS “Cold Boot” or a GPS “Warm Start”. In both cases the GPS module inside the ADU-07e system will be reset. In order to activate this feature use the following procedure: IMAGE “Resetting GPS” via “Front-panel Display” If you execute a “GPS Cold Boot”, the GPS module will be completely reset. It will delete all GPS internal data, like almanac, satellite positions and time information. As a result the GPS will require up to 15 minutes to receive a new almanac and renter a 3-D-Fix again. For that reason when executing the “GPS Cold Boot”, the ADU-07e system is shut-down automatically and needs to be rebooted. It may be useful to use this option in case you moved the ADU-07e system over long distances (>300km), where all satellite positions would be completely different from the location where the ADU-07e had its last Fix. Otherwise, the GPS could have problems getting a Fix and it might take quite a long time before it sees satellites again. If the user initiates a “GPS Warm Start”, only the GPS module will be reset. It will keep its almanac and satellite position data. As a result it will have a Fix within 3 to 4 seconds after the reset. The ADU-07e will stop all running measurements and resynchronize the GPS and will not shut-down. The Warm Boot is useful in case you want to move the ADU-07e system at short distances and keep the ADU-07e on power. It is required to execute the Warm Start after a system move has taken place because the instrument’s GPS module switches to a so called “position hold” mode after having obtained a G3Fix for longer than 10 minutes. In the “position hold” mode it is able to get very precise time information but it takes for granted that it is not moved anymore. If you move the system without initiating a “GPS Warm Start” the GPS module will get in trouble and will stop to provide new position and time information. “W-Lan Control” --------------- With these menu items you may switch on/off the ADU-07e internal W-Lan interface if built-in. Depending on the current state of the W-Lan, the “W-Lan Control” menu entry shows the following messages: IMAGE “W-Lan Control” via “Front-panel Display” As it can be seen in the figure above, the menu entry shows the test “Switch On?”, if the W-Lan is currently switched off. If clicking on the “PARAM” button now, the W-Lan will be switched on. Depending on the result of this action, the menu entry will display the result “Success”, “Failed” or “No Module” afterwards, if no W-Lan module is installed inside the ADU-07e system at all. If the W-Lan is currently switched off, the first entry will show the text “Switch Off?”. Pressing the “PARAM” button will now switch off the W-Lan interface inside the ADU-07e system. **Information:** In order to save battery power, the W-Lan module is switched off after system start by default. You need to switch it on before usage. In order to save energy during long term measurements it is recommended to switch off the module again. “USB Device” ------------ With this menu item you may prepare any attached USB mass storage devices to be removed. → please refer to chapter 13 for a detailed description ADU-07e Control by USB Devices ------------------------------------------- In order to make it more simple to use the ADU-07e system in even larger measurement campaigns, where multiple systems need to be handled at the same time e.g. by field personal less trained in ADU-07e programming, the instrument is able to start complete job-lists from “pre-configured” USB mass storage devices. This may be a USB pen-drive, USB hard-disk or other USB mass storage device. If such a “pre-configured” mass storage device is attached to the USB socket on the ADU-07e front panel (see chapter 2.1.1) the system is going to scan the device for pre-configured job-lists and – if present - transfer them into the internal “job” table automatically. The ADU-07e will then configure, start and stop jobs according to the preprogrammed list. It is also possible to use the attached mass storage device to store the measurements data on them directly. In order to be able to use a USB mass storage device along with the ADU-07e, it must contain a specific file system along with an XML configuration file. The method how to create such a pre-configured device is described in detail in the following chapters. **Inforamtion:** Please note, that this chapter describes the manual method to create a “pre-configured” USB mass storage device. You may also use the Web-interface to export a job-list to be used on a USB device. Please refer to chapter 8.3.2 to find out how to create a “pre-configured” USB device by means of the Web-interface. Directory Structure ------------------- On the mass storage device the following directory structure has to be created: IMAGE Directory structure of “pre-configured” USB mass storage devices - 1 As it can be seen in the picture above, the USB mass storage device needs to contain two folders. The first one is the “ADU07Conf” directory. It contains the “ADU07Conf.xml” XML configuration file. This file contains all instructions for the ADU-07e instrument of how to handle the USB mass storage device and the job-list that is stored on it. **Information:** Without the “ADU07Conf” directory and “ADU07Conf.xml” the USB mass storage device will not be mounted by the ADU-07e system and simply be ignored. It is not allowed to give a different name than “ADU07Conf”. Otherwise, the ADU-07e will also not recognize the USB device. The second directory is called “Job-list1” here. It contains all the XML job files that shall be part of a job-list. This directory and the XML job files inside may be named as desired by the user. References to the XML job files are created inside the “ADU07Conf.xml” XML configuration file to create job-lists out of the single XML job files. There can be even more than one directory containing XML job files. If the USB mass storage device is configured to store measurement data on the USB device, the data folders of the single measurements of the job-list will be located in the “root” directory of the USB device (see the following picture). IMAGE Directory structure of “pre-configured” USB mass storage devices – here also containing a folder with measured data **Caution:** Despite the standard FAT32 system normally installed on external USB-stick often works well with the ADU-07e Linux operating system, the Linux EXT3 file system is better protected against sudden power loss during file access. You may therefore consider to use the Linux EXT3 file system in this case. Even if recoding for days there have not been any problems with data storing on USB devices using this file-system. A Windows XP adapter for reading EXT3 file systems is available for free at the following link: http://www.fs-driver.org/ “ADU07Conf.xml” XML configuration file -------------------------------------- As already described in the prior chapters the ADU-07e searches for the “ADU07Conf.xml” configuration file on the USB mass storage device to get to know, how it should handle the USB device. If this specific file cannot be found inside the “ADU07Conf” directory or if it is invalid, the USB device will simply be ignored by the ADU-07e instrument. A sample “ADU07Conf.xml” file is shown in the following picture: .. code:: xml adjusted 0 17:52:00 0000-00-00 USB_TO_DEFAULT TRUE TRUE E_SERIES FALSE TRUE Example “ADU07Conf.xml” XML configuration file As it can be seen in the picture above the “ADU07Conf.xml” file contains several XML nodes that define the behavior of the USB mass storage device if attached to an ADU-07e. Generally spoken there are two main sections: The first one contains all configuration nodes to define, how the USB device shall be handled. This part consists of the “TargetDirectory”, “TimeFormat”, “TimeOffset”, “StorageMode”, “AdaptConfig” “AdaptSensorSpacing”, “AdaptSensorType”, AdaptChannelConfig” and “CleanJobTable” nodes. The nodes have the following meaning: **Description of nodes inside the “ADU07Conf.xml” XML configuration file** * **TargetDirectory** This node contains the target mount point for this device inside the ADU-07e file system. If the node is left empty, the ADU-07e will mount the device anywhere and directly unmount it again when the job-list has been transferred completely. In this case no measurement data can be stored in it. It is strongly recommended only to use mount points within the “/mtdata” directory of the ADU-07es file system (e.g. “/mtdata/usb/data1”). If it is mounted anywhere else inside the system, the ADU-07e´s internal file system may get messed up. **Note:** If you set the value of this node to “/mtdata/usb/data1”, the USB device will be mounted to the internal data directory. By this means no data will be stored on the CF-card anymore, but all data will be stored on the USB device instead, until you remove the device again from the ADU-07e system. * **StorageMode** This node defines how the data that is recorded according to the single jobs of the job-list shall be handled. You have the choice to store the data either on the USB device, on the internal CF-card or to the destination defined inside the XML job files. Therefore set the nodes value to one of the following values: * **USB_TO_USB:** store data of jobs started from USB device to the same USB device * **USB_TO_DEFAULT:** store data of jobs started from USB device to the default path on the internal CF card (“/mtdata/data”). * **USB_TO_JOB:** use the destination directory defined by the “target_dir” node inside the XML job file. If left empty, the data will always be stored on the internal CF-card. * **TimeFormat** By the use of this node you may define if the jobs of the job-list shall be started at the next possible start-time or whether the start-/stop times shall not be changed at all. * **absolute:** do not change start-/stop times of the jobs inside the job-list. * **relative:** adapt start-/stop times of the jobs to start the jobs at the next possible start time. Keep the structure of the job-list (sequence and duration - see chapter 13.3). * **adjusted:** adapt start-/stop times of the jobs to start the jobs at the point of time that is defined by the “start_date” and “start_time” nodes (sequence and duration - see chapter 13.3). * **grid:** adapt start-/stop times of the jobs to start the jobs at the next valid “Grid” time that is defined inside the “start_time” node (sequence and duration - see chapter 13.3). * **TimeOffset** This is an internal parameter that must be left empty. * **start_time/start_date** These two nodes contain the start-time and start-date, that shall be used in the “adjusted” and “grid” modes to determine the new start-time for all the jobs of the job-list. * **AdaptConfig** set this node value to "TRUE" to replace the site configuration (comments, ...) to the values that are currently active on the ADU system. If set to FALSE the values of the joblist will be used. * **AdaptSensorSpacing** Set this value to TRUE to use the values currently stored inside the ADU for the sensor spacing definition. If set to FALSE the sensor spacing values defined in the joblist will be used. * **AdaptSensorType** Set this value to E_SERIES to overwrite the sensor config (type and serial) for all intelligent sensors (MFS07e, MFS06e, ...) with the information that has been detected during boot. This should be the default. Set this value to ALL to replace all the sensor config inside the joblist with the currently used values of the ADU (Webinterface). Set this value to NONE to use the sensor config of the joblist and ignore all currently used ADU settings. * **AdaptChannelConfig** If set to “TRUE” the ADU-07e system will update the channel configuration of all jobs of the job-list with the values that have been determined when executing the “AutoGain AutoOffset” jobs via the “Selftest Config” page. The following values are updated: * Gain Stage 1 * Gain Stage 2 * DC Offset correction * RF filter setting (on LF and MF ADB boards) The values that are used for the update are read from the “ADU07ChannelConfig” XML file that is created / updated, whenever the “AutoGain AutoOffset” jobs are executed. These jobs try to determine the best fitting values for gains and DC offset correction for the current measurement site. To activate / deactivate the update of the gains and DC offset correction of the job-list jobs use the following values for the “AdaptChannelConfig” node: TRUE: update gain and DC offset correction settings FALSE: do not change the XML job files configuration settings * **CleanJobTable** With this node you select, whether the ADU-07e system shall clear the “jobs” table before the new actual job-list is started. This may be useful to remove old jobs that may conflict in start-/stop times with the jobs of the job-list or just to get a better overview. TRUE: clean “jobs” table before starting jobs of job-list FALSE: just start jobs of job-list and simply add them to the “jobs” table * **Job-list Jobs id=”1”** The “JobsList” node finally contains a list of XML job files that are part of the job-list and that shall therefore be started automatically by the “USB Auto-mounter”. The “Jobs” nodes contain a path relatively to the root directory on the USB stick where the corresponding XML file is located. The “id” attribute defines the number of the jobs inside the job-list (sequence). The second section of the “ADU07Conf.xml” file is the definition of the job-list that shall be started in case the USB device is attached to the ADU-07e system. The section is built up as follows: .. code:: xml /Job-list1/Job1.xml /Job-list1/Job2.xml For each job that shall become part of the job-list, a node “Job” needs to be created. The node gets a unique “id” value. It is simply incremented from job to job. Inside each “Job” node a node “TargetDirectory” must be defined that contains the complete path information of the XML job file belonging to this specific job. The path is given relatively to the “root” directory of the USB device. E.g.: If the XML job file named “Job1.xml” is located in the “/Job-list1” folder on the USB device, the contents of the “TargetDirectory” node must be “”/Job-list1/Job1.xml”. If the job-list is started, the jobs are read by the ADU-07e and transferred to the internal “jobs” table inside the MySQL database. If the “TimeFormat” node is set to “realtive”, the ADU-07e instrument will try to start the job-list at the next possible point in time. A description of this is given in the next chapter. Starting a Job-list ------------------- If a job-list was configured inside the “ADU07conf.xml” file, the ADU-07e will try to transfer all the XML job files into the “jobs” table of its database. From this location they will be started automatically. If one of these XML job files cannot be found, e.g. because the path pointing to it was programmed wrongly or the XML file itself is invalid, the job will not be started. All other (correct) job files will be started and transferred to the “jobs” table inside the database In case the “TimeFormat” node is set to “relative” the instrument will try to start the job-list at the next possible point in time. However, it will maintain the time structure of the job-list itself. The following example shall illustrate this issue: Let´s assume that we have a job-list consisting of these three jobs: **Job1.xml:** * start-time: 01.01.2000 14:00:00 * stop-time: 01.01.2000 14:10:00 **Job2.xml:** * start-time: 01.01.2000 13:50:00 * stop-time: 01.01.2000 13:55:00 **Job3.xml:** * start-time: 01.01.2000 14:08:00 * stop-time: 01.01.2000 14:18:00 The schedule for the jobs would be like this: IMAGE Time schedule of original job-list The job-list shall be started at the next possible point in time now. Let as assume that the current time is 19.06.2009 12:03:00. Now, the ADU-07e will scan the job-list for the job with the earliest start-time, which is “Job2.xml” in this case. Using a required handling time of 55 seconds it will then set the “new” start-time of the job to “19.06.2009 12:03:55” and the “new” stop time to “19.06.2009 12:08:55”. As one can see, the duration of the job is maintained. The job’s start- and stop time is simply shifted to the next possible start-time. In order to retain the time structure of the job list, the start and stop times of the subsequent jobs are changed as follows now: **Job1.xml:** * start-time: 19.06.2009 12:13:55 * stop-time: 19.06.2009 12:23:55 **Job2.xml:** * start-time: 19.06.2009 12:03:55 * stop-time: 19.06.2009 12:08:55 **Job3.xml:** * start-time: 19.06.2009 12:21:55 * stop-time: 19.06.2009 12:31:55 This will result in the new structure of the job-list given in the next picture: IMAGE Time schedule of “relative” job-list As it can be seen in this example, even if started at the next possible point in time, the relative structure of the job-list will not be changed. The jobs will be executed in the same chronological order, as they were defined in the original job files. In addition, the order they are entered inside the “ADU07Conf.xml” file does not matter. The structure of the job-list is simply defined by the start-/stop times of the individual XML job files. Using the “adjusted” mode instead, the user may configure a new start-date and start-time by dint of the “start_date” “start_time” nodes inside the “ADU07Conf” XML file. This way the complete job-list will be shifted to the user defined new start-date and time. The first job then will start exactly at time defined by the “start_date” “start_time” nodes: Example: **Job1.xml:** * start-time: 19.06.2009 12:13:55 * stop-time: 19.06.2009 12:23:55 **Job2.xml:** * start-time: 19.06.2009 12:03:55 * stop-time: 19.06.2009 12:08:55 **Job3.xml:** * start-time: 19.06.2009 12:21:55 * stop-time: 19.06.2009 12:31:55 **new start-date and time inside “ADU07Conf” XML file:** * 01.01.2010 10:00:00 IMAGE Figure 13-6: Time schedule of “adjusted” job-list If using the “grid” mode the user can configure a time grid that shall be used to start the complete job-list. Using the “grid” mode can help to ease the operation in the field The user knows that the joblist will be started exactly on the time grid (every 15 min., every hour, just what seems to be appropriate). The grid is defined by the “start_time” node. E.g. if setting the “start_time” nodes value to “00:15:00” the grid where the job-list can be started is the following: **Grid defined by “start_time” node:** * 00:15:00 (full 15 minutes) **Resulting valid start-times:** * …, 08:45:00, 09:00:00, 09:15:00, 09:30:00, … Example: **Job1.xml:** * start-time: 19.06.2009 12:13:55 * stop-time: 19.06.2009 12:23:55 **Job2.xml:** * start-time: 19.06.2009 12:03:55 * stop-time: 19.06.2009 12:08:55 **Job3.xml:** * start-time: 19.06.2009 12:21:55 * stop-time: 19.06.2009 12:31:55 **Grid defined by “start_time” node:** * 00:15:00 (full 15 minutes) **Current Time:** * 09:08:52 IMAGE Time schedule of “grid” job-list Connecting a Pre-configured USB Mass Storage Device ---------------------------------------------------- If you have a “pre-configured” mass storage device containing a job-list, you may start the latter by simply plugging-in the USB device to one of the USB sockets of the ADU-07e. As a result you will see the following messages on the front panel display: IMAGE Front-panel messages if attaching USB device When you see the last message “USB: job-list transferred completely” you can be sure, that all the jobs of the job-list have been transferred to the “jobs” table inside the ADU´s database. If you did not define the USB device as data storage media you may remove it then. To avoid data loss you should prepare the USB device to be removed before detaching it from the USB connector. This is achieved with the “USB Device” menu item of the front panel display: IMAGE Front-panel menu for removing USB device This procedure will synchronize the file system and write all cached data to the disks. By this means it is safe to remove the USB device without risk of data loss. **Caution:** Removing a USB Device without using the front-panel menu´s “Remove” button may cause data loss because Linux does a lot of file system data caching in RAM in order to speed up system performance. Removing a USB device on which a measurement presently running is storing its data will have the effect that the data stream cannot be saved on the device anymore. The data folder will simply disappear then and a total data loss will be the result. Hence, make sure that no active measurement is using the USB device anymore before its removal. Access via SSH Protocol ------------------------------------------- An access to the ADU-07e via SSH protocol is used to directly work on the ADU’s Linux operating system. In order to access the ADU-07e, you require an SSH client installed on your PC. For most Linux systems it is already part of the operating system. For Windows ™ systems, you may use “Putty” for example. Additionally, in order to access the ADU-07e you need a pair of username and password. By default the ADU-07e provides the following user accounts: .. csv-table:: Predefined Standard users on Linux operating system :delim: | Username|Password|Description root|!dgrtv255|This is the root user (super-user). He has unlimited access to the Linux system on the ADU-07e. Therefore this mode should only be used by trained personal for system configuration (e.g. updates) and debug purposes. aduuser|neptun|The aduuser is the standard user. It shall be used by all operating personnel, who just want to use the ADU-07e for standard measurement tasks. To establish an SSH connection to the ADU-07e instrument, in addition to the username and password you need the target IP address of the ADU-07e you want to login. The following settings are used as a system default: .. csv-table:: Default network settings of the ADU-07e :delim: | Name|Value IP address|192.168.0/1.SSS Broadcast address|255.255.255.0 Net-mask|255.255.255.0 As you can see in Table 14-2 the ADU-07e is configured for a Local Area Network (LAN). The IP address is set to a 192.168.0.SSS or 192.168.1.SSS address. The IP address is given on a sticker inside the ADU´s lid. It also can be read from the system status display. The following chapters describe the access to the system, on the one hand using a Linux operating system and its standard shell commands and on a second case using a Windows XP\ :sup:`®` operating system along with the freeware tool “PUTTY”. SSH Access from Linux Operating System -------------------------------------- To open an SSH connection from a Linux system, you have to do the following: 1. Open a new shell console on your Linux PC. It will look like this: IMAGE 2. Execute the following command: .. code:: ssh root@ After execution of this command on the shell console, the system will ask you for the “root” user´s password. It has to be typed in and confirmed by “Return” key. The following commands should be displayed on the shell console: IMAGE Now, you are logged into the Linux operating system of the ADU-07e. You are able to work on it, like on each and every other Linux shell console. For example you may directly examine the data directory of the file system. For this purpose type in the following command: .. code:: ls –l /mtdata Afterwards you should see the following entries on the shell console: IMAGE For a complete explanation of all Linux shell console commands, please refer to the relevant manuals and lists in the Internet or in Linux books and “How-to’s”. Please note, that the Linux operating system on the ADU-07e provides a limited command set only. In consequence of this some of the commands which you may find in the “How-to’s” may not work on the ADU-07e’s Linux system. SSH Access From Windows XP Operating System Using “PUTTY” --------------------------------------------------------- As Windows XP does not provide an SSH Client software on standard you need to install an additional free software tool. Here, the best is to use the “Putty” tool. It can be downloaded from the following URL: http://www.heise.de/software/download/putty/7016 or you just type “PUTTY” to a search engine. After having downloaded the program, just install it to your Windows system. After the installation has been finished, open the application. The following window will appear: IMAGE “Putty” main screen You just need to configure the connection to the ADU-07e system. For that purpose enter the target IP address in the “Host Name (or IP address) field. Select connection type SSH. Afterwards, try to open the connection to the ADU-07e system by clicking on the **Open** button. You should see a new window now, containing a shell console and asking you for username and password. These are the same ones as described in the chapter for the connection from a Linux system. IMAGE Shell console via SSH using “Putty” All other operation now is the same, as described in connection from a Linux system. **Information:** For an SSH connection to the ADU-07e system from a Windows PC it is important, that the PC and the ADU-07e system are residing within the same network and that the SSH port (default port 22) are opened and can be used. Otherwise, the connection will not be established. Changing Passwords ------------------ The default combination of username and passwords pre-defined for the standard ADU-07e can be modified by the user if desired. For this purpose you will have to log into the system via SSH as “root” user, as described in the chapters 14.1 and 14.2. Afterwards, please execute this command: .. code:: passwd By executing this command, the Linux system of the ADU-07e will ask you for the new password for the user who was entered as . After having typed in the new password, it has to be confirmed. Therefore, it has to be entered again. Eventually, the password for the current user is changed from the default phrase to the new one which you have entered here. Please note, that no SSH connection can be built up anymore using the old pair of username and password for this user. **Information:** As it is described in this chapter, it is only possible to change the password for the existing users “root” and “aduuser”. The Linux operating system of the ADU-07e does not support the creation of new users. Changing the Network Settings ----------------------------- The ADU-07e system comes up with a factory default network configuration after power on. It uses an IP address of the 192.168.x.x network range which is reserved for the connection of devices in home networks. You will find the default settings in chapter 14. This allows connecting the system without knowledge in which target IP network it will work later on. The network settings are activated as a part of the start-up procedure of the ADU-07e instrument. A “Shell script” is implemented on the ADU-07e software, which is started at boot time. To adapt the network settings to your needs, you will have to edit this shell script. It can be found in the following path on the ADU-07e´s Linux operating system: .. code:: \home\mtx-adu07-network-settings This shell script contains some constants that define the network settings: .. csv-table:: Defaults in shell script “mtx-adu07-network-settings” :delim: | Constant Name|Default Value|Description DEFAULT_IP_ADDRESS|192.168.0.SSS |Default IP address of the ADU-07e system DEFAULT_BROADCAST_ADDRESS|255.255.255.0|Default broadcast address of the ADU-07e system DEFAULT_GATEWAY|192.168.0.SSS|Default Gateway of the ADU-07e system To change the IP settings of the ADU-07e system, you have to change the values of these constants according to your requirements. Afterwards, it is required to restart the ADU-07e system to let the modified network settings become active. For editing the file, the “VI” editor is installed on the ADU-07e system. **Information:** If you change the network settings and restart the system, it will not be possible to connect to it with the old IP settings. Therefore make sure, that you are able to connect to the ADU-07e with the newly programmed network settings. It is possible to add additional shell commands, such as the “route” command here which will automatically be executed on start-up of the system. This for example may be necessary, if the system shall be visible outside of a network. To change the network settings, type in .. code:: vi mtx-adu07-network-settings. and then press “Return” Move the cursor to the position you want to edit. Press I to enter the Edit mode of vi editor and modify the numbers according to your needs. Then press ESC two times until the screen flashes and then press :wq in order to save the modification and leave the editor. IMAGE command to enter the network settings Now a new screen will be displayed: IMAGE editing the network number (here 218). Press “i” to enter the edit mode, change the number according to your requirements and press “ESC” key two times until screen flashes. Then type :wq in order to save and exit the editor. In order to change the W-LAN settings you have to edit the two files: startW-Lan and stopW-Lan accordingly using vi-editor again. In startW-Lan you need to edit the entries IP_ADDRESS and ESSID. in stopW-Lan you need to edit the “ifconfig” line accordingly. Access via Samba Server (Data Directory) ------------------------------------------- To get an easy access to the measurement data stored on the ADU-07e system, it supports a “Samba” file server. The “Samba” protocol is supported by both, Linux and Windows XP™ operating system. Therefore you will be able to connect to the ADU-07e system from both, Linux and Windows XP. Same as for the SSH access, the access to the data directories on the ADU-07e system via the Samba protocol has a password protection. To access the system, you need a pair of username and password. As factory default, the following pairs of username and password are implemented in the ADU-07e system: .. csv-table:: Standard users for “Samba” access :delim: | Username|Password root|!dgrtv255 aduuser|neptun As you can see, the factory default for the “Samba” users is equal to the Linux users, as they are defined in chapter 14. By the use of the “Samba” server as file server, you are able to browse through the measurement data, as if this would be a local directory on your Laptop or PC. In the data directory of the ADU-07e you will find the following sub directories: .. csv-table:: Subdirectories on “Samba” server :delim: | Name|Description data|The data directory contains the real measurement data, that is stored by the ADU-07e system on the internal CF-card. For each measurement a new folder is created, that contains the date and time, the measurement was started in its name. In this folders, the ATS data files are stored. log|The log folder contains some log files of the ADU-07e system. usb|This directory is contains the default mount directory for “pre-configured” USB devices, along with two directories to import / export job-lists. aduuser / root|This is the home folder of the according user on the Linux system. You may store user specific data in this directories. Measurement data can be examined and copied to your Laptop even during an active recording. The only thing you have to take care is to make sure that the files with the measurement are not blocked or deleted for the ADU-07e system as long as the measurement is still active. In the following chapters it is described, how you may enter the data directory from Linux and Windows XP operating systems. **Caution:** If you rename, move or delete measurement data files, whilst the measurement is still active, the ADU-07e is not able to write new measurement data to the disk anymore and/or the data gets corrupted! Accessing the “Samba” Server from Linux Operating System -------------------------------------------------------- If you use a Linux operating system on your Laptop or PC, the access to the “Samba” server running on the ADU-07e is quite easy. All you need is a Browser that supports the “Samba” protocol for file access. Metronix recommends to use the “OpenSUSE” Linux system. The standard browser of this system, the “Konqueror” supports “Samba” file access on default. This chapter will describe how to access the “Samba” server of the ADU-07e system from such an “OpenSUSE” Linux system using the “Konqueror”. You have to execute the following steps: 1. Open a new “Konqueror” window and type in the following URL in the address field: .. code:: smb:// This should call a password dialogue, if you connect to the ADU-07e for the first time. IMAGE Here you have to enter username and password. Afterwards, confirm your entries by clicking on the **OK** button. Now, you should see the contents of the data directory of the ADU-07e system in your “Konqueror” window. IMAGE You may browse through the directory as it would be located locally on your Laptop. You may even delete, copy and edit the files within the single subdirectories. Accessing the “Samba” Server from Windows XP, VISTA, 7 or 8 Operating System ---------------------------------------------------------------------------- The access to the “Samba” server on the Linux operating system from a Windows XP operating system is simple, too. Here you use the “File Explorer” to access the “Samba” server on the ADU-07e. You have to execute the following steps: 1. Open a new “File Explorer” window and type in the following URL in the address field: .. code:: \\ This should call a password dialogue, if you connect to the ADU-07e for the first time. IMAGE Here you have to enter username and password. Afterwards confirm your entries by clicking on the **OK** button. Now you should see the contents of the data directory of the ADU-07e system in your “File Explorer” window. IMAGE File Explorer Window with ADU directory structure You may browse through the directory, as you do it on your local Laptop. You may even delete, copy and edit the files in the single subdirectories. Access to the MySQL Database ------------------------------------------- On the ADU-07e system the main data interchange between the Web-interface acting as “HMI” (Human Machine Interface) and the hardware is done via the ADU-07e MySQL database. The name of the database on the ADU-07e is “mcpdb07”. It contains several tables for different types of data such as the self-test jobs, current system status etc. As the database also contains all the error and status messages, it is a good idea to dump the contents of it to an SQL file at the end of each survey. This can be done in three different ways: 1. **Direct access to the database via MySQL Shell Console tool:** The MySQL database is accessed by the use of the MySQL console tool. On the Shell Console MySQL commands are directly executed. This can either be done directly on the ADU-07e´s Shell Console if logged-in via SSH or via remote access from a different computer. 2. **Using the GUI freeware tools like “PHPMyAdmin”:** The “PHPMyAdmin” tool is a very useful and easy to operate tool to access MySQL databases. It generally provides all functionality of the Shell Console tool with the additional advantages of an Graphical User Interface (GUI). 3. **Using the Metronix database scripts:** For maintenance of the Metronix database, a special Shell script was created. This script, called “mtx-check-database” is residing in the “/home” directory of the ADU-07e system and can be used, if locked into the system via SSH. The single access methods are described in the following chapters. **Caution:** The ADU-07e system needs an accurate MySQL database for its operation. Therefore make sure that you do not delete or corrupt the database. Metronix advises you to only access the database by the “mtx-check-database” Shell script. Access via MySQL Shell tool --------------------------- To access the MySQL database with the MySQL Shell tool you must be locked into the system as “root” user via SSH. If done, execute the following command: .. code:: mysql This will start the MySQL Shell Console like shown in the following picture: IMAGE On this shell you may use all the SQL commands that are defined for the MySQL language. Please refer to the MySQL documentation for a detailed description of all the SQL commands. If you want to lock into the MySQL database from a remote computer, you have to use the following command: .. code:: mysql –h Afterwards, you may work on the MySQL database just as if you were locked in from the Shell Console of the ADU-07e system itself. Access via “PHPMyAdmin” tool ---------------------------- It is easier to access the MySQL database by the “PHPMyAdmin” open source tool. This tool is a web application similar to the ADU-07e Web-interface. It needs to be installed on a computer which is running a Webserver such as “Apache”. If you have such a system just simply install the “PHPMyAdmin” tool to the server directory on your computer. Nevertheless, if you do not have the “PHPMyAdmin” tool installed on your computer, you may call it directly from the ADU-07e system by using the following URL: .. code:: http:///phpmyadmin/main.php Afterwards, you should see the following page. IMAGE Login screen of “PHPMyAdmin” tool On this page you may enter “aduuser” for “Username” with no password and click on the “Login” button. Afterwards, you the following screen will be displayed: IMAGE Database selection screen of “PHPMyAdmin” tool On this page you may access the ADU-07e specific “mcpdb07” database and work on it. For a detailed description of the “PHPMyAdmin” tool please refer to the “PHPMyAdmin” manual. **Information:** If you access the “PHPMyAdmin” pages directly from the ADU-07e system and you use an ADU-07e MK1 (with Arcom Viper CPU board) the performance of the tool is very poor. Therefore, Metronix recommends to install the “PHPMyAdmin” tool and a Web-browser locally on your Laptop or PC and initiate a remote access to the database. The “PHPMyAdmin” tool as well an “Apache2” Web-server for Windows is available for example from: http://www.apachefriends.org/de/xampp-windows.html Use of “mtx-check-database” Shell Script ---------------------------------------- The easiest way to maintain the database is to use the “mtx-check-database” Shell script. It allows you to make copies of the database, check the database for damages and to repair the database, if broken. Additionally, the “mtx-check-database” script has some functionality which is performed on the ADU-07e system automatically: 1. **Automatic check of database on start-up:** Each time when the ADU-07e system starts, the “mtx-check-database” script checks the ADU-07e database for damages. If the database is OK, the current content of the database is dumped into “/home/mcpdb07.sql”. 1. **Automatic repair of database on start-up:** If during start-up of the ADU-07e system the database is marked as “damaged” or “crashed”, the “mtx-check-database” script tries to repair it. In case a repair is not possible, the current content of the database is replaced by the last copy of the MySQL database, that was written as a backup to “/home/mcpdb07.sql” the last time the ADU-07e system started without errors. All this functionality is available to the user, too. In order to make use of the script you have to log into the system via SSH as “root” user. Afterwards, you may use the following commands to work on the database: .. csv-table:: Parameters of Shell script “mtx-check-database” :delim: | Parameter|Description --check |Calling the script with this parameter the script will check the table that is defined in the field
in the MySQL database. If the table is broken, it shall return -1. If it OK, it shall return 0. If the
parameter is not applied, all tables will be checked. Return Value: 0: tables are OK, -1: at least one of the tables is broken --repair
|Calling the script with this parameter it will try to repair the according table. If this works correctly, it will return 0, otherwise it will return 0. If the
parameter is not applied, all tables will be repaired. Return Value: 0: tables are OK ; -1: at least one of the tables is broken --dump |Calling the script with this parameter it will dump the actual content of the MySQL database to the file defined with the parameter. If the parameter is not applied, the content will be written to file “\home\mcpdb07.sql”. --rebuild |Calling the script with this option will overwrite the actual content of the database with the database, that is stored in the sql file . If the parameter is not applied, the content will be taken from the file “\home\mcpdb07.sql”. Calling the script without any parameters will print a list of all available parameters on the shell console. Additionally, the version number of the Shell script will be displayed on the console together with a short description of the functionality of the script. As already mentioned in the chapters above, it is a good idea to dump the contents of the database to a SQL file and store it along with the measurement data of the measurement campaign. By this means all the system status messages are available for error tracking, if problems occur during data processing. In order to store the contents of the database to disk the “mtx-check-database” script is used: .. code:: mtx-check-database --dump Best is to dump the database to the path “/mtdata/log/” as you have access to this directory via “Samba” and therefore you are able to easily download the file from the ADU-07e system. Instead of the “log” directory you may use the “data” directory, too. **Information:** If unforeseen problems should occur during ADU-07e operation it is a good idea to dump the contents of the MySQL database in addition. Afterwards, send the database dump file to Metronix. We can load the database into an ADU-07e system and examine the status and error messages to help you to solve the problem. Integrating ADU-07e into a VPN ------------------------------------------- **Information:** Establishing a VPN connection to your VPN strongly depends on the settings of your VPN server. Therefore please ask your local network administrator for help to configure the “OpenVPN” client on the ADU-07e system. Especially if the ADU-07e system is equipped with the Lucom UR5(i) GSM modem it can be usefull to integrate the system into an existing VPN (Virtual Private Network). For this purpose the “OpenVPN” client is installed on the ADU-07e system. It is located in “/usr/sbin”. To establish a VPN connection from the ADU-07es Linux system you need to do the following: 1. **Adapt the “OpenVPN” configuration file:** To make it possible to connect to a VPN server you need to adapt the “OpenVPN” configuration file in “/etc/openvpn/openvpn.conf” to your needs. An example configuration file is shown in the following picture. It builds up a VPN connection to the “mdex.fixedIP” service of “mdex” company: .. code:: # act as client client # connection settings and host name dev tun #resolved IP address of fixedip.mdex.de is 80.146.165.22 remote 80.146.165.22 # use UDP and port 9300 for connection rport 9300 proto udp # driver node for tun.ko dev-node /dev/tun tun-mtu 1500 fragment 1300 # re-generate keys after one day reneg-sec 86400 # keepalive ns-cert-type server # this is the link to the server certificate file ca /etc/openvpn/IC3S-CA.CRT cipher BF-CBC # this ist he link tot he password file, if the authentification iss et # to “username and password” auth-user-pass /etc/openvpn/passwords.txt # use lzo compression for data transfer comp-lzo As the configuration strongly depends on your network you need to update this file to your needs. 2. **Adapt the password file** 3. **Adapt the “Master Certificate” file** 4. **Load the “tun.ko” driver:** The “tun.ko” driver is used to create virtual network adapters for the VPN. It is located in “/lib/modules//drivers/net/tun.ko”. It can be loaded to the kernel by using the following command: .. code:: insmod /lib/modules//drivers/net/tun.ko 5. **Start the “OpenVPN client”** Finally the “OpenVPN” client can be started by using the following command: .. code:: /usr/sbin/openvpn /etc/openvpn/openvpn.conf **To start the “OpenVPN” client as a deamon use the following command instead:** .. code:: start-stop-daemon –S –q –b –x /usr/sbin/openvpn/etc/openvpn/openvpn.conf If successful the ADU-07e system will finally be reachable within your VPN. For a detailed description of how to configure the “OpenVPN” client for your needs please see http://openvpn.net/index.php/open-source/documentation/howto.html. Fallback Strategy of the ADU-07e ------------------------------------------- As the ADU-07e provides a lot of different hardware and software functionalities, it may happen, that the user made a miss-configuration of a measurement job. This for example may be the selection of gains, filters or samplings frequencies that are not supported by a certain ADB board or the simultaneous use of the calibration board in different modes (different calibration frequencies). In this case the ADU-07e instrument will create a message and write it to the “System History”, the “Error List” and - in critical cases - even to the front panel display. In addition, the ADU-07e will try to use some fallback values, hence the measurement can be started anyhow. This may occur for the selection of the sampling frequencies of the ADB boards, the selection of gains and filters for the ADB boards as well as the use of the calibration board. For all these cases the according fallback strategies are described in the following chapters. Fallback Strategy for Sampling Frequencies ------------------------------------------- Although the ADU-07e system is able to execute simultaneous measurements with different channels and different sampling frequencies one of the limitations of the system is, that all channels within a single measurement must use the same sampling frequency. Otherwise the recorded data cannot not be processed correctly in the “ProcessingQueue”. Therefore the ADU-07e system uses the following fallback strategy: for each channel it is checked, if the sampling frequency is supported by the ADB board considered and if already another sampling frequency is used by one of the ADB boards which are employed at the measurement. The following picture shall illustrate the behavior of the ADU-07e system. IMAGE Fallback strategy for sampling frequencies As you can see in Figure 18-1 the ADU-07e checks for each channel, which is configured in the measurement, whether the desired sampling frequency is supported by the ADB board. If this is not the case, it uses a fallback value for the sampling frequency. After these checks have been done for the first measurement channel, the sampling frequency, which was chosen for the first channel is used as the “master” sampling frequency for all other channels. Only those channels will be taken in the measurement job, if they can support this sampling frequency, too. Otherwise the measurement will be started without them. Every time an ADB channel cannot take attend the measurement due to no fitting sampling frequency could be found, a message is written to the “System History”, the “Error List” and even to the front panel display. **Information:** As you normally use the Web-interface to configure a measurement job, you will not be able to set different sampling frequencies for channels within one measurement. Nevertheless this case may occur, if you try to use LF and HF ADB boards within the same measurement. Fallback Strategy for Gains ---------------------------- If you use the ADU-07e Web-interface for configuration of measurement job, you will not be able to set up improper gain values for an ADB board, because the Web-interface only lets you select gains fitting to the type of ADB board installed. Nevertheless, you can directly manipulate the XML job files manually. In this case it may happen, that you selected gains not supported by the ADB boards. If this happens, the ADU-07e system automatically selects a fallback value for the gains and starts the measurement with the corrected gain value using the following strategy: IMAGE Fallback strategy for gains Similar as for the sampling frequencies, the ADU-07e system will create a message in the “Error List” and “System History” to illuminate this problem. However, the measurement will be started using the fallback values. In difference to erroneous settings of sampling frequencies, which can cause that certain channels cannot be employed in the measurement the invalid setting of gains will never exclude channels from taking part at the measurement. Fallback Strategy for Filters ----------------------------- For all ADB boards a list of more than one filter can be selected for a measurement job. As not all combinations of filters are allowed and as not all filters are supported by the different ADB boards, the ADU-07e system checks the filter settings at start of the measurement. For this purpose it uses the following strategy: IMAGE Figure 18-3: Fallback strategy for filters The ADU-07e system checks all the filters that are configured for the ADB board in a measurement. If the filter is supported by the ADB board, it will be activated for the measurement job. If it is not supported by the ADB board, the filter will not be activated. A special check is made for the ADU-07e-LF ADB boards, as these boards need at least one of the radio-filters (RF filters) activated. So if after checking all the configured filters none of the radio-filters is activated, the default radio-filter “ADU07\LF_RF_1” is activated in addition to the other filters. A list of all valid filters and their combinations can be seen in chapter 9.3.2. Fallback Strategy for Simultaneous Use of Calibration Module ------------------------------------------------------------- The calibration board can be used by different measurements in parallel. There is one limitation regarding the parallel use of the calibration board: all measurements have to use the calibration board in the same operating mode. It means that they have to use the calibration board with the same frequency of the calibration signal and with the same attenuation value. If two measurements should use the calibration board with different settings in parallel, the following fallback strategy is used: IMAGE Fallback strategy for simultaneous use of calibration board As you can see in Figure 18-4 the new measurement is always started, as long as there are no conflicts in the configuration of the calibration board. If there are conflicting settings for the calibration board parameters, the new measurement is not started. The ADU-07e system assumes the resulting measurement data wouldn’t make sense without the correct calibration signal. The conflicting use of the calibration board is the only case, where a measurement is not started, although the desired channels would be vacant for a new measurement. **Information:** The routings of the calibration signal (CalRef, CalInt, CalSensor) do not interfere with the settings of the calibration board. Due to that reason, even two parallel measurements may use the calibration board with a different routing, but the same settings for the cal board (switched on/off / sampling frequency / attenuation). Recording Bands of ADU-07e ------------------------------------------- The ADU-07e can record different bands. The table below shows the relationship between band, sample rate etc. The preferred bands are high-lighted .. csv-table:: Recording bands of ADU-07e :delim: | Band name|Sample frequency (Hz)|Digitally filtered|Highest recording frequency (Hz) HF512k|524,288|Hardw.|250,000 HF256k|262,144|Hardw.|120,000 HF128k|131,972|Hardw.|60,000 HF64k|65,536|Hardw.|30,000 HF32k|32,768|Hardw.|15,000 HF16k|16,384|Hardw.|7,500 HF8k|8,192|Hardw.|3,750 LF4k|4,096|Hardw.|1,400 LF2k|2,048|Hardw.|700 LF1k|1,024|Hardw.|350 LF512|512|Hardw.|200 LF256|256|Hardw.|100 LF128|128|Hardw.|50 DF64|64|Softw.|25 DF32|32|Softw.|12 DF16|16|Softw.|6 DF8|8|Softw.|3 DF4|4|Softw.|1.5 DF2|2|Softw.|0.8 DF1|1|Softw.|0.4 DF2s|½|Softw.|0.2 DF4s|¼|Softw.|0.1 DF8s|⅛|Softw.|0.05 **Note:** The variations of bands created by digital filters is multifold. Above you find only an example of configurations. Job Types ------------------------------------------- With the Web-interface, different “jobs” can be configured and started on the ADU-07e. These jobs are created as XML files, that contain their detailed description. Out of this information the ADU-07e system gets to know what it should do. After such a job is readily configured with the Web-interface, it is written into a “Scheduling list” within the ADU-07e system. The XML job description is evaluated here and the according job is performed if it is due. There are mainly three different job types that can be handled by the ADU-07e system: .. csv-table:: Job types for the ADU-07e system :delim: | Value Name|Description Measurement job|This is the job type mainly used. It describes a measurement in its XML content. It is configured via the Web-interface and afterwards added to the “Scheduling list” of the ADU-07e system. |From there it will be started at the programmed start-time of the measurement and then be executed. The file does not contain the pure information about start- and stop-time only, but also all information required to configure the measurement hardware (ADB boards / gains, filters, …). |Furthermore, it provides information about the post processing to be done with the recorded data. It can be either just writing the data to the CF-card, a digital filtering or the splitting of the incoming time series into time slices. |All running measurements inside the ADU-07e can be identified by a unique “Measurement Index”. This index is valid for the measurement, as long as this is running. By its knowledge, you can refer to the corresponding measurement, for example in the log messages, that are created by the ADU-07e system, or you can stop the job. Stop job|A stop job is written to the “Scheduling list” of the ADU-07e each time you want to stop a running measurement. For this purpose the Stop job just contains a list of measurement indexes of all the measurements to be stopped. PHP info job|This job is used by the Web-interface to execute actions in the ADU-07e system directly. It will not be used by you. Shutdown job|This job is used to shut down the ADU-07e system. After it is started, the ADU-07e will automatically stop all running measurements and afterwards stop the system. It is indicated by blink codes on the front panel LEDs and messages on the front panel display. ADU-07e Event Job|These jobs are used to control the “Sleep Mode” and “Event Handling” of the ADU-07e. Those can be configured by the user via the Web-interface. All these jobs and their structure are explicitly described in chapter 0 .File Formats File Format of Time Series \*.ATS ------------------------------------------- This chapter provides a description of the data format of the time series recorded with the ADU-07e. All time series files have a \*.ATS file extension. (ADU Time Series) The filename represents all the information about the measurement such as ADU serial number, sample frequency and so on. Example: IMAGE The ADU serial number and the sample frequency do not have a leading tag. All other parts of the filename have a leading tag like V, C, R etc. Tags are separated by an underscore character _. The \*.ats files consist of a1,024 bit header followed by the binary data. The binary data is organized in words of 32 bit signed integer. If you multiply the integer number by the LSB value given in the header information, you will get the value in mV. Each channel has its own .ats file. The organization of the header can be seen below as a structure in C language: .. code:: The ATS Header (advanced time series) descibes the first 1024 bytes of your time series file. Even though this header will be continued - the full information about your measurements can only be found inside the measdoc.xml document. This document includes the selftest data, calibraion data. #ifndef ATSHEADER80_DEF_H #define ATSHEADER80_DEF_H #include /*! @todo UTM Zone number UTM letter Tx times six double at least Tx base freq */ typedef struct ATSComments80_s { char achClient [16]; //!< 000 h char achContractor [16]; //!< 010 h char achArea [16]; //!< 020 h char achSurveyID [16]; //!< 030 h char achOperator [16]; //!< 040 h char achReserved [112]; //!< 050 h char achXmlHeader [64]; //!< 0C0 h char achComments [512]; //!< 100 h } C_ATSComments80; typedef struct ATSHeader80_s { qint16 siHeaderLength; //!< 000h qint16 siHeaderVers; //!< 002h // This information can be found in the ChannelTS datastructure quint32 iSamples; //!< 004h amount of samples (each is a 32bit int) in the file float rSampleFreq; //!< 008h sampling frequency in Hz quint32 uiStartDateTime; //!< 00Ch unix TIMESTAMP (changed to unsigned!) double dblLSBMV; //!< 010h qint32 iGMTOffset; //!< 018h float rOrigSampleFreq; //!< 01Ch sampling frequency in Hz as ORIGINALLY recorded; this value should NOT change (for example after filtering) //The required data could probably found in the HardwareConfig qint16 siADUSerNum; //!< 020h qint16 siADCSerNum; //!< 022h char byChanNo; //!< 024h char byChopper; //!< 025h Chopper On/Off // Data from XML Job-specification char abyChanType [2]; //!< 026h char abySensorType [6]; //!< 028h qint16 siSensorSerNum; //!< 02Eh float rPosX1; //!< 030h e.g South negative float rPosY1; //!< 034h e.g West negative float rPosZ1; //!< 038h e.g bottom float rPosX2; //!< 03Ch e.g.North positive float rPosY2; //!< 040h e.g.East positive float rPosZ2; //!< 044h e.g. top float rDipLength; //!< 048h e.g. to be calculated; should not be used float rAngle; //!< 04Ch e.g. to be calculated; should not be used // Data from Selftest ? float rProbeRes; //!< 050h float rDCOffset; //!< 054h float rPreGain; //!< 058h e.g. Gain Stage 1 float rPostGain; //!< 05Ch e.g. Gain Stage 2 // Data from status information ? qint32 iLatitude; //!< 060h qint32 iLongitude; //!< 064h qint32 iElevation; //!< 068h char byLatLongType; //!< 06Ch U, G user, GPS char byAddCoordType; //!< 06Dh U = UTM, G = Gauss Krueger qint16 siGaussRefMeridian; //!< 06Eh double dblHochwert; //!< 070h also xcoord double dblRechtswert; //!< 078h also ycoord char byGPSStat; //!< 080h char byGPSAccuracy; //!< 081h qint16 iUTCOffset; //!< 082h char abySystemType[12]; //!< 084h // Data from XML-Job specification char abySurveyHeaderName [12]; //!< 090h char abyMeasType [4]; //!< 09Ch //TODO[OKH] // Next three fields will not be supported any more. double DCOffsetCorrValue ; //!< 0A0h DAC offset double qint8 DCOffestCorrOn; //!< 0A8h DC offset was switched on (1) or off(0) qint8 InputDivOn; //!< 0A9h inputput divider on(1) off(0); e.g when coil was connected qint16 not_used_var; //!< 0AAh char abySelfTestResult [2]; //!< 0ACh char abyReserved5 [2]; //!< 0AEh //qint16 calentries // max 128 entries //TODO[OKH] // Were the following fields ever used ? qint16 siCalFreqs; //!< 0B0h qint16 siCalEntryLength; //!< 0B2h qint16 siCalVersion; //!< 0B4h qint16 siCalStartAddress; //!< 0B6h char abyLFFilters [8]; //!< 0B8h char abyADU06CalFilename [12]; //!< 0C0h qint32 iADUCalTimeDate; //!< 0CCh char abySensorCalFilename [12]; //!< 0D0h qint32 iSensorCalTimeDate; //!< 0DCh float rPowerlineFreq1; //!< 0E0h float rPowerlineFreq2; //!< 0E4h char abyHFFilters[8]; //!< 0E8h // Unused ? double OriginalLSBMV; //!< 0F0h orig lsb from selftest without gains; used for ADC values qint32 unsed_var; //!< 0F8h char abyADBBoardType[4]; //!< 0FCh LF HF or MF //!< Comes from XML-Job spec. C_ATSComments80 tscComment; //!< 100h } C_ATSHeader80; #endif // ATSHEADER80_DEF_H Figure 21-1: 1024 Byte Header of ATS-File All the time series files will be stored in a special directory. Usually, the recorded data is stored on the ADU-07e flash-disk or on a USB pen-drive if inserted to ADU and configured accordingly. It will be stored in a folder mtdata/data. Each recording run will be stored in a specific subfolder named with the date and time of recording: Example: meas_2007-08-15_15-51-45. The name of the subfolder is derived from the start date and time of the measurement. Here the start date was 15 Aug 2007 and start time was 15:51:45. File Format of Time Series “meas-doc” XML ----------------------------------------- In addition to the time series you will find an XML document containing all the relevant information about the measurements. It can be read with any ASCII text editor. The example below shows how such an XML file looks alike. .. code:: xml 09:25:23 09:55:23 2009-11-09 2009-11-09 /mtdata/data 0 60 seconds 1 256 0 0 0 0 16384.0 0 0 64 1024 512 1 1 ADU07_LF_RF_4 0 0 0 0 0 0 … … Example of an XML file created along with the recording. The file has been shortened and contains more information than shown here. As you can see in Figure 21-2 the first section describes the measurement itself. The configuration shown here may differ from the one you selected. This is due to all values, which have been changed by the ADU-07e system to their fallback values are updated. The XML file describes here the measurement as it was executed by the ADU-07e system. Attached to this file you will find several other XML files, like the ADU07HwConfig file. These files describe the current status of the system at the time, this measurement was executed. The files have the following content: .. csv-table:: Important values of the self-test :delim: | Name|Description ADU07HwConfig|It contains the type identification and serial numbers for all hardware components, that were installed into the system at the time this measurement was executed. ADU07HwStatus|It contains the current status with synchronization state, disk space, battery state and other values. ADU07Selftest|It contains the self-test results of the ADU-07e system that were detected at the last start-up of the system in advance to this measurement. Using this additional information you can determine the complete status and configuration of the ADU-07e system at the point in time of this measurement. File Format of Processing Instructions “process-doc” XML -------------------------------------------------------- The “process-doc” XML file is used by the “OpenMT” tool to process data recorded by an ADU-07e instrument. It contains a description of the “processing tree” that shall be used for the data processing. A detailed description is given inside the „OpenMT / ViewMT software manual“. File Format of Processing Results “edi-xml” XML ----------------------------------------------- The “edi-xml” XML file is used by the “OpenMT” tool to store the processed data to a disk or database. It is generally designed as an XML equivalent to the existing EDI file format. Up to now it contains the parzened “auto-/cross spectra” data for the processed time series. A detailed description of the file format is given inside the „OpenMT / ViewMT software manual“. Error Codes and Messages Created by the ADU-07e ------------------------------------------------------- The table below contains all the error and information messages that could be created by the ADU-07e. Please note that the entries in the column “Sub Index” refer to the numbers that are shown as “Init Error” or “ADB Error” in the “Selftest” page for example. In order to find the complete message according to these numbers you have to take a look on the corresponding component. E.g. for the “ADB Errors” you have to take a look on all messages of component “ADB”. .. csv-table:: List of messages, that are created by the ADU-07e system :delim: | Component|Main Index|Sub Index|Message|Description MCP|1|1|meas started incompletely: invalid job file|The new measurement job, that should be started, is erroneous. There are errors in the XML syntax or in the description of the configuration of hardware components. Please check your XML job file. MCP|1|2|meas started incompletely: out of memory|There is not enough system memory available to start a new measurement. Please stop other currently running measurements before trying to restart the measurement. MCP|1|3|meas started incompletely: ADB sync failed|The synchronization of the ADB boards failed. The recorded data of the individual ADB channels may be out of synchronization. This is a hardware problem. Please contact the Metronix support team. MCP|1|4|disk error: could not write to disk|The ADU-07e was not able to write to the CF-card or an attached USB stick. This may either happen, if you renamed or deleted ATS files for an active measurement, or there is no free disk space anymore. Please note, that the data series will possibly be corrupted from the time of occurrence of this message. MCP|1|5|meas stopped unexpectedly: meas data error|During recording the last data buffers that were received from the measurement hardware had unequal size for the different channels of the ADB boards. This may only happen, if a measurement stopped because it was either cancelled by you, it reached the "Start / Stop" fill level mark and was started in "Start / Stop mode" or it caused a buffer overflow on the SDRAM buffer on the measurement hardware. In all cases the last data buffer of the measurement (< 4 seconds of data series) may be corrupted. MCP|1|6|meas stopped unexpectedly: buffer full on backplane - data ok|A measurement was stopped because a buffer overflow occurred in the SDRAM buffer on the measurement hardware. This may be caused, because you made measurements with to high sampling frequency over too long time. MCP|1|7|stop time reached: still downloading data|Measurement finished as scheduled, but the system is still downloading data. This may happen if using high frequencies where the recorded data cannot be stored to disk in real time. If you want to start a measurement on the same channels while the data download has not finished yet, the new measurement will not be started. MCP|1|8|meas stopped unexpectedly: too early|A measurement stopped before it reached its desired stop time. This may not happen in normal operation and is an indication for a hardware problem. This issue should be examined together with the Metronix support team. MCP|1|9|meas stopped unexpectedly: MCP internal error|The message indicates a problem in the handling of the measurement data inside the ADU-07e. It shall not occur in normal operation and can not be fixed by you. Please call the Metronix support team. MCP|1|10|meas not started|This message says that a measurement could not be started by the ADU-07e system. Occurrence may have different reasons. One could be, that all the channels configured for the measurement, are still blocked by another measurement. A further reason could be an invalid hardware configuration fro the ADU-07e system. MCP|1|11|meas ended|This message indicates the stop of a running measurement. The measurement index of the measurement is appended to these messages. MCP|1|12|new meas started|Indicates the start of a new measurement. The measurement index, that this measurement will have during its lifetime is appended to this message. MCP|1|13|meas timed out|This message is created, if not all data of the measurement was received by the CPU board, before the stop time of the measurement was reached. The ADU-07e system will try to stop this measurement and read all lasting data from the SDRAM buffer on the measurement hardware. MCP|1|14|system initialization error: database|During start-up the control program on the ADU-07e could not connect to the MySQL database. This problem could be caused by a database crash, for example if the system was switched off without shutting it down correctly. The database has to be repaired. Please contact the Metronix support team. MCP|1|15|system initialization error: hardware|One of the hardware components could not be initialized correctly at start-up of the ADU-07e system. The name of the hardware component is attached to this message. Please check your hardware for errors. MCP|1|16|found new hardware|This message gives you the information, that a new hardware component was detected at start-up of the system. The name of the component is attached to this message. MCP|1|17|meas data error: unequal buffer size due to hardware error|After receiving the last samples of a measurement the size of the buffers for the different channels of a measurement are not equal. MCP|1|18|got data of idle channel|The CPU board reads samples for a channel that is not recording data. It indicates hardware problems or invalid configuration of the ADU-07e system. If this message occurs you must to wait until the backplane SDRAM buffer is empty again, before starting a new measurement. Otherwise the measurement data of the new measurement could be corrupted by old data of the last measurement. MCP|1|19|unexpected MCP state|This is a collective message for unexpected states in the ADU-07e control program. Please send the message with its attached information to the Metronix support team. MCP|1|20|meas started incompletely: inv. sample frequency|One of the channels that should take part in the new measurement should use a sampling frequency, that is not supported by the according ADB board. The ADU-07e system will choose a fallback value instead. MCP|1|21|data disk space smaller than 5MB|The free disk space on the data disk is smaller than 5 MByte. Please delete old measurement data or clear the "Error List" and "System History" to free up more disk space. MCP|1|22|system is booting|This message informs you that the ADU-07e is currently booting up MCP|1|23|selftest is active|Informs you, that the ADU-07e system is currently executing selftest measurements. Attached to this message you can find the step, that is actually executed. MCP|1|24|system is shutting down|This message informs you, that the ADU-07e is currently shutting down. MCP|1|25|system is sleeping|This message informs you, that the ADU-07e system is entering sleep mode. MCP|1|26|system is ready|This message informs you, that the ADU-07e system was completely booted up and is ready to execute the self-test procedure. MCP|1|27|system woke up|Informs you, that the ADU-07e system woke up from sleep mode. MCP|1|28|system sleep error|This message informs you, that an error has occurred when entering or leaving the sleep mode. MCP|1|29|meas started incompletely: some channels not available|This message says that some of the channels which should take part in the measurement are not available. This may happen, if they are either still blocked by another measurement or if they do not support the sampling frequency, that shall be used in the measurement. MCP|1|30|selftest result: |This message shows you the result of the self-test procedure. If it is OK, no problems occurred during self-test. If the result is "NOK", please examine the self-test results in the "Selftest" page of the Web-interface. At least for one of the hardware components the "Init Error" or "ADB Error" field should show a value different from 0. You will find the according message in this table in the line that fits to the component and Sub-index you find in the "Init Error" or "ADB Error" field. MCP|1|31|meas cancelled by user|This message informs you, that a running measurement was cancelled by the user. The measurement index of the measurement is attached to this message. MCP|1|32|meas stopped manually|informs you, that after having received the last samples of the measurement, the buffers were different in size. It happened, because you cancelled an ongoing measurement. Please note, that the last few seconds (t < 4 seconds) of the time series are lost to avoid corruption of the measurement data. MCP|1|33|OpenMT: socket interface could not be opened/created|This error occurs, if an OpenMT_Data-interface Processing Object was configured for the MCP Processing Queue and the socket connection could not be created/opened, using the port number configured in the XML job file. Maybe the port number is already in use or there is no valid TCP/IP interface. MCP|1|34|OpenMT: socket interface could not be closed/deleted|This error occurs, if the socket interface could not be closed. Normally, this should not happen. The socket with this port number will not be available anymore until the system is rebooted. MCP|1|35|OpenMT: error while sending data via socket interface|This error signalizes a problem while sending data on the socket interface to the client application. If this error occurs the data may be received incompletely at the receiver/client application. It may happen if for example the client application exits unexpectedly. MCP|1|36|OpenMT: local OpenMT client could not be started|This error occurs if you configured the OpenMT_Data-interface in a way, that a local OpenMT client should be started. By this means the data would be processed right on the local system. For some reason the client could not be started. It can happen for example, if the OpenMT executable is not located at "/mtdata/mcp_sys" or there are not enough system resources to start the client. MCP|1|37|OpenMT: local OpenMT client could not be stopped|The error occurs, if the local OpenMT client could not be stopped at the end of the measurement and may happen, if the OpenMT application already exited due to some reason, or if OpenMT hung up. In this case the OpenMT process must be killed manually before it can be started again. MCP|1|38|sleep mode activated|The user has activated the "Sleep Mode". The ADU-07e system will go asleep, if ever possible. This will set the CPU board to "Suspend To RAM" mode. While sleeping, the system is not accessible via the Web-interface anymore. MCP|1|39|sleep mode deactivated|The user has deactivated the "Sleep Mode". The ADU-07e system will not go asleep anymore. MCP_USB|2|1|USB communication timeout|This message notifies you that problems occurred in USB communication between the measurement hardware and the CPU board. It may either be caused by a missing USB connection between CPU board and measurement hardware or hardware problems on these components. Please check hardware. MCP_USB|2|2|USB driver error|This message tells that the control program has problems in connecting to the USB driver. The reason may be the same as in the prior message. Additionally, there can be problems with the Linux system. Please check your hardware. If everything is OK with the hardware, call the Metronix support team. MICRO|3|1|meas not started: hardware error|A measurement could not be started due to problems with the system’s hardware. Please check your hardware. MICRO|3|2|all meas stopped: buffer overflow - data corruption|A buffer overflow occurred on the measurement hardware. Therefore all measurements are stopped. MICRO|3|3|Backplane SW: GPS - buffer overflow|An internal buffer overflow occurred in the ADU-07e while accessing the GPS board. This may not happen in normal operation and points to a problem with the GPS board. Pleas contact the Metronix support team. MICRO|3|4|Backplane SW: GPS - no Linefeed in GPS sentence|This message occurs if the data from the GPS board is corrupt and may happen if the GPS board is defective or not attached correctly into the slot. MICRO|3|5|Backplane SW: GPS - Timeout in interface - ignore during boot or reset of GPS|This message occurs, if data from the GPS board is corrupt. It can happen, if the GPS board is defective or is not attached correctly into the slot. The message may occur once after start-up of the system. MICRO|3|6|Backplane SW: 5Volt supply fail|This message indicates that the 5Volt power supply on the measurement hardware failed. This is a hardware problem. The message may occur once after start-up of the system as at that time the power supply is not fully powered up. MICRO|3|7|Backplane SW: internal error|This is a collective message for the micro controller on the measurement hardware. Please send this message with its attached information to the Metronix support team. HW_MSG|4|1|battery voltage switched to FAIR|The battery voltage switched from GOOD to FAIR. HW_MSG|4|2|battery voltage switched to LOW|The battery voltage switched from FAIR to LOW. Battery power is now critical and the battery should be exchanged immediately. HW_MSG|4|3|battery voltage critical: shutting down|The critical battery voltage forced the ADU-07e system to shut down. This functionality is not implemented yet. HW_MSG|4|4|temperature over maximum: shutting down|The internal temperature exceeded the maximum value. The system is shutting down. This functionality is not implemented yet. HW_MSG|4|5|temperature below minimum: shutting down|The internal temperature exceeded the minimum value. The system is shutting down. This functionality is not implemented yet. GPS_MSG|5|1|GPS board not responding|This functionality is not implemented yet. GPS_MSG|5|2|unknown GPS board|During start-up of the ADU-07e system an invalid GPS board was found, that is not supported by the system. Please check you GPS hardware. GPS_MSG|5|3|GPS lost sync|The ADU-07e system lost the synchronization to the GPS signal. This means that the state switched from "G3fix - fully synced" to a lower state. GPS_MSG|5|4|GPS gained sync|The ADU-07e system gained a full sync to the GPS signal. If this happens, the ADU-07e system time is synchronized to the GPS time. Even if the system looses the sync afterwards, the system is still synchronized. GPS_MSG|5|5|GPS: no antenna connected|This functionality is not implemented yet. GPS_MSG|5|6|GPS: no satellites found|This functionality is not implemented yet. GPS_MSG|5|7|GPS: insufficient satellites for sync|This functionality is not implemented yet. GPS_MSG|5|8|GPS: no time synchronization|This functionality is not implemented yet. BACK_MAIN|6|1|main backplane not responding|The main backplane board could not be initialized. Pleas check your hardware. BACK_MAIN|6|2|unknown main backplane type|The ADU-07e system, found an invalid main backplane board that is not supported by the system. BACK_MAIN|6|3|main backplane could not be booted|The controller on the main backplane board could not be booted. This could be caused by an unknown hardware component. BACK_MAIN|6|4|status display not accessible|This functionality is not implemented yet. SUB_BACK|7|1|sub backplane not responding|The sub backplane board could not be initialized. Please check your hardware. SUB_BACK|7|2|unknown sub backplane type|The ADU-07e system, found an invalid sub backplane board that is not supported by the system. SUB_BACK|7|3|sub backplane could not be booted|The FPGA on the sub backplane board could not be booted. This could be caused by real hardware problems on the sub backplane board or an unknown sub backplane board. CAL|8|1|cal. board not responding|The calibration board could not be initialized. Please check your hardware. CAL|8|2|unknown cal. board|The ADU-07e system, found an invalid calibration board that is not supported by the system. ADB|9|1|ADB board not responding|The ADB board could not be initialized. Please check your hardware. ADB|9|1|unknown ADB type|The ADU-07e system, found an invalid ADB board that is not supported by the system. ADB|9|2|invalid ADB configuration|During the configuration phase for a new measurement the ADB board should be started with a configuration that is not supported by this ADB board. The measurement will be started using fallback values. The modified configuration is attached to this message. Please check your measurement configuration. ADB|9|3|ADU07-ADB-LF: internal DC offset failure|The internal DC offset on the ADB board is too high and can not be corrected. This points to a hardware problem of the ADB board in this channel. Please check the hardware for errors. ADB|9|4|ADU07-ADB-LF: internal gain correction error|The internal gain correction on the ADB board failed and is out of range. This indicates a hardware problem of the ADB board in this channel. Please check the hardware for errors. ADB|9|5|ADU07-ADB-LF: gain out of range 1:1|The gain for combination "gain stage 1 = 1", "gain stage 2 = 1" is out of range. This points to a hardware problem. Please check the self-test results for this step. ADB|9|6|ADU07-ADB-LF: gain out of range 8:8|The gain for combination "gain stage 1 = 8", "gain stage 2 = 8" is out of range. This points to a hardware problem. Please check the self-test results for this step. ADB|9|7|ADU07-ADB-LF: gain out of range 1:64|The gain for combination "gain stage 1 = 1", "gain stage 2 = 64" is out of range. This points to a hardware problem. Please check the self-test results for this step. ADB|9|8|ADU07-ADB-LF: gain out of range 64:1|The gain for combination "gain stage 1 = 64", "gain stage 2 = 1" is out of range. This points to a hardware problem. Please check the self-test results for this step. ADB|9|9|ADU07-ADB-LF: external offset correction error|The external offset correction on the LF ADB board failed. This indicates a hardware problem with the offset correction DAC on the ADB board. Please check the hardware. ADB|9|10|ADU07-ADB-LF: 4Hz low pass filter error|The attenuation of the 4 Hz low pass filter on the LF ADB board is out of range. This points to hardware problems with the 4 Hz LP filter on the ADB board. Please check the hardware. ADB|9|11|ADU07-ADB-LF: noise out of range|The noise on the sensor input is out of range. Please activate the 4 Hz low pass filter for noise reduction, if possible and check the sensor connection. ADB|9|12|ADU07-ADB-LF: DC level too high for gain|The DC level on the sensor input is too high for an amplification. Therefore, do not use gain stages different then 1:1. Otherwise the input signal will exceed the maximum dynamic range of the channel and the measurement data will be useless. ADB|9|13|ADU07-ADB-HF: internal DC offset failure|The internal DC offset on the ADB board is too high and can not be corrected. This points to a hardware problem with the ADB board in this channel. Please check the hardware for errors. ADB|9|14|ADU07-ADB-HF: internal gain correction error|The internal gain correction on the ADB board failed and is out of range. This points to a hardware problem with the ADB board in this channel. Please check the hardware for errors. ADB|9|15|ADU07-ADB-HF: gain out of range 1:1|The gain value for combination "gain stage 1 = 1", "gain stage 2 = 1" is out of range. Indicates a possible hardware problem. Please check the self-test results for this step. ADB|9|16|ADU07-ADB-HF: gain out of range 8:8|The gain for combination "gain stage 1 = 8", "gain stage 2 = 8" is out of range. Indicates a possible hardware problem. Please check the self-test results for this step. ADB|9|17|ADU07-ADB-HF: gain out of range 1:64|The gain for combination "gain stage 1 = 1", "gain stage 2 = 64" is out of range. Indicates a possible hardware problem. Please check the self-test results for this step. ADB|9|18|ADU07-ADB-HF: gain out of range 64:1|The gain for combination "gain stage 1 = 64", "gain stage 2 = 1" is out of range. Indicates a possible hardware problem. Please check the self-test results for this step. ADB|9|19|ADU07-ADB-HF: 1Hz high pass filter error|The attenuation of the 1 Hz high-pass filter on the LF ADB board is out of range. This points to hardware problems with the 1 Hz HP filter on the ADB board. Please check the hardware. ADB|9|20|ADU07-ADB-HF: noise out of range|The noise on the sensor input is out of range. Please check the sensor connection. ADB|9|21|ADU07-ADB-HF: DC level too high for gain|The DC level on the sensor input is too high for amplification. Therefore do not use the gain stages different from 1:1. Otherwise, the input signal may exceed the maximum dynamic range of the channel and the measurement data will be useless. ADB|9|22|ADU07-ADB-COMMON: sync failed|The synchronization of the single ADB boards in advance to a measurement failed. Therefore, the single channels of the measurement may jitter by the t = 1/Sample Frequency. This may be a hardware problem. Please check the ADB board for errors. GPS_STATUS|10|1|GPS status report|This message shows a GPS status report containing the actual position, time and the synchronization status. HW_STATUS|11|1|HW status report|This message shows a hardware status report containing the actual battery voltage, current and status and other values. GLOBAL|12|1|unknown system identity|This message says, that the measurement contains an invalid system identity that is not supported. Please check your hardware. USB_AUTO-MOUNTER|13|1|USB: scanning device|This message tells that a new USB mass storage device was attached and is scanned by the USB Auto-mounter. The USB Auto-mounter will try to mount the device to its target directory and then start any job-lists, if configured. USB_AUTO-MOUNTER|13|2|USB: mounting device|The device is mounted to the configured target directory. USB_AUTO-MOUNTER|13|3|USB: starting job|The job of the job-list was started. USB_AUTO-MOUNTER|13|4|USB: mounting of device failed !|It was tried to mount the device to its target directory and it failed. Maybe the configured target directory inside the "ADU07Conf" XML file is invalid. Please check the configuration file. USB_AUTO-MOUNTER|13|5|USB: start of job failed|It was tried to start the XML job. This failed. The reason may be that there is no valid XML job file at the location specified in the ADU07Conf XML file. USB_AUTO-MOUNTER|13|6|USB: scanning of device failed|The newly attached USB device was tried to be scanned by the USB Auto-mounter. This failed. The reason can be that there was no preconfigured directory structure or no valid ADU07Conf XML file. USB_AUTO-MOUNTER|13|7|USB: device was detached|An attached USB device was detached again. USB_AUTO-MOUNTER|13|8|USB: job-list transferred completely|All jobs of a job-list from a USB device have been transferred completely to the "jobs" table. CON|14|1|connector not responding|The connector board could not be initialized. Please check your hardware. If you have an ADU-07e system with old, revision 1.0 connector board this is no problem (Revision 2.0 available since ADU-07e). CON|14|2|unknown connector type|The ADU-07e system, found an invalid connector board that is not supported by the system. SENSOR|15|1|no plug and play sensor found|The sensor on the specific input could not be initialized. Please check your hardware. If there is no MFS-06e, MFS-07e or EFD-07e sensor connected, this message is no problem. SENSOR|15|2|unknown sensor type|The ADU-07e system, found an invalid connector board that is not supported by the system. SENSOR|15|3|invalid XML cal file|The ADU-07e system found a new, intelligent sensor but was unable to read the sensor’s XML cal file from ii. This may either be caused by the XML cal file being broken, or by the sensor not having an XML cal file stored inside its EEPROM at all. This is kind of critical. The sensor will operate properly. If you want to recalibrate the sensor, please contact the Metronix support team. SENSOR|15|4|read XML cal file from sensor|The ADU-07e system, found a new, intelligent sensor and successfully read an XML cal file from its internal EEPROM. The file is stored inside the local database and will be used for all further measurements along with this sensor. USER|16|1|user msg.: |This is a user specific message. It is not created by the ADU-07e system, but by the customer who configured the system. Trouble Shooting ------------------------------------------- This chapter describes our experience to localize possible errors of the system and methods how to fix them or get around of it. System Self-test ----------------- As soon as the ADU-07e is connected to power, it will perform an automatic self-test incl. measurement of the resistance of the E-field lines. A) The system is booting the operating system. During this time the front panel display and the LEDs are not active. Also no Web access will be possible. This situation can last up to two minutes. B) After its booting, the system can be accessed via network and SSH. C) The driver for USB interface and FPGA is loaded then. D) The Web-Interface becomes active after the self-test is started which is indicated by the 3 blinking LEDs. E) The self-test procedure itself consists of several self-test steps. These steps have the following meaning: .. csv-table:: Self-test default values :delim: | Step Nr.|Short Name|Description|Mandatory 1|Start self-test|This self-test step sets the ADU-07e system into the “Selftest” operation mode. This is signalized by the front panel LED lights blinking. In this operation mode, no jobs are started except those of the self-test itself. The system is set back to “normal operation mode”, once the “Stop Self-test” step has been executed.|Yes 2|LF internal offset calibration - 1|This self-test step along with the “LF internal offset calibration - 2” step is used to eliminate any DC offset in the LF ADB board internal ADC circuitry.|Yes 3|LF internal offset calibration - 2|See “Step 2 / LF internal offset calibration - 1”|Yes 4|LF LSB detection|This self-test step is used to compute the correct value for the “Least Significant Bit” (LSB) of the LF ADC converters. The LSB gives the factor in “mV” to convert the raw ADC converter data values into real voltage values.|Yes 5|LF gain correction|This self-test step will calibrate the gain stages of the LF board.|Yes 6|LF gain test 1:1|This step will check the gain stages on the LF board. It will feed in a calibration signal from the “Calibration Board” and check whether the measured value is within the tolerance window. The gain setting used is 1:1 (Gain Stage 1 = 1 / Gain Stage 2 = 1). If this step fails, the gain stages on the LF ADB board must be checked.|No 7|LF gain test 8:8|See step “LF gain test 1:1”, but using a gain of 8:8 (Gain Stage 1 = 8 / Gain Stage 2 = 8).|No 8|LF gain test 1:64|See step “LF gain test 1:1”, but using a gain of 1:64 (Gain Stage 1 = 1 / Gain Stage 2 = 64).|No 9|LF gain test 64:1|See step “LF gain test 1:1”  not used |No 10|LF DC offset compensation|This self-test step is used to check the “DC offset compensation” hardware on the LF ADB board. This “offset compensation DAC” can be used to compensate DC offset voltage on the sensor input signal. In this test, a defined compensation voltage is configured and the resulting voltage value is measured. This way the ADU-07e may check, if the hardware is working correctly.|No 11|LF DC offset|This self-test step will measure the “DC offset” voltage on the sensor input. If the DC offset voltage exceeds a value of 150.0 mV a warning message is created that informs the user, that no gains should be used because otherwise the LF ADC will be overdriven.|No, but useful for configuring ADU-07e 12|LF 4Hz low pass filter check|This step is used to check, if the 4Hz low pass filter hardware is working correctly on the LF ADB board.|No 13|LF Probe Resistance|This step is used to determine the resistance on the sensor inputs. This is only useful for the E-field channels, as it gives an indication about the conductivity of the E-field probes to the Ground.|No, but useful for configuring ADU-07e 14|LF Sensor Input Noise|This step is performed to determine the maximum noise amplitude on the sensor inputs. This is an indicator for the maximum usable gain.|No, but useful for configuring ADU-07e 15|HF internal offset calibration - 1|This self-test step along with the “HF internal offset calibration - 2” step is used to eliminate any DC offset in the HF ADB board internal ADC circuitry.|Yes 16|HF internal offset calibration - 2|See “Step 2 / HF internal offset calibration - 1”|Yes 17|HF LSB detection|This self-test step is used to compute the correct value for the “Least Significant Bit” (LSB) of the HF ADC converters. The LSB gives the factor in “mV” to convert the raw ADC converter data values into real voltage values.|Yes 18|HF gain correction|This self-test step will calibrate the gain stages of the HF board.|Yes 19|HF gain test 1:1|This step will check the gain stages on the HF board. It will feed in a calibration signal from the “Calibration Board” and check whether the measured value is within the tolerance window. It uses a gain setting of 1:1 (Gain Stage 1 = 1 / Gain Stage 2 = 1). If this step fails, the gain stages on the HF ADB board must be checked.|No 20|HF gain test 8:8|See step “HF gain test 1:1”, but using a gain of 8:8 (Gain Stage 1 = 8 / Gain Stage 2 = 8).|No 21|HF gain test 1:64|See step “HF gain test 1:1”, but using a gain of 1:64 (Gain Stage 1 = 1 / Gain Stage 2 = 64).|No 22|HF 1Hz high pass filter check|This step is used to check, if the 1Hz high pass filter hardware is working correctly on the HF ADB board.|No 23|HF DC offset|This self-test step will measure the “DC offset” voltage on the sensor input. If the DC offset voltage exceeds a value of 150.0 mV a warning message is created that informs the user, that no gains should be used as otherwise the HF ADC will be overdriven.|No, but useful for configuring ADU-07e 24|HF Probe Resistance|This step is used to determine the resistance on the sensor inputs. This is only useful for the E-field channels, as here it gives an indication about the conductivity of the E-field probes to the Ground.|No, but useful for configuring ADU-07e 25|HF Sensor Input Noise|This step is used to determine the maximum noise amplitude on the sensor inputs. It is an indicator for the maximum usable gain.|No, but useful for configuring ADU-07e 26|Stop selftest|This step will stop the self-test procedure and set the ADU-07e system back to the normal operation mode. This is indicated by the front-panel LED lights not blinking anymore. Now the system will accept new jobs from the “jobs” table again.|Yes As it can be seen in the table above, only very few of the self-test steps are mandatory and need to be executed each and every time the system is starting up. Therefore, you can select either a “Short” or a “Full” self-test to be executed during system start-up. The two self-test versions have the following parameters: * **Short Self-test** → only the “mandatory” steps are executed. The system is fully operational afterwards, but no further tests of the internal hardware are carried out. It is recommended for applications when the system is powered on/off very often. The “Full” self-test should be done every few days or maybe at the begin and at the end of a survey at least every few weeks. In many cases the “Short” self-test is sufficient. → duration: approximately 10 minutes * **Full Self-test** → all self-test steps will be executed and it is the default configuration for the self-test procedure. It tests all internal hardware components for correct operation. In case the system is run in LF or observatory mode (powered up only once every few days), this is the desired configuration for the self-test. → duration: approximately 17 minutes The results of the self-test are stored in a database and can be displayed on the laptop. The table displayed below shows the results of such a self-test and their default / limit values. IMAGE Self-test results in ADU-07e Web-interface The self-test was executed without any problems, if the lines in the table “Init Error” and “ADB Error” show the value 0 for all the components. Additionally, in the status display located on the front panel gives the information whether the self-test result is ok (“OK”) or not (“NOK”). See the following table for the default values: .. csv-table:: Self-test default values :delim: | Name|Description|Default value Init Error|If this value is not 0, the initialization of the corresponding hardware component has failed. Please take a look at the system history and hardware configuration for additional information.|0 ADB Error|If this value is not 0, one or more of the self-test steps for the ADB board test failed. Please take a look at the according message in chapter 19. The main index (component) is always 9 (ADB).|0 DC Offset|This value shows the DC offset on the sensor input in Volt.|0 V Max. Amplitude|This value shows the maximum amplitude on the sensor input in Volt.|0 V Gain Amplitude|\-|1 HF LSB|This value shows the determined LSB value for the HF ADB boards in mV.|0,00060 mV LF LSB|This value shows the determined LSB value for the LF ADB boards in mV.|0,00045 mV HF Internal Offset|This value shows the internal ADC offset in increments. You may get the voltage value by multiplying this value with the LSB valence.|+/- 300 increments LF Internal Offset|Shows the internal ADC offset in increments. You may get the voltage value by multiplying this value with the LSB valence.|+/- 300 increments Gain Correction|Shows the internal ADC gain correction value.|1 Gain Test 1:1|Shows the test results for a Gain 1:1 test measurement.|0,024752 mV Gain Test 8:8|Shows the test results for a Gain 8:8 test measurement.|1,584200 mV Gain Test 1:64|Shows the test results for a Gain 1:64 test measurement.|1,584200 mV Gain Test 64:1|This value shows the test results for a Gain 64:1 test measurement.|1,584200 mV Ext. Offset DAC|This value shows the test result for the external Offset compensation DAC. It is only valid for LF ADB boards.|1 V +/- 0,01 V Attenuation ADU07_LF_LP_4HZ|This value shows the attenuation of the ADU07_LF_LP_4HZ low pass filter of the LF ADB board. This value is only valid for LF ADB boards.|0,7072 +/- 0,2 Attenuation ADU07_HF_HP_1HZ|This value shows the attenuation of the ADU07_HF_HP_1HZ high pass filter of the HF ADB board. This value is only valid for HF ADB boards.|0,7072 +/- 0,2 Resistivity|This value shows the probe resistance.|\- ADU Does Not Boot Properly -------------------------- If the ADU-07e is switched on, it boots up automatically and performs a self-test. After having switched-on the power, the status display will show a message after some 30 seconds and inform about the progress. In case you do not see any message on the status display even after a long time, this can indicate a hardware error. However, before entering the trouble shooting procedure, first check the voltage of the attached battery. If the battery is ok, there are various possibilities which can cause such a behavior of the instrument. One of them could be excluded quickly by using a new compact flash card to boot the system. Just open the 10 screws of the front panel and replace the flash card by the spare which was delivered along with the ADU-07e. The flash card is located on the left side. **Information:** Please consider that the default address of the spare flash card is 192.168.0.22. It can be changed to another number as described in chapter 14.4. Even if the front panel display does not show any reaction it might be possible to access the ADU via SSH protocol. A description how this can be achieved is described in chapter 14. If you get access to the CPU board this also indicates that the 5V power supply is ok. Bad Results in E-Channel ------------------------ If you find jumps in the time series of the electric field channel, you should check at first the electric field probe´s connection with the soil. The probe must sit firmly in the soil which also should be sufficiently wet. Add water if necessary. It may take some time (some hours) until the probe potential settles properly for long period measurement. It is recommended not to start long period measurements immediately after having set up the station. It is also important to check the connections of the E-field wire to the probe and to the instrument. The best way is to clamp the non-insulated wire of the probe and the cable directly under the connector of cable drum and instrument and fix it tightly. **Information:** A check of the probe resistance in the self test data may also help to detect bad contacts. The resistance should be as low as possible (<5kOhms). In conductive soil a probe resistance of 500 Ohms and less can be achieved. Bad Results in H-Channel ------------------------ If the magnetic field data shows strange behavior (jumps or oscillations) this could be caused by a sensor which has not been dug in properly. It is very important that the magnetometer is dug into the soil in order to prevent it from micro vibrations caused by wind. Also cables shaking in the wind have a bad influence. They must be fixed firmly near the sensor (at least the first meter) by fixing it with stones or some soil. The vertical component often has the smallest signal but is exposed to wind influence more than the horizontal magnetometers. The use of a plastic bucket which covers the top of the vertical sensor helps to minimize wind influence. A defective cable or connector may also cause problems. If you observe a strange behavior in a magnetic channel exchange the cable first. Self-test Values of all Channels Look Odd ----------------------------------------- The ADU-07e uses a test signal which is generated on the calibration board. During the automatic self-test after power up, these signals are used extensively to check the ADU-07e. The test signals are also sent to the sensors and in case a sensor cable is damaged and has a short circuit of the test signal against ground or a signal line this can dramatically influence the self-test results of all channels. In case you observe such behavior in the field you should at first disconnect all sensor cables and redo the self-test. In case the results look ok then, it is very likely that one or more sensor cables is/are damaged. You can find the bad one by plugging in the cables one after another and repeat the self-test several times. As soon as the error occurs again you have found the defective cable. You can speed up the procedure by selecting “short selftest” in the selftest configuration menu. Parallel Sensor Test -------------------- In order to check the functionality of the sensors it is a good idea to perform a so called parallel sensor test. For this purpose the 3 magnetometers are positioned horizontally and in parallel with a distance of about 2 m from each other. The electric field lines are laid out in parallel perpendicular to the magnetic sensors. Use a single probe for each line (all together four of them). Now you record time series. If everything works fine you must see well correlated time series of the electric and the magnetic channels. A noisy sensor can be found out by this method easily. Determination of Correct Gain Setting ------------------------------------- The ADU-07e has an input range of +/-1.25V at the E-field inputs and +/-10V on the H-field input. The multi-purpose socket (input 2) has an input voltage range of +/-1.25 for all 5 channels. The ADU-07e offers many different gain settings for each channel. At the ADU-07e the setting of the input sensitivity can be done by software for all 10 channels. If the correct sensor type is entered, the ADU will automatically set the correct attenuation of the input. **Manual Gain Setting** As a rule of thumb you should select the gain as large as possible with a reserve of factor 10 to the max. allowed input value. Check at a sampling rate of 1024 Hz and a gain of 1 what the max. positive and negative amplitude is. Now you can calculate the max. possible gain setting respecting the reserve of factor 5 for each channel. **Information:** It is important that all sensors are properly connected before setting the gains! Replacement of ADB-Board ------------------------ If an ADB-Board has failed in the self-test or seems to be faulty by other means it can be replaced by a spare board of the same type. The following section describes this procedure. * Loosen the 10 screws holding the front panel of the ADU. * Lift up the right side of the front panel and remove the 60 pole and the 8 pole ribbon cables from the board under the front panel. * Now flip the front-panel upright to 90° angle against the casing. * Unplug the network cable from the network socket if required * Now you can turn the front panel upside down aside the ADU case * Remove the 4 screws which hold the larger aluminum plate of the ADB board housing. * Unplug the board you want to exchange * Re-plug the new ADB-board into the slot * Now you may reassemble everything in the reverse order The new ADB-board and its parameters will be automatically detected by the software. IMAGE IMAGE IMAGE Replacement of ADB-Board The following picture shows the assignment of the slots to the channel number: IMAGE IMAGE Assignment of ADB-Board slots to the channels **Measurement of the Power-Supply Voltages** The power-supply voltages can be measured without need to open the ADU as follows: The + 12V and –12V for sensor supply can be measured on one of the magnetometer sockets of the ADU (see Figure 11-2 for the pin-out). You may use the grounding terminal to plug in the – cable of your multi-meter. The 3.3V digital supply can be measured on the GPS antenna socket. Case is –pole and center pin is +pole. There is also a +5V power supply voltage which can only be accessed internally. **Information:** Note, that Sensor-GND and DGND are not connected to each other. Solving Network Communication Problems -------------------------------------- Make sure that the network properties are set up correctly: No proxy-server shall be selected. Select direct access in the TCP/IP section of the network properties instead. The network settings on your operating system must be set in a way that the computer and the ADU-07e are working within the same address range i.g. 192.168.0.xxx. and a subnet mask is set to 255.255.255.0. If you want to access via the built-in W-LAN you have to select an address range of 192.168.10.xxx instead. The number selected in the PC network settings may not be the same as the ADU-07e network number. Check whether you get a response on a ping sent to the ADU’s network address. For that purpose you open a command window and type in .. code:: ping If you still do not get a communication between laptop and ADU you may check the network cable with an Ohm-meter. If your laptop does not support Gigabit network interface it is important that you use a crosslink network cable. If the network cable is ok, you may check the adapter of your laptop computer whether it has been setup properly and whether it is initialized. It may be important that you firstly connect the adaptor to the laptop and the network and then switch on the laptop (in case of automatic switch off of the network board in the laptop in case power-saving is activated). Many Ethernet adapters on laptops have a lamp (LED) to indicate what is going on. A clear sign that an adapter has not been initialized properly is that no activity is visible on the adapter’s LED. The last possibility that should be checked is whether the network section of the ADU’s CPU board has a failure. In this case it needs to be replaced by a new one. **Information:** Note, that the maximum cable length of the network cable with 10BaseT without repeater is defined to 100m by Ethernet standard. Check of Magnetometer Cable --------------------------- The pin-out of the magnetometer cable is given in chapter 11. Check the cable by using an Ohm-meter pin by pin according to the pinout table. Also check for damages of the cable’s isolation. Measurement of ADU-07e Self-Noise --------------------------------- This chapter describes how the self-noise of the ADU-07e can be tested. Select the switch “Shortcut” in the recording parameter settings and select a gain. Now you start a recording in the band of interest. After having performed the recording you should display the stacked spectra of this recording and compare it with the figures given below. **Information:** The displayed noise values are all referenced to the input of the ADU-07e. Setting a higher gain will usually lower the noise values. IMAGE Noise Spectra of ADU-07e LF-channels. Gain 1, 1, f\ :sub:`sample`\ =2,048Hz IMAGE Noise Spectra of ADU-07e LF-channels. Gain 8 8, f\ :sub:`sample`\ =2,048Hz IMAGE Noise Spectra of ADU-07e HF-channels. Gain 1, 1, f\ :sub:`sample` = 65,536 Hz IMAGE Noise Spectra of ADU-07e HF-channels. Gain 8, 8, f\ :sub:`sample` = 65,536 Hz Feeding-in a Test Signal to the Sensors --------------------------------------- In the following figures it is shown how a typical response to a test signal which is fed into the sensor´s calibration coil looks alike. Referring to the Manual of the MFS-06 sensor the calibration sensitivity of the MFS-06 is defined to :math:`\\k \rightleftharpoons = 4\frac{\text{nT}}{V}` The sensitivity of the sensor at frequencies >> 4 Hz is defined to 0.8 V/nT. The test signal has an amplitude of +/- 312.5mV square wave (Attenuation 8 was selected). If you feed-in this test signal of 32 Hz and record with 2048Hz sampling rate you will see a curve as shown below. The amplitude displayed will be 0.25V peak to peak (actually, the sensor generates a signal of 4nT/V\*.625Vpp\*.8nT/V=2Vpp). Due to the voltage divider 1:8 on the backplane the displayed signal is 0.25Vpp.The slight decays are caused because 32 Hz is not too far away from 4 Hz which is the feed-back cut-off frequency of the sensor. In the non-feed-back range of the sensor (<< 4Hz) you will see positive and negative spikes instead of the square waves (the sensor differentiates the input signal). Their amplitude depends on the frequency also. IMAGE Example of 32 Hz test signal fed into the MFS-06 sensor Solving GPS Problems -------------------- In case you cannot see a sufficient number of satellites or even no satellites at all this can have several reasons: a) Your GPS antenna doesn’t have a free view to the sky. This can be due to trees with wet leaves, buildings etc. In this case the system needs to be moved to a better location. b) The distance between the location where you had the last fix and the new site is long (>300km). Then it is necessary to wait a longer time because the system has to load a new almanac. This information is only sent every 12.5 minutes. So it takes much longer than usual to get a fix. It can be necessary to select GPS cold Boot on the status display and reboot the system in case that even after 20 minutes no fix could be achieved. c) The antenna might have a problem. Check the resistance of the antenna with an Ohm meter (life against GND). It should be around 70 Ohm (older antennas 240 Ohm). Replace the antenna if required or repair the connection when faulty. d) The internal wiring of the ADU-07e has a problem. Check whether you can measure 3.3V at the GPS socket. The system must be powered. e) When it always takes a long time to get a fix even under ideal conditions it could be that the battery on the GPS module is down. In this case the ADU has to be opened and the GPS module removed. Measure the battery voltage. It should be 3V. If too low, change the battery on the module by a suitable replacement 3V Lithium cell (CR3032). f) If none of the hints given above helps to solve the problem, an exchange of the clock board may be considered. The clock board´s location can easily be traced following the black antenna cable. Unscrew the lid and pull out the clock board.