SmartSolo Node Seismometers

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

14

----

15

16

= **Programming Defaults** =

17

18

We recommend that the SP 16HR-3C be set to a gain of 24db and no higher than 250 Hz sampling rate unless there is an explicit reason to do so. The BD3C-5 should be set to a gain of 6db (which is the maximum allowed). These are what we use for our internal experiments.

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

22

= **Fieldwork Preparation** =

23

24

(% class="box warningmessage" %)

25

(((

26

**INVEST IN FAST EXTERNAL HARD DRIVES – DO NOT LET THIS BE THE LIMITATION OF DATA HARVESTING**

27

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.**

)))

== Magnets ==

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.

= **Installation** =

(% 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

)))

47

48

== 1. Logbook documentation ~*~** TODO ADD LOGBOOK FORMS ==

49

50

(((

51

**Essential Details** for field logs:

52

53

* Station name

54

* Latitude, longitude, elevation

55

* Names of team members present

56

* Date and both local & UTC time of installation/removal

57

* Serial number (SN) of the TOP HALF of the sensor (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)

59

60

== 2. Node Placement ==

61

)))

62

63

**Protection**: Place nodes inside (landfill) biodegradable bags to minimize cleaning and cross-site soil contamination.

**Site Analysis**:

* **Take compass measurements away from the sensor as it will affect your measurement.**

68

* Take photographs from various angles to document the site setup thoroughly.

69

* Include a detailed site description in your notes

70

71

== 3. GPS Considerations ==

72

73

(% class="wikigeneratedid" %)

74

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.

75

76

== 4. Visibility and Location Marking ==

77

78

**Flag Placement**: Position a flag, preferably in a bright color (avoid green or yellow), near the instrument to aid in its future location.

**GPS Marking**:

* Use a GPS device to mark the instrument's exact location.

83

* Record this location in both your paper notes and the GPS device.

84

85

== (% style="color:inherit; font-family:inherit; font-size:max(18px, min(20px, 14.4444px + 0.462963vw))" %)5. Charge Time, Pre-Deployment & Post-Deployment(%%) ==

86

87

* **Charging Duration**: Both types of nodes take approximately 6-8 hours to fully charge from a flat state.

88

* **Pre-Deployment Charging**:

89

** Although the nodes hold their charge well, it's beneficial to give them a "top up" charge before deployment.

90

91

* **Operational Duration**:

92

** 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.

93

94

* **Post-Retrieval Charging**:

95

** After retrieval, charge the instruments to about 50-60% (indicated as "orange" level) unless they are to be immediately re-deployed.

96

* **Storage and Shipping Charge Level**:

97

** Maintain a battery charge level of around 50-60% (e.g. "orange") for both storage and shipping purposes.

98

** This charge level is recommended to prevent battery damage and is safe for transportation.

99

** Nodes should not be stored fully charged, and **they should especially not be stored with 0 charge as this damages lithium batteries.**

100

101

(((

102

== 6. Data Sharing and Metadata Creation ==

)))

**GPS Data**:

* Ensure you have documented precise lat/lon locations for each station and **DOCUMENTED THIS CAREFULLY**

**Photo Sharing**:

* It is strongly encouraged to take pictures of each site and upload these to a shared platform (OneDrive, Dropbox, etc.).

**Metadata File**:

* 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.

116

117

== 7. Additional Best Practices ==

118

119

* **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.

----

= **Seismic Station Demobilization and Documentation** =

124

125

1. (((

126

**Preparation for Demobilization**:

127

128

* Before starting the demobilization process, ensure you have a compass, tape, marker, pen, masking tape, clipboard, logbook, and compass ready in your tote bag.

129

)))

130

1. (((

131

**Locating the instrument**:

132

133

* Use the downloaded GPS file to accurately locate the node for demobilization.

134

* Import this KMZ file onto your phone for easy reference and location tracking.

135

* Utilize Google Maps or Google Earth to create a KMZ file of the station’s location.

136

)))

137

1. (((

138

**Labeling Instruments for Demobilization**:

139

140

* Write the station name and the instrument’s serial number on a masking tape label to apply to the top of the node.

141

* Add markers 'D' (for download), 'C' (for charge), and ‘R’ (for removal) next to checkboxes on the label.

142

* Affix this label to the top of the instrument to avoid confusion during the charging and downloading data.

143

)))

144

1. (((

145

**Photographing the Setup Node**:

146

147

* Take a photo of the entire setup node with the __//label//__ and __//compass visible//__.

148

* This photo serves as a final record of the instrument’s condition and orientation at the time of removal.

149

)))

150

1. (((

151

**Logging Demobilization Details**:

152

153

* Use the field logbook to note the time of demobilization, serial numbers, and station name.

154

* Record any observations or issues related to the instrument’s orientation, level, or any other relevant factors.

155

)))

156

1. (((

157

**Final Checks and Equipment Removal**:

158

159

* Before physically removing the instrument, double-check that all necessary data has been downloaded and all photos and notes have been taken.

160

* Carefully dismantle and pack the equipment, ensuring that all components are accounted for and securely stored for transport.

)))

