Skip to Content
Last modified by robert on 2026/01/19 17:43
From version 98.1
edited by robert
on 2026/01/19 17:43
Change comment: There is no comment for this version
To version 89.2
edited by robert
on 2025/10/28 18:02
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -4,30 +4,24 @@
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, and one type of one-channel node:
8 8  
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)**
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)**
12 12  
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 +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 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 -
20 20  ----
21 21  
22 22  = **Programming Defaults** =
23 23  
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 +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.
25 25  
26 -[[IGU16HR-3C programming screen set at 250 Hz. Ensure circled areas are set!>>image:5Hz_node_programming.labels.png||alt="IGU-16 3C programming screen"]]
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"]]
27 27  
28 -[[BD3C-5 programming screen set at 250 Hz. Ensure circled areas are set!>>image:5S_node_programming.labels.png||alt="BD3C-5 programming screen set at 250 hz. Ensure that the circled areas are set!"]]
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"]]
29 29  
30 -
31 31  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.
32 32  
33 33  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.
... ... @@ -42,9 +42,9 @@
42 42  
43 43  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.
44 44  
45 -Bluetooth (BD3C-5 only) should be turned OFF to conserve power.
39 +Bluetooth (BB nodes only) should be turned OFF to conserve power.
46 46  
47 -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).
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).
48 48  
49 49  {{info}}
50 50  **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!
... ... @@ -67,10 +67,8 @@
67 67  
68 68  == Animal-Proofing ==
69 69  
70 -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.
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.
71 71  
72 -If you come to collect your node and it is missing~-~- LOOK FOR IT! It may not have gotten far. We have found dozens of nodes by spending 15 minutes looking for them.
73 -
74 74  = **Installation** =
75 75  
76 76  (% class="box infomessage" %)
... ... @@ -95,6 +95,8 @@
95 95  == 2. Node Placement ==
96 96  )))
97 97  
90 +**Protection**: Place nodes inside (landfill) biodegradable bags to minimize cleaning and cross-site soil contamination.
91 +
98 98  **Site Analysis**:
99 99  
100 100  * **Take compass measurements away from the sensor as it will affect your measurement.**
... ... @@ -125,14 +125,11 @@
125 125  ** 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.
126 126  
127 127  * **Post-Retrieval Charging**:
128 -** After retrieval, charge the instruments to about 50-60% (indicated by ORANGE LED) unless they are to be immediately re-deployed or transported.
129 -* **State of Charge (SoC) for Storage**:
130 -** Maintain a battery charge level of around 50-60% (i.e., ORANGE) for storage.
131 -** This charge level is recommended to prevent battery damage, and should be checked every six months.
132 -** Nodes should //__not be stored at full-charge (GREEN), or 0-charge (RED).__//
133 -** Storage at 0-charge damages lithium batteries**.**
134 -* **SoC for Transport:**
135 -** Charge levels for transport will be advised by the freighter. The required SoC will depend on volume and transport method (air, land, sea).
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.**
136 136  
137 137  (((
138 138  == 6. Data Sharing and Metadata Creation ==
... ... @@ -140,7 +140,7 @@
140 140  
141 141  **GPS Data**:
142 142  
143 -* Ensure you have __carefully documented__ precise lat/lon locations for each station.
134 +* Ensure you have documented precise lat/lon locations for each station and **DOCUMENTED THIS CAREFULLY**
144 144  
145 145  **Photo Sharing**:
146 146  
... ... @@ -213,22 +213,20 @@
213 213  (((
214 214  == 2. Disassembling the Node: ==
215 215  
216 -* For the IGU-16HR, remove the battery section (bottom half) from the sensor by unscrewing the spike section counter-clockwise.
207 +* For the IGU-16HR, remove the battery (bottom half) from the sensor. This is done by unscrewing the spikes counter-clockwise.
217 217  )))
218 218  
219 219  (((
220 220  == 3. Setting Nodes in the Charging Box: ==
221 221  
222 -* Connect to a safe indoor power supply, and turn on (red rocker switch).
223 -* Charging will begin automatically when nodes are inserted in the charging rack.
224 -* Place IGU-16HR battery sections upside-down in the rack, oriented with the terminal connectors.
213 +* Place 1-16 IGU-16HR battery components upside-down into the charger, assuring they are oriented properly.
225 225  )))
226 226  
227 227  (((
228 228  == 4. Monitoring the Charging Process: ==
229 229  
230 -* Lights adjacent to the batteries will illuminate, indicating that charging is underway.
231 -* 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.
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.
232 232  )))
233 233  
234 234  (((
... ... @@ -327,15 +327,13 @@
327 327  )))
328 328  )))
329 329  
330 -== Smart Solo IGU-16HR Polarity Notice ==
319 +== Smart Solo Z Polarity bug (SP nodes ONLY!) ==
331 331  
332 -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.
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.**
333 333  
334 -**The BD3C-5 data does not require any sort of polarity inversion.**
335 -
336 336  == 18 Leap Second bug ==
337 337  
338 -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.
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.
339 339  
340 340  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.
341 341  
... ... @@ -418,23 +418,21 @@
418 418  
419 419  = **Cleaning** =
420 420  
421 -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.
408 +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.
422 422  
423 423  = **Weights (for shipping)** =
424 424  
425 425  The weights of bags of nodes, as well as data harvesters and node chargers, are listed below:
426 426  
427 -1 bag + 6*IGU-16HR nodes: 18 kg
414 +1 bag + 6 SP (IGU-16HR) nodes: 18 kg
428 428  
429 -1*IGU-16HR data harvester: 21.5 kg
416 +1 SP (IGU-16HR) data harvester: 21.5 kg
430 430  
431 -1*IGU-16HR charger: 26.3 kg
418 +1 SP (IGU-16HR) charger: 26.3 kg
432 432  
433 -1*BD3C-5 charger (with and without 16 cables): 21 kg / 14.5 kg
420 +1 BB (BD3C-5) charger/data harvester (with and without 16 cables): 21 kg / 14.5 kg
434 434  
435 -1 case + 5*BD3C-5 nodes: 22 kg (aggregate battery weight <5kg, 168Wh)
436 -
437 -1 case + 6*BD3C-5 nodes: 25 kg (aggregate battery weight >5kg, 168Wh)
422 +1 case + 5 BB (BD3C-5) nodes and 6 BB nodes: 22 kg / 25 kg
438 438  )))
439 439  
440 440  (% class="col-xs-12 col-sm-4" %)
5Hz_node_programming.labels.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.KB
Size
... ... @@ -1,1 +1,0 @@
1 -109.8 KB
Content
5S_node_programming.labels.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.KB
Size
... ... @@ -1,1 +1,0 @@
1 -114.2 KB
Content