Wiki source code of SmartSolo Node Seismometers

Last modified by robert on 2025/07/16 16:40

version	line-number	content
1.1	1	(% class="row" %)
	2	(((
	3	(% class="col-xs-12 col-sm-8" %)
	4	(((
42.3	5	= Node Types =
39.1	6
42.3	7	ANSIR carry two types of three-channel nodes
39.1	8
42.3	9	* SmartSolo IGU 16HR 3C (5 Hz Short Period)
43.1	10	* SmartSolo BD3C-5 (5 Second Broad-Band)
39.1	11
42.3	12	Both have a battery capacity of around 30 days. The programming, operation, and downloading procedures for both types of SmartSolo nodes are also similar.
39.1	13
	14	----
	15
42.4	16	= Programming Defaults =
17.1	17
58.1	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.
17.1	19
57.1	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.
23.1	21
43.2	22	= Fieldwork Preparation =
17.1	23
18.2	24	(% class="box warningmessage" %)
	25	(((
22.1	26	INVEST IN FAST EXTERNAL HARD DRIVES – DO NOT LET THIS BE THE LIMITATION OF DATA HARVESTING
	27
43.1	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.
60.1	29
	30	We have had good experience with the 4Tb Samsung T7 Shield drives.
17.1	31	)))
	32
57.1	33	== Magnets ==
	34
	35	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.
	40
18.2	41	= Installation =
17.1	42
62.1	43	(% 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
61.1	48	== 1. Logbook documentation ~~* TODO ADD LOGBOOK FORMS ==
17.1	49
18.2	50	(((
62.1	51	Essential Details for field logs:
18.2	52
	53	* Station name
62.1	54	* Latitude, longitude, elevation
18.2	55	* Names of team members present
62.1	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)
18.2	59
60.3	60	== 2. Node Placement ==
17.1	61	)))
	62
42.3	63	Protection: Place nodes inside (landfill) biodegradable bags to minimize cleaning and cross-site soil contamination.
17.1	64
18.2	65	Site Analysis:
	66
42.2	67	* Take compass measurements away from the sensor as it will affect your measurement.
62.1	68	* Take photographs from various angles to document the site setup thoroughly.
	69	* Include a detailed site description in your notes
18.2	70
60.3	71	== 3. GPS Considerations ==
18.2	72
20.1	73	(% class="wikigeneratedid" %)
43.2	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.
20.1	75
60.3	76	== 4. Visibility and Location Marking ==
20.1	77
18.2	78	Flag Placement: Position a flag, preferably in a bright color (avoid green or yellow), near the instrument to aid in its future location.
	79
	80	GPS Marking:
	81
	82	* 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
60.3	85	== (% style="color:inherit; font-family:inherit; font-size:max(18px, min(20px, 14.4444px + 0.462963vw))" %)5. Charge Time, Pre-Deployment & Post-Deployment(%%) ==
18.3	86
20.1	87	* Charging Duration: Both types of nodes take approximately 6-8 hours to fully charge from a flat state.
	88	* Pre-Deployment Charging:
42.2	89	** Although the nodes hold their charge well, it's beneficial to give them a "top up" charge before deployment.
20.1	90
	91	* Operational Duration:
42.2	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.
20.1	93
	94	* Post-Retrieval Charging:
42.2	95	** After retrieval, charge the instruments to about 50-60% (indicated as "orange" level) unless they are to be immediately re-deployed.
20.1	96	* Storage and Shipping Charge Level:
43.2	97	** Maintain a battery charge level of around 50-60% (e.g. "orange") for both storage and shipping purposes.
20.1	98	** This charge level is recommended to prevent battery damage and is safe for transportation.
60.4	99	Nodes should not be stored fully charged, and they should especially not be stored with 0 charge as this damages lithium batteries.**
20.1	100
42.2	101	(((
60.3	102	== 6. Data Sharing and Metadata Creation ==
28.1	103	)))
20.1	104
18.3	105	GPS Data:
	106
43.2	107	* Ensure you have documented precise lat/lon locations for each station and DOCUMENTED THIS CAREFULLY
18.3	108
	109	Photo Sharing:
	110
43.2	111	* It is strongly encouraged to take pictures of each site and upload these to a shared platform (OneDrive, Dropbox, etc.).
18.3	112
	113	Metadata File:
	114
60.3	115	* 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.
18.3	116
60.3	117	== 7. Additional Best Practices ==
18.3	118
43.2	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.
18.3	120
24.2	121	----
18.3	122
43.2	123	= Seismic Station Demobilization and Documentation =
24.1	124
	125	1. (((
	126	Preparation for Demobilization:
	127
43.2	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.
24.1	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
43.2	140	* Write the station name and the instrument’s serial number on a masking tape label to apply to the top of the node.
24.1	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.
39.1	161
	162
24.1	163	)))
	164
40.1	165	[[image:1706153556166-231.jpeg\|\|data-xwiki-image-style-alignment="center" height="345" width="460"]]
37.2	166
24.2	167	----
24.1	168
43.2	169	= Charging Procedure for Seismic Nodes =
24.1	170
45.1	171	(((
60.3	172	== 1. Preparation for Charging: ==
24.1	173
24.2	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.
	175	)))
24.1	176
45.1	177	(((
60.3	178	== 2. Disassembling the Node: ==
45.1	179
42.2	180	* For the IGU-16HR, remove the battery (bottom half) from the sensor. This is done by unscrewing the spikes counter-clockwise.
24.2	181	)))
24.1	182
45.1	183	(((
60.3	184	== 3. Setting Nodes in the Charging Box: ==
45.1	185
42.2	186	* Place 1-16 IGU-16HR battery components upside-down into the charger, assuring they are oriented properly.
24.2	187	)))
24.1	188
45.1	189	(((
60.3	190	== 4. Monitoring the Charging Process: ==
45.1	191
42.2	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.
24.2	194	)))
24.1	195
45.1	196	(((
60.3	197	== 5. Updating Charge Status: ==
45.1	198
34.2	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.
24.2	200	* This step is crucial for tracking the charging status of multiple units, especially when handling a large number of nodes.
	201	)))
24.1	202
39.1	203	[[IGU 16-HRcharger (left) and harvester (right)>>image:1705195933422-337.png\|\|data-xwiki-image-style-alignment="center" height="299" width="530"]]
36.2	204
	205
37.2	206
	207
39.1	208	[[image:1706153354750-415.png\|\|data-xwiki-image-style-alignment="center" height="317" width="562"]]
37.2	209
24.2	210	----
24.1	211
45.2	212	= Downloading and Converting Seismic Data to MiniSeed Format =
24.1	213
60.3	214	== Node Registration and Software Setup ==
24.1	215
24.2	216	1. (((
	217	Registering Nodes in the System:
24.1	218
24.2	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:
24.1	226
24.2	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
60.3	232	== Data Downloading Process ==
24.2	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.
29.1	248	* (% class="box warningmessage" %)
	249	(((
61.1	250	* Ensure to export data as "COUNTS" (int32), not "mV" (float). This is critical!
24.2	251
61.1	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.
27.1	253	)))
	254	)))
24.4	255
60.3	256	== Handling Nodes During Download ==
24.2	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. (((
35.1	266	//Investment in Storage Hardware~://
24.2	267
28.1	268	* (% class="box warningmessage" %)
	269	(((
31.2	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.
61.1	273	* The USB type for the harvester is TYPE-A, the typical normal rectangular shape.
24.2	274	)))
28.1	275	)))
24.2	276	1. (((
	277	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
34.1	285	* After downloading, mark the //"D"// box on your temporary labels to indicate completion.
36.1	286
	287
24.2	288	)))
	289
39.1	290	[[image:1706153266647-145.png\|\|data-xwiki-image-style-alignment="center" height="340" width="603"]]
36.2	291
	292
	293
39.1	294	[[Caption>>image:1705195543887-977.png\|\|data-xwiki-image-style-alignment="center" height="534" width="632"]]
36.2	295
	296
	297
	298
39.1	299	[[Caption>>image:1705195543890-537.png\|\|data-xwiki-image-style-alignment="center" height="397" width="665"]]
36.2	300
37.1	301
36.2	302
39.1	303	[[Caption>>image:1705195543891-334.png\|\|data-xwiki-image-style-alignment="center" height="379" width="650"]]
	304
	305
	306
	307	[[image:1705195543898-365.png\|\|data-xwiki-image-style-alignment="center" height="467" width="674"]]
	308
36.1	309	----
	310
45.5	311	= Cleaning =
36.1	312
59.1	313	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.
36.1	314
48.1	315	= Weights (for shipping) =
	316
	317	The weights of bags of nodes, as well as data harvesters and node chargers, are listed below:
	318
49.1	319	1 bag + 6 SP (IGU-16HR) nodes: 18 kg
48.1	320
49.1	321	1 SP (IGU-16HR) data harvester: 21.5 kg
48.1	322
49.1	323	1 SP (IGU-16HR) charger: 26.3 kg
48.1	324
49.1	325	1 BB (BD3C-5) charger/data harvester (with and without 16 cables): 21 kg / 14.5 kg
48.1	326
49.1	327	1 case + 5 BB (BD3C-5) nodes and 6 BB nodes: 22 kg / 25 kg
8.3	328	)))
	329
1.1	330	(% class="col-xs-12 col-sm-4" %)
	331	(((
10.1	332	(% class="box" %)
	333	(((
	334	Contents
1.1	335
44.1	336	{{toc/}}
	337
43.2	338
10.1	339	)))
1.1	340
11.1	341	(% class="box" %)
10.1	342	(((
11.1	343	= SmartSolo [[BD3C-5>>url:https://smartsolo.com/cp-4.html]] =
12.1	344
15.1	345	[[image:Smartsolo IGU BD3C 5 (2).jpg]]
	346
16.1	347	[[image:smartsolo.jpg]]
	348
13.2	349	\|(% style="width:189px" %)Frequency Band\|(% style="width:221px" %)5 Seconds to 150Hz
	350	\|(% style="width:189px" %)Sensitivity\|(% style="width:221px" %)200 V/m/s
	351	\|(% style="width:189px" %)Size (without spike)\|(% style="width:221px" %)158 x160mm
	352	\|(% style="width:189px" %)Weight\|(% style="width:221px" %)2.8 kg
	353	\|(% style="width:189px" %)Data Storage\|(% style="width:221px" %)64 Gb
49.3	354	\|(% style="width:189px" %)Battery\|(% style="width:221px" %)(((
	355	Lithium-ion battery contained in equipment (168.84 Wh)
	356
	357	UN3481 PI967 S1
12.1	358	)))
49.3	359	)))
11.1	360
12.1	361	(% class="box" %)
	362	(((
	363	= SmartSolo [[IGU-16HR>>url:https://smartsolo.com/cp-3.html]] =
11.1	364
16.1	365	[[image:smartsolo node.jpg]]
	366
	367	[[image:smartsolo node 2.jpg]]
	368
13.2	369	\|(% style="width:187px" %)Frequency Band\|(% style="width:224px" %)5 Hz to 1652Hz
	370	\|(% style="width:187px" %)Sensitivity\|(% style="width:224px" %)67.7 V/m/s
	371	\|(% style="width:187px" %)Size (with spike)\|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm
42.2	372	\|(% style="width:187px" %)Weight\|(% style="width:224px" %)2.4 kg
13.2	373	\|(% style="width:187px" %)Data Storage\|(% style="width:224px" %)64 Gb
49.2	374	\|(% style="width:187px" %)Battery\|(% style="width:224px" %)(((
49.3	375	Lithium-ion battery contained in equipment (96.48 Wh)
49.2	376
	377	UN3481 PI967 S2
10.1	378	)))
49.2	379	)))
4.1	380
9.2	381
1.1	382	)))
	383	)))

Wiki source code of SmartSolo Node Seismometers

Applications

Navigation