Skip to Content
Last modified by robert on 2026/02/27 19:58
From version 94.3
edited by KB
on 2026/01/19 11:59
Change comment: There is no comment for this version
To version 105.2
edited by robert
on 2026/02/17 12:43
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.KB
1 +XWiki.robert
Content
... ... @@ -6,10 +6,12 @@
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. Not 'HR')**
12 12  
13 +Visit the [[SmartSolo page>>https://smartsolo.com/igu.html]] for more detail.
14 +
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  
15 15  (% class="box infomessage" %)
... ... @@ -23,10 +23,11 @@
23 23  
24 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.
25 25  
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"]]
28 +[[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"]]
27 27  
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"]]
30 +[[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!"]]
29 29  
32 +
30 30  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.
31 31  
32 32  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.
... ... @@ -41,9 +41,9 @@
41 41  
42 42  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.
43 43  
44 -Bluetooth (BB nodes only) should be turned OFF to conserve power.
47 +Bluetooth (BD3C-5 only) should be turned OFF to conserve power.
45 45  
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).
49 +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).
47 47  
48 48  {{info}}
49 49  **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!
... ... @@ -66,8 +66,10 @@
66 66  
67 67  == Animal-Proofing ==
68 68  
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.
72 +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.
70 70  
74 +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.
75 +
71 71  = **Installation** =
72 72  
73 73  (% class="box infomessage" %)
... ... @@ -92,8 +92,6 @@
92 92  == 2. Node Placement ==
93 93  )))
94 94  
95 -**Protection**: Place nodes inside (landfill) biodegradable bags to minimize cleaning and cross-site soil contamination.
96 -
97 97  **Site Analysis**:
98 98  
99 99  * **Take compass measurements away from the sensor as it will affect your measurement.**
... ... @@ -124,11 +124,14 @@
124 124  ** 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.
125 125  
126 126  * **Post-Retrieval Charging**:
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.**
130 +** After retrieval, charge the instruments to about 50-60% (indicated by ORANGE LED) unless they are to be immediately re-deployed or transported.
131 +* **State of Charge (SoC) for Storage**:
132 +** Maintain a battery charge level of around 50-60% (i.e., ORANGE) for storage.
133 +** This charge level is recommended to prevent battery damage, and should be checked every six months.
134 +** Nodes should //__not be stored at full-charge (GREEN), or 0-charge (RED).__//
135 +** Storage at 0-charge damages lithium batteries**.**
136 +* **SoC for Transport:**
137 +** Charge levels for transport will be advised by the freighter. The required SoC will depend on volume and transport method (air, land, sea).
132 132  
133 133  (((
134 134  == 6. Data Sharing and Metadata Creation ==
... ... @@ -136,7 +136,7 @@
136 136  
137 137  **GPS Data**:
138 138  
139 -* Ensure you have documented precise lat/lon locations for each station and **DOCUMENTED THIS CAREFULLY**
145 +* Ensure you have __carefully documented__ precise lat/lon locations for each station.
140 140  
141 141  **Photo Sharing**:
142 142  
... ... @@ -209,20 +209,22 @@
209 209  (((
210 210  == 2. Disassembling the Node: ==
211 211  
212 -* For the IGU-16HR, remove the battery (bottom half) from the sensor. This is done by unscrewing the spikes counter-clockwise.
218 +* For the IGU-16HR, remove the battery section (bottom half) from the sensor by unscrewing the spike section counter-clockwise.
213 213  )))
214 214  
215 215  (((
216 216  == 3. Setting Nodes in the Charging Box: ==
217 217  
218 -* Place 1-16 IGU-16HR battery components upside-down into the charger, assuring they are oriented properly.
224 +* Connect to a safe indoor power supply, and turn on (red rocker switch).
225 +* Charging will begin automatically when nodes are inserted in the charging rack.
226 +* Place IGU-16HR battery sections upside-down in the rack, oriented with the terminal connectors.
219 219  )))
220 220  
221 221  (((
222 222  == 4. Monitoring the Charging Process: ==
223 223  
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.
232 +* Lights adjacent to the batteries will illuminate, indicating that charging is underway.
233 +* 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.
226 226  )))
227 227  
228 228  (((
... ... @@ -323,9 +323,9 @@
323 323  
324 324  == Smart Solo IGU-16HR Polarity Notice ==
325 325  
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.
334 +See [[5Hz Node Polarity Issues>>https://auspass.edu.au/xwiki/bin/view/Data/AusPass%20Data/#HSmartSoloNodePolarityIssues]] 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.
327 327  
328 -**The BD3C-5 data does not require a polarity inversion.**
336 +**The BD3C-5 data does not require any sort of polarity inversion.**
329 329  
330 330  == 18 Leap Second bug ==
331 331  
... ... @@ -410,23 +410,59 @@
410 410  
411 411  ----
412 412  
421 += Instrument Response =
422 +
423 +We are aware that there are various different published responses for these instruments and trust very few of them. One has to be careful with how polarity is handled between groups as well, and if one is working in integer counts (the ANSIR default) or mV (unclear why anyone would use this as it makes file sizes enormous). The response information published below is in **counts** and seems to fit well in huddle tests. Note that the response is the same for all channels and all units (e.g. there are no bespoke calibrations!), all appear to be sample rate insensitive, and the IGU data has been inverted (multiplied by -1) as described here: [[5Hz Node Polarity Issues>>https://auspass.edu.au/xwiki/bin/view/Data/AusPass%20Data/#HSmartSoloNodePolarityIssues]]
424 +
425 +== IGU 16HR-3C ==
426 +
427 + '16HR3C': {'poles':[(-22.211059+22.217768j), (-22.211059-22.217768j)],
428 + 'zeros':[0j, 0j],
429 + 'gain':1,
430 + 'sensitivity': 257019225.55108312}
431 +
432 +[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:IGU16_Z_huddle.png]]
433 +
434 +[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:IGU16_N_huddle.png]]
435 +
436 +== IGU 16-1C ==
437 +
438 +The 1C nodes seem to have a slightly different response to the 3C (TBA)
439 +
440 +== BD3C-5 ==
441 +
442 + 'BD3C': {'poles':[(-1720.4+0j), (-1.2+0.9j), (-1.2-0.9j)],
443 + 'zeros':[(14164+0j), (-7162+0j), 0j, 0j],
444 + 'gain':1.69726e-05,
445 + 'sensitivity': 702651512.6046528}
446 +
447 +*image TBA but they have been created in the past~-~- we are 100% confident our published responses are correct
448 +
449 +== Horizontal noise & how to avoid ==
450 +
451 +The 5 Hz nodes are susceptible to horizontal noise due to the placement of geophones in the units, **but this can be mitigated by completely burying the units flush with the ground.** In the below example, the node was set on the floor of our basement set on its plastic carrying case support. As such the amount of horizontal noise noticeably increases above ~~ 10Hz.
452 +
453 +[[Power spectrum huddle test vs a CMG-6TD (S1) and TC120/Centaur combo. The N and E channels have excess noise above 10Hz due to "sticking up" out of the ground.>>image:IGU16_spectrum.png]]
454 +
413 413  = **Cleaning** =
414 414  
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.
457 +When assembled, the nodes are water resistant but not submersible. They can handle a good spray and wipe-down. A stiff plastic brush is helpful to reach areas between the metal spikes on the bottom.
416 416  
417 417  = **Weights (for shipping)** =
418 418  
419 419  The weights of bags of nodes, as well as data harvesters and node chargers, are listed below:
420 420  
421 -1 bag + 6 SP (IGU-16HR) nodes: 18 kg
463 +1 bag + 6*IGU-16HR nodes: 18 kg
422 422  
423 -1 SP (IGU-16HR) data harvester: 21.5 kg
465 +1*IGU-16HR data harvester: 21.5 kg
424 424  
425 -1 SP (IGU-16HR) charger: 26.3 kg
467 +1*IGU-16HR charger: 26.3 kg
426 426  
427 -1 BB (BD3C-5) charger/data harvester (with and without 16 cables): 21 kg / 14.5 kg
469 +1*BD3C-5 charger (with and without 16 cables): 21 kg / 14.5 kg
428 428  
429 -1 case + 5 BB (BD3C-5) nodes and 6 BB nodes: 22 kg / 25 kg
471 +1 case + 5*BD3C-5 nodes: 22 kg (aggregate battery weight <5kg, 168Wh)
472 +
473 +1 case + 6*BD3C-5 nodes: 25 kg (aggregate battery weight >5kg, 168Wh)
430 430  )))
431 431  
432 432  (% class="col-xs-12 col-sm-4" %)
... ... @@ -510,8 +510,8 @@
510 510  |**Dimensions (LxHxW)**|558 x 357 x 300mm
511 511  |**Input rating**|100-210V - 50/60Hz
512 512  |**Power**|1000W
513 -|**Weight**|14.5kg
514 -|**Weight with cables**|21kg
557 +|**Weight**|14.5 kg
558 +|**Weight with cables**|21 kg
515 515  )))
516 516  
517 517  (% class="box" id="HSmartSoloBD3C-16PortableBatteryCharger" %)
... ... @@ -523,8 +523,8 @@
523 523  |**Dimensions (LxHxW)**|625 x 500 x 366mm
524 524  |**Input rating**|100-210V - 50/60Hz
525 525  |**Power**|100W
526 -|**Weight**|21.5 - 24kg
527 -|**Slots no.**|16
570 +|**Weight**|21.5 - 24 kg
571 +|**Capacity**|16 nodes
528 528  |**Download Speed**|20MB/sec/slot
529 529  )))
530 530  
... ... @@ -534,11 +534,11 @@
534 534  
535 535  [[image:20250729_124644.jpg]]
536 536  
537 -|**Dimensions (LxHxW)**|625 x 500 x 366mm
538 -|**Input rating**|100-210V - 50/60Hz
539 -|**Power**|640W
540 -|**Weight**|26.3kg
541 -|**Slots no.**|16
581 +|**Dimensions (LxHxW)**|625 x 500 x 366 mm
582 +|**Input rating**|100-210V - 50/60 Hz
583 +|**Power**|640 W
584 +|**Weight**|26.3 kg
585 +|**Capacity**|16 nodes
542 542  )))
543 543  
544 544  (% class="box" %)
... ... @@ -548,9 +548,9 @@
548 548  [[image:20250729_124957.jpg]]
549 549  
550 550  
551 -|**Dimensions (LxHxW)**|590 x 225 x 405mm
552 -|**Weight**|8.2kg
553 -|**Slots no.**|6
595 +|**Dimensions (LxHxW)**|590 x 225 x 405 mm
596 +|**Weight**|8.2 kg
597 +|**Capacity**|6 nodes
554 554  )))
555 555  
556 556  (% class="box" %)
... ... @@ -560,9 +560,13 @@
560 560  [[image:20250729_124502.jpg]]
561 561  
562 562  |**Dimensions (LxHxW)**|230 x 340 x 310mm
563 -|**Weight**|3.6kg
564 -|**Slots no.**|6
607 +|**Weight**|(((
608 +3.6kg (empty)
609 +
610 +18.0kg (full)
565 565  )))
612 +|**Capacity**|6 nodes
613 +)))
566 566  
567 567  (% class="box" %)
568 568  (((
... ... @@ -572,7 +572,7 @@
572 572  
573 573  |**Dimensions (LxHxW)**|225 x 200 x 550mm
574 574  |**Weight**|
575 -|**Slots no.**|6
623 +|**Capacity**|8 nodes
576 576  )))
577 577  )))
578 578  )))
5S_node_programming.labels.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.KB
Size
... ... @@ -1,0 +1,1 @@
1 +114.2 KB
Content
IGU16_N_huddle.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.robert
Size
... ... @@ -1,0 +1,1 @@
1 +65.7 KB
Content
IGU16_Z_huddle.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.robert
Size
... ... @@ -1,0 +1,1 @@
1 +67.4 KB
Content
IGU16_spectrum.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.robert
Size
... ... @@ -1,0 +1,1 @@
1 +65.0 KB
Content