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

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.

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

22

[[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"]]

23

24

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.

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

40

(% class="box warningmessage" %)

41

(((

42

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

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

)))

== 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).

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.

= **Installation** =

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

)))

63

64

== 1. Logbook documentation ==

65

66

(((

67

**Essential Details** for field logs:

68

69

* Station name

70

* Latitude, longitude, elevation

71

* Names of team members present

72

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

73

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

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 ==

79

)))

80

81

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

86

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

87

* Include a detailed site description in your notes

88

89

== 3. GPS Considerations ==

90

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. **These nodes will not start recording without attaining a GPS lock** and repeated attempts will excessively drain the battery.

93

94

== 4. Visibility and Location Marking ==

95

96

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

101

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

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

104

105

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

106

* **Pre-Deployment Charging**:

107

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

108

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.

111

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.

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.

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

119

(((

120

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

134

135

== 7. Additional Best Practices ==

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.

----

= **Seismic Station Demobilization and Documentation** =

142

143

1. (((

144

**Preparation for Demobilization**:

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.

147

)))

148

1. (((

149

**Locating the instrument**:

150

151

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

152

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

153

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

154

)))

155

1. (((

156

**Labeling Instruments for Demobilization**:

157

158

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

159

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

160

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

161

)))

162

1. (((

163

**Photographing the Setup Node**:

164

165

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

166

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

167

)))

168

1. (((

169

**Logging Demobilization Details**:

170

171

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

172

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

173

)))

174

1. (((

175

**Final Checks and Equipment Removal**:

176

177

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

178

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

188

189

(((

190

== 1. Preparation for Charging: ==

191

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.

)))

(((

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

)))

(((

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

)))

(((

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

)))

(((

== 5. Updating Charge Status: ==

216

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

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

219

)))

220

221

[[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** =

231

232

== Node Registration and Software Setup ==

233

234

1. (((

235

**Registering Nodes in the System**:

236

237

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

238

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

239

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

240

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

241

)))

242

1. (((

243

**Creating a New Project in SoloLite**:

244

245

* Open the “SoloLite” software.

246

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

247

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

248

)))

249

250

== Data Downloading Process ==

251

252

1. (((

253

**Initiating Data Download**:

254

255

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

256

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

257

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

258

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

259

)))

260

1. (((

261

**Exporting Data in Readable Format**:

262

263

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

264

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

265

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

266

* (% class="box warningmessage" %)

267

(((

268

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

269

270

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

275

276

1. (((

277

**Monitoring Download Indicators**:

278

279

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

280

* Disconnect nodes properly before unplugging anything.

281

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

282

)))

283

1. (((

284

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

285

286

* (% class="box warningmessage" %)

287

(((

288

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

289

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

)))

)))

1. (((

**Metadata and Time Settings**:

296

297

* Ensure all metadata is saved with the file.

298

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

299

)))

300

1. (((

301

**Finalizing the Download**:

302

303

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

332

333

= **Weights (for shipping)** =

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

346

)))

347

348

(% class="col-xs-12 col-sm-4" %)

(((

(% class="box" %)

(((

**Contents**

)))

(% class="box" %)

(((

= SmartSolo [[BD3C-5>>url:https://smartsolo.com/cp-4.html]] =

362

363

[[image:Smartsolo IGU BD3C 5 (2).jpg]]

364

365

[[image:smartsolo.jpg]]

366

367

|(% style="width:189px" %)**Frequency Band**|(% style="width:221px" %)5 Seconds to 150Hz

368

|(% style="width:189px" %)**Sensitivity**|(% style="width:221px" %)200 V/m/s

369

|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)158 x160mm

370

|(% style="width:189px" %)**Weight**|(% style="width:221px" %)2.8 kg

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)

UN3481 PI967 S1

)))

)))

(% class="box" %)

(((

= SmartSolo [[IGU-16HR>>url:https://smartsolo.com/cp-3.html]]3C =

382

383

[[image:smartsolo node.jpg]]

384

385

[[image:smartsolo node 2.jpg]]

386

387

|(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 1652Hz

388

|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)67.7 V/m/s

389

|(% style="width:187px" %)**Size (with spike)**|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm

390

|(% style="width:187px" %)**Weight**|(% style="width:224px" %)2.4 kg

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)

UN3481 PI967 S2

)))

)))

(% class="box" %)

(((

= 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

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

)))

(% class="box" %)

(((

= 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

|**Power**|640W

|**Weight**|26.3kg

|**Slots no.**|16

)))

(% class="box" %)

(((

= SmartSolo BD3C-5 Carry Bag =

442

443

[[image:20250729_124957.jpg]]

444

445

446

|**Dimensions (LxHxW)**|590 x 225 x 405mm

|**Weight**|8.2kg

|**Slots no.**|6

)))

(% class="box" %)

(((

= SmartSolo IGU-16 3C Carry Bag =

454

455

[[image:20250729_124502.jpg]]

456

457

|**Dimensions (LxHxW)**|230 x 340 x 310mm

|**Weight**|3.6kg

|**Slots no.**|6

)))

(% class="box" %)

(((

= SmartSolo IGU-16 1C Carry Bag =

465

466

[[image:20250729_124558.jpg]]

467

468

|**Dimensions (LxHxW)**|225 x 200 x 550mm

|**Weight**|

|**Slots no.**|6

)))

)))

)))

Wiki source code of SmartSolo Node Seismometers

Applications

Navigation