Skip to Content
Last modified by robert on 2026/01/19 17:43
From version 96.3
edited by KB
on 2026/01/19 13:47
Change comment: There is no comment for this version
To version 46.1
edited by robert
on 2024/05/15 21:20
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
... ... @@ -4,107 +4,64 @@
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)**
9 +* **SmartSolo IGU 16HR 3C (5 Hz Short Period)**
10 +* **SmartSolo BD3C-5 (5 Second Broad-Band)**
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 +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 -(% 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 -)))
19 19  
20 20  ----
21 21  
22 22  = **Programming Defaults** =
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.
19 +ANU recommends that the SP 16HR-3C be set to a gain of 24db and no higher than 250 Hz sampling rate. The BD3C-5 should be set to a gain of 6db (maximum allowed). These are what we use for our internal experiments. **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.
25 25  
26 -[[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" data-xwiki-image-label="IGU-16 3C programming screen set at 250 Hz. Ensure that the circled areas are set!"]]
27 27  
28 -[[BD3C-5 programming screen set at 250 hz. Ensure circled areas are set!>>image:5S_node_programming.labels.png||alt="BD3C-5 programming screen set at 250 hz. Ensure that the circled areas are set!"]]
29 -
30 -
31 -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.
32 -
33 -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.
34 -
35 -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.
36 -
37 -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!**
38 -
39 -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.
40 -
41 -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.
42 -
43 -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.
44 -
45 -Bluetooth (BD3C-5 only) should be turned OFF to conserve power.
46 -
47 -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).
48 -
49 -{{info}}
50 -**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!
51 -{{/info}}
52 -
53 53  = **Fieldwork Preparation** =
54 54  
24 +(% class="box infomessage" %)
25 +(((
55 55  (% class="box warningmessage" %)
56 56  (((
57 57  **INVEST IN FAST EXTERNAL HARD DRIVES – DO NOT LET THIS BE THE LIMITATION OF DATA HARVESTING**
58 58  
59 59  **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.**
60 -
61 -**We have had good experience with the 4Tb Samsung T7 Shield drives.**
62 62  )))
32 +)))
63 63  
64 -== Magnets ==
65 -
66 -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).
67 -
68 -== Animal-Proofing ==
69 -
70 -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.
71 -
72 72  = **Installation** =
73 73  
74 -(% class="box infomessage" %)
75 -(((
76 -**Field logs are a critical component of fieldwork and this is especially the case for large N nodal deploys. Take notes!**
77 -)))
36 +== **1. Logbook documentation** ==
78 78  
79 -== 1. Logbook documentation ==
80 -
81 81  (((
82 -**Essential Details** for field logs:
39 +**Essential Details**: Record the following in a logbook:
83 83  
84 84  * Station name
85 -* Latitude, longitude, elevation
42 +* Latitude and longitude
86 86  * Names of team members present
87 -* Date and both local & UTC time of installation/removal
88 -* Serial number (SN) of the TOP HALF of the sensor (if a BD3C-5, there is only one serial number)
89 -* 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)
44 +* Date and local time of installation
45 +* Serial number (SN) of the sensor
46 +* Detailed notes on the site conditions and setup
90 90  
91 -[[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!
92 -
93 -== 2. Node Placement ==
48 +== **2. Node Placement** ==
94 94  )))
95 95  
51 +**Protection**: Place nodes inside (landfill) biodegradable bags to minimize cleaning and cross-site soil contamination.
52 +
96 96  **Site Analysis**:
97 97  
98 98  * **Take compass measurements away from the sensor as it will affect your measurement.**
99 -* Take photographs from various angles to document the site setup thoroughly.
100 -* Include a detailed site description in your notes
56 +* Take multiple photographs from various angles to document the site setup thoroughly.
57 +* 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)
101 101  
102 -== 3. GPS Considerations ==
59 +== **3. GPS Considerations** ==
103 103  
104 104  (% class="wikigeneratedid" %)
105 105  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.
106 106  
107 -== 4. Visibility and Location Marking ==
64 +== **4. Visibility and Location Marking** ==
108 108  
109 109  **Flag Placement**: Position a flag, preferably in a bright color (avoid green or yellow), near the instrument to aid in its future location.
110 110  
... ... @@ -113,7 +113,7 @@
113 113  * Use a GPS device to mark the instrument's exact location.
114 114  * Record this location in both your paper notes and the GPS device.
115 115  
116 -== (% style="color:inherit; font-family:inherit; font-size:max(18px, min(20px, 14.4444px + 0.462963vw))" %)5. Charge Time, Pre-Deployment & Post-Deployment(%%) ==
73 +== (% style="color:inherit; font-family:inherit; font-size:max(18px, min(20px, 14.4444px + 0.462963vw))" %)**5. Charge Time, Pre-Deployment & Post-Deployment**(%%) ==
117 117  
118 118  * **Charging Duration**: Both types of nodes take approximately 6-8 hours to fully charge from a flat state.
119 119  * **Pre-Deployment Charging**:
... ... @@ -123,22 +123,19 @@
123 123  ** 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.
124 124  
125 125  * **Post-Retrieval Charging**:
126 -** After retrieval, charge the instruments to about 50-60% (indicated by ORANGE LED) unless they are to be immediately re-deployed or transported.
127 -* **State of Charge (SoC) for Storage**:
128 -** Maintain a battery charge level of around 50-60% (i.e., ORANGE) for storage.
129 -** This charge level is recommended to prevent battery damage, and should be checked every six months.
130 -** Nodes should //__not be stored at full-charge (GREEN), or 0-charge (RED).__//
131 -** Storage at 0-charge damages lithium batteries**.**
132 -* **SoC for Transport:**
133 -** Charge levels for transport will be advised by the freighter. The required SoC will depend on volume and transport method (air, land, sea).
83 +** After retrieval, charge the instruments to about 50-60% (indicated as "orange" level) unless they are to be immediately re-deployed.
84 +* **Storage and Shipping Charge Level**:
85 +** Maintain a battery charge level of around 50-60% (e.g. "orange") for both storage and shipping purposes.
86 +** This charge level is recommended to prevent battery damage and is safe for transportation.
87 +** Nodes should not be stored fully charged, and it **they should especially not be stored with 0 charge.**
134 134  
135 135  (((
136 -== 6. Data Sharing and Metadata Creation ==
90 +== **6- Data Sharing and Metadata Creation** ==
137 137  )))
138 138  
139 139  **GPS Data**:
140 140  
141 -* Ensure you have __carefully documented__ precise lat/lon locations for each station.
95 +* Ensure you have documented precise lat/lon locations for each station and **DOCUMENTED THIS CAREFULLY**
142 142  
143 143  **Photo Sharing**:
144 144  
... ... @@ -146,12 +146,20 @@
146 146  
147 147  **Metadata File**:
148 148  
149 -* 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.
103 +* Create and organize metadata via the ANU metadata standard (~*~*add example)
150 150  
151 -== 7. Additional Best Practices ==
105 +== **7- Additional Best Practices** ==
152 152  
107 +* **Environmental Responsibility**: Ensure that the node placement and the materials used are environmentally responsible and adhere to local regulations.
153 153  * **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.
154 154  
110 +* (((
111 +==== **Keeping the Instruments Clean** ====
112 +)))
113 +* (((
114 +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.
115 +)))
116 +
155 155  ----
156 156  
157 157  = **Seismic Station Demobilization and Documentation** =
... ... @@ -203,34 +203,32 @@
203 203  = **Charging Procedure for Seismic Nodes** =
204 204  
205 205  (((
206 -== 1. Preparation for Charging: ==
168 +== **1. Preparation for Charging**: ==
207 207  
208 208  * 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.
209 209  )))
210 210  
211 211  (((
212 -== 2. Disassembling the Node: ==
174 +== **2. Disassembling the Node**: ==
213 213  
214 -* For the IGU-16HR, remove the battery section (bottom half) from the sensor by unscrewing the spike section counter-clockwise.
176 +* For the IGU-16HR, remove the battery (bottom half) from the sensor. This is done by unscrewing the spikes counter-clockwise.
215 215  )))
216 216  
217 217  (((
218 -== 3. Setting Nodes in the Charging Box: ==
180 +== **3. Setting Nodes in the Charging Box**: ==
219 219  
220 -* Connect to a safe indoor power supply, and turn on (red rocker switch).
221 -* Charging will begin automatically when nodes are inserted in the charging rack.
222 -* Place IGU-16HR battery sections upside-down in the rack, oriented with the terminal connectors.
182 +* Place 1-16 IGU-16HR battery components upside-down into the charger, assuring they are oriented properly.
223 223  )))
224 224  
225 225  (((
226 -== 4. Monitoring the Charging Process: ==
186 +== **4. Monitoring the Charging Process**: ==
227 227  
228 -* Lights adjacent to the batteries will illuminate, indicating that charging is underway.
229 -* 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.
188 +* 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.
189 +* 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.
230 230  )))
231 231  
232 232  (((
233 -== 5. Updating Charge Status: ==
193 +== **5. Updating Charge Status**: ==
234 234  
235 235  * 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.
236 236  * This step is crucial for tracking the charging status of multiple units, especially when handling a large number of nodes.
... ... @@ -241,29 +241,14 @@
241 241  
242 242  
243 243  
244 -{{{
245 - }}}
204 +[[image:1706153354750-415.png||data-xwiki-image-style-alignment="center" height="317" width="562"]]
246 246  
247 247  ----
248 248  
249 249  = **Downloading and Converting Seismic Data to MiniSeed Format** =
250 250  
251 -(% class="wikigeneratedid" %)
252 -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]]
210 +== **Node Registration and Software Setup** ==
253 253  
254 -== Connection tips: ==
255 -
256 -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:
257 -
258 -* Place the node on the harvester gently, then firmly press it down onto the pins.
259 -* 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.
260 -* 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.
261 -* 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!
262 -
263 -
264 -
265 -== Node Registration and Software Setup ==
266 -
267 267  1. (((
268 268  **Registering Nodes in the System**:
269 269  
... ... @@ -280,29 +280,8 @@
280 280  * Ignore the settings for seismic recordings in the subsequent window. Resetting instruments (e.g., sampling rate, gain) requires reprogramming via script.
281 281  )))
282 282  
283 -== File structure ==
228 +== **Data Downloading Process** ==
284 284  
285 -There are essentially three main folders where relevant PROSPECT and PROJECT DATA is stored. Individual projects will be found as subfolders in these.
286 -
287 -=== SOLOLITE ===
288 -
289 -This folder stores SoloLite config files and parameters. Nothing too important stored here, you can always start over and re-create this.
290 -
291 -=== DCCDATA ===
292 -
293 -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.
294 -
295 -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)//
296 -
297 -Then in the SoloLite software, go to tools > Reanalyze Seismic Data
298 -
299 -=== SOLODATA ===
300 -
301 -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.
302 -
303 -
304 -== Data Downloading Process ==
305 -
306 306  1. (((
307 307  **Initiating Data Download**:
308 308  
... ... @@ -319,48 +319,14 @@
319 319  * Click “prepare” followed by “run” to start reformatting. Monitor this process in the small panel at the bottom left.
320 320  * (% class="box warningmessage" %)
321 321  (((
322 -* **Ensure to export data as "COUNTS" (int32), not "mV" (float). This is critical!**
246 +* **Ensure to export data as "COUNTS", not "mV".**
323 323  
324 -* **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.**
248 +* **Set "Remove Gain" to the same decibel gain as during programming** **(by default ANU sets this to 24db (a factor of 15.848932).**
325 325  )))
326 326  )))
327 327  
328 -== Smart Solo IGU-16HR Polarity Notice ==
252 +== **Handling Nodes During Download** ==
329 329  
330 -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.
331 -
332 -**The BD3C-5 data does not require a polarity inversion.**
333 -
334 -== 18 Leap Second bug ==
335 -
336 -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.
337 -
338 -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.
339 -
340 -{{code language="none"}}
341 -<?xml version="1.0" encoding="UTF-8"?>
342 -<config>
343 - <leapsecond>
344 - <interval>
345 - <start_time>2017-01-01#00:00:00</start_time>
346 - <end_time>2999-12-31#23:59:59</end_time>
347 - <second>18</second>
348 - </interval>
349 - <interval>
350 - <start_time>1970-01-01#00:00:00</start_time>
351 - <end_time>2017-01-01#00:00:00</end_time>
352 - <second>17</second>
353 - </interval>
354 - </leapsecond>
355 - <GPS_distance_threshold_degree>
356 - 4e-5
357 - </GPS_distance_threshold_degree>
358 -</config>
359 -{{/code}}
360 -
361 -
362 -== Handling Nodes During Download ==
363 -
364 364  1. (((
365 365  **Monitoring Download Indicators**:
366 366  
... ... @@ -376,7 +376,6 @@
376 376  * **Use fast external hard drives to avoid limitations in data harvesting.**
377 377  
378 378  * **Recommended specifications: USB-C, USB 3.0, and 4+ Tb of space.**
379 -* **The USB type for the harvester is TYPE-A, the typical normal rectangular shape.**
380 380  )))
381 381  )))
382 382  1. (((
... ... @@ -416,23 +416,9 @@
416 416  
417 417  = **Cleaning** =
418 418  
419 -When assembled, the nodes are water resistant but not submersible. They can handle a good spray and wipe-down. A strong, non-wire brush is helpful to reach areas between the metal spikes on the bottom.
308 +**Procedure for Seismic Nodes:**
420 420  
421 -= **Weights (for shipping)** =
422 -
423 -The weights of bags of nodes, as well as data harvesters and node chargers, are listed below:
424 -
425 -1 bag + 6*IGU-16HR nodes: 18 kg
426 -
427 -1*IGU-16HR data harvester: 21.5 kg
428 -
429 -1*IGU-16HR charger: 26.3 kg
430 -
431 -1*BD3C-5 charger (with and without 16 cables): 21 kg / 14.5 kg
432 -
433 -1 case + 5*BD3C-5 nodes: 22 kg (aggregate battery weight <5kg, 168Wh)
434 -
435 -1 case + 6*BD3C-5 nodes: 25 kg (aggregate battery weight >5kg, 168Wh)
310 +* If the nodes are placed in a sturdy 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!
436 436  )))
437 437  
438 438  (% class="col-xs-12 col-sm-4" %)
... ... @@ -456,19 +456,15 @@
456 456  
457 457  |(% style="width:189px" %)**Frequency Band**|(% style="width:221px" %)5 Seconds to 150Hz
458 458  |(% style="width:189px" %)**Sensitivity**|(% style="width:221px" %)200 V/m/s
459 -|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)Φ158 x160mm(H)
334 +|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)158 x160mm
460 460  |(% style="width:189px" %)**Weight**|(% style="width:221px" %)2.8 kg
461 461  |(% style="width:189px" %)**Data Storage**|(% style="width:221px" %)64 Gb
462 -|(% style="width:189px" %)**Battery**|(% style="width:221px" %)(((
463 -Lithium-ion battery contained in equipment (168.84 Wh)
464 -
465 -UN3481 PI967 S1
337 +|(% style="width:189px" %)**Battery**|(% style="width:221px" %)Li_etc XXAh
466 466  )))
467 -)))
468 468  
469 469  (% class="box" %)
470 470  (((
471 -= SmartSolo [[IGU-16HR>>url:https://smartsolo.com/cp-3.html]]3C =
342 += SmartSolo [[IGU-16HR>>url:https://smartsolo.com/cp-3.html]] =
472 472  
473 473  [[image:smartsolo node.jpg]]
474 474  
... ... @@ -475,110 +475,13 @@
475 475  [[image:smartsolo node 2.jpg]]
476 476  
477 477  |(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 1652Hz
478 -|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)76.7 V/m/s
479 -|(% style="width:187px" %)**Size (with spike)**|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm(H)
349 +|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)67.7 V/m/s
350 +|(% style="width:187px" %)**Size (with spike)**|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm
480 480  |(% style="width:187px" %)**Weight**|(% style="width:224px" %)2.4 kg
481 481  |(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)64 Gb
482 -|(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((
483 -Lithium-ion battery contained in equipment (96.48 Wh)
484 -
485 -UN3481 PI967 S2
353 +|(% style="width:187px" %)**Battery**|(% style="width:224px" %)Lithium ion XXAh
486 486  )))
487 -)))
488 488  
489 -(% class="box" %)
490 -(((
491 491  
492 -
493 -= SmartSolo [[IGU-16>>url:https://smartsolo.com/cp-3.html]]1C =
494 -
495 -
496 -[[image:Screenshot 2025-08-01 161027.png]]
497 -
498 -|(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 413Hz
499 -|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)80 V/m/s
500 -|(% style="width:187px" %)**Size (without spike)**|(% style="width:224px" %)95mm(L) × 103mm(W) × 118mm(H)
501 -|(% style="width:187px" %)**Weight**|(% style="width:224px" %)1.1 kg
502 -|(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)8 Gb
503 -|(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((
504 -Lithium-ion battery contained in equipment (38.48 Wh)
505 -
506 -UN3481 PI967 S2
507 507  )))
508 508  )))
509 -
510 -(% class="box" %)
511 -(((
512 -= SmartSolo BD3C-16 Portable Battery Charger =
513 -
514 -[[image:20250729_125049.jpg]]
515 -
516 -|**Dimensions (LxHxW)**|558 x 357 x 300mm
517 -|**Input rating**|100-210V - 50/60Hz
518 -|**Power**|1000W
519 -|**Weight**|14.5kg
520 -|**Weight with cables**|21kg
521 -)))
522 -
523 -(% class="box" id="HSmartSoloBD3C-16PortableBatteryCharger" %)
524 -(((
525 -= SmartSolo IGU-16 Portable Data Harvester =
526 -
527 -[[image:20250729_124747.jpg]]
528 -
529 -|**Dimensions (LxHxW)**|625 x 500 x 366mm
530 -|**Input rating**|100-210V - 50/60Hz
531 -|**Power**|100W
532 -|**Weight**|21.5 - 24kg
533 -|**Slots no.**|16
534 -|**Download Speed**|20MB/sec/slot
535 -)))
536 -
537 -(% class="box" %)
538 -(((
539 -= SmartSolo IGU-16 Portable Battery Charger =
540 -
541 -[[image:20250729_124644.jpg]]
542 -
543 -|**Dimensions (LxHxW)**|625 x 500 x 366mm
544 -|**Input rating**|100-210V - 50/60Hz
545 -|**Power**|640W
546 -|**Weight**|26.3kg
547 -|**Slots no.**|16
548 -)))
549 -
550 -(% class="box" %)
551 -(((
552 -= SmartSolo BD3C-5 Carry Case =
553 -
554 -[[image:20250729_124957.jpg]]
555 -
556 -
557 -|**Dimensions (LxHxW)**|590 x 225 x 405mm
558 -|**Weight**|8.2kg
559 -|**Slots no.**|6
560 -)))
561 -
562 -(% class="box" %)
563 -(((
564 -= SmartSolo IGU-16 3C Carry Bag =
565 -
566 -[[image:20250729_124502.jpg]]
567 -
568 -|**Dimensions (LxHxW)**|230 x 340 x 310mm
569 -|**Weight**|3.6kg
570 -|**Slots no.**|6
571 -)))
572 -
573 -(% class="box" %)
574 -(((
575 -= SmartSolo IGU-16 1C Carry Bag =
576 -
577 -[[image:20250729_124558.jpg]]
578 -
579 -|**Dimensions (LxHxW)**|225 x 200 x 550mm
580 -|**Weight**|
581 -|**Slots no.**|6
582 -)))
583 -)))
584 -)))
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
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