Skip to Content
Last modified by robert on 2026/01/19 17:43
From version 89.3
edited by robert
on 2025/10/29 10:39
Change comment: There is no comment for this version
To version 94.5
edited by KB
on 2026/01/19 13:22
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:5S_node_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  
... ... @@ -36,9 +36,9 @@
36 36  
37 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.
38 38  
39 -Bluetooth (BB nodes only) should be turned OFF to conserve power.
44 +Bluetooth (BD3C-5 only) should be turned OFF to conserve power.
40 40  
41 -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).
42 42  
43 43  {{info}}
44 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!
... ... @@ -61,7 +61,7 @@
61 61  
62 62  == Animal-Proofing ==
63 63  
64 -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.
65 65  
66 66  = **Installation** =
67 67  
... ... @@ -87,8 +87,6 @@
87 87  == 2. Node Placement ==
88 88  )))
89 89  
90 -**Protection**: Place nodes inside (landfill) biodegradable bags to minimize cleaning and cross-site soil contamination.
91 -
92 92  **Site Analysis**:
93 93  
94 94  * **Take compass measurements away from the sensor as it will affect your measurement.**
... ... @@ -119,11 +119,14 @@
119 119  ** 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.
120 120  
121 121  * **Post-Retrieval Charging**:
122 -** After retrieval, charge the instruments to about 50-60% (indicated as "orange" level) unless they are to be immediately re-deployed.
123 -* **Storage and Shipping Charge Level**:
124 -** Maintain a battery charge level of around 50-60% (e.g. "orange") for both storage and shipping purposes.
125 -** This charge level is recommended to prevent battery damage and is safe for transportation.
126 -** 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).
127 127  
128 128  (((
129 129  == 6. Data Sharing and Metadata Creation ==
... ... @@ -131,7 +131,7 @@
131 131  
132 132  **GPS Data**:
133 133  
134 -* 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.
135 135  
136 136  **Photo Sharing**:
137 137  
... ... @@ -204,20 +204,22 @@
204 204  (((
205 205  == 2. Disassembling the Node: ==
206 206  
207 -* 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.
208 208  )))
209 209  
210 210  (((
211 211  == 3. Setting Nodes in the Charging Box: ==
212 212  
213 -* 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.
214 214  )))
215 215  
216 216  (((
217 217  == 4. Monitoring the Charging Process: ==
218 218  
219 -* 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.
220 -* 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.
221 221  )))
222 222  
223 223  (((
... ... @@ -316,13 +316,15 @@
316 316  )))
317 317  )))
318 318  
319 -== Smart Solo Z Polarity bug (SP nodes ONLY!) ==
327 +== Smart Solo IGU-16HR Polarity Notice ==
320 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.**
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.
322 322  
331 +**The BD3C-5 data does not require a polarity inversion.**
332 +
323 323  == 18 Leap Second bug ==
324 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.
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.
326 326  
327 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 328  
5Hz_node_programming.labels.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.KB
Size
... ... @@ -1,0 +1,1 @@
1 +109.8 KB
Content