Wiki source code of SmartSolo Seismometers
Last modified by Kimberley on 2025/05/26 13:10
Show last authors
author | version | line-number | content |
---|---|---|---|
1 | (% class="row" %) | ||
2 | ((( | ||
3 | (% class="col-xs-12 col-sm-8" %) | ||
4 | ((( | ||
5 | = **Node Types** = | ||
6 | |||
7 | ANSIR carry two types of three-channel nodes | ||
8 | |||
9 | * **SmartSolo IGU 16HR 3C (5 Hz Short Period)** | ||
10 | * **SmartSolo BD3C-5 (5 Second Broad-Band)** | ||
11 | |||
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. | ||
13 | |||
14 | |||
15 | ---- | ||
16 | |||
17 | = **Programming Defaults** = | ||
18 | |||
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. | ||
20 | |||
21 | |||
22 | = **Fieldwork Preparation** = | ||
23 | |||
24 | (% class="box infomessage" %) | ||
25 | ((( | ||
26 | (% class="box warningmessage" %) | ||
27 | ((( | ||
28 | **INVEST IN FAST EXTERNAL HARD DRIVES – DO NOT LET THIS BE THE LIMITATION OF DATA HARVESTING** | ||
29 | |||
30 | **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.** | ||
31 | ))) | ||
32 | ))) | ||
33 | |||
34 | = **Installation** = | ||
35 | |||
36 | == **1. Logbook documentation** == | ||
37 | |||
38 | ((( | ||
39 | **Essential Details**: Record the following in a logbook: | ||
40 | |||
41 | * Station name | ||
42 | * Latitude and longitude | ||
43 | * Names of team members present | ||
44 | * Date and local time of installation | ||
45 | * Serial number (SN) of the sensor | ||
46 | * Detailed notes on the site conditions and setup | ||
47 | |||
48 | == **2. Node Placement** == | ||
49 | ))) | ||
50 | |||
51 | **Protection**: Place nodes inside (landfill) biodegradable bags to minimize cleaning and cross-site soil contamination. | ||
52 | |||
53 | **Site Analysis**: | ||
54 | |||
55 | * **Take compass measurements away from the sensor as it will affect your measurement.** | ||
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) | ||
58 | |||
59 | == **3. GPS Considerations** == | ||
60 | |||
61 | (% class="wikigeneratedid" %) | ||
62 | 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. | ||
63 | |||
64 | == **4. Visibility and Location Marking** == | ||
65 | |||
66 | **Flag Placement**: Position a flag, preferably in a bright color (avoid green or yellow), near the instrument to aid in its future location. | ||
67 | |||
68 | **GPS Marking**: | ||
69 | |||
70 | * Use a GPS device to mark the instrument's exact location. | ||
71 | * Record this location in both your paper notes and the GPS device. | ||
72 | |||
73 | == (% style="color:inherit; font-family:inherit; font-size:max(18px, min(20px, 14.4444px + 0.462963vw))" %)**5. Charge Time, Pre-Deployment & Post-Deployment**(%%) == | ||
74 | |||
75 | * **Charging Duration**: Both types of nodes take approximately 6-8 hours to fully charge from a flat state. | ||
76 | * **Pre-Deployment Charging**: | ||
77 | ** Although the nodes hold their charge well, it's beneficial to give them a "top up" charge before deployment. | ||
78 | |||
79 | * **Operational Duration**: | ||
80 | ** 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. | ||
81 | |||
82 | * **Post-Retrieval Charging**: | ||
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.** | ||
88 | |||
89 | ((( | ||
90 | == **6. Data Sharing and Metadata Creation** == | ||
91 | ))) | ||
92 | |||
93 | **GPS Data**: | ||
94 | |||
95 | * Ensure you have documented precise lat/lon locations for each station and **DOCUMENTED THIS CAREFULLY** | ||
96 | |||
97 | **Photo Sharing**: | ||
98 | |||
99 | * It is strongly encouraged to take pictures of each site and upload these to a shared platform (OneDrive, Dropbox, etc.). | ||
100 | |||
101 | **Metadata File**: | ||
102 | |||
103 | * Create and organize metadata according to the [[ANU metadata standard txt file>>attach:example_metadata.txt]]. | ||
104 | |||
105 | == **7. Additional Best Practices** == | ||
106 | |||
107 | * **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. | ||
108 | |||
109 | ---- | ||
110 | |||
111 | = **Seismic Station Demobilization and Documentation** = | ||
112 | |||
113 | 1. ((( | ||
114 | **Preparation for Demobilization**: | ||
115 | |||
116 | * Before starting the demobilization process, ensure you have a compass, tape, marker, pen, masking tape, clipboard, logbook, and compass ready in your tote bag. | ||
117 | ))) | ||
118 | 1. ((( | ||
119 | **Locating the instrument**: | ||
120 | |||
121 | * Use the downloaded GPS file to accurately locate the node for demobilization. | ||
122 | * Import this KMZ file onto your phone for easy reference and location tracking. | ||
123 | * Utilize Google Maps or Google Earth to create a KMZ file of the station’s location. | ||
124 | ))) | ||
125 | 1. ((( | ||
126 | **Labeling Instruments for Demobilization**: | ||
127 | |||
128 | * Write the station name and the instrument’s serial number on a masking tape label to apply to the top of the node. | ||
129 | * Add markers 'D' (for download), 'C' (for charge), and ‘R’ (for removal) next to checkboxes on the label. | ||
130 | * Affix this label to the top of the instrument to avoid confusion during the charging and downloading data. | ||
131 | ))) | ||
132 | 1. ((( | ||
133 | **Photographing the Setup Node**: | ||
134 | |||
135 | * Take a photo of the entire setup node with the __//label//__ and __//compass visible//__. | ||
136 | * This photo serves as a final record of the instrument’s condition and orientation at the time of removal. | ||
137 | ))) | ||
138 | 1. ((( | ||
139 | **Logging Demobilization Details**: | ||
140 | |||
141 | * Use the field logbook to note the time of demobilization, serial numbers, and station name. | ||
142 | * Record any observations or issues related to the instrument’s orientation, level, or any other relevant factors. | ||
143 | ))) | ||
144 | 1. ((( | ||
145 | **Final Checks and Equipment Removal**: | ||
146 | |||
147 | * Before physically removing the instrument, double-check that all necessary data has been downloaded and all photos and notes have been taken. | ||
148 | * Carefully dismantle and pack the equipment, ensuring that all components are accounted for and securely stored for transport. | ||
149 | |||
150 | |||
151 | ))) | ||
152 | |||
153 | [[image:1706153556166-231.jpeg||data-xwiki-image-style-alignment="center" height="345" width="460"]] | ||
154 | |||
155 | ---- | ||
156 | |||
157 | = **Charging Procedure for Seismic Nodes** = | ||
158 | |||
159 | ((( | ||
160 | == **1. Preparation for Charging**: == | ||
161 | |||
162 | * 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. | ||
163 | ))) | ||
164 | |||
165 | ((( | ||
166 | == **2. Disassembling the Node**: == | ||
167 | |||
168 | * For the IGU-16HR, remove the battery (bottom half) from the sensor. This is done by unscrewing the spikes counter-clockwise. | ||
169 | ))) | ||
170 | |||
171 | ((( | ||
172 | == **3. Setting Nodes in the Charging Box**: == | ||
173 | |||
174 | * Place 1-16 IGU-16HR battery components upside-down into the charger, assuring they are oriented properly. | ||
175 | ))) | ||
176 | |||
177 | ((( | ||
178 | == **4. Monitoring the Charging Process**: == | ||
179 | |||
180 | * 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. | ||
181 | * 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. | ||
182 | ))) | ||
183 | |||
184 | ((( | ||
185 | == **5. Updating Charge Status**: == | ||
186 | |||
187 | * 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. | ||
188 | * This step is crucial for tracking the charging status of multiple units, especially when handling a large number of nodes. | ||
189 | ))) | ||
190 | |||
191 | [[IGU 16-HRcharger (left) and harvester (right)>>image:1705195933422-337.png||data-xwiki-image-style-alignment="center" height="299" width="530"]] | ||
192 | |||
193 | |||
194 | |||
195 | |||
196 | [[image:1706153354750-415.png||data-xwiki-image-style-alignment="center" height="317" width="562"]] | ||
197 | |||
198 | ---- | ||
199 | |||
200 | = **Downloading and Converting Seismic Data to MiniSeed Format** = | ||
201 | |||
202 | == **Node Registration and Software Setup** == | ||
203 | |||
204 | 1. ((( | ||
205 | **Registering Nodes in the System**: | ||
206 | |||
207 | * To begin, register the nodes in the system so the software can recognize them. | ||
208 | * Navigate to the installation folder of “SmartSoloApps SoloLite”. | ||
209 | * Right-click on deviceconfig.exe and choose “run as an administrator”. Save the file to the “deviceconfig” directory (refer to the snapshot below). | ||
210 | * To avoid double registration, replace the file each time you register a new node. | ||
211 | ))) | ||
212 | 1. ((( | ||
213 | **Creating a New Project in SoloLite**: | ||
214 | |||
215 | * Open the “SoloLite” software. | ||
216 | * Go to “File” and create a new project. Don't worry about finding the exact 16 nodes used in script writing. | ||
217 | * Ignore the settings for seismic recordings in the subsequent window. Resetting instruments (e.g., sampling rate, gain) requires reprogramming via script. | ||
218 | ))) | ||
219 | |||
220 | == **Data Downloading Process** == | ||
221 | |||
222 | 1. ((( | ||
223 | **Initiating Data Download**: | ||
224 | |||
225 | * Once a new project is created, the Data Transfer View panel will display connected nodes with details like series number and data size. | ||
226 | * If “Prospect not matched” appears, it simply means the new project doesn’t match the original programming project. This is not a concern. | ||
227 | * Select all nodes and right-click to “force download”. This starts the download process. | ||
228 | * Completed downloads will appear as new folders in the Downloaded Data panel. | ||
229 | ))) | ||
230 | 1. ((( | ||
231 | **Exporting Data in Readable Format**: | ||
232 | |||
233 | * Go to the “Tool” menu and select “export seismic data”. | ||
234 | * Tailor other parameters to personal preference and ensure "Sample Interval" matches the setting used during node reset. | ||
235 | * Click “prepare” followed by “run” to start reformatting. Monitor this process in the small panel at the bottom left. | ||
236 | * (% class="box warningmessage" %) | ||
237 | ((( | ||
238 | * **Ensure to export data as "COUNTS", not "mV".** | ||
239 | |||
240 | * **Set "Remove Gain" to the same decibel gain as during programming** **(by default ANU sets this to 24db for short period nodes (a factor of 15.848932), and 6db for broadband nodes).** | ||
241 | ))) | ||
242 | ))) | ||
243 | |||
244 | == **Handling Nodes During Download** == | ||
245 | |||
246 | 1. ((( | ||
247 | **Monitoring Download Indicators**: | ||
248 | |||
249 | * During download, green lights on nodes will blink, and associated red lights on the rack will flash. | ||
250 | * Disconnect nodes properly before unplugging anything. | ||
251 | * Be cautious: if the laptop enters sleep mode, the download will pause. | ||
252 | ))) | ||
253 | 1. ((( | ||
254 | //**Investment in Storage Hardware**~:// | ||
255 | |||
256 | * (% class="box warningmessage" %) | ||
257 | ((( | ||
258 | * **Use fast external hard drives to avoid limitations in data harvesting.** | ||
259 | |||
260 | * **Recommended specifications: USB-C, USB 3.0, and 4+ Tb of space.** | ||
261 | ))) | ||
262 | ))) | ||
263 | 1. ((( | ||
264 | **Metadata and Time Settings**: | ||
265 | |||
266 | * Ensure all metadata is saved with the file. | ||
267 | * 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. | ||
268 | ))) | ||
269 | 1. ((( | ||
270 | **Finalizing the Download**: | ||
271 | |||
272 | * After downloading, mark the //"D"// box on your temporary labels to indicate completion. | ||
273 | |||
274 | |||
275 | ))) | ||
276 | |||
277 | [[image:1706153266647-145.png||data-xwiki-image-style-alignment="center" height="340" width="603"]] | ||
278 | |||
279 | |||
280 | |||
281 | [[Caption>>image:1705195543887-977.png||data-xwiki-image-style-alignment="center" height="534" width="632"]] | ||
282 | |||
283 | |||
284 | |||
285 | |||
286 | [[Caption>>image:1705195543890-537.png||data-xwiki-image-style-alignment="center" height="397" width="665"]] | ||
287 | |||
288 | |||
289 | |||
290 | [[Caption>>image:1705195543891-334.png||data-xwiki-image-style-alignment="center" height="379" width="650"]] | ||
291 | |||
292 | |||
293 | |||
294 | [[image:1705195543898-365.png||data-xwiki-image-style-alignment="center" height="467" width="674"]] | ||
295 | |||
296 | ---- | ||
297 | |||
298 | = **Cleaning** = | ||
299 | |||
300 | **Procedure for Seismic Nodes:** | ||
301 | |||
302 | Top half: | ||
303 | |||
304 | Bottom half: The metal spikes on the bottom half of the nodes can be cleaned using a wire brush, though should still be wiped down for dust afterwards. | ||
305 | |||
306 | |||
307 | = **Weights (for shipping)** = | ||
308 | |||
309 | The weights of bags of nodes, as well as data harvesters and node chargers, are listed below: | ||
310 | |||
311 | 1 bag + 6 SP (IGU-16HR) nodes: 18 kg | ||
312 | |||
313 | 1 SP (IGU-16HR) data harvester: 21.5 kg | ||
314 | |||
315 | 1 SP (IGU-16HR) charger: 26.3 kg | ||
316 | |||
317 | 1 BB (BD3C-5) charger/data harvester (with and without 16 cables): 21 kg / 14.5 kg | ||
318 | |||
319 | 1 case + 5 BB (BD3C-5) nodes and 6 BB nodes: 22 kg / 25 kg | ||
320 | ))) | ||
321 | |||
322 | (% class="col-xs-12 col-sm-4" %) | ||
323 | ((( | ||
324 | (% class="box" %) | ||
325 | ((( | ||
326 | **Contents** | ||
327 | |||
328 | {{toc/}} | ||
329 | |||
330 | |||
331 | ))) | ||
332 | |||
333 | (% class="box" %) | ||
334 | ((( | ||
335 | = SmartSolo [[BD3C-5>>url:https://smartsolo.com/cp-4.html]] = | ||
336 | |||
337 | [[image:Smartsolo IGU BD3C 5 (2).jpg]] | ||
338 | |||
339 | [[image:smartsolo.jpg]] | ||
340 | |||
341 | |(% style="width:189px" %)**Frequency Band**|(% style="width:221px" %)5 Seconds to 150Hz | ||
342 | |(% style="width:189px" %)**Sensitivity**|(% style="width:221px" %)200 V/m/s | ||
343 | |(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)158 x160mm | ||
344 | |(% style="width:189px" %)**Weight**|(% style="width:221px" %)2.8 kg | ||
345 | |(% style="width:189px" %)**Data Storage**|(% style="width:221px" %)64 Gb | ||
346 | |(% style="width:189px" %)**Battery**|(% style="width:221px" %)((( | ||
347 | Lithium-ion battery contained in equipment (168.84 Wh) | ||
348 | |||
349 | UN3481 PI967 S1 | ||
350 | ))) | ||
351 | ))) | ||
352 | |||
353 | (% class="box" %) | ||
354 | ((( | ||
355 | = SmartSolo [[IGU-16HR>>url:https://smartsolo.com/cp-3.html]] = | ||
356 | |||
357 | [[image:smartsolo node.jpg]] | ||
358 | |||
359 | [[image:smartsolo node 2.jpg]] | ||
360 | |||
361 | |(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 1652Hz | ||
362 | |(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)67.7 V/m/s | ||
363 | |(% style="width:187px" %)**Size (with spike)**|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm | ||
364 | |(% style="width:187px" %)**Weight**|(% style="width:224px" %)2.4 kg | ||
365 | |(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)64 Gb | ||
366 | |(% style="width:187px" %)**Battery**|(% style="width:224px" %)((( | ||
367 | Lithium-ion battery contained in equipment (96.48 Wh) | ||
368 | |||
369 | UN3481 PI967 S2 | ||
370 | ))) | ||
371 | ))) | ||
372 | |||
373 | |||
374 | ))) | ||
375 | ))) |