Changes for page ANU Seismic Data Loggers

Last modified by robert on 2026/02/19 15:45

From 56.1 to 55.1 From 73.1 to 72.1

From version 72.1

edited by robert
on 2026/02/11 16:40

Change comment: There is no comment for this version

To version 56.1

edited by robert
on 2025/08/06 16:45

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)
Attachments (4 modified, 0 added, 1 removed)

Details

Page properties

Content

@@ -16,10 +16,8 @@
  At 100 Hz and with a GPS cable connected these loggers draw about 220 mW of power once the screen is off (higher sample rates draw more power but only marginally, < 5 mW). Adding a sensor (e.g. a Trillium Compact 120) increases this to approximately 400 mW, or 0.4 volt-amps. So, in theory 7 Ah battery should last about 10 days without a solar panel, but in practice it seems to be a bit closer to 8 which may be due to variability in power drain while in getting GPS locks.
--For very sunny environments (latitudes < 30) a 20 Volt, 10 Watt solar panel should have no issue keeping these loggers alive over the summer months, and assuming unobstructed skies should also be fine over winter. **However** when possible a 20 Watt pane works best, especially as they usually cost only $10-20 more these days.
++For very sunny environments (latitudes < 30) a 20 Volts 10 Watt solar panel should have no issue keeping these loggers alive over the summer months, and assuming unobstructed skies should also be fine over winter. However there is no harm in using 20 or even a 40 Watt panel, especially for high latitudes, coastal regions, or areas without a full sky view. In theory up to a 60 Watt solar panel is fine, but we don't recommend anything over 40 Watts and that amount of power is already overkill.
--40 Watt panels can also be used, and may be needed for extreme climates, or areas without a full sky view. 60 Watt panels have also been known to work, but this is now reaching the the limit of what the loggers can reasonably handle for extended periods and are not recommended for long term deploys.
--
  (% class="box infomessage" %)
  (((
  Power issues are easy and cheap to solve relative to the cost of your experiment, don't skimp!
@@ -28,14 +28,6 @@
  (% class="wikigeneratedid" %)
  In the case of an LPR, there is a large compartment for housing an internal battery, able to accommodate anything from a 10-30Ah battery. To use a standard lead acid battery with a positive and negative terminal, a 6 pin adaptor must be used. This ensures the voltage from the external power port (pins A and C) connect to the battery and ensure the system actually recharges. (See [[Peripheral Equipment>>doc:Instrumentation.Peripheral Equipment.WebHome]] for a more comprehensive overview of this kind of setup)
--= GPS Considerations =
--
--GPS is required for the data to have accurate timestamps. A standard 3-5V 1575.42 Mhz coaxial "dongle" antenna works fine and can be found for relatively cheap (e.g. [[https:~~/~~/www.elecbee.com/en-3555-gps-antenna-bnc-male-for-garmin-gps-120120xl125-sounder-with-cable-2m) >>https://www.elecbee.com/en-3555-gps-antenna-bnc-male-for-garmin-gps-120120xl125-sounder-with-cable-2m]]. Anything that locates satellites and gives you a GPS-synced time works!
--
--The TerraSAWR has a built-in GPS but this doesn't work as well, especially if the logger is (wisely) buried. **The LPR does NOT have a built-in GPS antenna, so an external antenna is mandatory.**
--
--In a pinch, a severed or broken antenna can be mended back together relatively easily by non-experts. Even stripping the wire and twisting it back together by hand on site is possible!
--
  = Data Card Formatting and Information =
  Both the TerraSAWR and LPR-200 require SD Cards to be formatted in FAT32 filesystem. For 64Gb cards it can be difficult to format in FAT32, but [[software >>http://auspass.edu.au/field/fat32cardformatter.exe]]is available. ANU recommend SanDisk Extreme 150 mb/s cards in either 32 or 64Gb size. We strongly discourage using cards larger than 64Gb, and in general smaller cards are less likely to fail. We have also found that "adapter" cards (e.g. SD to microSD) are prone to having write issues and **strongly** advise against them.
@@ -42,8 +42,7 @@
  The loggers can be "pre-programmed" with information (e.g. site name, sampling rate, etc) or they can be programmed in the field using the buttons on the logger. To pre-program the cards you simply edit a text file (named "[[ANUSRSetup.txt>>http://auspass.edu.au/field/ANUSRSetup.txt]]" for the LPRs, or "[[tSAWRSetup.txt>>http://auspass.edu.au/field/tSAWRSetup.txt]]" for the TerraSAWRs) and place it in the root directory on the SDCard. When the logger boots up, it will parse and load this information.
--(% class="wikigeneratedid" id="HTheformatforANUSRSetup.txt2FLPR200swillbeasinglelineoftextthatlookslikethis:" %)
--The format for ANUSRSetup.txt / LPR200s will be a single line of text that looks like this:
++== The format for ANUSRSetup.txt / LPR200s will be a single line of text that looks like this: ==
  {{{XXX195G0100010034864      2 }}}
@@ -60,11 +60,10 @@
  (% class="box warningmessage" %)
  (((
--NOTE: the 2 at the very end is for "RECORD ON RESTART". The record on restart option ensures that if the logger dies and is powered back up whilst in the field (due to battery charging cycles or other causes) that the recording will resume. (# of blank spaces before this doesn't matter)
++NOTE: the 2 at the very end is for "RECORD ON RESTART". The record on restart option ensures that if the logger dies and is powered back up whilst in the field (due to battery charging cycles or other causes) that the recording will resume. (# of blank spaces before this doesn't matter)
  )))
--(% class="wikigeneratedid" id="HTheformatforTSAWRloggersisshorter:" %)
--The format for TSAWR loggers is shorter:
++== The format for TSAWR loggers is shorter: ==
  (% class="box errormessage" %)
  (((
@@ -83,8 +83,7 @@
                   and seismometer serial number (9999).
--(% class="wikigeneratedid" id="HTheformattingprocessusingthelogger:" %)
--The formatting process using the logger:
++== The formatting process using the logger: ==
  The process for formatting an SD card within the logger is straightforward. Navigate to the "SD INFORMATION" screen and press ERASE SD CARD. This process may take up to a minute. This will result in erasing all files from the card. Upon starting recording, a new 'seed' will be written containing all the information that the logger has been set with FINISH THIS SECTION
@@ -117,8 +117,8 @@
  This menu also displays the firmware version, battery, external, and solar voltages, and the temperature of the system.
--* Check that all //Initialisation Parameters// are marked as successful.
--* Check that solar voltage is above 10 V in the software, or preferrably physically check that the battery's voltage is increasing via a DMM.
++* Check all Initialisation Parameters are marked as successful.
++* Check that solar voltage is above 10 V, otherwise the station will not last long.
  == Live Seismometer Data ==
@@ -132,7 +132,7 @@
  This menu displays the status of the stations' GPS connection. The screen lists; UTC time, UTC date, latitude, longitude, altitude, number of satellite connections, and SNR.
--* Check that the station is connected to satellites. 3 or more should be perfectly adequate to keep time.
++* Check that the station is connected to satellites
  == SD Information ==
@@ -165,7 +165,7 @@
  (% class="box errormessage" %)
  (((
--Again, ensure the 'RECORD ON RESTART' option is marked with a cross (the default setting). This ensures that the logger will record any time it receives enough power!
++NOTE: Ensure the 'RECORD ON RESTART' option is marked with a cross.
  )))
  (% class="wikigeneratedid" %)
@@ -177,61 +177,34 @@
  = LogFile Conversion Script =
--Both the TSAWR and LPR-200 write logging information as a binary "dat" file which includes GPS time syncs, temperatures, battery power, and position. To convert them into ASCII you can read, use [[THIS PYTHON SCRIPT>>http://auspass.edu.au/field/anusr_log.py]] (current version: 1.42, 02/2026).
++Both the TSAWR and LPR-200 write logging information as a binary "dat" file which includes GPS time syncs, temperatures, battery power, and position. To convert them into ASCII you can read, use [[THIS PYTHON SCRIPT>>http://auspass.edu.au/field/anusr_log.py]].
  = Instrument Response =
--Both the TerraSAWR and LPR-200 use the same ADS1281 analog-to-digital converter chip and are designed to have identical instrument response. The ADC (analog to digital) chip in both loggers originally samples at 1024000 Hz and downsamples towards the output data rate via a 5th order SINC filter, then another four FIR filters. If the output is below 250 Hz, a final "pure" /5 decimation is done without any sort of FIR filter (for better or worse!).
++Both the TerraSAWR and LPR-200 use the same ADS1281 analog-to-digital converter chip and are designed to have identical instrument response. The ADC (analog to digital) chip in both loggers originally samples at 1024000 Hz and downsamples towards the output data rate via a 5th order SINC filter, then another four FIR filters. If the output is below 250 Hz, a final "pure" /5 decimation is done without any sort of FIR filter.
--In the logger's menu, the user can choose to apply a 2nd stage "sensor gain" by selecting an instrument type in the setup menu. This effectively selects a 10 Vpp (e.g. short period sensors), 20 Vpp, 40 Vpp (most broadband sensors) regime to match the sensor's sensitivity. This has the effect of doubling amplitude from 10v to 20v, or quadrupling from 10v to 40v. If you have set your sensor correctly (and the signal isn't clipped!) you can "correct" this by simply multiplying your data by 0.5 etc. This gain manifests itself in stage 2 in the response information.
++{{info}}
++The Stage 3 SINC coefficients (600+) during the initial 1024k > 16k decimation were left off as they slowed down the process x10 and contribute very little (< 0.3 db, < 0.31 ms) to the end result
++{{/info}}
--//(The 600+ Stage 3 SINC coefficients during the initial 1024k > 16k decimation were left off as they slowed down the process x10 and contribute at most 0.3 db amplitude and 0.31 ms phase delay discrepancies, and primarily only to frequencies near the nyquist. If for some reason you want to add this phase manually we can share the parameters with you.)//
++The user can choose to apply a 2nd stage "sensor gain" by selecting an instrument type in the setup menu. This effectively selects a 10 Vpp (e.g. short period sensors), 20 Vpp, 40 Vpp (most broadband sensors) regime to match the sensor's sensitivity. This has the effect of doubling amplitude from 10v to 20v, or quadrupling from 10v to 40v. If you have set your sensor correctly (and the signal isn't clipped!) you can "correct" this by simply multiplying your data by 0.5 etc. This gain manifests itself in stage 2 in the response information.
--You might notice that the response information may come in two versions. The response from our website (see link below) includes the 2nd "sensor gain" stage for clarity. e.g. here is a Trillium Compact 120 & ANU Logger response
++Instrument response can be downloaded from IRIS [[Nominal Response Library>>https://ds.iris.edu/ds/nrl/]] if need be, or [[directly from us>>http://auspass.edu.au/data/logger_response]] , or by downloading the response of an equivalent sensor at AusPass (e.g. get_stations(level='response') ).
--##Channel Response
--    From M/S (Velocity) to COUNTS ()
--    Overall Sensitivity: 3.95452e+08 defined at 1.000 Hz
--    8 stages:
--        Stage 1: PolesZerosResponseStage from M/S to V, gain: 754.3
--        Stage 2: ResponseStage from V to V, gain: 0.25
--        Stage 3: CoefficientsTypeResponseStage from V to COUNTS, gain: 2.09715e+06
--        Stage 4: FIRResponseStage from COUNTS to COUNTS, gain: 1
--        Stage 5: FIRResponseStage from COUNTS to COUNTS, gain: 1
--        Stage 6: FIRResponseStage from COUNTS to COUNTS, gain: 0.99998
--        Stage 7: FIRResponseStage from COUNTS to COUNTS, gain: 1##
++[[Amplitude and phase response for ANU logger at 50 Hz>>image:ANU_50hz_response.png]]
--However, if retrieving from AusPass or IRIS, the 2nd "sensor gain" stage is combined with the logger gain. This has no affect, but you may detect that the former Stage 2 V->V ResponseStage has been merged into the Stage 3 gain.
++[[Amplitude and phase response for ANU logger at 100 Hz>>image:ANU_100hz_response.png]]
--##Channel Response
--    From M/S (Velocity) to COUNTS ()
--    Overall Sensitivity: 3.9546e+08 defined at 1.000 Hz
--    6 stages:
--        Stage 1: PolesZerosResponseStage from M/S to V, gain: 754.3
--        Stage 2: CoefficientsTypeResponseStage from V to COUNTS, gain: 524288
--        Stage 3: FIRResponseStage from COUNTS to COUNTS, gain: 1
--        Stage 4: FIRResponseStage from COUNTS to COUNTS, gain: 1
--        Stage 5: FIRResponseStage from COUNTS to COUNTS, gain: 0.99998
--        Stage 6: FIRResponseStage from COUNTS to COUNTS, gain: 1##
++[[Amplitude and phase response for ANU logger at 250 Hz>>image:ANU_250hz_response.png]]
--For the most part, the data logger response essentially flat when the samplerate output is set to 100 Hz or less and for seismological purposes is likely to be impossible to detect below 20 Hz regardless.
--Instrument response can be downloaded from IRIS [[Nominal Response Library>>https://ds.iris.edu/ds/nrl/datalogger/anurses]] if need be, or [[directly from us>>http://auspass.edu.au/data/logger_response]] , or by downloading the response of an equivalent sensor at AusPass (e.g. get_stations(level='response') ).
++[[Amplitude and phase response for ANU logger at 1000 Hz>>image:ANU_1000hz_response.png]]
--[[Amplitude and phase response for ANU logger at 50 Hz>>image:ANU_50hz_response.png||data-xwiki-image-style-alignment="center" height="356" width="475"]]
++[[Huddle test comparing a Trillium Compact 120 + TerraSAWR vs a Trillium Compact 120 + Nanometrics Centaur (M8.AUANU)>>image:TC120_ANU_vs_CENTAUR.png||data-xwiki-image-style-alignment="center"]]
--[[Amplitude and phase response for ANU logger at 100 Hz>>image:ANU_100hz_response.png||data-xwiki-image-style-alignment="center" height="355" width="473"]]
--
--[[Amplitude and phase response for ANU logger at 250 Hz>>image:ANU_250hz_response.png||data-xwiki-image-style-alignment="center" height="359" width="479"]]
--
--[[Amplitude and phase response for ANU logger at 1000 Hz>>image:ANU_1000hz_response.png||data-xwiki-image-style-alignment="center" height="367" width="489"]]
--
--
--[[Huddle test comparing a Trillium Compact 120 + TerraSAWR vs a Trillium Compact 120 + Nanometrics Centaur (M8.AUANU) at 100 Hz>>image:TC120_ANU_vs_CENTAUR.png||data-xwiki-image-style-alignment="center"]]
--
  = ANU TerraSAWR (Gen 3, FW 3.5a, 2014- current) =
  Earliest known model is dated July 2014 (though first deployed in 2019) and our current flagship model. Lightweight and small.
@@ -240,10 +240,6 @@
  Earliest known model is dated May 2011 (but first deployed November 2012) and still in use today. Potentially capable of housing much larger batteries than the TSAWR due to the larger cavity space.
--We have found that the older LPR SD card slots can sometimes fail such that the data cards prematurely "pop out" during recording, which can be catastrophic. This seems to mostly occur in periods of hot weather, but not always. We have developed a small add-on that screws into the nearby serial port that effectively holds the cards in place and will ship included with these loggers. Screw the device in firmly, then **gently** slide over a pre-inserted card until it is flush with the top of the card. It probably won't slide over all the way and that's by design. Take care not to force the depress the card inadvertently (although testing has shown it will still record).
--
-- [[image:LPR_card_adaptors.jpg||alt="image of the LPR SD-card adapter"]]
--
  = ANU "ANUSR" (Gen 1, 2003? - 2012) =
  This logger has been retired for a long time and has a different instrument response. It used modular component boards and was powered via an acrylic case of 6 x 6V lantern batteries. There is a somewhat complete one above the CAT lab door if anyone is so inclined to have a look.
@@ -276,22 +276,6 @@
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
  (% class="box" %)
  (((
  = TerraSAWR Specs =
@@ -342,19 +342,4 @@
  [[image:LPR battery.jpg]]
  )))
  )))
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
  )))

ANU_1000hz_response.png

Size

@@ -1,1 +1,1 @@
--23.5 KB
++22.7 KB

Content

ANU_100hz_response.png

Size

@@ -1,1 +1,1 @@
--21.4 KB
++21.3 KB

Content

ANU_250hz_response.png

Size

@@ -1,1 +1,1 @@
--23.7 KB
++22.9 KB

Content

ANU_50hz_response.png

Size

@@ -1,1 +1,1 @@
--21793
++21828

Content

LPR_card_adaptors.jpg

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.robert

Size

...	...	@@ -1,1 +1,0 @@
1		-153.3 KB

Content

Changes for page ANU Seismic Data Loggers

Summary

Details

Applications

Navigation