Changes for page SmartSolo Node Seismometers
Last modified by robert on 2026/06/29 16:42
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 18 removed)
- 5S_node_programming.labels.png
- BD3C_N_huddle.0.1.png
- BD3C_N_huddle.0.5.png
- BD3C_N_huddle.png
- BD3C_Z_huddle.0.1.png
- BD3C_Z_huddle.0.5.png
- BD3C_Z_huddle.png
- BD3C_psd.png
- IGU16_1C_Z_huddle.png
- IGU16_N_huddle.png
- IGU16_Z_huddle.png
- IGU16_spectrum.png
- Smartsolo harvesting #4 copy.png
- Smartsolo harvesting #4.png
- Smartsolo harvesting #6 copy.png
- Smartsolo harvesting #8 copy.png
- Smartsolo harvesting #8.png
- Smartsolo harvesting #9 copy.png
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. robert1 +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 -[[IGU16 HR-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 screenset 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,18 +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 -= 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 86 = **Installation** = 87 87 88 88 (% class="box infomessage" %) ... ... @@ -109,14 +109,14 @@ 109 109 110 110 **Site Analysis**: 111 111 112 -* **Take compass measurements away from the sensor as it will affect your measurement. Use a stick or shovel to help align.**113 -* Take photographs from various angles to document the site setup thoroughly. Have a colleague stand next to it pointing at it.114 -* Include a detailed site description in your notes .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 115 115 116 116 == 3. GPS Considerations == 117 117 118 118 (% class="wikigeneratedid" %) 119 -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.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. 120 120 121 121 == 4. Visibility and Location Marking == 122 122 ... ... @@ -124,8 +124,8 @@ 124 124 125 125 **GPS Marking**: 126 126 127 -* 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.128 -* AlsowritetheGPS downonpaper (ieyour[[LOGSHEET>>http://auspass.edu.au/field/NODES_blank_fieldlog.pdf]]).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 129 130 130 == (% style="color:inherit; font-family:inherit; font-size:max(18px, min(20px, 14.4444px + 0.462963vw))" %)5. Charge Time, Pre-Deployment & Post-Deployment(%%) == 131 131 ... ... @@ -322,7 +322,7 @@ 322 322 323 323 * Once a new project is created, the Data Transfer View panel will display connected nodes with details like series number and data size. 324 324 * If “Prospect not matched” appears, it simply means the new project doesn’t match the original programming project. This is not a concern. 325 -* Select all nodes and right-click to “force download”. This starts the download process. [[image:Smartsolo harvesting #4 copy.png]]310 +* Select all nodes and right-click to “force download”. This starts the download process. 326 326 * Completed downloads will appear as new folders in the Downloaded Data panel. 327 327 ))) 328 328 1. ((( ... ... @@ -329,24 +329,21 @@ 329 329 **Exporting Data in Readable Format**: 330 330 331 331 * Go to the “Tool” menu and select “export seismic data”. 332 -* 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) 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. 333 333 * (% class="box warningmessage" %) 334 334 ((( 335 -**Ensure export data is set to "COUNTS" (int32), not "mV" (float). This is critical!** 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.** 336 336 ))) 337 -* 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. 338 -* Set "Remove DC" to "Yes" to centre the data around the zero value 339 -* Set the correct Start Time (UTC) and End Time (UTC) of the project to prevent the unnecessary export of older data 340 -* [[image:Smartsolo harvesting #9 copy.png]] 341 -* Click “prepare” followed by “run” to start reformatting. Monitor this process in the small panel at the bottom left. 342 -* 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]] 343 343 ))) 344 344 345 345 == Smart Solo IGU-16HR Polarity Notice == 346 346 347 -See [[ 5HzNodePolarityIssues>>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. 348 348 349 -**The BD3C-5 data does not require a nysort ofpolarity inversion.**331 +**The BD3C-5 data does not require a polarity inversion.** 350 350 351 351 == 18 Leap Second bug == 352 352 ... ... @@ -406,8 +406,11 @@ 406 406 **Finalizing the Download**: 407 407 408 408 * After downloading, mark the //"D"// box on your temporary labels to indicate completion. 391 + 392 + 409 409 ))) 410 410 395 +[[image:1706153266647-145.png||data-xwiki-image-style-alignment="center" height="340" width="603"]] 411 411 412 412 413 413 ... ... @@ -428,78 +428,23 @@ 428 428 429 429 ---- 430 430 431 -= Instrument Response = 432 - 433 -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]] 434 - 435 -== IGU 16HR-3C == 436 - 437 - '16HR3C': {'poles':[(-22.211059+22.217768j), (-22.211059-22.217768j)], 438 - 'zeros':[0j, 0j], 439 - 'gain':1, 440 - 'sensitivity': 257019225.55108312} 441 - 442 -[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:IGU16_Z_huddle.png]] 443 - 444 -[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz bandpass filter>>image:IGU16_N_huddle.png]] 445 - 446 -== IGU 16-1C == 447 - 448 -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. 449 - 450 -[[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]] 451 - 452 -== BD3C-5 == 453 - 454 - 'BD3C': {'poles':[(-1720.4+0j), (-1.2+0.9j), (-1.2-0.9j)], 455 - 'zeros':[(14164+0j), (-7162+0j), 0j, 0j], 456 - 'gain':1.69726e-05, 457 - 'sensitivity': 702651512.6046528} 458 - 459 -Above 0.5 Hz, the BD3C-5 response fits well: 460 - 461 -[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:BD3C_Z_huddle.0.5.png]] 462 - 463 -[[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]] 464 - 465 -(% class="wikigeneratedid" %) 466 -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: 467 - 468 - 469 -[[BD3C **0.1 **to 5 Hz bandpass filter>>image:BD3C_Z_huddle.0.1.png]] 470 - 471 -[[BD3C **0.1** to 5 Hz bandpass filter>>image:BD3C_N_huddle.0.1.png]] 472 - 473 -== IGU-16 Horizontal noise & how to avoid == 474 - 475 -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. 476 - 477 -[[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]] 478 - 479 -(% class="wikigeneratedid" %) 480 -The BD3C-5 nodes do not have this issue: 481 - 482 -[[BD3C-5 test, as above. There is no additional noise on the horizontal channels.>>image:BD3C_psd.png]] 483 - 484 484 = **Cleaning** = 485 485 486 -When assembled, the nodes are water resistantbut not submersible.Theycan handle a good sprayandwipe-down. A stiffplasticbrush 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. 487 487 488 488 = **Weights (for shipping)** = 489 489 490 490 The weights of bags of nodes, as well as data harvesters and node chargers, are listed below: 491 491 492 -1 bag + 6 *IGU-16HR nodes: 18 kg424 +1 bag + 6 SP (IGU-16HR) nodes: 18 kg 493 493 494 -1 *IGU-16HR data harvester: 21.5 kg426 +1 SP (IGU-16HR) data harvester: 21.5 kg 495 495 496 -1 *IGU-16HR charger: 26.3 kg428 +1 SP (IGU-16HR) charger: 26.3 kg 497 497 498 -1 *BD3C-5 charger (with and without 16 cables): 21 kg / 14.5 kg430 +1 BB (BD3C-5) charger/data harvester (with and without 16 cables): 21 kg / 14.5 kg 499 499 500 -1 case + 5*BD3C-5 nodes: 22 kg (aggregate battery weight <5kg, 168Wh) 501 - 502 -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 503 503 ))) 504 504 505 505 (% class="col-xs-12 col-sm-4" %) ... ... @@ -583,8 +583,8 @@ 583 583 |**Dimensions (LxHxW)**|558 x 357 x 300mm 584 584 |**Input rating**|100-210V - 50/60Hz 585 585 |**Power**|1000W 586 -|**Weight**|14.5 kg587 -|**Weight with cables**|21 kg516 +|**Weight**|14.5kg 517 +|**Weight with cables**|21kg 588 588 ))) 589 589 590 590 (% class="box" id="HSmartSoloBD3C-16PortableBatteryCharger" %) ... ... @@ -596,8 +596,8 @@ 596 596 |**Dimensions (LxHxW)**|625 x 500 x 366mm 597 597 |**Input rating**|100-210V - 50/60Hz 598 598 |**Power**|100W 599 -|**Weight**|21.5 - 24 kg600 -|** Capacity**|16nodes529 +|**Weight**|21.5 - 24kg 530 +|**Slots no.**|16 601 601 |**Download Speed**|20MB/sec/slot 602 602 ))) 603 603 ... ... @@ -607,11 +607,11 @@ 607 607 608 608 [[image:20250729_124644.jpg]] 609 609 610 -|**Dimensions (LxHxW)**|625 x 500 x 366 mm611 -|**Input rating**|100-210V - 50/60 Hz612 -|**Power**|640 W613 -|**Weight**|26.3 kg614 -|** Capacity**|16nodes540 +|**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 615 615 ))) 616 616 617 617 (% class="box" %) ... ... @@ -621,9 +621,9 @@ 621 621 [[image:20250729_124957.jpg]] 622 622 623 623 624 -|**Dimensions (LxHxW)**|590 x 225 x 405 mm625 -|**Weight**|8.2 kg626 -|** Capacity**|6nodes554 +|**Dimensions (LxHxW)**|590 x 225 x 405mm 555 +|**Weight**|8.2kg 556 +|**Slots no.**|6 627 627 ))) 628 628 629 629 (% class="box" %) ... ... @@ -633,13 +633,9 @@ 633 633 [[image:20250729_124502.jpg]] 634 634 635 635 |**Dimensions (LxHxW)**|230 x 340 x 310mm 636 -|**Weight**|((( 637 -3.6kg (empty) 638 - 639 -18.0kg (full) 566 +|**Weight**|3.6kg 567 +|**Slots no.**|6 640 640 ))) 641 -|**Capacity**|6 nodes 642 -))) 643 643 644 644 (% class="box" %) 645 645 ((( ... ... @@ -649,7 +649,7 @@ 649 649 650 650 |**Dimensions (LxHxW)**|225 x 200 x 550mm 651 651 |**Weight**| 652 -|** Capacity**|8nodes578 +|**Slots no.**|6 653 653 ))) 654 654 ))) 655 655 )))
- 5S_node_programming.labels.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.KB - Size
-
... ... @@ -1,1 +1,0 @@ 1 -114.2 KB - Content
- 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
- Smartsolo harvesting #4 copy.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.JackD - Size
-
... ... @@ -1,1 +1,0 @@ 1 -33.8 KB - Content
- Smartsolo harvesting #4.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.JackD - Size
-
... ... @@ -1,1 +1,0 @@ 1 -33.8 KB - Content
- Smartsolo harvesting #6 copy.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.JackD - Size
-
... ... @@ -1,1 +1,0 @@ 1 -33.6 KB - Content
- Smartsolo harvesting #8 copy.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.JackD - Size
-
... ... @@ -1,1 +1,0 @@ 1 -38.3 KB - Content
- Smartsolo harvesting #8.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.JackD - Size
-
... ... @@ -1,1 +1,0 @@ 1 -60.0 KB - Content
- Smartsolo harvesting #9 copy.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.JackD - Size
-
... ... @@ -1,1 +1,0 @@ 1 -28.7 KB - Content