Skip to Content
Last modified by robert on 2026/08/12 13:08
From version 107.1
edited by robert
on 2026/02/17 16:28
Change comment: There is no comment for this version
To version 119.1
edited by robert
on 2026/08/12 13:08
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -73,6 +73,18 @@
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 +
76 76  = **Installation** =
77 77  
78 78  (% class="box infomessage" %)
... ... @@ -94,35 +94,44 @@
94 94  
95 95  [[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!
96 96  
97 -== 2. Node Placement ==
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 ==
98 98  )))
99 99  
100 100  **Site Analysis**:
101 101  
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
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.
105 105  
106 -== 3. GPS Considerations ==
128 +== 4. GPS Considerations ==
107 107  
108 108  (% class="wikigeneratedid" %)
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.
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.
110 110  
111 -== 4. Visibility and Location Marking ==
133 +== 5. Visibility and Location Marking ==
112 112  
113 113  **Flag Placement**: Position a flag, preferably in a bright color (avoid green or yellow), near the instrument to aid in its future location.
114 114  
115 115  **GPS Marking**:
116 116  
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.
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]]).
119 119  
120 -== (% style="color:inherit; font-family:inherit; font-size:max(18px, min(20px, 14.4444px + 0.462963vw))" %)5. Charge Time, Pre-Deployment & Post-Deployment(%%) ==
142 +== (% style="color:inherit; font-family:inherit; font-size:max(18px, min(20px, 14.4444px + 0.462963vw))" %)6. Charge Time, Pre-Deployment & Post-Deployment(%%) ==
121 121  
122 122  * **Charging Duration**: Both types of nodes take approximately 6-8 hours to fully charge from a flat state.
123 123  * **Pre-Deployment Charging**:
124 124  ** Although the nodes hold their charge well, it's beneficial to give them a "top up" charge before deployment.
125 -
126 126  * **Operational Duration**:
127 127  ** 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.
128 128  
... ... @@ -137,7 +137,7 @@
137 137  ** Charge levels for transport will be advised by the freighter. The required SoC will depend on volume and transport method (air, land, sea).
138 138  
139 139  (((
140 -== 6. Data Sharing and Metadata Creation ==
161 +== 7. Data Sharing and Metadata Creation ==
141 141  )))
142 142  
143 143  **GPS Data**:
... ... @@ -152,7 +152,7 @@
152 152  
153 153  * 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.
154 154  
155 -== 7. Additional Best Practices ==
176 +== 8. Additional Best Practices ==
156 156  
157 157  * **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.
158 158  
... ... @@ -312,7 +312,7 @@
312 312  
313 313  * Once a new project is created, the Data Transfer View panel will display connected nodes with details like series number and data size.
314 314  * If “Prospect not matched” appears, it simply means the new project doesn’t match the original programming project. This is not a concern.
315 -* Select all nodes and right-click to “force download”. This starts the download process.
336 +* Select all nodes and right-click to “force download”. This starts the download process.[[image:Smartsolo harvesting #4 copy.png]]
316 316  * Completed downloads will appear as new folders in the Downloaded Data panel.
317 317  )))
318 318  1. (((
... ... @@ -319,14 +319,17 @@
319 319  **Exporting Data in Readable Format**:
320 320  
321 321  * Go to the “Tool” menu and select “export seismic data”.
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.
343 +* 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)
324 324  * (% class="box warningmessage" %)
325 325  (((
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.**
346 +**Ensure export data is set to "COUNTS" (int32), not "mV" (float). This is critical!**
329 329  )))
348 +* 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.
349 +* Set "Remove DC" to "Yes" to centre the data around the zero value
350 +* Set the correct Start Time (UTC) and End Time (UTC) of the project to prevent the unnecessary export of older data
351 +* [[image:Smartsolo harvesting #9 copy.png]]
352 +* Click “prepare” followed by “run” to start reformatting. Monitor this process in the small panel at the bottom left.
353 +* 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]]
330 330  )))
331 331  
332 332  == Smart Solo IGU-16HR Polarity Notice ==
... ... @@ -393,11 +393,8 @@
393 393  **Finalizing the Download**:
394 394  
395 395  * After downloading, mark the //"D"// box on your temporary labels to indicate completion.
396 -
397 -
398 398  )))
399 399  
400 -[[image:1706153266647-145.png||data-xwiki-image-style-alignment="center" height="340" width="603"]]
401 401  
402 402  
403 403  
... ... @@ -429,15 +429,15 @@
429 429   'gain':1,
430 430   'sensitivity': 257019225.55108312}
431 431  
432 -[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:IGU16_Z_huddle.png]]
453 +[[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"]]
433 433  
434 -[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:IGU16_N_huddle.png]]
455 +[[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"]]
435 435  
436 436  == IGU 16-1C ==
437 437  
438 438  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.
439 439  
440 -[[IGU-16 1C, X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter. Seems to be same response as IGU-16HR-3C.>>image:IGU16_1C_Z_huddle.png]]
461 +[[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"]]
441 441  
442 442  == BD3C-5 ==
443 443  
... ... @@ -446,17 +446,19 @@
446 446   'gain':1.69726e-05,
447 447   'sensitivity': 702651512.6046528}
448 448  
449 -[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:BD3C_Z_huddle.png]]
470 +Above 0.5 Hz, the BD3C-5 response fits well:
450 450  
451 -[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:BD3C_N_huddle.png]]
472 +[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:BD3C_Z_huddle.0.5.png]]
452 452  
474 +[[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]]
475 +
453 453  (% class="wikigeneratedid" %)
454 -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.
477 +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 455  
456 456  
457 -[[BD3C 0.1 to 5 Hz bandpass>>image:BD3C_Z_huddle.0.1.png]]
480 +[[BD3C **0.1 **to 5 Hz bandpass filter>>image:BD3C_Z_huddle.0.1.png]]
458 458  
459 -[[BD3C 0.1 to 5 Hz bandpass>>image:BD3C_N_huddle.0.1.png]]
482 +[[BD3C **0.1** to 5 Hz bandpass filter>>image:BD3C_N_huddle.0.1.png]]
460 460  
461 461  == IGU-16 Horizontal noise & how to avoid ==
462 462  
BD3C_N_huddle.0.1.png
Size
... ... @@ -1,1 +1,1 @@
1 -72.1 KB
1 +65.9 KB
Content
BD3C_Z_huddle.0.1.png
Size
... ... @@ -1,1 +1,1 @@
1 -52.1 KB
1 +64.3 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
1786503344572-296.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.robert
Size
... ... @@ -1,0 +1,1 @@
1 +1.4 MB
Content
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
BD3C_N_huddle.0.5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.robert
Size
... ... @@ -1,0 +1,1 @@
1 +68.4 KB
Content
BD3C_Z_huddle.0.5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.robert
Size
... ... @@ -1,0 +1,1 @@
1 +52.5 KB
Content
Smartsolo harvesting #4 copy.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.JackD
Size
... ... @@ -1,0 +1,1 @@
1 +33.8 KB
Content
Smartsolo harvesting #4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.JackD
Size
... ... @@ -1,0 +1,1 @@
1 +33.8 KB
Content
Smartsolo harvesting #6 copy.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.JackD
Size
... ... @@ -1,0 +1,1 @@
1 +33.6 KB
Content
Smartsolo harvesting #8 copy.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.JackD
Size
... ... @@ -1,0 +1,1 @@
1 +38.3 KB
Content
Smartsolo harvesting #8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.JackD
Size
... ... @@ -1,0 +1,1 @@
1 +60.0 KB
Content
Smartsolo harvesting #9 copy.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.JackD
Size
... ... @@ -1,0 +1,1 @@
1 +28.7 KB
Content
XWiki.XWikiComments[0]
Date
... ... @@ -1,0 +1,1 @@
1 +2026-07-09 10:45:51.967
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.