Skip to Content
Last modified by robert on 2026/09/07 17:05
From version 117.2
edited by robert
on 2026/08/12 12:56
Change comment: There is no comment for this version
To version 119.2
edited by robert
on 2026/09/07 15:45
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -71,11 +71,11 @@
71 71  
72 72  We have experienced interference from animals (foxes, dogs, goats) digging up and carrying nodes off for tens or hundreds of metres. It is helpful to minimise human and food smells (particularly on the rope handles) when working in areas where this is a risk. Or, wipe down affected nodes with 50-80% methylated spirits if extensive handling can not be avoided.
73 73  
74 -If you come to collect your node and it is missing~-~- LOOK FOR IT! It may not have gotten far. We have found dozens of nodes by spending 15 minutes looking for them.
74 +If you come to collect your node and it is missing~-~- **LOOK FOR IT!** It may not have gotten far. We have found dozens of nodes by spending 15 minutes looking for them.
75 75  
76 76  = External Power =
77 77  
78 -Both the 5Hz IGU-16HR and 5s BD3C-5 can be optionally powered via external battery via either a replacement bottom half (the 5Hz nodes) or a battery cable accessory (BD3C-5) using standard lead acid batteries from 9-36v. We have done preliminary testing at 250 Hz with a 12v battery:
78 +Both the 5Hz IGU-16HR and 5s BD3C-5 can be optionally powered via external battery via either a replacement bottom half (the 5Hz nodes) or a battery cable accessory (BD3C-5) using standard lead acid batteries from 9-36v. We have done preliminary testing at 250 Hz with a standard 12v deep cycle AGM battery:
79 79  
80 80  - BD3C-5: ~~2 days of recording per 1 Ah
81 81  
... ... @@ -108,10 +108,14 @@
108 108  
109 109  == 2. Burial ==
110 110  
111 -ALL nodes should be buried flush with the ground, no exceptions. If the node is sticking up the data data quality will be significantly reduced (especially the horizontal channels, see [[below>>https://auspass.edu.au/xwiki/bin/view/Instrumentation/SmartSolo%20Nodes/#HIGU-16Horizontalnoise26howtoavoid]]). It also catches wind, makes them more visible, etc. But mostly it makes the data bad. Don't be lazy: do it right.
111 +**ALL nodes should be buried flush with the ground, no exceptions**. If the node is sticking up the data data quality will be significantly reduced (especially the horizontal channels, see [[below>>https://auspass.edu.au/xwiki/bin/view/Instrumentation/SmartSolo%20Nodes/#HIGU-16Horizontalnoise26howtoavoid]]). It also catches wind, makes them more visible, etc. But mostly it makes the data bad.
112 112  
113 -[[An example of what not to do.>>image:1786503344572-296.jpg]]
113 +//Don't be lazy. Do it right. //
114 114  
115 +[[An example of what not to do.>>image:1786503344572-296.jpg||data-xwiki-image-style-alignment="center" height="341" width="404"]]
116 +
117 +[[North channel PSD of the sensor in the picture above (it is not good)>>image:1786503812585-338.02.28 PM.png||data-xwiki-image-style-alignment="center" height="244" width="451"]]
118 +
115 115  == 3. Node Placement ==
116 116  )))
117 117  
... ... @@ -435,6 +435,17 @@
435 435  
436 436  ----
437 437  
442 += Copying raw MiniSeed data without the Software =
443 +
444 +Lately we have been advocating for not writing to the proprietary DFD format (we don't know how this is structured) in the event that the software is misbehaving or one wants to use a linux machine or for whatever reason. This involves simply reading the devices as a mounted USB device and copying off the .MiniSeed files manually~-~- easy enough!
445 +
446 +However please note the filename and channel convention:
447 +
448 +3 Trace(s) in Stream:
449 +XX.TEST..LHX | 2026-09-01T03:26:14.000000Z - 2026-09-07T02:15:01.996000Z | 250.0 Hz, 128532000 samples
450 +XX.TEST..LHY | 2026-09-01T03:26:14.000000Z - 2026-09-07T02:15:01.996000Z | 250.0 Hz, 128532000 samples
451 +XX.TEST..LHZ | 2026-09-01T03:26:14.000000Z - 2026-09-07T02:15:01.996000Z | 250.0 Hz, 128532000 samples
452 +
438 438  = Instrument Response =
439 439  
440 440  We are aware that there are various different published responses for these instruments and trust very few of them. One has to be careful with how polarity is handled between groups as well, and if one is working in integer counts (the ANSIR default) or mV (unclear why anyone would use this as it makes file sizes enormous). The response information published below is in **counts** and seems to fit well in huddle tests. Note that the response is the same for all channels and all units (e.g. there are no bespoke calibrations!), all appear to be sample rate insensitive, and the IGU data has been inverted (multiplied by -1) as described here: [[5Hz Node Polarity Issues>>https://auspass.edu.au/xwiki/bin/view/Data/AusPass%20Data/#HSmartSoloNodePolarityIssues]]
1786503808210-822.02.28 PM.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.robert
Size
... ... @@ -1,0 +1,1 @@
1 +437.8 KB
Content
1786503812585-338.02.28 PM.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.robert
Size
... ... @@ -1,0 +1,1 @@
1 +437.8 KB
Content