Wiki source code of SmartSolo Node Seismometers

Version 95.2 by KB on 2026/01/19 13:42

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

Wiki source code of SmartSolo Node Seismometers

Applications

Navigation