Skip to Content
Last modified by robert on 2025/08/21 13:08
From version 8.6
edited by robert
on 2024/01/14 13:01
Change comment: There is no comment for this version
To version 59.2
edited by robert
on 2025/07/16 15:55
Change comment: allow view right for XWiki.XWikiAllGroup

Summary

Details

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