[[image:1706153556166-231.jpeg||data-xwiki-image-style-alignment="center" height="345" width="460"]]

----

= **Charging Procedure for Seismic Nodes** =

170

171

(((

172

== 1. Preparation for Charging: ==

173

174

* 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.

)))

(((

== 2. Disassembling the Node: ==

179

180

* For the IGU-16HR, remove the battery (bottom half) from the sensor. This is done by unscrewing the spikes counter-clockwise.

)))

(((

== 3. Setting Nodes in the Charging Box: ==

185

186

* Place 1-16 IGU-16HR battery components upside-down into the charger, assuring they are oriented properly.

)))

(((

== 4. Monitoring the Charging Process: ==

191

192

* 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.

193

* 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.

)))

(((

== 5. Updating Charge Status: ==

198

199

* 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.

200

* This step is crucial for tracking the charging status of multiple units, especially when handling a large number of nodes.

201

)))

202

203

[[IGU 16-HRcharger (left) and harvester (right)>>image:1705195933422-337.png||data-xwiki-image-style-alignment="center" height="299" width="530"]]

[[image:1706153354750-415.png||data-xwiki-image-style-alignment="center" height="317" width="562"]]

----

= **Downloading and Converting Seismic Data to MiniSeed Format** =

213

214

== Node Registration and Software Setup ==

215

216

1. (((

217

**Registering Nodes in the System**:

218

219

* To begin, register the nodes in the system so the software can recognize them.

220

* Navigate to the installation folder of “SmartSoloApps SoloLite”.

221

* Right-click on deviceconfig.exe and choose “run as an administrator”. Save the file to the “deviceconfig” directory (refer to the snapshot below).

222

* To avoid double registration, replace the file each time you register a new node.

223

)))

224

1. (((

225

**Creating a New Project in SoloLite**:

226

227

* Open the “SoloLite” software.

228

* Go to “File” and create a new project. Don't worry about finding the exact 16 nodes used in script writing.

229

* Ignore the settings for seismic recordings in the subsequent window. Resetting instruments (e.g., sampling rate, gain) requires reprogramming via script.

230

)))

231

232

== Data Downloading Process ==

233

234

1. (((

235

**Initiating Data Download**:

236

237

* Once a new project is created, the Data Transfer View panel will display connected nodes with details like series number and data size.

238

* If “Prospect not matched” appears, it simply means the new project doesn’t match the original programming project. This is not a concern.

239

* Select all nodes and right-click to “force download”. This starts the download process.

240

* Completed downloads will appear as new folders in the Downloaded Data panel.

241

)))

242

1. (((

243

**Exporting Data in Readable Format**:

244

245

* Go to the “Tool” menu and select “export seismic data”.

246

* Tailor other parameters to personal preference and ensure "Sample Interval" matches the setting used during node reset.

247

* Click “prepare” followed by “run” to start reformatting. Monitor this process in the small panel at the bottom left.

248

* (% class="box warningmessage" %)

249

(((

250

* **Ensure to export data as "COUNTS" (int32), not "mV" (float). This is critical!**

251

252

* **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.**

)))

)))

== Handling Nodes During Download ==

257

258

1. (((

259

**Monitoring Download Indicators**:

260

261

* During download, green lights on nodes will blink, and associated red lights on the rack will flash.

262

* Disconnect nodes properly before unplugging anything.

263

* Be cautious: if the laptop enters sleep mode, the download will pause.

264

)))

265

1. (((

266

//**Investment in Storage Hardware**~://

267

268

* (% class="box warningmessage" %)

269

(((

270

* **Use fast external hard drives to avoid limitations in data harvesting.**

271

272

* **Recommended specifications: USB-C, USB 3.0, and 4+ Tb of space.**

273

* **The USB type for the harvester is TYPE-A, the typical normal rectangular shape.**

)))

)))

1. (((

**Metadata and Time Settings**:

278

279

* Ensure all metadata is saved with the file.

280

* 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.

281

)))

282

1. (((

283

**Finalizing the Download**:

284

285

* After downloading, mark the //"D"// box on your temporary labels to indicate completion.

)))

[[image:1706153266647-145.png||data-xwiki-image-style-alignment="center" height="340" width="603"]]

[[Caption>>image:1705195543887-977.png||data-xwiki-image-style-alignment="center" height="534" width="632"]]

[[Caption>>image:1705195543890-537.png||data-xwiki-image-style-alignment="center" height="397" width="665"]]

[[Caption>>image:1705195543891-334.png||data-xwiki-image-style-alignment="center" height="379" width="650"]]

[[image:1705195543898-365.png||data-xwiki-image-style-alignment="center" height="467" width="674"]]

----

= **Cleaning** =

When still connected, the nodes are water resistant (don't submerge them!) and can handle a good spray / wipedown. A strong, non-wire brush is helpful to reach areas between the metal spikes on the bottom.

314

315

= **Weights (for shipping)** =

316

317

The weights of bags of nodes, as well as data harvesters and node chargers, are listed below:

318

319

1 bag + 6 SP (IGU-16HR) nodes: 18 kg

320

321

1 SP (IGU-16HR) data harvester: 21.5 kg