Skip to Content
Last modified by KB on 2025/12/04 12:33
From version 88.1
edited by robert
on 2025/10/27 16:35
Change comment: There is no comment for this version
To version 90.1
edited by KB
on 2025/12/04 12:31
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,7 +4,7 @@
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 9  * **SmartSolo IGU 16HR 3C (5 Hz Short Period)**
10 10  * **SmartSolo BD3C-5 (5 Second Broadband)**
... ... @@ -12,6 +12,11 @@
12 12  
13 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.
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 +
15 15  ----
16 16  
17 17  = **Programming Defaults** =
... ... @@ -233,9 +233,8 @@
233 233  
234 234  
235 235  {{{
241 + }}}
236 236  
237 -}}}
238 -
239 239  ----
240 240  
241 241  = **Downloading and Converting Seismic Data to MiniSeed Format** =
... ... @@ -321,6 +321,34 @@
321 321  
322 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 323  
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 +
324 324  == Handling Nodes During Download ==
325 325  
326 326  1. (((