SmartSolo Node Seismometers

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

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

46

47

= **Fieldwork Preparation** =

48

49

(% class="box warningmessage" %)

50

(((

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

)))

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

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.

= **Installation** =

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

)))

72

73

== 1. Logbook documentation ==

74

75

(((

76

**Essential Details** for field logs:

77

78

* Station name

79

* Latitude, longitude, elevation

80

* Names of team members present

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)

84

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

88

)))

89

90

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

95

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

96

* Include a detailed site description in your notes

97

98

== 3. GPS Considerations ==

99

100

(% class="wikigeneratedid" %)

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.

102

103

== 4. Visibility and Location Marking ==

104

105

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

110

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

111

112

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

113

114

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

115

* **Pre-Deployment Charging**:

116

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

117

118

* **Operational Duration**:

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.

120

121

* **Post-Retrieval Charging**:

122

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

123

* **Storage and Shipping Charge Level**:

124

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

125

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

127

128

(((

129

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

143

144

== 7. Additional Best Practices ==

145

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.

----

= **Seismic Station Demobilization and Documentation** =

151

152

1. (((

153

**Preparation for Demobilization**:

154

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

159

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

166

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

173

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

179

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

185

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.

)))

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

----

= **Charging Procedure for Seismic Nodes** =

197

198

(((

199

== 1. Preparation for Charging: ==

200

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.

)))

(((

== 2. Disassembling the Node: ==

206

207

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

212

213

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

)))

(((

== 4. Monitoring the Charging Process: ==

218

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.

)))

(((

== 5. Updating Charge Status: ==

225

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

)))

229

230

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

{{{

}}}

----

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

242

243

(% class="wikigeneratedid" %)

244

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

245

246

== Connection tips: ==

247

248

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:

249

250

* Place the node on the harvester gently, then firmly press it down onto the pins.

251

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

252

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

253

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

== Node Registration and Software Setup ==

258

259

1. (((

260

**Registering Nodes in the System**:

261

262

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

263

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

264

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

265

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

266

)))

267

1. (((

268

**Creating a New Project in SoloLite**:

269

270

* Open the “SoloLite” software.

271

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

272

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

)))

== File structure ==

There are essentially three main folders where relevant PROSPECT and PROJECT DATA is stored. Individual projects will be found as subfolders in these.

=== SOLOLITE ===

This folder stores SoloLite config files and parameters. Nothing too important stored here, you can always start over and re-create this.

=== DCCDATA ===

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.

286

287

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)//

288

289

Then in the SoloLite software, go to tools > Reanalyze Seismic Data

=== SOLODATA ===

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.

294

295

296

== Data Downloading Process ==

297

298

1. (((

299

**Initiating Data Download**:

300

301

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

302

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

303

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

304

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

305

)))

306

1. (((

307

**Exporting Data in Readable Format**:

308

309

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

310

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

311

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

312

* (% class="box warningmessage" %)

313

(((

314

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

315

316

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

)))

)))

== Smart Solo Z Polarity bug (SP nodes ONLY!) ==

321

322

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

323

324

== Handling Nodes During Download ==

325

326

1. (((

327

**Monitoring Download Indicators**:

328

329

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

330

* Disconnect nodes properly before unplugging anything.

331

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

332

)))

333

1. (((

334

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

335

336

* (% class="box warningmessage" %)

337

(((

338

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

339

340

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

341

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

)))

)))

1. (((

**Metadata and Time Settings**:

346

347

* Ensure all metadata is saved with the file.

348

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

349

)))

350

1. (((

351

**Finalizing the Download**:

352

353

* 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 / wipe-down. A strong, non-wire brush is helpful to reach areas between the metal spikes on the bottom.

382

383

= **Weights (for shipping)** =

384

385

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

386

387

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

388

389

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

390

391

1 SP (IGU-16HR) charger: 26.3 kg

392

393

1 BB (BD3C-5) charger/data harvester (with and without 16 cables): 21 kg / 14.5 kg

394

395

1 case + 5 BB (BD3C-5) nodes and 6 BB nodes: 22 kg / 25 kg

396

)))

397

398

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

(((

(% class="box" %)

(((

**Contents**

)))

(% class="box" %)

(((

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

412

413

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

414

415

[[image:smartsolo.jpg]]

416

417

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

418

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

419

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

420

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

421

|(% style="width:189px" %)**Data Storage**|(% style="width:221px" %)64 Gb

422

|(% style="width:189px" %)**Battery**|(% style="width:221px" %)(((

423

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 =

432

433

[[image:smartsolo node.jpg]]

434

435

[[image:smartsolo node 2.jpg]]

436

437

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

438

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

439

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

440

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

441

|(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)64 Gb

442

|(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((

443

Lithium-ion battery contained in equipment (96.48 Wh)

UN3481 PI967 S2

)))

)))

(% class="box" %)

(((

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

454

455

456

[[image:Screenshot 2025-08-01 161027.png]]

457

458

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

459

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

460

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

461

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

462

|(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)8 Gb

463

|(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((

464

Lithium-ion battery contained in equipment (38.48 Wh)

UN3481 PI967 S2

)))

)))

(% class="box" %)

(((

= SmartSolo BD3C-16 Portable Battery Charger =

473

474

[[image:20250729_125049.jpg]]

475

476

|**Dimensions (LxHxW)**|558 x 357 x 300mm

477

|**Input rating**|100-210V - 50/60Hz

478

|**Power**|1000W

479

|**Weight**|14.5kg

480

|**Weight with cables**|21kg

481

)))

482

483

(% class="box" id="HSmartSoloBD3C-16PortableBatteryCharger" %)

484

(((

485

= SmartSolo IGU-16 Portable Data Harvester =

486

487

[[image:20250729_124747.jpg]]

488

489

|**Dimensions (LxHxW)**|625 x 500 x 366mm

490

|**Input rating**|100-210V - 50/60Hz

491

|**Power**|100W

492

|**Weight**|21.5 - 24kg

493

|**Slots no.**|16

494

|**Download Speed**|20MB/sec/slot

)))

(% class="box" %)

(((

= SmartSolo IGU-16 Portable Battery Charger =

500

501

[[image:20250729_124644.jpg]]

502

503

|**Dimensions (LxHxW)**|625 x 500 x 366mm

504

|**Input rating**|100-210V - 50/60Hz

|**Power**|640W

|**Weight**|26.3kg

|**Slots no.**|16

)))

(% class="box" %)

(((

= SmartSolo BD3C-5 Carry Case =

513

514

[[image:20250729_124957.jpg]]

515

516

517

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

|**Weight**|8.2kg

|**Slots no.**|6

)))

(% class="box" %)

(((

= SmartSolo IGU-16 3C Carry Bag =

525

526

[[image:20250729_124502.jpg]]

527

528

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

|**Weight**|3.6kg

|**Slots no.**|6

)))

(% class="box" %)

(((

= SmartSolo IGU-16 1C Carry Bag =

536

537

[[image:20250729_124558.jpg]]

538

539

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

|**Weight**|

|**Slots no.**|6

)))

)))

)))

Wiki source code of SmartSolo Node Seismometers

Applications

Navigation