Skip to Content
Last modified by robert on 2025/10/29 10:39
From version 88.1
edited by robert
on 2025/10/27 16:35
Change comment: There is no comment for this version
To version 70.1
edited by Jack Dent
on 2025/07/31 09:39
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.robert
1 +XWiki.JackD
Content
... ... @@ -4,46 +4,21 @@
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 10  * **SmartSolo BD3C-5 (5 Second Broadband)**
11 -* **SmartSolo IGU 16 1C (5 Hz Short Period, single channel)**
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  
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.
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.
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"]]
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.
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 -
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 47  = **Fieldwork Preparation** =
48 48  
49 49  (% class="box warningmessage" %)
... ... @@ -232,28 +232,12 @@
232 232  
233 233  
234 234  
235 -{{{
210 +[[image:1706153354750-415.png||data-xwiki-image-style-alignment="center" height="317" width="562"]]
236 236  
237 -}}}
238 -
239 239  ----
240 240  
241 241  = **Downloading and Converting Seismic Data to MiniSeed Format** =
242 242  
243 -(% class="wikigeneratedid" %)
244 -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]]
245 -
246 -== Connection tips: ==
247 -
248 -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:
249 -
250 -* Place the node on the harvester gently, then firmly press it down onto the pins.
251 -* 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.
252 -* 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.
253 -* 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!
254 -
255 -
256 -
257 257  == Node Registration and Software Setup ==
258 258  
259 259  1. (((
... ... @@ -272,27 +272,6 @@
272 272  * Ignore the settings for seismic recordings in the subsequent window. Resetting instruments (e.g., sampling rate, gain) requires reprogramming via script.
273 273  )))
274 274  
275 -== File structure ==
276 -
277 -There are essentially three main folders where relevant PROSPECT and PROJECT DATA is stored. Individual projects will be found as subfolders in these.
278 -
279 -=== SOLOLITE ===
280 -
281 -This folder stores SoloLite config files and parameters. Nothing too important stored here, you can always start over and re-create this.
282 -
283 -=== DCCDATA ===
284 -
285 -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.
286 -
287 -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)//
288 -
289 -Then in the SoloLite software, go to tools > Reanalyze Seismic Data
290 -
291 -=== SOLODATA ===
292 -
293 -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.
294 -
295 -
296 296  == Data Downloading Process ==
297 297  
298 298  1. (((
... ... @@ -317,10 +317,6 @@
317 317  )))
318 318  )))
319 319  
320 -== Smart Solo Z Polarity bug (SP nodes ONLY!) ==
321 -
322 -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.**
323 -
324 324  == Handling Nodes During Download ==
325 325  
326 326  1. (((
... ... @@ -378,7 +378,7 @@
378 378  
379 379  = **Cleaning** =
380 380  
381 -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.
315 +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.
382 382  
383 383  = **Weights (for shipping)** =
384 384  
... ... @@ -416,7 +416,7 @@
416 416  
417 417  |(% style="width:189px" %)**Frequency Band**|(% style="width:221px" %)5 Seconds to 150Hz
418 418  |(% style="width:189px" %)**Sensitivity**|(% style="width:221px" %)200 V/m/s
419 -|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)Φ158 x160mm(H)
353 +|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)158 x160mm
420 420  |(% style="width:189px" %)**Weight**|(% style="width:221px" %)2.8 kg
421 421  |(% style="width:189px" %)**Data Storage**|(% style="width:221px" %)64 Gb
422 422  |(% style="width:189px" %)**Battery**|(% style="width:221px" %)(((
... ... @@ -435,8 +435,8 @@
435 435  [[image:smartsolo node 2.jpg]]
436 436  
437 437  |(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 1652Hz
438 -|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)76.7 V/m/s
439 -|(% style="width:187px" %)**Size (with spike)**|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm(H)
372 +|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)67.7 V/m/s
373 +|(% style="width:187px" %)**Size (with spike)**|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm
440 440  |(% style="width:187px" %)**Weight**|(% style="width:224px" %)2.4 kg
441 441  |(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)64 Gb
442 442  |(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((
... ... @@ -448,27 +448,6 @@
448 448  
449 449  (% class="box" %)
450 450  (((
451 -
452 -
453 -= SmartSolo [[IGU-16>>url:https://smartsolo.com/cp-3.html]]1C =
454 -
455 -
456 -[[image:Screenshot 2025-08-01 161027.png]]
457 -
458 -|(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 413Hz
459 -|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)80 V/m/s
460 -|(% style="width:187px" %)**Size (without spike)**|(% style="width:224px" %)95mm(L) × 103mm(W) × 118mm(H)
461 -|(% style="width:187px" %)**Weight**|(% style="width:224px" %)1.1 kg
462 -|(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)8 Gb
463 -|(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((
464 -Lithium-ion battery contained in equipment (38.48 Wh)
465 -
466 -UN3481 PI967 S2
467 -)))
468 -)))
469 -
470 -(% class="box" %)
471 -(((
472 472  = SmartSolo BD3C-16 Portable Battery Charger =
473 473  
474 474  [[image:20250729_125049.jpg]]
... ... @@ -498,7 +498,7 @@
498 498  (((
499 499  = SmartSolo IGU-16 Portable Battery Charger =
500 500  
501 -[[image:20250729_124644.jpg]]
414 += [[image:20250729_124644.jpg]] =
502 502  
503 503  |**Dimensions (LxHxW)**|625 x 500 x 366mm
504 504  |**Input rating**|100-210V - 50/60Hz
... ... @@ -507,18 +507,11 @@
507 507  |**Slots no.**|16
508 508  )))
509 509  
510 -(% class="box" %)
511 -(((
512 -= SmartSolo BD3C-5 Carry Case =
513 513  
514 -[[image:20250729_124957.jpg]]
515 515  
516 516  
517 -|**Dimensions (LxHxW)**|590 x 225 x 405mm
518 -|**Weight**|8.2kg
519 -|**Slots no.**|6
520 -)))
521 521  
427 +
522 522  (% class="box" %)
523 523  (((
524 524  = SmartSolo IGU-16 3C Carry Bag =
... ... @@ -526,10 +526,10 @@
526 526  [[image:20250729_124502.jpg]]
527 527  
528 528  |**Dimensions (LxHxW)**|230 x 340 x 310mm
529 -|**Weight**|3.6kg
530 530  |**Slots no.**|6
531 531  )))
532 532  
438 +
533 533  (% class="box" %)
534 534  (((
535 535  = SmartSolo IGU-16 1C Carry Bag =
... ... @@ -536,8 +536,7 @@
536 536  
537 537  [[image:20250729_124558.jpg]]
538 538  
539 -|**Dimensions (LxHxW)**|225 x 200 x 550mm
540 -|**Weight**|
445 +|**Dimensions (LxHxW)**|230 x 340 x 310mm
541 541  |**Slots no.**|6
542 542  )))
543 543  )))
20250729_124957.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -532.5 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