.. _adu-08e: .. |br| raw:: html
ADU-08e ============ Introduction ------------ Performance Characteristics ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The ADU-08e (Analog Digital Unit) is the core unit of the metronix multi-channel Geophysical Measurement System GMS-08. It is the result of more than 40 years of metronix´ experience in the design and manufacture of electromagnetic geophysical instruments. The ADU-08e can be equipped with up to 6 measurement channels (5 + one internal wired). The standard configuration for wide band MT and AMT consists of 5 broad band (HF+LF combined on one board) channels. The type of channel-boards which are plugged-in will be detected by the system automatically. Multiple ADU-08e 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) using GigaBit Ethernet, 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 also possible. The ADU-08e 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 6 channels, 24(HF)/32(LF) Bit A/D conversion and data storage as well as a very precise GPS controlled time base (using GPS and GLONASS). Data is stored on a removable SD card or on a USB pen drive orexternal USB hard-disk or, via the network, on the hard-disk of the connected control computer. Either the single ADU-08e 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 and aduclient software(Linux, Mac, Windows, Andoid). All metronix magnetometers like MFS-05, MFS-06(e), MFS-07(e), FGS-02, FGS-03e, SHFT-02(e) can be connected directly to the ADU-08e. It is also possible to connect magnetometers from other companies on option. The GMS-08 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 (HF) and 32 Bit (LF) 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 from 256Hz up to 524kHz * System can be operated as a stand-alone or as a multi-channel network system when connecting multiple ADU-08e in a Local Area Network (LAN). An integrated W-LAN module is now standard. * ADU-08e is controlled by any Web-browser without need of further software * ADU-08e is controlled by mobile phone or tablet (adu client software) * Multiple stand-alone systems are synchronized with GPS clock accuracy. * Compatible with all metronix sensors. * Automatic unattended recording mode, pre-configured job-lists * 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, MFS-10e, SHFT-02e, FGS-03e and future sensors) * Automated system self-check of ADU-08e 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-08e incl. sensors. * Compact, light-weight, ruggedized and water-protected instrument design. * Low power consumption * Wide operating temperature range from -30°C to +60°C ambient temperature. * Multiple methods such as MT, AMT, EMAP, RMT, CSAMT Technical Data ^^^^^^^^^^^^^^^^^ .. csv-table:: :delim: | Frequency range|DC to 524.288 kHz| Number of channels|5 (standard) expandable to 6 | Native sample rates of A/D converter|256 Hz to 524.288 kHz selectable by power of 2| |(lower sampling rates by on-line digital filtering)| A/D conversion |LF: 32 Bit (data rate max. 4,096 samples/sec)| |HF: 24 Bit (data rate max 262,144 samples/sec)| |One A/D conversion unit for each channel| Input noise|LF-ADB: 12 nV/√Hz @ 0.1 < f < 2 kHz and gain 16| |Ultra low noise mode LF: 6 nV/√Hz @gain 64| |HF-ADB: 13 nV/√Hz @ f >1kHz and gain 16| Input resistance |>10 MΩ| 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 (4 CPU cores)| Storage media|32 - 512 GByte SD card (4 TB on external USB disk with ext4), 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|GBit Ethernet with RJ45 connector, external WiFi module| Synchronization|72 channels GNSS synchronized clock, accuracy +/-30ns rms accuracy of 1pps signal, station position is also determined and stored (GPS, Glonass, BeiDou, Galileo)| Standard connectors for 5 channel system|1 x Network RJ45 ruggedized socket(s) | |3 x Magnetometer 10-pole | |4 x E-field input terminal 6-pole | |1 x GND terminal| |2 x input terminals for 12V battery protected against reverse polarity | |1 x ext. satellite antenna MCA-Type socket, | |2 x USB2.0 Type A | Status Display|5 lines with 64 alpha numeric characters for display of status information and direct parameter entry| Case|ruggedized, water-resistant case | Weight|appr. 6.2 kg| External dimensions|406*330*174 mm3| Power Input|9V … 15V DC| Power consumption |5.5W – 15W | |depending on operation mode| Operating temperature range|-30°C to + 60°C | *The system is protected against over voltage; around 16.xx V it should switch off.* |br| *All components inside the system are industrial (-40°C .. +85°C) grade with the CPUs on the ADB and Clock/GPS even ranging up to 125°C.* *Lightning protection is up to 1200V, fuses can be exchanged. Above the system will be seriously damaged* Error Messages ^^^^^^^^^^^^^^ .. csv-table:: :delim: | Component|MainIndex|SubIndex|Priority|Message|DisplayMsg.|Description MCP|1|1|e|meas started incompletely: invalid job file|Start failed: Invalid job|The new measurement job, that should be started, is erroneous. There are errors in the XML syntax or the description of the configuration of the hardware components. Please check your XML job file. MCP|1|2|e|meas started incompletely: out of memory|Start failed: 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|e|meas started incompletely: ADB sync failed|Start failed: ADB Sync failed|The synchronisation of the ADB boards failed. The recorded data of the single ADB channels may be out of synchronisation. This is a hardware problem. Please contact the Metronix support team. MCP|1|4|e|disk error: could not write to disk|disk error: could not writeto disk|The ADU-07 system, was not able to write to the CF-card or 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|e|meas stopped unexpectedly: meas data error|Unexpect. stop:Measurement data invalid|During recording of data 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|e|meas stopped unexpectedly: buffer full on backplane - data ok|Unexpect. stop:Buffer full on backplane - 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|i|stop time reached: still downloading data|Stop time reached: Still downloading|"Measurement finished as scheduled, but the system is still downloading data. This may happen if using high frequencies where the recorded can not be stored to disk in time. If you want to start a measurement on the same channels while the data download is not finished, the new measurement will not be started." MCP|1|8|e|meas stopped unexpectedly: too early|Unexpect. stop: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 should be examined together with the Metronix support team. MCP|1|9|e|meas stopped unexpectedly: MCP internal error|Unexpect. stop:MCP internal error|This message indicates a problem in the handling of the measurement data in the ADU-07 system. This shall not occur in normal operation and can not be fixed by you. Please call the Metronix support team. MCP|1|10|e|meas not started|Start failed: Measurement notstarted|This message says, that a measurement could not be started by the ADU-07 system. This may have different reasons. One could be, that all the channels, that are configured for the measurement, are still blocked by another measurement. Another reason could be an invalid hardware configuration fro the ADU-07 system. MCP|1|11|i|meas ended|Meas. completedcorrectly|This message indicates the stop of a running measurement. The measurement index of the measurement is appended to this messages. MCP|1|12|i|new meas started|Meas. started|This message indicated 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|i|meas timed out|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-07 system will try to stop this measurement and read all lasting data from the SDRAM buffer on the measurement hardware. MCP|1|14|e|system initialisation error: database|Init error: Database error|At start-up of the system the control program on the ADU-07 could not connect to the MySQL database. This problem could be caused by an 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|e|system initialisation error: hardware|Init error: Hardware error|One of the hardware components could not be initialised correctly at start-up of the ADU-07 system. The name of the hardware component is attached to this message. Please check your hardware for errors. MCP|1|16|i|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|e|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|e|got data of idle channel||The CPU board reads samples for a channel, that is not recording data. This points to hardware problems or invalid configuration of the ADU-07 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|i|unexpected MCP state||This is a collective message for unexpected states in the ADU-07 control program. Please send the message with its attached information to the Metronix support team. MCP|1|20|e|meas started incompletely: inv. sample frequency||One of the channels, that should take part in the new measurement should us a sampling frequency, that is not supported by the according ADB board. The ADU-07 system will choose a fallback value instead. MCP|1|21|e|data disk space smaller than 5MB|Disk space low|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|i|system is booting|Booting|This message informs you that the ADU-07 system is currently booting up MCP|1|23|i|selftest is active|Selftest|This message informs you, that the ADU-07 system is currently executing selftest measurements. Attached to this message you can find the step, that is actually executed. MCP|1|24|i|system is shutting down|Shutting down|This message informs you, that the ADU-07 system is currently shutting down. MCP|1|25|i|system is sleeping|Sleeping|This message informs you, that the ADU-07 system is going into sleep mode. MCP|1|26|i|system is ready|Idle|This message informs you, that the ADU-07 system was completely booted up and is ready to execute the selftest procedure. MCP|1|27|i|system woke up|Woke up from sleep|This message informs you, that the ADU-07 system woke up from sleep mode. MCP|1|28|e|system sleep error|Sleepmode error|This message informs you, that an error has occurred when entering or leaving the sleep mode. MCP|1|29|e|meas started incompletely: some channels not available|Start failed: channels not available|This message says, that some of the channels, that 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|i|selftest result:|Selftest:|This message shows you the result of the selftest procedure. If it is OK, no problems occurred during selftest. If the result is "NOK", please examine the selftest results in the "Selftest" page of the Webinterface. At least for one of the hardware components the "Init Error" or "ADB Error" field should show a value unequal 0. You will find the according message in this table in the row, that fits to the component and Subindex you find in the "Init Error" or "ADB Error" field. MCP|1|31|i|meas cancelled by user|Meas. cancelled|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|i|meas stopped manually||This message informs you, that after receiving the last samples of the measurement, the buffer were unequal of size. This happened, because you cancelled a running 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|e|OpenMT: socket interface could not be opened/created||This error occurs, if an OpenMT_DataInterface ProcessingObject was configured for the MCP ProcessingQueue and the socket connection could not be created/opened, using the port number that was configured in the XML job file. Maybe the port number is allready in use or there is no valid TCP/IP interface. MCP|1|34|e|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|e|OpenMT: error while sending data via socket interface||This error signals an problem while sending data on the socket interface to the client application. If this error occurs the data may be received incomplete at the receiver/client application. This may happen if for example the client application exits unexpectedly. MCP|1|36|e|OpenMT: local OpenMT client could not be started||This error occurs if you configured the OpenMT_DataInterface in a way, that a local OpenMT client should be started. This way the data would be processed right on the local system. For some reason the client could not be started. This may 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|e|OpenMT: local OpenMT client could not be stopped||This error occurs, if the local OpenMT client could not be stopped at the end of the measurement. This may happen, if the OpenMT application allready exited due to some reason, or if OpenMT hang up. In this case the OpenMT process must be killed by hand before it should be started again. MCP|1|38|i|sleep mode activated||The user has activated the "Sleep Mode". The ADU-07 system will go to sleep, if this is possible. This will set the CPU board to "Suspend To RAM". If sleeping, the system is not accessible via the Webinterface anymore. MCP|1|39|i|sleep mode deactivated||The user has deactivated the "Sleep Mode". The ADU-07 system will not go to sleep anymore. MCP|1|40|i|resetting sleep mode config||The user has reset the "Sleep Mode" configuration. Therefore the "Sleep Mode" will be deactivated and furthermore all "Wake Up Periode" will be deleted. MCP|1|41|i|W-LAN was activated|W-LAN was activated|The W-Lan module was activated. MCP|1|42|i|W-LAN was deactivated|W-LAN was deactivated|The W-Lan module was deactivated. MCP|1|43|i|system is rebooting|Rebooting|The system is rebooting. MCP|1|44|i|AutoCorr: Switched Gain|AutoCorr: Switched Gain|The AutoCorr Processing Object switched the gain for a channel to another value than the one that was used at start-up of the job. This may happen, either because the initial gain settings have been too conservative (switch to higher gain), or because the ADB board is near to be overpowered (switch to smaller gain). MCP|1|45|i|AutoCorr: Switched DC offset correction|AutoCorr: Switched DC offset correc- tion|The AutoCorr Processing Object switched the DC offset corerction for a channel to another value than the one that was used at start-up of the job. This may only happen, if the DC offset of the time series reaches a value bigger/smaller than +/-400mV. In this case the ADB board is in danger to be overpowered. MCP|1|46|e|disk error: 1 or more partitions are damaged and must be repaired|disk error: internal SD/CF card is damaged!|The ADU-07e system detected a damaged file system on 1 or more partitions of the internal CF/SD card. Please check the CF/SD card and try to repair the disk, e.g. by re-creating the system disk, using the Metronix update tool. If this problem should occur again afterwards, the disk may have reached its End Of Lifetime and MUST be replaced! MCP|1|47|e|disk error: target disk is full - stopping jobs recording on this disk|disk error: almost full -> stopping jobs|The target disk is almost 100% full. The ADU-07e system is stopping all jobs that are recording data to this disk. MCP|1|48|e|disk error: no USB mass storage device mounted - using internal disk instead of|disk error: no USB mounted using int. disk|Data should be recorded to external USB mass storage device mounted to ADU, but no device could be found when the job was started. Maybe the USB devices was detached. Recording to internal disk now instead of external USB device. MCP|1|49|e|Ejecting TS Data SD-Card||"The customer asked the ADU system to eject the TS data SD-Card. If failed, check the SD-Card. Maybe it is already ejected or no SD-Card is inserted into ADU system. Note that without TS data SD-Card installed the disk space for TS data is very limited. Always make sure that a TS data SD-Card is inserted if a job is started / running." MCP|1|50|e|Inserting TS Data SD-Card||The customer asked the ADU system to detect/insert a new TS data SD-Card. If this fails, check, if the inserted SD-Card is OK and contains a valid/supported file system, such as EXT-3, EXT-4 or FAT (including exFAT). MCP|1|51|e|Formating TS Data SD-Card||The customer asked the ADU system to format the currently plugged in Frontpanel SD-Card where all TS data is stored on. All data on the SD-Card will be deleted and the SD-Card will be created with 1 single EXT4 partition. MCP|1|52|e|No TS Data SD-Card inserted - job will NOT be started||There is no TS Data SD-Card plugged in on Frontpanel. The ADU system will not start the recording as there is no disk space available for the data. MCP|1|53|e|TS Data SD-Card failed - system will reboot||During operation severe problems arose with the Frontpanel TS Data SD-Card. It failed and is not accessible anymore. The ADU System will reboot itself to try to go back to normal operation. Currently running jobs will be continued after reboot. If this problem occurs again, the Frontpanel TS Data SD-Card MUST be exchanged. MCP_USB|2|1|e|USB communication timeout||This message advises you, that problems occurred in USB communication between the measurement hardware and the CPU board. This may either be caused by a missing USB connection between CPU board and measurement hardware or hardware problems on this components. Please check your hardware. MCP_USB|2|2|e|USB driver error||This message says, that the control program has problems with connecting to the USB driver. The reasons 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|e|meas not started: hardware error|Start failed: Hardware error|A measurement could not be started due to problems with the measurement hardware. Please check your hardware. MICRO|3|2|e|all meas stopped: HW error - data corruption|Unexpect. stop:HW error on backplane|A buffer overflow occurred on the measurement hardware. Therefore all measurements are stopped. MICRO|3|3|e|Backplane SW: GPS - buffer overflow||An internal buffer overflow occurred in the measurement hardware when accessing the GPS board. This may not happen in normal operation and points to a problem with GPS board. Pleas contact the Metronix support team. MICRO|3|4|e|Backplane SW: GPS - no Linefeed in GPS sentence||This message occurs, if the data from the GPS board is corrupt. This may happen, if the GPS board is defect or not attached correctly into the slot. MICRO|3|5|e|Backplane SW: GPS - Timeout in interface - ignore during boot or reset of GPS||This message occurs, if the data from the GPS board is corrupt. This may happen, if the GPS board is defect or not attached correctly into the slot. The message may occur once after start-up of the system. MICRO|3|6|e|Backplane SW: 5Volt supply fail||This message says, 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|e|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|i|battery voltage switched to FAIR|Battery FAIR!|The battery voltage switched from GOOD to FAIR. Please check the battery and change it to a new one. HW_MSG|4|2|e|battery voltage switched to LOW|Battery LOW!|The battery voltage switched from FAIR to LOW. Battery power is now critical and the battery has to be exchanged immediately. HW_MSG|4|3|e|battery voltage critical: shutting down|Power critical!Shutting down!|The critical battery voltage forced the ADU-07 system to shut down. This functionality is not implemented yet. HW_MSG|4|4|e|temperature over maximum: shutting down|Temp. critical!Shutting down!|The internal temperature exceeded the maximum value. The system is shutting down. This functionality is not implemented yet. HW_MSG|4|5|e|temperature under minimum: shutting down|Temp. critical!Shutting down!|The internal temperature exceeded the minimum value. The system is shutting down. This functionality is not implemented yet. HW_MSG|4|6|e|detected BAD DATA!|Detected BAD DATA!|The CEA "Bad Data" Selftest Step detected bad data in one of the channels. The user should check the complete set-up for this channel (ADB Board - Cable - Sensor). It may be that either the E-Field cables have been cut, or one of the other sensor cables or sensors is broken. GPS_MSG|5|1|e|GPS board not responding|GPS board not responding|This functionality is not implemented yet. GPS_MSG|5|2|e|unknown GPS board||During start-up of the ADU-07 system an invalid GPS board was found, that is not supported by the system. Please check you GPS hardware. GPS_MSG|5|3|i|GPS lost sync||The ADU-07 system lost the synchronisation to the GPS signal. This means, that the state switched from "G3fix - fully synced" to a lower state. GPS_MSG|5|4|i|GPS gained sync||The ADU-07 system gained a full sync to the GPS signal. If this happens, the ADU-07 system time is synchronised to the GPS time. Even if the system looses the sync afterwards, the system is still synchronised. GPS_MSG|5|5|i|GPS: no antenna connected||This functionality is not implemented yet. GPS_MSG|5|6|i|GPS: no satellites found||This functionality is not implemented yet. GPS_MSG|5|7|i|GPS: insufficient satellites for sync||This functionality is not implemented yet. GPS_MSG|5|8|e|GPS: no time synchronisation||This functionality is not implemented yet. GPS_MSG|5|9|i|GPS: toggled Dynamic Mode|GPS: toggled dynamic mode now|The Dynamic Mode of the GPS board was switched from stationary to moving, or vice versa. BACK_MAIN|6|1|e|main backplane not responding||The main backplane board could not be initialised. Pleas check your hardware. BACK_MAIN|6|2|e|unknown main backplane type|Main backplane:Unkown type|The ADU-07 system, found an invalid main backplane board that is not supported by the system. BACK_MAIN|6|3|e|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|e|status display not accessible||This functionality is not implemented yet. SUB_BACK|7|1|e|sub backplane not responding|Sub backplane: No response|The sub backplane board could not be initialised. Please check your hardware. SUB_BACK|7|2|e|unknown sub backplane type|Sub backplane: Unknown type|The ADU-07 system, found an invalid sub backplane board that is not supported by the system. SUB_BACK|7|3|e|sub backplane could not be booted|Sub backplane: Boot error|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|e|cal. board not responding|CAL board: No response|The calibration board could not be initialised. Please check your hardware. CAL|8|2|e|unknown cal. board|CAL board: unknown type|The ADU-07 system, found an invalid calibration board that is not supported by the system. ADB|9|1|e|ADB board not responding|ADB board: No response|The ADB board could not be initialised. Please check your hardware. ADB|9|1|e|unknown ADB type||The ADU-07 system, found an invalid ADB board that is not supported by the system. ADB|9|2|e|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 changed configuration is attached to this message. Please check your measurement configuration. ADB|9|3|e|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 with the ADB board in this channel. Please check the hardware for errors. ADB|9|4|e|ADU07-ADB-LF: 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|5|e|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 selftest results for this step. ADB|9|6|e|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 selftest results for this step. ADB|9|7|e|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 selftest results for this step. ADB|9|8|e|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 selftest results for this step. ADB|9|9|e|ADU07-ADB-LF: external offset correction error||The external offset correction on the LF ADB board failed. This points to hardware problems with the offset correction DAC on the ADB board. Please check the hardware. ADB|9|10|e|ADU07-ADB-LF/MF: 4Hz low pass filter error||The attenuation of the 4 Hz low pass filter on the LF/MF 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|e|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|e|ADU07-ADB-LF: DC level too high for gain|ADB: DC level too high|The DC level on the sensor input is too high for a amplification. Therefore do not use the gain stages other 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|e|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|e|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|e|ADU07-ADB-HF: 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 selftest results for this step. ADB|9|16|e|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. This points to a hardware problem. Please check the selftest results for this step. ADB|9|17|e|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. This points to a hardware problem. Please check the selftest results for this step. ADB|9|18|e|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. This points to a hardware problem. Please check the selftest results for this step. ADB|9|19|e|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|e|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|e|ADU07-ADB-HF: DC level too high for gain|ADB: DC level too high|The DC level on the sensor input is too high for a amplification. Therefore do not use the gain stages other 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|22|e|ADU07-ADB-COMMON: sync failed|ADB: sync error|The synchronisation of the single ADB boards before a measurement failed. Therefore the single channels of the measurement may jitter by the t = 1/Sample Frequency. This points to a hardware problem. Please check the ADB board for errors. ADB|9|23|e|ADU07-ADB-MF: 500Hz high pass filter error||The attenuation of the 500 Hz high pass filter on the MF ADB board is out of range. This points to hardware problems with the 500 Hz HP filter on the ADB board. Please check the hardware. ADB|9|24|e|ADU07-ADB-MF: gain out of range 4:16 (LF)||The gain for combination "gain stage 1 = 4", "gain stage 2 = 16" is out of range on the LF input circuitry for the ADU07-ADB-MF board. This points to a hardware problem. Please check the selftest results for this step. ADB|9|25|e|ADU07-ADB-MF: gain out of range 16:4 (LF)||The gain for combination "gain stage 1 = 16", "gain stage 2 = 4" is out of range on the LF input circuitry for the ADU07-ADB-MF board. This points to a hardware problem. Please check the selftest results for this step. ADB|9|26|e|ADU07-ADB-MF: gain out of range 4:16 (HF)||The gain for combination "gain stage 1 = 4", "gain stage 2 = 16" is out of range on the HF input circuitry for the ADU07-ADB-MF board. This points to a hardware problem. Please check the selftest results for this step. ADB|9|27|e|ADU07-ADB-MF: gain out of range 16:4 (HF)||The gain for combination "gain stage 1 = 16", "gain stage 2 = 4" is out of range on the HF input circuitry for the ADU07-ADB-MF board. This points to a hardware problem. Please check the selftest results for this step. ADB|9|28|e|ADU07-ADB: Gain Correction factors out of date -> updated now|ADB: Gain Corr Out Of Date updated now!|The Gain Correction factors that are stored inisde the ADB EEPROMs is out of date. A re-calibration of the Gain Stages should be done by executing the according selftest steps. ADB|9|29|e|ADU07-ADB: Gain Correction factors are invalid. Using Defaults (1.0).|ADB: Gain Corr Invalid|The Gain Correction factors that are stored inside the ADB EEPROMs are invalid (either because the Cal File is damaged or the File does not fit to the ADB Board type). In either case the Gain Stages need to be re-calibrated executing the according selftest steps. In the meantime all correction factors will be set to 1.0. ADB|9|30|e|ADU07-ADB: Calibration of Gain Stages failed|ADB: Calibra tion of Gain Stages failed|The Calibration of the Gain Stages failed. The Gain Correction factors are propably invalid now. The Calibration should be re-started. If it fails again a HW problem occured. ADB|9|31|e|ADU07-ADB: Gain Correction factor out of tolerance window|ADB: Gain Corr.Factor Out Of Range|The determined Gain Correction factor for a certain Gain Stage is out of range. This points to a HW error on the ADB board. ADB|9|32|e|ADU07-ADB: Unknown error in Gain Stage calibration|ADB: Gain Corr Invalid|An unknown error occured during the calibration of the gain stage. This should not happen. Nothing can be done by the user. ADB|9|33|e|Unified Fast Selftest cannot be executed on MF board.|ADB: Unified Fast Selftest does not work on ADU07-ADB-MF|The Unified Fast Selftest does not work on the ADU07-ADB-MF board. Please use another selftest mode. ADB|9|34|e|Detection of LF LSB failed|ADB: Detection of LF LSB failed|The detetcion of the LF LSB failed. This points to a hardware problem, either with the ADB board, or the Calibration part of the Clock/GPS board. ADB|9|35|e|Detection of HF LSB failed|ADB: Detection of HF LSB failed|The detetcion of the HF LSB failed. This points to a hardware problem, either with the ADB board, or the Calibration part of the Clock/GPS board. ADB|9|36|e|probe resistance out of range - check electrode and cable|ADB: probe re- sistance out ofrange|The detetcion of the probe resistance failed. Check the E-Field cable or E-Field probe. ADB|9|37|e|Magnetic Field sensor check failed - check sensor and cable|ADB: Check of Magnetic field sensor failed|The check of the magnetic field sensor failed. It shows wrong phase / amplitude values. Please check the connected Magnetic Field sensor ans sensor cable. ADB|9|38|e|Gain Stage amplification on ADB is out of range - hardware error|ADB: Gain Stage out of range|The gain amplification for the Gain Stage on the ADB board is out of range. This points to an hardware problem, either with the ADB board or the calibration board. ADB|9|39|e|Input Divider do not work correctly - hardware error|ADB: Input Divider error|The Input Divider that configure the ADB board to work as E-Field or H-Field channel, do not work correctly. This points to a problem with the ADB board (hardware error). ADB|9|40|e|Radio Filter do not work correctly - hardware error|ADB: Radio Filter error|The Radio Filter on the ADB board to not work correctly. This is caused by a hardware error on the ADB board. As a result the recorded time series may be overpowered, if you record data in high noise environment (e.g. close to radio transmitters, power lines, …). ADB|9|41|e|Probe Resistance is too high - check electrode and cable|ADB: Probe Re- sistance too high|The Probe Resistance that has been detected during selftest is too high. This points to either a broken E-Field cable or a broken probe. The E-Field probe and cable for the according channel should be checked, unless the measurement is done on very resitive ground. ADB|9|42|e|Probe Resistance big anisotropy between Ex and Ey - check elecrode and cable|ADB: Probe Re- sistance big anisotropy|There is a big anisotropy in Probe Resistance between Ex and Ey channels. Unless the measurement takes place ground with very different resistance values for Ex and Ey the electrodes and cables should be checked. Likely they are broken for either Ex or Ey or one of the directions has bad connection to the ground. GPS_STATUS|10|1|i|GPS Status report||This message shows a GPS status report. HW_STATUS|11|1|i|HW status report||This message shows a hardware status report containing the actual battery voltage, current and status and other values. GLOBAL|12|1|e|unknown system identity|GLOBAL: unknownsystem info|This message says, that the measurement contains an invalid system identity, that is not supported by the ADU-07 system. Please check your hardware. USB_AUTOMOUNTER|13|1|i|USB: scanning device|USB: scanning device|This message says, that a new USB mass storage device was attached and is scanned by the USB Automounter. The USB Automounter will try to mount the device to ist target directory and start any job-lists, if configured. USB_AUTOMOUNTER|13|2|i|USB: mounting device|USB: mounting device|The device is mounted to the configured target directory. USB_AUTOMOUNTER|13|3|i|USB: submitting job|USB: submittingjob|The job of the job-list was submitted to the ADU-07(e) internal job table. USB_AUTOMOUNTER|13|4|e|USB: mounting of device failed !|USB: mounting of device failed|It was tried to mount the device to ist target directory, what failed. Maybe the configured target directory inside the "ADU07Conf" XML file is invalid. Please check the configuration file. USB_AUTOMOUNTER|13|5|e|USB: start of job failed|USB: starting 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 specifed in the ADU07Conf XML file. USB_AUTOMOUNTER|13|6|e|USB: scanning of device failed|USB: scanning device failed|The newly attached USB device was tried to be scanned by the USB Automounter. This failed. The reason can be that there was no preconfigured directory strutcture or now valid ADU07Conf XML file. USB_AUTOMOUNTER|13|7|i|USB: device was detached|USB: device wasdetached|An attached USB device was detached again. USB_AUTOMOUNTER|13|8|i|USB: job-list transferred completely|USB: job-list transferred completely|All jobs of an job-list from an USB device have been transferred completely to the "jobs" table. USB_AUTOMOUNTER|13|9|i|USB: script was executed correctly|USB: script executed correctly|A script of the script-list inside the ADU07Conf XML file was executed correctly. USB_AUTOMOUNTER|13|10|i|USB: execution of script failed|USB: script execution failed|The execution of a script defined inside the ADU07Conf XML file failed. Check the script that should be started. USB_AUTOMOUNTER|13|11|i|USB: script-list executed completely|USB: scipt-listexecuted completely|All scripts of the script-list have been executed. CON|14|1|i|connector not responding|Connector boardNo response|The connector board could not be initialised. Please check your hardware. If you have an ADU-07 system with old, revision 1.0 connector board this is no problem (Revision 2.0 available since ADU-07e). CON|14|2|e|unknown connector type|Connector boardUnknown type|The ADU-07 system, found an invalid connector board that is not supported by the system. CON|14|3|e|failed to configure sensor input dividers|Connector boardFailed to set input dividers|When starting a measurement the ADU-07e system failed to correctly configure the sensor input dividers. This probably is a hardware error on the Connector Board. As a result the sensor input dividers may either be set to 1 or 8 with may result in a time series amplitude beeing to high or low (depending on the sensor type). SENSOR|15|1|i|no plug and play sensor found|Sensor: No PNP sensor found|The sensor on the specific input could not be initialised. Please check your hardware. If you there is no MFS-06e, MFS-07e or EFD-07e sensor connected, this is no problem. SENSOR|15|2|e|unknown sensor type|Sensor: Unknown type|The ADU-07 system, found an invalid connector board that is not supported by the system. SENSOR|15|3|i|invalid XML cal file|Sensor: invalid XML CALfile|The ADU-07 system, found an new, intelligent sensor but was unable to read the sensors XML cal file from it. This may either be caused ba the XML cal file beeing broken, or by the sensor having no XML cal file stored inside ist EEPROM at all. This is cirtical. The sensor will operate properly. If you want to recalibrate the sensor, please contact the Metronix support team. SENSOR|15|4|i|read XML cal file from sensor|Sensor: read CAL file|The ADU-07 system, found an new, intelligent sensor and successfully read a XML cal file from ist 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|i|user msg.:|User MSG:|This is a user specific message. It is not created by the ADU-07 system, but by the customer who configured the system. PWR_STAGE|17|1|i|power stage not responding|Power Stage No response|The connected Power Stage (ARS2000 drive) could not be detected during boot-up of the system. PWR_STAGE|17|2|e|unknown power stage type|Power Stage Unknown type|During boot-up of the system a Power Stage was detected, but its type information is invalid. PWR_STAGE|17|3|e|Power Stage error: check manual -|Power Stage error:|Internal error of the Power Stage has occured. Check the TXM-22 manual for a detailed description of the error. PWR_STAGE|17|4|i|Cleared Power Stage error:|Cleared Power Stage error:|An active error of the Power Stage was cleared. PWR_STAGE|17|5|e|Undervoltage Power Stage: check power supply|Undervoltage Power Stage|During operation the DC link voltage of the connected Power Stage drop beneath the minimum value. Please check the power supply for the Power Stage. PWR_STAGE|17|6|e|Overvoltage Power Stage: check braking resistor and operation mode|Overvoltage Power Stage|During operation the DC link voltage of the connected Power Stage exceeded the maximum value. Please check the braking resistor and the operation mode (output frequency and current). PWR_STAGE|17|7|e|Overtemperature Power Stage: check cooling|OvertemperaturePower Stage|During operation the Power Stage temperature exceeded the maximum value. Please check the cooling of the Power Stage. PWR_STAGE|17|8|e|Short Ciurcuit in Power Stage: check electrodes and cables|Short Circuit Power Stage|The output of the Power Stage is short circuited. Please check the electrode and cables. PWR_STAGE|17|9|e|Overload of Power Stage: check operation mode|Overload Power Stage|The Power Stage was overloaded. Please check your operation mode and if needed, reduce the output current. PWR_STAGE|17|10|e|Failed to load DC link of Power Stage|Failed to load DC link of Power Stage|The DC link of the Power Stage cannot be loaded. Please check the braking resistor and power supply. PWR_STAGE|17|11|e|Failed to reset Power Stage|Failed to resetPower Stage|The reset of the Power Stage failed. Check the communication interface to the Power Stage (cables). PWR_STAGE|17|12|e|Failed to acknowledge error in Power Stage|Failed to ack. errors in PowerStage|The acknowledge of errors inside the Power Stage failed. Check the communication interface to the Power Stage (cables). PWR_STAGE|17|13|e|Failed to enable Power Stage|Failed to enab.Power Stage|The Power Stage can not be enabled. Check power supply and hardware enable signals. PWR_STAGE|17|14|e|Failed to disable Power Stage|Failed to disable Power Stage|The Power Stage can not be disabled. This is a serious problem. Check the communication cables. PWR_STAGE|17|15|i|Detecting electrode coupling|Detecting Elec trode Coupling|The TXM-22 started to detect the electrode coupling. PWR_STAGE|17|16|e|Failed to detect the electrode coupling|Failed to de tect Electrode Coupling|The Power Stage failed to detect the electrode coupling. As a result no signal can be fed into the ground in a correct manner. Please check the electrode coupling. PWR_STAGE|17|17|e|Emergency Shutdown Active|Emergency Shut down Active|An Emergency Shutdown occured. The Power Stage was switched off therefore. Please check the Power Stage condition and find out the reason for the Emergency Shutdown. Afterwards release the Emergency Switch. PWR_STAGE|17|18|i|Emergency Shutdown was Cleared|Emergency Shut down was clear ed|The Emergency Shutdown cleared. The Power Stage is ready for operation again. PWR_STAGE|17|19|e|Lost Connection to Power Stage|Lost Connect tion to Power Stage|The Connection to the Power Stage was lost. No communication can be done between TXB-22 and TXM-22 anymore. Please check the cabling between the two devices. PWR_STAGE|17|20|i|Reconnected to Power Stage|Reconnected to Power Stage|The connection to the Power Stage was established again. The system is now working correctly again. PWR_STAGE|17|21|i|Power Stage Output was enabled|Power Stage Output was enabled|The Power Stage Output was enabled and is now outputting signal waveforms. PWR_STAGE|17|22|i|Power Stage Output was disabled|Power Stage Output was disabled|The Power Stage Output was disabled and is not outputting signal waveforms, even if a job is running. The output current is hardly set to 0. PWR_STAGE|17|23|e|Sequence Config Error: Base Frequency is 0Hz|Seqc. Config Error: Base Frequency = 0Hz|The configured Sequence is invalid. The base frequency for the output signal was set to 0Hz. This is no valid value. The execution of the Sequence (Joblist) will be stopped. PWR_STAGE|17|24|e|Sequence Config Error: Rotation Frequency is 0Hz|Seqc. Config Error: RotationFrequency = 0Hz|The configured Sequence is invalid. The "Rotating Dipole" or "Alternating Dipole" functionality is active AND the rotation frequency is set to 0Hz. The joblist will be started, but before a output signal is generated, the error must be acknowledged. The output signals current dipole will not be rotated or alternated. PWR_STAGE|17|25|e|General Config Error: Invalid Operation mode|General Config Error: Invalid Operation Mode|The configured Sequence is invalid. An invalid operation mode was configured. E.g. in the current version the "HF" mode is not available. The joblist will be started in LF mode instead with the fastest possible output signal frequency. PWR_STAGE|17|26|e|Invalid FW Version: TXM-22 Operation stopped|Invalid FW Ver sion: Operationstopped|When initialising the ARS2000 (TXM-22 Power Stage) and invalid or not supported FW version was detected inside the Power Stage. For security meanings the operation of the TXM-22 system was stopped. No jobs can be started. Check the Power Stage FW version on the "Hardware Config" page of the User Interface and ask Metronix for support. PWR_STAGE|17|27|i|Testfirmware was found inside Power Stage|Test FW Versionwas found in Power Stage|A Test FW version was found inside the connected TXM-22 Power Stage. This should only occur in prototypes. As the FW version is marked as Test FW and therefore as untested undefined behaviour may occur. Please inform Metronix of this issue. If Metronix says the FW can be used, this message can be ignored. Otherwhise a FW update with the lates released FW should be done. GSM|18|1|e|invalid phone number|GSM: invalid phone number|When trying to sent a new status SMS the configured phone number was invalid. As a result the SMS was not sent to the recipient. GSM|18|2|i|Sending new status SMS||A new status SMS was sent. GSM|18|3|i|Communication error with GSM modem||A communication error with the GSM modem occured. Overview -------- The ADU-08e comes in a waterproof, ruggedized Peli case housing. .. image:: /media/adu-08e/adu-08e.jpg :width: 80% :align: center :alt: adu-08e The ADU-08e is delivered along with an additional external GPS-antenna and two battery cables. Figure 3 2 and 2-3 show the ADU-08e and its operating elements. All operating elements are numbered and described in more detail in the following pages. .. figure:: /media/adu-08e/operating_elements_front_panel.jpg :width: 80% :align: center :alt: adu-08e Operating elements of ADU-08e front-panel 1. USB Socket 2. GPS Status LED 3. Recording Status LED 4. Battery Status LED 5. GPS antenna 6. Binding posts for auxiliary power supply 7. Key pad 8. On/Off button 9. Slot for SD card 10. Display 11. Bridge for internal or external GPS Antenna, left is external, right is internal antenna (as shown in the picture) .. figure:: /media/adu-08e/operating_elements_left_side.jpg :width: 80% :align: center Operating elements of ADU-08e left side 11. Network socket 12. USB socket 13. GPS antenna socket 14. Battery sockets .. figure:: /media/adu-08e/operating_elements_right_side.jpg :width: 80% :align: center Operating elements of ADU-08e right side 15. E-field connectors 16. GND socket 17. Magnetometer connectors USB Type “A” Connectors ^^^^^^^^^^^^^^^^^^^^^^^ You will find one USB Type A connector on the front lid and another one on the left side for connection of USB mass storage devices or USB WiFi stick. Mass-storage devices and WiFi sticks will be recognized by the operating system automatically. GPS status LED ^^^^^^^^^^^^^^ This LED shows 3 states: .. csv-table:: :delim: | .. image:: /media/adu-08e-2C/led_off.png|LED off|No GPS synchronization or system in clock hold mode. .. image:: /media/adu-08e-2C/led_blink.png|LED blink|System has detected sufficient number of satellites, but has not reached the maximum accuracy yet. .. image:: /media/adu-08e-2C/led_steady_green.png|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 track. 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 switched on 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: | .. image:: /media/adu-08e-2C/battery_good.png|Battery good (voltage higher than 12.0V, fully charged) .. image:: /media/adu-08e-2C/battery_voltage_fair.png|Battery voltage fair (<12.0V and >10.5V) .. image:: /media/adu-08e-2C/battery_low.png|Battery low (voltage < 10.5 and > 10.0V) shutdown will come soon. .. image:: /media/adu-08e-2C/system_shutdown_jobs_closed.png|The system has shut down and closed all running jobs automatically. 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. GPS Antenna ^^^^^^^^^^^ The built-in GPS antenna receives the signals from the satellites. It needs to have view to the open sky. In case the built-in antenna is used, the ADU may not be installed in a metal box. Binding Posts for Auxiliary Power Supply ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Here a 9 to 15V power source can be connected in order to power the ADU-08e. Navigation Buttons ^^^^^^^^^^^^^^^^^^^^^^^ There are four buttons (Up, Down, Left, Right) and another three (Back, Home, Enter) which allow to navigate within the display content. If an entry has made you can confirm it by the Enter button. Another four buttons (F1, F2, F3, F4) are used as soft keys. Their function depend on the selected display page. Button On / Off ^^^^^^^^^^^^^^^^^^^^^^^ Pushing this button will start the instrument if connected to a power source. In order to shut down a running instrument press the button for a longer time (5 seconds) until you see the shut-down message in the display. Confirm the shut-down and wait for about 30 seconds until the ADU switches off. On a running system this button is also used to activate a dark status display. Slot for SD card ^^^^^^^^^^^^^^^^ Here an SD card can be inserted. It is used for data storage and can have a size up to 200 GByte presently. The size delivered on standard is 32 GByte. 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 seconds in case no button is pushed. In order to switch it on again you need to press the “On” button (8). Battery Connectors ^^^^^^^^^^^^^^^^^^ The ADU-08e is equipped with 2 battery sockets. You can connect a 12V battery or two batteries in parallel for extended operation time. Before the delivered battery cable can be connected, you have to remove the protection cap of the socket. The input voltage is 12 V nominal; the allowed voltage spans from 10.5V to max. 16V. The inputs are protected against wrong polarity and over and under voltage. If the ADU should not work, check for wrong polarity or wrong voltage. If the instrument shall be operated without interruption, you may use the second battery input to connect a fresh battery. After having it connected, you may disconnect the old battery from the ADU-08e for recharging. An auxiliary 3rd battery input is provided on the front-panel. Here for instance a small Gel- or Li-Ion battery can be connected in order to provide a continuous power-supply when the system is transported to the next site. It may especially be helpful when the distance between two sites is only a few hundred meters as it could be the case in small scale AMT or RMT surveys. Antenna socket for external GPS antenna ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The ADU comes with a built-in GPS antenna which is sufficient for most cases. We also deliver a second external antenna which may be used in difficult reception situations or when the ADU is housed in a metal case. In this case the cable bridge has to be plug into position EXT. Socket for Network ^^^^^^^^^^^^^^^^^^ The network cable is connected to this socket (RJ45 type). USB socket ^^^^^^^^^^ A USB device such as USB key or WLAN key can be connected here. 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 6 is the pin where the standard E-field cable has to be connected to. In a typical arrangement the ADU is located in the center of the two E-field lines. Plug-in the cable connector in a way that the red dots match on plug and socket and push the plug in until it clicks. .. csv-table:: :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 -) .. figure:: /media/faq/pinout/Pinning_of_E-Field_Plug-rear_view_(to_solder_cups).jpg :width: 15% :align: center Pinning of E-Field socket (front view) GND Socket ^^^^^^^^^^ This socket is used to connect the grounding rod or electrode with the ADU. The grounding can be done by a steel rod or an electrode. Grounding should be done closely to the ADU. .. caution:: 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-08e 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 red dots match on plug and socket and push the plug in until it clicks. .. csv-table:: :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|:math:`I^{2}C` SDA 10|:math:`I^{2}C` SCL .. figure:: /media/adu-08e/pinning_h_field_socket_front_view.jpg :width: 10% :align: center Pinning of H-Field socket (front view) .. include:: ./installation_adu.rstinclude .. include:: ./front_panel_display.rstinclude .. include:: ./reading_data.rstinclude .. include:: ./adu08e_transfer_functions.rst Declaration of EU Conformity ---------------------------- The ADU-08e complies with all EU standards relevant for this product (see below). .. include:: ./terms_and_abbreviations.rstinclude .. include:: ./safety_notes.rstinclude .. include:: ./general_notes.rstinclude