Skip to Content
Last modified by robert on 2025/10/29 10:39
From version 61.1
edited by robert
on 2025/07/16 16:21
Change comment: There is no comment for this version
To version 89.1
edited by robert
on 2025/10/28 18:01
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -4,25 +4,48 @@
4 4  (((
5 5  = **Node Types** =
6 6  
7 -ANSIR carry two types of three-channel nodes
7 +ANSIR carry two types of three-channel nodes, and one type of one-channel node:
8 8  
9 9  * **SmartSolo IGU 16HR 3C (5 Hz Short Period)**
10 -* **SmartSolo BD3C-5 (5 Second Broad-Band)**
10 +* **SmartSolo BD3C-5 (5 Second Broadband)**
11 +* **SmartSolo IGU 16 1C (5 Hz Short Period, single channel)**
11 11  
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.
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.
13 13  
14 14  ----
15 15  
16 16  = **Programming Defaults** =
17 17  
18 -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.
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 19  
20 -**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.
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 21  
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 +
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 +
22 22  = **Fieldwork Preparation** =
23 23  
24 -(% class="box infomessage" %)
25 -(((
26 26  (% class="box warningmessage" %)
27 27  (((
28 28  **INVEST IN FAST EXTERNAL HARD DRIVES – DO NOT LET THIS BE THE LIMITATION OF DATA HARVESTING**
... ... @@ -31,7 +31,6 @@
31 31  
32 32  **We have had good experience with the 4Tb Samsung T7 Shield drives.**
33 33  )))
34 -)))
35 35  
36 36  == Magnets ==
37 37  
... ... @@ -43,18 +43,25 @@
43 43  
44 44  = **Installation** =
45 45  
46 -== 1. Logbook documentation ~*~** TODO ADD LOGBOOK FORMS ==
68 +(% class="box infomessage" %)
69 +(((
70 +**Field logs are a critical component of fieldwork and this is especially the case for large N nodal deploys. Take notes!**
71 +)))
47 47  
73 +== 1. Logbook documentation ==
74 +
48 48  (((
49 -**Essential Details**: Record the following in a logbook:
76 +**Essential Details** for field logs:
50 50  
51 51  * Station name
52 -* Latitude and longitude
79 +* Latitude, longitude, elevation
53 53  * Names of team members present
54 -* Date and local time of installation
55 -* Serial number (SN) of the sensor
56 -* Detailed notes on the site conditions and setup
81 +* Date and both local & UTC time of installation/removal
82 +* Serial number (SN) of the TOP HALF of the sensor (if a BD3C-5, there is only one serial number)
83 +* 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)
57 57  
85 +[[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!
86 +
58 58  == 2. Node Placement ==
59 59  )))
60 60  
... ... @@ -63,8 +63,8 @@
63 63  **Site Analysis**:
64 64  
65 65  * **Take compass measurements away from the sensor as it will affect your measurement.**
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)
95 +* Take photographs from various angles to document the site setup thoroughly.
96 +* Include a detailed site description in your notes
68 68  
69 69  == 3. GPS Considerations ==
70 70  
... ... @@ -203,12 +203,27 @@
203 203  
204 204  
205 205  
206 -[[image:1706153354750-415.png||data-xwiki-image-style-alignment="center" height="317" width="562"]]
235 +{{{
236 + }}}
207 207  
208 208  ----
209 209  
210 210  = **Downloading and Converting Seismic Data to MiniSeed Format** =
211 211  
242 +(% class="wikigeneratedid" %)
243 +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>>url:https://nappe.wustl.edu/smartsolo/files/smartsolo_online_training.pdf]]
244 +
245 +== Connection tips: ==
246 +
247 +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:
248 +
249 +* Place the node on the harvester gently, then firmly press it down onto the pins.
250 +* 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.
251 +* 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 each other.
252 +* Nodes will likely not show up in the order that they should, though this is not an issue. E.g, a node in slot 6 on the harvester may show up in port 13 in the SoloLite software. Annoying, but it doesn't matter so long as you keep track of what's been harvested!
253 +
254 +
255 +
212 212  == Node Registration and Software Setup ==
213 213  
214 214  1. (((
... ... @@ -227,6 +227,27 @@
227 227  * Ignore the settings for seismic recordings in the subsequent window. Resetting instruments (e.g., sampling rate, gain) requires reprogramming via script.
228 228  )))
229 229  
274 +== File structure ==
275 +
276 +There are essentially three main folders where relevant PROSPECT and PROJECT DATA is stored. Individual projects will be found as subfolders in these.
277 +
278 +=== SOLOLITE ===
279 +
280 +This folder stores SoloLite config files and parameters. Nothing too important stored here, you can always start over and re-create this.
281 +
282 +=== DCCDATA ===
283 +
284 +This folder stores the RAW data you have harvested from the nodes. The data will still be on the nodes (unless you erased it) in case of emergency, but regardless, this is the folder you want to back up and save somewhere.
285 +
286 +If you had a weird time harvesting a node, you can always manually copy it as if it were a USB stick and place it into this folder manually. The structure is: //C:/DCCDATA/prospect_name/project_name/SERIALNUMBER/label(usually a timestamp but can be anything)//
287 +
288 +Then in the SoloLite software, go to tools > Reanalyze Seismic Data
289 +
290 +=== SOLODATA ===
291 +
292 +This folder stores **exported** (e.g. miniseed) data. It is structured similarly. If your DCCDATA is intact, this can always be re-created if need be.
293 +
294 +
230 230  == Data Downloading Process ==
231 231  
232 232  1. (((
... ... @@ -251,6 +251,38 @@
251 251  )))
252 252  )))
253 253  
319 +== Smart Solo Z Polarity bug (SP nodes ONLY!) ==
320 +
321 +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 in the SoloLite software or inverting the response metadata. **The BD3C-5 data does not require a polarity inversion.**
322 +
323 +== 18 Leap Second bug ==
324 +
325 +Not so much a bug as much as "a thing that can happen if your SoloLite installation is corrupted". If you notice your data has large time offsets, you should suspect that the number of leap seconds has not been accounted properly. There is a file "smartsoloconfig.xml" that needs to be present in "C:\SmartSoloApps SoloLite" (e.g. the main program directory) that dictates the leap second offset for the last two data ranges. Since 2017-01-01, this is 18 seconds.
326 +
327 +If this file is missing, just create a new one structured like so, name it "smartsoloconfig.xml" and put it in your main program directory. Then, Reanalyze your data (tools > Reanalyze seismic data) and your data should have the correct time. You can also do this manually, if you want. The offset is 18 seconds precisely.
328 +
329 +{{code language="none"}}
330 +<?xml version="1.0" encoding="UTF-8"?>
331 +<config>
332 + <leapsecond>
333 + <interval>
334 + <start_time>2017-01-01#00:00:00</start_time>
335 + <end_time>2999-12-31#23:59:59</end_time>
336 + <second>18</second>
337 + </interval>
338 + <interval>
339 + <start_time>1970-01-01#00:00:00</start_time>
340 + <end_time>2017-01-01#00:00:00</end_time>
341 + <second>17</second>
342 + </interval>
343 + </leapsecond>
344 + <GPS_distance_threshold_degree>
345 + 4e-5
346 + </GPS_distance_threshold_degree>
347 +</config>
348 +{{/code}}
349 +
350 +
254 254  == Handling Nodes During Download ==
255 255  
256 256  1. (((
... ... @@ -308,7 +308,7 @@
308 308  
309 309  = **Cleaning** =
310 310  
311 -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.
408 +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 312  
313 313  = **Weights (for shipping)** =
314 314  
... ... @@ -346,7 +346,7 @@
346 346  
347 347  |(% style="width:189px" %)**Frequency Band**|(% style="width:221px" %)5 Seconds to 150Hz
348 348  |(% style="width:189px" %)**Sensitivity**|(% style="width:221px" %)200 V/m/s
349 -|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)158 x160mm
446 +|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)Φ158 x160mm(H)
350 350  |(% style="width:189px" %)**Weight**|(% style="width:221px" %)2.8 kg
351 351  |(% style="width:189px" %)**Data Storage**|(% style="width:221px" %)64 Gb
352 352  |(% style="width:189px" %)**Battery**|(% style="width:221px" %)(((
... ... @@ -358,7 +358,7 @@
358 358  
359 359  (% class="box" %)
360 360  (((
361 -= SmartSolo [[IGU-16HR>>url:https://smartsolo.com/cp-3.html]] =
458 += SmartSolo [[IGU-16HR>>url:https://smartsolo.com/cp-3.html]]3C =
362 362  
363 363  [[image:smartsolo node.jpg]]
364 364  
... ... @@ -365,8 +365,8 @@
365 365  [[image:smartsolo node 2.jpg]]
366 366  
367 367  |(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 1652Hz
368 -|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)67.7 V/m/s
369 -|(% style="width:187px" %)**Size (with spike)**|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm
465 +|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)76.7 V/m/s
466 +|(% style="width:187px" %)**Size (with spike)**|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm(H)
370 370  |(% style="width:187px" %)**Weight**|(% style="width:224px" %)2.4 kg
371 371  |(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)64 Gb
372 372  |(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((
... ... @@ -376,6 +376,99 @@
376 376  )))
377 377  )))
378 378  
476 +(% class="box" %)
477 +(((
379 379  
479 +
480 += SmartSolo [[IGU-16>>url:https://smartsolo.com/cp-3.html]]1C =
481 +
482 +
483 +[[image:Screenshot 2025-08-01 161027.png]]
484 +
485 +|(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 413Hz
486 +|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)80 V/m/s
487 +|(% style="width:187px" %)**Size (without spike)**|(% style="width:224px" %)95mm(L) × 103mm(W) × 118mm(H)
488 +|(% style="width:187px" %)**Weight**|(% style="width:224px" %)1.1 kg
489 +|(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)8 Gb
490 +|(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((
491 +Lithium-ion battery contained in equipment (38.48 Wh)
492 +
493 +UN3481 PI967 S2
380 380  )))
381 381  )))
496 +
497 +(% class="box" %)
498 +(((
499 += SmartSolo BD3C-16 Portable Battery Charger =
500 +
501 +[[image:20250729_125049.jpg]]
502 +
503 +|**Dimensions (LxHxW)**|558 x 357 x 300mm
504 +|**Input rating**|100-210V - 50/60Hz
505 +|**Power**|1000W
506 +|**Weight**|14.5kg
507 +|**Weight with cables**|21kg
508 +)))
509 +
510 +(% class="box" id="HSmartSoloBD3C-16PortableBatteryCharger" %)
511 +(((
512 += SmartSolo IGU-16 Portable Data Harvester =
513 +
514 +[[image:20250729_124747.jpg]]
515 +
516 +|**Dimensions (LxHxW)**|625 x 500 x 366mm
517 +|**Input rating**|100-210V - 50/60Hz
518 +|**Power**|100W
519 +|**Weight**|21.5 - 24kg
520 +|**Slots no.**|16
521 +|**Download Speed**|20MB/sec/slot
522 +)))
523 +
524 +(% class="box" %)
525 +(((
526 += SmartSolo IGU-16 Portable Battery Charger =
527 +
528 +[[image:20250729_124644.jpg]]
529 +
530 +|**Dimensions (LxHxW)**|625 x 500 x 366mm
531 +|**Input rating**|100-210V - 50/60Hz
532 +|**Power**|640W
533 +|**Weight**|26.3kg
534 +|**Slots no.**|16
535 +)))
536 +
537 +(% class="box" %)
538 +(((
539 += SmartSolo BD3C-5 Carry Case =
540 +
541 +[[image:20250729_124957.jpg]]
542 +
543 +
544 +|**Dimensions (LxHxW)**|590 x 225 x 405mm
545 +|**Weight**|8.2kg
546 +|**Slots no.**|6
547 +)))
548 +
549 +(% class="box" %)
550 +(((
551 += SmartSolo IGU-16 3C Carry Bag =
552 +
553 +[[image:20250729_124502.jpg]]
554 +
555 +|**Dimensions (LxHxW)**|230 x 340 x 310mm
556 +|**Weight**|3.6kg
557 +|**Slots no.**|6
558 +)))
559 +
560 +(% class="box" %)
561 +(((
562 += SmartSolo IGU-16 1C Carry Bag =
563 +
564 +[[image:20250729_124558.jpg]]
565 +
566 +|**Dimensions (LxHxW)**|225 x 200 x 550mm
567 +|**Weight**|
568 +|**Slots no.**|6
569 +)))
570 +)))
571 +)))
20250729_124502.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.JackD
Size
... ... @@ -1,0 +1,1 @@
1 +318.3 KB
Content
20250729_124558.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.JackD
Size
... ... @@ -1,0 +1,1 @@
1 +376.8 KB
Content
20250729_124644.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.JackD
Size
... ... @@ -1,0 +1,1 @@
1 +528.0 KB
Content
20250729_124747.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.JackD
Size
... ... @@ -1,0 +1,1 @@
1 +488.5 KB
Content
20250729_124957.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.JackD
Size
... ... @@ -1,0 +1,1 @@
1 +532.5 KB
Content
20250729_125049.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.JackD
Size
... ... @@ -1,0 +1,1 @@
1 +457.6 KB
Content
BB_programming.labels.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.robert
Size
... ... @@ -1,0 +1,1 @@
1 +111.5 KB
Content
SP_programming.labels.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.robert
Size
... ... @@ -1,0 +1,1 @@
1 +106.7 KB
Content
Screenshot 2025-08-01 161027.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.JackD
Size
... ... @@ -1,0 +1,1 @@
1 +82.8 KB
Content