Skip to Content
Last modified by robert on 2026/09/07 17:05
From version 120.3
edited by robert
on 2026/09/07 17:05
Change comment: There is no comment for this version
To version 110.17
edited by Jack Dent
on 2026/06/15 11:02
Change comment: (Autosaved)

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.robert
1 +XWiki.JackD
Content
... ... @@ -71,20 +71,8 @@
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 -= External Power =
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 standard 12v deep cycle AGM battery:
79 -
80 -- BD3C-5: ~~2 days of recording per 1 Ah
81 -
82 -- IGU16-HR 3C:  ~~3.5 days of recording per 1 Ah
83 -
84 -- IGU16-HR 1C: ~~7 days of recording per 1 Ah
85 -
86 -Of course, these can also be fit with a solar panel & charge controller which would then theoretically keep them going indefinitely (limited only by the disk storage, which at 250 Hz could be on the order of 12 months).
87 -
88 88  = **Installation** =
89 89  
90 90  (% class="box infomessage" %)
... ... @@ -106,44 +106,35 @@
106 106  
107 107  [[HERE>>http://auspass.edu.au/field/NODES_blank_fieldlog.pdf]] is an example logsheet that works well for nodes, feel free to print and use!
108 108  
109 -== 2. Burial ==
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.
112 -
113 -//Don't be lazy. Do it right. //
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 -
119 -== 3. Node Placement ==
97 +== 2. Node Placement ==
120 120  )))
121 121  
122 122  **Site Analysis**:
123 123  
124 -* **Take compass measurements away from the sensor as it will affect your measurement. Use a stick or shovel to help align.**
125 -* Take photographs from various angles to document the site setup thoroughly. Have a colleague stand next to it pointing at it.
126 -* Include a detailed site description in your notes.
102 +* **Take compass measurements away from the sensor as it will affect your measurement.**
103 +* Take photographs from various angles to document the site setup thoroughly.
104 +* Include a detailed site description in your notes
127 127  
128 -== 4. GPS Considerations ==
106 +== 3. GPS Considerations ==
129 129  
130 130  (% class="wikigeneratedid" %)
131 -The GPS antenna is at the top and center of the unit, and will (usually) only receive signal with a clear sky view directly above. The signal is able to penetrate plastic and terracotta planters and a thin (2 cm?) layer of soil, but may struggle if the soil layer is too thick. **These nodes will not start recording without attaining a GPS lock** and repeated attempts will excessively drain the battery.
109 +The GPS antenna is at the top and center of the unit, and will (usually) only receive signal with a clear sky view directly above. The signal is able to penetrate plastic and terracotta planters and a thin layer of soil, but may struggle if the soil layer is too thick. **These nodes will not start recording without attaining a GPS lock** and repeated attempts will excessively drain the battery.
132 132  
133 -== 5. Visibility and Location Marking ==
111 +== 4. Visibility and Location Marking ==
134 134  
135 135  **Flag Placement**: Position a flag, preferably in a bright color (avoid green or yellow), near the instrument to aid in its future location.
136 136  
137 137  **GPS Marking**:
138 138  
139 -* Use a GPS device to mark the instrument's exact location. Most modern cell phones can get to about a 3m error with their internal GPS also; you can probably also get away with investing a few dollars in a good app that shows error and lets you log markers.
140 -* Also write the GPS down on paper (ie your [[LOG SHEET>>http://auspass.edu.au/field/NODES_blank_fieldlog.pdf]]).
117 +* Use a GPS device to mark the instrument's exact location.
118 +* Record this location in both your paper notes and the GPS device.
141 141  
142 -== (% style="color:inherit; font-family:inherit; font-size:max(18px, min(20px, 14.4444px + 0.462963vw))" %)6. Charge Time, Pre-Deployment & Post-Deployment(%%) ==
120 +== (% style="color:inherit; font-family:inherit; font-size:max(18px, min(20px, 14.4444px + 0.462963vw))" %)5. Charge Time, Pre-Deployment & Post-Deployment(%%) ==
143 143  
144 144  * **Charging Duration**: Both types of nodes take approximately 6-8 hours to fully charge from a flat state.
145 145  * **Pre-Deployment Charging**:
146 146  ** Although the nodes hold their charge well, it's beneficial to give them a "top up" charge before deployment.
125 +
147 147  * **Operational Duration**:
148 148  ** When recording at 250 Hz, with GPS on and Bluetooth disabled, the instruments are expected to last about 30 days per charge cycle. If they are set to run only overnight, this can be extended to 60 days.
149 149  
... ... @@ -158,7 +158,7 @@
158 158  ** Charge levels for transport will be advised by the freighter. The required SoC will depend on volume and transport method (air, land, sea).
159 159  
160 160  (((
161 -== 7. Data Sharing and Metadata Creation ==
140 +== 6. Data Sharing and Metadata Creation ==
162 162  )))
163 163  
164 164  **GPS Data**:
... ... @@ -173,7 +173,7 @@
173 173  
174 174  * Create and organize metadata according to the [[ANU metadata standard txt file>>attach:example_metadata.txt]]. This is going to be particularly important if you are reusing nodes at different sites... not documenting the serial numbers (of the **top half** of the node) and the times they were deployed can lead to station mix-ups.
175 175  
176 -== 8. Additional Best Practices ==
155 +== 7. Additional Best Practices ==
177 177  
178 178  * **Training and Familiarisation**: Make sure all team members are adequately trained in using the GPS devices, compass use, and other equipment to ensure consistent and accurate data collection.
179 179  
... ... @@ -439,28 +439,6 @@
439 439  
440 440  ----
441 441  
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 or OSX machine or for whatever reason. If the nodes are programmed with an output set to MiniSeed, harvesting can be as simple as reading the devices as a mounted USB device and copying off the .MiniSeed files manually.
445 -
446 -However please note the filename and channel convention. Raw data (here a BD3C-5) as usual has completely bizarre default channel codes (e.g. this should be DH?). Take care to interpret XYZ correctly though- many manufacturers will define X as East and Y as North to coincide with a typical Cartesian frame. **This is backwards here.**
447 -
448 -This raw stream...
449 -
450 -##3 Trace(s) in Stream:
451 -XX.TEST..LHX | 2026-09-01T03:26:14.000000Z - 2026-09-07T02:15:01.996000Z | 250.0 Hz, 128532000 samples
452 -XX.TEST..LHY | 2026-09-01T03:26:14.000000Z - 2026-09-07T02:15:01.996000Z | 250.0 Hz, 128532000 samples
453 -XX.TEST..LHZ | 2026-09-01T03:26:14.000000Z - 2026-09-07T02:15:01.996000Z | 250.0 Hz, 128532000 samples##
454 -
455 -Should be renamed as:
456 -
457 -##3 Trace(s) in Stream:
458 -XX.TEST..DH**N** | 2026-09-01T03:26:14.000000Z - 2026-09-07T02:15:01.996000Z | 250.0 Hz, 128532000 samples
459 -XX.TEST..DH**E** | 2026-09-01T03:26:14.000000Z - 2026-09-07T02:15:01.996000Z | 250.0 Hz, 128532000 samples
460 -XX.TEST..DH**Z** | 2026-09-01T03:26:14.000000Z - 2026-09-07T02:15:01.996000Z | 250.0 Hz, 128532000 samples##
461 -
462 -With** X = +North, Y = +East, and Z = +Z**
463 -
464 464  = Instrument Response =
465 465  
466 466  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]]
... ... @@ -472,15 +472,15 @@
472 472   'gain':1,
473 473   'sensitivity': 257019225.55108312}
474 474  
475 -[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:16HR_Z_huddle.png||alt="IGU16_Z_huddle.png"]]
432 +[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:IGU16_Z_huddle.png]]
476 476  
477 -[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz bandpass filter>>image:16HR_N_huddle.png||alt="IGU16_N_huddle.png"]]
434 +[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz bandpass filter>>image:IGU16_N_huddle.png]]
478 478  
479 479  == IGU 16-1C ==
480 480  
481 481  The 1C nodes seem to have the same response as the 3-channel IGU-16HR-3C (above), however the response posted at IRIS-NRL seems to imply that there is no poles and zeros information (e.g. a flat/linear response). This is 100% not so.
482 482  
483 -[[IGU-16 1C, X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz bandpass filter. Seems to be same response as IGU-16HR-3C.>>image:16HR1C_Z_huddle.png||alt="IGU16_1C_Z_huddle.png"]]
440 +[[IGU-16 1C, X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz bandpass filter. Seems to be same response as IGU-16HR-3C.>>image:IGU16_1C_Z_huddle.png]]
484 484  
485 485  == BD3C-5 ==
486 486  
... ... @@ -496,7 +496,7 @@
496 496  [[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz bandpass filter>>image:BD3C_N_huddle.0.5.png]]
497 497  
498 498  (% class="wikigeneratedid" %)
499 -Below the corner frequency (0.2 Hz) the phase response still fares well, but amplitude response may need to be dialed in a bit (it seems a bit high). We are working to try to calibrate this a bit better. In the next two figures the filter is **0.1** to 5 Hz:
456 +Below the corner frequency (0.2 Hz) the phase response still fares well, but amplitude response may need to be dialed in a bit (it seems a bit high). In the next two figures the filter is **0.1** to 5 Hz:
500 500  
501 501  
502 502  [[BD3C **0.1 **to 5 Hz bandpass filter>>image:BD3C_Z_huddle.0.1.png]]
16HR1C_Z_huddle.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -92.1 KB
Content
16HR_N_huddle.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -88.4 KB
Content
16HR_Z_huddle.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -80.8 KB
Content
1786503344572-296.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -1.4 MB
Content
1786503808210-822.02.28 PM.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -437.8 KB
Content
1786503812585-338.02.28 PM.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -437.8 KB
Content
BD3C_N_huddle.0.1.png
Size
... ... @@ -1,1 +1,1 @@
1 -65.9 KB
1 +72.1 KB
Content
BD3C_N_huddle.0.5.png
Size
... ... @@ -1,1 +1,1 @@
1 -68.4 KB
1 +73.3 KB
Content
BD3C_Z_huddle.0.1.png
Size
... ... @@ -1,1 +1,1 @@
1 -64.3 KB
1 +52.1 KB
Content
BD3C_Z_huddle.0.5.png
Size
... ... @@ -1,1 +1,1 @@
1 -52.5 KB
1 +64.6 KB
Content
XWiki.XWikiComments[0]
Date
... ... @@ -1,1 +1,0 @@
1 -2026-07-09 10:45:51.967
Author
... ... @@ -1,1 +1,0 @@
1 -Mark Goldman
Comment
... ... @@ -1,1 +1,0 @@
1 -I can verify that the default orientation for the SmartSolo 3C nodes is positive values for case motion to the South, West, and downwards. We have co-located nodes with permanent stations and noticed this correlation when comparing waveforms.