Skip to Content
Last modified by robert on 2026/06/29 16:42
From version 95.1
edited by KB
on 2026/01/19 13:40
Change comment: There is no comment for this version
To version 113.1
edited by robert
on 2026/06/17 17:14
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)**
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)**
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:5S_node_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.
... ... @@ -68,6 +68,20 @@
68 68  
69 69  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 +
76 += External Power =
77 +
78 +Both the 5Hz IGU-16HR and 5s BD3C-5 can be optionally powered via external battery via either a replacement bottom half (the 5Hz nodes) or a battery cable accessory (BD3C-5) using standard lead acid batteries from 9-36v. We have done preliminary testing at 250 Hz with a 12v battery:
79 +
80 +- BD3C-5: ~~2 days of recording per 1 Ah
81 +
82 +- IGU16-HR 3C:  ~~3.5 days of recording per 1 Ah
83 +
84 +- IGU16-HR 1C: ~~7 days of recording per 1 Ah
85 +
86 +Of course, these can also be fit with a solar panel & charge controller which would then theoretically keep them going indefinitely (limited only by the disk storage, which at 250 Hz could be on the order of 12 months).
87 +
71 71  = **Installation** =
72 72  
73 73  (% class="box infomessage" %)
... ... @@ -94,14 +94,14 @@
94 94  
95 95  **Site Analysis**:
96 96  
97 -* **Take compass measurements away from the sensor as it will affect your measurement.**
98 -* Take photographs from various angles to document the site setup thoroughly.
99 -* Include a detailed site description in your notes
114 +* **Take compass measurements away from the sensor as it will affect your measurement. Use a stick or shovel to help align.**
115 +* Take photographs from various angles to document the site setup thoroughly. Have a colleague stand next to it pointing at it.
116 +* Include a detailed site description in your notes.
100 100  
101 101  == 3. GPS Considerations ==
102 102  
103 103  (% class="wikigeneratedid" %)
104 -The GPS antenna is at the top and center of the unit, and will (usually) only receive signal with a clear sky view directly above. The signal is able to penetrate plastic and terracotta planters and a thin layer of soil, but may struggle if the soil layer is too thick. **These nodes will not start recording without attaining a GPS lock** and repeated attempts will excessively drain the battery.
121 +The GPS antenna is at the top and center of the unit, and will (usually) only receive signal with a clear sky view directly above. The signal is able to penetrate plastic and terracotta planters and a thin (2 cm?) layer of soil, but may struggle if the soil layer is too thick. **These nodes will not start recording without attaining a GPS lock** and repeated attempts will excessively drain the battery.
105 105  
106 106  == 4. Visibility and Location Marking ==
107 107  
... ... @@ -109,8 +109,8 @@
109 109  
110 110  **GPS Marking**:
111 111  
112 -* Use a GPS device to mark the instrument's exact location.
113 -* Record this location in both your paper notes and the GPS device.
129 +* Use a GPS device to mark the instrument's exact location. Most modern cell phones can get to about a 3m error with their internal GPS also; you can probably also get away with investing a few dollars in a good app that shows error and lets you log markers.
130 +* Also write the GPS down on paper (ie your [[LOG SHEET>>http://auspass.edu.au/field/NODES_blank_fieldlog.pdf]]).
114 114  
115 115  == (% style="color:inherit; font-family:inherit; font-size:max(18px, min(20px, 14.4444px + 0.462963vw))" %)5. Charge Time, Pre-Deployment & Post-Deployment(%%) ==
116 116  
... ... @@ -307,7 +307,7 @@
307 307  
308 308  * Once a new project is created, the Data Transfer View panel will display connected nodes with details like series number and data size.
309 309  * If “Prospect not matched” appears, it simply means the new project doesn’t match the original programming project. This is not a concern.
310 -* Select all nodes and right-click to “force download”. This starts the download process.
327 +* Select all nodes and right-click to “force download”. This starts the download process.[[image:Smartsolo harvesting #4 copy.png]]
311 311  * Completed downloads will appear as new folders in the Downloaded Data panel.
312 312  )))
313 313  1. (((
... ... @@ -314,21 +314,24 @@
314 314  **Exporting Data in Readable Format**:
315 315  
316 316  * Go to the “Tool” menu and select “export seismic data”.
317 -* Tailor other parameters to personal preference and ensure "Sample Interval" matches the setting used during node reset.
318 -* Click “prepare” followed by “run” to start reformatting. Monitor this process in the small panel at the bottom left.
334 +* Tailor other parameters to project preference and ensure "Sample Interval" matches the setting used during node reset (note: the standard used by ANU is 4ms, or 250hz)
319 319  * (% class="box warningmessage" %)
320 320  (((
321 -* **Ensure to export data as "COUNTS" (int32), not "mV" (float). This is critical!**
322 -
323 -* **Set "Remove Gain" to the same decibel gain as during programming. By default ANU sets this to 24db for short period nodes (a scaling factor of 15.848932), and 6db (a factor of 2.0) for broadband nodes.**
337 +**Ensure export data is set to "COUNTS" (int32), not "mV" (float). This is critical!**
324 324  )))
339 +* Set "Remove Gain" to the same decibel gain as during programming. By default ANU sets this to 24db for short period nodes (a scaling factor of 15.848932), and 6db (a factor of 2.0) for broadband nodes.
340 +* Set "Remove DC" to "Yes" to centre the data around the zero value
341 +* Set the correct Start Time (UTC) and End Time (UTC) of the project to prevent the unnecessary export of older data
342 +* [[image:Smartsolo harvesting #9 copy.png]]
343 +* Click “prepare” followed by “run” to start reformatting. Monitor this process in the small panel at the bottom left.
344 +* The data will be exported to the SOLODATA folder. For a windows system, the following file explorer page is where you must navigate to to locate your project folder[[image:Smartsolo harvesting #8 copy.png]]
325 325  )))
326 326  
327 327  == Smart Solo IGU-16HR Polarity Notice ==
328 328  
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.
349 +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 330  
331 -**The BD3C-5 data does not require a polarity inversion.**
351 +**The BD3C-5 data does not require any sort of polarity inversion.**
332 332  
333 333  == 18 Leap Second bug ==
334 334  
... ... @@ -388,11 +388,8 @@
388 388  **Finalizing the Download**:
389 389  
390 390  * After downloading, mark the //"D"// box on your temporary labels to indicate completion.
391 -
392 -
393 393  )))
394 394  
395 -[[image:1706153266647-145.png||data-xwiki-image-style-alignment="center" height="340" width="603"]]
396 396  
397 397  
398 398  
... ... @@ -413,9 +413,62 @@
413 413  
414 414  ----
415 415  
433 += Instrument Response =
434 +
435 +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]]
436 +
437 +== IGU 16HR-3C ==
438 +
439 + '16HR3C': {'poles':[(-22.211059+22.217768j), (-22.211059-22.217768j)],
440 + 'zeros':[0j, 0j],
441 + 'gain':1,
442 + 'sensitivity': 257019225.55108312}
443 +
444 +[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:IGU16_Z_huddle.png]]
445 +
446 +[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz bandpass filter>>image:IGU16_N_huddle.png]]
447 +
448 +== IGU 16-1C ==
449 +
450 +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.
451 +
452 +[[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]]
453 +
454 +== BD3C-5 ==
455 +
456 + 'BD3C': {'poles':[(-1720.4+0j), (-1.2+0.9j), (-1.2-0.9j)],
457 + 'zeros':[(14164+0j), (-7162+0j), 0j, 0j],
458 + 'gain':1.69726e-05,
459 + 'sensitivity': 702651512.6046528}
460 +
461 +Above 0.5 Hz, the BD3C-5 response fits well:
462 +
463 +[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:BD3C_Z_huddle.0.5.png]]
464 +
465 +[[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]]
466 +
467 +(% class="wikigeneratedid" %)
468 +Below the corner frequency (0.2 Hz) the phase response still fares well, but amplitude response may need to be dialed in a bit (it seems a bit high). In the next two figures the filter is **0.1** to 5 Hz:
469 +
470 +
471 +[[BD3C **0.1 **to 5 Hz bandpass filter>>image:BD3C_Z_huddle.0.1.png]]
472 +
473 +[[BD3C **0.1** to 5 Hz bandpass filter>>image:BD3C_N_huddle.0.1.png]]
474 +
475 +== IGU-16 Horizontal noise & how to avoid ==
476 +
477 +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.
478 +
479 +[[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]]
480 +
481 +(% class="wikigeneratedid" %)
482 +The BD3C-5 nodes do not have this issue:
483 +
484 +[[BD3C-5 test, as above. There is no additional noise on the horizontal channels.>>image:BD3C_psd.png]]
485 +
416 416  = **Cleaning** =
417 417  
418 -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.
488 +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 419  
420 420  = **Weights (for shipping)** =
421 421  
... ... @@ -515,8 +515,8 @@
515 515  |**Dimensions (LxHxW)**|558 x 357 x 300mm
516 516  |**Input rating**|100-210V - 50/60Hz
517 517  |**Power**|1000W
518 -|**Weight**|14.5kg
519 -|**Weight with cables**|21kg
588 +|**Weight**|14.5 kg
589 +|**Weight with cables**|21 kg
520 520  )))
521 521  
522 522  (% class="box" id="HSmartSoloBD3C-16PortableBatteryCharger" %)
... ... @@ -528,8 +528,8 @@
528 528  |**Dimensions (LxHxW)**|625 x 500 x 366mm
529 529  |**Input rating**|100-210V - 50/60Hz
530 530  |**Power**|100W
531 -|**Weight**|21.5 - 24kg
532 -|**Slots no.**|16
601 +|**Weight**|21.5 - 24 kg
602 +|**Capacity**|16 nodes
533 533  |**Download Speed**|20MB/sec/slot
534 534  )))
535 535  
... ... @@ -539,11 +539,11 @@
539 539  
540 540  [[image:20250729_124644.jpg]]
541 541  
542 -|**Dimensions (LxHxW)**|625 x 500 x 366mm
543 -|**Input rating**|100-210V - 50/60Hz
544 -|**Power**|640W
545 -|**Weight**|26.3kg
546 -|**Slots no.**|16
612 +|**Dimensions (LxHxW)**|625 x 500 x 366 mm
613 +|**Input rating**|100-210V - 50/60 Hz
614 +|**Power**|640 W
615 +|**Weight**|26.3 kg
616 +|**Capacity**|16 nodes
547 547  )))
548 548  
549 549  (% class="box" %)
... ... @@ -553,9 +553,9 @@
553 553  [[image:20250729_124957.jpg]]
554 554  
555 555  
556 -|**Dimensions (LxHxW)**|590 x 225 x 405mm
557 -|**Weight**|8.2kg
558 -|**Slots no.**|6
626 +|**Dimensions (LxHxW)**|590 x 225 x 405 mm
627 +|**Weight**|8.2 kg
628 +|**Capacity**|6 nodes
559 559  )))
560 560  
561 561  (% class="box" %)
... ... @@ -565,9 +565,13 @@
565 565  [[image:20250729_124502.jpg]]
566 566  
567 567  |**Dimensions (LxHxW)**|230 x 340 x 310mm
568 -|**Weight**|3.6kg
569 -|**Slots no.**|6
638 +|**Weight**|(((
639 +3.6kg (empty)
640 +
641 +18.0kg (full)
570 570  )))
643 +|**Capacity**|6 nodes
644 +)))
571 571  
572 572  (% class="box" %)
573 573  (((
... ... @@ -577,7 +577,7 @@
577 577  
578 578  |**Dimensions (LxHxW)**|225 x 200 x 550mm
579 579  |**Weight**|
580 -|**Slots no.**|6
654 +|**Capacity**|8 nodes
581 581  )))
582 582  )))
583 583  )))
5S_node_programming.labels.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.KB
Size
... ... @@ -1,0 +1,1 @@
1 +114.2 KB
Content
BD3C_N_huddle.0.1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.robert
Size
... ... @@ -1,0 +1,1 @@
1 +72.1 KB
Content
BD3C_N_huddle.0.5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.robert
Size
... ... @@ -1,0 +1,1 @@
1 +73.3 KB
Content
BD3C_N_huddle.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.robert
Size
... ... @@ -1,0 +1,1 @@
1 +72.1 KB
Content
BD3C_Z_huddle.0.1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.robert
Size
... ... @@ -1,0 +1,1 @@
1 +52.1 KB
Content
BD3C_Z_huddle.0.5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.robert
Size
... ... @@ -1,0 +1,1 @@
1 +64.6 KB
Content
BD3C_Z_huddle.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.robert
Size
... ... @@ -1,0 +1,1 @@
1 +52.1 KB
Content
BD3C_psd.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.robert
Size
... ... @@ -1,0 +1,1 @@
1 +73.7 KB
Content
IGU16_1C_Z_huddle.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.robert
Size
... ... @@ -1,0 +1,1 @@
1 +72.3 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
Smartsolo harvesting #4 copy.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.JackD
Size
... ... @@ -1,0 +1,1 @@
1 +33.8 KB
Content
Smartsolo harvesting #4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.JackD
Size
... ... @@ -1,0 +1,1 @@
1 +33.8 KB
Content
Smartsolo harvesting #6 copy.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.JackD
Size
... ... @@ -1,0 +1,1 @@
1 +33.6 KB
Content
Smartsolo harvesting #8 copy.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.JackD
Size
... ... @@ -1,0 +1,1 @@
1 +38.3 KB
Content
Smartsolo harvesting #8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.JackD
Size
... ... @@ -1,0 +1,1 @@
1 +60.0 KB
Content
Smartsolo harvesting #9 copy.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.JackD
Size
... ... @@ -1,0 +1,1 @@
1 +28.7 KB
Content