Skip to Content
Last modified by robert on 2026/01/19 17:43
From version 96.2
edited by KB
on 2026/01/19 13:47
Change comment: There is no comment for this version
To version 93.1
edited by KB
on 2026/01/19 11:55
Change comment: IGU-16 3C (5Hz node) programming screen set at 250 Hz. Ensure that the highlighted areas are set!

Summary

Details

Page properties
Content
... ... @@ -6,9 +6,9 @@
6 6  
7 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, '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 '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 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  
... ... @@ -21,13 +21,12 @@
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.
24 +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" data-xwiki-image-label="IGU-16 3C programming screen set at 250 Hz. Ensure that the circled areas are set!"]]
26 +[[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!"]]
28 +[[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.
44 +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).
46 +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,7 +67,7 @@
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.
69 +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 72  = **Installation** =
73 73  
... ... @@ -93,6 +93,8 @@
93 93  == 2. Node Placement ==
94 94  )))
95 95  
95 +**Protection**: Place nodes inside (landfill) biodegradable bags to minimize cleaning and cross-site soil contamination.
96 +
96 96  **Site Analysis**:
97 97  
98 98  * **Take compass measurements away from the sensor as it will affect your measurement.**
... ... @@ -123,14 +123,11 @@
123 123  ** 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.
124 124  
125 125  * **Post-Retrieval Charging**:
126 -** After retrieval, charge the instruments to about 50-60% (indicated by ORANGE LED) unless they are to be immediately re-deployed or transported.
127 -* **State of Charge (SoC) for Storage**:
128 -** Maintain a battery charge level of around 50-60% (i.e., ORANGE) for storage.
129 -** This charge level is recommended to prevent battery damage, and should be checked every six months.
130 -** Nodes should //__not be stored at full-charge (GREEN), or 0-charge (RED).__//
131 -** Storage at 0-charge damages lithium batteries**.**
132 -* **SoC for Transport:**
133 -** Charge levels for transport will be advised by the freighter. The required SoC will depend on volume and transport method (air, land, sea).
127 +** After retrieval, charge the instruments to about 50-60% (indicated as "orange" level) unless they are to be immediately re-deployed.
128 +* **Storage and Shipping Charge Level**:
129 +** Maintain a battery charge level of around 50-60% (e.g. "orange") for both storage and shipping purposes.
130 +** This charge level is recommended to prevent battery damage and is safe for transportation.
131 +** Nodes should not be stored fully charged, and **they should especially not be stored with 0 charge as this damages lithium batteries.**
134 134  
135 135  (((
136 136  == 6. Data Sharing and Metadata Creation ==
... ... @@ -138,7 +138,7 @@
138 138  
139 139  **GPS Data**:
140 140  
141 -* Ensure you have __carefully documented__ precise lat/lon locations for each station.
139 +* Ensure you have documented precise lat/lon locations for each station and **DOCUMENTED THIS CAREFULLY**
142 142  
143 143  **Photo Sharing**:
144 144  
... ... @@ -211,22 +211,20 @@
211 211  (((
212 212  == 2. Disassembling the Node: ==
213 213  
214 -* For the IGU-16HR, remove the battery section (bottom half) from the sensor by unscrewing the spike section counter-clockwise.
212 +* For the IGU-16HR, remove the battery (bottom half) from the sensor. This is done by unscrewing the spikes counter-clockwise.
215 215  )))
216 216  
217 217  (((
218 218  == 3. Setting Nodes in the Charging Box: ==
219 219  
220 -* Connect to a safe indoor power supply, and turn on (red rocker switch).
221 -* Charging will begin automatically when nodes are inserted in the charging rack.
222 -* Place IGU-16HR battery sections upside-down in the rack, oriented with the terminal connectors.
218 +* Place 1-16 IGU-16HR battery components upside-down into the charger, assuring they are oriented properly.
223 223  )))
224 224  
225 225  (((
226 226  == 4. Monitoring the Charging Process: ==
227 227  
228 -* Lights adjacent to the batteries will illuminate, indicating that charging is underway.
229 -* 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.
224 +* 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.
225 +* 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.
230 230  )))
231 231  
232 232  (((
... ... @@ -416,23 +416,21 @@
416 416  
417 417  = **Cleaning** =
418 418  
419 -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.
415 +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.
420 420  
421 421  = **Weights (for shipping)** =
422 422  
423 423  The weights of bags of nodes, as well as data harvesters and node chargers, are listed below:
424 424  
425 -1 bag + 6*IGU-16HR nodes: 18 kg
421 +1 bag + 6 SP (IGU-16HR) nodes: 18 kg
426 426  
427 -1*IGU-16HR data harvester: 21.5 kg
423 +1 SP (IGU-16HR) data harvester: 21.5 kg
428 428  
429 -1*IGU-16HR charger: 26.3 kg
425 +1 SP (IGU-16HR) charger: 26.3 kg
430 430  
431 -1*BD3C-5 charger (with and without 16 cables): 21 kg / 14.5 kg
427 +1 BB (BD3C-5) charger/data harvester (with and without 16 cables): 21 kg / 14.5 kg
432 432  
433 -1 case + 5*BD3C-5 nodes: 22 kg (aggregate battery weight <5kg, 168Wh)
434 -
435 -1 case + 6*BD3C-5 nodes: 25 kg (aggregate battery weight >5kg, 168Wh)
429 +1 case + 5 BB (BD3C-5) nodes and 6 BB nodes: 22 kg / 25 kg
436 436  )))
437 437  
438 438  (% 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