Skip to Content
Last modified by robert on 2026/02/27 19:58
From version 108.1
edited by robert
on 2026/02/18 14:46
Change comment: There is no comment for this version
To version 75.1
edited by robert
on 2025/07/31 20:04
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -4,36 +4,25 @@
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. Not 'HR')**
9 +* **SmartSolo IGU 16HR 3C (5 Hz Short Period)**
10 +* **SmartSolo BD3C-5 (5 Second Broadband)**
12 12  
13 -Visit the [[SmartSolo page>>https://smartsolo.com/igu.html]] for more detail.
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 -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 -
22 22  ----
23 23  
24 24  = **Programming Defaults** =
25 25  
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.
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.
27 27  
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"]]
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"]]
29 29  
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!"]]
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"]]
31 31  
32 -
33 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 34  
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 -
37 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 38  
39 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!**
... ... @@ -44,9 +44,9 @@
44 44  
45 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.
46 46  
47 -Bluetooth (BD3C-5 only) should be turned OFF to conserve power.
36 +Bluetooth (BB nodes only) should be turned OFF to conserve power.
48 48  
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).
38 +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).
50 50  
51 51  {{info}}
52 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!
... ... @@ -69,10 +69,8 @@
69 69  
70 70  == Animal-Proofing ==
71 71  
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.
61 +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.
73 73  
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 -
76 76  = **Installation** =
77 77  
78 78  (% class="box infomessage" %)
... ... @@ -97,6 +97,8 @@
97 97  == 2. Node Placement ==
98 98  )))
99 99  
87 +**Protection**: Place nodes inside (landfill) biodegradable bags to minimize cleaning and cross-site soil contamination.
88 +
100 100  **Site Analysis**:
101 101  
102 102  * **Take compass measurements away from the sensor as it will affect your measurement.**
... ... @@ -127,14 +127,11 @@
127 127  ** 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.
128 128  
129 129  * **Post-Retrieval Charging**:
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).
119 +** After retrieval, charge the instruments to about 50-60% (indicated as "orange" level) unless they are to be immediately re-deployed.
120 +* **Storage and Shipping Charge Level**:
121 +** Maintain a battery charge level of around 50-60% (e.g. "orange") for both storage and shipping purposes.
122 +** This charge level is recommended to prevent battery damage and is safe for transportation.
123 +** Nodes should not be stored fully charged, and **they should especially not be stored with 0 charge as this damages lithium batteries.**
138 138  
139 139  (((
140 140  == 6. Data Sharing and Metadata Creation ==
... ... @@ -142,7 +142,7 @@
142 142  
143 143  **GPS Data**:
144 144  
145 -* Ensure you have __carefully documented__ precise lat/lon locations for each station.
131 +* Ensure you have documented precise lat/lon locations for each station and **DOCUMENTED THIS CAREFULLY**
146 146  
147 147  **Photo Sharing**:
148 148  
... ... @@ -215,22 +215,20 @@
215 215  (((
216 216  == 2. Disassembling the Node: ==
217 217  
218 -* For the IGU-16HR, remove the battery section (bottom half) from the sensor by unscrewing the spike section counter-clockwise.
204 +* For the IGU-16HR, remove the battery (bottom half) from the sensor. This is done by unscrewing the spikes counter-clockwise.
219 219  )))
220 220  
221 221  (((
222 222  == 3. Setting Nodes in the Charging Box: ==
223 223  
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.
210 +* Place 1-16 IGU-16HR battery components upside-down into the charger, assuring they are oriented properly.
227 227  )))
228 228  
229 229  (((
230 230  == 4. Monitoring the Charging Process: ==
231 231  
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.
216 +* 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.
217 +* 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.
234 234  )))
235 235  
236 236  (((
... ... @@ -245,27 +245,12 @@
245 245  
246 246  
247 247  
248 -{{{
249 - }}}
232 +[[image:1706153354750-415.png||data-xwiki-image-style-alignment="center" height="317" width="562"]]
250 250  
251 251  ----
252 252  
253 253  = **Downloading and Converting Seismic Data to MiniSeed Format** =
254 254  
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 -
269 269  == Node Registration and Software Setup ==
270 270  
271 271  1. (((
... ... @@ -284,27 +284,6 @@
284 284  * Ignore the settings for seismic recordings in the subsequent window. Resetting instruments (e.g., sampling rate, gain) requires reprogramming via script.
285 285  )))
286 286  
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 -
308 308  == Data Downloading Process ==
309 309  
310 310  1. (((
... ... @@ -329,40 +329,6 @@
329 329  )))
330 330  )))
331 331  
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 -
366 366  == Handling Nodes During Download ==
367 367  
368 368  1. (((
... ... @@ -418,78 +418,23 @@
418 418  
419 419  ----
420 420  
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 bandpass filter>>image:IGU16_N_huddle.png]]
435 -
436 -== IGU 16-1C ==
437 -
438 -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.
439 -
440 -[[IGU-16 1C, X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz bandpass filter. Seems to be same response as IGU-16HR-3C.>>image:IGU16_1C_Z_huddle.png]]
441 -
442 -== BD3C-5 ==
443 -
444 - 'BD3C': {'poles':[(-1720.4+0j), (-1.2+0.9j), (-1.2-0.9j)],
445 - 'zeros':[(14164+0j), (-7162+0j), 0j, 0j],
446 - 'gain':1.69726e-05,
447 - 'sensitivity': 702651512.6046528}
448 -
449 -Above 0.5 Hz, the BD3C-5 response fits well:
450 -
451 -[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:BD3C_Z_huddle.0.5.png]]
452 -
453 -[[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]]
454 -
455 -(% class="wikigeneratedid" %)
456 -Below the corner frequency 0.2 Hz (5 seconds) the response still does a good job, but may need to be dialed in a bit. In the next two figures the filter is 0.1 to 5 Hz. We are looking into this..
457 -
458 -
459 -[[BD3C **0.1 **to 5 Hz bandpass filter>>image:BD3C_Z_huddle.0.1.png]]
460 -
461 -[[BD3C **0.1** to 5 Hz bandpass filter>>image:BD3C_N_huddle.0.1.png]]
462 -
463 -== IGU-16 Horizontal noise & how to avoid ==
464 -
465 -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.
466 -
467 -[[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]]
468 -
469 -(% class="wikigeneratedid" %)
470 -The BD3C-5 nodes do not have this issue:
471 -
472 -[[BD3C-5 test, as above. There is no additional noise on the horizontal channels.>>image:BD3C_psd.png]]
473 -
474 474  = **Cleaning** =
475 475  
476 -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.
337 +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.
477 477  
478 478  = **Weights (for shipping)** =
479 479  
480 480  The weights of bags of nodes, as well as data harvesters and node chargers, are listed below:
481 481  
482 -1 bag + 6*IGU-16HR nodes: 18 kg
343 +1 bag + 6 SP (IGU-16HR) nodes: 18 kg
483 483  
484 -1*IGU-16HR data harvester: 21.5 kg
345 +1 SP (IGU-16HR) data harvester: 21.5 kg
485 485  
486 -1*IGU-16HR charger: 26.3 kg
347 +1 SP (IGU-16HR) charger: 26.3 kg
487 487  
488 -1*BD3C-5 charger (with and without 16 cables): 21 kg / 14.5 kg
349 +1 BB (BD3C-5) charger/data harvester (with and without 16 cables): 21 kg / 14.5 kg
489 489  
490 -1 case + 5*BD3C-5 nodes: 22 kg (aggregate battery weight <5kg, 168Wh)
491 -
492 -1 case + 6*BD3C-5 nodes: 25 kg (aggregate battery weight >5kg, 168Wh)
351 +1 case + 5 BB (BD3C-5) nodes and 6 BB nodes: 22 kg / 25 kg
493 493  )))
494 494  
495 495  (% class="col-xs-12 col-sm-4" %)
... ... @@ -513,7 +513,7 @@
513 513  
514 514  |(% style="width:189px" %)**Frequency Band**|(% style="width:221px" %)5 Seconds to 150Hz
515 515  |(% style="width:189px" %)**Sensitivity**|(% style="width:221px" %)200 V/m/s
516 -|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)Φ158 x160mm(H)
375 +|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)158 x160mm
517 517  |(% style="width:189px" %)**Weight**|(% style="width:221px" %)2.8 kg
518 518  |(% style="width:189px" %)**Data Storage**|(% style="width:221px" %)64 Gb
519 519  |(% style="width:189px" %)**Battery**|(% style="width:221px" %)(((
... ... @@ -532,8 +532,8 @@
532 532  [[image:smartsolo node 2.jpg]]
533 533  
534 534  |(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 1652Hz
535 -|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)76.7 V/m/s
536 -|(% style="width:187px" %)**Size (with spike)**|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm(H)
394 +|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)67.7 V/m/s
395 +|(% style="width:187px" %)**Size (with spike)**|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm
537 537  |(% style="width:187px" %)**Weight**|(% style="width:224px" %)2.4 kg
538 538  |(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)64 Gb
539 539  |(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((
... ... @@ -545,27 +545,6 @@
545 545  
546 546  (% class="box" %)
547 547  (((
548 -
549 -
550 -= SmartSolo [[IGU-16>>url:https://smartsolo.com/cp-3.html]]1C =
551 -
552 -
553 -[[image:Screenshot 2025-08-01 161027.png]]
554 -
555 -|(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 413Hz
556 -|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)80 V/m/s
557 -|(% style="width:187px" %)**Size (without spike)**|(% style="width:224px" %)95mm(L) × 103mm(W) × 118mm(H)
558 -|(% style="width:187px" %)**Weight**|(% style="width:224px" %)1.1 kg
559 -|(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)8 Gb
560 -|(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((
561 -Lithium-ion battery contained in equipment (38.48 Wh)
562 -
563 -UN3481 PI967 S2
564 -)))
565 -)))
566 -
567 -(% class="box" %)
568 -(((
569 569  = SmartSolo BD3C-16 Portable Battery Charger =
570 570  
571 571  [[image:20250729_125049.jpg]]
... ... @@ -573,8 +573,8 @@
573 573  |**Dimensions (LxHxW)**|558 x 357 x 300mm
574 574  |**Input rating**|100-210V - 50/60Hz
575 575  |**Power**|1000W
576 -|**Weight**|14.5 kg
577 -|**Weight with cables**|21 kg
414 +|**Weight**|14.5kg
415 +|**Weight with cables**|21kg
578 578  )))
579 579  
580 580  (% class="box" id="HSmartSoloBD3C-16PortableBatteryCharger" %)
... ... @@ -586,8 +586,8 @@
586 586  |**Dimensions (LxHxW)**|625 x 500 x 366mm
587 587  |**Input rating**|100-210V - 50/60Hz
588 588  |**Power**|100W
589 -|**Weight**|21.5 - 24 kg
590 -|**Capacity**|16 nodes
427 +|**Weight**|21.5 - 24kg
428 +|**Slots no.**|16
591 591  |**Download Speed**|20MB/sec/slot
592 592  )))
593 593  
... ... @@ -595,25 +595,25 @@
595 595  (((
596 596  = SmartSolo IGU-16 Portable Battery Charger =
597 597  
598 -[[image:20250729_124644.jpg]]
436 += [[image:20250729_124644.jpg]] =
599 599  
600 -|**Dimensions (LxHxW)**|625 x 500 x 366 mm
601 -|**Input rating**|100-210V - 50/60 Hz
602 -|**Power**|640 W
603 -|**Weight**|26.3 kg
604 -|**Capacity**|16 nodes
438 +|**Dimensions (LxHxW)**|625 x 500 x 366mm
439 +|**Input rating**|100-210V - 50/60Hz
440 +|**Power**|640W
441 +|**Weight**|26.3kg
442 +|**Slots no.**|16
605 605  )))
606 606  
607 607  (% class="box" %)
608 608  (((
609 -= SmartSolo BD3C-5 Carry Case =
447 += SmartSolo BD3C-5 Carry Bag =
610 610  
611 611  [[image:20250729_124957.jpg]]
612 612  
613 613  
614 -|**Dimensions (LxHxW)**|590 x 225 x 405 mm
615 -|**Weight**|8.2 kg
616 -|**Capacity**|6 nodes
452 +|**Dimensions (LxHxW)**|590 x 225 x 405mm
453 +|**Weight**|8.2kg
454 +|**Slots no.**|6
617 617  )))
618 618  
619 619  (% class="box" %)
... ... @@ -623,13 +623,9 @@
623 623  [[image:20250729_124502.jpg]]
624 624  
625 625  |**Dimensions (LxHxW)**|230 x 340 x 310mm
626 -|**Weight**|(((
627 -3.6kg (empty)
628 -
629 -18.0kg (full)
464 +|**Weight**|3.6kg
465 +|**Slots no.**|6
630 630  )))
631 -|**Capacity**|6 nodes
632 -)))
633 633  
634 634  (% class="box" %)
635 635  (((
... ... @@ -639,7 +639,7 @@
639 639  
640 640  |**Dimensions (LxHxW)**|225 x 200 x 550mm
641 641  |**Weight**|
642 -|**Capacity**|8 nodes
476 +|**Slots no.**|6
643 643  )))
644 644  )))
645 645  )))
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
BD3C_N_huddle.0.1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -72.1 KB
Content
BD3C_N_huddle.0.5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -73.3 KB
Content
BD3C_N_huddle.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -72.1 KB
Content
BD3C_Z_huddle.0.1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -52.1 KB
Content
BD3C_Z_huddle.0.5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -64.6 KB
Content
BD3C_Z_huddle.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -52.1 KB
Content
BD3C_psd.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -73.7 KB
Content
IGU16_1C_Z_huddle.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -72.3 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
Screenshot 2025-08-01 161027.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -82.8 KB
Content