Skip to Content
Last modified by KB on 2025/12/04 12:33
From version 22.1
edited by robert
on 2024/01/23 12:51
Change comment: There is no comment for this version
To version 90.1
edited by KB
on 2025/12/04 12:31
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -SmartSolo Nodes
1 +SmartSolo Node Seismometers
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.robert
1 +XWiki.KB
Content
... ... @@ -2,53 +2,110 @@
2 2  (((
3 3  (% class="col-xs-12 col-sm-8" %)
4 4  (((
5 -= **Node Setup** =
5 += **Node Types** =
6 6  
7 -Short term (~~30 day) battery powered nodes
7 +ANSIR supply two types of three-channel nodes, and one type of one-channel node:
8 8  
9 -== **Pre-Fieldwork Preparation** ==
9 +* **SmartSolo IGU 16HR 3C (5 Hz Short Period)**
10 +* **SmartSolo BD3C-5 (5 Second Broadband)**
11 +* **SmartSolo IGU 16 1C (5 Hz Short Period, single channel)**
10 10  
13 +The three-channel nodes have a 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.
14 +
11 11  (% class="box infomessage" %)
12 12  (((
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 feasibility for IGU 16 (<100Wh) and BD3C (168Wh) nodes. Advice will be sought from freighters on a case-by-case basis while they implement new guidelines.
18 +)))
19 +
20 +----
21 +
22 += **Programming Defaults** =
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.
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 +
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"]]
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.
31 +
32 +Note that the samplerate is instead given in sample spacing, in milliseconds. 4 ms = 250 Hz, 1 ms = 1000 Hz, 10 ms = 100 Hz, ad nauseam.
33 +
34 +Be sure to set the channel types to Seismic and the gain appropriately. For active source (i.e. explosions) you can leave the gain at 0, but for passive experiments some gain is purported to be helpful (although we have found this to be somewhat negligible). We can confirm that 6db for the broadband nodes and 24db for the short period works well.
35 +
36 +If you want recording to begin immediately, ensure that begin date is in the past by at least a few days. If you prefer to have a timed turn-on, then set the times as needed. **Be warned that recording will not begin until a GPS lock is achieved, so if you set it to a future turn-on but bury it too deeply, it may not record!**
37 +
38 +In newer versions of the software there is a "power consumption" setting.. we are no sure what this does exactly, but the manual says it gives life a "boost" at the expense of about 3 db of resolution. Until this can be quantified a bit better it is not recommended.
39 +
40 +Storage type can be DLD (proprietary) or Miniseed. We assume the software works best with their proprietary format so prefer not to risk any issues. You can export to miniseed later.
41 +
42 +GPS is best set to cycle mode (e.g. once per hour) instead of constant "always on". The clock drift on these are almost nil even if there is no sync at all, so it's best to conserve power.
43 +
44 +Bluetooth (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 +
13 13  (% class="box warningmessage" %)
14 14  (((
15 15  **INVEST IN FAST EXTERNAL HARD DRIVES – DO NOT LET THIS BE THE LIMITATION OF DATA HARVESTING**
16 16  
17 -**Plan on 1 Tb to store ALL data for 50 nodes @ 250 Hz and a single ~~30 day occupation**
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.**
18 18  )))
19 -)))
20 20  
63 +== Magnets ==
64 +
65 +If you are short on magnets, you may find it easier and a lot cheaper to buy magnets in Australia. AMF Magnetics is a good retailer, and [[this item>>https://magnet.com.au/collections/shop?q=23012B]] seems to work well. It is also advantageous to use smaller magnets and store/carry them individually in your back pocket (as well as stick them to various places in your field vehicle, etc).
66 +
67 +== Animal-Proofing ==
68 +
69 +We have experienced 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 +
21 21  = **Installation** =
22 22  
23 -=== **1- Logbook documentation** ===
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 +)))
24 24  
78 +== 1. Logbook documentation ==
79 +
25 25  (((
26 -**Essential Details**: Record the following in a logbook:
81 +**Essential Details** for field logs:
27 27  
28 28  * Station name
29 -* Latitude and longitude
84 +* Latitude, longitude, elevation
30 30  * Names of team members present
31 -* Date and local time of installation
32 -* Serial number (SN) of the sensor
33 -* Detailed notes on the site conditions and setup
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)
34 34  
35 -=== **2- Node Placement** ===
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 ==
36 36  )))
37 37  
38 -**Protection**: Place nodes inside thick, landfill biodegradable plastic bags for environmental protection.
95 +**Protection**: Place nodes inside (landfill) biodegradable bags to minimize cleaning and cross-site soil contamination.
39 39  
40 40  **Site Analysis**:
41 41  
42 -* Conduct compass measurements away from the node and metallic structures, adjusting for inclination angle.
43 -* Take multiple photographs from various angles to document the site setup thoroughly.
44 -* 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)
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
45 45  
46 -=== **3- GPS Considerations** ===
103 +== 3. GPS Considerations ==
47 47  
48 48  (% class="wikigeneratedid" %)
49 -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.
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.
50 50  
51 -=== **4- Visibility and Location Marking** ===
108 +== 4. Visibility and Location Marking ==
52 52  
53 53  **Flag Placement**: Position a flag, preferably in a bright color (avoid green or yellow), near the instrument to aid in its future location.
54 54  
... ... @@ -57,242 +57,319 @@
57 57  * Use a GPS device to mark the instrument's exact location.
58 58  * Record this location in both your paper notes and the GPS device.
59 59  
60 -=== (% style="color:inherit; font-family:inherit; font-size:max(18px, min(20px, 14.4444px + 0.462963vw))" %)**5- Charge Time, Pre-Deployment & Post-Deployment**(%%) ===
117 +== (% style="color:inherit; font-family:inherit; font-size:max(18px, min(20px, 14.4444px + 0.462963vw))" %)5. Charge Time, Pre-Deployment & Post-Deployment(%%) ==
61 61  
62 62  * **Charging Duration**: Both types of nodes take approximately 6-8 hours to fully charge from a flat state.
63 63  * **Pre-Deployment Charging**:
64 -** Although the nodes hold their charge well, it's beneficial to give them a "top up" charge right before deployment.
121 +** Although the nodes hold their charge well, it's beneficial to give them a "top up" charge before deployment.
65 65  
66 66  * **Operational Duration**:
67 -** When recording at 250 Hz, with GPS on and Bluetooth disabled, the instruments are expected to last about 30 days per charge cycle.
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.
68 68  
69 69  * **Post-Retrieval Charging**:
70 -** Do not store the instruments with completely drained batteries.
71 -** After retrieval, charge the instruments to about 50-60% (indicated as "orange" level) for optimal battery health.
72 -
127 +** After retrieval, charge the instruments to about 50-60% (indicated as "orange" level) unless they are to be immediately re-deployed.
73 73  * **Storage and Shipping Charge Level**:
74 -** Maintain a battery charge level of around 50-60% for both storage and shipping purposes.
129 +** Maintain a battery charge level of around 50-60% (e.g. "orange") for both storage and shipping purposes.
75 75  ** 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.**
76 76  
77 -=== ===
133 +(((
134 +== 6. Data Sharing and Metadata Creation ==
135 +)))
78 78  
79 -=== ===
80 -
81 -=== **6- Data Sharing and Metadata Creation** ===
82 -
83 83  **GPS Data**:
84 84  
85 -* Download the GPS file to a laptop.
86 -* Share this file on a drive accessible to all team members for uniform understanding of node locations.
139 +* Ensure you have documented precise lat/lon locations for each station and **DOCUMENTED THIS CAREFULLY**
87 87  
88 88  **Photo Sharing**:
89 89  
90 -* Upload site photos to a shared platform (OneDrive, Dropbox, etc.).
91 -* Integrating photos into Google Maps or Google Earth can be particularly beneficial for easy location referencing.
143 +* It is strongly encouraged to take pictures of each site and upload these to a shared platform (OneDrive, Dropbox, etc.).
92 92  
93 93  **Metadata File**:
94 94  
95 -* Create a metadata XML file for each node, which is essential for data organisation and future reference.
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.
96 96  
97 -=== **7- Additional Best Practices** ===
149 +== 7. Additional Best Practices ==
98 98  
99 -* **Environmental Responsibility**: Ensure that the node placement and the materials used are environmentally responsible and adhere to local regulations.
100 -* **Training and Familiarisation**: Make sure all team members are adequately trained in using the GPS devices, compass, and other equipment to ensure consistent and accurate data collection.
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.
101 101  
102 -* (((
103 -==== **Keeping the Instruments Clean** ====
104 -)))
105 -* (((
106 -Use a (**landfill**, not //compost//) degradable bag when installing to keep the instrument clean. This will save you many hours of time cleaning them in preparation for their return. [[Here is a video>>url:http://auspass.edu.au/field/bd3c_removal.mp4]] demonstrating its effectiveness.
107 -)))
153 +----
108 108  
109 -= =
155 += **Seismic Station Demobilization and Documentation** =
110 110  
111 -= SmartSolo IGU 16HR 3C (5 Hz) Short Period Node =
157 +1. (((
158 +**Preparation for Demobilization**:
112 112  
113 -blahblah
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**:
114 114  
115 -== Sub-paragraph ==
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**:
116 116  
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**:
117 117  
118 -== ==
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**:
119 119  
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**:
120 120  
121 -= Smart Solo BD3C-5 (5 second) Broad-Band Node =
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.
122 122  
123 -Lorem
194 +
195 +)))
124 124  
125 -[[image:1705196270090-364.png]]
197 +[[image:1706153556166-231.jpeg||data-xwiki-image-style-alignment="center" height="345" width="460"]]
126 126  
199 +----
127 127  
128 -== GPS Considerations ==
201 += **Charging Procedure for Seismic Nodes** =
129 129  
130 -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.
203 +(((
204 +== 1. Preparation for Charging: ==
131 131  
132 -= Keeping the Instruments Clean =
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 +)))
133 133  
134 -Use a (**landfill**, not //compost//) degradable bag when installing to keep the instrument clean. This will save you many hours of time cleaning them in preparation for their return. [[Here is a video>>url:http://auspass.edu.au/field/bd3c_removal.mp4]] demonstrating its effectiveness.
209 +(((
210 +== 2. Disassembling the Node: ==
135 135  
212 +* For the IGU-16HR, remove the battery (bottom half) from the sensor. This is done by unscrewing the spikes counter-clockwise.
213 +)))
136 136  
137 -= Charge Time, Instrument Life, and Charge During Storage & Shipping =
215 +(((
216 +== 3. Setting Nodes in the Charging Box: ==
138 138  
139 -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.
218 +* Place 1-16 IGU-16HR battery components upside-down into the charger, assuring they are oriented properly.
219 +)))
140 140  
141 -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.
221 +(((
222 +== 4. Monitoring the Charging Process: ==
142 142  
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 +)))
143 143  
144 -= Best Practices and Guide =
228 +(((
229 +== 5. Updating Charge Status: ==
145 145  
146 -== Install ==
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 +)))
147 147  
148 -Logbook is required (used again for pick up & metadata creation)
235 +[[IGU 16-HRcharger (left) and harvester (right)>>image:1705195933422-337.png||data-xwiki-image-style-alignment="center" height="299" width="530"]]
149 149  
150 -- station name
151 151  
152 -- lat / long
153 153  
154 -- team members
155 155  
156 -- date and local time
240 +{{{
241 + }}}
157 157  
158 -- SN of sensor
243 +----
159 159  
160 -- notes on site
245 += **Downloading and Converting Seismic Data to MiniSeed Format** =
161 161  
162 -Place nodes in thick (“landfill biodegradable”) plastic bags in the hole
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]]
163 163  
164 -Take compass measurement away from node and fences [make sure to adjust inclination angle]
250 +== Connection tips: ==
165 165  
166 -Take many photos from the site from different angles 
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:
167 167  
168 -Add a precise site description to the notes such as distances and orientations from landmarks 
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!
169 169  
170 -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.
171 171  
172 -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.
173 173  
174 -Download the GPS (Garmin) file to a laptop and share drive to share with other GPS devices
261 +== Node Registration and Software Setup ==
175 175  
176 -Share photos in a shared location (Google photos, OneDrive, Dropbox, etc), but most useful are those added to a Google Maps/Earth location
263 +1. (((
264 +**Registering Nodes in the System**:
177 177  
178 -Create metadata .xml file
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**:
179 179  
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 +)))
180 180  
181 -== Removing/Demob ==
279 +== File structure ==
182 182  
183 -Download and then use the GPS file to locate the node 
281 +There are essentially three main folders where relevant PROSPECT and PROJECT DATA is stored. Individual projects will be found as subfolders in these.
184 184  
185 -Use Google Maps / Google Earth to create a kmz file that can then be imported onto your phone.  
283 +=== SOLOLITE ===
186 186  
285 +This folder stores SoloLite config files and parameters. Nothing too important stored here, you can always start over and re-create this.
187 187  
188 -Upload photos of the site  
287 +=== DCCDATA ===
189 189  
190 -- station name
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.
191 191  
192 -- latitude
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)//
193 193  
194 -- longitude
293 +Then in the SoloLite software, go to tools > Reanalyze Seismic Data
195 195  
196 -- elevation
295 +=== SOLODATA ===
197 197  
198 -* SN of sensor – SN of battery (optional)
199 -* Site notes and name of location (e.g. Richards garden, Te Mini steam field eastern side) 
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.
200 200  
201 -Upload photos into Google Earth and on a shared drive
202 202  
203 -Before removing the instrument have your compass, tape, marker, pen, clipboard, logbook and compass ready (in tote bag!). 
300 +== Data Downloading Process ==
204 204  
205 -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. When dealing with dozens or hundreds of these you WILL start to mix them up after a while! Having an easy visual cue keep them sorted will save you a great deal of confusion later on.
302 +1. (((
303 +**Initiating Data Download**:
206 206  
207 -Take a photo of the entire setup node with the label on it + compass 
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**:
208 208  
209 -Use existing field logbook to note time, SN and station name plus any notes – including any issues with orientation or level or anything else
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!**
210 210  
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 +)))
211 211  
212 -== Charging ==
324 +== Smart Solo Z Polarity bug (SP nodes ONLY!) ==
213 213  
214 -Clean node prior to charging and harvesting the data
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 3 Z channel data manually rather than in the SoloLite software or inverting the response metadata. **The BD3C-5 data does not require a polarity inversion.**
215 215  
216 -Remove battery (and spike) from the sensor by twisting the spike part of the instrument
328 +== 18 Leap Second bug ==
217 217  
218 -Set 16 nodes into the charging box (spikes up)
330 +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 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.
219 219  
220 -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.
332 +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.
221 221  
222 -This is a good time to check the "C" box on your temporary labels to mark that the unit has been charged
334 +{{code language="none"}}
335 +<?xml version="1.0" encoding="UTF-8"?>
336 +<config>
337 + <leapsecond>
338 + <interval>
339 + <start_time>2017-01-01#00:00:00</start_time>
340 + <end_time>2999-12-31#23:59:59</end_time>
341 + <second>18</second>
342 + </interval>
343 + <interval>
344 + <start_time>1970-01-01#00:00:00</start_time>
345 + <end_time>2017-01-01#00:00:00</end_time>
346 + <second>17</second>
347 + </interval>
348 + </leapsecond>
349 + <GPS_distance_threshold_degree>
350 + 4e-5
351 + </GPS_distance_threshold_degree>
352 +</config>
353 +{{/code}}
223 223  
224 -[[IGU 16-HRcharger (left) and harvester (right)>>image:1705195933422-337.png||data-xwiki-image-style-alignment="center"]]
225 225  
356 +== Handling Nodes During Download ==
226 226  
358 +1. (((
359 +**Monitoring Download Indicators**:
227 227  
228 -== Downloading and Converting Data to MiniSeed ==
361 +* During download, green lights on nodes will blink, and associated red lights on the rack will flash.
362 +* Disconnect nodes properly before unplugging anything.
363 +* Be cautious: if the laptop enters sleep mode, the download will pause.
364 +)))
365 +1. (((
366 +//**Investment in Storage Hardware**~://
229 229  
368 +* (% class="box warningmessage" %)
369 +(((
370 +* **Use fast external hard drives to avoid limitations in data harvesting.**
230 230  
231 -The first thing to do is to register the nodes in the system, so the software can recognize them. To do this, go to the folder where the “SmartSoloApps SoloLite” was installed. Then right-click the deviceconfig.exe program to “run as an administrator” and save the file to the directory of “deviceconfig” (snapshot below). Note that to avoid registering the same node twice, you can simply replace the file each time you do the registration.
372 +* **Recommended specifications: USB-C, USB 3.0, and 4+ Tb of space.**
373 +* **The USB type for the harvester is TYPE-A, the typical normal rectangular shape.**
374 +)))
375 +)))
376 +1. (((
377 +**Metadata and Time Settings**:
232 232  
233 -[[image:1705195543887-977.png]]
379 +* Ensure all metadata is saved with the file.
380 +* 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.
381 +)))
382 +1. (((
383 +**Finalizing the Download**:
234 234  
385 +* After downloading, mark the //"D"// box on your temporary labels to indicate completion.
235 235  
236 -Then open the “SoloLite” software, and just go to “File” to make a new project. In this case, you do not need to find the exact 16 nodes that were grouped for script writing. Do not worry about the settings for the seismic recordings for the next window to pop up, as the only way to reset the instruments (e.g., sampling rate, gain etc) is to write script to re-program them.
387 +
388 +)))
237 237  
238 -[[image:1705195543890-537.png||data-xwiki-image-style-alignment="center"]]
390 +[[image:1706153266647-145.png||data-xwiki-image-style-alignment="center" height="340" width="603"]]
239 239  
240 240  
241 -Once you create the new project, your Data Transfer View panel on the bottom right of the window will show these nodes that have properly connected to the data harvest, including series number, data size etc. It is okay if the “Prospect not matched”, which simply means the project you just created does not match the one you made to program them. Simply select all these nodes, and right click to “force download”, which will initiate the downloading process. Once they are done, you will see new folders created for each slot at your Downloaded Data panel on the top left of the window.
242 242  
243 -[[image:1705195543891-334.png||data-xwiki-image-style-alignment="center"]]
394 +[[Caption>>image:1705195543887-977.png||data-xwiki-image-style-alignment="center" height="534" width="632"]]
244 244  
245 -At this stage, it means that the raw DLL data of the recording has been downloaded successfully to your local machine. To output data in readable format, such as SAC or miniSEED, click the “Tool” menu and select “export seismic data”. The parameters here should be straightforward to set and tailored to personal reference.
246 246  
247 -(% class="box warningmessage" %)
248 -(((
249 -**Please make sure that data is exported as "COUNTS" and NOT "mV"!**
250 -)))
251 251  
252 -(% class="box warningmessage" %)
253 -(((
254 -**Furthermore you must also set "Remove Gain" to the same decibel gain setting that was set during programming! ANU always set this to 18 db (double check) for all types of nodes.**
255 -)))
256 256  
257 -A list of ANU group preferred parameters can be found at the end of this session. One thing to note is that the “Sample Interval” must be set exactly to this used to reset the nodes. Once you are done with the setting, click “prepare” before “run”. If everything works correctly, you should see the reformatting process from the small panel on the bottom left of this popped up window.
399 +[[Caption>>image:1705195543890-537.png||data-xwiki-image-style-alignment="center" height="397" width="665"]]
258 258  
259 -Now the data should be ready. Then you can select these data and right click to output the GPS information associated with them.
260 260  
261 -[[image:1705195543898-365.png||data-xwiki-image-style-alignment="center"]]
262 262  
263 -When downloading, all the green lights on the nodes will blink. The associated red lights on the rack will flash when it is downloading, and make sure to disconnect the nodes before you unplug anything. Be careful: if the laptop goes to sleep, the download process will pause.
403 +[[Caption>>image:1705195543891-334.png||data-xwiki-image-style-alignment="center" height="379" width="650"]]
264 264  
265 -(% class="box infomessage" %)
266 -(((
267 -**INVEST IN FAST EXTERNAL HARD DRIVES – DO NOT LET THIS BE THE LIMITATION OF DATA HARVESTING**. USB-C, USB 3.0, and 4+ Tb of space are highly recommended!
268 -)))
269 269  
270 -When downloading, ensure that all metadata is saved along with the file.
271 271  
272 -Start and endtime: the system will automatically find the earliest time of the data and set that as the starting time. However, you can set the time a day earlier with a sharp start of 00:00:00. In this case, all the outputted data segments will be 24 hours long starting from midnight.
407 +[[image:1705195543898-365.png||data-xwiki-image-style-alignment="center" height="467" width="674"]]
273 273  
274 -//Once downloaded, mark the "D" box on your temporary labels!//
409 +----
275 275  
276 -== Converting data ==
411 += **Cleaning** =
277 277  
278 -Check the data all have been converted to miniseed correctly 
413 +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.
279 279  
280 -– 3 files per station per day 
415 += **Weights (for shipping)** =
281 281  
282 -* Files are the same size (NOTE if having memory issues one or more of the components may have 0-1 kb)
283 -* ~~ 5 Gb / node / month
417 +The weights of bags of nodes, as well as data harvesters and node chargers, are listed below:
284 284  
285 -//Tick ‘R’ box on the node label//
419 +1 bag + 6 SP (IGU-16HR) nodes: 18 kg
286 286  
421 +1 SP (IGU-16HR) data harvester: 21.5 kg
287 287  
288 -== Cleaning ==
423 +1 SP (IGU-16HR) charger: 26.3 kg
289 289  
290 -If the nodes are placed in a thick plastic bag at the time of installation, the cleaning procedure should be straightforward. If not you have a lot of work to do before they are returned to us!
425 +1 BB (BD3C-5) charger/data harvester (with and without 16 cables): 21 kg / 14.5 kg
291 291  
292 -
427 +1 case + 5 BB (BD3C-5) nodes and 6 BB nodes: 22 kg / 25 kg
293 293  )))
294 294  
295 -
296 296  (% class="col-xs-12 col-sm-4" %)
297 297  (((
298 298  (% class="box" %)
... ... @@ -299,24 +299,11 @@
299 299  (((
300 300  **Contents**
301 301  
302 -(% class="wikitoc" %)
303 -* [[SmartSolo IGU 16HR 3C (5 Hz) Short Period Node>>path:#HSmartSoloIGU16HR3C285Hz29ShortPeriodNode]]
304 -** [[Sub-paragraph>>path:#HSub-paragraph]]
305 -** [[ >>path:#H]]
306 -* [[Smart Solo BD3C-5 (5 second) Broad-Band Node>>path:#HSmartSoloBD3C-5285second29Broad-BandNode]]
307 -** [[GPS Considerations>>path:#HGPSConsiderations]]
308 -* [[Keeping the Instruments Clean>>path:#HKeepingtheInstrumentsClean]]
309 -* [[Charge Time, Instrument Life, and Charge During Storage & Shipping>>path:#HChargeTime2CInstrumentLife2CandChargeDuringStorage26Shipping]]
310 -* [[Best Practices and Guide>>path:#HBestPracticesandGuide]]
311 -** [[Install>>path:#HInstall]]
312 -** [[Removing/Demob>>path:#HRemoving2FDemob]]
313 -** [[Charging>>path:#HCharging]]
314 -** [[Downloading and Converting Data to MiniSeed>>path:#HDownloadingandConvertingDatatoMiniSeed]]
315 -** [[Converting data>>path:#HConvertingdata]]
316 -** [[Cleaning>>path:#HCleaning]]
436 +{{toc/}}
437 +
438 +
317 317  )))
318 318  
319 -
320 320  (% class="box" %)
321 321  (((
322 322  = SmartSolo [[BD3C-5>>url:https://smartsolo.com/cp-4.html]] =
... ... @@ -327,15 +327,19 @@
327 327  
328 328  |(% style="width:189px" %)**Frequency Band**|(% style="width:221px" %)5 Seconds to 150Hz
329 329  |(% style="width:189px" %)**Sensitivity**|(% style="width:221px" %)200 V/m/s
330 -|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)158 x160mm
451 +|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)Φ158 x160mm(H)
331 331  |(% style="width:189px" %)**Weight**|(% style="width:221px" %)2.8 kg
332 332  |(% style="width:189px" %)**Data Storage**|(% style="width:221px" %)64 Gb
333 -|(% style="width:189px" %)**Battery**|(% style="width:221px" %)Li_etc XXAh
454 +|(% style="width:189px" %)**Battery**|(% style="width:221px" %)(((
455 +Lithium-ion battery contained in equipment (168.84 Wh)
456 +
457 +UN3481 PI967 S1
334 334  )))
459 +)))
335 335  
336 336  (% class="box" %)
337 337  (((
338 -= SmartSolo [[IGU-16HR>>url:https://smartsolo.com/cp-3.html]] =
463 += SmartSolo [[IGU-16HR>>url:https://smartsolo.com/cp-3.html]]3C =
339 339  
340 340  [[image:smartsolo node.jpg]]
341 341  
... ... @@ -342,13 +342,110 @@
342 342  [[image:smartsolo node 2.jpg]]
343 343  
344 344  |(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 1652Hz
345 -|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)67.7 V/m/s
346 -|(% style="width:187px" %)**Size (with spike)**|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm
347 -|(% style="width:187px" %)**Weight**|(% style="width:224px" %)2.3 kg
470 +|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)76.7 V/m/s
471 +|(% style="width:187px" %)**Size (with spike)**|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm(H)
472 +|(% style="width:187px" %)**Weight**|(% style="width:224px" %)2.4 kg
348 348  |(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)64 Gb
349 -|(% style="width:187px" %)**Battery**|(% style="width:224px" %)Li_etc XXAh
474 +|(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((
475 +Lithium-ion battery contained in equipment (96.48 Wh)
476 +
477 +UN3481 PI967 S2
350 350  )))
479 +)))
351 351  
481 +(% class="box" %)
482 +(((
352 352  
484 +
485 += SmartSolo [[IGU-16>>url:https://smartsolo.com/cp-3.html]]1C =
486 +
487 +
488 +[[image:Screenshot 2025-08-01 161027.png]]
489 +
490 +|(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 413Hz
491 +|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)80 V/m/s
492 +|(% style="width:187px" %)**Size (without spike)**|(% style="width:224px" %)95mm(L) × 103mm(W) × 118mm(H)
493 +|(% style="width:187px" %)**Weight**|(% style="width:224px" %)1.1 kg
494 +|(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)8 Gb
495 +|(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((
496 +Lithium-ion battery contained in equipment (38.48 Wh)
497 +
498 +UN3481 PI967 S2
353 353  )))
354 354  )))
501 +
502 +(% class="box" %)
503 +(((
504 += SmartSolo BD3C-16 Portable Battery Charger =
505 +
506 +[[image:20250729_125049.jpg]]
507 +
508 +|**Dimensions (LxHxW)**|558 x 357 x 300mm
509 +|**Input rating**|100-210V - 50/60Hz
510 +|**Power**|1000W
511 +|**Weight**|14.5kg
512 +|**Weight with cables**|21kg
513 +)))
514 +
515 +(% class="box" id="HSmartSoloBD3C-16PortableBatteryCharger" %)
516 +(((
517 += SmartSolo IGU-16 Portable Data Harvester =
518 +
519 +[[image:20250729_124747.jpg]]
520 +
521 +|**Dimensions (LxHxW)**|625 x 500 x 366mm
522 +|**Input rating**|100-210V - 50/60Hz
523 +|**Power**|100W
524 +|**Weight**|21.5 - 24kg
525 +|**Slots no.**|16
526 +|**Download Speed**|20MB/sec/slot
527 +)))
528 +
529 +(% class="box" %)
530 +(((
531 += SmartSolo IGU-16 Portable Battery Charger =
532 +
533 +[[image:20250729_124644.jpg]]
534 +
535 +|**Dimensions (LxHxW)**|625 x 500 x 366mm
536 +|**Input rating**|100-210V - 50/60Hz
537 +|**Power**|640W
538 +|**Weight**|26.3kg
539 +|**Slots no.**|16
540 +)))
541 +
542 +(% class="box" %)
543 +(((
544 += SmartSolo BD3C-5 Carry Case =
545 +
546 +[[image:20250729_124957.jpg]]
547 +
548 +
549 +|**Dimensions (LxHxW)**|590 x 225 x 405mm
550 +|**Weight**|8.2kg
551 +|**Slots no.**|6
552 +)))
553 +
554 +(% class="box" %)
555 +(((
556 += SmartSolo IGU-16 3C Carry Bag =
557 +
558 +[[image:20250729_124502.jpg]]
559 +
560 +|**Dimensions (LxHxW)**|230 x 340 x 310mm
561 +|**Weight**|3.6kg
562 +|**Slots no.**|6
563 +)))
564 +
565 +(% class="box" %)
566 +(((
567 += SmartSolo IGU-16 1C Carry Bag =
568 +
569 +[[image:20250729_124558.jpg]]
570 +
571 +|**Dimensions (LxHxW)**|225 x 200 x 550mm
572 +|**Weight**|
573 +|**Slots no.**|6
574 +)))
575 +)))
576 +)))
1706153266647-145.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.sima
Size
... ... @@ -1,0 +1,1 @@
1 +1.7 MB
Content
1706153354750-415.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.sima
Size
... ... @@ -1,0 +1,1 @@
1 +2.1 MB
Content
1706153556166-231.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.sima
Size
... ... @@ -1,0 +1,1 @@
1 +839.4 KB
Content
20250729_124502.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.JackD
Size
... ... @@ -1,0 +1,1 @@
1 +318.3 KB
Content
20250729_124558.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.JackD
Size
... ... @@ -1,0 +1,1 @@
1 +376.8 KB
Content
20250729_124644.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.JackD
Size
... ... @@ -1,0 +1,1 @@
1 +528.0 KB
Content
20250729_124747.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.JackD
Size
... ... @@ -1,0 +1,1 @@
1 +488.5 KB
Content
20250729_124957.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.JackD
Size
... ... @@ -1,0 +1,1 @@
1 +532.5 KB
Content
20250729_125049.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.JackD
Size
... ... @@ -1,0 +1,1 @@
1 +457.6 KB
Content
BB_programming.labels.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.robert
Size
... ... @@ -1,0 +1,1 @@
1 +111.5 KB
Content
SP_programming.labels.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.robert
Size
... ... @@ -1,0 +1,1 @@
1 +106.7 KB
Content
Screenshot 2025-08-01 161027.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.JackD
Size
... ... @@ -1,0 +1,1 @@
1 +82.8 KB
Content
example_metadata.txt
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.robert
Size
... ... @@ -1,0 +1,1 @@
1 +2.7 KB
Content
... ... @@ -1,0 +1,46 @@
1 +# AKL-HR Node Array (AHNA) code X5
2 +CITE: Name, Name, and Name. (2023). A Node Array [Data set]. International Federation of Digital Seismograph Networks. https://doi.org/10.7914/8jxr-7029
3 +
4 +#SITE START END LAT LONG ELEV SPS RECORDER S/N SENSOR S/N PROPERTY,LOCALITY,COUNTRY COMMENTS
5 +
6 +# INSTALL
7 +AKL01 20-05-2023T00:00 30-06-2023T00:00 -37.0471 175.5245 75 250 SSNODE_C 590001950 SSNODE_5S 590001950 "Te Puru,Hauraki,NZ"
8 +AKL02 20-05-2023T00:00 30-06-2023T00:00 -36.7476 175.5026 70 250 SSNODE_C 590001943 SSNODE_5S 590001943 "Coromandel Town,Hauraki,NZ"
9 +AKL03 20-05-2023T00:00 30-06-2023T00:00 -36.9694 175.5020 98 250 SSNODE_C 590002068 SSNODE_5S 590002068 "Te Mata,Hauraki,NZ"
10 +AKL05 19-05-2023T19:00 22-02-2023T00:00 -36.5996 174.3312 102 250 SSNODE_C 590001957 SSNODE_5S 590001957 "South Head South,Auckland,NZ" "site was disturbed"
11 +AKL06 19-05-2023T19:00 30-06-2023T00:00 -37.2459 175.3426 34 250 SSNODE_C 590001930 SSNODE_5S 590001930 "Back Miranda,Auckland,NZ"
12 +AKB05 02-05-2023T00:37 30-06-2023T00:00 -36.6651 175.4800 63 250 TSAWR TS085A TRILL120 4875 "Colville,Hauraki,NZ"
13 +
14 +# SERVICE 1
15 +AKL05 22-02-2023T00:00 30-06-2023T00:00 -36.5996 174.3312 102 250 SSNODE_C 590001999 SSNODE_.2S 590001999 "South Head South,Auckland,NZ" "swapped node to shortperiod"
16 +
17 +
18 +
19 +
20 +################### ANY LINE BEGINNING WITH # will be commented! Comments are good!
21 +
22 +
23 +# NOTES
24 +# the start/end time is not critical, but good to have. what IS critical are the times of instrument changes as this potentially affects response information
25 +# to mark equipment changes, add a new line with an updated start date (e.g. AKL05 above)
26 +# can use tabs or spaces, but spaces tend to look nicer. formatting ultimately doesn't matter too much so long as there is any sort of "white space" between the fields
27 +# if you don't know a serial number, put 999. if you don't know the elevation, put 0
28 +# for Nodes, put the same serial number for both Recoder and Sensor (since they are the same!)
29 +
30 +
31 +# EXAMPLE INSTRUMENT LABELS
32 +#LPR200 = ANU LPR-200 logger (beige box)
33 +#TSAWR = ANU TerraSAWR logger (yellow box)
34 +
35 +#TRILL120 = Trillium Compact 120s
36 +#TRILL20 = Trillium Compact 20s
37 +#TRILL120PH = Trillium Compact 120s PostHole
38 +#CMG6TD = Guralp 6TD
39 +#CMG3ESP = Guralp 3ESP
40 +#3DLITE = Lenarrtz 3D-LITE
41 +
42 +#SSNODE_C = output was in COUNTS (there is also SSNODE_MV, if you (accidentally!) output to millivolts etc)
43 +#SSNODE_5S = broadband (can also use SSNODE_BB)
44 +#SSNODE_.2S = shortperiod (can also use SSNODE_SP)
45 +
46 +#it doesn't matter too much what you use for equipment labels, so long as they are consistent and otherwise defined somewhere in the comments!
XWiki.XWikiRights[0]
Allow/Deny
... ... @@ -1,0 +1,1 @@
1 +Allow
Groups
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiAllGroup
Levels
... ... @@ -1,0 +1,1 @@
1 +comment
XWiki.XWikiRights[1]
Allow/Deny
... ... @@ -1,0 +1,1 @@
1 +Allow
Levels
... ... @@ -1,0 +1,1 @@
1 +comment
Users
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest