Skip to Content
Last modified by robert on 2026/02/27 19:58
From version 102.1
edited by robert
on 2026/02/16 17:44
Change comment: There is no comment for this version
To version 59.6
edited by robert
on 2025/07/16 15:58
Change comment: allow comment right for XWiki.XWikiGuest

Summary

Details

Page properties
Content
... ... @@ -4,62 +4,34 @@
4 4  (((
5 5  = **Node Types** =
6 6  
7 -ANSIR supply two types of three-channel nodes, and one type of one-channel node:
7 +ANSIR carry two types of three-channel nodes
8 8  
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)**
9 +* **SmartSolo IGU 16HR 3C (5 Hz Short Period)**
10 +* **SmartSolo BD3C-5 (5 Second Broad-Band)**
12 12  
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.
12 +Both have a battery capacity of around 30 days. The programming, operation, and downloading procedures for both types of SmartSolo nodes are also similar.
14 14  
15 -(% class="box infomessage" %)
16 -(((
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.
18 -)))
19 19  
20 20  ----
21 21  
22 22  = **Programming Defaults** =
23 23  
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.
19 +We recommend that the SP 16HR-3C be set to a gain of 24db and no higher than 250 Hz sampling rate unless there is an explicit reason to do so. The BD3C-5 should be set to a gain of 6db (which is the maximum allowed). These are what we use for our internal experiments.
25 25  
26 -[[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"]]
21 +**Note that this gain must be removed when exporting to miniseed, **otherwise amplitudes will be a factor of either 15.84893192 (24db) or 2 (6db) too high. We also recommend disabling bluetooth to increase battery life, and to enable "FIFO" mode just in case old data is still present on the units and you run out of space (although it is unlikely you will go over 64 Gb for one deploy). If using the "timed turn-on" option, please be aware that **the units will not begin recording until they have acquired a GPS lock**, which may nor occur if they are buried too deeply or have very poor sky view.
27 27  
28 -[[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!"]]
29 29  
30 -
31 -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.
32 -
33 -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.
34 -
35 -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.
36 -
37 -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!**
38 -
39 -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.
40 -
41 -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.
42 -
43 -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.
44 -
45 -Bluetooth (BD3C-5 only) should be turned OFF to conserve power.
46 -
47 -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).
48 -
49 -{{info}}
50 -**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!
51 -{{/info}}
52 -
53 53  = **Fieldwork Preparation** =
54 54  
26 +(% class="box infomessage" %)
27 +(((
55 55  (% class="box warningmessage" %)
56 56  (((
57 57  **INVEST IN FAST EXTERNAL HARD DRIVES – DO NOT LET THIS BE THE LIMITATION OF DATA HARVESTING**
58 58  
59 59  **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 -
61 -**We have had good experience with the 4Tb Samsung T7 Shield drives.**
62 62  )))
34 +)))
63 63  
64 64  == Magnets ==
65 65  
... ... @@ -67,46 +67,39 @@
67 67  
68 68  == Animal-Proofing ==
69 69  
70 -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.
42 +We have experienced times where foxes (or some other animal) will dig up nodes and potentially carry them off for tens or hundreds of meteres. Being sanitary with the rope handles (e.g. not getting food grease on them) seems to help, as well as spraying the nodes and handles with methylated spirits et al. when deploying. There are other specialized products available depending on your environment.
71 71  
72 -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.
73 -
74 74  = **Installation** =
75 75  
76 -(% class="box infomessage" %)
77 -(((
78 -**Field logs are a critical component of fieldwork and this is especially the case for large N nodal deploys. Take notes!**
79 -)))
46 +== **1. Logbook documentation** ==
80 80  
81 -== 1. Logbook documentation ==
82 -
83 83  (((
84 -**Essential Details** for field logs:
49 +**Essential Details**: Record the following in a logbook:
85 85  
86 86  * Station name
87 -* Latitude, longitude, elevation
52 +* Latitude and longitude
88 88  * Names of team members present
89 -* Date and both local & UTC time of installation/removal
90 -* Serial number (SN) of the TOP HALF of the sensor (if a BD3C-5, there is only one serial number)
91 -* 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)
54 +* Date and local time of installation
55 +* Serial number (SN) of the sensor
56 +* Detailed notes on the site conditions and setup
92 92  
93 -[[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!
94 -
95 -== 2. Node Placement ==
58 +== **2. Node Placement** ==
96 96  )))
97 97  
61 +**Protection**: Place nodes inside (landfill) biodegradable bags to minimize cleaning and cross-site soil contamination.
62 +
98 98  **Site Analysis**:
99 99  
100 100  * **Take compass measurements away from the sensor as it will affect your measurement.**
101 -* Take photographs from various angles to document the site setup thoroughly.
102 -* Include a detailed site description in your notes
66 +* Take multiple photographs from various angles to document the site setup thoroughly.
67 +* Include a detailed site description in your notes, specifying distances and orientations from nearby landmarks (e.g. Richards garden, Te Mini steam field eastern side)
103 103  
104 -== 3. GPS Considerations ==
69 +== **3. GPS Considerations** ==
105 105  
106 106  (% class="wikigeneratedid" %)
107 107  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.
108 108  
109 -== 4. Visibility and Location Marking ==
74 +== **4. Visibility and Location Marking** ==
110 110  
111 111  **Flag Placement**: Position a flag, preferably in a bright color (avoid green or yellow), near the instrument to aid in its future location.
112 112  
... ... @@ -115,7 +115,7 @@
115 115  * Use a GPS device to mark the instrument's exact location.
116 116  * Record this location in both your paper notes and the GPS device.
117 117  
118 -== (% style="color:inherit; font-family:inherit; font-size:max(18px, min(20px, 14.4444px + 0.462963vw))" %)5. Charge Time, Pre-Deployment & Post-Deployment(%%) ==
83 +== (% style="color:inherit; font-family:inherit; font-size:max(18px, min(20px, 14.4444px + 0.462963vw))" %)**5. Charge Time, Pre-Deployment & Post-Deployment**(%%) ==
119 119  
120 120  * **Charging Duration**: Both types of nodes take approximately 6-8 hours to fully charge from a flat state.
121 121  * **Pre-Deployment Charging**:
... ... @@ -125,22 +125,19 @@
125 125  ** 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.
126 126  
127 127  * **Post-Retrieval Charging**:
128 -** After retrieval, charge the instruments to about 50-60% (indicated by ORANGE LED) unless they are to be immediately re-deployed or transported.
129 -* **State of Charge (SoC) for Storage**:
130 -** Maintain a battery charge level of around 50-60% (i.e., ORANGE) for storage.
131 -** This charge level is recommended to prevent battery damage, and should be checked every six months.
132 -** Nodes should //__not be stored at full-charge (GREEN), or 0-charge (RED).__//
133 -** Storage at 0-charge damages lithium batteries**.**
134 -* **SoC for Transport:**
135 -** Charge levels for transport will be advised by the freighter. The required SoC will depend on volume and transport method (air, land, sea).
93 +** After retrieval, charge the instruments to about 50-60% (indicated as "orange" level) unless they are to be immediately re-deployed.
94 +* **Storage and Shipping Charge Level**:
95 +** Maintain a battery charge level of around 50-60% (e.g. "orange") for both storage and shipping purposes.
96 +** This charge level is recommended to prevent battery damage and is safe for transportation.
97 +** Nodes should not be stored fully charged, and it **they should especially not be stored with 0 charge.**
136 136  
137 137  (((
138 -== 6. Data Sharing and Metadata Creation ==
100 +== **6. Data Sharing and Metadata Creation** ==
139 139  )))
140 140  
141 141  **GPS Data**:
142 142  
143 -* Ensure you have __carefully documented__ precise lat/lon locations for each station.
105 +* Ensure you have documented precise lat/lon locations for each station and **DOCUMENTED THIS CAREFULLY**
144 144  
145 145  **Photo Sharing**:
146 146  
... ... @@ -148,9 +148,9 @@
148 148  
149 149  **Metadata File**:
150 150  
151 -* 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.
113 +* Create and organize metadata according to the [[ANU metadata standard txt file>>attach:example_metadata.txt]].
152 152  
153 -== 7. Additional Best Practices ==
115 +== **7. Additional Best Practices** ==
154 154  
155 155  * **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.
156 156  
... ... @@ -205,34 +205,32 @@
205 205  = **Charging Procedure for Seismic Nodes** =
206 206  
207 207  (((
208 -== 1. Preparation for Charging: ==
170 +== **1. Preparation for Charging**: ==
209 209  
210 210  * 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.
211 211  )))
212 212  
213 213  (((
214 -== 2. Disassembling the Node: ==
176 +== **2. Disassembling the Node**: ==
215 215  
216 -* For the IGU-16HR, remove the battery section (bottom half) from the sensor by unscrewing the spike section counter-clockwise.
178 +* For the IGU-16HR, remove the battery (bottom half) from the sensor. This is done by unscrewing the spikes counter-clockwise.
217 217  )))
218 218  
219 219  (((
220 -== 3. Setting Nodes in the Charging Box: ==
182 +== **3. Setting Nodes in the Charging Box**: ==
221 221  
222 -* Connect to a safe indoor power supply, and turn on (red rocker switch).
223 -* Charging will begin automatically when nodes are inserted in the charging rack.
224 -* Place IGU-16HR battery sections upside-down in the rack, oriented with the terminal connectors.
184 +* Place 1-16 IGU-16HR battery components upside-down into the charger, assuring they are oriented properly.
225 225  )))
226 226  
227 227  (((
228 -== 4. Monitoring the Charging Process: ==
188 +== **4. Monitoring the Charging Process**: ==
229 229  
230 -* Lights adjacent to the batteries will illuminate, indicating that charging is underway.
231 -* 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.
190 +* Once the nodes are set in the charging box and the charging process begins, lights adjacent to the batteries will illuminate. These lights indicate that charging is underway.
191 +* Observe the transition of the lights from steady red to orange, then to green, and finally to flashing green. A flashing green light signifies that the batteries are fully charged. For storage, the goal is to charge them to ORANGE.
232 232  )))
233 233  
234 234  (((
235 -== 5. Updating Charge Status: ==
195 +== **5. Updating Charge Status**: ==
236 236  
237 237  * 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.
238 238  * This step is crucial for tracking the charging status of multiple units, especially when handling a large number of nodes.
... ... @@ -243,29 +243,14 @@
243 243  
244 244  
245 245  
246 -{{{
247 - }}}
206 +[[image:1706153354750-415.png||data-xwiki-image-style-alignment="center" height="317" width="562"]]
248 248  
249 249  ----
250 250  
251 251  = **Downloading and Converting Seismic Data to MiniSeed Format** =
252 252  
253 -(% class="wikigeneratedid" %)
254 -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]]
212 +== **Node Registration and Software Setup** ==
255 255  
256 -== Connection tips: ==
257 -
258 -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:
259 -
260 -* Place the node on the harvester gently, then firmly press it down onto the pins.
261 -* 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.
262 -* 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.
263 -* 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!
264 -
265 -
266 -
267 -== Node Registration and Software Setup ==
268 -
269 269  1. (((
270 270  **Registering Nodes in the System**:
271 271  
... ... @@ -282,29 +282,8 @@
282 282  * Ignore the settings for seismic recordings in the subsequent window. Resetting instruments (e.g., sampling rate, gain) requires reprogramming via script.
283 283  )))
284 284  
285 -== File structure ==
230 +== **Data Downloading Process** ==
286 286  
287 -There are essentially three main folders where relevant PROSPECT and PROJECT DATA is stored. Individual projects will be found as subfolders in these.
288 -
289 -=== SOLOLITE ===
290 -
291 -This folder stores SoloLite config files and parameters. Nothing too important stored here, you can always start over and re-create this.
292 -
293 -=== DCCDATA ===
294 -
295 -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.
296 -
297 -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)//
298 -
299 -Then in the SoloLite software, go to tools > Reanalyze Seismic Data
300 -
301 -=== SOLODATA ===
302 -
303 -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.
304 -
305 -
306 -== Data Downloading Process ==
307 -
308 308  1. (((
309 309  **Initiating Data Download**:
310 310  
... ... @@ -321,48 +321,14 @@
321 321  * Click “prepare” followed by “run” to start reformatting. Monitor this process in the small panel at the bottom left.
322 322  * (% class="box warningmessage" %)
323 323  (((
324 -* **Ensure to export data as "COUNTS" (int32), not "mV" (float). This is critical!**
248 +* **Ensure to export data as "COUNTS", not "mV".**
325 325  
326 -* **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.**
250 +* **Set "Remove Gain" to the same decibel gain as during programming** **(by default ANU sets this to 24db for short period nodes (a factor of 15.848932), and 6db for broadband nodes).**
327 327  )))
328 328  )))
329 329  
330 -== Smart Solo IGU-16HR Polarity Notice ==
254 +== **Handling Nodes During Download** ==
331 331  
332 -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.
333 -
334 -**The BD3C-5 data does not require any sort of polarity inversion.**
335 -
336 -== 18 Leap Second bug ==
337 -
338 -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.
339 -
340 -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.
341 -
342 -{{code language="none"}}
343 -<?xml version="1.0" encoding="UTF-8"?>
344 -<config>
345 - <leapsecond>
346 - <interval>
347 - <start_time>2017-01-01#00:00:00</start_time>
348 - <end_time>2999-12-31#23:59:59</end_time>
349 - <second>18</second>
350 - </interval>
351 - <interval>
352 - <start_time>1970-01-01#00:00:00</start_time>
353 - <end_time>2017-01-01#00:00:00</end_time>
354 - <second>17</second>
355 - </interval>
356 - </leapsecond>
357 - <GPS_distance_threshold_degree>
358 - 4e-5
359 - </GPS_distance_threshold_degree>
360 -</config>
361 -{{/code}}
362 -
363 -
364 -== Handling Nodes During Download ==
365 -
366 366  1. (((
367 367  **Monitoring Download Indicators**:
368 368  
... ... @@ -378,7 +378,6 @@
378 378  * **Use fast external hard drives to avoid limitations in data harvesting.**
379 379  
380 380  * **Recommended specifications: USB-C, USB 3.0, and 4+ Tb of space.**
381 -* **The USB type for the harvester is TYPE-A, the typical normal rectangular shape.**
382 382  )))
383 383  )))
384 384  1. (((
... ... @@ -416,55 +416,23 @@
416 416  
417 417  ----
418 418  
419 -= Instrument Response =
420 -
421 -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, as well as if one is working in integer counts (the ANSIR default) or mV (why anyone uses this is beyond our comprehension). The response information published below is in counts and seems to fit well in huddle tests. Note that these 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]]
422 -
423 -== IGU16-3C ==
424 -
425 - '16HR3C': {'poles':[(-22.211059+22.217768j), (-22.211059-22.217768j)],
426 - 'zeros':[0j, 0j],
427 - 'gain':1,
428 - 'sensitivity': 257019225.55108312}
429 -
430 -[[Caption>>image:IGU16_Z_huddle.png]]
431 -
432 -[[Caption>>image:IGU16_N_huddle.png]]
433 -
434 -== IGU16-1C ==
435 -
436 -== BD3C-5 ==
437 -
438 - 'BD3C': {'poles':[(-1720.4+0j), (-1.2+0.9j), (-1.2-0.9j)],
439 - 'zeros':[(14164+0j), (-7162+0j), 0j, 0j],
440 - 'gain':1.69726e-05,
441 - 'sensitivity': 702651512.6046528}
442 -
443 -== Horizontal noise & how to avoid ==
444 -
445 -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.
446 -
447 -[[Power spectrum huddle test vs a CMG-6TD (S1) and TC120/Centaur combo, all filtered 0.5-5 Hz. The N and E channels have excess noise above 10Hz due to "sticking up" out of the ground.>>image:IGU16_spectrum.png]]
448 -
449 449  = **Cleaning** =
450 450  
451 -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.
310 +When still connected, the nodes are water resistant (don't submerge them!) and can handle a good spray / wipedown. A strong, non-wire brush is helpful to reach areas between the metal spikes on the bottom.
452 452  
453 453  = **Weights (for shipping)** =
454 454  
455 455  The weights of bags of nodes, as well as data harvesters and node chargers, are listed below:
456 456  
457 -1 bag + 6*IGU-16HR nodes: 18 kg
316 +1 bag + 6 SP (IGU-16HR) nodes: 18 kg
458 458  
459 -1*IGU-16HR data harvester: 21.5 kg
318 +1 SP (IGU-16HR) data harvester: 21.5 kg
460 460  
461 -1*IGU-16HR charger: 26.3 kg
320 +1 SP (IGU-16HR) charger: 26.3 kg
462 462  
463 -1*BD3C-5 charger (with and without 16 cables): 21 kg / 14.5 kg
322 +1 BB (BD3C-5) charger/data harvester (with and without 16 cables): 21 kg / 14.5 kg
464 464  
465 -1 case + 5*BD3C-5 nodes: 22 kg (aggregate battery weight <5kg, 168Wh)
466 -
467 -1 case + 6*BD3C-5 nodes: 25 kg (aggregate battery weight >5kg, 168Wh)
324 +1 case + 5 BB (BD3C-5) nodes and 6 BB nodes: 22 kg / 25 kg
468 468  )))
469 469  
470 470  (% class="col-xs-12 col-sm-4" %)
... ... @@ -488,7 +488,7 @@
488 488  
489 489  |(% style="width:189px" %)**Frequency Band**|(% style="width:221px" %)5 Seconds to 150Hz
490 490  |(% style="width:189px" %)**Sensitivity**|(% style="width:221px" %)200 V/m/s
491 -|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)Φ158 x160mm(H)
348 +|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)158 x160mm
492 492  |(% style="width:189px" %)**Weight**|(% style="width:221px" %)2.8 kg
493 493  |(% style="width:189px" %)**Data Storage**|(% style="width:221px" %)64 Gb
494 494  |(% style="width:189px" %)**Battery**|(% style="width:221px" %)(((
... ... @@ -500,7 +500,7 @@
500 500  
501 501  (% class="box" %)
502 502  (((
503 -= SmartSolo [[IGU-16HR>>url:https://smartsolo.com/cp-3.html]]3C =
360 += SmartSolo [[IGU-16HR>>url:https://smartsolo.com/cp-3.html]] =
504 504  
505 505  [[image:smartsolo node.jpg]]
506 506  
... ... @@ -507,8 +507,8 @@
507 507  [[image:smartsolo node 2.jpg]]
508 508  
509 509  |(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 1652Hz
510 -|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)76.7 V/m/s
511 -|(% style="width:187px" %)**Size (with spike)**|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm(H)
367 +|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)67.7 V/m/s
368 +|(% style="width:187px" %)**Size (with spike)**|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm
512 512  |(% style="width:187px" %)**Weight**|(% style="width:224px" %)2.4 kg
513 513  |(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)64 Gb
514 514  |(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((
... ... @@ -518,103 +518,6 @@
518 518  )))
519 519  )))
520 520  
521 -(% class="box" %)
522 -(((
523 523  
524 -
525 -= SmartSolo [[IGU-16>>url:https://smartsolo.com/cp-3.html]]1C =
526 -
527 -
528 -[[image:Screenshot 2025-08-01 161027.png]]
529 -
530 -|(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 413Hz
531 -|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)80 V/m/s
532 -|(% style="width:187px" %)**Size (without spike)**|(% style="width:224px" %)95mm(L) × 103mm(W) × 118mm(H)
533 -|(% style="width:187px" %)**Weight**|(% style="width:224px" %)1.1 kg
534 -|(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)8 Gb
535 -|(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((
536 -Lithium-ion battery contained in equipment (38.48 Wh)
537 -
538 -UN3481 PI967 S2
539 539  )))
540 540  )))
541 -
542 -(% class="box" %)
543 -(((
544 -= SmartSolo BD3C-16 Portable Battery Charger =
545 -
546 -[[image:20250729_125049.jpg]]
547 -
548 -|**Dimensions (LxHxW)**|558 x 357 x 300mm
549 -|**Input rating**|100-210V - 50/60Hz
550 -|**Power**|1000W
551 -|**Weight**|14.5 kg
552 -|**Weight with cables**|21 kg
553 -)))
554 -
555 -(% class="box" id="HSmartSoloBD3C-16PortableBatteryCharger" %)
556 -(((
557 -= SmartSolo IGU-16 Portable Data Harvester =
558 -
559 -[[image:20250729_124747.jpg]]
560 -
561 -|**Dimensions (LxHxW)**|625 x 500 x 366mm
562 -|**Input rating**|100-210V - 50/60Hz
563 -|**Power**|100W
564 -|**Weight**|21.5 - 24 kg
565 -|**Capacity**|16 nodes
566 -|**Download Speed**|20MB/sec/slot
567 -)))
568 -
569 -(% class="box" %)
570 -(((
571 -= SmartSolo IGU-16 Portable Battery Charger =
572 -
573 -[[image:20250729_124644.jpg]]
574 -
575 -|**Dimensions (LxHxW)**|625 x 500 x 366 mm
576 -|**Input rating**|100-210V - 50/60 Hz
577 -|**Power**|640 W
578 -|**Weight**|26.3 kg
579 -|**Capacity**|16 nodes
580 -)))
581 -
582 -(% class="box" %)
583 -(((
584 -= SmartSolo BD3C-5 Carry Case =
585 -
586 -[[image:20250729_124957.jpg]]
587 -
588 -
589 -|**Dimensions (LxHxW)**|590 x 225 x 405 mm
590 -|**Weight**|8.2 kg
591 -|**Capacity**|6 nodes
592 -)))
593 -
594 -(% class="box" %)
595 -(((
596 -= SmartSolo IGU-16 3C Carry Bag =
597 -
598 -[[image:20250729_124502.jpg]]
599 -
600 -|**Dimensions (LxHxW)**|230 x 340 x 310mm
601 -|**Weight**|(((
602 -3.6kg (empty)
603 -
604 -18.0kg (full)
605 -)))
606 -|**Capacity**|6 nodes
607 -)))
608 -
609 -(% class="box" %)
610 -(((
611 -= SmartSolo IGU-16 1C Carry Bag =
612 -
613 -[[image:20250729_124558.jpg]]
614 -
615 -|**Dimensions (LxHxW)**|225 x 200 x 550mm
616 -|**Weight**|
617 -|**Capacity**|8 nodes
618 -)))
619 -)))
620 -)))
20250729_124502.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -318.3 KB
Content
20250729_124558.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -376.8 KB
Content
20250729_124644.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -528.0 KB
Content
20250729_124747.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -488.5 KB
Content
20250729_124957.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -532.5 KB
Content
20250729_125049.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -457.6 KB
Content
5Hz_node_programming.labels.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.KB
Size
... ... @@ -1,1 +1,0 @@
1 -109.8 KB
Content
5S_node_programming.labels.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.KB
Size
... ... @@ -1,1 +1,0 @@
1 -114.2 KB
Content
BB_programming.labels.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -111.5 KB
Content
IGU16_N_huddle.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -65.7 KB
Content
IGU16_Z_huddle.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -67.4 KB
Content
IGU16_spectrum.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -65.0 KB
Content
SP_programming.labels.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -106.7 KB
Content
Screenshot 2025-08-01 161027.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -82.8 KB
Content