Skip to Content
Last modified by robert on 2026/02/27 19:58
From version 105.2
edited by robert
on 2026/02/17 12:43
Change comment: There is no comment for this version
To version 94.4
edited by KB
on 2026/01/19 13:20
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,12 +6,10 @@
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)**
9 +* **SmartSolo IGU 16HR 3C (5 Hz, 'very' short period)**
10 10  * **SmartSolo BD3C-5 (5 second, short period)**
11 -* **SmartSolo IGU-16 1C (5 Hz, 'very' short period, single channel. Not 'HR')**
11 +* **SmartSolo IGU 16 1C (5 Hz, 'very' short period, single channel)**
12 12  
13 -Visit the [[SmartSolo page>>https://smartsolo.com/igu.html]] for more detail.
14 -
15 15  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.
16 16  
17 17  (% class="box infomessage" %)
... ... @@ -25,11 +25,10 @@
25 25  
26 26  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.
27 27  
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"]]
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"]]
29 29  
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!"]]
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"]]
31 31  
32 -
33 33  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.
34 34  
35 35  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.
... ... @@ -71,8 +71,6 @@
71 71  
72 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.
73 73  
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 -
76 76  = **Installation** =
77 77  
78 78  (% class="box infomessage" %)
... ... @@ -131,10 +131,10 @@
131 131  * **State of Charge (SoC) for Storage**:
132 132  ** Maintain a battery charge level of around 50-60% (i.e., ORANGE) for storage.
133 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).__//
129 +** Nodes should __not be stored at full-charge (GREEN), or 0-charge (RED).__
135 135  ** Storage at 0-charge damages lithium batteries**.**
136 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 +** Charge levels for transport will be advised by the freighter. The required SoC will usually fall between 0-60% depending on method (air, land, sea).
138 138  
139 139  (((
140 140  == 6. Data Sharing and Metadata Creation ==
... ... @@ -331,9 +331,9 @@
331 331  
332 332  == Smart Solo IGU-16HR Polarity Notice ==
333 333  
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.
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.
335 335  
336 -**The BD3C-5 data does not require any sort of polarity inversion.**
331 +**The BD3C-5 data does not require a polarity inversion.**
337 337  
338 338  == 18 Leap Second bug ==
339 339  
... ... @@ -418,59 +418,23 @@
418 418  
419 419  ----
420 420  
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 -
455 455  = **Cleaning** =
456 456  
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.
418 +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.
458 458  
459 459  = **Weights (for shipping)** =
460 460  
461 461  The weights of bags of nodes, as well as data harvesters and node chargers, are listed below:
462 462  
463 -1 bag + 6*IGU-16HR nodes: 18 kg
424 +1 bag + 6 SP (IGU-16HR) nodes: 18 kg
464 464  
465 -1*IGU-16HR data harvester: 21.5 kg
426 +1 SP (IGU-16HR) data harvester: 21.5 kg
466 466  
467 -1*IGU-16HR charger: 26.3 kg
428 +1 SP (IGU-16HR) charger: 26.3 kg
468 468  
469 -1*BD3C-5 charger (with and without 16 cables): 21 kg / 14.5 kg
430 +1 BB (BD3C-5) charger/data harvester (with and without 16 cables): 21 kg / 14.5 kg
470 470  
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)
432 +1 case + 5 BB (BD3C-5) nodes and 6 BB nodes: 22 kg / 25 kg
474 474  )))
475 475  
476 476  (% class="col-xs-12 col-sm-4" %)
... ... @@ -554,8 +554,8 @@
554 554  |**Dimensions (LxHxW)**|558 x 357 x 300mm
555 555  |**Input rating**|100-210V - 50/60Hz
556 556  |**Power**|1000W
557 -|**Weight**|14.5 kg
558 -|**Weight with cables**|21 kg
516 +|**Weight**|14.5kg
517 +|**Weight with cables**|21kg
559 559  )))
560 560  
561 561  (% class="box" id="HSmartSoloBD3C-16PortableBatteryCharger" %)
... ... @@ -567,8 +567,8 @@
567 567  |**Dimensions (LxHxW)**|625 x 500 x 366mm
568 568  |**Input rating**|100-210V - 50/60Hz
569 569  |**Power**|100W
570 -|**Weight**|21.5 - 24 kg
571 -|**Capacity**|16 nodes
529 +|**Weight**|21.5 - 24kg
530 +|**Slots no.**|16
572 572  |**Download Speed**|20MB/sec/slot
573 573  )))
574 574  
... ... @@ -578,11 +578,11 @@
578 578  
579 579  [[image:20250729_124644.jpg]]
580 580  
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
540 +|**Dimensions (LxHxW)**|625 x 500 x 366mm
541 +|**Input rating**|100-210V - 50/60Hz
542 +|**Power**|640W
543 +|**Weight**|26.3kg
544 +|**Slots no.**|16
586 586  )))
587 587  
588 588  (% class="box" %)
... ... @@ -592,9 +592,9 @@
592 592  [[image:20250729_124957.jpg]]
593 593  
594 594  
595 -|**Dimensions (LxHxW)**|590 x 225 x 405 mm
596 -|**Weight**|8.2 kg
597 -|**Capacity**|6 nodes
554 +|**Dimensions (LxHxW)**|590 x 225 x 405mm
555 +|**Weight**|8.2kg
556 +|**Slots no.**|6
598 598  )))
599 599  
600 600  (% class="box" %)
... ... @@ -604,13 +604,9 @@
604 604  [[image:20250729_124502.jpg]]
605 605  
606 606  |**Dimensions (LxHxW)**|230 x 340 x 310mm
607 -|**Weight**|(((
608 -3.6kg (empty)
609 -
610 -18.0kg (full)
566 +|**Weight**|3.6kg
567 +|**Slots no.**|6
611 611  )))
612 -|**Capacity**|6 nodes
613 -)))
614 614  
615 615  (% class="box" %)
616 616  (((
... ... @@ -620,7 +620,7 @@
620 620  
621 621  |**Dimensions (LxHxW)**|225 x 200 x 550mm
622 622  |**Weight**|
623 -|**Capacity**|8 nodes
578 +|**Slots no.**|6
624 624  )))
625 625  )))
626 626  )))
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