Skip to Content
Last modified by KB on 2025/12/04 12:33
From version 90.1
edited by KB
on 2025/12/04 12:31
Change comment: There is no comment for this version
To version 75.1
edited by robert
on 2025/07/31 20:04
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.KB
1 +XWiki.robert
Content
... ... @@ -4,19 +4,13 @@
4 4  (((
5 5  = **Node Types** =
6 6  
7 -ANSIR supply 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 -(% class="box infomessage" %)
16 -(((
17 -**Freight update, 2026: **Freight options for lithium-ion batteries are changing in 2025/2026 to comply with updated transport safety regulations. This will impact supply feasibility for IGU 16 (<100Wh) and BD3C (168Wh) nodes. Advice will be sought from freighters on a case-by-case basis while they implement new guidelines.
18 -)))
19 -
20 20  ----
21 21  
22 22  = **Programming Defaults** =
... ... @@ -29,8 +29,6 @@
29 29  
30 30  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.
31 31  
32 -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.
33 -
34 34  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.
35 35  
36 36  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!**
... ... @@ -237,27 +237,12 @@
237 237  
238 238  
239 239  
240 -{{{
241 - }}}
232 +[[image:1706153354750-415.png||data-xwiki-image-style-alignment="center" height="317" width="562"]]
242 242  
243 243  ----
244 244  
245 245  = **Downloading and Converting Seismic Data to MiniSeed Format** =
246 246  
247 -(% class="wikigeneratedid" %)
248 -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]]
249 -
250 -== Connection tips: ==
251 -
252 -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:
253 -
254 -* Place the node on the harvester gently, then firmly press it down onto the pins.
255 -* 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.
256 -* 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.
257 -* 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!
258 -
259 -
260 -
261 261  == Node Registration and Software Setup ==
262 262  
263 263  1. (((
... ... @@ -276,27 +276,6 @@
276 276  * Ignore the settings for seismic recordings in the subsequent window. Resetting instruments (e.g., sampling rate, gain) requires reprogramming via script.
277 277  )))
278 278  
279 -== File structure ==
280 -
281 -There are essentially three main folders where relevant PROSPECT and PROJECT DATA is stored. Individual projects will be found as subfolders in these.
282 -
283 -=== SOLOLITE ===
284 -
285 -This folder stores SoloLite config files and parameters. Nothing too important stored here, you can always start over and re-create this.
286 -
287 -=== DCCDATA ===
288 -
289 -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.
290 -
291 -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)//
292 -
293 -Then in the SoloLite software, go to tools > Reanalyze Seismic Data
294 -
295 -=== SOLODATA ===
296 -
297 -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.
298 -
299 -
300 300  == Data Downloading Process ==
301 301  
302 302  1. (((
... ... @@ -321,38 +321,6 @@
321 321  )))
322 322  )))
323 323  
324 -== Smart Solo Z Polarity bug (SP nodes ONLY!) ==
325 -
326 -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.**
327 -
328 -== 18 Leap Second bug ==
329 -
330 -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.
331 -
332 -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.
333 -
334 -{{code language="none"}}
335 -<?xml version="1.0" encoding="UTF-8"?>
336 -<config>
337 - <leapsecond>
338 - <interval>
339 - <start_time>2017-01-01#00:00:00</start_time>
340 - <end_time>2999-12-31#23:59:59</end_time>
341 - <second>18</second>
342 - </interval>
343 - <interval>
344 - <start_time>1970-01-01#00:00:00</start_time>
345 - <end_time>2017-01-01#00:00:00</end_time>
346 - <second>17</second>
347 - </interval>
348 - </leapsecond>
349 - <GPS_distance_threshold_degree>
350 - 4e-5
351 - </GPS_distance_threshold_degree>
352 -</config>
353 -{{/code}}
354 -
355 -
356 356  == Handling Nodes During Download ==
357 357  
358 358  1. (((
... ... @@ -410,7 +410,7 @@
410 410  
411 411  = **Cleaning** =
412 412  
413 -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.
337 +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.
414 414  
415 415  = **Weights (for shipping)** =
416 416  
... ... @@ -448,7 +448,7 @@
448 448  
449 449  |(% style="width:189px" %)**Frequency Band**|(% style="width:221px" %)5 Seconds to 150Hz
450 450  |(% style="width:189px" %)**Sensitivity**|(% style="width:221px" %)200 V/m/s
451 -|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)Φ158 x160mm(H)
375 +|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)158 x160mm
452 452  |(% style="width:189px" %)**Weight**|(% style="width:221px" %)2.8 kg
453 453  |(% style="width:189px" %)**Data Storage**|(% style="width:221px" %)64 Gb
454 454  |(% style="width:189px" %)**Battery**|(% style="width:221px" %)(((
... ... @@ -467,8 +467,8 @@
467 467  [[image:smartsolo node 2.jpg]]
468 468  
469 469  |(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 1652Hz
470 -|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)76.7 V/m/s
471 -|(% style="width:187px" %)**Size (with spike)**|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm(H)
394 +|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)67.7 V/m/s
395 +|(% style="width:187px" %)**Size (with spike)**|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm
472 472  |(% style="width:187px" %)**Weight**|(% style="width:224px" %)2.4 kg
473 473  |(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)64 Gb
474 474  |(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((
... ... @@ -480,27 +480,6 @@
480 480  
481 481  (% class="box" %)
482 482  (((
483 -
484 -
485 -= SmartSolo [[IGU-16>>url:https://smartsolo.com/cp-3.html]]1C =
486 -
487 -
488 -[[image:Screenshot 2025-08-01 161027.png]]
489 -
490 -|(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 413Hz
491 -|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)80 V/m/s
492 -|(% style="width:187px" %)**Size (without spike)**|(% style="width:224px" %)95mm(L) × 103mm(W) × 118mm(H)
493 -|(% style="width:187px" %)**Weight**|(% style="width:224px" %)1.1 kg
494 -|(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)8 Gb
495 -|(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((
496 -Lithium-ion battery contained in equipment (38.48 Wh)
497 -
498 -UN3481 PI967 S2
499 -)))
500 -)))
501 -
502 -(% class="box" %)
503 -(((
504 504  = SmartSolo BD3C-16 Portable Battery Charger =
505 505  
506 506  [[image:20250729_125049.jpg]]
... ... @@ -530,7 +530,7 @@
530 530  (((
531 531  = SmartSolo IGU-16 Portable Battery Charger =
532 532  
533 -[[image:20250729_124644.jpg]]
436 += [[image:20250729_124644.jpg]] =
534 534  
535 535  |**Dimensions (LxHxW)**|625 x 500 x 366mm
536 536  |**Input rating**|100-210V - 50/60Hz
... ... @@ -541,7 +541,7 @@
541 541  
542 542  (% class="box" %)
543 543  (((
544 -= SmartSolo BD3C-5 Carry Case =
447 += SmartSolo BD3C-5 Carry Bag =
545 545  
546 546  [[image:20250729_124957.jpg]]
547 547  
Screenshot 2025-08-01 161027.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -82.8 KB
Content