Skip to Content
Last modified by robert on 2026/08/12 13:08
From version 112.1
edited by robert
on 2026/06/17 16:54
Change comment: There is no comment for this version
To version 117.1
edited by robert
on 2026/08/12 12:50
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -83,6 +83,8 @@
83 83  
84 84  - IGU16-HR 1C: ~~7 days of recording per 1 Ah
85 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 +
86 86  = **Installation** =
87 87  
88 88  (% class="box infomessage" %)
... ... @@ -104,7 +104,9 @@
104 104  
105 105  [[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!
106 106  
107 -== 2. Node Placement ==
109 +== 2. Burial ==
110 +
111 +== 3. Node Placement ==
108 108  )))
109 109  
110 110  **Site Analysis**:
... ... @@ -113,12 +113,12 @@
113 113  * Take photographs from various angles to document the site setup thoroughly. Have a colleague stand next to it pointing at it.
114 114  * Include a detailed site description in your notes.
115 115  
116 -== 3. GPS Considerations ==
120 +== 4. GPS Considerations ==
117 117  
118 118  (% class="wikigeneratedid" %)
119 119  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.
120 120  
121 -== 4. Visibility and Location Marking ==
125 +== 5. Visibility and Location Marking ==
122 122  
123 123  **Flag Placement**: Position a flag, preferably in a bright color (avoid green or yellow), near the instrument to aid in its future location.
124 124  
... ... @@ -127,12 +127,11 @@
127 127  * 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.
128 128  * Also write the GPS down on paper (ie your [[LOG SHEET>>http://auspass.edu.au/field/NODES_blank_fieldlog.pdf]]).
129 129  
130 -== (% style="color:inherit; font-family:inherit; font-size:max(18px, min(20px, 14.4444px + 0.462963vw))" %)5. Charge Time, Pre-Deployment & Post-Deployment(%%) ==
134 +== (% style="color:inherit; font-family:inherit; font-size:max(18px, min(20px, 14.4444px + 0.462963vw))" %)6. Charge Time, Pre-Deployment & Post-Deployment(%%) ==
131 131  
132 132  * **Charging Duration**: Both types of nodes take approximately 6-8 hours to fully charge from a flat state.
133 133  * **Pre-Deployment Charging**:
134 134  ** Although the nodes hold their charge well, it's beneficial to give them a "top up" charge before deployment.
135 -
136 136  * **Operational Duration**:
137 137  ** 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.
138 138  
... ... @@ -147,7 +147,7 @@
147 147  ** Charge levels for transport will be advised by the freighter. The required SoC will depend on volume and transport method (air, land, sea).
148 148  
149 149  (((
150 -== 6. Data Sharing and Metadata Creation ==
153 +== 7. Data Sharing and Metadata Creation ==
151 151  )))
152 152  
153 153  **GPS Data**:
... ... @@ -162,7 +162,7 @@
162 162  
163 163  * 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.
164 164  
165 -== 7. Additional Best Practices ==
168 +== 8. Additional Best Practices ==
166 166  
167 167  * **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.
168 168  
... ... @@ -439,15 +439,15 @@
439 439   'gain':1,
440 440   'sensitivity': 257019225.55108312}
441 441  
442 -[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:IGU16_Z_huddle.png]]
445 +[[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"]]
443 443  
444 -[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz bandpass filter>>image:IGU16_N_huddle.png]]
447 +[[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"]]
445 445  
446 446  == IGU 16-1C ==
447 447  
448 448  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.
449 449  
450 -[[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]]
453 +[[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"]]
451 451  
452 452  == BD3C-5 ==
453 453  
... ... @@ -463,7 +463,7 @@
463 463  [[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]]
464 464  
465 465  (% class="wikigeneratedid" %)
466 -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:
469 +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:
467 467  
468 468  
469 469  [[BD3C **0.1 **to 5 Hz bandpass filter>>image:BD3C_Z_huddle.0.1.png]]
BD3C_N_huddle.0.1.png
Size
... ... @@ -1,1 +1,1 @@
1 -72.1 KB
1 +65.9 KB
Content
BD3C_N_huddle.0.5.png
Size
... ... @@ -1,1 +1,1 @@
1 -73.3 KB
1 +68.4 KB
Content
BD3C_Z_huddle.0.1.png
Size
... ... @@ -1,1 +1,1 @@
1 -52.1 KB
1 +64.3 KB
Content
BD3C_Z_huddle.0.5.png
Size
... ... @@ -1,1 +1,1 @@
1 -64.6 KB
1 +52.5 KB
Content
16HR1C_Z_huddle.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.robert
Size
... ... @@ -1,0 +1,1 @@
1 +92.1 KB
Content
16HR_N_huddle.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.robert
Size
... ... @@ -1,0 +1,1 @@
1 +88.4 KB
Content
16HR_Z_huddle.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.robert
Size
... ... @@ -1,0 +1,1 @@
1 +80.8 KB
Content
XWiki.XWikiComments[0]
Author
... ... @@ -1,0 +1,1 @@
1 +Mark Goldman
Comment
... ... @@ -1,0 +1,1 @@
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.
Date
... ... @@ -1,0 +1,1 @@
1 +2026-07-09 10:45:51.967