Skip to Content
Last modified by robert on 2026/02/27 19:58
From version 107.1
edited by robert
on 2026/02/17 16:28
Change comment: There is no comment for this version
To version 7.1
edited by robert
on 2024/01/14 12:24
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
Content
... ... @@ -2,642 +2,150 @@
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. Not 'HR')**
9 +== Sub-paragraph ==
12 12  
13 -Visit the [[SmartSolo page>>https://smartsolo.com/igu.html]] for more detail.
14 14  
15 -The three-channel nodes have a theoretical battery capacity of ~~30 days, whereas the single-channel type has a capacity of ~~50 days. The programming, operation and downloading procedures for all types of SmartSolo nodes are also similar.
12 +== ==
16 16  
17 -(% class="box infomessage" %)
18 -(((
19 -**Freight update, 2026: **Freight options for lithium-ion batteries are changing in 2025/2026 to comply with updated transport safety regulations. This will impact supply of IGU 16 (<100Wh) and BD3C (168Wh) nodes. Advice will be sought from freighters on a case-by-case basis while they implement new guidelines.
20 -)))
21 21  
22 -----
15 += Smart Solo BD3C-5 (5 second) Broad-Band Node =
23 23  
24 -= **Programming Defaults** =
17 +Lorem
25 25  
26 -The nodes must be programmed in the SoloLite software prior to use. The screenshots below show our recommended parameters for the 5 Hz (16HR-3C) and 5 second (BDC3-5) nodes.
27 27  
28 -[[IGU16HR-3C programming screen set at 250 Hz. Ensure circled areas are set!>>image:5Hz_node_programming.labels.png||alt="IGU-16 3C programming screen"]]
20 +== GPS Considerations ==
29 29  
30 -[[BD3C-5 programming screen set at 250 Hz. Ensure circled areas are set!>>image:5S_node_programming.labels.png||alt="BD3C-5 programming screen set at 250 hz. Ensure that the circled areas are set!"]]
22 +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.
31 31  
24 +== Keeping the Instruments Clean ==
32 32  
33 -FIFO (first in, first out) data mode is safest as this will overwrite old data in case you forgot to clear the storage. At <= 250 hz you can fit 4++ months of data on these, shouldn't be an issue.
26 +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.
34 34  
35 -Note that the samplerate is instead given in sample spacing, in milliseconds. 4 ms = 250 Hz, 1 ms = 1000 Hz, 10 ms = 100 Hz, ad nauseam.
36 36  
37 -Be sure to set the channel types to Seismic and the gain appropriately. For active source (i.e. explosions) you can leave the gain at 0, but for passive experiments some gain is purported to be helpful (although we have found this to be somewhat negligible). We can confirm that 6db for the broadband nodes and 24db for the short period works well.
29 += Charge Time, Instrument Life, and Charge During Storage & Shipping =
38 38  
39 -If you want recording to begin immediately, ensure that begin date is in the past by at least a few days. If you prefer to have a timed turn-on, then set the times as needed. **Be warned that recording will not begin until a GPS lock is achieved, so if you set it to a future turn-on but bury it too deeply, it may not record!**
31 +Both nodes take about 6-8 hours to charge from flat and hold their charge reasonably well, however you may benefit from a "top up" charge immediately prior to deploy. The instruments should last around 30 days per cycle (recording at 250hz) with GPS on cycle on and bluetooth disabled.
40 40  
41 -In newer versions of the software there is a "power consumption" setting.. we are no sure what this does exactly, but the manual says it gives life a "boost" at the expense of about 3 db of resolution. Until this can be quantified a bit better it is not recommended.
33 +Upon retrieval, the instruments should not be stored flat as this will damage the batteries. It is recommended to charge them back up "to orange" such that they are charged around ~~50-60%. This is also acceptable for shipping.
42 42  
43 -Storage type can be DLD (proprietary) or Miniseed. We assume the software works best with their proprietary format so prefer not to risk any issues. You can export to miniseed later.
44 44  
45 -GPS is best set to cycle mode (e.g. once per hour) instead of constant "always on". The clock drift on these are almost nil even if there is no sync at all, so it's best to conserve power.
36 += Best Practices and Guide =
46 46  
47 -Bluetooth (BD3C-5 only) should be turned OFF to conserve power.
38 +== Install ==
48 48  
49 -We recommend that the 16HR-3C be set to a gain of 24db for passive experiments and no higher than 250 Hz sampling rate unless there is an explicit reason to do so. The BD3C-5 should be set to a gain of 6db (which is the maximum allowed) for passive experiments (or 0 db if active).
40 +Logbook is required (used again for pick up & metadata creation)
50 50  
51 -{{info}}
52 -**Note that any applied instrument gain must be removed when exporting (e.g. to miniseed) after your deploy, **otherwise amplitudes will be a factor of either 15.84893192 (24db) or 2 (6db) too high!
53 -{{/info}}
42 +- station name
54 54  
55 -= **Fieldwork Preparation** =
44 +- lat / long
56 56  
57 -(% class="box warningmessage" %)
58 -(((
59 -**INVEST IN FAST EXTERNAL HARD DRIVES – DO NOT LET THIS BE THE LIMITATION OF DATA HARVESTING**
46 +- team members
60 60  
61 -**Assume ~~1 Tb of storage for both raw and exported data per 50 nodes @ 250 Hz & 30 days. One node recording at 250 Hz for 30 days tends to create about 3 Gb of miniseed data.**
48 +- date and local time
62 62  
63 -**We have had good experience with the 4Tb Samsung T7 Shield drives.**
64 -)))
50 +- SN of sensor
65 65  
66 -== Magnets ==
52 +- notes on site
67 67  
68 -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).
54 +Place nodes in thick (“landfill biodegradable”) plastic bags in the hole
69 69  
70 -== Animal-Proofing ==
56 +Take compass measurement away from node and fences [make sure to adjust inclination angle]
71 71  
72 -We have experienced interference from animals (foxes, dogs, goats) digging up and carrying nodes off for tens or hundreds of metres. It is helpful to minimise human and food smells (particularly on the rope handles) when working in areas where this is a risk. Or, wipe down affected nodes with 50-80% methylated spirits if extensive handling can not be avoided.
58 +Take many photos from the site from different angles 
73 73  
74 -If you come to collect your node and it is missing~-~- LOOK FOR IT! It may not have gotten far. We have found dozens of nodes by spending 15 minutes looking for them.
60 +Add a precise site description to the notes such as distances and orientations from landmarks 
75 75  
76 -= **Installation** =
62 +It will be very helpful in locating the instrument if you place a flag next to it, preferably in a color other than green or yellow.
77 77  
78 -(% class="box infomessage" %)
79 -(((
80 -**Field logs are a critical component of fieldwork and this is especially the case for large N nodal deploys. Take notes!**
81 -)))
64 +Make a mark (digital) of the instrument's location using a GPS device. Record the location both in your paper notes and on the GPS device.
82 82  
83 -== 1. Logbook documentation ==
66 +Download the GPS (Garmin) file to a laptop and share drive to share with other GPS devices
84 84  
85 -(((
86 -**Essential Details** for field logs:
68 +Share photos in a shared location (Google photos, OneDrive, Dropbox, etc), but most useful are those added to a Google Maps/Earth location
87 87  
88 -* Station name
89 -* Latitude, longitude, elevation
90 -* Names of team members present
91 -* Date and both local & UTC time of installation/removal
92 -* Serial number (SN) of the TOP HALF of the sensor (if a BD3C-5, there is only one serial number)
93 -* 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)
70 +Create metadata .xml file
94 94  
95 -[[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!
96 96  
97 -== 2. Node Placement ==
98 -)))
73 +== Removing/Demob ==
99 99  
100 -**Site Analysis**:
75 +Download and then use the GPS file to locate the node 
101 101  
102 -* **Take compass measurements away from the sensor as it will affect your measurement.**
103 -* Take photographs from various angles to document the site setup thoroughly.
104 -* Include a detailed site description in your notes
77 +Use Google Maps / Google Earth to create a kmz file that can then be imported onto your phone.  
105 105  
106 -== 3. GPS Considerations ==
107 107  
108 -(% class="wikigeneratedid" %)
109 -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.
80 +Upload photos of the site
110 110  
111 -== 4. Visibility and Location Marking ==
82 +- station name
112 112  
113 -**Flag Placement**: Position a flag, preferably in a bright color (avoid green or yellow), near the instrument to aid in its future location.
84 +- latitude
114 114  
115 -**GPS Marking**:
86 +- longitude
116 116  
117 -* Use a GPS device to mark the instrument's exact location.
118 -* Record this location in both your paper notes and the GPS device.
88 +- elevation
119 119  
120 -== (% style="color:inherit; font-family:inherit; font-size:max(18px, min(20px, 14.4444px + 0.462963vw))" %)5. Charge Time, Pre-Deployment & Post-Deployment(%%) ==
90 +* SN of sensor – SN of battery (optional)
91 +* Site notes and name of location (e.g. Richards garden, Te Mini steam field eastern side)
121 121  
122 -* **Charging Duration**: Both types of nodes take approximately 6-8 hours to fully charge from a flat state.
123 -* **Pre-Deployment Charging**:
124 -** Although the nodes hold their charge well, it's beneficial to give them a "top up" charge before deployment.
93 +Upload photos into Google Earth and on a shared drive
125 125  
126 -* **Operational Duration**:
127 -** 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.
95 +Before removing the instrument have your compass, tape, marker, pen, clipboard, logbook and compass ready (in tote bag!). 
128 128  
129 -* **Post-Retrieval Charging**:
130 -** After retrieval, charge the instruments to about 50-60% (indicated by ORANGE LED) unless they are to be immediately re-deployed or transported.
131 -* **State of Charge (SoC) for Storage**:
132 -** Maintain a battery charge level of around 50-60% (i.e., ORANGE) for storage.
133 -** This charge level is recommended to prevent battery damage, and should be checked every six months.
134 -** Nodes should //__not be stored at full-charge (GREEN), or 0-charge (RED).__//
135 -** Storage at 0-charge damages lithium batteries**.**
136 -* **SoC for Transport:**
137 -** Charge levels for transport will be advised by the freighter. The required SoC will depend on volume and transport method (air, land, sea).
97 +Write the station name and the instrument’s serial number, along with 'D' and 'C' and ‘R’, each next to a box to indicate 'download' and 'charge'. Stick this label to the top of the instrument.
138 138  
139 -(((
140 -== 6. Data Sharing and Metadata Creation ==
141 -)))
99 +Take a photo of the entire setup node with the label on it + compass 
142 142  
143 -**GPS Data**:
101 +Use existing field logbook to note time, SN and station name plus any notes – including any issues with orientation or level or anything else
144 144  
145 -* Ensure you have __carefully documented__ precise lat/lon locations for each station.
146 146  
147 -**Photo Sharing**:
104 +== Charging ==
148 148  
149 -* It is strongly encouraged to take pictures of each site and upload these to a shared platform (OneDrive, Dropbox, etc.).
106 +Clean node prior to charging and harvesting the data
150 150  
151 -**Metadata File**:
108 +Remove battery (and spike) from the sensor by twisting the spike part of the instrument
152 152  
153 -* 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.
110 +Set 16 nodes into the charging box (spikes up)
154 154  
155 -== 7. Additional Best Practices ==
112 +Red lights on the box next to the batteries will come on and remain a steady red light while charging. This will change to orange, then to green, then to flashing green when fully charged.
156 156  
157 -* **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.
114 +This is a good time to check the "C" box on your temporary labels to mark that the unit has been charged
158 158  
159 -----
160 -
161 -= **Seismic Station Demobilization and Documentation** =
162 -
163 -1. (((
164 -**Preparation for Demobilization**:
165 -
166 -* Before starting the demobilization process, ensure you have a compass, tape, marker, pen, masking tape, clipboard, logbook, and compass ready in your tote bag.
167 -)))
168 -1. (((
169 -**Locating the instrument**:
170 -
171 -* Use the downloaded GPS file to accurately locate the node for demobilization.
172 -* Import this KMZ file onto your phone for easy reference and location tracking.
173 -* Utilize Google Maps or Google Earth to create a KMZ file of the station’s location.
174 -)))
175 -1. (((
176 -**Labeling Instruments for Demobilization**:
177 -
178 -* Write the station name and the instrument’s serial number on a masking tape label to apply to the top of the node.
179 -* Add markers 'D' (for download), 'C' (for charge), and ‘R’ (for removal) next to checkboxes on the label.
180 -* Affix this label to the top of the instrument to avoid confusion during the charging and downloading data.
181 -)))
182 -1. (((
183 -**Photographing the Setup Node**:
184 -
185 -* Take a photo of the entire setup node with the __//label//__ and __//compass visible//__.
186 -* This photo serves as a final record of the instrument’s condition and orientation at the time of removal.
187 -)))
188 -1. (((
189 -**Logging Demobilization Details**:
190 -
191 -* Use the field logbook to note the time of demobilization, serial numbers, and station name.
192 -* Record any observations or issues related to the instrument’s orientation, level, or any other relevant factors.
193 -)))
194 -1. (((
195 -**Final Checks and Equipment Removal**:
196 -
197 -* Before physically removing the instrument, double-check that all necessary data has been downloaded and all photos and notes have been taken.
198 -* Carefully dismantle and pack the equipment, ensuring that all components are accounted for and securely stored for transport.
199 -
200 200  
201 201  )))
202 202  
203 -[[image:1706153556166-231.jpeg||data-xwiki-image-style-alignment="center" height="345" width="460"]]
204 204  
205 -----
206 -
207 -= **Charging Procedure for Seismic Nodes** =
208 -
209 -(((
210 -== 1. Preparation for Charging: ==
211 -
212 -* 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.
213 -)))
214 -
215 -(((
216 -== 2. Disassembling the Node: ==
217 -
218 -* For the IGU-16HR, remove the battery section (bottom half) from the sensor by unscrewing the spike section counter-clockwise.
219 -)))
220 -
221 -(((
222 -== 3. Setting Nodes in the Charging Box: ==
223 -
224 -* Connect to a safe indoor power supply, and turn on (red rocker switch).
225 -* Charging will begin automatically when nodes are inserted in the charging rack.
226 -* Place IGU-16HR battery sections upside-down in the rack, oriented with the terminal connectors.
227 -)))
228 -
229 -(((
230 -== 4. Monitoring the Charging Process: ==
231 -
232 -* Lights adjacent to the batteries will illuminate, indicating that charging is underway.
233 -* 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.
234 -)))
235 -
236 -(((
237 -== 5. Updating Charge Status: ==
238 -
239 -* 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.
240 -* This step is crucial for tracking the charging status of multiple units, especially when handling a large number of nodes.
241 -)))
242 -
243 -[[IGU 16-HRcharger (left) and harvester (right)>>image:1705195933422-337.png||data-xwiki-image-style-alignment="center" height="299" width="530"]]
244 -
245 -
246 -
247 -
248 -{{{
249 - }}}
250 -
251 -----
252 -
253 -= **Downloading and Converting Seismic Data to MiniSeed Format** =
254 -
255 -(% class="wikigeneratedid" %)
256 -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]]
257 -
258 -== Connection tips: ==
259 -
260 -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:
261 -
262 -* Place the node on the harvester gently, then firmly press it down onto the pins.
263 -* 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.
264 -* 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.
265 -* 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!
266 -
267 -
268 -
269 -== Node Registration and Software Setup ==
270 -
271 -1. (((
272 -**Registering Nodes in the System**:
273 -
274 -* To begin, register the nodes in the system so the software can recognize them.
275 -* Navigate to the installation folder of “SmartSoloApps SoloLite”.
276 -* Right-click on deviceconfig.exe and choose “run as an administrator”. Save the file to the “deviceconfig” directory (refer to the snapshot below).
277 -* To avoid double registration, replace the file each time you register a new node.
278 -)))
279 -1. (((
280 -**Creating a New Project in SoloLite**:
281 -
282 -* Open the “SoloLite” software.
283 -* Go to “File” and create a new project. Don't worry about finding the exact 16 nodes used in script writing.
284 -* Ignore the settings for seismic recordings in the subsequent window. Resetting instruments (e.g., sampling rate, gain) requires reprogramming via script.
285 -)))
286 -
287 -== File structure ==
288 -
289 -There are essentially three main folders where relevant PROSPECT and PROJECT DATA is stored. Individual projects will be found as subfolders in these.
290 -
291 -=== SOLOLITE ===
292 -
293 -This folder stores SoloLite config files and parameters. Nothing too important stored here, you can always start over and re-create this.
294 -
295 -=== DCCDATA ===
296 -
297 -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.
298 -
299 -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)//
300 -
301 -Then in the SoloLite software, go to tools > Reanalyze Seismic Data
302 -
303 -=== SOLODATA ===
304 -
305 -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.
306 -
307 -
308 -== Data Downloading Process ==
309 -
310 -1. (((
311 -**Initiating Data Download**:
312 -
313 -* Once a new project is created, the Data Transfer View panel will display connected nodes with details like series number and data size.
314 -* If “Prospect not matched” appears, it simply means the new project doesn’t match the original programming project. This is not a concern.
315 -* Select all nodes and right-click to “force download”. This starts the download process.
316 -* Completed downloads will appear as new folders in the Downloaded Data panel.
317 -)))
318 -1. (((
319 -**Exporting Data in Readable Format**:
320 -
321 -* Go to the “Tool” menu and select “export seismic data”.
322 -* Tailor other parameters to personal preference and ensure "Sample Interval" matches the setting used during node reset.
323 -* Click “prepare” followed by “run” to start reformatting. Monitor this process in the small panel at the bottom left.
324 -* (% class="box warningmessage" %)
325 -(((
326 -* **Ensure to export data as "COUNTS" (int32), not "mV" (float). This is critical!**
327 -
328 -* **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.**
329 -)))
330 -)))
331 -
332 -== Smart Solo IGU-16HR Polarity Notice ==
333 -
334 -See [[5Hz Node Polarity Issues>>https://auspass.edu.au/xwiki/bin/view/Data/AusPass%20Data/#HSmartSoloNodePolarityIssues]] for discussion. If data is headed to AusPass, we prefer to invert the IGU-16HR channel data manually rather than in the SoloLite software or inverting the response metadata.
335 -
336 -**The BD3C-5 data does not require any sort of polarity inversion.**
337 -
338 -== 18 Leap Second bug ==
339 -
340 -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.
341 -
342 -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.
343 -
344 -{{code language="none"}}
345 -<?xml version="1.0" encoding="UTF-8"?>
346 -<config>
347 - <leapsecond>
348 - <interval>
349 - <start_time>2017-01-01#00:00:00</start_time>
350 - <end_time>2999-12-31#23:59:59</end_time>
351 - <second>18</second>
352 - </interval>
353 - <interval>
354 - <start_time>1970-01-01#00:00:00</start_time>
355 - <end_time>2017-01-01#00:00:00</end_time>
356 - <second>17</second>
357 - </interval>
358 - </leapsecond>
359 - <GPS_distance_threshold_degree>
360 - 4e-5
361 - </GPS_distance_threshold_degree>
362 -</config>
363 -{{/code}}
364 -
365 -
366 -== Handling Nodes During Download ==
367 -
368 -1. (((
369 -**Monitoring Download Indicators**:
370 -
371 -* During download, green lights on nodes will blink, and associated red lights on the rack will flash.
372 -* Disconnect nodes properly before unplugging anything.
373 -* Be cautious: if the laptop enters sleep mode, the download will pause.
374 -)))
375 -1. (((
376 -//**Investment in Storage Hardware**~://
377 -
378 -* (% class="box warningmessage" %)
379 -(((
380 -* **Use fast external hard drives to avoid limitations in data harvesting.**
381 -
382 -* **Recommended specifications: USB-C, USB 3.0, and 4+ Tb of space.**
383 -* **The USB type for the harvester is TYPE-A, the typical normal rectangular shape.**
384 -)))
385 -)))
386 -1. (((
387 -**Metadata and Time Settings**:
388 -
389 -* Ensure all metadata is saved with the file.
390 -* 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.
391 -)))
392 -1. (((
393 -**Finalizing the Download**:
394 -
395 -* After downloading, mark the //"D"// box on your temporary labels to indicate completion.
396 -
397 -
398 -)))
399 -
400 -[[image:1706153266647-145.png||data-xwiki-image-style-alignment="center" height="340" width="603"]]
401 -
402 -
403 -
404 -[[Caption>>image:1705195543887-977.png||data-xwiki-image-style-alignment="center" height="534" width="632"]]
405 -
406 -
407 -
408 -
409 -[[Caption>>image:1705195543890-537.png||data-xwiki-image-style-alignment="center" height="397" width="665"]]
410 -
411 -
412 -
413 -[[Caption>>image:1705195543891-334.png||data-xwiki-image-style-alignment="center" height="379" width="650"]]
414 -
415 -
416 -
417 -[[image:1705195543898-365.png||data-xwiki-image-style-alignment="center" height="467" width="674"]]
418 -
419 -----
420 -
421 -= Instrument Response =
422 -
423 -We are aware that there are various different published responses for these instruments and trust very few of them. One has to be careful with how polarity is handled between groups as well, and if one is working in integer counts (the ANSIR default) or mV (unclear why anyone would use this as it makes file sizes enormous). The response information published below is in **counts** and seems to fit well in huddle tests. Note that the response is the same for all channels and all units (e.g. there are no bespoke calibrations!), all appear to be sample rate insensitive, and the IGU data has been inverted (multiplied by -1) as described here: [[5Hz Node Polarity Issues>>https://auspass.edu.au/xwiki/bin/view/Data/AusPass%20Data/#HSmartSoloNodePolarityIssues]]
424 -
425 -== IGU 16HR-3C ==
426 -
427 - '16HR3C': {'poles':[(-22.211059+22.217768j), (-22.211059-22.217768j)],
428 - 'zeros':[0j, 0j],
429 - 'gain':1,
430 - 'sensitivity': 257019225.55108312}
431 -
432 -[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:IGU16_Z_huddle.png]]
433 -
434 -[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:IGU16_N_huddle.png]]
435 -
436 -== IGU 16-1C ==
437 -
438 -The 1C nodes seem to have the same response as the 3-channel IGU-16HR-3C (above), however the response posted at IRIS-NRL seems to imply that there is no poles and zeros information (e.g. a flat/linear response). This is 100% not so.
439 -
440 -[[IGU-16 1C, X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter. Seems to be same response as IGU-16HR-3C.>>image:IGU16_1C_Z_huddle.png]]
441 -
442 -== BD3C-5 ==
443 -
444 - 'BD3C': {'poles':[(-1720.4+0j), (-1.2+0.9j), (-1.2-0.9j)],
445 - 'zeros':[(14164+0j), (-7162+0j), 0j, 0j],
446 - 'gain':1.69726e-05,
447 - 'sensitivity': 702651512.6046528}
448 -
449 -[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:BD3C_Z_huddle.png]]
450 -
451 -[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:BD3C_N_huddle.png]]
452 -
453 -(% class="wikigeneratedid" %)
454 -Below the corner frequency 0.2 Hz (i.e. 5 seconds) the response still does a good job, but may need to be dialed in a bit. We are looking into this.
455 -
456 -
457 -[[BD3C 0.1 to 5 Hz bandpass>>image:BD3C_Z_huddle.0.1.png]]
458 -
459 -[[BD3C 0.1 to 5 Hz bandpass>>image:BD3C_N_huddle.0.1.png]]
460 -
461 -== IGU-16 Horizontal noise & how to avoid ==
462 -
463 -The** 5 Hz nodes** are susceptible to horizontal noise due to the placement of geophones in the units, **but this can be mitigated by completely burying the units flush with the ground.** In the below example, the node was set on the floor of our basement set on its plastic carrying case support. As such the amount of horizontal noise noticeably increases above ~~ 10Hz.
464 -
465 -[[IGU-16HR-3C Power spectrum huddle test vs a CMG-6TD (S1) and TC120/Centaur combo. The N and E channels have excess noise above 10Hz due to "sticking up" out of the ground.>>image:IGU16_spectrum.png]]
466 -
467 -(% class="wikigeneratedid" %)
468 -The BD3C-5 nodes do not have this issue:
469 -
470 -[[BD3C-5 test, as above. There is no additional noise on the horizontal channels.>>image:BD3C_psd.png]]
471 -
472 -= **Cleaning** =
473 -
474 -When assembled, the nodes are water resistant but not submersible. They can handle a good spray and wipe-down. A stiff plastic brush is helpful to reach areas between the metal spikes on the bottom.
475 -
476 -= **Weights (for shipping)** =
477 -
478 -The weights of bags of nodes, as well as data harvesters and node chargers, are listed below:
479 -
480 -1 bag + 6*IGU-16HR nodes: 18 kg
481 -
482 -1*IGU-16HR data harvester: 21.5 kg
483 -
484 -1*IGU-16HR charger: 26.3 kg
485 -
486 -1*BD3C-5 charger (with and without 16 cables): 21 kg / 14.5 kg
487 -
488 -1 case + 5*BD3C-5 nodes: 22 kg (aggregate battery weight <5kg, 168Wh)
489 -
490 -1 case + 6*BD3C-5 nodes: 25 kg (aggregate battery weight >5kg, 168Wh)
491 -)))
492 -
493 493  (% class="col-xs-12 col-sm-4" %)
494 494  (((
495 -(% class="box" %)
496 -(((
497 -**Contents**
498 -
122 +{{box title="**Contents**"}}
499 499  {{toc/}}
124 +{{/box}}
500 500  
501 -
502 -)))
126 +{{box title="= SmartSolo [[BD3C-5>>https://smartsolo.com/cp-4.html]] =
503 503  
504 -(% class="box" %)
505 -(((
506 -= SmartSolo [[BD3C-5>>url:https://smartsolo.com/cp-4.html]] =
128 += [[image:Trillium compact posthole.jpg]] =
507 507  
508 -[[image:Smartsolo IGU BD3C 5 (2).jpg]]
130 +|(% style=~"width:115px~" %)**Sensitivity **|(% style=~"width:112px~" %)5 seconds
131 +|(% style=~"width:139px~" %)**Size (Diameter x Height)**|(% style=~"width:88px~" %)? x ? cm
132 +|(% style=~"width:139px~" %)**Weight**|(% style=~"width:88px~" %)? kg"}}
133 +|(% style="width:228px" %)**Battery**|(% style="width:183px" %)lithium (30 days)
134 +
135 +{{/box}}
509 509  
510 -[[image:smartsolo.jpg]]
137 +{{box title="= SmartSolo [[IGU-16HR>>https://smartsolo.com/cp-3.html]] =
511 511  
512 -|(% style="width:189px" %)**Frequency Band**|(% style="width:221px" %)5 Seconds to 150Hz
513 -|(% style="width:189px" %)**Sensitivity**|(% style="width:221px" %)200 V/m/s
514 -|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)Φ158 x160mm(H)
515 -|(% style="width:189px" %)**Weight**|(% style="width:221px" %)2.8 kg
516 -|(% style="width:189px" %)**Data Storage**|(% style="width:221px" %)64 Gb
517 -|(% style="width:189px" %)**Battery**|(% style="width:221px" %)(((
518 -Lithium-ion battery contained in equipment (168.84 Wh)
139 += [[image:Trillium compact posthole.jpg]] =
519 519  
520 -UN3481 PI967 S1
521 -)))
522 -)))
523 -
524 -(% class="box" %)
525 -(((
526 -= SmartSolo [[IGU-16HR>>url:https://smartsolo.com/cp-3.html]]3C =
527 -
528 -[[image:smartsolo node.jpg]]
529 -
530 -[[image:smartsolo node 2.jpg]]
531 -
532 -|(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 1652Hz
533 -|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)76.7 V/m/s
534 -|(% style="width:187px" %)**Size (with spike)**|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm(H)
535 -|(% style="width:187px" %)**Weight**|(% style="width:224px" %)2.4 kg
536 -|(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)64 Gb
537 -|(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((
538 -Lithium-ion battery contained in equipment (96.48 Wh)
539 -
540 -UN3481 PI967 S2
541 -)))
542 -)))
543 -
544 -(% class="box" %)
545 -(((
141 +|(% style=~"width:115px~" %)**Sensitivity **|(% style=~"width:112px~" %)0.2 seconds (5 Hz)
142 +|(% style=~"width:139px~" %)**Size (Diameter x Height)**|(% style=~"width:88px~" %)? x ? cm
143 +|(% style=~"width:139px~" %)**Weight**|(% style=~"width:88px~" %)? kg"}}
144 +|(% style="width:228px" %)**Battery**|(% style="width:183px" %)lithium (30 days)
546 546  
146 +{{/box}}
547 547  
548 -= SmartSolo [[IGU-16>>url:https://smartsolo.com/cp-3.html]]1C =
549 549  
550 -
551 -[[image:Screenshot 2025-08-01 161027.png]]
552 -
553 -|(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 413Hz
554 -|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)80 V/m/s
555 -|(% style="width:187px" %)**Size (without spike)**|(% style="width:224px" %)95mm(L) × 103mm(W) × 118mm(H)
556 -|(% style="width:187px" %)**Weight**|(% style="width:224px" %)1.1 kg
557 -|(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)8 Gb
558 -|(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((
559 -Lithium-ion battery contained in equipment (38.48 Wh)
560 -
561 -UN3481 PI967 S2
149 +
562 562  )))
563 563  )))
564 -
565 -(% class="box" %)
566 -(((
567 -= SmartSolo BD3C-16 Portable Battery Charger =
568 -
569 -[[image:20250729_125049.jpg]]
570 -
571 -|**Dimensions (LxHxW)**|558 x 357 x 300mm
572 -|**Input rating**|100-210V - 50/60Hz
573 -|**Power**|1000W
574 -|**Weight**|14.5 kg
575 -|**Weight with cables**|21 kg
576 -)))
577 -
578 -(% class="box" id="HSmartSoloBD3C-16PortableBatteryCharger" %)
579 -(((
580 -= SmartSolo IGU-16 Portable Data Harvester =
581 -
582 -[[image:20250729_124747.jpg]]
583 -
584 -|**Dimensions (LxHxW)**|625 x 500 x 366mm
585 -|**Input rating**|100-210V - 50/60Hz
586 -|**Power**|100W
587 -|**Weight**|21.5 - 24 kg
588 -|**Capacity**|16 nodes
589 -|**Download Speed**|20MB/sec/slot
590 -)))
591 -
592 -(% class="box" %)
593 -(((
594 -= SmartSolo IGU-16 Portable Battery Charger =
595 -
596 -[[image:20250729_124644.jpg]]
597 -
598 -|**Dimensions (LxHxW)**|625 x 500 x 366 mm
599 -|**Input rating**|100-210V - 50/60 Hz
600 -|**Power**|640 W
601 -|**Weight**|26.3 kg
602 -|**Capacity**|16 nodes
603 -)))
604 -
605 -(% class="box" %)
606 -(((
607 -= SmartSolo BD3C-5 Carry Case =
608 -
609 -[[image:20250729_124957.jpg]]
610 -
611 -
612 -|**Dimensions (LxHxW)**|590 x 225 x 405 mm
613 -|**Weight**|8.2 kg
614 -|**Capacity**|6 nodes
615 -)))
616 -
617 -(% class="box" %)
618 -(((
619 -= SmartSolo IGU-16 3C Carry Bag =
620 -
621 -[[image:20250729_124502.jpg]]
622 -
623 -|**Dimensions (LxHxW)**|230 x 340 x 310mm
624 -|**Weight**|(((
625 -3.6kg (empty)
626 -
627 -18.0kg (full)
628 -)))
629 -|**Capacity**|6 nodes
630 -)))
631 -
632 -(% class="box" %)
633 -(((
634 -= SmartSolo IGU-16 1C Carry Bag =
635 -
636 -[[image:20250729_124558.jpg]]
637 -
638 -|**Dimensions (LxHxW)**|225 x 200 x 550mm
639 -|**Weight**|
640 -|**Capacity**|8 nodes
641 -)))
642 -)))
643 -)))
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
5Hz_node_programming.labels.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.KB
Size
... ... @@ -1,1 +1,0 @@
1 -109.8 KB
Content
5S_node_programming.labels.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.KB
Size
... ... @@ -1,1 +1,0 @@
1 -114.2 KB
Content
BB_programming.labels.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -111.5 KB
Content
BD3C_N_huddle.0.1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -72.1 KB
Content
BD3C_N_huddle.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -72.1 KB
Content
BD3C_Z_huddle.0.1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -52.1 KB
Content
BD3C_Z_huddle.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -52.1 KB
Content
BD3C_psd.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -73.7 KB
Content
IGU16_1C_Z_huddle.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -72.3 KB
Content
IGU16_N_huddle.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -65.7 KB
Content
IGU16_Z_huddle.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -67.4 KB
Content
IGU16_spectrum.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -65.0 KB
Content
SP_programming.labels.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -106.7 KB
Content
Screenshot 2025-08-01 161027.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -82.8 KB
Content
Smartsolo 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