Skip to Content
Last modified by robert on 2026/01/19 17:43
From version 93.1
edited by KB
on 2026/01/19 11:55
Change comment: IGU-16 3C (5Hz node) programming screen set at 250 Hz. Ensure that the highlighted areas are set!
To version 4.1
edited by robert
on 2024/01/10 18:46
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,577 +2,47 @@
2 2  (((
3 3  (% class="col-xs-12 col-sm-8" %)
4 4  (((
5 -= **Node Types** =
5 += SmartSolo IGU 16HR 3C (5 Hz) Short Period Node =
6 6  
7 -ANSIR supply two types of three-channel nodes, and one type of one-channel node:
7 +blahblah
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 +== Sub-paragraph ==
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.
11 +Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
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 -)))
13 +== Sub-paragraph ==
19 19  
20 -----
15 +Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
21 21  
22 -= **Programming Defaults** =
17 +=== Sub-sub paragraph ===
23 23  
24 -The nodes must be programmed in the SoloLite software prior to use. Screenshots for the short period 16HR-3C and broadband BDC3-5 are shown with our recommended parameters.
19 +Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
25 25  
26 -[[IGU-16 3C (short period node) programming screen set at 250 Hz. Ensure that the highlighted areas are set!>>image:SP_programming.labels.png||alt="IGU-16 3C programming screen"]]
27 27  
28 -[[BD3C-5 (broadband node) programming screen set at 250 hz. Ensure that the highlighted areas are set!>>image:BB_programming.labels.png||alt="BD3C-5 programming screen"]]
22 += Smart Solo BD3C-5 (5 second) Broad-Band Node =
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.
24 +Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
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.
26 +== GPS Considerations ==
33 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.
28 +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.
35 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!**
30 +== Keeping the Instruments Clean ==
37 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 (BB nodes only) should be turned OFF to conserve power.
45 -
46 -We recommend that the SP 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 -
54 -(% class="box warningmessage" %)
55 -(((
56 -**INVEST IN FAST EXTERNAL HARD DRIVES – DO NOT LET THIS BE THE LIMITATION OF DATA HARVESTING**
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.**
32 +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>>http://auspass.edu.au/field/bd3c_removal.mp4]] demonstrating its effectiveness.
61 61  )))
62 62  
63 -== Magnets ==
64 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 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.
70 -
71 -= **Installation** =
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 -)))
77 -
78 -== 1. Logbook documentation ==
79 -
80 -(((
81 -**Essential Details** for field logs:
82 -
83 -* Station name
84 -* Latitude, longitude, elevation
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)
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 ==
93 -)))
94 -
95 -**Protection**: Place nodes inside (landfill) biodegradable bags to minimize cleaning and cross-site soil contamination.
96 -
97 -**Site Analysis**:
98 -
99 -* **Take compass measurements away from the sensor as it will affect your measurement.**
100 -* Take photographs from various angles to document the site setup thoroughly.
101 -* Include a detailed site description in your notes
102 -
103 -== 3. GPS Considerations ==
104 -
105 -(% class="wikigeneratedid" %)
106 -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.
107 -
108 -== 4. Visibility and Location Marking ==
109 -
110 -**Flag Placement**: Position a flag, preferably in a bright color (avoid green or yellow), near the instrument to aid in its future location.
111 -
112 -**GPS Marking**:
113 -
114 -* Use a GPS device to mark the instrument's exact location.
115 -* Record this location in both your paper notes and the GPS device.
116 -
117 -== (% style="color:inherit; font-family:inherit; font-size:max(18px, min(20px, 14.4444px + 0.462963vw))" %)5. Charge Time, Pre-Deployment & Post-Deployment(%%) ==
118 -
119 -* **Charging Duration**: Both types of nodes take approximately 6-8 hours to fully charge from a flat state.
120 -* **Pre-Deployment Charging**:
121 -** Although the nodes hold their charge well, it's beneficial to give them a "top up" charge before deployment.
122 -
123 -* **Operational Duration**:
124 -** 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.
125 -
126 -* **Post-Retrieval Charging**:
127 -** After retrieval, charge the instruments to about 50-60% (indicated as "orange" level) unless they are to be immediately re-deployed.
128 -* **Storage and Shipping Charge Level**:
129 -** Maintain a battery charge level of around 50-60% (e.g. "orange") for both storage and shipping purposes.
130 -** This charge level is recommended to prevent battery damage and is safe for transportation.
131 -** Nodes should not be stored fully charged, and **they should especially not be stored with 0 charge as this damages lithium batteries.**
132 -
133 -(((
134 -== 6. Data Sharing and Metadata Creation ==
135 -)))
136 -
137 -**GPS Data**:
138 -
139 -* Ensure you have documented precise lat/lon locations for each station and **DOCUMENTED THIS CAREFULLY**
140 -
141 -**Photo Sharing**:
142 -
143 -* It is strongly encouraged to take pictures of each site and upload these to a shared platform (OneDrive, Dropbox, etc.).
144 -
145 -**Metadata File**:
146 -
147 -* 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.
148 -
149 -== 7. Additional Best Practices ==
150 -
151 -* **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.
152 -
153 -----
154 -
155 -= **Seismic Station Demobilization and Documentation** =
156 -
157 -1. (((
158 -**Preparation for Demobilization**:
159 -
160 -* Before starting the demobilization process, ensure you have a compass, tape, marker, pen, masking tape, clipboard, logbook, and compass ready in your tote bag.
161 -)))
162 -1. (((
163 -**Locating the instrument**:
164 -
165 -* Use the downloaded GPS file to accurately locate the node for demobilization.
166 -* Import this KMZ file onto your phone for easy reference and location tracking.
167 -* Utilize Google Maps or Google Earth to create a KMZ file of the station’s location.
168 -)))
169 -1. (((
170 -**Labeling Instruments for Demobilization**:
171 -
172 -* Write the station name and the instrument’s serial number on a masking tape label to apply to the top of the node.
173 -* Add markers 'D' (for download), 'C' (for charge), and ‘R’ (for removal) next to checkboxes on the label.
174 -* Affix this label to the top of the instrument to avoid confusion during the charging and downloading data.
175 -)))
176 -1. (((
177 -**Photographing the Setup Node**:
178 -
179 -* Take a photo of the entire setup node with the __//label//__ and __//compass visible//__.
180 -* This photo serves as a final record of the instrument’s condition and orientation at the time of removal.
181 -)))
182 -1. (((
183 -**Logging Demobilization Details**:
184 -
185 -* Use the field logbook to note the time of demobilization, serial numbers, and station name.
186 -* Record any observations or issues related to the instrument’s orientation, level, or any other relevant factors.
187 -)))
188 -1. (((
189 -**Final Checks and Equipment Removal**:
190 -
191 -* Before physically removing the instrument, double-check that all necessary data has been downloaded and all photos and notes have been taken.
192 -* Carefully dismantle and pack the equipment, ensuring that all components are accounted for and securely stored for transport.
193 -
194 -
195 -)))
196 -
197 -[[image:1706153556166-231.jpeg||data-xwiki-image-style-alignment="center" height="345" width="460"]]
198 -
199 -----
200 -
201 -= **Charging Procedure for Seismic Nodes** =
202 -
203 -(((
204 -== 1. Preparation for Charging: ==
205 -
206 -* 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.
207 -)))
208 -
209 -(((
210 -== 2. Disassembling the Node: ==
211 -
212 -* For the IGU-16HR, remove the battery (bottom half) from the sensor. This is done by unscrewing the spikes counter-clockwise.
213 -)))
214 -
215 -(((
216 -== 3. Setting Nodes in the Charging Box: ==
217 -
218 -* Place 1-16 IGU-16HR battery components upside-down into the charger, assuring they are oriented properly.
219 -)))
220 -
221 -(((
222 -== 4. Monitoring the Charging Process: ==
223 -
224 -* 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.
225 -* 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.
226 -)))
227 -
228 -(((
229 -== 5. Updating Charge Status: ==
230 -
231 -* 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.
232 -* This step is crucial for tracking the charging status of multiple units, especially when handling a large number of nodes.
233 -)))
234 -
235 -[[IGU 16-HRcharger (left) and harvester (right)>>image:1705195933422-337.png||data-xwiki-image-style-alignment="center" height="299" width="530"]]
236 -
237 -
238 -
239 -
240 -{{{
241 - }}}
242 -
243 -----
244 -
245 -= **Downloading and Converting Seismic Data to MiniSeed Format** =
246 -
247 -(% class="wikigeneratedid" %)
248 -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]]
249 -
250 -== Connection tips: ==
251 -
252 -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:
253 -
254 -* Place the node on the harvester gently, then firmly press it down onto the pins.
255 -* 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.
256 -* 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.
257 -* 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!
258 -
259 -
260 -
261 -== Node Registration and Software Setup ==
262 -
263 -1. (((
264 -**Registering Nodes in the System**:
265 -
266 -* To begin, register the nodes in the system so the software can recognize them.
267 -* Navigate to the installation folder of “SmartSoloApps SoloLite”.
268 -* Right-click on deviceconfig.exe and choose “run as an administrator”. Save the file to the “deviceconfig” directory (refer to the snapshot below).
269 -* To avoid double registration, replace the file each time you register a new node.
270 -)))
271 -1. (((
272 -**Creating a New Project in SoloLite**:
273 -
274 -* Open the “SoloLite” software.
275 -* Go to “File” and create a new project. Don't worry about finding the exact 16 nodes used in script writing.
276 -* Ignore the settings for seismic recordings in the subsequent window. Resetting instruments (e.g., sampling rate, gain) requires reprogramming via script.
277 -)))
278 -
279 -== File structure ==
280 -
281 -There are essentially three main folders where relevant PROSPECT and PROJECT DATA is stored. Individual projects will be found as subfolders in these.
282 -
283 -=== SOLOLITE ===
284 -
285 -This folder stores SoloLite config files and parameters. Nothing too important stored here, you can always start over and re-create this.
286 -
287 -=== DCCDATA ===
288 -
289 -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.
290 -
291 -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)//
292 -
293 -Then in the SoloLite software, go to tools > Reanalyze Seismic Data
294 -
295 -=== SOLODATA ===
296 -
297 -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.
298 -
299 -
300 -== Data Downloading Process ==
301 -
302 -1. (((
303 -**Initiating Data Download**:
304 -
305 -* Once a new project is created, the Data Transfer View panel will display connected nodes with details like series number and data size.
306 -* If “Prospect not matched” appears, it simply means the new project doesn’t match the original programming project. This is not a concern.
307 -* Select all nodes and right-click to “force download”. This starts the download process.
308 -* Completed downloads will appear as new folders in the Downloaded Data panel.
309 -)))
310 -1. (((
311 -**Exporting Data in Readable Format**:
312 -
313 -* Go to the “Tool” menu and select “export seismic data”.
314 -* Tailor other parameters to personal preference and ensure "Sample Interval" matches the setting used during node reset.
315 -* Click “prepare” followed by “run” to start reformatting. Monitor this process in the small panel at the bottom left.
316 -* (% class="box warningmessage" %)
317 -(((
318 -* **Ensure to export data as "COUNTS" (int32), not "mV" (float). This is critical!**
319 -
320 -* **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.**
321 -)))
322 -)))
323 -
324 -== Smart Solo IGU-16HR Polarity Notice ==
325 -
326 -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.
327 -
328 -**The BD3C-5 data does not require a polarity inversion.**
329 -
330 -== 18 Leap Second bug ==
331 -
332 -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.
333 -
334 -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.
335 -
336 -{{code language="none"}}
337 -<?xml version="1.0" encoding="UTF-8"?>
338 -<config>
339 - <leapsecond>
340 - <interval>
341 - <start_time>2017-01-01#00:00:00</start_time>
342 - <end_time>2999-12-31#23:59:59</end_time>
343 - <second>18</second>
344 - </interval>
345 - <interval>
346 - <start_time>1970-01-01#00:00:00</start_time>
347 - <end_time>2017-01-01#00:00:00</end_time>
348 - <second>17</second>
349 - </interval>
350 - </leapsecond>
351 - <GPS_distance_threshold_degree>
352 - 4e-5
353 - </GPS_distance_threshold_degree>
354 -</config>
355 -{{/code}}
356 -
357 -
358 -== Handling Nodes During Download ==
359 -
360 -1. (((
361 -**Monitoring Download Indicators**:
362 -
363 -* During download, green lights on nodes will blink, and associated red lights on the rack will flash.
364 -* Disconnect nodes properly before unplugging anything.
365 -* Be cautious: if the laptop enters sleep mode, the download will pause.
366 -)))
367 -1. (((
368 -//**Investment in Storage Hardware**~://
369 -
370 -* (% class="box warningmessage" %)
371 -(((
372 -* **Use fast external hard drives to avoid limitations in data harvesting.**
373 -
374 -* **Recommended specifications: USB-C, USB 3.0, and 4+ Tb of space.**
375 -* **The USB type for the harvester is TYPE-A, the typical normal rectangular shape.**
376 -)))
377 -)))
378 -1. (((
379 -**Metadata and Time Settings**:
380 -
381 -* Ensure all metadata is saved with the file.
382 -* System auto-determines the earliest data time as the start time. You can set it a day earlier at 00:00:00 for 24-hour data segments starting from midnight.
383 -)))
384 -1. (((
385 -**Finalizing the Download**:
386 -
387 -* After downloading, mark the //"D"// box on your temporary labels to indicate completion.
388 -
389 -
390 -)))
391 -
392 -[[image:1706153266647-145.png||data-xwiki-image-style-alignment="center" height="340" width="603"]]
393 -
394 -
395 -
396 -[[Caption>>image:1705195543887-977.png||data-xwiki-image-style-alignment="center" height="534" width="632"]]
397 -
398 -
399 -
400 -
401 -[[Caption>>image:1705195543890-537.png||data-xwiki-image-style-alignment="center" height="397" width="665"]]
402 -
403 -
404 -
405 -[[Caption>>image:1705195543891-334.png||data-xwiki-image-style-alignment="center" height="379" width="650"]]
406 -
407 -
408 -
409 -[[image:1705195543898-365.png||data-xwiki-image-style-alignment="center" height="467" width="674"]]
410 -
411 -----
412 -
413 -= **Cleaning** =
414 -
415 -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.
416 -
417 -= **Weights (for shipping)** =
418 -
419 -The weights of bags of nodes, as well as data harvesters and node chargers, are listed below:
420 -
421 -1 bag + 6 SP (IGU-16HR) nodes: 18 kg
422 -
423 -1 SP (IGU-16HR) data harvester: 21.5 kg
424 -
425 -1 SP (IGU-16HR) charger: 26.3 kg
426 -
427 -1 BB (BD3C-5) charger/data harvester (with and without 16 cables): 21 kg / 14.5 kg
428 -
429 -1 case + 5 BB (BD3C-5) nodes and 6 BB nodes: 22 kg / 25 kg
430 -)))
431 -
432 432  (% class="col-xs-12 col-sm-4" %)
433 433  (((
434 -(% class="box" %)
435 -(((
436 -**Contents**
437 -
38 +{{box title="**Contents**"}}
438 438  {{toc/}}
40 +{{/box}}
439 439  
440 -
441 -)))
442 442  
443 -(% class="box" %)
444 -(((
445 -= SmartSolo [[BD3C-5>>url:https://smartsolo.com/cp-4.html]] =
43 +//[[IGU-16HR>>https://smartsolo.com/cp-3.html]]//
446 446  
447 -[[image:Smartsolo IGU BD3C 5 (2).jpg]]
448 448  
449 -[[image:smartsolo.jpg]]
450 -
451 -|(% style="width:189px" %)**Frequency Band**|(% style="width:221px" %)5 Seconds to 150Hz
452 -|(% style="width:189px" %)**Sensitivity**|(% style="width:221px" %)200 V/m/s
453 -|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)Φ158 x160mm(H)
454 -|(% style="width:189px" %)**Weight**|(% style="width:221px" %)2.8 kg
455 -|(% style="width:189px" %)**Data Storage**|(% style="width:221px" %)64 Gb
456 -|(% style="width:189px" %)**Battery**|(% style="width:221px" %)(((
457 -Lithium-ion battery contained in equipment (168.84 Wh)
458 -
459 -UN3481 PI967 S1
46 +//[[BD3C-5>>https://smartsolo.com/cp-4.html]]//
460 460  )))
461 461  )))
462 -
463 -(% class="box" %)
464 -(((
465 -= SmartSolo [[IGU-16HR>>url:https://smartsolo.com/cp-3.html]]3C =
466 -
467 -[[image:smartsolo node.jpg]]
468 -
469 -[[image:smartsolo node 2.jpg]]
470 -
471 -|(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 1652Hz
472 -|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)76.7 V/m/s
473 -|(% style="width:187px" %)**Size (with spike)**|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm(H)
474 -|(% style="width:187px" %)**Weight**|(% style="width:224px" %)2.4 kg
475 -|(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)64 Gb
476 -|(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((
477 -Lithium-ion battery contained in equipment (96.48 Wh)
478 -
479 -UN3481 PI967 S2
480 -)))
481 -)))
482 -
483 -(% class="box" %)
484 -(((
485 -
486 -
487 -= SmartSolo [[IGU-16>>url:https://smartsolo.com/cp-3.html]]1C =
488 -
489 -
490 -[[image:Screenshot 2025-08-01 161027.png]]
491 -
492 -|(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 413Hz
493 -|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)80 V/m/s
494 -|(% style="width:187px" %)**Size (without spike)**|(% style="width:224px" %)95mm(L) × 103mm(W) × 118mm(H)
495 -|(% style="width:187px" %)**Weight**|(% style="width:224px" %)1.1 kg
496 -|(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)8 Gb
497 -|(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((
498 -Lithium-ion battery contained in equipment (38.48 Wh)
499 -
500 -UN3481 PI967 S2
501 -)))
502 -)))
503 -
504 -(% class="box" %)
505 -(((
506 -= SmartSolo BD3C-16 Portable Battery Charger =
507 -
508 -[[image:20250729_125049.jpg]]
509 -
510 -|**Dimensions (LxHxW)**|558 x 357 x 300mm
511 -|**Input rating**|100-210V - 50/60Hz
512 -|**Power**|1000W
513 -|**Weight**|14.5kg
514 -|**Weight with cables**|21kg
515 -)))
516 -
517 -(% class="box" id="HSmartSoloBD3C-16PortableBatteryCharger" %)
518 -(((
519 -= SmartSolo IGU-16 Portable Data Harvester =
520 -
521 -[[image:20250729_124747.jpg]]
522 -
523 -|**Dimensions (LxHxW)**|625 x 500 x 366mm
524 -|**Input rating**|100-210V - 50/60Hz
525 -|**Power**|100W
526 -|**Weight**|21.5 - 24kg
527 -|**Slots no.**|16
528 -|**Download Speed**|20MB/sec/slot
529 -)))
530 -
531 -(% class="box" %)
532 -(((
533 -= SmartSolo IGU-16 Portable Battery Charger =
534 -
535 -[[image:20250729_124644.jpg]]
536 -
537 -|**Dimensions (LxHxW)**|625 x 500 x 366mm
538 -|**Input rating**|100-210V - 50/60Hz
539 -|**Power**|640W
540 -|**Weight**|26.3kg
541 -|**Slots no.**|16
542 -)))
543 -
544 -(% class="box" %)
545 -(((
546 -= SmartSolo BD3C-5 Carry Case =
547 -
548 -[[image:20250729_124957.jpg]]
549 -
550 -
551 -|**Dimensions (LxHxW)**|590 x 225 x 405mm
552 -|**Weight**|8.2kg
553 -|**Slots no.**|6
554 -)))
555 -
556 -(% class="box" %)
557 -(((
558 -= SmartSolo IGU-16 3C Carry Bag =
559 -
560 -[[image:20250729_124502.jpg]]
561 -
562 -|**Dimensions (LxHxW)**|230 x 340 x 310mm
563 -|**Weight**|3.6kg
564 -|**Slots no.**|6
565 -)))
566 -
567 -(% class="box" %)
568 -(((
569 -= SmartSolo IGU-16 1C Carry Bag =
570 -
571 -[[image:20250729_124558.jpg]]
572 -
573 -|**Dimensions (LxHxW)**|225 x 200 x 550mm
574 -|**Weight**|
575 -|**Slots no.**|6
576 -)))
577 -)))
578 -)))
1705195543887-977.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -259.0 KB
Content
1705195543890-537.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -52.4 KB
Content
1705195543891-334.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -75.6 KB
Content
1705195543898-365.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -141.1 KB
Content
1705195933422-337.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -2.0 MB
Content
1705196270090-364.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -375.2 KB
Content
1706153266647-145.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.sima
Size
... ... @@ -1,1 +1,0 @@
1 -1.7 MB
Content
1706153354750-415.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.sima
Size
... ... @@ -1,1 +1,0 @@
1 -2.1 MB
Content
1706153556166-231.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.sima
Size
... ... @@ -1,1 +1,0 @@
1 -839.4 KB
Content
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
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
Smartsolo IGU BD3C 5 (2).jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -909.0 KB
Content
Smartsolo IGU BD3C 5.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -2.7 MB
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!
smartsolo node 2.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -1.0 MB
Content
smartsolo node.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -1.1 MB
Content
smartsolo.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -1.0 MB
Content
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