Skip to Content
Last modified by robert on 2026/02/27 19:58
From version 108.1
edited by robert
on 2026/02/18 14:46
Change comment: There is no comment for this version
To version 96.3
edited by KB
on 2026/01/19 13:47
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,9 +25,9 @@
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 +[[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!"]]
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 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!"]]
31 31  
32 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.
... ... @@ -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" %)
... ... @@ -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.
330 +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.**
332 +**The BD3C-5 data does not require a polarity inversion.**
337 337  
338 338  == 18 Leap Second bug ==
339 339  
... ... @@ -418,62 +418,9 @@
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 bandpass filter>>image:IGU16_N_huddle.png]]
435 -
436 -== IGU 16-1C ==
437 -
438 -The 1C nodes seem to have the same response as the 3-channel IGU-16HR-3C (above), however the response posted at IRIS-NRL seems to imply that there is no poles and zeros information (e.g. a flat/linear response). This is 100% not so.
439 -
440 -[[IGU-16 1C, X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz bandpass filter. Seems to be same response as IGU-16HR-3C.>>image:IGU16_1C_Z_huddle.png]]
441 -
442 -== BD3C-5 ==
443 -
444 - 'BD3C': {'poles':[(-1720.4+0j), (-1.2+0.9j), (-1.2-0.9j)],
445 - 'zeros':[(14164+0j), (-7162+0j), 0j, 0j],
446 - 'gain':1.69726e-05,
447 - 'sensitivity': 702651512.6046528}
448 -
449 -Above 0.5 Hz, the BD3C-5 response fits well:
450 -
451 -[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:BD3C_Z_huddle.0.5.png]]
452 -
453 -[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz bandpass filter>>image:BD3C_N_huddle.0.5.png]]
454 -
455 -(% class="wikigeneratedid" %)
456 -Below the corner frequency 0.2 Hz (5 seconds) the response still does a good job, but may need to be dialed in a bit. In the next two figures the filter is 0.1 to 5 Hz. We are looking into this..
457 -
458 -
459 -[[BD3C **0.1 **to 5 Hz bandpass filter>>image:BD3C_Z_huddle.0.1.png]]
460 -
461 -[[BD3C **0.1** to 5 Hz bandpass filter>>image:BD3C_N_huddle.0.1.png]]
462 -
463 -== IGU-16 Horizontal noise & how to avoid ==
464 -
465 -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.
466 -
467 -[[IGU-16HR-3C 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]]
468 -
469 -(% class="wikigeneratedid" %)
470 -The BD3C-5 nodes do not have this issue:
471 -
472 -[[BD3C-5 test, as above. There is no additional noise on the horizontal channels.>>image:BD3C_psd.png]]
473 -
474 474  = **Cleaning** =
475 475  
476 -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.
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.
477 477  
478 478  = **Weights (for shipping)** =
479 479  
... ... @@ -573,8 +573,8 @@
573 573  |**Dimensions (LxHxW)**|558 x 357 x 300mm
574 574  |**Input rating**|100-210V - 50/60Hz
575 575  |**Power**|1000W
576 -|**Weight**|14.5 kg
577 -|**Weight with cables**|21 kg
519 +|**Weight**|14.5kg
520 +|**Weight with cables**|21kg
578 578  )))
579 579  
580 580  (% class="box" id="HSmartSoloBD3C-16PortableBatteryCharger" %)
... ... @@ -586,8 +586,8 @@
586 586  |**Dimensions (LxHxW)**|625 x 500 x 366mm
587 587  |**Input rating**|100-210V - 50/60Hz
588 588  |**Power**|100W
589 -|**Weight**|21.5 - 24 kg
590 -|**Capacity**|16 nodes
532 +|**Weight**|21.5 - 24kg
533 +|**Slots no.**|16
591 591  |**Download Speed**|20MB/sec/slot
592 592  )))
593 593  
... ... @@ -597,11 +597,11 @@
597 597  
598 598  [[image:20250729_124644.jpg]]
599 599  
600 -|**Dimensions (LxHxW)**|625 x 500 x 366 mm
601 -|**Input rating**|100-210V - 50/60 Hz
602 -|**Power**|640 W
603 -|**Weight**|26.3 kg
604 -|**Capacity**|16 nodes
543 +|**Dimensions (LxHxW)**|625 x 500 x 366mm
544 +|**Input rating**|100-210V - 50/60Hz
545 +|**Power**|640W
546 +|**Weight**|26.3kg
547 +|**Slots no.**|16
605 605  )))
606 606  
607 607  (% class="box" %)
... ... @@ -611,9 +611,9 @@
611 611  [[image:20250729_124957.jpg]]
612 612  
613 613  
614 -|**Dimensions (LxHxW)**|590 x 225 x 405 mm
615 -|**Weight**|8.2 kg
616 -|**Capacity**|6 nodes
557 +|**Dimensions (LxHxW)**|590 x 225 x 405mm
558 +|**Weight**|8.2kg
559 +|**Slots no.**|6
617 617  )))
618 618  
619 619  (% class="box" %)
... ... @@ -623,13 +623,9 @@
623 623  [[image:20250729_124502.jpg]]
624 624  
625 625  |**Dimensions (LxHxW)**|230 x 340 x 310mm
626 -|**Weight**|(((
627 -3.6kg (empty)
628 -
629 -18.0kg (full)
569 +|**Weight**|3.6kg
570 +|**Slots no.**|6
630 630  )))
631 -|**Capacity**|6 nodes
632 -)))
633 633  
634 634  (% class="box" %)
635 635  (((
... ... @@ -639,7 +639,7 @@
639 639  
640 640  |**Dimensions (LxHxW)**|225 x 200 x 550mm
641 641  |**Weight**|
642 -|**Capacity**|8 nodes
581 +|**Slots no.**|6
643 643  )))
644 644  )))
645 645  )))
BD3C_N_huddle.0.1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -72.1 KB
Content
BD3C_N_huddle.0.5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -73.3 KB
Content
BD3C_N_huddle.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -72.1 KB
Content
BD3C_Z_huddle.0.1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -52.1 KB
Content
BD3C_Z_huddle.0.5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -64.6 KB
Content
BD3C_Z_huddle.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -52.1 KB
Content
BD3C_psd.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -73.7 KB
Content
IGU16_1C_Z_huddle.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -72.3 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