Wiki source code of SmartSolo Node Seismometers

Last modified by robert on 2026/02/27 19:58

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
90.1	7	ANSIR supply two types of three-channel nodes, and one type of one-channel node:
39.1	8
105.2	9	* SmartSolo IGU-16HR 3C (5 Hz, 'very' short period)
94.4	10	* SmartSolo BD3C-5 (5 second, short period)
105.2	11	* SmartSolo IGU-16 1C (5 Hz, 'very' short period, single channel. Not 'HR')
39.1	12
105.2	13	Visit the [[SmartSolo page>>https://smartsolo.com/igu.html]] for more detail.
	14
91.2	15	The three-channel nodes have a theoretical 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.
39.1	16
90.1	17	(% class="box infomessage" %)
	18	(((
91.1	19	Freight update, 2026: Freight options for lithium-ion batteries are changing in 2025/2026 to comply with updated transport safety regulations. This will impact supply of IGU 16 (<100Wh) and BD3C (168Wh) nodes. Advice will be sought from freighters on a case-by-case basis while they implement new guidelines.
90.1	20	)))
	21
39.1	22	----
	23
42.4	24	= Programming Defaults =
17.1	25
94.2	26	The nodes must be programmed in the SoloLite software prior to use. The screenshots below show our recommended parameters for the 5 Hz (16HR-3C) and 5 second (BDC3-5) nodes.
17.1	27
98.1	28	[[IGU16HR-3C programming screen set at 250 Hz. Ensure circled areas are set!>>image:5Hz_node_programming.labels.png\|\|alt="IGU-16 3C programming screen"]]
74.2	29
97.1	30	[[BD3C-5 programming screen set at 250 Hz. Ensure circled areas are set!>>image:5S_node_programming.labels.png\|\|alt="BD3C-5 programming screen set at 250 hz. Ensure that the circled areas are set!"]]
74.2	31
96.2	32
74.2	33	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.
	34
75.2	35	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.
	36
74.2	37	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.
	38
75.1	39	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!
	40
74.2	41	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.
	42
75.1	43	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.
74.2	44
75.1	45	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.
74.2	46
94.4	47	Bluetooth (BD3C-5 only) should be turned OFF to conserve power.
75.1	48
94.4	49	We recommend that the 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).
74.2	50
75.1	51	{{info}}
	52	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!
	53	{{/info}}
23.1	54
43.2	55	= Fieldwork Preparation =
17.1	56
18.2	57	(% class="box warningmessage" %)
	58	(((
22.1	59	INVEST IN FAST EXTERNAL HARD DRIVES – DO NOT LET THIS BE THE LIMITATION OF DATA HARVESTING
	60
43.1	61	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	62
	63	We have had good experience with the 4Tb Samsung T7 Shield drives.
17.1	64	)))
	65
57.1	66	== Magnets ==
	67
	68	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).
	69
	70	== Animal-Proofing ==
	71
94.4	72	We have experienced interference from animals (foxes, dogs, goats) digging up and carrying nodes off for tens or hundreds of metres. It is helpful to minimise human and food smells (particularly on the rope handles) when working in areas where this is a risk. Or, wipe down affected nodes with 50-80% methylated spirits if extensive handling can not be avoided.
57.1	73
98.1	74	If you come to collect your node and it is missing~-~- LOOK FOR IT! It may not have gotten far. We have found dozens of nodes by spending 15 minutes looking for them.
	75
18.2	76	= Installation =
17.1	77
62.1	78	(% class="box infomessage" %)
	79	(((
	80	Field logs are a critical component of fieldwork and this is especially the case for large N nodal deploys. Take notes!
	81	)))
	82
64.1	83	== 1. Logbook documentation ==
17.1	84
18.2	85	(((
62.1	86	Essential Details for field logs:
18.2	87
	88	* Station name
62.1	89	* Latitude, longitude, elevation
18.2	90	* Names of team members present
62.1	91	* Date and both local & UTC time of installation/removal
	92	* Serial number (SN) of the TOP HALF of the sensor (if a BD3C-5, there is only one serial number)
	93	* 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	94
64.1	95	[[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!
	96
60.3	97	== 2. Node Placement ==
17.1	98	)))
	99
18.2	100	Site Analysis:
	101
42.2	102	* Take compass measurements away from the sensor as it will affect your measurement.
62.1	103	* Take photographs from various angles to document the site setup thoroughly.
	104	* Include a detailed site description in your notes
18.2	105
60.3	106	== 3. GPS Considerations ==
18.2	107
20.1	108	(% class="wikigeneratedid" %)
43.2	109	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	110
60.3	111	== 4. Visibility and Location Marking ==
20.1	112
18.2	113	Flag Placement: Position a flag, preferably in a bright color (avoid green or yellow), near the instrument to aid in its future location.
	114
	115	GPS Marking:
	116
	117	* Use a GPS device to mark the instrument's exact location.
	118	* Record this location in both your paper notes and the GPS device.
	119
60.3	120	== (% 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	121
20.1	122	* Charging Duration: Both types of nodes take approximately 6-8 hours to fully charge from a flat state.
	123	* Pre-Deployment Charging:
42.2	124	** Although the nodes hold their charge well, it's beneficial to give them a "top up" charge before deployment.
20.1	125
	126	* Operational Duration:
42.2	127	** 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	128
	129	* Post-Retrieval Charging:
94.4	130	** After retrieval, charge the instruments to about 50-60% (indicated by ORANGE LED) unless they are to be immediately re-deployed or transported.
	131	* State of Charge (SoC) for Storage:
	132	** Maintain a battery charge level of around 50-60% (i.e., ORANGE) for storage.
	133	** This charge level is recommended to prevent battery damage, and should be checked every six months.
94.5	134	** Nodes should //__not be stored at full-charge (GREEN), or 0-charge (RED).__//
94.4	135	Storage at 0-charge damages lithium batteries.**
	136	* SoC for Transport:
94.5	137	** Charge levels for transport will be advised by the freighter. The required SoC will depend on volume and transport method (air, land, sea).
20.1	138
42.2	139	(((
60.3	140	== 6. Data Sharing and Metadata Creation ==
28.1	141	)))
20.1	142
18.3	143	GPS Data:
	144
94.4	145	* Ensure you have __carefully documented__ precise lat/lon locations for each station.
18.3	146
	147	Photo Sharing:
	148
43.2	149	* It is strongly encouraged to take pictures of each site and upload these to a shared platform (OneDrive, Dropbox, etc.).
18.3	150
	151	Metadata File:
	152
60.3	153	* 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	154
60.3	155	== 7. Additional Best Practices ==
18.3	156
43.2	157	* 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	158
24.2	159	----
18.3	160
43.2	161	= Seismic Station Demobilization and Documentation =
24.1	162
	163	1. (((
	164	Preparation for Demobilization:
	165
43.2	166	* 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	167	)))
	168	1. (((
	169	Locating the instrument:
	170
	171	* Use the downloaded GPS file to accurately locate the node for demobilization.
	172	* Import this KMZ file onto your phone for easy reference and location tracking.
	173	* Utilize Google Maps or Google Earth to create a KMZ file of the station’s location.
	174	)))
	175	1. (((
	176	Labeling Instruments for Demobilization:
	177
43.2	178	* 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	179	* Add markers 'D' (for download), 'C' (for charge), and ‘R’ (for removal) next to checkboxes on the label.
	180	* Affix this label to the top of the instrument to avoid confusion during the charging and downloading data.
	181	)))
	182	1. (((
	183	Photographing the Setup Node:
	184
	185	* Take a photo of the entire setup node with the __//label//__ and __//compass visible//__.
	186	* This photo serves as a final record of the instrument’s condition and orientation at the time of removal.
	187	)))
	188	1. (((
	189	Logging Demobilization Details:
	190
	191	* Use the field logbook to note the time of demobilization, serial numbers, and station name.
	192	* Record any observations or issues related to the instrument’s orientation, level, or any other relevant factors.
	193	)))
	194	1. (((
	195	Final Checks and Equipment Removal:
	196
	197	* Before physically removing the instrument, double-check that all necessary data has been downloaded and all photos and notes have been taken.
	198	* Carefully dismantle and pack the equipment, ensuring that all components are accounted for and securely stored for transport.
39.1	199
	200
24.1	201	)))
	202
40.1	203	[[image:1706153556166-231.jpeg\|\|data-xwiki-image-style-alignment="center" height="345" width="460"]]
37.2	204
24.2	205	----
24.1	206
43.2	207	= Charging Procedure for Seismic Nodes =
24.1	208
45.1	209	(((
60.3	210	== 1. Preparation for Charging: ==
24.1	211
24.2	212	* 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.
	213	)))
24.1	214
45.1	215	(((
60.3	216	== 2. Disassembling the Node: ==
45.1	217
94.4	218	* For the IGU-16HR, remove the battery section (bottom half) from the sensor by unscrewing the spike section counter-clockwise.
24.2	219	)))
24.1	220
45.1	221	(((
60.3	222	== 3. Setting Nodes in the Charging Box: ==
45.1	223
94.4	224	* Connect to a safe indoor power supply, and turn on (red rocker switch).
	225	* Charging will begin automatically when nodes are inserted in the charging rack.
	226	* Place IGU-16HR battery sections upside-down in the rack, oriented with the terminal connectors.
24.2	227	)))
24.1	228
45.1	229	(((
60.3	230	== 4. Monitoring the Charging Process: ==
45.1	231
94.4	232	* Lights adjacent to the batteries will illuminate, indicating that charging is underway.
	233	* Observe the transition of the lights from steady RED to ORANGE, then GREEN, and finally to FLASHING GREEN. A flashing green light indicates the batteries are fully charged.
24.2	234	)))
24.1	235
45.1	236	(((
60.3	237	== 5. Updating Charge Status: ==
45.1	238
34.2	239	* 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	240	* This step is crucial for tracking the charging status of multiple units, especially when handling a large number of nodes.
	241	)))
24.1	242
39.1	243	[[IGU 16-HRcharger (left) and harvester (right)>>image:1705195933422-337.png\|\|data-xwiki-image-style-alignment="center" height="299" width="530"]]
36.2	244
	245
37.2	246
	247
88.1	248	{{{
89.1	249	}}}
37.2	250
24.2	251	----
24.1	252
45.2	253	= Downloading and Converting Seismic Data to MiniSeed Format =
24.1	254
86.1	255	(% class="wikigeneratedid" %)
	256	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]]
	257
86.2	258	== Connection tips: ==
86.1	259
	260	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:
	261
86.2	262	* Place the node on the harvester gently, then firmly press it down onto the pins.
	263	* 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.
	264	* 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.
	265	* 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!
86.1	266
	267
	268
60.3	269	== Node Registration and Software Setup ==
24.1	270
24.2	271	1. (((
	272	Registering Nodes in the System:
24.1	273
24.2	274	* To begin, register the nodes in the system so the software can recognize them.
	275	* Navigate to the installation folder of “SmartSoloApps SoloLite”.
	276	* Right-click on deviceconfig.exe and choose “run as an administrator”. Save the file to the “deviceconfig” directory (refer to the snapshot below).
	277	* To avoid double registration, replace the file each time you register a new node.
	278	)))
	279	1. (((
	280	Creating a New Project in SoloLite:
24.1	281
24.2	282	* Open the “SoloLite” software.
	283	* Go to “File” and create a new project. Don't worry about finding the exact 16 nodes used in script writing.
	284	* Ignore the settings for seismic recordings in the subsequent window. Resetting instruments (e.g., sampling rate, gain) requires reprogramming via script.
	285	)))
	286
88.1	287	== File structure ==
	288
	289	There are essentially three main folders where relevant PROSPECT and PROJECT DATA is stored. Individual projects will be found as subfolders in these.
	290
	291	=== SOLOLITE ===
	292
	293	This folder stores SoloLite config files and parameters. Nothing too important stored here, you can always start over and re-create this.
	294
	295	=== DCCDATA ===
	296
	297	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.
	298
	299	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)//
	300
	301	Then in the SoloLite software, go to tools > Reanalyze Seismic Data
	302
	303	=== SOLODATA ===
	304
	305	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.
	306
	307
60.3	308	== Data Downloading Process ==
24.2	309
	310	1. (((
	311	Initiating Data Download:
	312
	313	* Once a new project is created, the Data Transfer View panel will display connected nodes with details like series number and data size.
	314	* If “Prospect not matched” appears, it simply means the new project doesn’t match the original programming project. This is not a concern.
	315	* Select all nodes and right-click to “force download”. This starts the download process.
	316	* Completed downloads will appear as new folders in the Downloaded Data panel.
	317	)))
	318	1. (((
	319	Exporting Data in Readable Format:
	320
	321	* Go to the “Tool” menu and select “export seismic data”.
	322	* Tailor other parameters to personal preference and ensure "Sample Interval" matches the setting used during node reset.
	323	* Click “prepare” followed by “run” to start reformatting. Monitor this process in the small panel at the bottom left.
29.1	324	* (% class="box warningmessage" %)
	325	(((
61.1	326	* Ensure to export data as "COUNTS" (int32), not "mV" (float). This is critical!
24.2	327
61.1	328	* 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	329	)))
	330	)))
24.4	331
91.2	332	== Smart Solo IGU-16HR Polarity Notice ==
82.1	333
99.1	334	See [[5Hz Node Polarity Issues>>https://auspass.edu.au/xwiki/bin/view/Data/AusPass%20Data/#HSmartSoloNodePolarityIssues]] for discussion. If data is headed to AusPass, we prefer to invert the IGU-16HR channel data manually rather than in the SoloLite software or inverting the response metadata.
82.1	335
98.1	336	The BD3C-5 data does not require any sort of polarity inversion.
91.2	337
89.1	338	== 18 Leap Second bug ==
	339
91.2	340	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 constant 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.
89.1	341
	342	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.
	343
	344	{{code language="none"}}
	345	<?xml version="1.0" encoding="UTF-8"?>
	346	<config>
	347	<leapsecond>
	348	<interval>
	349	<start_time>2017-01-01#00:00:00</start_time>
	350	<end_time>2999-12-31#23:59:59</end_time>
	351	<second>18</second>
	352	</interval>
	353	<interval>
	354	<start_time>1970-01-01#00:00:00</start_time>
	355	<end_time>2017-01-01#00:00:00</end_time>
	356	<second>17</second>
	357	</interval>
	358	</leapsecond>
	359	<GPS_distance_threshold_degree>
	360	4e-5
	361	</GPS_distance_threshold_degree>
	362	</config>
	363	{{/code}}
	364
	365
60.3	366	== Handling Nodes During Download ==
24.2	367
	368	1. (((
	369	Monitoring Download Indicators:
	370
	371	* During download, green lights on nodes will blink, and associated red lights on the rack will flash.
	372	* Disconnect nodes properly before unplugging anything.
	373	* Be cautious: if the laptop enters sleep mode, the download will pause.
	374	)))
	375	1. (((
35.1	376	//Investment in Storage Hardware~://
24.2	377
28.1	378	* (% class="box warningmessage" %)
	379	(((
31.2	380	* Use fast external hard drives to avoid limitations in data harvesting.
	381
	382	* Recommended specifications: USB-C, USB 3.0, and 4+ Tb of space.
61.1	383	* The USB type for the harvester is TYPE-A, the typical normal rectangular shape.
24.2	384	)))
28.1	385	)))
24.2	386	1. (((
	387	Metadata and Time Settings:
	388
	389	* Ensure all metadata is saved with the file.
	390	* 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.
	391	)))
	392	1. (((
	393	Finalizing the Download:
	394
34.1	395	* After downloading, mark the //"D"// box on your temporary labels to indicate completion.
36.1	396
	397
24.2	398	)))
	399
39.1	400	[[image:1706153266647-145.png\|\|data-xwiki-image-style-alignment="center" height="340" width="603"]]
36.2	401
	402
	403
39.1	404	[[Caption>>image:1705195543887-977.png\|\|data-xwiki-image-style-alignment="center" height="534" width="632"]]
36.2	405
	406
	407
	408
39.1	409	[[Caption>>image:1705195543890-537.png\|\|data-xwiki-image-style-alignment="center" height="397" width="665"]]
36.2	410
37.1	411
36.2	412
39.1	413	[[Caption>>image:1705195543891-334.png\|\|data-xwiki-image-style-alignment="center" height="379" width="650"]]
	414
	415
	416
	417	[[image:1705195543898-365.png\|\|data-xwiki-image-style-alignment="center" height="467" width="674"]]
	418
36.1	419	----
	420
102.1	421	= Instrument Response =
	422
103.1	423	We are aware that there are various different published responses for these instruments and trust very few of them. One has to be careful with how polarity is handled between groups as well, and if one is working in integer counts (the ANSIR default) or mV (unclear why anyone would use this as it makes file sizes enormous). The response information published below is in counts and seems to fit well in huddle tests. Note that the response is the same for all channels and all units (e.g. there are no bespoke calibrations!), all appear to be sample rate insensitive, and the IGU data has been inverted (multiplied by -1) as described here: [[5Hz Node Polarity Issues>>https://auspass.edu.au/xwiki/bin/view/Data/AusPass%20Data/#HSmartSoloNodePolarityIssues]]
102.1	424
103.1	425	== IGU 16HR-3C ==
102.1	426
	427	'16HR3C': {'poles':[(-22.211059+22.217768j), (-22.211059-22.217768j)],
	428	'zeros':[0j, 0j],
	429	'gain':1,
	430	'sensitivity': 257019225.55108312}
	431
104.2	432	[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:IGU16_Z_huddle.png]]
102.1	433
107.2	434	[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz bandpass filter>>image:IGU16_N_huddle.png]]
102.1	435
103.1	436	== IGU 16-1C ==
102.1	437
107.1	438	The 1C nodes seem to have the same response as the 3-channel IGU-16HR-3C (above), however the response posted at IRIS-NRL seems to imply that there is no poles and zeros information (e.g. a flat/linear response). This is 100% not so.
104.1	439
107.2	440	[[IGU-16 1C, X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz bandpass filter. Seems to be same response as IGU-16HR-3C.>>image:IGU16_1C_Z_huddle.png]]
107.1	441
102.1	442	== BD3C-5 ==
	443
	444	'BD3C': {'poles':[(-1720.4+0j), (-1.2+0.9j), (-1.2-0.9j)],
	445	'zeros':[(14164+0j), (-7162+0j), 0j, 0j],
	446	'gain':1.69726e-05,
	447	'sensitivity': 702651512.6046528}
	448
108.1	449	Above 0.5 Hz, the BD3C-5 response fits well:
104.1	450
108.1	451	[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:BD3C_Z_huddle.0.5.png]]
105.3	452
108.1	453	[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz bandpass filter>>image:BD3C_N_huddle.0.5.png]]
	454
105.5	455	(% class="wikigeneratedid" %)
109.1	456	Below the corner frequency (0.2 Hz) the phase response still fares well, but amplitude response may need to be dialed in a bit (it seems a bit high). In the next two figures the filter is 0.1 to 5 Hz:
105.5	457
	458
107.2	459	[[BD3C 0.1 to 5 Hz bandpass filter>>image:BD3C_Z_huddle.0.1.png]]
105.5	460
107.2	461	[[BD3C 0.1 to 5 Hz bandpass filter>>image:BD3C_N_huddle.0.1.png]]
105.5	462
105.4	463	== IGU-16 Horizontal noise & how to avoid ==
102.1	464
107.1	465	The 5 Hz nodes are susceptible to horizontal noise due to the placement of geophones in the units, but this can be mitigated by completely burying the units flush with the ground. In the below example, the node was set on the floor of our basement set on its plastic carrying case support. As such the amount of horizontal noise noticeably increases above ~~ 10Hz.
102.1	466
105.3	467	[[IGU-16HR-3C Power spectrum huddle test vs a CMG-6TD (S1) and TC120/Centaur combo. The N and E channels have excess noise above 10Hz due to "sticking up" out of the ground.>>image:IGU16_spectrum.png]]
102.1	468
105.3	469	(% class="wikigeneratedid" %)
	470	The BD3C-5 nodes do not have this issue:
	471
	472	[[BD3C-5 test, as above. There is no additional noise on the horizontal channels.>>image:BD3C_psd.png]]
	473
45.5	474	= Cleaning =
36.1	475
105.1	476	When assembled, the nodes are water resistant but not submersible. They can handle a good spray and wipe-down. A stiff plastic brush is helpful to reach areas between the metal spikes on the bottom.
36.1	477
48.1	478	= Weights (for shipping) =
	479
	480	The weights of bags of nodes, as well as data harvesters and node chargers, are listed below:
	481
95.1	482	1 bag + 6*IGU-16HR nodes: 18 kg
48.1	483
95.1	484	1*IGU-16HR data harvester: 21.5 kg
48.1	485
95.1	486	1*IGU-16HR charger: 26.3 kg
48.1	487
95.1	488	1*BD3C-5 charger (with and without 16 cables): 21 kg / 14.5 kg
48.1	489
95.1	490	1 case + 5*BD3C-5 nodes: 22 kg (aggregate battery weight <5kg, 168Wh)
	491
	492	1 case + 6*BD3C-5 nodes: 25 kg (aggregate battery weight >5kg, 168Wh)
8.3	493	)))
	494
1.1	495	(% class="col-xs-12 col-sm-4" %)
	496	(((
10.1	497	(% class="box" %)
	498	(((
	499	Contents
1.1	500
44.1	501	{{toc/}}
	502
43.2	503
10.1	504	)))
1.1	505
11.1	506	(% class="box" %)
10.1	507	(((
11.1	508	= SmartSolo [[BD3C-5>>url:https://smartsolo.com/cp-4.html]] =
12.1	509
15.1	510	[[image:Smartsolo IGU BD3C 5 (2).jpg]]
	511
16.1	512	[[image:smartsolo.jpg]]
	513
13.2	514	\|(% style="width:189px" %)Frequency Band\|(% style="width:221px" %)5 Seconds to 150Hz
	515	\|(% style="width:189px" %)Sensitivity\|(% style="width:221px" %)200 V/m/s
81.1	516	\|(% style="width:189px" %)Size (without spike)\|(% style="width:221px" %)Φ158 x160mm(H)
13.2	517	\|(% style="width:189px" %)Weight\|(% style="width:221px" %)2.8 kg
	518	\|(% style="width:189px" %)Data Storage\|(% style="width:221px" %)64 Gb
49.3	519	\|(% style="width:189px" %)Battery\|(% style="width:221px" %)(((
	520	Lithium-ion battery contained in equipment (168.84 Wh)
	521
	522	UN3481 PI967 S1
12.1	523	)))
49.3	524	)))
11.1	525
12.1	526	(% class="box" %)
	527	(((
69.1	528	= SmartSolo [[IGU-16HR>>url:https://smartsolo.com/cp-3.html]]3C =
11.1	529
16.1	530	[[image:smartsolo node.jpg]]
	531
	532	[[image:smartsolo node 2.jpg]]
	533
13.2	534	\|(% style="width:187px" %)Frequency Band\|(% style="width:224px" %)5 Hz to 1652Hz
79.1	535	\|(% style="width:187px" %)Sensitivity\|(% style="width:224px" %)76.7 V/m/s
81.1	536	\|(% style="width:187px" %)Size (with spike)\|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm(H)
42.2	537	\|(% style="width:187px" %)Weight\|(% style="width:224px" %)2.4 kg
13.2	538	\|(% style="width:187px" %)Data Storage\|(% style="width:224px" %)64 Gb
49.2	539	\|(% style="width:187px" %)Battery\|(% style="width:224px" %)(((
49.3	540	Lithium-ion battery contained in equipment (96.48 Wh)
49.2	541
	542	UN3481 PI967 S2
10.1	543	)))
49.2	544	)))
4.1	545
66.1	546	(% class="box" %)
	547	(((
79.1	548
	549
	550	= SmartSolo [[IGU-16>>url:https://smartsolo.com/cp-3.html]]1C =
	551
	552
	553	[[image:Screenshot 2025-08-01 161027.png]]
	554
	555	\|(% style="width:187px" %)Frequency Band\|(% style="width:224px" %)5 Hz to 413Hz
	556	\|(% style="width:187px" %)Sensitivity\|(% style="width:224px" %)80 V/m/s
81.1	557	\|(% style="width:187px" %)Size (without spike)\|(% style="width:224px" %)95mm(L) × 103mm(W) × 118mm(H)
79.1	558	\|(% style="width:187px" %)Weight\|(% style="width:224px" %)1.1 kg
80.1	559	\|(% style="width:187px" %)Data Storage\|(% style="width:224px" %)8 Gb
79.1	560	\|(% style="width:187px" %)Battery\|(% style="width:224px" %)(((
80.1	561	Lithium-ion battery contained in equipment (38.48 Wh)
79.1	562
	563	UN3481 PI967 S2
	564	)))
	565	)))
	566
	567	(% class="box" %)
	568	(((
65.1	569	= SmartSolo BD3C-16 Portable Battery Charger =
	570
68.1	571	[[image:20250729_125049.jpg]]
65.1	572
	573	\|Dimensions (LxHxW)\|558 x 357 x 300mm
	574	\|Input rating\|100-210V - 50/60Hz
	575	\|Power\|1000W
101.1	576	\|Weight\|14.5 kg
	577	\|Weight with cables\|21 kg
66.1	578	)))
65.1	579
66.1	580	(% class="box" id="HSmartSoloBD3C-16PortableBatteryCharger" %)
	581	(((
	582	= SmartSolo IGU-16 Portable Data Harvester =
65.1	583
68.1	584	[[image:20250729_124747.jpg]]
65.1	585
	586	\|Dimensions (LxHxW)\|625 x 500 x 366mm
	587	\|Input rating\|100-210V - 50/60Hz
	588	\|Power\|100W
101.1	589	\|Weight\|21.5 - 24 kg
	590	\|Capacity\|16 nodes
65.1	591	\|Download Speed\|20MB/sec/slot
66.1	592	)))
65.1	593
67.1	594	(% class="box" %)
	595	(((
	596	= SmartSolo IGU-16 Portable Battery Charger =
66.1	597
75.2	598	[[image:20250729_124644.jpg]]
66.1	599
101.1	600	\|Dimensions (LxHxW)\|625 x 500 x 366 mm
	601	\|Input rating\|100-210V - 50/60 Hz
	602	\|Power\|640 W
	603	\|Weight\|26.3 kg
	604	\|Capacity\|16 nodes
67.1	605	)))
65.1	606
72.1	607	(% class="box" %)
	608	(((
75.2	609	= SmartSolo BD3C-5 Carry Case =
65.1	610
72.1	611	[[image:20250729_124957.jpg]]
67.1	612
68.1	613
101.1	614	\|Dimensions (LxHxW)\|590 x 225 x 405 mm
	615	\|Weight\|8.2 kg
	616	\|Capacity\|6 nodes
72.1	617	)))
69.1	618
67.1	619	(% class="box" %)
	620	(((
70.1	621	= SmartSolo IGU-16 3C Carry Bag =
67.1	622
68.1	623	[[image:20250729_124502.jpg]]
	624
65.1	625	\|Dimensions (LxHxW)\|230 x 340 x 310mm
100.1	626	\|Weight\|(((
	627	3.6kg (empty)
	628
	629	18.0kg (full)
67.1	630	)))
101.1	631	\|Capacity\|6 nodes
100.1	632	)))
65.1	633
67.1	634	(% class="box" %)
	635	(((
70.1	636	= SmartSolo IGU-16 1C Carry Bag =
67.1	637
68.1	638	[[image:20250729_124558.jpg]]
	639
71.1	640	\|Dimensions (LxHxW)\|225 x 200 x 550mm
74.1	641	\|Weight\|
101.1	642	\|Capacity\|8 nodes
1.1	643	)))
	644	)))
67.1	645	)))

Wiki source code of SmartSolo Node Seismometers

Applications

Navigation