Wiki source code of SmartSolo Node Seismometers

Version 118.1 by robert on 2026/08/12 13:06

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

Wiki source code of SmartSolo Node Seismometers

Applications

Navigation