Skip to Content
Last modified by robert on 2026/02/27 19:58
From version 74.2
edited by robert
on 2025/07/31 19:59
Change comment: There is no comment for this version
To version 105.3
edited by robert
on 2026/02/17 15:40
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -4,37 +4,54 @@
4 4  (((
5 5  = **Node Types** =
6 6  
7 -ANSIR carry two types of three-channel nodes
7 +ANSIR supply two types of three-channel nodes, and one type of one-channel node:
8 8  
9 -* **SmartSolo IGU 16HR 3C (5 Hz Short Period)**
10 -* **SmartSolo BD3C-5 (5 Second Broadband)**
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. Not 'HR')**
11 11  
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.
13 +Visit the [[SmartSolo page>>https://smartsolo.com/igu.html]] for more detail.
13 13  
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.
16 +
17 +(% class="box infomessage" %)
18 +(((
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.
20 +)))
21 +
14 14  ----
15 15  
16 16  = **Programming Defaults** =
17 17  
18 -The nodes must be programmed in the SoloLite software prior to use. Screenshots for the short period 16HR-3C and broadband BDC3-5 are shown with our recommended parameters.
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.
19 19  
20 -[[IGU-16 3C (short period node) programming screen set at 250 Hz. Ensure that the highlighted areas are set!>>image:SP_programming.labels.png||alt="IGU-16 3C programming screen"]]
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"]]
21 21  
22 -[[BD3C-5 (broadband node) programming screen set at 250 hz. Ensure that the highlighted areas are set!>>image:BB_programming.labels.png||alt="BD3C-5 programming screen"]]
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!"]]
23 23  
32 +
24 24  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.
25 25  
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 +
26 26  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.
27 27  
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 +
28 28  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.
29 29  
30 -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 output to miniseed later.
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.
31 31  
32 -GPS mode is best in cycle mode (e.g. once per hour) instead of constant. The clock drift on these are almost nil even if there is no sync at all, so it's best to conserve power.
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.
33 33  
34 -We recommend that the SP 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).
47 +Bluetooth (BD3C-5 only) should be turned OFF to conserve power.
35 35  
36 -**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.
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).
37 37  
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}}
54 +
38 38  = **Fieldwork Preparation** =
39 39  
40 40  (% class="box warningmessage" %)
... ... @@ -52,8 +52,10 @@
52 52  
53 53  == Animal-Proofing ==
54 54  
55 -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.
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.
56 56  
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 +
57 57  = **Installation** =
58 58  
59 59  (% class="box infomessage" %)
... ... @@ -78,8 +78,6 @@
78 78  == 2. Node Placement ==
79 79  )))
80 80  
81 -**Protection**: Place nodes inside (landfill) biodegradable bags to minimize cleaning and cross-site soil contamination.
82 -
83 83  **Site Analysis**:
84 84  
85 85  * **Take compass measurements away from the sensor as it will affect your measurement.**
... ... @@ -110,11 +110,14 @@
110 110  ** 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.
111 111  
112 112  * **Post-Retrieval Charging**:
113 -** After retrieval, charge the instruments to about 50-60% (indicated as "orange" level) unless they are to be immediately re-deployed.
114 -* **Storage and Shipping Charge Level**:
115 -** Maintain a battery charge level of around 50-60% (e.g. "orange") for both storage and shipping purposes.
116 -** This charge level is recommended to prevent battery damage and is safe for transportation.
117 -** Nodes should not be stored fully charged, and **they should especially not be stored with 0 charge as this damages lithium batteries.**
130 +** After retrieval, charge the instruments to about 50-60% (indicated by ORANGE LED) unless they are to be immediately re-deployed or transported.
131 +* **State of Charge (SoC) for Storage**:
132 +** Maintain a battery charge level of around 50-60% (i.e., ORANGE) for storage.
133 +** This charge level is recommended to prevent battery damage, and should be checked every six months.
134 +** Nodes should //__not be stored at full-charge (GREEN), or 0-charge (RED).__//
135 +** Storage at 0-charge damages lithium batteries**.**
136 +* **SoC for Transport:**
137 +** Charge levels for transport will be advised by the freighter. The required SoC will depend on volume and transport method (air, land, sea).
118 118  
119 119  (((
120 120  == 6. Data Sharing and Metadata Creation ==
... ... @@ -122,7 +122,7 @@
122 122  
123 123  **GPS Data**:
124 124  
125 -* Ensure you have documented precise lat/lon locations for each station and **DOCUMENTED THIS CAREFULLY**
145 +* Ensure you have __carefully documented__ precise lat/lon locations for each station.
126 126  
127 127  **Photo Sharing**:
128 128  
... ... @@ -195,20 +195,22 @@
195 195  (((
196 196  == 2. Disassembling the Node: ==
197 197  
198 -* For the IGU-16HR, remove the battery (bottom half) from the sensor. This is done by unscrewing the spikes counter-clockwise.
218 +* For the IGU-16HR, remove the battery section (bottom half) from the sensor by unscrewing the spike section counter-clockwise.
199 199  )))
200 200  
201 201  (((
202 202  == 3. Setting Nodes in the Charging Box: ==
203 203  
204 -* Place 1-16 IGU-16HR battery components upside-down into the charger, assuring they are oriented properly.
224 +* Connect to a safe indoor power supply, and turn on (red rocker switch).
225 +* Charging will begin automatically when nodes are inserted in the charging rack.
226 +* Place IGU-16HR battery sections upside-down in the rack, oriented with the terminal connectors.
205 205  )))
206 206  
207 207  (((
208 208  == 4. Monitoring the Charging Process: ==
209 209  
210 -* 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.
211 -* 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 +* Lights adjacent to the batteries will illuminate, indicating that charging is underway.
233 +* Observe the transition of the lights from steady RED to ORANGE, then GREEN, and finally to FLASHING GREEN. A flashing green light indicates the batteries are fully charged.
212 212  )))
213 213  
214 214  (((
... ... @@ -223,12 +223,27 @@
223 223  
224 224  
225 225  
226 -[[image:1706153354750-415.png||data-xwiki-image-style-alignment="center" height="317" width="562"]]
248 +{{{
249 + }}}
227 227  
228 228  ----
229 229  
230 230  = **Downloading and Converting Seismic Data to MiniSeed Format** =
231 231  
255 +(% class="wikigeneratedid" %)
256 +SmartSolo provides the following powerpoint for SmartSolo node programming and operation. Note that ANSIR only uses a portion of their process for our own uses: [[https:~~/~~/nappe.wustl.edu/smartsolo/files/smartsolo_online_training.pdf>>url:https://nappe.wustl.edu/smartsolo/files/smartsolo_online_training.pdf]]
257 +
258 +== Connection tips: ==
259 +
260 +Connecting SmartSolo nodes to their harvesters and having SoloLite recognise them can be a bit tricky, here are some tricks to help register and program them easier:
261 +
262 +* Place the node on the harvester gently, then firmly press it down onto the pins.
263 +* Place all nodes onto the harvester before trying any troubleshooting, as they may not show up while the SoloLite software is running. Once all are connected, try restarting the software for them to be recognised.
264 +* If a node is refusing to connect, try it with another slot. It is easiest if you place all 16 nodes on the harvester, and swap any nodes that refuse to connect with each other.
265 +* Nodes will likely not show up in the order that they should, though this is not an issue. E.g, a node in slot 6 on the harvester may show up in port 13 in the SoloLite software. Annoying, but it doesn't matter so long as you keep track of what's been harvested!
266 +
267 +
268 +
232 232  == Node Registration and Software Setup ==
233 233  
234 234  1. (((
... ... @@ -247,6 +247,27 @@
247 247  * Ignore the settings for seismic recordings in the subsequent window. Resetting instruments (e.g., sampling rate, gain) requires reprogramming via script.
248 248  )))
249 249  
287 +== File structure ==
288 +
289 +There are essentially three main folders where relevant PROSPECT and PROJECT DATA is stored. Individual projects will be found as subfolders in these.
290 +
291 +=== SOLOLITE ===
292 +
293 +This folder stores SoloLite config files and parameters. Nothing too important stored here, you can always start over and re-create this.
294 +
295 +=== DCCDATA ===
296 +
297 +This folder stores the RAW data you have harvested from the nodes. The data will still be on the nodes (unless you erased it) in case of emergency, but regardless, this is the folder you want to back up and save somewhere.
298 +
299 +If you had a weird time harvesting a node, you can always manually copy it as if it were a USB stick and place it into this folder manually. The structure is: //C:/DCCDATA/prospect_name/project_name/SERIALNUMBER/label(usually a timestamp but can be anything)//
300 +
301 +Then in the SoloLite software, go to tools > Reanalyze Seismic Data
302 +
303 +=== SOLODATA ===
304 +
305 +This folder stores **exported** (e.g. miniseed) data. It is structured similarly. If your DCCDATA is intact, this can always be re-created if need be.
306 +
307 +
250 250  == Data Downloading Process ==
251 251  
252 252  1. (((
... ... @@ -271,6 +271,40 @@
271 271  )))
272 272  )))
273 273  
332 +== Smart Solo IGU-16HR Polarity Notice ==
333 +
334 +See [[5Hz Node Polarity Issues>>https://auspass.edu.au/xwiki/bin/view/Data/AusPass%20Data/#HSmartSoloNodePolarityIssues]] for discussion. If data is headed to AusPass, we prefer to invert the IGU-16HR channel data manually rather than in the SoloLite software or inverting the response metadata.
335 +
336 +**The BD3C-5 data does not require any sort of polarity inversion.**
337 +
338 +== 18 Leap Second bug ==
339 +
340 +Not so much a //bug// as much as "a thing that can happen if your SoloLite installation is corrupted". If you notice your data has large constant time offsets, you should suspect that the number of leap seconds has not been accounted properly. There is a file "smartsoloconfig.xml" that needs to be present in "C:\SmartSoloApps SoloLite" (e.g. the main program directory) that dictates the leap second offset for the last two data ranges. Since 2017-01-01, this is 18 seconds. At some point in the next few years it will be 19 seconds.
341 +
342 +If this file is missing, just create a new one structured like so, name it "smartsoloconfig.xml" and put it in your main program directory. Then, Reanalyze your data (tools > Reanalyze seismic data) and your data should have the correct time. You can also do this manually, if you want. The offset is 18 seconds precisely.
343 +
344 +{{code language="none"}}
345 +<?xml version="1.0" encoding="UTF-8"?>
346 +<config>
347 + <leapsecond>
348 + <interval>
349 + <start_time>2017-01-01#00:00:00</start_time>
350 + <end_time>2999-12-31#23:59:59</end_time>
351 + <second>18</second>
352 + </interval>
353 + <interval>
354 + <start_time>1970-01-01#00:00:00</start_time>
355 + <end_time>2017-01-01#00:00:00</end_time>
356 + <second>17</second>
357 + </interval>
358 + </leapsecond>
359 + <GPS_distance_threshold_degree>
360 + 4e-5
361 + </GPS_distance_threshold_degree>
362 +</config>
363 +{{/code}}
364 +
365 +
274 274  == Handling Nodes During Download ==
275 275  
276 276  1. (((
... ... @@ -326,23 +326,66 @@
326 326  
327 327  ----
328 328  
421 += Instrument Response =
422 +
423 +We are aware that there are various different published responses for these instruments and trust very few of them. One has to be careful with how polarity is handled between groups as well, and if one is working in integer counts (the ANSIR default) or mV (unclear why anyone would use this as it makes file sizes enormous). The response information published below is in **counts** and seems to fit well in huddle tests. Note that the response is the same for all channels and all units (e.g. there are no bespoke calibrations!), all appear to be sample rate insensitive, and the IGU data has been inverted (multiplied by -1) as described here: [[5Hz Node Polarity Issues>>https://auspass.edu.au/xwiki/bin/view/Data/AusPass%20Data/#HSmartSoloNodePolarityIssues]]
424 +
425 +== IGU 16HR-3C ==
426 +
427 + '16HR3C': {'poles':[(-22.211059+22.217768j), (-22.211059-22.217768j)],
428 + 'zeros':[0j, 0j],
429 + 'gain':1,
430 + 'sensitivity': 257019225.55108312}
431 +
432 +[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:IGU16_Z_huddle.png]]
433 +
434 +[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:IGU16_N_huddle.png]]
435 +
436 +== IGU 16-1C ==
437 +
438 +The 1C nodes seem to have a slightly different response to the 3C (TBA)
439 +
440 +== BD3C-5 ==
441 +
442 + 'BD3C': {'poles':[(-1720.4+0j), (-1.2+0.9j), (-1.2-0.9j)],
443 + 'zeros':[(14164+0j), (-7162+0j), 0j, 0j],
444 + 'gain':1.69726e-05,
445 + 'sensitivity': 702651512.6046528}
446 +
447 +[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:BD3C_Z_huddle.png]]
448 +
449 +[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:BD3C_N_huddle.png]]
450 +
451 +== Horizontal noise & how to avoid ==
452 +
453 +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.
454 +
455 +[[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]]
456 +
457 +(% class="wikigeneratedid" %)
458 +The BD3C-5 nodes do not have this issue:
459 +
460 +[[BD3C-5 test, as above. There is no additional noise on the horizontal channels.>>image:BD3C_psd.png]]
461 +
329 329  = **Cleaning** =
330 330  
331 -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.
464 +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.
332 332  
333 333  = **Weights (for shipping)** =
334 334  
335 335  The weights of bags of nodes, as well as data harvesters and node chargers, are listed below:
336 336  
337 -1 bag + 6 SP (IGU-16HR) nodes: 18 kg
470 +1 bag + 6*IGU-16HR nodes: 18 kg
338 338  
339 -1 SP (IGU-16HR) data harvester: 21.5 kg
472 +1*IGU-16HR data harvester: 21.5 kg
340 340  
341 -1 SP (IGU-16HR) charger: 26.3 kg
474 +1*IGU-16HR charger: 26.3 kg
342 342  
343 -1 BB (BD3C-5) charger/data harvester (with and without 16 cables): 21 kg / 14.5 kg
476 +1*BD3C-5 charger (with and without 16 cables): 21 kg / 14.5 kg
344 344  
345 -1 case + 5 BB (BD3C-5) nodes and 6 BB nodes: 22 kg / 25 kg
478 +1 case + 5*BD3C-5 nodes: 22 kg (aggregate battery weight <5kg, 168Wh)
479 +
480 +1 case + 6*BD3C-5 nodes: 25 kg (aggregate battery weight >5kg, 168Wh)
346 346  )))
347 347  
348 348  (% class="col-xs-12 col-sm-4" %)
... ... @@ -366,7 +366,7 @@
366 366  
367 367  |(% style="width:189px" %)**Frequency Band**|(% style="width:221px" %)5 Seconds to 150Hz
368 368  |(% style="width:189px" %)**Sensitivity**|(% style="width:221px" %)200 V/m/s
369 -|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)158 x160mm
504 +|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)Φ158 x160mm(H)
370 370  |(% style="width:189px" %)**Weight**|(% style="width:221px" %)2.8 kg
371 371  |(% style="width:189px" %)**Data Storage**|(% style="width:221px" %)64 Gb
372 372  |(% style="width:189px" %)**Battery**|(% style="width:221px" %)(((
... ... @@ -385,8 +385,8 @@
385 385  [[image:smartsolo node 2.jpg]]
386 386  
387 387  |(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 1652Hz
388 -|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)67.7 V/m/s
389 -|(% style="width:187px" %)**Size (with spike)**|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm
523 +|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)76.7 V/m/s
524 +|(% style="width:187px" %)**Size (with spike)**|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm(H)
390 390  |(% style="width:187px" %)**Weight**|(% style="width:224px" %)2.4 kg
391 391  |(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)64 Gb
392 392  |(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((
... ... @@ -398,6 +398,27 @@
398 398  
399 399  (% class="box" %)
400 400  (((
536 +
537 +
538 += SmartSolo [[IGU-16>>url:https://smartsolo.com/cp-3.html]]1C =
539 +
540 +
541 +[[image:Screenshot 2025-08-01 161027.png]]
542 +
543 +|(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 413Hz
544 +|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)80 V/m/s
545 +|(% style="width:187px" %)**Size (without spike)**|(% style="width:224px" %)95mm(L) × 103mm(W) × 118mm(H)
546 +|(% style="width:187px" %)**Weight**|(% style="width:224px" %)1.1 kg
547 +|(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)8 Gb
548 +|(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((
549 +Lithium-ion battery contained in equipment (38.48 Wh)
550 +
551 +UN3481 PI967 S2
552 +)))
553 +)))
554 +
555 +(% class="box" %)
556 +(((
401 401  = SmartSolo BD3C-16 Portable Battery Charger =
402 402  
403 403  [[image:20250729_125049.jpg]]
... ... @@ -405,8 +405,8 @@
405 405  |**Dimensions (LxHxW)**|558 x 357 x 300mm
406 406  |**Input rating**|100-210V - 50/60Hz
407 407  |**Power**|1000W
408 -|**Weight**|14.5kg
409 -|**Weight with cables**|21kg
564 +|**Weight**|14.5 kg
565 +|**Weight with cables**|21 kg
410 410  )))
411 411  
412 412  (% class="box" id="HSmartSoloBD3C-16PortableBatteryCharger" %)
... ... @@ -418,8 +418,8 @@
418 418  |**Dimensions (LxHxW)**|625 x 500 x 366mm
419 419  |**Input rating**|100-210V - 50/60Hz
420 420  |**Power**|100W
421 -|**Weight**|21.5 - 24kg
422 -|**Slots no.**|16
577 +|**Weight**|21.5 - 24 kg
578 +|**Capacity**|16 nodes
423 423  |**Download Speed**|20MB/sec/slot
424 424  )))
425 425  
... ... @@ -427,25 +427,25 @@
427 427  (((
428 428  = SmartSolo IGU-16 Portable Battery Charger =
429 429  
430 -= [[image:20250729_124644.jpg]] =
586 +[[image:20250729_124644.jpg]]
431 431  
432 -|**Dimensions (LxHxW)**|625 x 500 x 366mm
433 -|**Input rating**|100-210V - 50/60Hz
434 -|**Power**|640W
435 -|**Weight**|26.3kg
436 -|**Slots no.**|16
588 +|**Dimensions (LxHxW)**|625 x 500 x 366 mm
589 +|**Input rating**|100-210V - 50/60 Hz
590 +|**Power**|640 W
591 +|**Weight**|26.3 kg
592 +|**Capacity**|16 nodes
437 437  )))
438 438  
439 439  (% class="box" %)
440 440  (((
441 -= SmartSolo BD3C-5 Carry Bag =
597 += SmartSolo BD3C-5 Carry Case =
442 442  
443 443  [[image:20250729_124957.jpg]]
444 444  
445 445  
446 -|**Dimensions (LxHxW)**|590 x 225 x 405mm
447 -|**Weight**|8.2kg
448 -|**Slots no.**|6
602 +|**Dimensions (LxHxW)**|590 x 225 x 405 mm
603 +|**Weight**|8.2 kg
604 +|**Capacity**|6 nodes
449 449  )))
450 450  
451 451  (% class="box" %)
... ... @@ -455,9 +455,13 @@
455 455  [[image:20250729_124502.jpg]]
456 456  
457 457  |**Dimensions (LxHxW)**|230 x 340 x 310mm
458 -|**Weight**|3.6kg
459 -|**Slots no.**|6
614 +|**Weight**|(((
615 +3.6kg (empty)
616 +
617 +18.0kg (full)
460 460  )))
619 +|**Capacity**|6 nodes
620 +)))
461 461  
462 462  (% class="box" %)
463 463  (((
... ... @@ -467,7 +467,7 @@
467 467  
468 468  |**Dimensions (LxHxW)**|225 x 200 x 550mm
469 469  |**Weight**|
470 -|**Slots no.**|6
630 +|**Capacity**|8 nodes
471 471  )))
472 472  )))
473 473  )))
5Hz_node_programming.labels.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.KB
Size
... ... @@ -1,0 +1,1 @@
1 +109.8 KB
Content
5S_node_programming.labels.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.KB
Size
... ... @@ -1,0 +1,1 @@
1 +114.2 KB
Content
BD3C_N_huddle.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.robert
Size
... ... @@ -1,0 +1,1 @@
1 +73.3 KB
Content
BD3C_Z_huddle.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.robert
Size
... ... @@ -1,0 +1,1 @@
1 +64.6 KB
Content
BD3C_psd.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.robert
Size
... ... @@ -1,0 +1,1 @@
1 +73.7 KB
Content
IGU16_N_huddle.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.robert
Size
... ... @@ -1,0 +1,1 @@
1 +65.7 KB
Content
IGU16_Z_huddle.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.robert
Size
... ... @@ -1,0 +1,1 @@
1 +67.4 KB
Content
IGU16_spectrum.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.robert
Size
... ... @@ -1,0 +1,1 @@
1 +65.0 KB
Content
Screenshot 2025-08-01 161027.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.JackD
Size
... ... @@ -1,0 +1,1 @@
1 +82.8 KB
Content