Skip to Content
Last modified by robert on 2025/10/29 10:39
From version 84.1
edited by Jack Dent
on 2025/09/29 11:45
Change comment: There is no comment for this version
To version 60.1
edited by robert
on 2025/07/16 16:02
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.JackD
1 +XWiki.robert
Content
... ... @@ -4,60 +4,27 @@
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 -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.
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 -[[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"]]
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 -[[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"]]
24 24  
25 -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.
26 -
27 -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.
28 -
29 -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.
30 -
31 -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!**
32 -
33 -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.
34 -
35 -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.
36 -
37 -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.
38 -
39 -Bluetooth (BB nodes only) should be turned OFF to conserve power.
40 -
41 -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).
42 -
43 -{{info}}
44 -**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!
45 -{{/info}}
46 -
47 -=== **Programming tips**: ===
48 -
49 -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:
50 -
51 - - Place the node on the harvester gently, then firmly press it down onto the pins
52 -
53 - - 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.
54 -
55 - - 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
56 -
57 - - 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
58 -
59 59  = **Fieldwork Preparation** =
60 60  
26 +(% class="box infomessage" %)
27 +(((
61 61  (% class="box warningmessage" %)
62 62  (((
63 63  **INVEST IN FAST EXTERNAL HARD DRIVES – DO NOT LET THIS BE THE LIMITATION OF DATA HARVESTING**
... ... @@ -66,6 +66,7 @@
66 66  
67 67  **We have had good experience with the 4Tb Samsung T7 Shield drives.**
68 68  )))
36 +)))
69 69  
70 70  == Magnets ==
71 71  
... ... @@ -77,26 +77,19 @@
77 77  
78 78  = **Installation** =
79 79  
80 -(% class="box infomessage" %)
81 -(((
82 -**Field logs are a critical component of fieldwork and this is especially the case for large N nodal deploys. Take notes!**
83 -)))
48 +== **1. Logbook documentation** ==
84 84  
85 -== 1. Logbook documentation ==
86 -
87 87  (((
88 -**Essential Details** for field logs:
51 +**Essential Details**: Record the following in a logbook:
89 89  
90 90  * Station name
91 -* Latitude, longitude, elevation
54 +* Latitude and longitude
92 92  * Names of team members present
93 -* Date and both local & UTC time of installation/removal
94 -* Serial number (SN) of the TOP HALF of the sensor (if a BD3C-5, there is only one serial number)
95 -* 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)
56 +* Date and local time of installation
57 +* Serial number (SN) of the sensor
58 +* Detailed notes on the site conditions and setup
96 96  
97 -[[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!
98 -
99 -== 2. Node Placement ==
60 +== **2. Node Placement** ==
100 100  )))
101 101  
102 102  **Protection**: Place nodes inside (landfill) biodegradable bags to minimize cleaning and cross-site soil contamination.
... ... @@ -104,15 +104,15 @@
104 104  **Site Analysis**:
105 105  
106 106  * **Take compass measurements away from the sensor as it will affect your measurement.**
107 -* Take photographs from various angles to document the site setup thoroughly.
108 -* Include a detailed site description in your notes
68 +* Take multiple photographs from various angles to document the site setup thoroughly.
69 +* 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)
109 109  
110 -== 3. GPS Considerations ==
71 +== **3. GPS Considerations** ==
111 111  
112 112  (% class="wikigeneratedid" %)
113 113  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.
114 114  
115 -== 4. Visibility and Location Marking ==
76 +== **4. Visibility and Location Marking** ==
116 116  
117 117  **Flag Placement**: Position a flag, preferably in a bright color (avoid green or yellow), near the instrument to aid in its future location.
118 118  
... ... @@ -121,7 +121,7 @@
121 121  * Use a GPS device to mark the instrument's exact location.
122 122  * Record this location in both your paper notes and the GPS device.
123 123  
124 -== (% style="color:inherit; font-family:inherit; font-size:max(18px, min(20px, 14.4444px + 0.462963vw))" %)5. Charge Time, Pre-Deployment & Post-Deployment(%%) ==
85 +== (% style="color:inherit; font-family:inherit; font-size:max(18px, min(20px, 14.4444px + 0.462963vw))" %)**5. Charge Time, Pre-Deployment & Post-Deployment**(%%) ==
125 125  
126 126  * **Charging Duration**: Both types of nodes take approximately 6-8 hours to fully charge from a flat state.
127 127  * **Pre-Deployment Charging**:
... ... @@ -135,10 +135,10 @@
135 135  * **Storage and Shipping Charge Level**:
136 136  ** Maintain a battery charge level of around 50-60% (e.g. "orange") for both storage and shipping purposes.
137 137  ** This charge level is recommended to prevent battery damage and is safe for transportation.
138 -** Nodes should not be stored fully charged, and **they should especially not be stored with 0 charge as this damages lithium batteries.**
99 +** Nodes should not be stored fully charged, and it **they should especially not be stored with 0 charge.**
139 139  
140 140  (((
141 -== 6. Data Sharing and Metadata Creation ==
102 +== **6. Data Sharing and Metadata Creation** ==
142 142  )))
143 143  
144 144  **GPS Data**:
... ... @@ -151,9 +151,9 @@
151 151  
152 152  **Metadata File**:
153 153  
154 -* 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.
115 +* Create and organize metadata according to the [[ANU metadata standard txt file>>attach:example_metadata.txt]].
155 155  
156 -== 7. Additional Best Practices ==
117 +== **7. Additional Best Practices** ==
157 157  
158 158  * **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.
159 159  
... ... @@ -208,25 +208,25 @@
208 208  = **Charging Procedure for Seismic Nodes** =
209 209  
210 210  (((
211 -== 1. Preparation for Charging: ==
172 +== **1. Preparation for Charging**: ==
212 212  
213 213  * 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.
214 214  )))
215 215  
216 216  (((
217 -== 2. Disassembling the Node: ==
178 +== **2. Disassembling the Node**: ==
218 218  
219 219  * For the IGU-16HR, remove the battery (bottom half) from the sensor. This is done by unscrewing the spikes counter-clockwise.
220 220  )))
221 221  
222 222  (((
223 -== 3. Setting Nodes in the Charging Box: ==
184 +== **3. Setting Nodes in the Charging Box**: ==
224 224  
225 225  * Place 1-16 IGU-16HR battery components upside-down into the charger, assuring they are oriented properly.
226 226  )))
227 227  
228 228  (((
229 -== 4. Monitoring the Charging Process: ==
190 +== **4. Monitoring the Charging Process**: ==
230 230  
231 231  * 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.
232 232  * 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.
... ... @@ -233,7 +233,7 @@
233 233  )))
234 234  
235 235  (((
236 -== 5. Updating Charge Status: ==
197 +== **5. Updating Charge Status**: ==
237 237  
238 238  * 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.
239 239  * This step is crucial for tracking the charging status of multiple units, especially when handling a large number of nodes.
... ... @@ -250,7 +250,7 @@
250 250  
251 251  = **Downloading and Converting Seismic Data to MiniSeed Format** =
252 252  
253 -== Node Registration and Software Setup ==
214 +== **Node Registration and Software Setup** ==
254 254  
255 255  1. (((
256 256  **Registering Nodes in the System**:
... ... @@ -268,7 +268,7 @@
268 268  * Ignore the settings for seismic recordings in the subsequent window. Resetting instruments (e.g., sampling rate, gain) requires reprogramming via script.
269 269  )))
270 270  
271 -== Data Downloading Process ==
232 +== **Data Downloading Process** ==
272 272  
273 273  1. (((
274 274  **Initiating Data Download**:
... ... @@ -286,18 +286,14 @@
286 286  * Click “prepare” followed by “run” to start reformatting. Monitor this process in the small panel at the bottom left.
287 287  * (% class="box warningmessage" %)
288 288  (((
289 -* **Ensure to export data as "COUNTS" (int32), not "mV" (float). This is critical!**
250 +* **Ensure to export data as "COUNTS", not "mV".**
290 290  
291 -* **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.**
252 +* **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).**
292 292  )))
293 293  )))
294 294  
295 -== Smart Solo Z Polarity bug ==
256 +== **Handling Nodes During Download** ==
296 296  
297 -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.
298 -
299 -== Handling Nodes During Download ==
300 -
301 301  1. (((
302 302  **Monitoring Download Indicators**:
303 303  
... ... @@ -313,7 +313,6 @@
313 313  * **Use fast external hard drives to avoid limitations in data harvesting.**
314 314  
315 315  * **Recommended specifications: USB-C, USB 3.0, and 4+ Tb of space.**
316 -* **The USB type for the harvester is TYPE-A, the typical normal rectangular shape.**
317 317  )))
318 318  )))
319 319  1. (((
... ... @@ -353,7 +353,7 @@
353 353  
354 354  = **Cleaning** =
355 355  
356 -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.
312 +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.
357 357  
358 358  = **Weights (for shipping)** =
359 359  
... ... @@ -391,7 +391,7 @@
391 391  
392 392  |(% style="width:189px" %)**Frequency Band**|(% style="width:221px" %)5 Seconds to 150Hz
393 393  |(% style="width:189px" %)**Sensitivity**|(% style="width:221px" %)200 V/m/s
394 -|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)Φ158 x160mm(H)
350 +|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)158 x160mm
395 395  |(% style="width:189px" %)**Weight**|(% style="width:221px" %)2.8 kg
396 396  |(% style="width:189px" %)**Data Storage**|(% style="width:221px" %)64 Gb
397 397  |(% style="width:189px" %)**Battery**|(% style="width:221px" %)(((
... ... @@ -403,7 +403,7 @@
403 403  
404 404  (% class="box" %)
405 405  (((
406 -= SmartSolo [[IGU-16HR>>url:https://smartsolo.com/cp-3.html]]3C =
362 += SmartSolo [[IGU-16HR>>url:https://smartsolo.com/cp-3.html]] =
407 407  
408 408  [[image:smartsolo node.jpg]]
409 409  
... ... @@ -410,8 +410,8 @@
410 410  [[image:smartsolo node 2.jpg]]
411 411  
412 412  |(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 1652Hz
413 -|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)76.7 V/m/s
414 -|(% style="width:187px" %)**Size (with spike)**|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm(H)
369 +|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)67.7 V/m/s
370 +|(% style="width:187px" %)**Size (with spike)**|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm
415 415  |(% style="width:187px" %)**Weight**|(% style="width:224px" %)2.4 kg
416 416  |(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)64 Gb
417 417  |(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((
... ... @@ -421,99 +421,6 @@
421 421  )))
422 422  )))
423 423  
424 -(% class="box" %)
425 -(((
426 426  
427 -
428 -= SmartSolo [[IGU-16>>url:https://smartsolo.com/cp-3.html]]1C =
429 -
430 -
431 -[[image:Screenshot 2025-08-01 161027.png]]
432 -
433 -|(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 413Hz
434 -|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)80 V/m/s
435 -|(% style="width:187px" %)**Size (without spike)**|(% style="width:224px" %)95mm(L) × 103mm(W) × 118mm(H)
436 -|(% style="width:187px" %)**Weight**|(% style="width:224px" %)1.1 kg
437 -|(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)8 Gb
438 -|(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((
439 -Lithium-ion battery contained in equipment (38.48 Wh)
440 -
441 -UN3481 PI967 S2
442 442  )))
443 443  )))
444 -
445 -(% class="box" %)
446 -(((
447 -= SmartSolo BD3C-16 Portable Battery Charger =
448 -
449 -[[image:20250729_125049.jpg]]
450 -
451 -|**Dimensions (LxHxW)**|558 x 357 x 300mm
452 -|**Input rating**|100-210V - 50/60Hz
453 -|**Power**|1000W
454 -|**Weight**|14.5kg
455 -|**Weight with cables**|21kg
456 -)))
457 -
458 -(% class="box" id="HSmartSoloBD3C-16PortableBatteryCharger" %)
459 -(((
460 -= SmartSolo IGU-16 Portable Data Harvester =
461 -
462 -[[image:20250729_124747.jpg]]
463 -
464 -|**Dimensions (LxHxW)**|625 x 500 x 366mm
465 -|**Input rating**|100-210V - 50/60Hz
466 -|**Power**|100W
467 -|**Weight**|21.5 - 24kg
468 -|**Slots no.**|16
469 -|**Download Speed**|20MB/sec/slot
470 -)))
471 -
472 -(% class="box" %)
473 -(((
474 -= SmartSolo IGU-16 Portable Battery Charger =
475 -
476 -[[image:20250729_124644.jpg]]
477 -
478 -|**Dimensions (LxHxW)**|625 x 500 x 366mm
479 -|**Input rating**|100-210V - 50/60Hz
480 -|**Power**|640W
481 -|**Weight**|26.3kg
482 -|**Slots no.**|16
483 -)))
484 -
485 -(% class="box" %)
486 -(((
487 -= SmartSolo BD3C-5 Carry Case =
488 -
489 -[[image:20250729_124957.jpg]]
490 -
491 -
492 -|**Dimensions (LxHxW)**|590 x 225 x 405mm
493 -|**Weight**|8.2kg
494 -|**Slots no.**|6
495 -)))
496 -
497 -(% class="box" %)
498 -(((
499 -= SmartSolo IGU-16 3C Carry Bag =
500 -
501 -[[image:20250729_124502.jpg]]
502 -
503 -|**Dimensions (LxHxW)**|230 x 340 x 310mm
504 -|**Weight**|3.6kg
505 -|**Slots no.**|6
506 -)))
507 -
508 -(% class="box" %)
509 -(((
510 -= SmartSolo IGU-16 1C Carry Bag =
511 -
512 -[[image:20250729_124558.jpg]]
513 -
514 -|**Dimensions (LxHxW)**|225 x 200 x 550mm
515 -|**Weight**|
516 -|**Slots no.**|6
517 -)))
518 -)))
519 -)))
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.XWikiComments[0]
Author
... ... @@ -1,0 +1,1 @@
1 +Anonymous
Comment
... ... @@ -1,0 +1,1 @@
1 +test comment
Date
... ... @@ -1,0 +1,1 @@
1 +2025-07-16 15:59:01.66