Changes for page SmartSolo Node Seismometers
Last modified by robert on 2025/08/21 13:08
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 1 removed)
-
Objects (0 modified, 0 added, 2 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -SmartSolo Node Seismometers1 +SmartSolo Nodes - Content
-
... ... @@ -7,59 +7,45 @@ 7 7 ANSIR carry two types of three-channel nodes 8 8 9 9 * **SmartSolo IGU 16HR 3C (5 Hz Short Period)** 10 -* **SmartSolo BD3C-5 (5 Second Broad band)**10 +* **SmartSolo BD3C-5 (5 Second Broad-Band)** 11 11 12 -Both have a battery capacity of around 30 days. The programming, operation and downloading procedures for both types of SmartSolo nodes are also similar. 12 +Both have a battery capacity of around 30 days. The programming, operation, and downloading procedures for both types of SmartSolo nodes are also similar. 13 13 14 + 14 14 ---- 15 15 16 16 = **Programming Defaults** = 17 17 18 - Werecommend that the SP 16HR-3C be set to a gain of 24db and no higher than 250 Hz sampling rate unlessthereisan explicitreason to do so.TheBD3C-5should be set to again of6db(whichis themaximumallowed).These arewhatwe useforournal experiments.19 +ANU recommends that the SP 16HR-3C be set to a gain of 24db and no higher than 250 Hz sampling rate. The BD3C-5 should be set to a gain of 6db (maximum allowed). These are what we use for our internal experiments. **Note that this gain must be removed when exporting to miniseed, **otherwise amplitudes will be a factor of either 15.84893192 (24db) or 2 (6db) too high. We also recommend disabling bluetooth to increase battery life, and to enable "FIFO" mode just in case old data is still present on the units and you run out of space (although it is unlikely you will go over 64 Gb for one deploy). If using the "timed turn-on" option, please be aware that **the units will not begin recording until they have acquired a GPS lock**, which may nor occur if they are buried too deeply or have very poor sky view. 19 19 20 -**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. 21 21 22 22 = **Fieldwork Preparation** = 23 23 24 +(% class="box infomessage" %) 25 +((( 24 24 (% class="box warningmessage" %) 25 25 ((( 26 26 **INVEST IN FAST EXTERNAL HARD DRIVES – DO NOT LET THIS BE THE LIMITATION OF DATA HARVESTING** 27 27 28 28 **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.** 29 - 30 -**We have had good experience with the 4Tb Samsung T7 Shield drives.** 31 31 ))) 32 +))) 32 32 33 -== Magnets == 34 - 35 -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). 36 - 37 -== Animal-Proofing == 38 - 39 -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. 40 - 41 41 = **Installation** = 42 42 43 -(% class="box infomessage" %) 44 -((( 45 -**Field logs are a critical component of fieldwork and this is especially the case for large N nodal deploys. Take notes!** 46 -))) 36 +== **1- Logbook documentation** == 47 47 48 -== 1. Logbook documentation == 49 - 50 50 ((( 51 -**Essential Details** forfieldlogs:39 +**Essential Details**: Record the following in a logbook: 52 52 53 53 * Station name 54 -* Latitude ,longitude, elevation42 +* Latitude and longitude 55 55 * Names of team members present 56 -* Date and bothlocal& UTCtime of installation/removal57 -* Serial number (SN) of the TOP HALF of thesensor(if a BD3C-5, there is only one serial number)58 -* 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)44 +* Date and local time of installation 45 +* Serial number (SN) of the sensor 46 +* Detailed notes on the site conditions and setup 59 59 60 -[[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! 61 - 62 -== 2. Node Placement == 48 +== **2- Node Placement** == 63 63 ))) 64 64 65 65 **Protection**: Place nodes inside (landfill) biodegradable bags to minimize cleaning and cross-site soil contamination. ... ... @@ -67,15 +67,15 @@ 67 67 **Site Analysis**: 68 68 69 69 * **Take compass measurements away from the sensor as it will affect your measurement.** 70 -* Take photographs from various angles to document the site setup thoroughly. 71 -* Include a detailed site description in your notes 56 +* Take multiple photographs from various angles to document the site setup thoroughly. 57 +* Include a detailed site description in your notes, specifying distances and orientations from nearby landmarks (e.g. Richards garden, Te Mini steam field eastern side) 72 72 73 -== 3 .GPS Considerations ==59 +== **3- GPS Considerations** == 74 74 75 75 (% class="wikigeneratedid" %) 76 76 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. 77 77 78 -== 4 .Visibility and Location Marking ==64 +== **4- Visibility and Location Marking** == 79 79 80 80 **Flag Placement**: Position a flag, preferably in a bright color (avoid green or yellow), near the instrument to aid in its future location. 81 81 ... ... @@ -84,7 +84,7 @@ 84 84 * Use a GPS device to mark the instrument's exact location. 85 85 * Record this location in both your paper notes and the GPS device. 86 86 87 -== (% style="color:inherit; font-family:inherit; font-size:max(18px, min(20px, 14.4444px + 0.462963vw))" %)5 .Charge Time, Pre-Deployment & Post-Deployment(%%) ==73 +== (% style="color:inherit; font-family:inherit; font-size:max(18px, min(20px, 14.4444px + 0.462963vw))" %)**5- Charge Time, Pre-Deployment & Post-Deployment**(%%) == 88 88 89 89 * **Charging Duration**: Both types of nodes take approximately 6-8 hours to fully charge from a flat state. 90 90 * **Pre-Deployment Charging**: ... ... @@ -98,10 +98,10 @@ 98 98 * **Storage and Shipping Charge Level**: 99 99 ** Maintain a battery charge level of around 50-60% (e.g. "orange") for both storage and shipping purposes. 100 100 ** This charge level is recommended to prevent battery damage and is safe for transportation. 101 -** Nodes should not be stored fully charged, and **they should especially not be stored with 0 charge as this damages lithium batteries.**87 +** Nodes should not be stored fully charged, and it **they should especially not be stored with 0 charge.** 102 102 103 103 ((( 104 -== 6 .Data Sharing and Metadata Creation ==90 +== **6- Data Sharing and Metadata Creation** == 105 105 ))) 106 106 107 107 **GPS Data**: ... ... @@ -114,12 +114,20 @@ 114 114 115 115 **Metadata File**: 116 116 117 -* Create and organize metadata accordingto the[[ANU metadata standardtxt 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) andthetimes they were deployed can lead to station mix-ups.103 +* Create and organize metadata via the ANU metadata standard (~*~*add example) 118 118 119 -== 7 .Additional Best Practices ==105 +== **7- Additional Best Practices** == 120 120 107 +* **Environmental Responsibility**: Ensure that the node placement and the materials used are environmentally responsible and adhere to local regulations. 121 121 * **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. 122 122 110 +* ((( 111 +==== **Keeping the Instruments Clean** ==== 112 +))) 113 +* ((( 114 +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. 115 +))) 116 + 123 123 ---- 124 124 125 125 = **Seismic Station Demobilization and Documentation** = ... ... @@ -171,25 +171,25 @@ 171 171 = **Charging Procedure for Seismic Nodes** = 172 172 173 173 ((( 174 -== 1. Preparation for Charging: == 168 +== **1. Preparation for Charging**: == 175 175 176 176 * 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. 177 177 ))) 178 178 179 179 ((( 180 -== 2. Disassembling the Node: == 174 +== **2. Disassembling the Node**: == 181 181 182 182 * For the IGU-16HR, remove the battery (bottom half) from the sensor. This is done by unscrewing the spikes counter-clockwise. 183 183 ))) 184 184 185 185 ((( 186 -== 3. Setting Nodes in the Charging Box: == 180 +== **3. Setting Nodes in the Charging Box**: == 187 187 188 188 * Place 1-16 IGU-16HR battery components upside-down into the charger, assuring they are oriented properly. 189 189 ))) 190 190 191 191 ((( 192 -== 4. Monitoring the Charging Process: == 186 +== **4. Monitoring the Charging Process**: == 193 193 194 194 * 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. 195 195 * 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. ... ... @@ -196,7 +196,7 @@ 196 196 ))) 197 197 198 198 ((( 199 -== 5. Updating Charge Status: == 193 +== **5. Updating Charge Status**: == 200 200 201 201 * 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. 202 202 * This step is crucial for tracking the charging status of multiple units, especially when handling a large number of nodes. ... ... @@ -213,7 +213,7 @@ 213 213 214 214 = **Downloading and Converting Seismic Data to MiniSeed Format** = 215 215 216 -== Node Registration and Software Setup == 210 +== **Node Registration and Software Setup** == 217 217 218 218 1. ((( 219 219 **Registering Nodes in the System**: ... ... @@ -231,7 +231,7 @@ 231 231 * Ignore the settings for seismic recordings in the subsequent window. Resetting instruments (e.g., sampling rate, gain) requires reprogramming via script. 232 232 ))) 233 233 234 -== Data Downloading Process == 228 +== **Data Downloading Process** == 235 235 236 236 1. ((( 237 237 **Initiating Data Download**: ... ... @@ -249,13 +249,13 @@ 249 249 * Click “prepare” followed by “run” to start reformatting. Monitor this process in the small panel at the bottom left. 250 250 * (% class="box warningmessage" %) 251 251 ((( 252 -* **Ensure to export data as "COUNTS" (int32), not "mV"(float).This is critical!**246 +* **Ensure to export data as "COUNTS", not "mV".** 253 253 254 -* **Set "Remove Gain" to the same decibel gain as during programming .By default ANU sets this to 24dbfor short period nodes(ascalingfactor of 15.848932), and 6db (a factor of 2.0) for broadband nodes.**248 +* **Set "Remove Gain" to the same decibel gain as during programming** **(by default ANU sets this to 24db (a factor of 15.848932).** 255 255 ))) 256 256 ))) 257 257 258 -== Handling Nodes During Download == 252 +== **Handling Nodes During Download** == 259 259 260 260 1. ((( 261 261 **Monitoring Download Indicators**: ... ... @@ -272,7 +272,6 @@ 272 272 * **Use fast external hard drives to avoid limitations in data harvesting.** 273 273 274 274 * **Recommended specifications: USB-C, USB 3.0, and 4+ Tb of space.** 275 -* **The USB type for the harvester is TYPE-A, the typical normal rectangular shape.** 276 276 ))) 277 277 ))) 278 278 1. ((( ... ... @@ -312,21 +312,9 @@ 312 312 313 313 = **Cleaning** = 314 314 315 - When still connected, the nodes are water resistant (don't submergethem!) and can handle a good spray/ wipedown. A strong, non-wire brushis helpful to reachareas between the metal spikeson thebottom.308 +**Procedure for Seismic Nodes:** 316 316 317 -= **Weights (for shipping)** = 318 - 319 -The weights of bags of nodes, as well as data harvesters and node chargers, are listed below: 320 - 321 -1 bag + 6 SP (IGU-16HR) nodes: 18 kg 322 - 323 -1 SP (IGU-16HR) data harvester: 21.5 kg 324 - 325 -1 SP (IGU-16HR) charger: 26.3 kg 326 - 327 -1 BB (BD3C-5) charger/data harvester (with and without 16 cables): 21 kg / 14.5 kg 328 - 329 -1 case + 5 BB (BD3C-5) nodes and 6 BB nodes: 22 kg / 25 kg 310 +* If the nodes are placed in a sturdy 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! 330 330 ))) 331 331 332 332 (% class="col-xs-12 col-sm-4" %) ... ... @@ -353,12 +353,8 @@ 353 353 |(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)158 x160mm 354 354 |(% style="width:189px" %)**Weight**|(% style="width:221px" %)2.8 kg 355 355 |(% style="width:189px" %)**Data Storage**|(% style="width:221px" %)64 Gb 356 -|(% style="width:189px" %)**Battery**|(% style="width:221px" %)((( 357 -Lithium-ion battery contained in equipment (168.84 Wh) 358 - 359 -UN3481 PI967 S1 337 +|(% style="width:189px" %)**Battery**|(% style="width:221px" %)Li_etc XXAh 360 360 ))) 361 -))) 362 362 363 363 (% class="box" %) 364 364 ((( ... ... @@ -373,12 +373,8 @@ 373 373 |(% style="width:187px" %)**Size (with spike)**|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm 374 374 |(% style="width:187px" %)**Weight**|(% style="width:224px" %)2.4 kg 375 375 |(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)64 Gb 376 -|(% style="width:187px" %)**Battery**|(% style="width:224px" %)((( 377 -Lithium-ion battery contained in equipment (96.48 Wh) 378 - 379 -UN3481 PI967 S2 353 +|(% style="width:187px" %)**Battery**|(% style="width:224px" %)Lithium ion XXAh 380 380 ))) 381 -))) 382 382 383 383 384 384 )))
- 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!
- 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