Wiki source code of SmartSolo Node Seismometers

Version 112.1 by robert on 2026/06/17 16:54

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
112.1	76	= External Power =
	77
	78	Both the 5Hz IGU-16HR and 5s BD3C-5 can be optionally powered via external battery via either a replacement bottom half (the 5Hz nodes) or a battery cable accessory (BD3C-5) using standard lead acid batteries from 9-36v. We have done preliminary testing at 250 Hz with a 12v battery:
	79
	80	- BD3C-5: ~~2 days of recording per 1 Ah
	81
	82	- IGU16-HR 3C: ~~3.5 days of recording per 1 Ah
	83
	84	- IGU16-HR 1C: ~~7 days of recording per 1 Ah
	85
18.2	86	= Installation =
17.1	87
62.1	88	(% class="box infomessage" %)
	89	(((
	90	Field logs are a critical component of fieldwork and this is especially the case for large N nodal deploys. Take notes!
	91	)))
	92
64.1	93	== 1. Logbook documentation ==
17.1	94
18.2	95	(((
62.1	96	Essential Details for field logs:
18.2	97
	98	* Station name
62.1	99	* Latitude, longitude, elevation
18.2	100	* Names of team members present
62.1	101	* Date and both local & UTC time of installation/removal
	102	* Serial number (SN) of the TOP HALF of the sensor (if a BD3C-5, there is only one serial number)
	103	* 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	104
64.1	105	[[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!
	106
60.3	107	== 2. Node Placement ==
17.1	108	)))
	109
18.2	110	Site Analysis:
	111
112.1	112	* Take compass measurements away from the sensor as it will affect your measurement. Use a stick or shovel to help align.
	113	* Take photographs from various angles to document the site setup thoroughly. Have a colleague stand next to it pointing at it.
	114	* Include a detailed site description in your notes.
18.2	115
60.3	116	== 3. GPS Considerations ==
18.2	117
20.1	118	(% class="wikigeneratedid" %)
112.1	119	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 (2 cm?) 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	120
60.3	121	== 4. Visibility and Location Marking ==
20.1	122
18.2	123	Flag Placement: Position a flag, preferably in a bright color (avoid green or yellow), near the instrument to aid in its future location.
	124
	125	GPS Marking:
	126
112.1	127	* Use a GPS device to mark the instrument's exact location. Most modern cell phones can get to about a 3m error with their internal GPS also; you can probably also get away with investing a few dollars in a good app that shows error and lets you log markers.
	128	* Also write the GPS down on paper (ie your [[LOG SHEET>>http://auspass.edu.au/field/NODES_blank_fieldlog.pdf]]).
18.2	129
60.3	130	== (% 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	131
20.1	132	* Charging Duration: Both types of nodes take approximately 6-8 hours to fully charge from a flat state.
	133	* Pre-Deployment Charging:
42.2	134	** Although the nodes hold their charge well, it's beneficial to give them a "top up" charge before deployment.
20.1	135
	136	* Operational Duration:
42.2	137	** 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	138
	139	* Post-Retrieval Charging:
94.4	140	** After retrieval, charge the instruments to about 50-60% (indicated by ORANGE LED) unless they are to be immediately re-deployed or transported.
	141	* State of Charge (SoC) for Storage:
	142	** Maintain a battery charge level of around 50-60% (i.e., ORANGE) for storage.
	143	** This charge level is recommended to prevent battery damage, and should be checked every six months.
94.5	144	** Nodes should //__not be stored at full-charge (GREEN), or 0-charge (RED).__//
94.4	145	Storage at 0-charge damages lithium batteries.**
	146	* SoC for Transport:
94.5	147	** 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	148
42.2	149	(((
60.3	150	== 6. Data Sharing and Metadata Creation ==
28.1	151	)))
20.1	152
18.3	153	GPS Data:
	154
94.4	155	* Ensure you have __carefully documented__ precise lat/lon locations for each station.
18.3	156
	157	Photo Sharing:
	158
43.2	159	* It is strongly encouraged to take pictures of each site and upload these to a shared platform (OneDrive, Dropbox, etc.).
18.3	160
	161	Metadata File:
	162
60.3	163	* 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	164
60.3	165	== 7. Additional Best Practices ==
18.3	166
43.2	167	* 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	168
24.2	169	----
18.3	170
43.2	171	= Seismic Station Demobilization and Documentation =
24.1	172
	173	1. (((
	174	Preparation for Demobilization:
	175
43.2	176	* 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	177	)))
	178	1. (((
	179	Locating the instrument:
	180
	181	* Use the downloaded GPS file to accurately locate the node for demobilization.
	182	* Import this KMZ file onto your phone for easy reference and location tracking.
	183	* Utilize Google Maps or Google Earth to create a KMZ file of the station’s location.
	184	)))
	185	1. (((
	186	Labeling Instruments for Demobilization:
	187
43.2	188	* 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	189	* Add markers 'D' (for download), 'C' (for charge), and ‘R’ (for removal) next to checkboxes on the label.
	190	* Affix this label to the top of the instrument to avoid confusion during the charging and downloading data.
	191	)))
	192	1. (((
	193	Photographing the Setup Node:
	194
	195	* Take a photo of the entire setup node with the __//label//__ and __//compass visible//__.
	196	* This photo serves as a final record of the instrument’s condition and orientation at the time of removal.
	197	)))
	198	1. (((
	199	Logging Demobilization Details:
	200
	201	* Use the field logbook to note the time of demobilization, serial numbers, and station name.
	202	* Record any observations or issues related to the instrument’s orientation, level, or any other relevant factors.
	203	)))
	204	1. (((
	205	Final Checks and Equipment Removal:
	206
	207	* Before physically removing the instrument, double-check that all necessary data has been downloaded and all photos and notes have been taken.
	208	* Carefully dismantle and pack the equipment, ensuring that all components are accounted for and securely stored for transport.
39.1	209
	210
24.1	211	)))
	212
40.1	213	[[image:1706153556166-231.jpeg\|\|data-xwiki-image-style-alignment="center" height="345" width="460"]]
37.2	214
24.2	215	----
24.1	216
43.2	217	= Charging Procedure for Seismic Nodes =
24.1	218
45.1	219	(((
60.3	220	== 1. Preparation for Charging: ==
24.1	221
24.2	222	* 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.
	223	)))
24.1	224
45.1	225	(((
60.3	226	== 2. Disassembling the Node: ==
45.1	227
94.4	228	* For the IGU-16HR, remove the battery section (bottom half) from the sensor by unscrewing the spike section counter-clockwise.
24.2	229	)))
24.1	230
45.1	231	(((
60.3	232	== 3. Setting Nodes in the Charging Box: ==
45.1	233
94.4	234	* Connect to a safe indoor power supply, and turn on (red rocker switch).
	235	* Charging will begin automatically when nodes are inserted in the charging rack.
	236	* Place IGU-16HR battery sections upside-down in the rack, oriented with the terminal connectors.
24.2	237	)))
24.1	238
45.1	239	(((
60.3	240	== 4. Monitoring the Charging Process: ==
45.1	241
94.4	242	* Lights adjacent to the batteries will illuminate, indicating that charging is underway.
	243	* 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	244	)))
24.1	245
45.1	246	(((
60.3	247	== 5. Updating Charge Status: ==
45.1	248
34.2	249	* 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	250	* This step is crucial for tracking the charging status of multiple units, especially when handling a large number of nodes.
	251	)))
24.1	252
39.1	253	[[IGU 16-HRcharger (left) and harvester (right)>>image:1705195933422-337.png\|\|data-xwiki-image-style-alignment="center" height="299" width="530"]]
36.2	254
	255
37.2	256
	257
88.1	258	{{{
89.1	259	}}}
37.2	260
24.2	261	----
24.1	262
45.2	263	= Downloading and Converting Seismic Data to MiniSeed Format =
24.1	264
86.1	265	(% class="wikigeneratedid" %)
	266	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]]
	267
86.2	268	== Connection tips: ==
86.1	269
	270	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:
	271
86.2	272	* Place the node on the harvester gently, then firmly press it down onto the pins.
	273	* 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.
	274	* 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.
	275	* 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	276
	277
	278
60.3	279	== Node Registration and Software Setup ==
24.1	280
24.2	281	1. (((
	282	Registering Nodes in the System:
24.1	283
24.2	284	* To begin, register the nodes in the system so the software can recognize them.
	285	* Navigate to the installation folder of “SmartSoloApps SoloLite”.
	286	* Right-click on deviceconfig.exe and choose “run as an administrator”. Save the file to the “deviceconfig” directory (refer to the snapshot below).
	287	* To avoid double registration, replace the file each time you register a new node.
	288	)))
	289	1. (((
	290	Creating a New Project in SoloLite:
24.1	291
24.2	292	* Open the “SoloLite” software.
	293	* Go to “File” and create a new project. Don't worry about finding the exact 16 nodes used in script writing.
	294	* Ignore the settings for seismic recordings in the subsequent window. Resetting instruments (e.g., sampling rate, gain) requires reprogramming via script.
	295	)))
	296
88.1	297	== File structure ==
	298
	299	There are essentially three main folders where relevant PROSPECT and PROJECT DATA is stored. Individual projects will be found as subfolders in these.
	300
	301	=== SOLOLITE ===
	302
	303	This folder stores SoloLite config files and parameters. Nothing too important stored here, you can always start over and re-create this.
	304
	305	=== DCCDATA ===
	306
	307	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.
	308
	309	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)//
	310
	311	Then in the SoloLite software, go to tools > Reanalyze Seismic Data
	312
	313	=== SOLODATA ===
	314
	315	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.
	316
	317
60.3	318	== Data Downloading Process ==
24.2	319
	320	1. (((
	321	Initiating Data Download:
	322
	323	* Once a new project is created, the Data Transfer View panel will display connected nodes with details like series number and data size.
	324	* If “Prospect not matched” appears, it simply means the new project doesn’t match the original programming project. This is not a concern.
110.1	325	* Select all nodes and right-click to “force download”. This starts the download process.[[image:Smartsolo harvesting #4 copy.png]]
24.2	326	* Completed downloads will appear as new folders in the Downloaded Data panel.
	327	)))
	328	1. (((
	329	Exporting Data in Readable Format:
	330
	331	* Go to the “Tool” menu and select “export seismic data”.
110.14	332	* Tailor other parameters to project preference and ensure "Sample Interval" matches the setting used during node reset (note: the standard used by ANU is 4ms, or 250hz)
29.1	333	* (% class="box warningmessage" %)
	334	(((
110.3	335	Ensure export data is set to "COUNTS" (int32), not "mV" (float). This is critical!
27.1	336	)))
110.3	337	* 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.
110.14	338	* Set "Remove DC" to "Yes" to centre the data around the zero value
110.3	339	* Set the correct Start Time (UTC) and End Time (UTC) of the project to prevent the unnecessary export of older data
	340	* [[image:Smartsolo harvesting #9 copy.png]]
	341	* Click “prepare” followed by “run” to start reformatting. Monitor this process in the small panel at the bottom left.
110.14	342	* The data will be exported to the SOLODATA folder. For a windows system, the following file explorer page is where you must navigate to to locate your project folder[[image:Smartsolo harvesting #8 copy.png]]
110.3	343	)))
24.4	344
91.2	345	== Smart Solo IGU-16HR Polarity Notice ==
82.1	346
99.1	347	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	348
98.1	349	The BD3C-5 data does not require any sort of polarity inversion.
91.2	350
89.1	351	== 18 Leap Second bug ==
	352
91.2	353	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	354
	355	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.
	356
	357	{{code language="none"}}
	358	<?xml version="1.0" encoding="UTF-8"?>
	359	<config>
	360	<leapsecond>
	361	<interval>
	362	<start_time>2017-01-01#00:00:00</start_time>
	363	<end_time>2999-12-31#23:59:59</end_time>
	364	<second>18</second>
	365	</interval>
	366	<interval>
	367	<start_time>1970-01-01#00:00:00</start_time>
	368	<end_time>2017-01-01#00:00:00</end_time>
	369	<second>17</second>
	370	</interval>
	371	</leapsecond>
	372	<GPS_distance_threshold_degree>
	373	4e-5
	374	</GPS_distance_threshold_degree>
	375	</config>
	376	{{/code}}
	377
	378
60.3	379	== Handling Nodes During Download ==
24.2	380
	381	1. (((
	382	Monitoring Download Indicators:
	383
	384	* During download, green lights on nodes will blink, and associated red lights on the rack will flash.
	385	* Disconnect nodes properly before unplugging anything.
	386	* Be cautious: if the laptop enters sleep mode, the download will pause.
	387	)))
	388	1. (((
35.1	389	//Investment in Storage Hardware~://
24.2	390
28.1	391	* (% class="box warningmessage" %)
	392	(((
31.2	393	* Use fast external hard drives to avoid limitations in data harvesting.
	394
	395	* Recommended specifications: USB-C, USB 3.0, and 4+ Tb of space.
61.1	396	* The USB type for the harvester is TYPE-A, the typical normal rectangular shape.
24.2	397	)))
28.1	398	)))
24.2	399	1. (((
	400	Metadata and Time Settings:
	401
	402	* Ensure all metadata is saved with the file.
	403	* 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.
	404	)))
	405	1. (((
	406	Finalizing the Download:
	407
34.1	408	* After downloading, mark the //"D"// box on your temporary labels to indicate completion.
24.2	409	)))
	410
36.2	411
	412
	413
39.1	414	[[Caption>>image:1705195543887-977.png\|\|data-xwiki-image-style-alignment="center" height="534" width="632"]]
36.2	415
	416
	417
	418
39.1	419	[[Caption>>image:1705195543890-537.png\|\|data-xwiki-image-style-alignment="center" height="397" width="665"]]
36.2	420
37.1	421
36.2	422
39.1	423	[[Caption>>image:1705195543891-334.png\|\|data-xwiki-image-style-alignment="center" height="379" width="650"]]
	424
	425
	426
	427	[[image:1705195543898-365.png\|\|data-xwiki-image-style-alignment="center" height="467" width="674"]]
	428
36.1	429	----
	430
102.1	431	= Instrument Response =
	432
103.1	433	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	434
103.1	435	== IGU 16HR-3C ==
102.1	436
	437	'16HR3C': {'poles':[(-22.211059+22.217768j), (-22.211059-22.217768j)],
	438	'zeros':[0j, 0j],
	439	'gain':1,
	440	'sensitivity': 257019225.55108312}
	441
104.2	442	[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:IGU16_Z_huddle.png]]
102.1	443
107.2	444	[[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	445
103.1	446	== IGU 16-1C ==
102.1	447
107.1	448	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	449
107.2	450	[[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	451
102.1	452	== BD3C-5 ==
	453
	454	'BD3C': {'poles':[(-1720.4+0j), (-1.2+0.9j), (-1.2-0.9j)],
	455	'zeros':[(14164+0j), (-7162+0j), 0j, 0j],
	456	'gain':1.69726e-05,
	457	'sensitivity': 702651512.6046528}
	458
108.1	459	Above 0.5 Hz, the BD3C-5 response fits well:
104.1	460
108.1	461	[[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	462
108.1	463	[[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]]
	464
105.5	465	(% class="wikigeneratedid" %)
109.1	466	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	467
	468
107.2	469	[[BD3C 0.1 to 5 Hz bandpass filter>>image:BD3C_Z_huddle.0.1.png]]
105.5	470
107.2	471	[[BD3C 0.1 to 5 Hz bandpass filter>>image:BD3C_N_huddle.0.1.png]]
105.5	472
105.4	473	== IGU-16 Horizontal noise & how to avoid ==
102.1	474
107.1	475	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	476
105.3	477	[[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	478
105.3	479	(% class="wikigeneratedid" %)
	480	The BD3C-5 nodes do not have this issue:
	481
	482	[[BD3C-5 test, as above. There is no additional noise on the horizontal channels.>>image:BD3C_psd.png]]
	483
45.5	484	= Cleaning =
36.1	485
105.1	486	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	487
48.1	488	= Weights (for shipping) =
	489
	490	The weights of bags of nodes, as well as data harvesters and node chargers, are listed below:
	491
95.1	492	1 bag + 6*IGU-16HR nodes: 18 kg
48.1	493
95.1	494	1*IGU-16HR data harvester: 21.5 kg
48.1	495
95.1	496	1*IGU-16HR charger: 26.3 kg
48.1	497
95.1	498	1*BD3C-5 charger (with and without 16 cables): 21 kg / 14.5 kg
48.1	499
95.1	500	1 case + 5*BD3C-5 nodes: 22 kg (aggregate battery weight <5kg, 168Wh)
	501
	502	1 case + 6*BD3C-5 nodes: 25 kg (aggregate battery weight >5kg, 168Wh)
8.3	503	)))
	504
1.1	505	(% class="col-xs-12 col-sm-4" %)
	506	(((
10.1	507	(% class="box" %)
	508	(((
	509	Contents
1.1	510
44.1	511	{{toc/}}
	512
43.2	513
10.1	514	)))
1.1	515
11.1	516	(% class="box" %)
10.1	517	(((
11.1	518	= SmartSolo [[BD3C-5>>url:https://smartsolo.com/cp-4.html]] =
12.1	519
15.1	520	[[image:Smartsolo IGU BD3C 5 (2).jpg]]
	521
16.1	522	[[image:smartsolo.jpg]]
	523
13.2	524	\|(% style="width:189px" %)Frequency Band\|(% style="width:221px" %)5 Seconds to 150Hz
	525	\|(% style="width:189px" %)Sensitivity\|(% style="width:221px" %)200 V/m/s
81.1	526	\|(% style="width:189px" %)Size (without spike)\|(% style="width:221px" %)Φ158 x160mm(H)
13.2	527	\|(% style="width:189px" %)Weight\|(% style="width:221px" %)2.8 kg
	528	\|(% style="width:189px" %)Data Storage\|(% style="width:221px" %)64 Gb
49.3	529	\|(% style="width:189px" %)Battery\|(% style="width:221px" %)(((
	530	Lithium-ion battery contained in equipment (168.84 Wh)
	531
	532	UN3481 PI967 S1
12.1	533	)))
49.3	534	)))
11.1	535
12.1	536	(% class="box" %)
	537	(((
69.1	538	= SmartSolo [[IGU-16HR>>url:https://smartsolo.com/cp-3.html]]3C =
11.1	539
16.1	540	[[image:smartsolo node.jpg]]
	541
	542	[[image:smartsolo node 2.jpg]]
	543
13.2	544	\|(% style="width:187px" %)Frequency Band\|(% style="width:224px" %)5 Hz to 1652Hz
79.1	545	\|(% style="width:187px" %)Sensitivity\|(% style="width:224px" %)76.7 V/m/s
81.1	546	\|(% style="width:187px" %)Size (with spike)\|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm(H)
42.2	547	\|(% style="width:187px" %)Weight\|(% style="width:224px" %)2.4 kg
13.2	548	\|(% style="width:187px" %)Data Storage\|(% style="width:224px" %)64 Gb
49.2	549	\|(% style="width:187px" %)Battery\|(% style="width:224px" %)(((
49.3	550	Lithium-ion battery contained in equipment (96.48 Wh)
49.2	551
	552	UN3481 PI967 S2
10.1	553	)))
49.2	554	)))
4.1	555
66.1	556	(% class="box" %)
	557	(((
79.1	558
	559
	560	= SmartSolo [[IGU-16>>url:https://smartsolo.com/cp-3.html]]1C =
	561
	562
	563	[[image:Screenshot 2025-08-01 161027.png]]
	564
	565	\|(% style="width:187px" %)Frequency Band\|(% style="width:224px" %)5 Hz to 413Hz
	566	\|(% style="width:187px" %)Sensitivity\|(% style="width:224px" %)80 V/m/s
81.1	567	\|(% style="width:187px" %)Size (without spike)\|(% style="width:224px" %)95mm(L) × 103mm(W) × 118mm(H)
79.1	568	\|(% style="width:187px" %)Weight\|(% style="width:224px" %)1.1 kg
80.1	569	\|(% style="width:187px" %)Data Storage\|(% style="width:224px" %)8 Gb
79.1	570	\|(% style="width:187px" %)Battery\|(% style="width:224px" %)(((
80.1	571	Lithium-ion battery contained in equipment (38.48 Wh)
79.1	572
	573	UN3481 PI967 S2
	574	)))
	575	)))
	576
	577	(% class="box" %)
	578	(((
65.1	579	= SmartSolo BD3C-16 Portable Battery Charger =
	580
68.1	581	[[image:20250729_125049.jpg]]
65.1	582
	583	\|Dimensions (LxHxW)\|558 x 357 x 300mm
	584	\|Input rating\|100-210V - 50/60Hz
	585	\|Power\|1000W
101.1	586	\|Weight\|14.5 kg
	587	\|Weight with cables\|21 kg
66.1	588	)))
65.1	589
66.1	590	(% class="box" id="HSmartSoloBD3C-16PortableBatteryCharger" %)
	591	(((
	592	= SmartSolo IGU-16 Portable Data Harvester =
65.1	593
68.1	594	[[image:20250729_124747.jpg]]
65.1	595
	596	\|Dimensions (LxHxW)\|625 x 500 x 366mm
	597	\|Input rating\|100-210V - 50/60Hz
	598	\|Power\|100W
101.1	599	\|Weight\|21.5 - 24 kg
	600	\|Capacity\|16 nodes
65.1	601	\|Download Speed\|20MB/sec/slot
66.1	602	)))
65.1	603
67.1	604	(% class="box" %)
	605	(((
	606	= SmartSolo IGU-16 Portable Battery Charger =
66.1	607
75.2	608	[[image:20250729_124644.jpg]]
66.1	609
101.1	610	\|Dimensions (LxHxW)\|625 x 500 x 366 mm
	611	\|Input rating\|100-210V - 50/60 Hz
	612	\|Power\|640 W
	613	\|Weight\|26.3 kg
	614	\|Capacity\|16 nodes
67.1	615	)))
65.1	616
72.1	617	(% class="box" %)
	618	(((
75.2	619	= SmartSolo BD3C-5 Carry Case =
65.1	620
72.1	621	[[image:20250729_124957.jpg]]
67.1	622
68.1	623
101.1	624	\|Dimensions (LxHxW)\|590 x 225 x 405 mm
	625	\|Weight\|8.2 kg
	626	\|Capacity\|6 nodes
72.1	627	)))
69.1	628
67.1	629	(% class="box" %)
	630	(((
70.1	631	= SmartSolo IGU-16 3C Carry Bag =
67.1	632
68.1	633	[[image:20250729_124502.jpg]]
	634
65.1	635	\|Dimensions (LxHxW)\|230 x 340 x 310mm
100.1	636	\|Weight\|(((
	637	3.6kg (empty)
	638
	639	18.0kg (full)
67.1	640	)))
101.1	641	\|Capacity\|6 nodes
100.1	642	)))
65.1	643
67.1	644	(% class="box" %)
	645	(((
70.1	646	= SmartSolo IGU-16 1C Carry Bag =
67.1	647
68.1	648	[[image:20250729_124558.jpg]]
	649
71.1	650	\|Dimensions (LxHxW)\|225 x 200 x 550mm
74.1	651	\|Weight\|
101.1	652	\|Capacity\|8 nodes
1.1	653	)))
	654	)))
67.1	655	)))

Wiki source code of SmartSolo Node Seismometers

Applications

Navigation