Skip to Content
Last modified by robert on 2026/01/19 17:43
From version 75.1
edited by robert
on 2025/07/31 20:04
Change comment: There is no comment for this version
To version 95.1
edited by KB
on 2026/01/19 13:40
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.robert
1 +XWiki.KB
Content
... ... @@ -4,25 +4,33 @@
4 4  (((
5 5  = **Node Types** =
6 6  
7 -ANSIR carry two types of three-channel nodes
7 +ANSIR supply two types of three-channel nodes, and one type of one-channel node:
8 8  
9 -* **SmartSolo IGU 16HR 3C (5 Hz Short Period)**
10 -* **SmartSolo BD3C-5 (5 Second Broadband)**
9 +* **SmartSolo IGU 16HR 3C (5 Hz, 'very' short period)**
10 +* **SmartSolo BD3C-5 (5 second, short period)**
11 +* **SmartSolo IGU 16 1C (5 Hz, 'very' 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 theoretical 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  
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 of 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 +
14 14  ----
15 15  
16 16  = **Programming Defaults** =
17 17  
18 -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.
24 +The nodes must be programmed in the SoloLite software prior to use. The screenshots below show our recommended parameters for the 5 Hz (16HR-3C) and 5 second (BDC3-5) nodes.
19 19  
20 -[[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"]]
26 +[[IGU-16 3C programming screen set at 250 Hz. Ensure that the circled areas are set!>>image:5Hz_node_programming.labels.png||alt="IGU-16 3C programming screen"]]
21 21  
22 -[[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"]]
28 +[[BD3C-5 programming screen set at 250 hz. Ensure that the circled areas are set!>>image:5S_node_programming.labels.png||alt="BD3C-5 programming screen"]]
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  
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 +
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  
28 28  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!**
... ... @@ -33,9 +33,9 @@
33 33  
34 34  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.
35 35  
36 -Bluetooth (BB nodes only) should be turned OFF to conserve power.
44 +Bluetooth (BD3C-5 only) should be turned OFF to conserve power.
37 37  
38 -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).
46 +We recommend that the 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).
39 39  
40 40  {{info}}
41 41  **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!
... ... @@ -58,7 +58,7 @@
58 58  
59 59  == Animal-Proofing ==
60 60  
61 -We have experienced times where foxes (or some other animal) will dig up nodes and potentially carry them off for tens or hundreds of meteres. Being sanitary with the rope handles (e.g. not getting food grease on them) seems to help, as well as spraying the nodes and handles with methylated spirits et al. when deploying. There are other specialized products available depending on your environment.
69 +We have experienced interference from animals (foxes, dogs, goats) digging up and carrying nodes off for tens or hundreds of metres. It is helpful to minimise human and food smells (particularly on the rope handles) when working in areas where this is a risk. Or, wipe down affected nodes with 50-80% methylated spirits if extensive handling can not be avoided.
62 62  
63 63  = **Installation** =
64 64  
... ... @@ -84,8 +84,6 @@
84 84  == 2. Node Placement ==
85 85  )))
86 86  
87 -**Protection**: Place nodes inside (landfill) biodegradable bags to minimize cleaning and cross-site soil contamination.
88 -
89 89  **Site Analysis**:
90 90  
91 91  * **Take compass measurements away from the sensor as it will affect your measurement.**
... ... @@ -116,11 +116,14 @@
116 116  ** When recording at 250 Hz, with GPS on and Bluetooth disabled, the instruments are expected to last about 30 days per charge cycle. If they are set to run only overnight, this can be extended to 60 days.
117 117  
118 118  * **Post-Retrieval Charging**:
119 -** After retrieval, charge the instruments to about 50-60% (indicated as "orange" level) unless they are to be immediately re-deployed.
120 -* **Storage and Shipping Charge Level**:
121 -** Maintain a battery charge level of around 50-60% (e.g. "orange") for both storage and shipping purposes.
122 -** This charge level is recommended to prevent battery damage and is safe for transportation.
123 -** Nodes should not be stored fully charged, and **they should especially not be stored with 0 charge as this damages lithium batteries.**
125 +** After retrieval, charge the instruments to about 50-60% (indicated by ORANGE LED) unless they are to be immediately re-deployed or transported.
126 +* **State of Charge (SoC) for Storage**:
127 +** Maintain a battery charge level of around 50-60% (i.e., ORANGE) for storage.
128 +** This charge level is recommended to prevent battery damage, and should be checked every six months.
129 +** Nodes should //__not be stored at full-charge (GREEN), or 0-charge (RED).__//
130 +** Storage at 0-charge damages lithium batteries**.**
131 +* **SoC for Transport:**
132 +** Charge levels for transport will be advised by the freighter. The required SoC will depend on volume and transport method (air, land, sea).
124 124  
125 125  (((
126 126  == 6. Data Sharing and Metadata Creation ==
... ... @@ -128,7 +128,7 @@
128 128  
129 129  **GPS Data**:
130 130  
131 -* Ensure you have documented precise lat/lon locations for each station and **DOCUMENTED THIS CAREFULLY**
140 +* Ensure you have __carefully documented__ precise lat/lon locations for each station.
132 132  
133 133  **Photo Sharing**:
134 134  
... ... @@ -201,20 +201,22 @@
201 201  (((
202 202  == 2. Disassembling the Node: ==
203 203  
204 -* For the IGU-16HR, remove the battery (bottom half) from the sensor. This is done by unscrewing the spikes counter-clockwise.
213 +* For the IGU-16HR, remove the battery section (bottom half) from the sensor by unscrewing the spike section counter-clockwise.
205 205  )))
206 206  
207 207  (((
208 208  == 3. Setting Nodes in the Charging Box: ==
209 209  
210 -* Place 1-16 IGU-16HR battery components upside-down into the charger, assuring they are oriented properly.
219 +* Connect to a safe indoor power supply, and turn on (red rocker switch).
220 +* Charging will begin automatically when nodes are inserted in the charging rack.
221 +* Place IGU-16HR battery sections upside-down in the rack, oriented with the terminal connectors.
211 211  )))
212 212  
213 213  (((
214 214  == 4. Monitoring the Charging Process: ==
215 215  
216 -* 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.
217 -* 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.
227 +* Lights adjacent to the batteries will illuminate, indicating that charging is underway.
228 +* Observe the transition of the lights from steady RED to ORANGE, then GREEN, and finally to FLASHING GREEN. A flashing green light indicates the batteries are fully charged.
218 218  )))
219 219  
220 220  (((
... ... @@ -229,12 +229,27 @@
229 229  
230 230  
231 231  
232 -[[image:1706153354750-415.png||data-xwiki-image-style-alignment="center" height="317" width="562"]]
243 +{{{
244 + }}}
233 233  
234 234  ----
235 235  
236 236  = **Downloading and Converting Seismic Data to MiniSeed Format** =
237 237  
250 +(% class="wikigeneratedid" %)
251 +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]]
252 +
253 +== Connection tips: ==
254 +
255 +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:
256 +
257 +* Place the node on the harvester gently, then firmly press it down onto the pins.
258 +* 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.
259 +* 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.
260 +* 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!
261 +
262 +
263 +
238 238  == Node Registration and Software Setup ==
239 239  
240 240  1. (((
... ... @@ -253,6 +253,27 @@
253 253  * Ignore the settings for seismic recordings in the subsequent window. Resetting instruments (e.g., sampling rate, gain) requires reprogramming via script.
254 254  )))
255 255  
282 +== File structure ==
283 +
284 +There are essentially three main folders where relevant PROSPECT and PROJECT DATA is stored. Individual projects will be found as subfolders in these.
285 +
286 +=== SOLOLITE ===
287 +
288 +This folder stores SoloLite config files and parameters. Nothing too important stored here, you can always start over and re-create this.
289 +
290 +=== DCCDATA ===
291 +
292 +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.
293 +
294 +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)//
295 +
296 +Then in the SoloLite software, go to tools > Reanalyze Seismic Data
297 +
298 +=== SOLODATA ===
299 +
300 +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.
301 +
302 +
256 256  == Data Downloading Process ==
257 257  
258 258  1. (((
... ... @@ -277,6 +277,40 @@
277 277  )))
278 278  )))
279 279  
327 +== Smart Solo IGU-16HR Polarity Notice ==
328 +
329 +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 channel data manually rather than in the SoloLite software or inverting the response metadata.
330 +
331 +**The BD3C-5 data does not require a polarity inversion.**
332 +
333 +== 18 Leap Second bug ==
334 +
335 +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 constant 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.
336 +
337 +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.
338 +
339 +{{code language="none"}}
340 +<?xml version="1.0" encoding="UTF-8"?>
341 +<config>
342 + <leapsecond>
343 + <interval>
344 + <start_time>2017-01-01#00:00:00</start_time>
345 + <end_time>2999-12-31#23:59:59</end_time>
346 + <second>18</second>
347 + </interval>
348 + <interval>
349 + <start_time>1970-01-01#00:00:00</start_time>
350 + <end_time>2017-01-01#00:00:00</end_time>
351 + <second>17</second>
352 + </interval>
353 + </leapsecond>
354 + <GPS_distance_threshold_degree>
355 + 4e-5
356 + </GPS_distance_threshold_degree>
357 +</config>
358 +{{/code}}
359 +
360 +
280 280  == Handling Nodes During Download ==
281 281  
282 282  1. (((
... ... @@ -334,21 +334,23 @@
334 334  
335 335  = **Cleaning** =
336 336  
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.
418 +When assembled, the nodes are water resistant but not submersible. They can handle a good spray and wipe-down. A strong, non-wire brush is helpful to reach areas between the metal spikes on the bottom.
338 338  
339 339  = **Weights (for shipping)** =
340 340  
341 341  The weights of bags of nodes, as well as data harvesters and node chargers, are listed below:
342 342  
343 -1 bag + 6 SP (IGU-16HR) nodes: 18 kg
424 +1 bag + 6*IGU-16HR nodes: 18 kg
344 344  
345 -1 SP (IGU-16HR) data harvester: 21.5 kg
426 +1*IGU-16HR data harvester: 21.5 kg
346 346  
347 -1 SP (IGU-16HR) charger: 26.3 kg
428 +1*IGU-16HR charger: 26.3 kg
348 348  
349 -1 BB (BD3C-5) charger/data harvester (with and without 16 cables): 21 kg / 14.5 kg
430 +1*BD3C-5 charger (with and without 16 cables): 21 kg / 14.5 kg
350 350  
351 -1 case + 5 BB (BD3C-5) nodes and 6 BB nodes: 22 kg / 25 kg
432 +1 case + 5*BD3C-5 nodes: 22 kg (aggregate battery weight <5kg, 168Wh)
433 +
434 +1 case + 6*BD3C-5 nodes: 25 kg (aggregate battery weight >5kg, 168Wh)
352 352  )))
353 353  
354 354  (% class="col-xs-12 col-sm-4" %)
... ... @@ -372,7 +372,7 @@
372 372  
373 373  |(% style="width:189px" %)**Frequency Band**|(% style="width:221px" %)5 Seconds to 150Hz
374 374  |(% style="width:189px" %)**Sensitivity**|(% style="width:221px" %)200 V/m/s
375 -|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)158 x160mm
458 +|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)Φ158 x160mm(H)
376 376  |(% style="width:189px" %)**Weight**|(% style="width:221px" %)2.8 kg
377 377  |(% style="width:189px" %)**Data Storage**|(% style="width:221px" %)64 Gb
378 378  |(% style="width:189px" %)**Battery**|(% style="width:221px" %)(((
... ... @@ -391,8 +391,8 @@
391 391  [[image:smartsolo node 2.jpg]]
392 392  
393 393  |(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 1652Hz
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
477 +|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)76.7 V/m/s
478 +|(% style="width:187px" %)**Size (with spike)**|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm(H)
396 396  |(% style="width:187px" %)**Weight**|(% style="width:224px" %)2.4 kg
397 397  |(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)64 Gb
398 398  |(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((
... ... @@ -404,6 +404,27 @@
404 404  
405 405  (% class="box" %)
406 406  (((
490 +
491 +
492 += SmartSolo [[IGU-16>>url:https://smartsolo.com/cp-3.html]]1C =
493 +
494 +
495 +[[image:Screenshot 2025-08-01 161027.png]]
496 +
497 +|(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 413Hz
498 +|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)80 V/m/s
499 +|(% style="width:187px" %)**Size (without spike)**|(% style="width:224px" %)95mm(L) × 103mm(W) × 118mm(H)
500 +|(% style="width:187px" %)**Weight**|(% style="width:224px" %)1.1 kg
501 +|(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)8 Gb
502 +|(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((
503 +Lithium-ion battery contained in equipment (38.48 Wh)
504 +
505 +UN3481 PI967 S2
506 +)))
507 +)))
508 +
509 +(% class="box" %)
510 +(((
407 407  = SmartSolo BD3C-16 Portable Battery Charger =
408 408  
409 409  [[image:20250729_125049.jpg]]
... ... @@ -433,7 +433,7 @@
433 433  (((
434 434  = SmartSolo IGU-16 Portable Battery Charger =
435 435  
436 -= [[image:20250729_124644.jpg]] =
540 +[[image:20250729_124644.jpg]]
437 437  
438 438  |**Dimensions (LxHxW)**|625 x 500 x 366mm
439 439  |**Input rating**|100-210V - 50/60Hz
... ... @@ -444,7 +444,7 @@
444 444  
445 445  (% class="box" %)
446 446  (((
447 -= SmartSolo BD3C-5 Carry Bag =
551 += SmartSolo BD3C-5 Carry Case =
448 448  
449 449  [[image:20250729_124957.jpg]]
450 450  
5Hz_node_programming.labels.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.KB
Size
... ... @@ -1,0 +1,1 @@
1 +109.8 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