Skip to Content
Last modified by robert on 2025/10/29 10:39
From version 85.1
edited by Jack Dent
on 2025/09/29 12:55
Change comment: There is no comment for this version
To version 59.5
edited by robert
on 2025/07/16 15:58
Change comment: clear view right for XWiki.XWikiAllGroup

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.JackD
1 +XWiki.robert
Content
... ... @@ -4,70 +4,34 @@
4 4  (((
5 5  = **Node Types** =
6 6  
7 -ANSIR carry two types of three-channel nodes, and one type of one-channel node:
7 +ANSIR carry two types of three-channel nodes
8 8  
9 9  * **SmartSolo IGU 16HR 3C (5 Hz Short Period)**
10 -* **SmartSolo BD3C-5 (5 Second Broadband)**
11 -* **SmartSolo IGU 16 1C (5 Hz Short Period, single channel)**
10 +* **SmartSolo BD3C-5 (5 Second Broad-Band)**
12 12  
13 -The three-channel nodes have a battery capacity of ~~30 days, whereas the single-channel type has a capacity of ~~50 days. The programming, operation and downloading procedures for all types of SmartSolo nodes are also similar.
12 +Both have a battery capacity of around 30 days. The programming, operation, and downloading procedures for both types of SmartSolo nodes are also similar.
14 14  
14 +
15 15  ----
16 16  
17 17  = **Programming Defaults** =
18 18  
19 -SmartSolo provides the following powerpoint for SmartSolo node programming and operation. Note that ANSIR only uses a portion of their process for our own uses: [[https:~~/~~/nappe.wustl.edu/smartsolo/files/smartsolo_online_training.pdf>>https://nappe.wustl.edu/smartsolo/files/smartsolo_online_training.pdf]]
19 +We recommend that the SP 16HR-3C be set to a gain of 24db and no higher than 250 Hz sampling rate unless there is an explicit reason to do so. The BD3C-5 should be set to a gain of 6db (which is the maximum allowed). These are what we use for our internal experiments.
20 20  
21 -The nodes must be programmed in the SoloLite software prior to use. Screenshots for the short period 16HR-3C and broadband BDC3-5 are shown with our recommended parameters.
21 +**Note that this gain must be removed when exporting to miniseed, **otherwise amplitudes will be a factor of either 15.84893192 (24db) or 2 (6db) too high. We also recommend disabling bluetooth to increase battery life, and to enable "FIFO" mode just in case old data is still present on the units and you run out of space (although it is unlikely you will go over 64 Gb for one deploy). If using the "timed turn-on" option, please be aware that **the units will not begin recording until they have acquired a GPS lock**, which may nor occur if they are buried too deeply or have very poor sky view.
22 22  
23 -[[IGU-16 3C (short period node) programming screen set at 250 Hz. Ensure that the highlighted areas are set!>>image:SP_programming.labels.png||alt="IGU-16 3C programming screen"]]
24 24  
25 -[[BD3C-5 (broadband node) programming screen set at 250 hz. Ensure that the highlighted areas are set!>>image:BB_programming.labels.png||alt="BD3C-5 programming screen"]]
26 -
27 -FIFO (first in, first out) data mode is safest as this will overwrite old data in case you forgot to clear the storage. At <= 250 hz you can fit 4++ months of data on these, shouldn't be an issue.
28 -
29 -Note that the samplerate is instead given in sample spacing, in milliseconds. 4 ms = 250 Hz, 1 ms = 1000 Hz, 10 ms = 100 Hz, ad nauseam.
30 -
31 -Be sure to set the channel types to Seismic and the gain appropriately. For active source (i.e. explosions) you can leave the gain at 0, but for passive experiments some gain is purported to be helpful (although we have found this to be somewhat negligible). We can confirm that 6db for the broadband nodes and 24db for the short period works well.
32 -
33 -If you want recording to begin immediately, ensure that begin date is in the past by at least a few days. If you prefer to have a timed turn-on, then set the times as needed. **Be warned that recording will not begin until a GPS lock is achieved, so if you set it to a future turn-on but bury it too deeply, it may not record!**
34 -
35 -In newer versions of the software there is a "power consumption" setting.. we are no sure what this does exactly, but the manual says it gives life a "boost" at the expense of about 3 db of resolution. Until this can be quantified a bit better it is not recommended.
36 -
37 -Storage type can be DLD (proprietary) or Miniseed. We assume the software works best with their proprietary format so prefer not to risk any issues. You can export to miniseed later.
38 -
39 -GPS is best set to cycle mode (e.g. once per hour) instead of constant "always on". The clock drift on these are almost nil even if there is no sync at all, so it's best to conserve power.
40 -
41 -Bluetooth (BB nodes only) should be turned OFF to conserve power.
42 -
43 -We recommend that the SP 16HR-3C be set to a gain of 24db for passive experiments and no higher than 250 Hz sampling rate unless there is an explicit reason to do so. The BD3C-5 should be set to a gain of 6db (which is the maximum allowed) for passive experiments (or 0 db if active).
44 -
45 -{{info}}
46 -**Note that any applied instrument gain must be removed when exporting (e.g. to miniseed) after your deploy, **otherwise amplitudes will be a factor of either 15.84893192 (24db) or 2 (6db) too high!
47 -{{/info}}
48 -
49 -=== **Programming tips**: ===
50 -
51 -Connecting SmartSolo nodes to their harvesters and having SoloLite recognise them can be a bit tricky, here are some tricks to help register and program them easier:
52 -
53 - - Place the node on the harvester gently, then firmly press it down onto the pins
54 -
55 - - Place all nodes onto the harvester before trying any troubleshooting, as they may not show up while the SoloLite software is running. Once all are connected, try  restarting the software for them to be recognised.
56 -
57 - - If a node is refusing to connect, try it with another slot. It is easiest if you place all 16 nodes on the harvester, and swap any nodes that refuse to connect with eachother
58 -
59 - - Nodes will likely not show up in the order that they should, though this is not an issue. Eg, a node in slot 6 on the harvester may show up in port 13 in the SoloLite software
60 -
61 61  = **Fieldwork Preparation** =
62 62  
26 +(% class="box infomessage" %)
27 +(((
63 63  (% class="box warningmessage" %)
64 64  (((
65 65  **INVEST IN FAST EXTERNAL HARD DRIVES – DO NOT LET THIS BE THE LIMITATION OF DATA HARVESTING**
66 66  
67 67  **Assume ~~1 Tb of storage for both raw and exported data per 50 nodes @ 250 Hz & 30 days. One node recording at 250 Hz for 30 days tends to create about 3 Gb of miniseed data.**
68 -
69 -**We have had good experience with the 4Tb Samsung T7 Shield drives.**
70 70  )))
34 +)))
71 71  
72 72  == Magnets ==
73 73  
... ... @@ -79,26 +79,19 @@
79 79  
80 80  = **Installation** =
81 81  
82 -(% class="box infomessage" %)
83 -(((
84 -**Field logs are a critical component of fieldwork and this is especially the case for large N nodal deploys. Take notes!**
85 -)))
46 +== **1. Logbook documentation** ==
86 86  
87 -== 1. Logbook documentation ==
88 -
89 89  (((
90 -**Essential Details** for field logs:
49 +**Essential Details**: Record the following in a logbook:
91 91  
92 92  * Station name
93 -* Latitude, longitude, elevation
52 +* Latitude and longitude
94 94  * Names of team members present
95 -* Date and both local & UTC time of installation/removal
96 -* Serial number (SN) of the TOP HALF of the sensor (if a BD3C-5, there is only one serial number)
97 -* Detailed notes on the site conditions and setup, anything else that will be helpful to find it again ("by the fence", "south of rock", etc)
54 +* Date and local time of installation
55 +* Serial number (SN) of the sensor
56 +* Detailed notes on the site conditions and setup
98 98  
99 -[[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!
100 -
101 -== 2. Node Placement ==
58 +== **2. Node Placement** ==
102 102  )))
103 103  
104 104  **Protection**: Place nodes inside (landfill) biodegradable bags to minimize cleaning and cross-site soil contamination.
... ... @@ -106,15 +106,15 @@
106 106  **Site Analysis**:
107 107  
108 108  * **Take compass measurements away from the sensor as it will affect your measurement.**
109 -* Take photographs from various angles to document the site setup thoroughly.
110 -* Include a detailed site description in your notes
66 +* Take multiple photographs from various angles to document the site setup thoroughly.
67 +* Include a detailed site description in your notes, specifying distances and orientations from nearby landmarks (e.g. Richards garden, Te Mini steam field eastern side)
111 111  
112 -== 3. GPS Considerations ==
69 +== **3. GPS Considerations** ==
113 113  
114 114  (% class="wikigeneratedid" %)
115 115  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.
116 116  
117 -== 4. Visibility and Location Marking ==
74 +== **4. Visibility and Location Marking** ==
118 118  
119 119  **Flag Placement**: Position a flag, preferably in a bright color (avoid green or yellow), near the instrument to aid in its future location.
120 120  
... ... @@ -123,7 +123,7 @@
123 123  * Use a GPS device to mark the instrument's exact location.
124 124  * Record this location in both your paper notes and the GPS device.
125 125  
126 -== (% style="color:inherit; font-family:inherit; font-size:max(18px, min(20px, 14.4444px + 0.462963vw))" %)5. Charge Time, Pre-Deployment & Post-Deployment(%%) ==
83 +== (% style="color:inherit; font-family:inherit; font-size:max(18px, min(20px, 14.4444px + 0.462963vw))" %)**5. Charge Time, Pre-Deployment & Post-Deployment**(%%) ==
127 127  
128 128  * **Charging Duration**: Both types of nodes take approximately 6-8 hours to fully charge from a flat state.
129 129  * **Pre-Deployment Charging**:
... ... @@ -137,10 +137,10 @@
137 137  * **Storage and Shipping Charge Level**:
138 138  ** Maintain a battery charge level of around 50-60% (e.g. "orange") for both storage and shipping purposes.
139 139  ** This charge level is recommended to prevent battery damage and is safe for transportation.
140 -** Nodes should not be stored fully charged, and **they should especially not be stored with 0 charge as this damages lithium batteries.**
97 +** Nodes should not be stored fully charged, and it **they should especially not be stored with 0 charge.**
141 141  
142 142  (((
143 -== 6. Data Sharing and Metadata Creation ==
100 +== **6. Data Sharing and Metadata Creation** ==
144 144  )))
145 145  
146 146  **GPS Data**:
... ... @@ -153,9 +153,9 @@
153 153  
154 154  **Metadata File**:
155 155  
156 -* 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.
113 +* Create and organize metadata according to the [[ANU metadata standard txt file>>attach:example_metadata.txt]].
157 157  
158 -== 7. Additional Best Practices ==
115 +== **7. Additional Best Practices** ==
159 159  
160 160  * **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.
161 161  
... ... @@ -210,25 +210,25 @@
210 210  = **Charging Procedure for Seismic Nodes** =
211 211  
212 212  (((
213 -== 1. Preparation for Charging: ==
170 +== **1. Preparation for Charging**: ==
214 214  
215 215  * Before charging, ensure each node is clean. This involves removing any dirt or debris to maintain the integrity of the equipment and ensure effective charging.
216 216  )))
217 217  
218 218  (((
219 -== 2. Disassembling the Node: ==
176 +== **2. Disassembling the Node**: ==
220 220  
221 221  * For the IGU-16HR, remove the battery (bottom half) from the sensor. This is done by unscrewing the spikes counter-clockwise.
222 222  )))
223 223  
224 224  (((
225 -== 3. Setting Nodes in the Charging Box: ==
182 +== **3. Setting Nodes in the Charging Box**: ==
226 226  
227 227  * Place 1-16 IGU-16HR battery components upside-down into the charger, assuring they are oriented properly.
228 228  )))
229 229  
230 230  (((
231 -== 4. Monitoring the Charging Process: ==
188 +== **4. Monitoring the Charging Process**: ==
232 232  
233 233  * Once the nodes are set in the charging box and the charging process begins, lights adjacent to the batteries will illuminate. These lights indicate that charging is underway.
234 234  * Observe the transition of the lights from steady red to orange, then to green, and finally to flashing green. A flashing green light signifies that the batteries are fully charged. For storage, the goal is to charge them to ORANGE.
... ... @@ -235,7 +235,7 @@
235 235  )))
236 236  
237 237  (((
238 -== 5. Updating Charge Status: ==
195 +== **5. Updating Charge Status**: ==
239 239  
240 240  * During the charging period, take this opportunity to update the status of each unit. Check the //"C"// box on your temporary labels to indicate that the unit has been successfully charged.
241 241  * This step is crucial for tracking the charging status of multiple units, especially when handling a large number of nodes.
... ... @@ -252,7 +252,7 @@
252 252  
253 253  = **Downloading and Converting Seismic Data to MiniSeed Format** =
254 254  
255 -== Node Registration and Software Setup ==
212 +== **Node Registration and Software Setup** ==
256 256  
257 257  1. (((
258 258  **Registering Nodes in the System**:
... ... @@ -270,7 +270,7 @@
270 270  * Ignore the settings for seismic recordings in the subsequent window. Resetting instruments (e.g., sampling rate, gain) requires reprogramming via script.
271 271  )))
272 272  
273 -== Data Downloading Process ==
230 +== **Data Downloading Process** ==
274 274  
275 275  1. (((
276 276  **Initiating Data Download**:
... ... @@ -288,18 +288,14 @@
288 288  * Click “prepare” followed by “run” to start reformatting. Monitor this process in the small panel at the bottom left.
289 289  * (% class="box warningmessage" %)
290 290  (((
291 -* **Ensure to export data as "COUNTS" (int32), not "mV" (float). This is critical!**
248 +* **Ensure to export data as "COUNTS", not "mV".**
292 292  
293 -* **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.**
250 +* **Set "Remove Gain" to the same decibel gain as during programming** **(by default ANU sets this to 24db for short period nodes (a factor of 15.848932), and 6db for broadband nodes).**
294 294  )))
295 295  )))
296 296  
297 -== Smart Solo Z Polarity bug ==
254 +== **Handling Nodes During Download** ==
298 298  
299 -See [[https:~~/~~/auspass.edu.au/xwiki/bin/view/Data/AusPass%20Data/#HSmartSoloNodeZPolaritybug>>https://auspass.edu.au/xwiki/bin/view/Data/AusPass%20Data/#HSmartSoloNodeZPolaritybug]] for discussion. If data is headed to AusPass, we prefer to invert the IGU-16HR 3 Z channel data manually rather than invert the response metadata. The BD3C-5 data does not require a polarity inversion.
300 -
301 -== Handling Nodes During Download ==
302 -
303 303  1. (((
304 304  **Monitoring Download Indicators**:
305 305  
... ... @@ -315,7 +315,6 @@
315 315  * **Use fast external hard drives to avoid limitations in data harvesting.**
316 316  
317 317  * **Recommended specifications: USB-C, USB 3.0, and 4+ Tb of space.**
318 -* **The USB type for the harvester is TYPE-A, the typical normal rectangular shape.**
319 319  )))
320 320  )))
321 321  1. (((
... ... @@ -355,7 +355,7 @@
355 355  
356 356  = **Cleaning** =
357 357  
358 -When still connected, the nodes are water resistant (don't submerge them!) and can handle a good spray / wipe-down. A strong, non-wire brush is helpful to reach areas between the metal spikes on the bottom.
310 +When still connected, the nodes are water resistant (don't submerge them!) and can handle a good spray / wipedown. A strong, non-wire brush is helpful to reach areas between the metal spikes on the bottom.
359 359  
360 360  = **Weights (for shipping)** =
361 361  
... ... @@ -393,7 +393,7 @@
393 393  
394 394  |(% style="width:189px" %)**Frequency Band**|(% style="width:221px" %)5 Seconds to 150Hz
395 395  |(% style="width:189px" %)**Sensitivity**|(% style="width:221px" %)200 V/m/s
396 -|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)Φ158 x160mm(H)
348 +|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)158 x160mm
397 397  |(% style="width:189px" %)**Weight**|(% style="width:221px" %)2.8 kg
398 398  |(% style="width:189px" %)**Data Storage**|(% style="width:221px" %)64 Gb
399 399  |(% style="width:189px" %)**Battery**|(% style="width:221px" %)(((
... ... @@ -405,7 +405,7 @@
405 405  
406 406  (% class="box" %)
407 407  (((
408 -= SmartSolo [[IGU-16HR>>url:https://smartsolo.com/cp-3.html]]3C =
360 += SmartSolo [[IGU-16HR>>url:https://smartsolo.com/cp-3.html]] =
409 409  
410 410  [[image:smartsolo node.jpg]]
411 411  
... ... @@ -412,8 +412,8 @@
412 412  [[image:smartsolo node 2.jpg]]
413 413  
414 414  |(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 1652Hz
415 -|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)76.7 V/m/s
416 -|(% style="width:187px" %)**Size (with spike)**|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm(H)
367 +|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)67.7 V/m/s
368 +|(% style="width:187px" %)**Size (with spike)**|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm
417 417  |(% style="width:187px" %)**Weight**|(% style="width:224px" %)2.4 kg
418 418  |(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)64 Gb
419 419  |(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((
... ... @@ -423,99 +423,6 @@
423 423  )))
424 424  )))
425 425  
426 -(% class="box" %)
427 -(((
428 428  
429 -
430 -= SmartSolo [[IGU-16>>url:https://smartsolo.com/cp-3.html]]1C =
431 -
432 -
433 -[[image:Screenshot 2025-08-01 161027.png]]
434 -
435 -|(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 413Hz
436 -|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)80 V/m/s
437 -|(% style="width:187px" %)**Size (without spike)**|(% style="width:224px" %)95mm(L) × 103mm(W) × 118mm(H)
438 -|(% style="width:187px" %)**Weight**|(% style="width:224px" %)1.1 kg
439 -|(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)8 Gb
440 -|(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((
441 -Lithium-ion battery contained in equipment (38.48 Wh)
442 -
443 -UN3481 PI967 S2
444 444  )))
445 445  )))
446 -
447 -(% class="box" %)
448 -(((
449 -= SmartSolo BD3C-16 Portable Battery Charger =
450 -
451 -[[image:20250729_125049.jpg]]
452 -
453 -|**Dimensions (LxHxW)**|558 x 357 x 300mm
454 -|**Input rating**|100-210V - 50/60Hz
455 -|**Power**|1000W
456 -|**Weight**|14.5kg
457 -|**Weight with cables**|21kg
458 -)))
459 -
460 -(% class="box" id="HSmartSoloBD3C-16PortableBatteryCharger" %)
461 -(((
462 -= SmartSolo IGU-16 Portable Data Harvester =
463 -
464 -[[image:20250729_124747.jpg]]
465 -
466 -|**Dimensions (LxHxW)**|625 x 500 x 366mm
467 -|**Input rating**|100-210V - 50/60Hz
468 -|**Power**|100W
469 -|**Weight**|21.5 - 24kg
470 -|**Slots no.**|16
471 -|**Download Speed**|20MB/sec/slot
472 -)))
473 -
474 -(% class="box" %)
475 -(((
476 -= SmartSolo IGU-16 Portable Battery Charger =
477 -
478 -[[image:20250729_124644.jpg]]
479 -
480 -|**Dimensions (LxHxW)**|625 x 500 x 366mm
481 -|**Input rating**|100-210V - 50/60Hz
482 -|**Power**|640W
483 -|**Weight**|26.3kg
484 -|**Slots no.**|16
485 -)))
486 -
487 -(% class="box" %)
488 -(((
489 -= SmartSolo BD3C-5 Carry Case =
490 -
491 -[[image:20250729_124957.jpg]]
492 -
493 -
494 -|**Dimensions (LxHxW)**|590 x 225 x 405mm
495 -|**Weight**|8.2kg
496 -|**Slots no.**|6
497 -)))
498 -
499 -(% class="box" %)
500 -(((
501 -= SmartSolo IGU-16 3C Carry Bag =
502 -
503 -[[image:20250729_124502.jpg]]
504 -
505 -|**Dimensions (LxHxW)**|230 x 340 x 310mm
506 -|**Weight**|3.6kg
507 -|**Slots no.**|6
508 -)))
509 -
510 -(% class="box" %)
511 -(((
512 -= SmartSolo IGU-16 1C Carry Bag =
513 -
514 -[[image:20250729_124558.jpg]]
515 -
516 -|**Dimensions (LxHxW)**|225 x 200 x 550mm
517 -|**Weight**|
518 -|**Slots no.**|6
519 -)))
520 -)))
521 -)))
20250729_124502.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -318.3 KB
Content
20250729_124558.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -376.8 KB
Content
20250729_124644.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -528.0 KB
Content
20250729_124747.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -488.5 KB
Content
20250729_124957.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -532.5 KB
Content
20250729_125049.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -457.6 KB
Content
BB_programming.labels.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -111.5 KB
Content
SP_programming.labels.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -106.7 KB
Content
Screenshot 2025-08-01 161027.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -82.8 KB
Content
XWiki.XWikiRights[1]
Allow/Deny
... ... @@ -1,1 +1,0 @@
1 -Allow
Levels
... ... @@ -1,1 +1,0 @@
1 -comment
Users
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest