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, 9 removed)
-
Objects (0 modified, 0 added, 2 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -SmartSolo Node Seismometers1 +SmartSolo Nodes - Content
-
... ... @@ -2,96 +2,69 @@ 2 2 ((( 3 3 (% class="col-xs-12 col-sm-8" %) 4 4 ((( 5 -= **Node Types** = 5 += **SmartSolo Node Types and Procedures** = 6 6 7 - ANSIR carrytwotypesof three-channel nodes7 +**SmartSolo Node Variants:** 8 8 9 -* **SmartSolo IGU 16HR 3C (5 Hz Short Period )**10 -* **SmartSolo BD3C-5 (5 Second Broadband)**9 +* **SmartSolo IGU 16HR 3C (5 Hz) Short Period Node** 10 +* **SmartSolo BD3C-5 (5-second) Broad-Band Node** 11 11 12 - Bothhavea battery capacityof around30days. Theprogramming,operation and downloading procedures for both types of SmartSolo nodes are alsosimilar.12 +The installation, demobilization, and data downloading procedures for both types of SmartSolo nodes – the IGU 16HR 3C Short Period Node and the BD3C-5 Broad-Band Node – are largely similar. 13 13 14 +This uniformity in process ensures ease of operation across different node types, allowing for a streamlined approach in fieldwork and data management. 15 + 14 14 ---- 15 15 16 -= ** ProgrammingDefaults** =18 += **Node Setup** = 17 17 18 - The nodesmust be programmedintheSoloLitesoftwarepriortose.Screenshotsfor theshort period16HR-3C andbroadbandBDC3-5 areshown withour recommendedparameters.20 +Short term (~~30 day) battery powered nodes. The default gain should be 24 db for the 16HR-3C and 6 db for the BD3C-5 19 19 20 -[[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"]] 21 21 22 - [[BD3C-5 (broadband node) programmingscreenset at 250 hz. Ensurethat thehighlightedareasare set!>>image:BB_programming.labels.png||alt="BD3C-5programming screen"]]23 +~*~**this needs to be reformatted 23 23 24 - FIFO(first in, first out) data modes safest as this will overwriteold data in case you forgotto clearthe storage. At<= 250 hz you can fit 4++ monthsof data on these, shouldn't be an issue.25 +== **Pre-Fieldwork Preparation** == 25 25 26 -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. 27 - 28 -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. 29 - 30 -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 output to miniseed later. 31 - 32 -GPS mode is best in cycle mode (e.g. once per hour) instead of constant. The clock drift on these are almost nil even if there is no sync at all, so it's best to conserve power. 33 - 34 -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). 35 - 36 -**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. 37 - 38 -= **Fieldwork Preparation** = 39 - 27 +(% class="box infomessage" %) 28 +((( 40 40 (% class="box warningmessage" %) 41 41 ((( 42 42 **INVEST IN FAST EXTERNAL HARD DRIVES – DO NOT LET THIS BE THE LIMITATION OF DATA HARVESTING** 43 43 44 -**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.** 45 - 46 -**We have had good experience with the 4Tb Samsung T7 Shield drives.** 33 +**Plan on 1 Tb to store ALL data for 50 nodes @ 250 Hz and a single ~~30 day occupation** 47 47 ))) 35 +))) 48 48 49 -== Magnets == 50 - 51 -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). 52 - 53 -== Animal-Proofing == 54 - 55 -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. 56 - 57 57 = **Installation** = 58 58 59 -(% class="box infomessage" %) 60 -((( 61 -**Field logs are a critical component of fieldwork and this is especially the case for large N nodal deploys. Take notes!** 62 -))) 39 +=== **1- Logbook documentation** === 63 63 64 -== 1. Logbook documentation == 65 - 66 66 ((( 67 -**Essential Details** forfieldlogs:42 +**Essential Details**: Record the following in a logbook: 68 68 69 69 * Station name 70 -* Latitude ,longitude, elevation45 +* Latitude and longitude 71 71 * Names of team members present 72 -* Date and bothlocal& UTCtime of installation/removal73 -* Serial number (SN) of the TOP HALF of thesensor(if a BD3C-5, there is only one serial number)74 -* 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)47 +* Date and local time of installation 48 +* Serial number (SN) of the sensor 49 +* Detailed notes on the site conditions and setup 75 75 76 -[[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! 77 - 78 -== 2. Node Placement == 51 +=== **2- Node Placement** === 79 79 ))) 80 80 81 -**Protection**: Place nodes inside (landfill)biodegradable bagstominimizecleaningandcross-sitesoilcontamination.54 +**Protection**: Place nodes inside thick, landfill biodegradable plastic bags for environmental protection. 82 82 83 83 **Site Analysis**: 84 84 85 -* **Takecompass measurements away from thesensorasitwillaffectyourmeasurement.**86 -* Take photographs from various angles to document the site setup thoroughly. 87 -* Include a detailed site description in your notes 58 +* Conduct compass measurements away from the node and metallic structures, adjusting for inclination angle. 59 +* Take multiple photographs from various angles to document the site setup thoroughly. 60 +* 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) 88 88 89 -== 3 .GPS Considerations ==62 +=== **3- GPS Considerations** === 90 90 91 91 (% class="wikigeneratedid" %) 92 -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. **Thesenodeswill not start recording without attaining a GPS lock** and repeated attempts will excessively drain the battery.65 +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. 93 93 94 -== 4 .Visibility and Location Marking ==67 +=== **4- Visibility and Location Marking** === 95 95 96 96 **Flag Placement**: Position a flag, preferably in a bright color (avoid green or yellow), near the instrument to aid in its future location. 97 97 ... ... @@ -100,50 +100,63 @@ 100 100 * Use a GPS device to mark the instrument's exact location. 101 101 * Record this location in both your paper notes and the GPS device. 102 102 103 -== (% style="color:inherit; font-family:inherit; font-size:max(18px, min(20px, 14.4444px + 0.462963vw))" %)5 .Charge Time, Pre-Deployment & Post-Deployment(%%) ==76 +=== (% style="color:inherit; font-family:inherit; font-size:max(18px, min(20px, 14.4444px + 0.462963vw))" %)**5- Charge Time, Pre-Deployment & Post-Deployment**(%%) === 104 104 105 105 * **Charging Duration**: Both types of nodes take approximately 6-8 hours to fully charge from a flat state. 106 106 * **Pre-Deployment Charging**: 107 -** Although the nodes hold their charge well, it's beneficial to give them a "top up" charge before deployment. 80 +** Although the nodes hold their charge well, it's beneficial to give them a "top up" charge right before deployment. 108 108 109 109 * **Operational Duration**: 110 -** 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.83 +** When recording at 250 Hz, with GPS on and Bluetooth disabled, the instruments are expected to last about 30 days per charge cycle. 111 111 112 112 * **Post-Retrieval Charging**: 113 -** After retrieval, charge the instruments to about 50-60% (indicated as "orange" level) unless they are to be immediately re-deployed. 86 +** Do not store the instruments with completely drained batteries. 87 +** After retrieval, charge the instruments to about 50-60% (indicated as "orange" level) for optimal battery health. 88 + 114 114 * **Storage and Shipping Charge Level**: 115 -** Maintain a battery charge level of around 50-60% (e.g. "orange")for both storage and shipping purposes.90 +** Maintain a battery charge level of around 50-60% for both storage and shipping purposes. 116 116 ** This charge level is recommended to prevent battery damage and is safe for transportation. 117 -** Nodes should not be stored fully charged, and **they should especially not be stored with 0 charge as this damages lithium batteries.** 118 118 119 -((( 120 -== 6. Data Sharing and Metadata Creation == 93 +=== === 94 + 95 +* ((( 96 +=== **6- Data Sharing and Metadata Creation** === 121 121 ))) 122 122 123 123 **GPS Data**: 124 124 125 -* Ensure you have documented precise lat/lon locations for each station and **DOCUMENTED THIS CAREFULLY** 101 +* Download the GPS file to a laptop. 102 +* Share this file on a drive accessible to all team members for uniform understanding of node locations. 126 126 127 127 **Photo Sharing**: 128 128 129 -* It is strongly encouraged to take pictures of each site and upload these to a shared platform (OneDrive, Dropbox, etc.). 106 +* Upload site photos to a shared platform (OneDrive, Dropbox, etc.). 107 +* Integrating photos into Google Maps or Google Earth can be particularly beneficial for easy location referencing. 130 130 131 131 **Metadata File**: 132 132 133 -* Create a ndorganizemetadataaccordingtothe[[ANU metadatastandardtxt file>>attach:example_metadata.txt]].Thisisgoingto be particularlyimportant ifyou arereusing nodesatdifferent sites... not documenting the serialnumbers(of the **top half** ofthe node)and thetimes they weredeployed canlead to station mix-ups.111 +* Create a metadata XML file for each node, which is essential for data organisation and future reference. 134 134 135 -== 7 .Additional Best Practices ==113 +=== **7- Additional Best Practices** === 136 136 137 -* **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. 115 +* **Environmental Responsibility**: Ensure that the node placement and the materials used are environmentally responsible and adhere to local regulations. 116 +* **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. 138 138 118 +* ((( 119 +==== **Keeping the Instruments Clean** ==== 120 +))) 121 +* ((( 122 +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. 123 +))) 124 + 139 139 ---- 140 140 141 -= **Seismic Station Demobilization and Documentation** = 127 +=== **Seismic Station Demobilization and Documentation** === 142 142 143 143 1. ((( 144 144 **Preparation for Demobilization**: 145 145 146 -* Before starting the demobilization process, ensure you have a compass, tape, marker, pen, masking tape,clipboard, logbook, and compass ready in your tote bag.132 +* Before starting the demobilization process, ensure you have a compass, tape, marker, pen, clipboard, logbook, and compass ready in your tote bag. 147 147 ))) 148 148 1. ((( 149 149 **Locating the instrument**: ... ... @@ -155,7 +155,7 @@ 155 155 1. ((( 156 156 **Labeling Instruments for Demobilization**: 157 157 158 -* Write the station name and the instrument’s serial number on a masking tapelabelto apply to the top of the node.144 +* Write the station name and the instrument’s serial number on a label. 159 159 * Add markers 'D' (for download), 'C' (for charge), and ‘R’ (for removal) next to checkboxes on the label. 160 160 * Affix this label to the top of the instrument to avoid confusion during the charging and downloading data. 161 161 ))) ... ... @@ -184,36 +184,32 @@ 184 184 185 185 ---- 186 186 187 -= **Charging Procedure for Seismic Nodes** = 173 +=== **Charging Procedure for Seismic Nodes** === 188 188 189 -((( 190 - == 1.Preparation for Charging:==175 +1. ((( 176 +**Preparation for Charging**: 191 191 192 192 * 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. 193 193 ))) 180 +1. ((( 181 +**Disassembling the Node**: 194 194 195 -((( 196 -== 2. Disassembling the Node: == 197 - 198 -* For the IGU-16HR, remove the battery (bottom half) from the sensor. This is done by unscrewing the spikes counter-clockwise. 183 +* Carefully remove the battery and the spike from the sensor. This is typically done by twisting the spike part of the instrument to release these components. 199 199 ))) 185 +1. ((( 186 +**Setting Nodes in the Charging Box**: 200 200 201 -((( 202 -== 3. Setting Nodes in the Charging Box: == 203 - 204 -* Place 1-16 IGU-16HR battery components upside-down into the charger, assuring they are oriented properly. 188 +* Place up to 16 nodes into the charging box, arranging them with the spikes pointing upwards. This configuration is essential for proper connection and efficient charging. 205 205 ))) 190 +1. ((( 191 +**Monitoring the Charging Process**: 206 206 207 -((( 208 -== 4. Monitoring the Charging Process: == 209 - 210 -* 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. 211 -* 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. 193 +* Once the nodes are set in the charging box and the charging process begins, red lights adjacent to the batteries will illuminate. These lights indicate that charging is underway. 194 +* 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. 212 212 ))) 196 +1. ((( 197 +**Updating Charge Status**: 213 213 214 -((( 215 -== 5. Updating Charge Status: == 216 - 217 217 * 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. 218 218 * This step is crucial for tracking the charging status of multiple units, especially when handling a large number of nodes. 219 219 ))) ... ... @@ -227,9 +227,9 @@ 227 227 228 228 ---- 229 229 230 -= **Downloading and Converting Seismic Data to MiniSeed Format** = 212 +=== **Downloading and Converting Seismic Data to MiniSeed Format** === 231 231 232 -== Node Registration and Software Setup == 214 +==== **Node Registration and Software Setup** ==== 233 233 234 234 1. ((( 235 235 **Registering Nodes in the System**: ... ... @@ -247,7 +247,7 @@ 247 247 * Ignore the settings for seismic recordings in the subsequent window. Resetting instruments (e.g., sampling rate, gain) requires reprogramming via script. 248 248 ))) 249 249 250 -== Data Downloading Process == 232 +==== **Data Downloading Process** ==== 251 251 252 252 1. ((( 253 253 **Initiating Data Download**: ... ... @@ -265,13 +265,13 @@ 265 265 * Click “prepare” followed by “run” to start reformatting. Monitor this process in the small panel at the bottom left. 266 266 * (% class="box warningmessage" %) 267 267 ((( 268 -* **Ensure to export data as "COUNTS" (int32), not "mV"(float).This is critical!**250 +* **Ensure to export data as "COUNTS", not "mV".** 269 269 270 -* **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.**252 +* **Set "Remove Gain" to the same decibel gain as during programming** **(by default ANU sets this to 24db (a factor of 15.848932).** 271 271 ))) 272 272 ))) 273 273 274 -== Handling Nodes During Download == 256 +==== **Handling Nodes During Download** ==== 275 275 276 276 1. ((( 277 277 **Monitoring Download Indicators**: ... ... @@ -288,7 +288,6 @@ 288 288 * **Use fast external hard drives to avoid limitations in data harvesting.** 289 289 290 290 * **Recommended specifications: USB-C, USB 3.0, and 4+ Tb of space.** 291 -* **The USB type for the harvester is TYPE-A, the typical normal rectangular shape.** 292 292 ))) 293 293 ))) 294 294 1. ((( ... ... @@ -326,23 +326,13 @@ 326 326 327 327 ---- 328 328 329 -= **Cleaning** = 310 +=== **Cleaning** === 330 330 331 - 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.312 +**Procedure for Seismic Nodes:** 332 332 333 - =**Weights(for shipping)**=314 +* 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! 334 334 335 -The weights of bags of nodes, as well as data harvesters and node chargers, are listed below: 336 - 337 -1 bag + 6 SP (IGU-16HR) nodes: 18 kg 338 - 339 -1 SP (IGU-16HR) data harvester: 21.5 kg 340 - 341 -1 SP (IGU-16HR) charger: 26.3 kg 342 - 343 -1 BB (BD3C-5) charger/data harvester (with and without 16 cables): 21 kg / 14.5 kg 344 - 345 -1 case + 5 BB (BD3C-5) nodes and 6 BB nodes: 22 kg / 25 kg 316 += = 346 346 ))) 347 347 348 348 (% class="col-xs-12 col-sm-4" %) ... ... @@ -351,11 +351,24 @@ 351 351 ((( 352 352 **Contents** 353 353 354 -{{toc/}} 355 - 356 - 325 +(% class="wikitoc" %) 326 +* [[SmartSolo IGU 16HR 3C (5 Hz) Short Period Node>>path:#HSmartSoloIGU16HR3C285Hz29ShortPeriodNode]] 327 +** [[Sub-paragraph>>path:#HSub-paragraph]] 328 +** [[ >>path:#H]] 329 +* [[Smart Solo BD3C-5 (5 second) Broad-Band Node>>path:#HSmartSoloBD3C-5285second29Broad-BandNode]] 330 +** [[GPS Considerations>>path:#HGPSConsiderations]] 331 +* [[Keeping the Instruments Clean>>path:#HKeepingtheInstrumentsClean]] 332 +* [[Charge Time, Instrument Life, and Charge During Storage & Shipping>>path:#HChargeTime2CInstrumentLife2CandChargeDuringStorage26Shipping]] 333 +* [[Best Practices and Guide>>path:#HBestPracticesandGuide]] 334 +** [[Install>>path:#HInstall]] 335 +** [[Removing/Demob>>path:#HRemoving2FDemob]] 336 +** [[Charging>>path:#HCharging]] 337 +** [[Downloading and Converting Data to MiniSeed>>path:#HDownloadingandConvertingDatatoMiniSeed]] 338 +** [[Converting data>>path:#HConvertingdata]] 339 +** [[Cleaning>>path:#HCleaning]] 357 357 ))) 358 358 342 + 359 359 (% class="box" %) 360 360 ((( 361 361 = SmartSolo [[BD3C-5>>url:https://smartsolo.com/cp-4.html]] = ... ... @@ -369,16 +369,12 @@ 369 369 |(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)158 x160mm 370 370 |(% style="width:189px" %)**Weight**|(% style="width:221px" %)2.8 kg 371 371 |(% style="width:189px" %)**Data Storage**|(% style="width:221px" %)64 Gb 372 -|(% style="width:189px" %)**Battery**|(% style="width:221px" %)((( 373 -Lithium-ion battery contained in equipment (168.84 Wh) 374 - 375 -UN3481 PI967 S1 356 +|(% style="width:189px" %)**Battery**|(% style="width:221px" %)Li_etc XXAh 376 376 ))) 377 -))) 378 378 379 379 (% class="box" %) 380 380 ((( 381 -= SmartSolo [[IGU-16HR>>url:https://smartsolo.com/cp-3.html]] 3C=361 += SmartSolo [[IGU-16HR>>url:https://smartsolo.com/cp-3.html]] = 382 382 383 383 [[image:smartsolo node.jpg]] 384 384 ... ... @@ -387,87 +387,11 @@ 387 387 |(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 1652Hz 388 388 |(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)67.7 V/m/s 389 389 |(% style="width:187px" %)**Size (with spike)**|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm 390 -|(% style="width:187px" %)**Weight**|(% style="width:224px" %)2. 4kg370 +|(% style="width:187px" %)**Weight**|(% style="width:224px" %)2.3 kg 391 391 |(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)64 Gb 392 -|(% style="width:187px" %)**Battery**|(% style="width:224px" %)((( 393 -Lithium-ion battery contained in equipment (96.48 Wh) 394 - 395 -UN3481 PI967 S2 372 +|(% style="width:187px" %)**Battery**|(% style="width:224px" %)Li_etc XXAh 396 396 ))) 397 -))) 398 398 399 -(% class="box" %) 400 -((( 401 -= SmartSolo BD3C-16 Portable Battery Charger = 402 - 403 -[[image:20250729_125049.jpg]] 404 - 405 -|**Dimensions (LxHxW)**|558 x 357 x 300mm 406 -|**Input rating**|100-210V - 50/60Hz 407 -|**Power**|1000W 408 -|**Weight**|14.5kg 409 -|**Weight with cables**|21kg 375 + 410 410 ))) 411 - 412 -(% class="box" id="HSmartSoloBD3C-16PortableBatteryCharger" %) 413 -((( 414 -= SmartSolo IGU-16 Portable Data Harvester = 415 - 416 -[[image:20250729_124747.jpg]] 417 - 418 -|**Dimensions (LxHxW)**|625 x 500 x 366mm 419 -|**Input rating**|100-210V - 50/60Hz 420 -|**Power**|100W 421 -|**Weight**|21.5 - 24kg 422 -|**Slots no.**|16 423 -|**Download Speed**|20MB/sec/slot 424 424 ))) 425 - 426 -(% class="box" %) 427 -((( 428 -= SmartSolo IGU-16 Portable Battery Charger = 429 - 430 -= [[image:20250729_124644.jpg]] = 431 - 432 -|**Dimensions (LxHxW)**|625 x 500 x 366mm 433 -|**Input rating**|100-210V - 50/60Hz 434 -|**Power**|640W 435 -|**Weight**|26.3kg 436 -|**Slots no.**|16 437 -))) 438 - 439 -(% class="box" %) 440 -((( 441 -= SmartSolo BD3C-5 Carry Bag = 442 - 443 -[[image:20250729_124957.jpg]] 444 - 445 - 446 -|**Dimensions (LxHxW)**|590 x 225 x 405mm 447 -|**Weight**|8.2kg 448 -|**Slots no.**|6 449 -))) 450 - 451 -(% class="box" %) 452 -((( 453 -= SmartSolo IGU-16 3C Carry Bag = 454 - 455 -[[image:20250729_124502.jpg]] 456 - 457 -|**Dimensions (LxHxW)**|230 x 340 x 310mm 458 -|**Weight**|3.6kg 459 -|**Slots no.**|6 460 -))) 461 - 462 -(% class="box" %) 463 -((( 464 -= SmartSolo IGU-16 1C Carry Bag = 465 - 466 -[[image:20250729_124558.jpg]] 467 - 468 -|**Dimensions (LxHxW)**|225 x 200 x 550mm 469 -|**Weight**| 470 -|**Slots no.**|6 471 -))) 472 -))) 473 -)))
- 20250729_124502.jpg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.JackD - Size
-
... ... @@ -1,1 +1,0 @@ 1 -318.3 KB - Content
- 20250729_124558.jpg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.JackD - Size
-
... ... @@ -1,1 +1,0 @@ 1 -376.8 KB - Content
- 20250729_124644.jpg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.JackD - Size
-
... ... @@ -1,1 +1,0 @@ 1 -528.0 KB - Content
- 20250729_124747.jpg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.JackD - Size
-
... ... @@ -1,1 +1,0 @@ 1 -488.5 KB - Content
- 20250729_124957.jpg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.JackD - Size
-
... ... @@ -1,1 +1,0 @@ 1 -532.5 KB - Content
- 20250729_125049.jpg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.JackD - Size
-
... ... @@ -1,1 +1,0 @@ 1 -457.6 KB - Content
- BB_programming.labels.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.robert - Size
-
... ... @@ -1,1 +1,0 @@ 1 -111.5 KB - Content
- SP_programming.labels.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.robert - Size
-
... ... @@ -1,1 +1,0 @@ 1 -106.7 KB - Content
- example_metadata.txt
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.robert - Size
-
... ... @@ -1,1 +1,0 @@ 1 -2.7 KB - Content
-
... ... @@ -1,46 +1,0 @@ 1 -# AKL-HR Node Array (AHNA) code X5 2 -CITE: Name, Name, and Name. (2023). A Node Array [Data set]. International Federation of Digital Seismograph Networks. https://doi.org/10.7914/8jxr-7029 3 - 4 -#SITE START END LAT LONG ELEV SPS RECORDER S/N SENSOR S/N PROPERTY,LOCALITY,COUNTRY COMMENTS 5 - 6 -# INSTALL 7 -AKL01 20-05-2023T00:00 30-06-2023T00:00 -37.0471 175.5245 75 250 SSNODE_C 590001950 SSNODE_5S 590001950 "Te Puru,Hauraki,NZ" 8 -AKL02 20-05-2023T00:00 30-06-2023T00:00 -36.7476 175.5026 70 250 SSNODE_C 590001943 SSNODE_5S 590001943 "Coromandel Town,Hauraki,NZ" 9 -AKL03 20-05-2023T00:00 30-06-2023T00:00 -36.9694 175.5020 98 250 SSNODE_C 590002068 SSNODE_5S 590002068 "Te Mata,Hauraki,NZ" 10 -AKL05 19-05-2023T19:00 22-02-2023T00:00 -36.5996 174.3312 102 250 SSNODE_C 590001957 SSNODE_5S 590001957 "South Head South,Auckland,NZ" "site was disturbed" 11 -AKL06 19-05-2023T19:00 30-06-2023T00:00 -37.2459 175.3426 34 250 SSNODE_C 590001930 SSNODE_5S 590001930 "Back Miranda,Auckland,NZ" 12 -AKB05 02-05-2023T00:37 30-06-2023T00:00 -36.6651 175.4800 63 250 TSAWR TS085A TRILL120 4875 "Colville,Hauraki,NZ" 13 - 14 -# SERVICE 1 15 -AKL05 22-02-2023T00:00 30-06-2023T00:00 -36.5996 174.3312 102 250 SSNODE_C 590001999 SSNODE_.2S 590001999 "South Head South,Auckland,NZ" "swapped node to shortperiod" 16 - 17 - 18 - 19 - 20 -################### ANY LINE BEGINNING WITH # will be commented! Comments are good! 21 - 22 - 23 -# NOTES 24 -# the start/end time is not critical, but good to have. what IS critical are the times of instrument changes as this potentially affects response information 25 -# to mark equipment changes, add a new line with an updated start date (e.g. AKL05 above) 26 -# can use tabs or spaces, but spaces tend to look nicer. formatting ultimately doesn't matter too much so long as there is any sort of "white space" between the fields 27 -# if you don't know a serial number, put 999. if you don't know the elevation, put 0 28 -# for Nodes, put the same serial number for both Recoder and Sensor (since they are the same!) 29 - 30 - 31 -# EXAMPLE INSTRUMENT LABELS 32 -#LPR200 = ANU LPR-200 logger (beige box) 33 -#TSAWR = ANU TerraSAWR logger (yellow box) 34 - 35 -#TRILL120 = Trillium Compact 120s 36 -#TRILL20 = Trillium Compact 20s 37 -#TRILL120PH = Trillium Compact 120s PostHole 38 -#CMG6TD = Guralp 6TD 39 -#CMG3ESP = Guralp 3ESP 40 -#3DLITE = Lenarrtz 3D-LITE 41 - 42 -#SSNODE_C = output was in COUNTS (there is also SSNODE_MV, if you (accidentally!) output to millivolts etc) 43 -#SSNODE_5S = broadband (can also use SSNODE_BB) 44 -#SSNODE_.2S = shortperiod (can also use SSNODE_SP) 45 - 46 -#it doesn't matter too much what you use for equipment labels, so long as they are consistent and otherwise defined somewhere in the comments!
- 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