Skip to Content
Last modified by robert on 2026/01/19 17:43
From version 83.1
edited by robert
on 2025/08/21 13:08
Change comment: There is no comment for this version
To version 94.3
edited by KB
on 2026/01/19 11:59
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,23 +4,28 @@
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 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)**
11 -* **SmartSolo IGU 16 1C (5 Hz Short Period, single channel)**
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)**
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.
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.
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 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 +
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.
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.
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"]]
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"]]
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"]]
28 +[[BD3C-5 programming screen set at 250 hz. Ensure that the circled areas are set!>>image:BB_programming.labels.png||alt="BD3C-5 programming screen"]]
24 24  
25 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 26  
... ... @@ -232,12 +232,27 @@
232 232  
233 233  
234 234  
235 -[[image:1706153354750-415.png||data-xwiki-image-style-alignment="center" height="317" width="562"]]
240 +{{{
241 + }}}
236 236  
237 237  ----
238 238  
239 239  = **Downloading and Converting Seismic Data to MiniSeed Format** =
240 240  
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 +
241 241  == Node Registration and Software Setup ==
242 242  
243 243  1. (((
... ... @@ -256,6 +256,27 @@
256 256  * Ignore the settings for seismic recordings in the subsequent window. Resetting instruments (e.g., sampling rate, gain) requires reprogramming via script.
257 257  )))
258 258  
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 +
259 259  == Data Downloading Process ==
260 260  
261 261  1. (((
... ... @@ -280,10 +280,40 @@
280 280  )))
281 281  )))
282 282  
283 -== Smart Solo Z Polarity bug ==
324 +== Smart Solo IGU-16HR Polarity Notice ==
284 284  
285 -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 invert the response metadata. The BD3C-5 data does not require a polarity inversion.
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 channel data manually rather than in the SoloLite software or inverting the response metadata.
286 286  
328 +**The BD3C-5 data does not require a polarity inversion.**
329 +
330 +== 18 Leap Second bug ==
331 +
332 +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.
333 +
334 +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.
335 +
336 +{{code language="none"}}
337 +<?xml version="1.0" encoding="UTF-8"?>
338 +<config>
339 + <leapsecond>
340 + <interval>
341 + <start_time>2017-01-01#00:00:00</start_time>
342 + <end_time>2999-12-31#23:59:59</end_time>
343 + <second>18</second>
344 + </interval>
345 + <interval>
346 + <start_time>1970-01-01#00:00:00</start_time>
347 + <end_time>2017-01-01#00:00:00</end_time>
348 + <second>17</second>
349 + </interval>
350 + </leapsecond>
351 + <GPS_distance_threshold_degree>
352 + 4e-5
353 + </GPS_distance_threshold_degree>
354 +</config>
355 +{{/code}}
356 +
357 +
287 287  == Handling Nodes During Download ==
288 288  
289 289  1. (((
5Hz_node_programming.labels.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.KB
Size
... ... @@ -1,0 +1,1 @@
1 +109.8 KB
Content