Skip to Content
Last modified by robert on 2026/02/27 19:58
From version 106.1
edited by robert
on 2026/02/17 16:18
Change comment: There is no comment for this version
To version 60.2
edited by robert
on 2025/07/16 16:08
Change comment: Deleted object

Summary

Details

Page properties
Content
... ... @@ -4,56 +4,27 @@
4 4  (((
5 5  = **Node Types** =
6 6  
7 -ANSIR supply two types of three-channel nodes, and one type of one-channel node:
7 +ANSIR carry two types of three-channel nodes
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. Not 'HR')**
9 +* **SmartSolo IGU 16HR 3C (5 Hz Short Period)**
10 +* **SmartSolo BD3C-5 (5 Second Broad-Band)**
12 12  
13 -Visit the [[SmartSolo page>>https://smartsolo.com/igu.html]] for more detail.
12 +Both have a battery capacity of around 30 days. The programming, operation, and downloading procedures for both types of SmartSolo nodes are also similar.
14 14  
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 -(% class="box infomessage" %)
18 -(((
19 -**Freight update, 2026: **Freight options for lithium-ion batteries are changing in 2025/2026 to comply with updated transport safety regulations. This will impact supply of IGU 16 (<100Wh) and BD3C (168Wh) nodes. Advice will be sought from freighters on a case-by-case basis while they implement new guidelines.
20 -)))
21 -
22 22  ----
23 23  
24 24  = **Programming Defaults** =
25 25  
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.
19 +We recommend that the SP 16HR-3C be set to a gain of 24db 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). These are what we use for our internal experiments.
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"]]
21 +**Note that this gain must be removed when exporting to miniseed, **otherwise amplitudes will be a factor of either 15.84893192 (24db) or 2 (6db) too high. We also recommend disabling bluetooth to increase battery life, and to enable "FIFO" mode just in case old data is still present on the units and you run out of space (although it is unlikely you will go over 64 Gb for one deploy). If using the "timed turn-on" option, please be aware that **the units will not begin recording until they have acquired a GPS lock**, which may nor occur if they are buried too deeply or have very poor sky view.
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!"]]
31 31  
32 -
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 -
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.
36 -
37 -Be sure to set the channel types to Seismic and the gain appropriately. For active source (i.e. explosions) you can leave the gain at 0, but for passive experiments some gain is purported to be helpful (although we have found this to be somewhat negligible). We can confirm that 6db for the broadband nodes and 24db for the short period works well.
38 -
39 -If you want recording to begin immediately, ensure that begin date is in the past by at least a few days. If you prefer to have a timed turn-on, then set the times as needed. **Be warned that recording will not begin until a GPS lock is achieved, so if you set it to a future turn-on but bury it too deeply, it may not record!**
40 -
41 -In newer versions of the software there is a "power consumption" setting.. we are no sure what this does exactly, but the manual says it gives life a "boost" at the expense of about 3 db of resolution. Until this can be quantified a bit better it is not recommended.
42 -
43 -Storage type can be DLD (proprietary) or Miniseed. We assume the software works best with their proprietary format so prefer not to risk any issues. You can export to miniseed later.
44 -
45 -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.
46 -
47 -Bluetooth (BD3C-5 only) should be turned OFF to conserve power.
48 -
49 -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).
50 -
51 -{{info}}
52 -**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!
53 -{{/info}}
54 -
55 55  = **Fieldwork Preparation** =
56 56  
26 +(% class="box infomessage" %)
27 +(((
57 57  (% class="box warningmessage" %)
58 58  (((
59 59  **INVEST IN FAST EXTERNAL HARD DRIVES – DO NOT LET THIS BE THE LIMITATION OF DATA HARVESTING**
... ... @@ -62,6 +62,7 @@
62 62  
63 63  **We have had good experience with the 4Tb Samsung T7 Shield drives.**
64 64  )))
36 +)))
65 65  
66 66  == Magnets ==
67 67  
... ... @@ -69,46 +69,39 @@
69 69  
70 70  == Animal-Proofing ==
71 71  
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.
44 +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.
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 -(% class="box infomessage" %)
79 -(((
80 -**Field logs are a critical component of fieldwork and this is especially the case for large N nodal deploys. Take notes!**
81 -)))
48 +== **1. Logbook documentation** ==
82 82  
83 -== 1. Logbook documentation ==
84 -
85 85  (((
86 -**Essential Details** for field logs:
51 +**Essential Details**: Record the following in a logbook:
87 87  
88 88  * Station name
89 -* Latitude, longitude, elevation
54 +* Latitude and longitude
90 90  * Names of team members present
91 -* Date and both local & UTC time of installation/removal
92 -* Serial number (SN) of the TOP HALF of the sensor (if a BD3C-5, there is only one serial number)
93 -* Detailed notes on the site conditions and setup, anything else that will be helpful to find it again ("by the fence", "south of rock", etc)
56 +* Date and local time of installation
57 +* Serial number (SN) of the sensor
58 +* Detailed notes on the site conditions and setup
94 94  
95 -[[HERE>>http://auspass.edu.au/field/NODES_blank_fieldlog.pdf]] is an example logsheet that works well for nodes, feel free to print and use!
96 -
97 -== 2. Node Placement ==
60 +== **2. Node Placement** ==
98 98  )))
99 99  
63 +**Protection**: Place nodes inside (landfill) biodegradable bags to minimize cleaning and cross-site soil contamination.
64 +
100 100  **Site Analysis**:
101 101  
102 102  * **Take compass measurements away from the sensor as it will affect your measurement.**
103 -* Take photographs from various angles to document the site setup thoroughly.
104 -* Include a detailed site description in your notes
68 +* Take multiple photographs from various angles to document the site setup thoroughly.
69 +* Include a detailed site description in your notes, specifying distances and orientations from nearby landmarks (e.g. Richards garden, Te Mini steam field eastern side)
105 105  
106 -== 3. GPS Considerations ==
71 +== **3. GPS Considerations** ==
107 107  
108 108  (% class="wikigeneratedid" %)
109 109  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.
110 110  
111 -== 4. Visibility and Location Marking ==
76 +== **4. Visibility and Location Marking** ==
112 112  
113 113  **Flag Placement**: Position a flag, preferably in a bright color (avoid green or yellow), near the instrument to aid in its future location.
114 114  
... ... @@ -117,7 +117,7 @@
117 117  * Use a GPS device to mark the instrument's exact location.
118 118  * Record this location in both your paper notes and the GPS device.
119 119  
120 -== (% style="color:inherit; font-family:inherit; font-size:max(18px, min(20px, 14.4444px + 0.462963vw))" %)5. Charge Time, Pre-Deployment & Post-Deployment(%%) ==
85 +== (% style="color:inherit; font-family:inherit; font-size:max(18px, min(20px, 14.4444px + 0.462963vw))" %)**5. Charge Time, Pre-Deployment & Post-Deployment**(%%) ==
121 121  
122 122  * **Charging Duration**: Both types of nodes take approximately 6-8 hours to fully charge from a flat state.
123 123  * **Pre-Deployment Charging**:
... ... @@ -127,22 +127,19 @@
127 127  ** 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.
128 128  
129 129  * **Post-Retrieval Charging**:
130 -** After retrieval, charge the instruments to about 50-60% (indicated by ORANGE LED) unless they are to be immediately re-deployed or transported.
131 -* **State of Charge (SoC) for Storage**:
132 -** Maintain a battery charge level of around 50-60% (i.e., ORANGE) for storage.
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).__//
135 -** Storage at 0-charge damages lithium batteries**.**
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).
95 +** After retrieval, charge the instruments to about 50-60% (indicated as "orange" level) unless they are to be immediately re-deployed.
96 +* **Storage and Shipping Charge Level**:
97 +** Maintain a battery charge level of around 50-60% (e.g. "orange") for both storage and shipping purposes.
98 +** This charge level is recommended to prevent battery damage and is safe for transportation.
99 +** Nodes should not be stored fully charged, and it **they should especially not be stored with 0 charge.**
138 138  
139 139  (((
140 -== 6. Data Sharing and Metadata Creation ==
102 +== **6. Data Sharing and Metadata Creation** ==
141 141  )))
142 142  
143 143  **GPS Data**:
144 144  
145 -* Ensure you have __carefully documented__ precise lat/lon locations for each station.
107 +* Ensure you have documented precise lat/lon locations for each station and **DOCUMENTED THIS CAREFULLY**
146 146  
147 147  **Photo Sharing**:
148 148  
... ... @@ -150,9 +150,9 @@
150 150  
151 151  **Metadata File**:
152 152  
153 -* Create and organize metadata according to the [[ANU metadata standard txt file>>attach:example_metadata.txt]]. This is going to be particularly important if you are reusing nodes at different sites... not documenting the serial numbers (of the **top half** of the node) and the times they were deployed can lead to station mix-ups.
115 +* Create and organize metadata according to the [[ANU metadata standard txt file>>attach:example_metadata.txt]].
154 154  
155 -== 7. Additional Best Practices ==
117 +== **7. Additional Best Practices** ==
156 156  
157 157  * **Training and Familiarisation**: Make sure all team members are adequately trained in using the GPS devices, compass use, and other equipment to ensure consistent and accurate data collection.
158 158  
... ... @@ -207,34 +207,32 @@
207 207  = **Charging Procedure for Seismic Nodes** =
208 208  
209 209  (((
210 -== 1. Preparation for Charging: ==
172 +== **1. Preparation for Charging**: ==
211 211  
212 212  * Before charging, ensure each node is clean. This involves removing any dirt or debris to maintain the integrity of the equipment and ensure effective charging.
213 213  )))
214 214  
215 215  (((
216 -== 2. Disassembling the Node: ==
178 +== **2. Disassembling the Node**: ==
217 217  
218 -* For the IGU-16HR, remove the battery section (bottom half) from the sensor by unscrewing the spike section counter-clockwise.
180 +* For the IGU-16HR, remove the battery (bottom half) from the sensor. This is done by unscrewing the spikes counter-clockwise.
219 219  )))
220 220  
221 221  (((
222 -== 3. Setting Nodes in the Charging Box: ==
184 +== **3. Setting Nodes in the Charging Box**: ==
223 223  
224 -* Connect to a safe indoor power supply, and turn on (red rocker switch).
225 -* Charging will begin automatically when nodes are inserted in the charging rack.
226 -* Place IGU-16HR battery sections upside-down in the rack, oriented with the terminal connectors.
186 +* Place 1-16 IGU-16HR battery components upside-down into the charger, assuring they are oriented properly.
227 227  )))
228 228  
229 229  (((
230 -== 4. Monitoring the Charging Process: ==
190 +== **4. Monitoring the Charging Process**: ==
231 231  
232 -* Lights adjacent to the batteries will illuminate, indicating that charging is underway.
233 -* 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.
192 +* 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.
193 +* 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.
234 234  )))
235 235  
236 236  (((
237 -== 5. Updating Charge Status: ==
197 +== **5. Updating Charge Status**: ==
238 238  
239 239  * During the charging period, take this opportunity to update the status of each unit. Check the //"C"// box on your temporary labels to indicate that the unit has been successfully charged.
240 240  * This step is crucial for tracking the charging status of multiple units, especially when handling a large number of nodes.
... ... @@ -245,29 +245,14 @@
245 245  
246 246  
247 247  
248 -{{{
249 - }}}
208 +[[image:1706153354750-415.png||data-xwiki-image-style-alignment="center" height="317" width="562"]]
250 250  
251 251  ----
252 252  
253 253  = **Downloading and Converting Seismic Data to MiniSeed Format** =
254 254  
255 -(% class="wikigeneratedid" %)
256 -SmartSolo provides the following powerpoint for SmartSolo node programming and operation. Note that ANSIR only uses a portion of their process for our own uses: [[https:~~/~~/nappe.wustl.edu/smartsolo/files/smartsolo_online_training.pdf>>url:https://nappe.wustl.edu/smartsolo/files/smartsolo_online_training.pdf]]
214 +== **Node Registration and Software Setup** ==
257 257  
258 -== Connection tips: ==
259 -
260 -Connecting SmartSolo nodes to their harvesters and having SoloLite recognise them can be a bit tricky, here are some tricks to help register and program them easier:
261 -
262 -* Place the node on the harvester gently, then firmly press it down onto the pins.
263 -* Place all nodes onto the harvester before trying any troubleshooting, as they may not show up while the SoloLite software is running. Once all are connected, try restarting the software for them to be recognised.
264 -* If a node is refusing to connect, try it with another slot. It is easiest if you place all 16 nodes on the harvester, and swap any nodes that refuse to connect with each other.
265 -* Nodes will likely not show up in the order that they should, though this is not an issue. E.g, a node in slot 6 on the harvester may show up in port 13 in the SoloLite software. Annoying, but it doesn't matter so long as you keep track of what's been harvested!
266 -
267 -
268 -
269 -== Node Registration and Software Setup ==
270 -
271 271  1. (((
272 272  **Registering Nodes in the System**:
273 273  
... ... @@ -284,29 +284,8 @@
284 284  * Ignore the settings for seismic recordings in the subsequent window. Resetting instruments (e.g., sampling rate, gain) requires reprogramming via script.
285 285  )))
286 286  
287 -== File structure ==
232 +== **Data Downloading Process** ==
288 288  
289 -There are essentially three main folders where relevant PROSPECT and PROJECT DATA is stored. Individual projects will be found as subfolders in these.
290 -
291 -=== SOLOLITE ===
292 -
293 -This folder stores SoloLite config files and parameters. Nothing too important stored here, you can always start over and re-create this.
294 -
295 -=== DCCDATA ===
296 -
297 -This folder stores the RAW data you have harvested from the nodes. The data will still be on the nodes (unless you erased it) in case of emergency, but regardless, this is the folder you want to back up and save somewhere.
298 -
299 -If you had a weird time harvesting a node, you can always manually copy it as if it were a USB stick and place it into this folder manually. The structure is: //C:/DCCDATA/prospect_name/project_name/SERIALNUMBER/label(usually a timestamp but can be anything)//
300 -
301 -Then in the SoloLite software, go to tools > Reanalyze Seismic Data
302 -
303 -=== SOLODATA ===
304 -
305 -This folder stores **exported** (e.g. miniseed) data. It is structured similarly. If your DCCDATA is intact, this can always be re-created if need be.
306 -
307 -
308 -== Data Downloading Process ==
309 -
310 310  1. (((
311 311  **Initiating Data Download**:
312 312  
... ... @@ -323,48 +323,14 @@
323 323  * Click “prepare” followed by “run” to start reformatting. Monitor this process in the small panel at the bottom left.
324 324  * (% class="box warningmessage" %)
325 325  (((
326 -* **Ensure to export data as "COUNTS" (int32), not "mV" (float). This is critical!**
250 +* **Ensure to export data as "COUNTS", not "mV".**
327 327  
328 -* **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.**
252 +* **Set "Remove Gain" to the same decibel gain as during programming** **(by default ANU sets this to 24db for short period nodes (a factor of 15.848932), and 6db for broadband nodes).**
329 329  )))
330 330  )))
331 331  
332 -== Smart Solo IGU-16HR Polarity Notice ==
256 +== **Handling Nodes During Download** ==
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.
335 -
336 -**The BD3C-5 data does not require any sort of polarity inversion.**
337 -
338 -== 18 Leap Second bug ==
339 -
340 -Not so much a //bug// as much as "a thing that can happen if your SoloLite installation is corrupted". If you notice your data has large constant time offsets, you should suspect that the number of leap seconds has not been accounted properly. There is a file "smartsoloconfig.xml" that needs to be present in "C:\SmartSoloApps SoloLite" (e.g. the main program directory) that dictates the leap second offset for the last two data ranges. Since 2017-01-01, this is 18 seconds. At some point in the next few years it will be 19 seconds.
341 -
342 -If this file is missing, just create a new one structured like so, name it "smartsoloconfig.xml" and put it in your main program directory. Then, Reanalyze your data (tools > Reanalyze seismic data) and your data should have the correct time. You can also do this manually, if you want. The offset is 18 seconds precisely.
343 -
344 -{{code language="none"}}
345 -<?xml version="1.0" encoding="UTF-8"?>
346 -<config>
347 - <leapsecond>
348 - <interval>
349 - <start_time>2017-01-01#00:00:00</start_time>
350 - <end_time>2999-12-31#23:59:59</end_time>
351 - <second>18</second>
352 - </interval>
353 - <interval>
354 - <start_time>1970-01-01#00:00:00</start_time>
355 - <end_time>2017-01-01#00:00:00</end_time>
356 - <second>17</second>
357 - </interval>
358 - </leapsecond>
359 - <GPS_distance_threshold_degree>
360 - 4e-5
361 - </GPS_distance_threshold_degree>
362 -</config>
363 -{{/code}}
364 -
365 -
366 -== Handling Nodes During Download ==
367 -
368 368  1. (((
369 369  **Monitoring Download Indicators**:
370 370  
... ... @@ -380,7 +380,6 @@
380 380  * **Use fast external hard drives to avoid limitations in data harvesting.**
381 381  
382 382  * **Recommended specifications: USB-C, USB 3.0, and 4+ Tb of space.**
383 -* **The USB type for the harvester is TYPE-A, the typical normal rectangular shape.**
384 384  )))
385 385  )))
386 386  1. (((
... ... @@ -418,76 +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, but the 3C version seems to fit a lot better than the version published at IRIS-NRL which has no PAZ information. We are looking into this.
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 -[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:BD3C_Z_huddle.png]]
448 -
449 -[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:BD3C_N_huddle.png]]
450 -
451 -(% class="wikigeneratedid" %)
452 -Below the corner frequency 0.2 Hz (i.e. 5 seconds) the response still does a good job, but may need to be dialed in a bit. We are looking into this.
453 -
454 -(% class="wikigeneratedid" %)
455 -
456 -
457 -[[BD3C 0.1 to 5 Hz bandpass>>image:BD3C_Z_huddle.0.1.png]]
458 -
459 -[[BD3C 0.1 to 5 Hz bandpass>>image:BD3C_N_huddle.0.1.png]]
460 -
461 -== IGU-16 Horizontal noise & how to avoid ==
462 -
463 -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.
464 -
465 -[[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]]
466 -
467 -(% class="wikigeneratedid" %)
468 -The BD3C-5 nodes do not have this issue:
469 -
470 -[[BD3C-5 test, as above. There is no additional noise on the horizontal channels.>>image:BD3C_psd.png]]
471 -
472 472  = **Cleaning** =
473 473  
474 -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.
312 +When still connected, the nodes are water resistant (don't submerge them!) and can handle a good spray / wipedown. A strong, non-wire brush is helpful to reach areas between the metal spikes on the bottom.
475 475  
476 476  = **Weights (for shipping)** =
477 477  
478 478  The weights of bags of nodes, as well as data harvesters and node chargers, are listed below:
479 479  
480 -1 bag + 6*IGU-16HR nodes: 18 kg
318 +1 bag + 6 SP (IGU-16HR) nodes: 18 kg
481 481  
482 -1*IGU-16HR data harvester: 21.5 kg
320 +1 SP (IGU-16HR) data harvester: 21.5 kg
483 483  
484 -1*IGU-16HR charger: 26.3 kg
322 +1 SP (IGU-16HR) charger: 26.3 kg
485 485  
486 -1*BD3C-5 charger (with and without 16 cables): 21 kg / 14.5 kg
324 +1 BB (BD3C-5) charger/data harvester (with and without 16 cables): 21 kg / 14.5 kg
487 487  
488 -1 case + 5*BD3C-5 nodes: 22 kg (aggregate battery weight <5kg, 168Wh)
489 -
490 -1 case + 6*BD3C-5 nodes: 25 kg (aggregate battery weight >5kg, 168Wh)
326 +1 case + 5 BB (BD3C-5) nodes and 6 BB nodes: 22 kg / 25 kg
491 491  )))
492 492  
493 493  (% class="col-xs-12 col-sm-4" %)
... ... @@ -511,7 +511,7 @@
511 511  
512 512  |(% style="width:189px" %)**Frequency Band**|(% style="width:221px" %)5 Seconds to 150Hz
513 513  |(% style="width:189px" %)**Sensitivity**|(% style="width:221px" %)200 V/m/s
514 -|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)Φ158 x160mm(H)
350 +|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)158 x160mm
515 515  |(% style="width:189px" %)**Weight**|(% style="width:221px" %)2.8 kg
516 516  |(% style="width:189px" %)**Data Storage**|(% style="width:221px" %)64 Gb
517 517  |(% style="width:189px" %)**Battery**|(% style="width:221px" %)(((
... ... @@ -523,7 +523,7 @@
523 523  
524 524  (% class="box" %)
525 525  (((
526 -= SmartSolo [[IGU-16HR>>url:https://smartsolo.com/cp-3.html]]3C =
362 += SmartSolo [[IGU-16HR>>url:https://smartsolo.com/cp-3.html]] =
527 527  
528 528  [[image:smartsolo node.jpg]]
529 529  
... ... @@ -530,8 +530,8 @@
530 530  [[image:smartsolo node 2.jpg]]
531 531  
532 532  |(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 1652Hz
533 -|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)76.7 V/m/s
534 -|(% style="width:187px" %)**Size (with spike)**|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm(H)
369 +|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)67.7 V/m/s
370 +|(% style="width:187px" %)**Size (with spike)**|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm
535 535  |(% style="width:187px" %)**Weight**|(% style="width:224px" %)2.4 kg
536 536  |(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)64 Gb
537 537  |(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((
... ... @@ -541,103 +541,6 @@
541 541  )))
542 542  )))
543 543  
544 -(% class="box" %)
545 -(((
546 546  
547 -
548 -= SmartSolo [[IGU-16>>url:https://smartsolo.com/cp-3.html]]1C =
549 -
550 -
551 -[[image:Screenshot 2025-08-01 161027.png]]
552 -
553 -|(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 413Hz
554 -|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)80 V/m/s
555 -|(% style="width:187px" %)**Size (without spike)**|(% style="width:224px" %)95mm(L) × 103mm(W) × 118mm(H)
556 -|(% style="width:187px" %)**Weight**|(% style="width:224px" %)1.1 kg
557 -|(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)8 Gb
558 -|(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((
559 -Lithium-ion battery contained in equipment (38.48 Wh)
560 -
561 -UN3481 PI967 S2
562 562  )))
563 563  )))
564 -
565 -(% class="box" %)
566 -(((
567 -= SmartSolo BD3C-16 Portable Battery Charger =
568 -
569 -[[image:20250729_125049.jpg]]
570 -
571 -|**Dimensions (LxHxW)**|558 x 357 x 300mm
572 -|**Input rating**|100-210V - 50/60Hz
573 -|**Power**|1000W
574 -|**Weight**|14.5 kg
575 -|**Weight with cables**|21 kg
576 -)))
577 -
578 -(% class="box" id="HSmartSoloBD3C-16PortableBatteryCharger" %)
579 -(((
580 -= SmartSolo IGU-16 Portable Data Harvester =
581 -
582 -[[image:20250729_124747.jpg]]
583 -
584 -|**Dimensions (LxHxW)**|625 x 500 x 366mm
585 -|**Input rating**|100-210V - 50/60Hz
586 -|**Power**|100W
587 -|**Weight**|21.5 - 24 kg
588 -|**Capacity**|16 nodes
589 -|**Download Speed**|20MB/sec/slot
590 -)))
591 -
592 -(% class="box" %)
593 -(((
594 -= SmartSolo IGU-16 Portable Battery Charger =
595 -
596 -[[image:20250729_124644.jpg]]
597 -
598 -|**Dimensions (LxHxW)**|625 x 500 x 366 mm
599 -|**Input rating**|100-210V - 50/60 Hz
600 -|**Power**|640 W
601 -|**Weight**|26.3 kg
602 -|**Capacity**|16 nodes
603 -)))
604 -
605 -(% class="box" %)
606 -(((
607 -= SmartSolo BD3C-5 Carry Case =
608 -
609 -[[image:20250729_124957.jpg]]
610 -
611 -
612 -|**Dimensions (LxHxW)**|590 x 225 x 405 mm
613 -|**Weight**|8.2 kg
614 -|**Capacity**|6 nodes
615 -)))
616 -
617 -(% class="box" %)
618 -(((
619 -= SmartSolo IGU-16 3C Carry Bag =
620 -
621 -[[image:20250729_124502.jpg]]
622 -
623 -|**Dimensions (LxHxW)**|230 x 340 x 310mm
624 -|**Weight**|(((
625 -3.6kg (empty)
626 -
627 -18.0kg (full)
628 -)))
629 -|**Capacity**|6 nodes
630 -)))
631 -
632 -(% class="box" %)
633 -(((
634 -= SmartSolo IGU-16 1C Carry Bag =
635 -
636 -[[image:20250729_124558.jpg]]
637 -
638 -|**Dimensions (LxHxW)**|225 x 200 x 550mm
639 -|**Weight**|
640 -|**Capacity**|8 nodes
641 -)))
642 -)))
643 -)))
20250729_124502.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -318.3 KB
Content
20250729_124558.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -376.8 KB
Content
20250729_124644.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -528.0 KB
Content
20250729_124747.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -488.5 KB
Content
20250729_124957.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -532.5 KB
Content
20250729_125049.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -457.6 KB
Content
5Hz_node_programming.labels.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.KB
Size
... ... @@ -1,1 +1,0 @@
1 -109.8 KB
Content
5S_node_programming.labels.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.KB
Size
... ... @@ -1,1 +1,0 @@
1 -114.2 KB
Content
BB_programming.labels.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -111.5 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.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.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_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
SP_programming.labels.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -106.7 KB
Content
Screenshot 2025-08-01 161027.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -82.8 KB
Content