Skip to Content
Last modified by robert on 2026/06/29 16:42
From version 112.1
edited by robert
on 2026/06/17 16:54
Change comment: There is no comment for this version
To version 59.3
edited by robert
on 2025/07/16 15:55
Change comment: allow comment right for XWiki.XWikiAllGroup

Summary

Details

Page properties
Content
... ... @@ -4,64 +4,34 @@
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**
60 60  
61 61  **Assume ~~1 Tb of storage for both raw and exported data per 50 nodes @ 250 Hz & 30 days. One node recording at 250 Hz for 30 days tends to create about 3 Gb of miniseed data.**
62 -
63 -**We have had good experience with the 4Tb Samsung T7 Shield drives.**
64 64  )))
34 +)))
65 65  
66 66  == Magnets ==
67 67  
... ... @@ -69,65 +69,48 @@
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.
42 +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 -= 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 -(% class="box infomessage" %)
89 -(((
90 -**Field logs are a critical component of fieldwork and this is especially the case for large N nodal deploys. Take notes!**
91 -)))
46 +== **1. Logbook documentation** ==
92 92  
93 -== 1. Logbook documentation ==
94 -
95 95  (((
96 -**Essential Details** for field logs:
49 +**Essential Details**: Record the following in a logbook:
97 97  
98 98  * Station name
99 -* Latitude, longitude, elevation
52 +* Latitude and longitude
100 100  * Names of team members present
101 -* Date and both local & UTC time of installation/removal
102 -* Serial number (SN) of the TOP HALF of the sensor (if a BD3C-5, there is only one serial number)
103 -* 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)
54 +* Date and local time of installation
55 +* Serial number (SN) of the sensor
56 +* Detailed notes on the site conditions and setup
104 104  
105 -[[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!
106 -
107 -== 2. Node Placement ==
58 +== **2. Node Placement** ==
108 108  )))
109 109  
61 +**Protection**: Place nodes inside (landfill) biodegradable bags to minimize cleaning and cross-site soil contamination.
62 +
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.
65 +* **Take compass measurements away from the sensor as it will affect your measurement.**
66 +* Take multiple photographs from various angles to document the site setup thoroughly.
67 +* 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)
115 115  
116 -== 3. GPS Considerations ==
69 +== **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.
72 +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 -== 4. Visibility and Location Marking ==
74 +== **4. Visibility and Location Marking** ==
122 122  
123 123  **Flag Placement**: Position a flag, preferably in a bright color (avoid green or yellow), near the instrument to aid in its future location.
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 -* Also write the GPS down on paper (ie your [[LOG SHEET>>http://auspass.edu.au/field/NODES_blank_fieldlog.pdf]]).
80 +* Use a GPS device to mark the instrument's exact location.
81 +* Record this location in both your paper notes and the GPS device.
129 129  
130 -== (% style="color:inherit; font-family:inherit; font-size:max(18px, min(20px, 14.4444px + 0.462963vw))" %)5. Charge Time, Pre-Deployment & Post-Deployment(%%) ==
83 +== (% 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  
132 132  * **Charging Duration**: Both types of nodes take approximately 6-8 hours to fully charge from a flat state.
133 133  * **Pre-Deployment Charging**:
... ... @@ -137,22 +137,19 @@
137 137  ** 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.
138 138  
139 139  * **Post-Retrieval Charging**:
140 -** After retrieval, charge the instruments to about 50-60% (indicated by ORANGE LED) unless they are to be immediately re-deployed or transported.
141 -* **State of Charge (SoC) for Storage**:
142 -** Maintain a battery charge level of around 50-60% (i.e., ORANGE) for storage.
143 -** This charge level is recommended to prevent battery damage, and should be checked every six months.
144 -** Nodes should //__not be stored at full-charge (GREEN), or 0-charge (RED).__//
145 -** Storage at 0-charge damages lithium batteries**.**
146 -* **SoC for Transport:**
147 -** Charge levels for transport will be advised by the freighter. The required SoC will depend on volume and transport method (air, land, sea).
93 +** After retrieval, charge the instruments to about 50-60% (indicated as "orange" level) unless they are to be immediately re-deployed.
94 +* **Storage and Shipping Charge Level**:
95 +** Maintain a battery charge level of around 50-60% (e.g. "orange") for both storage and shipping purposes.
96 +** This charge level is recommended to prevent battery damage and is safe for transportation.
97 +** Nodes should not be stored fully charged, and it **they should especially not be stored with 0 charge.**
148 148  
149 149  (((
150 -== 6. Data Sharing and Metadata Creation ==
100 +== **6. Data Sharing and Metadata Creation** ==
151 151  )))
152 152  
153 153  **GPS Data**:
154 154  
155 -* Ensure you have __carefully documented__ precise lat/lon locations for each station.
105 +* Ensure you have documented precise lat/lon locations for each station and **DOCUMENTED THIS CAREFULLY**
156 156  
157 157  **Photo Sharing**:
158 158  
... ... @@ -160,9 +160,9 @@
160 160  
161 161  **Metadata File**:
162 162  
163 -* 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.
113 +* Create and organize metadata according to the [[ANU metadata standard txt file>>attach:example_metadata.txt]].
164 164  
165 -== 7. Additional Best Practices ==
115 +== **7. Additional Best Practices** ==
166 166  
167 167  * **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.
168 168  
... ... @@ -217,34 +217,32 @@
217 217  = **Charging Procedure for Seismic Nodes** =
218 218  
219 219  (((
220 -== 1. Preparation for Charging: ==
170 +== **1. Preparation for Charging**: ==
221 221  
222 222  * 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.
223 223  )))
224 224  
225 225  (((
226 -== 2. Disassembling the Node: ==
176 +== **2. Disassembling the Node**: ==
227 227  
228 -* For the IGU-16HR, remove the battery section (bottom half) from the sensor by unscrewing the spike section counter-clockwise.
178 +* For the IGU-16HR, remove the battery (bottom half) from the sensor. This is done by unscrewing the spikes counter-clockwise.
229 229  )))
230 230  
231 231  (((
232 -== 3. Setting Nodes in the Charging Box: ==
182 +== **3. Setting Nodes in the Charging Box**: ==
233 233  
234 -* Connect to a safe indoor power supply, and turn on (red rocker switch).
235 -* Charging will begin automatically when nodes are inserted in the charging rack.
236 -* Place IGU-16HR battery sections upside-down in the rack, oriented with the terminal connectors.
184 +* Place 1-16 IGU-16HR battery components upside-down into the charger, assuring they are oriented properly.
237 237  )))
238 238  
239 239  (((
240 -== 4. Monitoring the Charging Process: ==
188 +== **4. Monitoring the Charging Process**: ==
241 241  
242 -* Lights adjacent to the batteries will illuminate, indicating that charging is underway.
243 -* 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.
190 +* 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.
191 +* 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.
244 244  )))
245 245  
246 246  (((
247 -== 5. Updating Charge Status: ==
195 +== **5. Updating Charge Status**: ==
248 248  
249 249  * 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.
250 250  * This step is crucial for tracking the charging status of multiple units, especially when handling a large number of nodes.
... ... @@ -255,29 +255,14 @@
255 255  
256 256  
257 257  
258 -{{{
259 - }}}
206 +[[image:1706153354750-415.png||data-xwiki-image-style-alignment="center" height="317" width="562"]]
260 260  
261 261  ----
262 262  
263 263  = **Downloading and Converting Seismic Data to MiniSeed Format** =
264 264  
265 -(% class="wikigeneratedid" %)
266 -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]]
212 +== **Node Registration and Software Setup** ==
267 267  
268 -== Connection tips: ==
269 -
270 -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:
271 -
272 -* Place the node on the harvester gently, then firmly press it down onto the pins.
273 -* 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.
274 -* 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.
275 -* 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!
276 -
277 -
278 -
279 -== Node Registration and Software Setup ==
280 -
281 281  1. (((
282 282  **Registering Nodes in the System**:
283 283  
... ... @@ -294,35 +294,14 @@
294 294  * Ignore the settings for seismic recordings in the subsequent window. Resetting instruments (e.g., sampling rate, gain) requires reprogramming via script.
295 295  )))
296 296  
297 -== File structure ==
230 +== **Data Downloading Process** ==
298 298  
299 -There are essentially three main folders where relevant PROSPECT and PROJECT DATA is stored. Individual projects will be found as subfolders in these.
300 -
301 -=== SOLOLITE ===
302 -
303 -This folder stores SoloLite config files and parameters. Nothing too important stored here, you can always start over and re-create this.
304 -
305 -=== DCCDATA ===
306 -
307 -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.
308 -
309 -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)//
310 -
311 -Then in the SoloLite software, go to tools > Reanalyze Seismic Data
312 -
313 -=== SOLODATA ===
314 -
315 -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.
316 -
317 -
318 -== Data Downloading Process ==
319 -
320 320  1. (((
321 321  **Initiating Data Download**:
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]]
237 +* 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,55 +329,18 @@
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)
244 +* Tailor other parameters to personal preference and ensure "Sample Interval" matches the setting used during node reset.
245 +* 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!**
248 +* **Ensure to export data as "COUNTS", not "mV".**
249 +
250 +* **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).**
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 -== Smart Solo IGU-16HR Polarity Notice ==
254 +== **Handling Nodes During Download** ==
346 346  
347 -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.
348 -
349 -**The BD3C-5 data does not require any sort of polarity inversion.**
350 -
351 -== 18 Leap Second bug ==
352 -
353 -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.
354 -
355 -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.
356 -
357 -{{code language="none"}}
358 -<?xml version="1.0" encoding="UTF-8"?>
359 -<config>
360 - <leapsecond>
361 - <interval>
362 - <start_time>2017-01-01#00:00:00</start_time>
363 - <end_time>2999-12-31#23:59:59</end_time>
364 - <second>18</second>
365 - </interval>
366 - <interval>
367 - <start_time>1970-01-01#00:00:00</start_time>
368 - <end_time>2017-01-01#00:00:00</end_time>
369 - <second>17</second>
370 - </interval>
371 - </leapsecond>
372 - <GPS_distance_threshold_degree>
373 - 4e-5
374 - </GPS_distance_threshold_degree>
375 -</config>
376 -{{/code}}
377 -
378 -
379 -== Handling Nodes During Download ==
380 -
381 381  1. (((
382 382  **Monitoring Download Indicators**:
383 383  
... ... @@ -393,7 +393,6 @@
393 393  * **Use fast external hard drives to avoid limitations in data harvesting.**
394 394  
395 395  * **Recommended specifications: USB-C, USB 3.0, and 4+ Tb of space.**
396 -* **The USB type for the harvester is TYPE-A, the typical normal rectangular shape.**
397 397  )))
398 398  )))
399 399  1. (((
... ... @@ -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.
283 +
284 +
409 409  )))
410 410  
287 +[[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 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.
310 +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.
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 kg
316 +1 bag + 6 SP (IGU-16HR) nodes: 18 kg
493 493  
494 -1*IGU-16HR data harvester: 21.5 kg
318 +1 SP (IGU-16HR) data harvester: 21.5 kg
495 495  
496 -1*IGU-16HR charger: 26.3 kg
320 +1 SP (IGU-16HR) charger: 26.3 kg
497 497  
498 -1*BD3C-5 charger (with and without 16 cables): 21 kg / 14.5 kg
322 +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)
324 +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" %)
... ... @@ -523,7 +523,7 @@
523 523  
524 524  |(% style="width:189px" %)**Frequency Band**|(% style="width:221px" %)5 Seconds to 150Hz
525 525  |(% style="width:189px" %)**Sensitivity**|(% style="width:221px" %)200 V/m/s
526 -|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)Φ158 x160mm(H)
348 +|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)158 x160mm
527 527  |(% style="width:189px" %)**Weight**|(% style="width:221px" %)2.8 kg
528 528  |(% style="width:189px" %)**Data Storage**|(% style="width:221px" %)64 Gb
529 529  |(% style="width:189px" %)**Battery**|(% style="width:221px" %)(((
... ... @@ -535,7 +535,7 @@
535 535  
536 536  (% class="box" %)
537 537  (((
538 -= SmartSolo [[IGU-16HR>>url:https://smartsolo.com/cp-3.html]]3C =
360 += SmartSolo [[IGU-16HR>>url:https://smartsolo.com/cp-3.html]] =
539 539  
540 540  [[image:smartsolo node.jpg]]
541 541  
... ... @@ -542,8 +542,8 @@
542 542  [[image:smartsolo node 2.jpg]]
543 543  
544 544  |(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 1652Hz
545 -|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)76.7 V/m/s
546 -|(% style="width:187px" %)**Size (with spike)**|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm(H)
367 +|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)67.7 V/m/s
368 +|(% style="width:187px" %)**Size (with spike)**|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm
547 547  |(% style="width:187px" %)**Weight**|(% style="width:224px" %)2.4 kg
548 548  |(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)64 Gb
549 549  |(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((
... ... @@ -553,103 +553,6 @@
553 553  )))
554 554  )))
555 555  
556 -(% class="box" %)
557 -(((
558 558  
559 -
560 -= SmartSolo [[IGU-16>>url:https://smartsolo.com/cp-3.html]]1C =
561 -
562 -
563 -[[image:Screenshot 2025-08-01 161027.png]]
564 -
565 -|(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 413Hz
566 -|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)80 V/m/s
567 -|(% style="width:187px" %)**Size (without spike)**|(% style="width:224px" %)95mm(L) × 103mm(W) × 118mm(H)
568 -|(% style="width:187px" %)**Weight**|(% style="width:224px" %)1.1 kg
569 -|(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)8 Gb
570 -|(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((
571 -Lithium-ion battery contained in equipment (38.48 Wh)
572 -
573 -UN3481 PI967 S2
574 574  )))
575 575  )))
576 -
577 -(% class="box" %)
578 -(((
579 -= SmartSolo BD3C-16 Portable Battery Charger =
580 -
581 -[[image:20250729_125049.jpg]]
582 -
583 -|**Dimensions (LxHxW)**|558 x 357 x 300mm
584 -|**Input rating**|100-210V - 50/60Hz
585 -|**Power**|1000W
586 -|**Weight**|14.5 kg
587 -|**Weight with cables**|21 kg
588 -)))
589 -
590 -(% class="box" id="HSmartSoloBD3C-16PortableBatteryCharger" %)
591 -(((
592 -= SmartSolo IGU-16 Portable Data Harvester =
593 -
594 -[[image:20250729_124747.jpg]]
595 -
596 -|**Dimensions (LxHxW)**|625 x 500 x 366mm
597 -|**Input rating**|100-210V - 50/60Hz
598 -|**Power**|100W
599 -|**Weight**|21.5 - 24 kg
600 -|**Capacity**|16 nodes
601 -|**Download Speed**|20MB/sec/slot
602 -)))
603 -
604 -(% class="box" %)
605 -(((
606 -= SmartSolo IGU-16 Portable Battery Charger =
607 -
608 -[[image:20250729_124644.jpg]]
609 -
610 -|**Dimensions (LxHxW)**|625 x 500 x 366 mm
611 -|**Input rating**|100-210V - 50/60 Hz
612 -|**Power**|640 W
613 -|**Weight**|26.3 kg
614 -|**Capacity**|16 nodes
615 -)))
616 -
617 -(% class="box" %)
618 -(((
619 -= SmartSolo BD3C-5 Carry Case =
620 -
621 -[[image:20250729_124957.jpg]]
622 -
623 -
624 -|**Dimensions (LxHxW)**|590 x 225 x 405 mm
625 -|**Weight**|8.2 kg
626 -|**Capacity**|6 nodes
627 -)))
628 -
629 -(% class="box" %)
630 -(((
631 -= SmartSolo IGU-16 3C Carry Bag =
632 -
633 -[[image:20250729_124502.jpg]]
634 -
635 -|**Dimensions (LxHxW)**|230 x 340 x 310mm
636 -|**Weight**|(((
637 -3.6kg (empty)
638 -
639 -18.0kg (full)
640 -)))
641 -|**Capacity**|6 nodes
642 -)))
643 -
644 -(% class="box" %)
645 -(((
646 -= SmartSolo IGU-16 1C Carry Bag =
647 -
648 -[[image:20250729_124558.jpg]]
649 -
650 -|**Dimensions (LxHxW)**|225 x 200 x 550mm
651 -|**Weight**|
652 -|**Capacity**|8 nodes
653 -)))
654 -)))
655 -)))
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.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
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
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
XWiki.XWikiRights[0]
Levels
... ... @@ -1,1 +1,1 @@
1 -comment
1 +view,comment
XWiki.XWikiRights[1]
Allow/Deny
... ... @@ -1,1 +1,0 @@
1 -Allow
Levels
... ... @@ -1,1 +1,0 @@
1 -comment
Users
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest