Skip to Content
Last modified by robert on 2026/01/19 17:43
From version 94.5
edited by KB
on 2026/01/19 13:22
Change comment: There is no comment for this version
To version 42.1
edited by robert
on 2024/03/06 13:19
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -SmartSolo Node Seismometers
1 +SmartSolo Nodes
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.KB
1 +XWiki.robert
Content
... ... @@ -2,108 +2,69 @@
2 2  (((
3 3  (% class="col-xs-12 col-sm-8" %)
4 4  (((
5 -= **Node Types** =
5 += **SmartSolo Node Types and Procedures** =
6 6  
7 -ANSIR supply two types of three-channel nodes, and one type of one-channel node:
7 +**SmartSolo Node Variants:**
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)**
9 +* **SmartSolo IGU 16HR 3C (5 Hz) Short Period Node**
10 +* **SmartSolo BD3C-5 (5-second) Broad-Band Node**
12 12  
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.
12 +The installation, demobilization, and data downloading procedures for both types of SmartSolo nodes – the IGU 16HR 3C Short Period Node and the BD3C-5 Broad-Band Node – are largely similar.
14 14  
15 -(% class="box infomessage" %)
16 -(((
17 -**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.
18 -)))
14 +This uniformity in process ensures ease of operation across different node types, allowing for a streamlined approach in fieldwork and data management.
19 19  
20 20  ----
21 21  
22 -= **Programming Defaults** =
18 += **Node Setup** =
23 23  
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.
20 +Short term (~~30 day) battery powered nodes. The default gain should be 24 db for the 16HR-3C and 6 db for the BD3C-5
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"]]
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"]]
23 +~*~**this needs to be reformatted
29 29  
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.
25 +== **Pre-Fieldwork Preparation** ==
31 31  
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.
33 -
34 -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.
35 -
36 -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!**
37 -
38 -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.
39 -
40 -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.
41 -
42 -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.
43 -
44 -Bluetooth (BD3C-5 only) should be turned OFF to conserve power.
45 -
46 -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).
47 -
48 -{{info}}
49 -**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!
50 -{{/info}}
51 -
52 -= **Fieldwork Preparation** =
53 -
27 +(% class="box infomessage" %)
28 +(((
54 54  (% class="box warningmessage" %)
55 55  (((
56 56  **INVEST IN FAST EXTERNAL HARD DRIVES – DO NOT LET THIS BE THE LIMITATION OF DATA HARVESTING**
57 57  
58 -**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.**
59 -
60 -**We have had good experience with the 4Tb Samsung T7 Shield drives.**
33 +**Plan on 1 Tb to store ALL data for 50 nodes @ 250 Hz and a single ~~30 day occupation**
61 61  )))
35 +)))
62 62  
63 -== Magnets ==
64 -
65 -If you are short on magnets, you may find it easier and a lot cheaper to buy magnets in Australia. AMF Magnetics is a good retailer, and [[this item>>https://magnet.com.au/collections/shop?q=23012B]] seems to work well. It is also advantageous to use smaller magnets and store/carry them individually in your back pocket (as well as stick them to various places in your field vehicle, etc).
66 -
67 -== Animal-Proofing ==
68 -
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 -
71 71  = **Installation** =
72 72  
73 -(% class="box infomessage" %)
74 -(((
75 -**Field logs are a critical component of fieldwork and this is especially the case for large N nodal deploys. Take notes!**
76 -)))
39 +=== **1- Logbook documentation** ===
77 77  
78 -== 1. Logbook documentation ==
79 -
80 80  (((
81 -**Essential Details** for field logs:
42 +**Essential Details**: Record the following in a logbook:
82 82  
83 83  * Station name
84 -* Latitude, longitude, elevation
45 +* Latitude and longitude
85 85  * Names of team members present
86 -* Date and both local & UTC time of installation/removal
87 -* Serial number (SN) of the TOP HALF of the sensor (if a BD3C-5, there is only one serial number)
88 -* 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)
47 +* Date and local time of installation
48 +* Serial number (SN) of the sensor
49 +* Detailed notes on the site conditions and setup
89 89  
90 -[[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!
91 -
92 -== 2. Node Placement ==
51 +=== **2- Node Placement** ===
93 93  )))
94 94  
54 +**Protection**: Place nodes inside thick, landfill biodegradable plastic bags for environmental protection.
55 +
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
58 +* Conduct compass measurements away from the node and metallic structures, adjusting for inclination angle.
59 +* Take multiple photographs from various angles to document the site setup thoroughly.
60 +* 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)
100 100  
101 -== 3. GPS Considerations ==
62 +=== **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.
65 +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. The BD3C will not start recording without first attaining a GPS lock.
105 105  
106 -== 4. Visibility and Location Marking ==
67 +=== **4- Visibility and Location Marking** ===
107 107  
108 108  **Flag Placement**: Position a flag, preferably in a bright color (avoid green or yellow), near the instrument to aid in its future location.
109 109  
... ... @@ -112,53 +112,63 @@
112 112  * Use a GPS device to mark the instrument's exact location.
113 113  * Record this location in both your paper notes and the GPS device.
114 114  
115 -== (% style="color:inherit; font-family:inherit; font-size:max(18px, min(20px, 14.4444px + 0.462963vw))" %)5. Charge Time, Pre-Deployment & Post-Deployment(%%) ==
76 +=== (% 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  
117 117  * **Charging Duration**: Both types of nodes take approximately 6-8 hours to fully charge from a flat state.
118 118  * **Pre-Deployment Charging**:
119 -** Although the nodes hold their charge well, it's beneficial to give them a "top up" charge before deployment.
80 +** Although the nodes hold their charge well, it's beneficial to give them a "top up" charge right before deployment.
120 120  
121 121  * **Operational Duration**:
122 -** 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.
83 +** When recording at 250 Hz, with GPS on and Bluetooth disabled, the instruments are expected to last about 30 days per charge cycle.
123 123  
124 124  * **Post-Retrieval Charging**:
125 -** After retrieval, charge the instruments to about 50-60% (indicated by ORANGE LED) unless they are to be immediately re-deployed or transported.
126 -* **State of Charge (SoC) for Storage**:
127 -** Maintain a battery charge level of around 50-60% (i.e., ORANGE) for storage.
128 -** This charge level is recommended to prevent battery damage, and should be checked every six months.
129 -** Nodes should //__not be stored at full-charge (GREEN), or 0-charge (RED).__//
130 -** Storage at 0-charge damages lithium batteries**.**
131 -* **SoC for Transport:**
132 -** Charge levels for transport will be advised by the freighter. The required SoC will depend on volume and transport method (air, land, sea).
86 +** Do not store the instruments with completely drained batteries.
87 +** After retrieval, charge the instruments to about 50-60% (indicated as "orange" level) for optimal battery health.
133 133  
134 -(((
135 -== 6. Data Sharing and Metadata Creation ==
89 +* **Storage and Shipping Charge Level**:
90 +** Maintain a battery charge level of around 50-60% for both storage and shipping purposes.
91 +** This charge level is recommended to prevent battery damage and is safe for transportation.
92 +
93 +=== ===
94 +
95 +* (((
96 +=== **6- Data Sharing and Metadata Creation** ===
136 136  )))
137 137  
138 138  **GPS Data**:
139 139  
140 -* Ensure you have __carefully documented__ precise lat/lon locations for each station.
101 +* Download the GPS file to a laptop.
102 +* Share this file on a drive accessible to all team members for uniform understanding of node locations.
141 141  
142 142  **Photo Sharing**:
143 143  
144 -* It is strongly encouraged to take pictures of each site and upload these to a shared platform (OneDrive, Dropbox, etc.).
106 +* Upload site photos to a shared platform (OneDrive, Dropbox, etc.).
107 +* Integrating photos into Google Maps or Google Earth can be particularly beneficial for easy location referencing.
145 145  
146 146  **Metadata File**:
147 147  
148 -* 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.
111 +* Create a metadata XML file for each node, which is essential for data organisation and future reference.
149 149  
150 -== 7. Additional Best Practices ==
113 +=== **7- Additional Best Practices** ===
151 151  
152 -* **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.
115 +* **Environmental Responsibility**: Ensure that the node placement and the materials used are environmentally responsible and adhere to local regulations.
116 +* **Training and Familiarisation**: Make sure all team members are adequately trained in using the GPS devices, compass, and other equipment to ensure consistent and accurate data collection.
153 153  
118 +* (((
119 +==== **Keeping the Instruments Clean** ====
120 +)))
121 +* (((
122 +Use a (**landfill**, not //compost//) degradable bag when installing to keep the instrument clean. This will save you many hours of time cleaning them in preparation for their return. [[Here is a video>>url:http://auspass.edu.au/field/bd3c_removal.mp4]] demonstrating its effectiveness.
123 +)))
124 +
154 154  ----
155 155  
156 -= **Seismic Station Demobilization and Documentation** =
127 +=== **Seismic Station Demobilization and Documentation** ===
157 157  
158 158  1. (((
159 159  **Preparation for Demobilization**:
160 160  
161 -* Before starting the demobilization process, ensure you have a compass, tape, marker, pen, masking tape, clipboard, logbook, and compass ready in your tote bag.
132 +* Before starting the demobilization process, ensure you have a compass, tape, marker, pen, clipboard, logbook, and compass ready in your tote bag.
162 162  )))
163 163  1. (((
164 164  **Locating the instrument**:
... ... @@ -170,7 +170,7 @@
170 170  1. (((
171 171  **Labeling Instruments for Demobilization**:
172 172  
173 -* Write the station name and the instrument’s serial number on a masking tape label to apply to the top of the node.
144 +* Write the station name and the instrument’s serial number on a label.
174 174  * Add markers 'D' (for download), 'C' (for charge), and ‘R’ (for removal) next to checkboxes on the label.
175 175  * Affix this label to the top of the instrument to avoid confusion during the charging and downloading data.
176 176  )))
... ... @@ -199,38 +199,32 @@
199 199  
200 200  ----
201 201  
202 -= **Charging Procedure for Seismic Nodes** =
173 +=== **Charging Procedure for Seismic Nodes** ===
203 203  
204 -(((
205 -== 1. Preparation for Charging: ==
175 +1. (((
176 +**Preparation for Charging**:
206 206  
207 207  * 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.
208 208  )))
180 +1. (((
181 +**Disassembling the Node**:
209 209  
210 -(((
211 -== 2. Disassembling the Node: ==
212 -
213 -* For the IGU-16HR, remove the battery section (bottom half) from the sensor by unscrewing the spike section counter-clockwise.
183 +* Carefully remove the battery and the spike from the sensor. This is typically done by twisting the spike part of the instrument to release these components.
214 214  )))
185 +1. (((
186 +**Setting Nodes in the Charging Box**:
215 215  
216 -(((
217 -== 3. Setting Nodes in the Charging Box: ==
218 -
219 -* Connect to a safe indoor power supply, and turn on (red rocker switch).
220 -* Charging will begin automatically when nodes are inserted in the charging rack.
221 -* Place IGU-16HR battery sections upside-down in the rack, oriented with the terminal connectors.
188 +* Place up to 16 nodes into the charging box, arranging them with the spikes pointing upwards. This configuration is essential for proper connection and efficient charging.
222 222  )))
190 +1. (((
191 +**Monitoring the Charging Process**:
223 223  
224 -(((
225 -== 4. Monitoring the Charging Process: ==
226 -
227 -* Lights adjacent to the batteries will illuminate, indicating that charging is underway.
228 -* 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.
193 +* Once the nodes are set in the charging box and the charging process begins, red lights adjacent to the batteries will illuminate. These lights indicate that charging is underway.
194 +* 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.
229 229  )))
196 +1. (((
197 +**Updating Charge Status**:
230 230  
231 -(((
232 -== 5. Updating Charge Status: ==
233 -
234 234  * 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.
235 235  * This step is crucial for tracking the charging status of multiple units, especially when handling a large number of nodes.
236 236  )))
... ... @@ -240,29 +240,14 @@
240 240  
241 241  
242 242  
243 -{{{
244 - }}}
208 +[[image:1706153354750-415.png||data-xwiki-image-style-alignment="center" height="317" width="562"]]
245 245  
246 246  ----
247 247  
248 -= **Downloading and Converting Seismic Data to MiniSeed Format** =
212 +=== **Downloading and Converting Seismic Data to MiniSeed Format** ===
249 249  
250 -(% class="wikigeneratedid" %)
251 -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** ====
252 252  
253 -== Connection tips: ==
254 -
255 -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:
256 -
257 -* Place the node on the harvester gently, then firmly press it down onto the pins.
258 -* 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.
259 -* 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.
260 -* 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!
261 -
262 -
263 -
264 -== Node Registration and Software Setup ==
265 -
266 266  1. (((
267 267  **Registering Nodes in the System**:
268 268  
... ... @@ -279,29 +279,8 @@
279 279  * Ignore the settings for seismic recordings in the subsequent window. Resetting instruments (e.g., sampling rate, gain) requires reprogramming via script.
280 280  )))
281 281  
282 -== File structure ==
232 +==== **Data Downloading Process** ====
283 283  
284 -There are essentially three main folders where relevant PROSPECT and PROJECT DATA is stored. Individual projects will be found as subfolders in these.
285 -
286 -=== SOLOLITE ===
287 -
288 -This folder stores SoloLite config files and parameters. Nothing too important stored here, you can always start over and re-create this.
289 -
290 -=== DCCDATA ===
291 -
292 -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.
293 -
294 -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)//
295 -
296 -Then in the SoloLite software, go to tools > Reanalyze Seismic Data
297 -
298 -=== SOLODATA ===
299 -
300 -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.
301 -
302 -
303 -== Data Downloading Process ==
304 -
305 305  1. (((
306 306  **Initiating Data Download**:
307 307  
... ... @@ -318,48 +318,14 @@
318 318  * Click “prepare” followed by “run” to start reformatting. Monitor this process in the small panel at the bottom left.
319 319  * (% class="box warningmessage" %)
320 320  (((
321 -* **Ensure to export data as "COUNTS" (int32), not "mV" (float). This is critical!**
250 +* **Ensure to export data as "COUNTS", not "mV".**
322 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.**
252 +* **Set "Remove Gain" to the same decibel gain as during programming** **(by default ANU sets this to 24db (a factor of 15.848932).**
324 324  )))
325 325  )))
326 326  
327 -== Smart Solo IGU-16HR Polarity Notice ==
256 +==== **Handling Nodes During Download** ====
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.
330 -
331 -**The BD3C-5 data does not require a polarity inversion.**
332 -
333 -== 18 Leap Second bug ==
334 -
335 -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.
336 -
337 -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.
338 -
339 -{{code language="none"}}
340 -<?xml version="1.0" encoding="UTF-8"?>
341 -<config>
342 - <leapsecond>
343 - <interval>
344 - <start_time>2017-01-01#00:00:00</start_time>
345 - <end_time>2999-12-31#23:59:59</end_time>
346 - <second>18</second>
347 - </interval>
348 - <interval>
349 - <start_time>1970-01-01#00:00:00</start_time>
350 - <end_time>2017-01-01#00:00:00</end_time>
351 - <second>17</second>
352 - </interval>
353 - </leapsecond>
354 - <GPS_distance_threshold_degree>
355 - 4e-5
356 - </GPS_distance_threshold_degree>
357 -</config>
358 -{{/code}}
359 -
360 -
361 -== Handling Nodes During Download ==
362 -
363 363  1. (((
364 364  **Monitoring Download Indicators**:
365 365  
... ... @@ -375,7 +375,6 @@
375 375  * **Use fast external hard drives to avoid limitations in data harvesting.**
376 376  
377 377  * **Recommended specifications: USB-C, USB 3.0, and 4+ Tb of space.**
378 -* **The USB type for the harvester is TYPE-A, the typical normal rectangular shape.**
379 379  )))
380 380  )))
381 381  1. (((
... ... @@ -413,23 +413,13 @@
413 413  
414 414  ----
415 415  
416 -= **Cleaning** =
310 +=== **Cleaning** ===
417 417  
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.
312 +**Procedure for Seismic Nodes:**
419 419  
420 -= **Weights (for shipping)** =
314 +* If the nodes are placed in a thick plastic bag at the time of installation, the cleaning procedure should be straightforward. If not you have a lot of work to do before they are returned to us!
421 421  
422 -The weights of bags of nodes, as well as data harvesters and node chargers, are listed below:
423 -
424 -1 bag + 6 SP (IGU-16HR) nodes: 18 kg
425 -
426 -1 SP (IGU-16HR) data harvester: 21.5 kg
427 -
428 -1 SP (IGU-16HR) charger: 26.3 kg
429 -
430 -1 BB (BD3C-5) charger/data harvester (with and without 16 cables): 21 kg / 14.5 kg
431 -
432 -1 case + 5 BB (BD3C-5) nodes and 6 BB nodes: 22 kg / 25 kg
316 += =
433 433  )))
434 434  
435 435  (% class="col-xs-12 col-sm-4" %)
... ... @@ -438,11 +438,24 @@
438 438  (((
439 439  **Contents**
440 440  
441 -{{toc/}}
442 -
443 -
325 +(% class="wikitoc" %)
326 +* [[SmartSolo IGU 16HR 3C (5 Hz) Short Period Node>>path:#HSmartSoloIGU16HR3C285Hz29ShortPeriodNode]]
327 +** [[Sub-paragraph>>path:#HSub-paragraph]]
328 +** [[ >>path:#H]]
329 +* [[Smart Solo BD3C-5 (5 second) Broad-Band Node>>path:#HSmartSoloBD3C-5285second29Broad-BandNode]]
330 +** [[GPS Considerations>>path:#HGPSConsiderations]]
331 +* [[Keeping the Instruments Clean>>path:#HKeepingtheInstrumentsClean]]
332 +* [[Charge Time, Instrument Life, and Charge During Storage & Shipping>>path:#HChargeTime2CInstrumentLife2CandChargeDuringStorage26Shipping]]
333 +* [[Best Practices and Guide>>path:#HBestPracticesandGuide]]
334 +** [[Install>>path:#HInstall]]
335 +** [[Removing/Demob>>path:#HRemoving2FDemob]]
336 +** [[Charging>>path:#HCharging]]
337 +** [[Downloading and Converting Data to MiniSeed>>path:#HDownloadingandConvertingDatatoMiniSeed]]
338 +** [[Converting data>>path:#HConvertingdata]]
339 +** [[Cleaning>>path:#HCleaning]]
444 444  )))
445 445  
342 +
446 446  (% class="box" %)
447 447  (((
448 448  = SmartSolo [[BD3C-5>>url:https://smartsolo.com/cp-4.html]] =
... ... @@ -453,19 +453,15 @@
453 453  
454 454  |(% style="width:189px" %)**Frequency Band**|(% style="width:221px" %)5 Seconds to 150Hz
455 455  |(% style="width:189px" %)**Sensitivity**|(% style="width:221px" %)200 V/m/s
456 -|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)Φ158 x160mm(H)
353 +|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)158 x160mm
457 457  |(% style="width:189px" %)**Weight**|(% style="width:221px" %)2.8 kg
458 458  |(% style="width:189px" %)**Data Storage**|(% style="width:221px" %)64 Gb
459 -|(% style="width:189px" %)**Battery**|(% style="width:221px" %)(((
460 -Lithium-ion battery contained in equipment (168.84 Wh)
461 -
462 -UN3481 PI967 S1
356 +|(% style="width:189px" %)**Battery**|(% style="width:221px" %)Li_etc XXAh
463 463  )))
464 -)))
465 465  
466 466  (% class="box" %)
467 467  (((
468 -= SmartSolo [[IGU-16HR>>url:https://smartsolo.com/cp-3.html]]3C =
361 += SmartSolo [[IGU-16HR>>url:https://smartsolo.com/cp-3.html]] =
469 469  
470 470  [[image:smartsolo node.jpg]]
471 471  
... ... @@ -472,110 +472,13 @@
472 472  [[image:smartsolo node 2.jpg]]
473 473  
474 474  |(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 1652Hz
475 -|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)76.7 V/m/s
476 -|(% style="width:187px" %)**Size (with spike)**|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm(H)
477 -|(% style="width:187px" %)**Weight**|(% style="width:224px" %)2.4 kg
368 +|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)67.7 V/m/s
369 +|(% style="width:187px" %)**Size (with spike)**|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm
370 +|(% style="width:187px" %)**Weight**|(% style="width:224px" %)2.3 kg
478 478  |(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)64 Gb
479 -|(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((
480 -Lithium-ion battery contained in equipment (96.48 Wh)
481 -
482 -UN3481 PI967 S2
372 +|(% style="width:187px" %)**Battery**|(% style="width:224px" %)Li_etc XXAh
483 483  )))
484 -)))
485 485  
486 -(% class="box" %)
487 -(((
488 488  
489 -
490 -= SmartSolo [[IGU-16>>url:https://smartsolo.com/cp-3.html]]1C =
491 -
492 -
493 -[[image:Screenshot 2025-08-01 161027.png]]
494 -
495 -|(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 413Hz
496 -|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)80 V/m/s
497 -|(% style="width:187px" %)**Size (without spike)**|(% style="width:224px" %)95mm(L) × 103mm(W) × 118mm(H)
498 -|(% style="width:187px" %)**Weight**|(% style="width:224px" %)1.1 kg
499 -|(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)8 Gb
500 -|(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((
501 -Lithium-ion battery contained in equipment (38.48 Wh)
502 -
503 -UN3481 PI967 S2
504 504  )))
505 505  )))
506 -
507 -(% class="box" %)
508 -(((
509 -= SmartSolo BD3C-16 Portable Battery Charger =
510 -
511 -[[image:20250729_125049.jpg]]
512 -
513 -|**Dimensions (LxHxW)**|558 x 357 x 300mm
514 -|**Input rating**|100-210V - 50/60Hz
515 -|**Power**|1000W
516 -|**Weight**|14.5kg
517 -|**Weight with cables**|21kg
518 -)))
519 -
520 -(% class="box" id="HSmartSoloBD3C-16PortableBatteryCharger" %)
521 -(((
522 -= SmartSolo IGU-16 Portable Data Harvester =
523 -
524 -[[image:20250729_124747.jpg]]
525 -
526 -|**Dimensions (LxHxW)**|625 x 500 x 366mm
527 -|**Input rating**|100-210V - 50/60Hz
528 -|**Power**|100W
529 -|**Weight**|21.5 - 24kg
530 -|**Slots no.**|16
531 -|**Download Speed**|20MB/sec/slot
532 -)))
533 -
534 -(% class="box" %)
535 -(((
536 -= SmartSolo IGU-16 Portable Battery Charger =
537 -
538 -[[image:20250729_124644.jpg]]
539 -
540 -|**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
545 -)))
546 -
547 -(% class="box" %)
548 -(((
549 -= SmartSolo BD3C-5 Carry Case =
550 -
551 -[[image:20250729_124957.jpg]]
552 -
553 -
554 -|**Dimensions (LxHxW)**|590 x 225 x 405mm
555 -|**Weight**|8.2kg
556 -|**Slots no.**|6
557 -)))
558 -
559 -(% class="box" %)
560 -(((
561 -= SmartSolo IGU-16 3C Carry Bag =
562 -
563 -[[image:20250729_124502.jpg]]
564 -
565 -|**Dimensions (LxHxW)**|230 x 340 x 310mm
566 -|**Weight**|3.6kg
567 -|**Slots no.**|6
568 -)))
569 -
570 -(% class="box" %)
571 -(((
572 -= SmartSolo IGU-16 1C Carry Bag =
573 -
574 -[[image:20250729_124558.jpg]]
575 -
576 -|**Dimensions (LxHxW)**|225 x 200 x 550mm
577 -|**Weight**|
578 -|**Slots no.**|6
579 -)))
580 -)))
581 -)))
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
BB_programming.labels.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -111.5 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
example_metadata.txt
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -2.7 KB
Content
... ... @@ -1,46 +1,0 @@
1 -# AKL-HR Node Array (AHNA) code X5
2 -CITE: Name, Name, and Name. (2023). A Node Array [Data set]. International Federation of Digital Seismograph Networks. https://doi.org/10.7914/8jxr-7029
3 -
4 -#SITE START END LAT LONG ELEV SPS RECORDER S/N SENSOR S/N PROPERTY,LOCALITY,COUNTRY COMMENTS
5 -
6 -# INSTALL
7 -AKL01 20-05-2023T00:00 30-06-2023T00:00 -37.0471 175.5245 75 250 SSNODE_C 590001950 SSNODE_5S 590001950 "Te Puru,Hauraki,NZ"
8 -AKL02 20-05-2023T00:00 30-06-2023T00:00 -36.7476 175.5026 70 250 SSNODE_C 590001943 SSNODE_5S 590001943 "Coromandel Town,Hauraki,NZ"
9 -AKL03 20-05-2023T00:00 30-06-2023T00:00 -36.9694 175.5020 98 250 SSNODE_C 590002068 SSNODE_5S 590002068 "Te Mata,Hauraki,NZ"
10 -AKL05 19-05-2023T19:00 22-02-2023T00:00 -36.5996 174.3312 102 250 SSNODE_C 590001957 SSNODE_5S 590001957 "South Head South,Auckland,NZ" "site was disturbed"
11 -AKL06 19-05-2023T19:00 30-06-2023T00:00 -37.2459 175.3426 34 250 SSNODE_C 590001930 SSNODE_5S 590001930 "Back Miranda,Auckland,NZ"
12 -AKB05 02-05-2023T00:37 30-06-2023T00:00 -36.6651 175.4800 63 250 TSAWR TS085A TRILL120 4875 "Colville,Hauraki,NZ"
13 -
14 -# SERVICE 1
15 -AKL05 22-02-2023T00:00 30-06-2023T00:00 -36.5996 174.3312 102 250 SSNODE_C 590001999 SSNODE_.2S 590001999 "South Head South,Auckland,NZ" "swapped node to shortperiod"
16 -
17 -
18 -
19 -
20 -################### ANY LINE BEGINNING WITH # will be commented! Comments are good!
21 -
22 -
23 -# NOTES
24 -# the start/end time is not critical, but good to have. what IS critical are the times of instrument changes as this potentially affects response information
25 -# to mark equipment changes, add a new line with an updated start date (e.g. AKL05 above)
26 -# can use tabs or spaces, but spaces tend to look nicer. formatting ultimately doesn't matter too much so long as there is any sort of "white space" between the fields
27 -# if you don't know a serial number, put 999. if you don't know the elevation, put 0
28 -# for Nodes, put the same serial number for both Recoder and Sensor (since they are the same!)
29 -
30 -
31 -# EXAMPLE INSTRUMENT LABELS
32 -#LPR200 = ANU LPR-200 logger (beige box)
33 -#TSAWR = ANU TerraSAWR logger (yellow box)
34 -
35 -#TRILL120 = Trillium Compact 120s
36 -#TRILL20 = Trillium Compact 20s
37 -#TRILL120PH = Trillium Compact 120s PostHole
38 -#CMG6TD = Guralp 6TD
39 -#CMG3ESP = Guralp 3ESP
40 -#3DLITE = Lenarrtz 3D-LITE
41 -
42 -#SSNODE_C = output was in COUNTS (there is also SSNODE_MV, if you (accidentally!) output to millivolts etc)
43 -#SSNODE_5S = broadband (can also use SSNODE_BB)
44 -#SSNODE_.2S = shortperiod (can also use SSNODE_SP)
45 -
46 -#it doesn't matter too much what you use for equipment labels, so long as they are consistent and otherwise defined somewhere in the comments!
XWiki.XWikiRights[0]
Allow/Deny
... ... @@ -1,1 +1,0 @@
1 -Allow
Groups
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiAllGroup
Levels
... ... @@ -1,1 +1,0 @@
1 -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