Skip to Content
Last modified by robert on 2026/08/12 13:08
From version 117.1
edited by robert
on 2026/08/12 12:50
Change comment: There is no comment for this version
To version 105.5
edited by robert
on 2026/02/17 15:49
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -73,18 +73,6 @@
73 73  
74 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 12v 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,36 +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 -== 3. Node Placement ==
97 +== 2. Node Placement ==
112 112  )))
113 113  
114 114  **Site Analysis**:
115 115  
116 -* **Take compass measurements away from the sensor as it will affect your measurement. Use a stick or shovel to help align.**
117 -* Take photographs from various angles to document the site setup thoroughly. Have a colleague stand next to it pointing at it.
118 -* 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
119 119  
120 -== 4. GPS Considerations ==
106 +== 3. GPS Considerations ==
121 121  
122 122  (% class="wikigeneratedid" %)
123 -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.
124 124  
125 -== 5. Visibility and Location Marking ==
111 +== 4. Visibility and Location Marking ==
126 126  
127 127  **Flag Placement**: Position a flag, preferably in a bright color (avoid green or yellow), near the instrument to aid in its future location.
128 128  
129 129  **GPS Marking**:
130 130  
131 -* 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.
132 -* 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.
133 133  
134 -== (% 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(%%) ==
135 135  
136 136  * **Charging Duration**: Both types of nodes take approximately 6-8 hours to fully charge from a flat state.
137 137  * **Pre-Deployment Charging**:
138 138  ** Although the nodes hold their charge well, it's beneficial to give them a "top up" charge before deployment.
125 +
139 139  * **Operational Duration**:
140 140  ** 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.
141 141  
... ... @@ -150,7 +150,7 @@
150 150  ** Charge levels for transport will be advised by the freighter. The required SoC will depend on volume and transport method (air, land, sea).
151 151  
152 152  (((
153 -== 7. Data Sharing and Metadata Creation ==
140 +== 6. Data Sharing and Metadata Creation ==
154 154  )))
155 155  
156 156  **GPS Data**:
... ... @@ -165,7 +165,7 @@
165 165  
166 166  * 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.
167 167  
168 -== 8. Additional Best Practices ==
155 +== 7. Additional Best Practices ==
169 169  
170 170  * **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.
171 171  
... ... @@ -325,7 +325,7 @@
325 325  
326 326  * Once a new project is created, the Data Transfer View panel will display connected nodes with details like series number and data size.
327 327  * If “Prospect not matched” appears, it simply means the new project doesn’t match the original programming project. This is not a concern.
328 -* Select all nodes and right-click to “force download”. This starts the download process.[[image:Smartsolo harvesting #4 copy.png]]
315 +* Select all nodes and right-click to “force download”. This starts the download process.
329 329  * Completed downloads will appear as new folders in the Downloaded Data panel.
330 330  )))
331 331  1. (((
... ... @@ -332,17 +332,14 @@
332 332  **Exporting Data in Readable Format**:
333 333  
334 334  * Go to the “Tool” menu and select “export seismic data”.
335 -* Tailor other parameters to project preference and ensure "Sample Interval" matches the setting used during node reset (note: the standard used by ANU is 4ms, or 250hz)
322 +* Tailor other parameters to personal preference and ensure "Sample Interval" matches the setting used during node reset.
323 +* Click “prepare” followed by “run” to start reformatting. Monitor this process in the small panel at the bottom left.
336 336  * (% class="box warningmessage" %)
337 337  (((
338 -**Ensure export data is set to "COUNTS" (int32), not "mV" (float). This is critical!**
326 +* **Ensure to export data as "COUNTS" (int32), not "mV" (float). This is critical!**
327 +
328 +* **Set "Remove Gain" to the same decibel gain as during programming. By default ANU sets this to 24db for short period nodes (a scaling factor of 15.848932), and 6db (a factor of 2.0) for broadband nodes.**
339 339  )))
340 -* Set "Remove Gain" to the same decibel gain as during programming. By default ANU sets this to 24db for short period nodes (a scaling factor of 15.848932), and 6db (a factor of 2.0) for broadband nodes.
341 -* Set "Remove DC" to "Yes" to centre the data around the zero value
342 -* Set the correct Start Time (UTC) and End Time (UTC) of the project to prevent the unnecessary export of older data
343 -* [[image:Smartsolo harvesting #9 copy.png]]
344 -* Click “prepare” followed by “run” to start reformatting. Monitor this process in the small panel at the bottom left.
345 -* The data will be exported to the SOLODATA folder. For a windows system, the following file explorer page is where you must navigate to to locate your project folder[[image:Smartsolo harvesting #8 copy.png]]
346 346  )))
347 347  
348 348  == Smart Solo IGU-16HR Polarity Notice ==
... ... @@ -409,8 +409,11 @@
409 409  **Finalizing the Download**:
410 410  
411 411  * After downloading, mark the //"D"// box on your temporary labels to indicate completion.
396 +
397 +
412 412  )))
413 413  
400 +[[image:1706153266647-145.png||data-xwiki-image-style-alignment="center" height="340" width="603"]]
414 414  
415 415  
416 416  
... ... @@ -442,16 +442,14 @@
442 442   'gain':1,
443 443   'sensitivity': 257019225.55108312}
444 444  
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"]]
432 +[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:IGU16_Z_huddle.png]]
446 446  
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"]]
434 +[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:IGU16_N_huddle.png]]
448 448  
449 449  == IGU 16-1C ==
450 450  
451 -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.
438 +The 1C nodes seem to have a slightly different response to the 3C (TBA)
452 452  
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"]]
454 -
455 455  == BD3C-5 ==
456 456  
457 457   'BD3C': {'poles':[(-1720.4+0j), (-1.2+0.9j), (-1.2-0.9j)],
... ... @@ -459,23 +459,23 @@
459 459   'gain':1.69726e-05,
460 460   'sensitivity': 702651512.6046528}
461 461  
462 -Above 0.5 Hz, the BD3C-5 response fits well:
447 +[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:BD3C_Z_huddle.png]]
463 463  
464 -[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:BD3C_Z_huddle.0.5.png]]
449 +[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:BD3C_N_huddle.png]]
465 465  
466 -[[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]]
451 +(% class="wikigeneratedid" %)
452 +Below the corner frequency 0.2 Hz (i.e. 5 seconds) the response still does a good job, but may need to be dialed in a bit. We are looking into this.
467 467  
468 468  (% class="wikigeneratedid" %)
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:
455 +
470 470  
457 +[[BD3C 0.1 to 5 Hz bandpass>>image:BD3C_Z_huddle.0.1.png]]
471 471  
472 -[[BD3C **0.1 **to 5 Hz bandpass filter>>image:BD3C_Z_huddle.0.1.png]]
459 +[[BD3C 0.1 to 5 Hz bandpass>>image:BD3C_N_huddle.0.1.png]]
473 473  
474 -[[BD3C **0.1** to 5 Hz bandpass filter>>image:BD3C_N_huddle.0.1.png]]
475 -
476 476  == IGU-16 Horizontal noise & how to avoid ==
477 477  
478 -The** 5 Hz nodes** are susceptible to horizontal noise due to the placement of geophones in the units, **but this can be mitigated by completely burying the units flush with the ground.** In the below example, the node was set on the floor of our basement set on its plastic carrying case support. As such the amount of horizontal noise noticeably increases above ~~ 10Hz.
463 +The** 5 Hz nodes** are susceptible to horizontal noise due to the placement of geophones in the units, **but this can be mitigated by completely burying the units flush with the ground.** In the below example, the node was set on the floor of our basement set on its plastic carrying case support. As such the amount of horizontal noise noticeably increases above ~~ 10Hz.
479 479  
480 480  [[IGU-16HR-3C Power spectrum huddle test vs a CMG-6TD (S1) and TC120/Centaur combo. The N and E channels have excess noise above 10Hz due to "sticking up" out of the ground.>>image:IGU16_spectrum.png]]
481 481  
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
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
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -68.4 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
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -52.5 KB
Content
IGU16_1C_Z_huddle.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -72.3 KB
Content
Smartsolo harvesting #4 copy.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -33.8 KB
Content
Smartsolo harvesting #4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -33.8 KB
Content
Smartsolo harvesting #6 copy.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -33.6 KB
Content
Smartsolo harvesting #8 copy.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -38.3 KB
Content
Smartsolo harvesting #8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -60.0 KB
Content
Smartsolo harvesting #9 copy.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -28.7 KB
Content
XWiki.XWikiComments[0]
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.
Date
... ... @@ -1,1 +1,0 @@
1 -2026-07-09 10:45:51.967