Skip to Content
Last modified by robert on 2025/10/29 10:39
From version 74.2
edited by robert
on 2025/07/31 19:59
Change comment: There is no comment for this version
To version 89.2
edited by robert
on 2025/10/28 18:02
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -4,12 +4,13 @@
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 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  
... ... @@ -23,17 +23,25 @@
23 23  
24 24  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.
25 25  
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 +
26 26  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.
27 27  
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 +
28 28  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.
29 29  
30 -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 output to miniseed later.
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.
31 31  
32 -GPS mode is best in cycle mode (e.g. once per hour) instead of constant. The clock drift on these are almost nil even if there is no sync at all, so it's best to conserve power.
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.
33 33  
39 +Bluetooth (BB nodes only) should be turned OFF to conserve power.
40 +
34 34  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).
35 35  
36 -**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.
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}}
37 37  
38 38  = **Fieldwork Preparation** =
39 39  
... ... @@ -223,12 +223,27 @@
223 223  
224 224  
225 225  
226 -[[image:1706153354750-415.png||data-xwiki-image-style-alignment="center" height="317" width="562"]]
235 +{{{
236 + }}}
227 227  
228 228  ----
229 229  
230 230  = **Downloading and Converting Seismic Data to MiniSeed Format** =
231 231  
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 +
232 232  == Node Registration and Software Setup ==
233 233  
234 234  1. (((
... ... @@ -247,6 +247,27 @@
247 247  * Ignore the settings for seismic recordings in the subsequent window. Resetting instruments (e.g., sampling rate, gain) requires reprogramming via script.
248 248  )))
249 249  
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 +
250 250  == Data Downloading Process ==
251 251  
252 252  1. (((
... ... @@ -271,6 +271,38 @@
271 271  )))
272 272  )))
273 273  
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. At some point in the next few years it will be 19 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 +
274 274  == Handling Nodes During Download ==
275 275  
276 276  1. (((
... ... @@ -328,7 +328,7 @@
328 328  
329 329  = **Cleaning** =
330 330  
331 -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.
332 332  
333 333  = **Weights (for shipping)** =
334 334  
... ... @@ -366,7 +366,7 @@
366 366  
367 367  |(% style="width:189px" %)**Frequency Band**|(% style="width:221px" %)5 Seconds to 150Hz
368 368  |(% style="width:189px" %)**Sensitivity**|(% style="width:221px" %)200 V/m/s
369 -|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)158 x160mm
446 +|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)Φ158 x160mm(H)
370 370  |(% style="width:189px" %)**Weight**|(% style="width:221px" %)2.8 kg
371 371  |(% style="width:189px" %)**Data Storage**|(% style="width:221px" %)64 Gb
372 372  |(% style="width:189px" %)**Battery**|(% style="width:221px" %)(((
... ... @@ -385,8 +385,8 @@
385 385  [[image:smartsolo node 2.jpg]]
386 386  
387 387  |(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 1652Hz
388 -|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)67.7 V/m/s
389 -|(% 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)
390 390  |(% style="width:187px" %)**Weight**|(% style="width:224px" %)2.4 kg
391 391  |(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)64 Gb
392 392  |(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((
... ... @@ -398,6 +398,27 @@
398 398  
399 399  (% class="box" %)
400 400  (((
478 +
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
494 +)))
495 +)))
496 +
497 +(% class="box" %)
498 +(((
401 401  = SmartSolo BD3C-16 Portable Battery Charger =
402 402  
403 403  [[image:20250729_125049.jpg]]
... ... @@ -427,7 +427,7 @@
427 427  (((
428 428  = SmartSolo IGU-16 Portable Battery Charger =
429 429  
430 -= [[image:20250729_124644.jpg]] =
528 +[[image:20250729_124644.jpg]]
431 431  
432 432  |**Dimensions (LxHxW)**|625 x 500 x 366mm
433 433  |**Input rating**|100-210V - 50/60Hz
... ... @@ -438,7 +438,7 @@
438 438  
439 439  (% class="box" %)
440 440  (((
441 -= SmartSolo BD3C-5 Carry Bag =
539 += SmartSolo BD3C-5 Carry Case =
442 442  
443 443  [[image:20250729_124957.jpg]]
444 444  
Screenshot 2025-08-01 161027.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.JackD
Size
... ... @@ -1,0 +1,1 @@
1 +82.8 KB
Content