Skip to Content
Last modified by robert on 2026/02/27 19:58
From version 104.1
edited by robert
on 2026/02/16 18:29
Change comment: There is no comment for this version
To version 94.2
edited by KB
on 2026/01/19 11:58
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
... ... @@ -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  
... ... @@ -23,11 +23,10 @@
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 -[[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"]]
26 +[[IGU-16 3C (short period node) programming screen set at 250 Hz. Ensure that the highlighted 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 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,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.
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 -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  
95 +**Protection**: Place nodes inside (landfill) biodegradable bags to minimize cleaning and cross-site soil contamination.
96 +
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).
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.**
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.
139 +* 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.
212 +* 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.
218 +* 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.
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 232  )))
233 233  
234 234  (((
... ... @@ -329,9 +329,9 @@
329 329  
330 330  == Smart Solo IGU-16HR Polarity Notice ==
331 331  
332 -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.
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.
333 333  
334 -**The BD3C-5 data does not require any sort of polarity inversion.**
328 +**The BD3C-5 data does not require a polarity inversion.**
335 335  
336 336  == 18 Leap Second bug ==
337 337  
... ... @@ -416,59 +416,23 @@
416 416  
417 417  ----
418 418  
419 -= Instrument Response =
420 -
421 -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]]
422 -
423 -== IGU 16HR-3C ==
424 -
425 - '16HR3C': {'poles':[(-22.211059+22.217768j), (-22.211059-22.217768j)],
426 - 'zeros':[0j, 0j],
427 - 'gain':1,
428 - 'sensitivity': 257019225.55108312}
429 -
430 -[[X axis is samples (.01 s), Y axis is velocity (m/s)>>image:IGU16_Z_huddle.png]]
431 -
432 -[[X axis is samples (.01 s), Y axis is velocity (m/s)>>image:IGU16_N_huddle.png]]
433 -
434 -== IGU 16-1C ==
435 -
436 -The 1C nodes seem to have a slightly different response to the 3C (TBA)
437 -
438 -== BD3C-5 ==
439 -
440 - 'BD3C': {'poles':[(-1720.4+0j), (-1.2+0.9j), (-1.2-0.9j)],
441 - 'zeros':[(14164+0j), (-7162+0j), 0j, 0j],
442 - 'gain':1.69726e-05,
443 - 'sensitivity': 702651512.6046528}
444 -
445 -*image TBA but they have been created in the past~-~- we are 100% confident our published responses are correct
446 -
447 -== Horizontal noise & how to avoid ==
448 -
449 -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.
450 -
451 -[[Power spectrum huddle test vs a CMG-6TD (S1) and TC120/Centaur combo, all filtered 0.5-5 Hz. The N and E channels have excess noise above 10Hz due to "sticking up" out of the ground.>>image:IGU16_spectrum.png]]
452 -
453 453  = **Cleaning** =
454 454  
455 -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.
456 456  
457 457  = **Weights (for shipping)** =
458 458  
459 459  The weights of bags of nodes, as well as data harvesters and node chargers, are listed below:
460 460  
461 -1 bag + 6*IGU-16HR nodes: 18 kg
421 +1 bag + 6 SP (IGU-16HR) nodes: 18 kg
462 462  
463 -1*IGU-16HR data harvester: 21.5 kg
423 +1 SP (IGU-16HR) data harvester: 21.5 kg
464 464  
465 -1*IGU-16HR charger: 26.3 kg
425 +1 SP (IGU-16HR) charger: 26.3 kg
466 466  
467 -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
468 468  
469 -1 case + 5*BD3C-5 nodes: 22 kg (aggregate battery weight <5kg, 168Wh)
470 -
471 -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
472 472  )))
473 473  
474 474  (% class="col-xs-12 col-sm-4" %)
... ... @@ -552,8 +552,8 @@
552 552  |**Dimensions (LxHxW)**|558 x 357 x 300mm
553 553  |**Input rating**|100-210V - 50/60Hz
554 554  |**Power**|1000W
555 -|**Weight**|14.5 kg
556 -|**Weight with cables**|21 kg
513 +|**Weight**|14.5kg
514 +|**Weight with cables**|21kg
557 557  )))
558 558  
559 559  (% class="box" id="HSmartSoloBD3C-16PortableBatteryCharger" %)
... ... @@ -565,8 +565,8 @@
565 565  |**Dimensions (LxHxW)**|625 x 500 x 366mm
566 566  |**Input rating**|100-210V - 50/60Hz
567 567  |**Power**|100W
568 -|**Weight**|21.5 - 24 kg
569 -|**Capacity**|16 nodes
526 +|**Weight**|21.5 - 24kg
527 +|**Slots no.**|16
570 570  |**Download Speed**|20MB/sec/slot
571 571  )))
572 572  
... ... @@ -576,11 +576,11 @@
576 576  
577 577  [[image:20250729_124644.jpg]]
578 578  
579 -|**Dimensions (LxHxW)**|625 x 500 x 366 mm
580 -|**Input rating**|100-210V - 50/60 Hz
581 -|**Power**|640 W
582 -|**Weight**|26.3 kg
583 -|**Capacity**|16 nodes
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
584 584  )))
585 585  
586 586  (% class="box" %)
... ... @@ -590,9 +590,9 @@
590 590  [[image:20250729_124957.jpg]]
591 591  
592 592  
593 -|**Dimensions (LxHxW)**|590 x 225 x 405 mm
594 -|**Weight**|8.2 kg
595 -|**Capacity**|6 nodes
551 +|**Dimensions (LxHxW)**|590 x 225 x 405mm
552 +|**Weight**|8.2kg
553 +|**Slots no.**|6
596 596  )))
597 597  
598 598  (% class="box" %)
... ... @@ -602,13 +602,9 @@
602 602  [[image:20250729_124502.jpg]]
603 603  
604 604  |**Dimensions (LxHxW)**|230 x 340 x 310mm
605 -|**Weight**|(((
606 -3.6kg (empty)
607 -
608 -18.0kg (full)
563 +|**Weight**|3.6kg
564 +|**Slots no.**|6
609 609  )))
610 -|**Capacity**|6 nodes
611 -)))
612 612  
613 613  (% class="box" %)
614 614  (((
... ... @@ -618,7 +618,7 @@
618 618  
619 619  |**Dimensions (LxHxW)**|225 x 200 x 550mm
620 620  |**Weight**|
621 -|**Capacity**|8 nodes
575 +|**Slots no.**|6
622 622  )))
623 623  )))
624 624  )))
5S_node_programming.labels.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.KB
Size
... ... @@ -1,1 +1,0 @@
1 -114.2 KB
Content
IGU16_N_huddle.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -65.7 KB
Content
IGU16_Z_huddle.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -67.4 KB
Content
IGU16_spectrum.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -65.0 KB
Content