Changes for page SmartSolo Node Seismometers
Last modified by KB on 2025/12/04 12:33
From version 20.1
edited by Sima Mousavi
on 2024/01/18 17:25
on 2024/01/18 17:25
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
-
Attachments (0 modified, 13 added, 0 removed)
-
Objects (0 modified, 2 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -SmartSolo Nodes 1 +SmartSolo Node Seismometers - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. sima1 +XWiki.robert - Content
-
... ... @@ -2,51 +2,105 @@ 2 2 ((( 3 3 (% class="col-xs-12 col-sm-8" %) 4 4 ((( 5 -= **Node Setup** =5 += **Node Types** = 6 6 7 -S hort term(~~30day)batterypowerednodes7 +ANSIR carry 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 11 -(% class="box infomessage" %) 12 -((( 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 + 15 +---- 16 + 17 += **Programming Defaults** = 18 + 19 +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. 20 + 21 +[[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"]] 22 + 23 +[[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"]] 24 + 25 +FIFO (first in, first out) data mode is safest as this will overwrite old data in case you forgot to clear the storage. At <= 250 hz you can fit 4++ months of data on these, shouldn't be an issue. 26 + 27 +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. 28 + 29 +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. 30 + 31 +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!** 32 + 33 +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. 34 + 35 +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. 36 + 37 +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. 38 + 39 +Bluetooth (BB nodes only) should be turned OFF to conserve power. 40 + 41 +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). 42 + 43 +{{info}} 44 +**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! 45 +{{/info}} 46 + 47 += **Fieldwork Preparation** = 48 + 13 13 (% class="box warningmessage" %) 14 14 ((( 15 -**INVEST IN FAST EXTERNAL HARD DRIVES – DO NOT LET THIS BE THE LIMITATION OF DATA HARVESTING ** 51 +**INVEST IN FAST EXTERNAL HARD DRIVES – DO NOT LET THIS BE THE LIMITATION OF DATA HARVESTING** 52 + 53 +**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.** 54 + 55 +**We have had good experience with the 4Tb Samsung T7 Shield drives.** 16 16 ))) 17 -))) 18 18 58 +== Magnets == 59 + 60 +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). 61 + 62 +== Animal-Proofing == 63 + 64 +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. 65 + 19 19 = **Installation** = 20 20 21 -=== **1- Logbook documentation** === 68 +(% class="box infomessage" %) 69 +((( 70 +**Field logs are a critical component of fieldwork and this is especially the case for large N nodal deploys. Take notes!** 71 +))) 22 22 73 +== 1. Logbook documentation == 74 + 23 23 ((( 24 -**Essential Details** :Recordthefollowingin alogbook:76 +**Essential Details** for field logs: 25 25 26 26 * Station name 27 -* Latitude andlongitude79 +* Latitude, longitude, elevation 28 28 * Names of team members present 29 -* Date and local time of installation 30 -* Serial number (SN) of the sensor 31 -* Detailed notes on the site conditions and setup 81 +* Date and both local & UTC time of installation/removal 82 +* Serial number (SN) of the TOP HALF of the sensor (if a BD3C-5, there is only one serial number) 83 +* 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) 32 32 33 -=== **2- Node Placement** === 85 +[[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! 86 + 87 +== 2. Node Placement == 34 34 ))) 35 35 36 -**Protection**: Place nodes inside thick,landfill biodegradableplasticbagsforenvironmentalprotection.90 +**Protection**: Place nodes inside (landfill) biodegradable bags to minimize cleaning and cross-site soil contamination. 37 37 38 38 **Site Analysis**: 39 39 40 -* Conductcompass measurements away from the nodeandmetallicstructures,adjusting forinclination angle.41 -* Take multiple photographs from various angles to document the site setup thoroughly.42 -* 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)94 +* **Take compass measurements away from the sensor as it will affect your measurement.** 95 +* Take photographs from various angles to document the site setup thoroughly. 96 +* Include a detailed site description in your notes 43 43 44 -== =**3-GPS Considerations**===98 +== 3. GPS Considerations == 45 45 46 46 (% class="wikigeneratedid" %) 47 -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 BD3Cwill not start recording withoutfirstattaining a GPS lock.101 +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. 48 48 49 -== =**4-Visibility and Location Marking**===103 +== 4. Visibility and Location Marking == 50 50 51 51 **Flag Placement**: Position a flag, preferably in a bright color (avoid green or yellow), near the instrument to aid in its future location. 52 52 ... ... @@ -55,245 +55,319 @@ 55 55 * Use a GPS device to mark the instrument's exact location. 56 56 * Record this location in both your paper notes and the GPS device. 57 57 58 -== =(% style="color:inherit; font-family:inherit; font-size:max(18px, min(20px, 14.4444px + 0.462963vw))" %)**5-Charge Time, Pre-Deployment & Post-Deployment**(%%) ===112 +== (% style="color:inherit; font-family:inherit; font-size:max(18px, min(20px, 14.4444px + 0.462963vw))" %)5. Charge Time, Pre-Deployment & Post-Deployment(%%) == 59 59 60 60 * **Charging Duration**: Both types of nodes take approximately 6-8 hours to fully charge from a flat state. 61 61 * **Pre-Deployment Charging**: 62 -** Although the nodes hold their charge well, it's beneficial to give them a "top up" charge rightbefore deployment.116 +** Although the nodes hold their charge well, it's beneficial to give them a "top up" charge before deployment. 63 63 64 - 65 65 * **Operational Duration**: 66 -** When recording at 250 Hz, with GPS on and Bluetooth disabled, the instruments are expected to last about 30 days per charge cycle. 119 +** 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 - 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 - 73 - 122 +** After retrieval, charge the instruments to about 50-60% (indicated as "orange" level) unless they are to be immediately re-deployed. 74 74 * **Storage and Shipping Charge Level**: 75 -** Maintain a battery charge level of around 50-60% for both storage and shipping purposes. 124 +** Maintain a battery charge level of around 50-60% (e.g. "orange") for both storage and shipping purposes. 76 76 ** This charge level is recommended to prevent battery damage and is safe for transportation. 126 +** Nodes should not be stored fully charged, and **they should especially not be stored with 0 charge as this damages lithium batteries.** 77 77 78 -=== === 128 +((( 129 +== 6. Data Sharing and Metadata Creation == 130 +))) 79 79 80 -=== === 81 - 82 -=== **6- Data Sharing and Metadata Creation** === 83 - 84 84 **GPS Data**: 85 85 86 -* Download the GPS file to a laptop. 87 -* Share this file on a drive accessible to all team members for uniform understanding of node locations. 134 +* Ensure you have documented precise lat/lon locations for each station and **DOCUMENTED THIS CAREFULLY** 88 88 89 89 **Photo Sharing**: 90 90 91 -* Upload site photos to a shared platform (OneDrive, Dropbox, etc.). 92 -* Integrating photos into Google Maps or Google Earth can be particularly beneficial for easy location referencing. 138 +* It is strongly encouraged to take pictures of each site and upload these to a shared platform (OneDrive, Dropbox, etc.). 93 93 94 94 **Metadata File**: 95 95 96 -* Create a metadata XML fileforeachnode,which isessentialfordata organisation andfuturereference.142 +* 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. 97 97 98 -== =**7-Additional Best Practices**===144 +== 7. Additional Best Practices == 99 99 100 -* **Environmental Responsibility**: Ensure that the node placement and the materials used are environmentally responsible and adhere to local regulations. 101 -* **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. 146 +* **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. 102 102 103 -* ((( 104 -==== **Keeping the Instruments Clean** ==== 105 -))) 106 -* ((( 107 -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. 108 -))) 148 +---- 109 109 110 -= = 150 += **Seismic Station Demobilization and Documentation** = 111 111 112 -= SmartSolo IGU 16HR 3C (5 Hz) Short Period Node = 152 +1. ((( 153 +**Preparation for Demobilization**: 113 113 114 -blahblah 155 +* Before starting the demobilization process, ensure you have a compass, tape, marker, pen, masking tape, clipboard, logbook, and compass ready in your tote bag. 156 +))) 157 +1. ((( 158 +**Locating the instrument**: 115 115 116 -== Sub-paragraph == 160 +* Use the downloaded GPS file to accurately locate the node for demobilization. 161 +* Import this KMZ file onto your phone for easy reference and location tracking. 162 +* Utilize Google Maps or Google Earth to create a KMZ file of the station’s location. 163 +))) 164 +1. ((( 165 +**Labeling Instruments for Demobilization**: 117 117 167 +* Write the station name and the instrument’s serial number on a masking tape label to apply to the top of the node. 168 +* Add markers 'D' (for download), 'C' (for charge), and ‘R’ (for removal) next to checkboxes on the label. 169 +* Affix this label to the top of the instrument to avoid confusion during the charging and downloading data. 170 +))) 171 +1. ((( 172 +**Photographing the Setup Node**: 118 118 119 -== == 174 +* Take a photo of the entire setup node with the __//label//__ and __//compass visible//__. 175 +* This photo serves as a final record of the instrument’s condition and orientation at the time of removal. 176 +))) 177 +1. ((( 178 +**Logging Demobilization Details**: 120 120 180 +* Use the field logbook to note the time of demobilization, serial numbers, and station name. 181 +* Record any observations or issues related to the instrument’s orientation, level, or any other relevant factors. 182 +))) 183 +1. ((( 184 +**Final Checks and Equipment Removal**: 121 121 122 -= Smart Solo BD3C-5 (5 second) Broad-Band Node = 186 +* Before physically removing the instrument, double-check that all necessary data has been downloaded and all photos and notes have been taken. 187 +* Carefully dismantle and pack the equipment, ensuring that all components are accounted for and securely stored for transport. 123 123 124 -Lorem 189 + 190 +))) 125 125 126 -[[image:17051 96270090-364.png]]192 +[[image:1706153556166-231.jpeg||data-xwiki-image-style-alignment="center" height="345" width="460"]] 127 127 194 +---- 128 128 129 -= =GPSConsiderations ==196 += **Charging Procedure for Seismic Nodes** = 130 130 131 -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. 198 +((( 199 +== 1. Preparation for Charging: == 132 132 133 -= Keeping the Instruments Clean = 201 +* 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. 202 +))) 134 134 135 -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. 204 +((( 205 +== 2. Disassembling the Node: == 136 136 207 +* For the IGU-16HR, remove the battery (bottom half) from the sensor. This is done by unscrewing the spikes counter-clockwise. 208 +))) 137 137 138 -= Charge Time, Instrument Life, and Charge During Storage & Shipping = 210 +((( 211 +== 3. Setting Nodes in the Charging Box: == 139 139 140 -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. 213 +* Place 1-16 IGU-16HR battery components upside-down into the charger, assuring they are oriented properly. 214 +))) 141 141 142 -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. 216 +((( 217 +== 4. Monitoring the Charging Process: == 143 143 219 +* 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. 220 +* 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. 221 +))) 144 144 145 -= Best Practices and Guide = 223 +((( 224 +== 5. Updating Charge Status: == 146 146 147 -== Install == 226 +* 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. 227 +* This step is crucial for tracking the charging status of multiple units, especially when handling a large number of nodes. 228 +))) 148 148 149 - Logbookisrequired(usedagainforpick up &metadatacreation)230 +[[IGU 16-HRcharger (left) and harvester (right)>>image:1705195933422-337.png||data-xwiki-image-style-alignment="center" height="299" width="530"]] 150 150 151 -- station name 152 152 153 -- lat / long 154 154 155 -- team members 156 156 157 -- date and local time 235 +{{{ 236 + }}} 158 158 159 -- SN of sensor238 +---- 160 160 161 - -noteson site240 += **Downloading and Converting Seismic Data to MiniSeed Format** = 162 162 163 -Place nodes in thick (“landfill biodegradable”) plastic bags in the hole 242 +(% class="wikigeneratedid" %) 243 +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]] 164 164 165 - Takecompass measurement away fromnodeand fences [make suretoadjustinclinationangle]245 +== Connection tips: == 166 166 167 - Take manyphotosfromthesitefromdifferent angles247 +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: 168 168 169 -Add a precise site description to the notes such as distances and orientations from landmarks 249 +* Place the node on the harvester gently, then firmly press it down onto the pins. 250 +* 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. 251 +* 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. 252 +* 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! 170 170 171 -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. 172 172 173 -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. 174 174 175 - DownloadtheGPS (Garmin) filetoalaptopandshare drive tosharewith other GPSdevices256 +== Node Registration and Software Setup == 176 176 177 -Share photos in a shared location (Google photos, OneDrive, Dropbox, etc), but most useful are those added to a Google Maps/Earth location 258 +1. ((( 259 +**Registering Nodes in the System**: 178 178 179 -Create metadata .xml file 261 +* To begin, register the nodes in the system so the software can recognize them. 262 +* Navigate to the installation folder of “SmartSoloApps SoloLite”. 263 +* Right-click on deviceconfig.exe and choose “run as an administrator”. Save the file to the “deviceconfig” directory (refer to the snapshot below). 264 +* To avoid double registration, replace the file each time you register a new node. 265 +))) 266 +1. ((( 267 +**Creating a New Project in SoloLite**: 180 180 269 +* Open the “SoloLite” software. 270 +* Go to “File” and create a new project. Don't worry about finding the exact 16 nodes used in script writing. 271 +* Ignore the settings for seismic recordings in the subsequent window. Resetting instruments (e.g., sampling rate, gain) requires reprogramming via script. 272 +))) 181 181 182 -== Removing/Demob==274 +== File structure == 183 183 184 - DownloadandthenusetheGPSfileto locatethe node276 +There are essentially three main folders where relevant PROSPECT and PROJECT DATA is stored. Individual projects will be found as subfolders in these. 185 185 186 - UseGoogle Maps / GoogleEarthto create a kmz file that can then be imported onto your phone.278 +=== SOLOLITE === 187 187 280 +This folder stores SoloLite config files and parameters. Nothing too important stored here, you can always start over and re-create this. 188 188 189 - Uploadphotosof the site282 +=== DCCDATA === 190 190 191 - -station name284 +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. 192 192 193 - -latitude286 +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)// 194 194 195 - -longitude288 +Then in the SoloLite software, go to tools > Reanalyze Seismic Data 196 196 197 - -elevation290 +=== SOLODATA === 198 198 199 -* SN of sensor – SN of battery (optional) 200 -* Site notes and name of location (e.g. Richards garden, Te Mini steam field eastern side) 292 +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. 201 201 202 -Upload photos into Google Earth and on a shared drive 203 203 204 - Beforeremoving the instrument have your compass,tape,marker, pen, clipboard, logbookand compassready (in tote bag!).295 +== Data Downloading Process == 205 205 206 -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. 297 +1. ((( 298 +**Initiating Data Download**: 207 207 208 -Take a photo of the entire setup node with the label on it + compass 300 +* Once a new project is created, the Data Transfer View panel will display connected nodes with details like series number and data size. 301 +* If “Prospect not matched” appears, it simply means the new project doesn’t match the original programming project. This is not a concern. 302 +* Select all nodes and right-click to “force download”. This starts the download process. 303 +* Completed downloads will appear as new folders in the Downloaded Data panel. 304 +))) 305 +1. ((( 306 +**Exporting Data in Readable Format**: 209 209 210 -Use existing field logbook to note time, SN and station name plus any notes – including any issues with orientation or level or anything else 308 +* Go to the “Tool” menu and select “export seismic data”. 309 +* Tailor other parameters to personal preference and ensure "Sample Interval" matches the setting used during node reset. 310 +* Click “prepare” followed by “run” to start reformatting. Monitor this process in the small panel at the bottom left. 311 +* (% class="box warningmessage" %) 312 +((( 313 +* **Ensure to export data as "COUNTS" (int32), not "mV" (float). This is critical!** 211 211 315 +* **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.** 316 +))) 317 +))) 212 212 213 -== Charging ==319 +== Smart Solo Z Polarity bug (SP nodes ONLY!) == 214 214 215 - Cleannodepriorto chargingand harvesting the data321 +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.** 216 216 217 - Removebattery(and spike)from thesensorby twistingthe spike part of the instrument323 +== 18 Leap Second bug == 218 218 219 -Set 16nodes into the charging box(spikesup)325 +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. 220 220 221 - Redlightson theboxnexttothebatterieswillcome on and remain asteady redlightwhilecharging.Thiswillchangeto orange,thentogreen,thentoflashinggreen whenfullycharged.327 +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. 222 222 223 -This is a good time to check the "C" box on your temporary labels to mark that the unit has been charged 329 +{{code language="none"}} 330 +<?xml version="1.0" encoding="UTF-8"?> 331 +<config> 332 + <leapsecond> 333 + <interval> 334 + <start_time>2017-01-01#00:00:00</start_time> 335 + <end_time>2999-12-31#23:59:59</end_time> 336 + <second>18</second> 337 + </interval> 338 + <interval> 339 + <start_time>1970-01-01#00:00:00</start_time> 340 + <end_time>2017-01-01#00:00:00</end_time> 341 + <second>17</second> 342 + </interval> 343 + </leapsecond> 344 + <GPS_distance_threshold_degree> 345 + 4e-5 346 + </GPS_distance_threshold_degree> 347 +</config> 348 +{{/code}} 224 224 225 -[[IGU 16-HRcharger (left) and harvester (right)>>image:1705195933422-337.png||data-xwiki-image-style-alignment="center"]] 226 226 351 +== Handling Nodes During Download == 227 227 353 +1. ((( 354 +**Monitoring Download Indicators**: 228 228 229 -== Downloading and Converting Data to MiniSeed == 356 +* During download, green lights on nodes will blink, and associated red lights on the rack will flash. 357 +* Disconnect nodes properly before unplugging anything. 358 +* Be cautious: if the laptop enters sleep mode, the download will pause. 359 +))) 360 +1. ((( 361 +//**Investment in Storage Hardware**~:// 230 230 363 +* (% class="box warningmessage" %) 364 +((( 365 +* **Use fast external hard drives to avoid limitations in data harvesting.** 231 231 232 -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. 367 +* **Recommended specifications: USB-C, USB 3.0, and 4+ Tb of space.** 368 +* **The USB type for the harvester is TYPE-A, the typical normal rectangular shape.** 369 +))) 370 +))) 371 +1. ((( 372 +**Metadata and Time Settings**: 233 233 234 -[[image:1705195543887-977.png]] 374 +* Ensure all metadata is saved with the file. 375 +* 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. 376 +))) 377 +1. ((( 378 +**Finalizing the Download**: 235 235 380 +* After downloading, mark the //"D"// box on your temporary labels to indicate completion. 236 236 237 -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. 382 + 383 +))) 238 238 239 -[[image:170 5195543890-537.png||data-xwiki-image-style-alignment="center"]]385 +[[image:1706153266647-145.png||data-xwiki-image-style-alignment="center" height="340" width="603"]] 240 240 241 241 242 -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. 243 243 244 -[[image:17051955438 91-334.png||data-xwiki-image-style-alignment="center"]]389 +[[Caption>>image:1705195543887-977.png||data-xwiki-image-style-alignment="center" height="534" width="632"]] 245 245 246 -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. 247 247 248 -(% class="box warningmessage" %) 249 -((( 250 -**Please make sure that data is exported as "COUNTS" and NOT "mV"!** 251 -))) 252 252 253 -(% class="box warningmessage" %) 254 -((( 255 -**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.** 256 -))) 257 257 258 - A listof ANUgroup preferredparameters canbe foundatthe end of this session. One thingto noteisthat the “SampleInterval” must be set exactly to this used to reset thenodes. Onceyou are done with thesetting, click “prepare”before “run”. If everything works correctly, you should see the reformattingprocess from the small panel onthebottom left of this popped upwindow.394 +[[Caption>>image:1705195543890-537.png||data-xwiki-image-style-alignment="center" height="397" width="665"]] 259 259 260 -Now the data should be ready. Then you can select these data and right click to output the GPS information associated with them. 261 261 262 -[[image:1705195543898-365.png||data-xwiki-image-style-alignment="center"]] 263 263 264 - When downloading,all thegreenlights on the nodeswill blink. The associated red lightsontherack will flash whenit is downloading, andmakesureto disconnectthenodes beforeyou unplug anything. Becareful:if the laptopgoes to sleep, the download process will pause.398 +[[Caption>>image:1705195543891-334.png||data-xwiki-image-style-alignment="center" height="379" width="650"]] 265 265 266 -(% class="box infomessage" %) 267 -((( 268 -**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! 269 -))) 270 270 271 -When downloading, ensure that all metadata is saved along with the file. 272 272 273 - Start and endtime:the system will automatically findthe earliest time of the data and set that asthestartingtime. However, you cansetthetimea day earlierwitha sharp start of 00:00:00. In this case, all the outputteddata segmentswill be 24 hours long starting from midnight.402 +[[image:1705195543898-365.png||data-xwiki-image-style-alignment="center" height="467" width="674"]] 274 274 275 - //Once downloaded, mark the "D" box on your temporary labels!//404 +---- 276 276 277 -= =Convertingdata==406 += **Cleaning** = 278 278 279 - Checkthe dataallhave been converted tominiseedcorrectly408 +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. 280 280 281 - –3 filesper stationper day410 += **Weights (for shipping)** = 282 282 283 -* Files are the same size (NOTE if having memory issues one or more of the components may have 0-1 kb) 284 -* ~~ 5 Gb / node / month 412 +The weights of bags of nodes, as well as data harvesters and node chargers, are listed below: 285 285 286 - //Tick‘R’boxonthenodelabel//414 +1 bag + 6 SP (IGU-16HR) nodes: 18 kg 287 287 416 +1 SP (IGU-16HR) data harvester: 21.5 kg 288 288 289 - ==Cleaning==418 +1 SP (IGU-16HR) charger: 26.3 kg 290 290 291 - Ifthenodesareplacedinathick plasticbag at thetimeofinstallation, thecleaning procedureshould be straightforward.Ifnot you havea lot of worktodobefore they are returned to us!420 +1 BB (BD3C-5) charger/data harvester (with and without 16 cables): 21 kg / 14.5 kg 292 292 293 - 422 +1 case + 5 BB (BD3C-5) nodes and 6 BB nodes: 22 kg / 25 kg 294 294 ))) 295 295 296 - 297 297 (% class="col-xs-12 col-sm-4" %) 298 298 ((( 299 299 (% class="box" %) ... ... @@ -300,24 +300,11 @@ 300 300 ((( 301 301 **Contents** 302 302 303 -(% class="wikitoc" %) 304 -* [[SmartSolo IGU 16HR 3C (5 Hz) Short Period Node>>path:#HSmartSoloIGU16HR3C285Hz29ShortPeriodNode]] 305 -** [[Sub-paragraph>>path:#HSub-paragraph]] 306 -** [[ >>path:#H]] 307 -* [[Smart Solo BD3C-5 (5 second) Broad-Band Node>>path:#HSmartSoloBD3C-5285second29Broad-BandNode]] 308 -** [[GPS Considerations>>path:#HGPSConsiderations]] 309 -* [[Keeping the Instruments Clean>>path:#HKeepingtheInstrumentsClean]] 310 -* [[Charge Time, Instrument Life, and Charge During Storage & Shipping>>path:#HChargeTime2CInstrumentLife2CandChargeDuringStorage26Shipping]] 311 -* [[Best Practices and Guide>>path:#HBestPracticesandGuide]] 312 -** [[Install>>path:#HInstall]] 313 -** [[Removing/Demob>>path:#HRemoving2FDemob]] 314 -** [[Charging>>path:#HCharging]] 315 -** [[Downloading and Converting Data to MiniSeed>>path:#HDownloadingandConvertingDatatoMiniSeed]] 316 -** [[Converting data>>path:#HConvertingdata]] 317 -** [[Cleaning>>path:#HCleaning]] 431 +{{toc/}} 432 + 433 + 318 318 ))) 319 319 320 - 321 321 (% class="box" %) 322 322 ((( 323 323 = SmartSolo [[BD3C-5>>url:https://smartsolo.com/cp-4.html]] = ... ... @@ -328,15 +328,19 @@ 328 328 329 329 |(% style="width:189px" %)**Frequency Band**|(% style="width:221px" %)5 Seconds to 150Hz 330 330 |(% style="width:189px" %)**Sensitivity**|(% style="width:221px" %)200 V/m/s 331 -|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)158 x160mm 446 +|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)Φ158 x160mm(H) 332 332 |(% style="width:189px" %)**Weight**|(% style="width:221px" %)2.8 kg 333 333 |(% style="width:189px" %)**Data Storage**|(% style="width:221px" %)64 Gb 334 -|(% style="width:189px" %)**Battery**|(% style="width:221px" %)Li_etc XXAh 449 +|(% style="width:189px" %)**Battery**|(% style="width:221px" %)((( 450 +Lithium-ion battery contained in equipment (168.84 Wh) 451 + 452 +UN3481 PI967 S1 335 335 ))) 454 +))) 336 336 337 337 (% class="box" %) 338 338 ((( 339 -= SmartSolo [[IGU-16HR>>url:https://smartsolo.com/cp-3.html]] = 458 += SmartSolo [[IGU-16HR>>url:https://smartsolo.com/cp-3.html]]3C = 340 340 341 341 [[image:smartsolo node.jpg]] 342 342 ... ... @@ -343,13 +343,110 @@ 343 343 [[image:smartsolo node 2.jpg]] 344 344 345 345 |(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 1652Hz 346 -|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %) 67.7 V/m/s347 -|(% style="width:187px" %)**Size (with spike)**|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm 348 -|(% style="width:187px" %)**Weight**|(% style="width:224px" %)2. 3kg465 +|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)76.7 V/m/s 466 +|(% style="width:187px" %)**Size (with spike)**|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm(H) 467 +|(% style="width:187px" %)**Weight**|(% style="width:224px" %)2.4 kg 349 349 |(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)64 Gb 350 -|(% style="width:187px" %)**Battery**|(% style="width:224px" %)Li_etc XXAh 469 +|(% style="width:187px" %)**Battery**|(% style="width:224px" %)((( 470 +Lithium-ion battery contained in equipment (96.48 Wh) 471 + 472 +UN3481 PI967 S2 351 351 ))) 474 +))) 352 352 476 +(% class="box" %) 477 +((( 353 353 479 + 480 += SmartSolo [[IGU-16>>url:https://smartsolo.com/cp-3.html]]1C = 481 + 482 + 483 +[[image:Screenshot 2025-08-01 161027.png]] 484 + 485 +|(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 413Hz 486 +|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)80 V/m/s 487 +|(% style="width:187px" %)**Size (without spike)**|(% style="width:224px" %)95mm(L) × 103mm(W) × 118mm(H) 488 +|(% style="width:187px" %)**Weight**|(% style="width:224px" %)1.1 kg 489 +|(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)8 Gb 490 +|(% style="width:187px" %)**Battery**|(% style="width:224px" %)((( 491 +Lithium-ion battery contained in equipment (38.48 Wh) 492 + 493 +UN3481 PI967 S2 354 354 ))) 355 355 ))) 496 + 497 +(% class="box" %) 498 +((( 499 += SmartSolo BD3C-16 Portable Battery Charger = 500 + 501 +[[image:20250729_125049.jpg]] 502 + 503 +|**Dimensions (LxHxW)**|558 x 357 x 300mm 504 +|**Input rating**|100-210V - 50/60Hz 505 +|**Power**|1000W 506 +|**Weight**|14.5kg 507 +|**Weight with cables**|21kg 508 +))) 509 + 510 +(% class="box" id="HSmartSoloBD3C-16PortableBatteryCharger" %) 511 +((( 512 += SmartSolo IGU-16 Portable Data Harvester = 513 + 514 +[[image:20250729_124747.jpg]] 515 + 516 +|**Dimensions (LxHxW)**|625 x 500 x 366mm 517 +|**Input rating**|100-210V - 50/60Hz 518 +|**Power**|100W 519 +|**Weight**|21.5 - 24kg 520 +|**Slots no.**|16 521 +|**Download Speed**|20MB/sec/slot 522 +))) 523 + 524 +(% class="box" %) 525 +((( 526 += SmartSolo IGU-16 Portable Battery Charger = 527 + 528 +[[image:20250729_124644.jpg]] 529 + 530 +|**Dimensions (LxHxW)**|625 x 500 x 366mm 531 +|**Input rating**|100-210V - 50/60Hz 532 +|**Power**|640W 533 +|**Weight**|26.3kg 534 +|**Slots no.**|16 535 +))) 536 + 537 +(% class="box" %) 538 +((( 539 += SmartSolo BD3C-5 Carry Case = 540 + 541 +[[image:20250729_124957.jpg]] 542 + 543 + 544 +|**Dimensions (LxHxW)**|590 x 225 x 405mm 545 +|**Weight**|8.2kg 546 +|**Slots no.**|6 547 +))) 548 + 549 +(% class="box" %) 550 +((( 551 += SmartSolo IGU-16 3C Carry Bag = 552 + 553 +[[image:20250729_124502.jpg]] 554 + 555 +|**Dimensions (LxHxW)**|230 x 340 x 310mm 556 +|**Weight**|3.6kg 557 +|**Slots no.**|6 558 +))) 559 + 560 +(% class="box" %) 561 +((( 562 += SmartSolo IGU-16 1C Carry Bag = 563 + 564 +[[image:20250729_124558.jpg]] 565 + 566 +|**Dimensions (LxHxW)**|225 x 200 x 550mm 567 +|**Weight**| 568 +|**Slots no.**|6 569 +))) 570 +))) 571 +)))
- 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