Skip to Content
Last modified by KB on 2025/12/04 12:33
From version 90.1
edited by KB
on 2025/12/04 12:31
Change comment: There is no comment for this version
To version 59.2
edited by robert
on 2025/07/16 15:55
Change comment: allow view right for XWiki.XWikiAllGroup

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.KB
1 +XWiki.robert
Content
... ... @@ -4,61 +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 9  * **SmartSolo IGU 16HR 3C (5 Hz Short Period)**
10 -* **SmartSolo BD3C-5 (5 Second Broadband)**
11 -* **SmartSolo IGU 16 1C (5 Hz Short Period, single channel)**
10 +* **SmartSolo BD3C-5 (5 Second Broad-Band)**
12 12  
13 -The three-channel nodes have a 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 feasibility for 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. Screenshots for the short period 16HR-3C and broadband BDC3-5 are shown with our recommended parameters.
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 -[[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"]]
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 (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"]]
29 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 -
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 -
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 -
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 -
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 -
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.
41 -
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.
43 -
44 -Bluetooth (BB nodes only) should be turned OFF to conserve power.
45 -
46 -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 -
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}}
51 -
52 52  = **Fieldwork Preparation** =
53 53  
26 +(% class="box infomessage" %)
27 +(((
54 54  (% class="box warningmessage" %)
55 55  (((
56 56  **INVEST IN FAST EXTERNAL HARD DRIVES – DO NOT LET THIS BE THE LIMITATION OF DATA HARVESTING**
57 57  
58 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.**
59 -
60 -**We have had good experience with the 4Tb Samsung T7 Shield drives.**
61 61  )))
34 +)))
62 62  
63 63  == Magnets ==
64 64  
... ... @@ -70,26 +70,19 @@
70 70  
71 71  = **Installation** =
72 72  
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 -)))
46 +== **1. Logbook documentation** ==
77 77  
78 -== 1. Logbook documentation ==
79 -
80 80  (((
81 -**Essential Details** for field logs:
49 +**Essential Details**: Record the following in a logbook:
82 82  
83 83  * Station name
84 -* Latitude, longitude, elevation
52 +* Latitude and longitude
85 85  * Names of team members present
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)
54 +* Date and local time of installation
55 +* Serial number (SN) of the sensor
56 +* Detailed notes on the site conditions and setup
89 89  
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 -
92 -== 2. Node Placement ==
58 +== **2. Node Placement** ==
93 93  )))
94 94  
95 95  **Protection**: Place nodes inside (landfill) biodegradable bags to minimize cleaning and cross-site soil contamination.
... ... @@ -97,15 +97,15 @@
97 97  **Site Analysis**:
98 98  
99 99  * **Take compass measurements away from the sensor as it will affect your measurement.**
100 -* Take photographs from various angles to document the site setup thoroughly.
101 -* 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)
102 102  
103 -== 3. GPS Considerations ==
69 +== **3. GPS Considerations** ==
104 104  
105 105  (% class="wikigeneratedid" %)
106 106  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.
107 107  
108 -== 4. Visibility and Location Marking ==
74 +== **4. Visibility and Location Marking** ==
109 109  
110 110  **Flag Placement**: Position a flag, preferably in a bright color (avoid green or yellow), near the instrument to aid in its future location.
111 111  
... ... @@ -114,7 +114,7 @@
114 114  * Use a GPS device to mark the instrument's exact location.
115 115  * Record this location in both your paper notes and the GPS device.
116 116  
117 -== (% 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**(%%) ==
118 118  
119 119  * **Charging Duration**: Both types of nodes take approximately 6-8 hours to fully charge from a flat state.
120 120  * **Pre-Deployment Charging**:
... ... @@ -128,10 +128,10 @@
128 128  * **Storage and Shipping Charge Level**:
129 129  ** Maintain a battery charge level of around 50-60% (e.g. "orange") for both storage and shipping purposes.
130 130  ** This charge level is recommended to prevent battery damage and is safe for transportation.
131 -** Nodes should not be stored fully charged, and **they should especially not be stored with 0 charge as this damages lithium batteries.**
97 +** Nodes should not be stored fully charged, and it **they should especially not be stored with 0 charge.**
132 132  
133 133  (((
134 -== 6. Data Sharing and Metadata Creation ==
100 +== **6. Data Sharing and Metadata Creation** ==
135 135  )))
136 136  
137 137  **GPS Data**:
... ... @@ -144,9 +144,9 @@
144 144  
145 145  **Metadata File**:
146 146  
147 -* 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]].
148 148  
149 -== 7. Additional Best Practices ==
115 +== **7. Additional Best Practices** ==
150 150  
151 151  * **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.
152 152  
... ... @@ -201,25 +201,25 @@
201 201  = **Charging Procedure for Seismic Nodes** =
202 202  
203 203  (((
204 -== 1. Preparation for Charging: ==
170 +== **1. Preparation for Charging**: ==
205 205  
206 206  * 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.
207 207  )))
208 208  
209 209  (((
210 -== 2. Disassembling the Node: ==
176 +== **2. Disassembling the Node**: ==
211 211  
212 212  * For the IGU-16HR, remove the battery (bottom half) from the sensor. This is done by unscrewing the spikes counter-clockwise.
213 213  )))
214 214  
215 215  (((
216 -== 3. Setting Nodes in the Charging Box: ==
182 +== **3. Setting Nodes in the Charging Box**: ==
217 217  
218 218  * Place 1-16 IGU-16HR battery components upside-down into the charger, assuring they are oriented properly.
219 219  )))
220 220  
221 221  (((
222 -== 4. Monitoring the Charging Process: ==
188 +== **4. Monitoring the Charging Process**: ==
223 223  
224 224  * 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.
225 225  * 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.
... ... @@ -226,7 +226,7 @@
226 226  )))
227 227  
228 228  (((
229 -== 5. Updating Charge Status: ==
195 +== **5. Updating Charge Status**: ==
230 230  
231 231  * 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.
232 232  * This step is crucial for tracking the charging status of multiple units, especially when handling a large number of nodes.
... ... @@ -237,29 +237,14 @@
237 237  
238 238  
239 239  
240 -{{{
241 - }}}
206 +[[image:1706153354750-415.png||data-xwiki-image-style-alignment="center" height="317" width="562"]]
242 242  
243 243  ----
244 244  
245 245  = **Downloading and Converting Seismic Data to MiniSeed Format** =
246 246  
247 -(% class="wikigeneratedid" %)
248 -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** ==
249 249  
250 -== Connection tips: ==
251 -
252 -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:
253 -
254 -* Place the node on the harvester gently, then firmly press it down onto the pins.
255 -* 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.
256 -* 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.
257 -* 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!
258 -
259 -
260 -
261 -== Node Registration and Software Setup ==
262 -
263 263  1. (((
264 264  **Registering Nodes in the System**:
265 265  
... ... @@ -276,29 +276,8 @@
276 276  * Ignore the settings for seismic recordings in the subsequent window. Resetting instruments (e.g., sampling rate, gain) requires reprogramming via script.
277 277  )))
278 278  
279 -== File structure ==
230 +== **Data Downloading Process** ==
280 280  
281 -There are essentially three main folders where relevant PROSPECT and PROJECT DATA is stored. Individual projects will be found as subfolders in these.
282 -
283 -=== SOLOLITE ===
284 -
285 -This folder stores SoloLite config files and parameters. Nothing too important stored here, you can always start over and re-create this.
286 -
287 -=== DCCDATA ===
288 -
289 -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.
290 -
291 -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)//
292 -
293 -Then in the SoloLite software, go to tools > Reanalyze Seismic Data
294 -
295 -=== SOLODATA ===
296 -
297 -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.
298 -
299 -
300 -== Data Downloading Process ==
301 -
302 302  1. (((
303 303  **Initiating Data Download**:
304 304  
... ... @@ -315,46 +315,14 @@
315 315  * Click “prepare” followed by “run” to start reformatting. Monitor this process in the small panel at the bottom left.
316 316  * (% class="box warningmessage" %)
317 317  (((
318 -* **Ensure to export data as "COUNTS" (int32), not "mV" (float). This is critical!**
248 +* **Ensure to export data as "COUNTS", not "mV".**
319 319  
320 -* **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).**
321 321  )))
322 322  )))
323 323  
324 -== Smart Solo Z Polarity bug (SP nodes ONLY!) ==
254 +== **Handling Nodes During Download** ==
325 325  
326 -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 3 Z channel data manually rather than in the SoloLite software or inverting the response metadata. **The BD3C-5 data does not require a polarity inversion.**
327 -
328 -== 18 Leap Second bug ==
329 -
330 -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 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.
331 -
332 -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.
333 -
334 -{{code language="none"}}
335 -<?xml version="1.0" encoding="UTF-8"?>
336 -<config>
337 - <leapsecond>
338 - <interval>
339 - <start_time>2017-01-01#00:00:00</start_time>
340 - <end_time>2999-12-31#23:59:59</end_time>
341 - <second>18</second>
342 - </interval>
343 - <interval>
344 - <start_time>1970-01-01#00:00:00</start_time>
345 - <end_time>2017-01-01#00:00:00</end_time>
346 - <second>17</second>
347 - </interval>
348 - </leapsecond>
349 - <GPS_distance_threshold_degree>
350 - 4e-5
351 - </GPS_distance_threshold_degree>
352 -</config>
353 -{{/code}}
354 -
355 -
356 -== Handling Nodes During Download ==
357 -
358 358  1. (((
359 359  **Monitoring Download Indicators**:
360 360  
... ... @@ -370,7 +370,6 @@
370 370  * **Use fast external hard drives to avoid limitations in data harvesting.**
371 371  
372 372  * **Recommended specifications: USB-C, USB 3.0, and 4+ Tb of space.**
373 -* **The USB type for the harvester is TYPE-A, the typical normal rectangular shape.**
374 374  )))
375 375  )))
376 376  1. (((
... ... @@ -410,7 +410,7 @@
410 410  
411 411  = **Cleaning** =
412 412  
413 -When still connected, the nodes are water resistant (don't submerge them!) and can handle a good spray / 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.
414 414  
415 415  = **Weights (for shipping)** =
416 416  
... ... @@ -448,7 +448,7 @@
448 448  
449 449  |(% style="width:189px" %)**Frequency Band**|(% style="width:221px" %)5 Seconds to 150Hz
450 450  |(% style="width:189px" %)**Sensitivity**|(% style="width:221px" %)200 V/m/s
451 -|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)Φ158 x160mm(H)
348 +|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)158 x160mm
452 452  |(% style="width:189px" %)**Weight**|(% style="width:221px" %)2.8 kg
453 453  |(% style="width:189px" %)**Data Storage**|(% style="width:221px" %)64 Gb
454 454  |(% style="width:189px" %)**Battery**|(% style="width:221px" %)(((
... ... @@ -460,7 +460,7 @@
460 460  
461 461  (% class="box" %)
462 462  (((
463 -= SmartSolo [[IGU-16HR>>url:https://smartsolo.com/cp-3.html]]3C =
360 += SmartSolo [[IGU-16HR>>url:https://smartsolo.com/cp-3.html]] =
464 464  
465 465  [[image:smartsolo node.jpg]]
466 466  
... ... @@ -467,8 +467,8 @@
467 467  [[image:smartsolo node 2.jpg]]
468 468  
469 469  |(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 1652Hz
470 -|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)76.7 V/m/s
471 -|(% 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
472 472  |(% style="width:187px" %)**Weight**|(% style="width:224px" %)2.4 kg
473 473  |(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)64 Gb
474 474  |(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((
... ... @@ -478,99 +478,6 @@
478 478  )))
479 479  )))
480 480  
481 -(% class="box" %)
482 -(((
483 483  
484 -
485 -= SmartSolo [[IGU-16>>url:https://smartsolo.com/cp-3.html]]1C =
486 -
487 -
488 -[[image:Screenshot 2025-08-01 161027.png]]
489 -
490 -|(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 413Hz
491 -|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)80 V/m/s
492 -|(% style="width:187px" %)**Size (without spike)**|(% style="width:224px" %)95mm(L) × 103mm(W) × 118mm(H)
493 -|(% style="width:187px" %)**Weight**|(% style="width:224px" %)1.1 kg
494 -|(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)8 Gb
495 -|(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((
496 -Lithium-ion battery contained in equipment (38.48 Wh)
497 -
498 -UN3481 PI967 S2
499 499  )))
500 500  )))
501 -
502 -(% class="box" %)
503 -(((
504 -= SmartSolo BD3C-16 Portable Battery Charger =
505 -
506 -[[image:20250729_125049.jpg]]
507 -
508 -|**Dimensions (LxHxW)**|558 x 357 x 300mm
509 -|**Input rating**|100-210V - 50/60Hz
510 -|**Power**|1000W
511 -|**Weight**|14.5kg
512 -|**Weight with cables**|21kg
513 -)))
514 -
515 -(% class="box" id="HSmartSoloBD3C-16PortableBatteryCharger" %)
516 -(((
517 -= SmartSolo IGU-16 Portable Data Harvester =
518 -
519 -[[image:20250729_124747.jpg]]
520 -
521 -|**Dimensions (LxHxW)**|625 x 500 x 366mm
522 -|**Input rating**|100-210V - 50/60Hz
523 -|**Power**|100W
524 -|**Weight**|21.5 - 24kg
525 -|**Slots no.**|16
526 -|**Download Speed**|20MB/sec/slot
527 -)))
528 -
529 -(% class="box" %)
530 -(((
531 -= SmartSolo IGU-16 Portable Battery Charger =
532 -
533 -[[image:20250729_124644.jpg]]
534 -
535 -|**Dimensions (LxHxW)**|625 x 500 x 366mm
536 -|**Input rating**|100-210V - 50/60Hz
537 -|**Power**|640W
538 -|**Weight**|26.3kg
539 -|**Slots no.**|16
540 -)))
541 -
542 -(% class="box" %)
543 -(((
544 -= SmartSolo BD3C-5 Carry Case =
545 -
546 -[[image:20250729_124957.jpg]]
547 -
548 -
549 -|**Dimensions (LxHxW)**|590 x 225 x 405mm
550 -|**Weight**|8.2kg
551 -|**Slots no.**|6
552 -)))
553 -
554 -(% class="box" %)
555 -(((
556 -= SmartSolo IGU-16 3C Carry Bag =
557 -
558 -[[image:20250729_124502.jpg]]
559 -
560 -|**Dimensions (LxHxW)**|230 x 340 x 310mm
561 -|**Weight**|3.6kg
562 -|**Slots no.**|6
563 -)))
564 -
565 -(% class="box" %)
566 -(((
567 -= SmartSolo IGU-16 1C Carry Bag =
568 -
569 -[[image:20250729_124558.jpg]]
570 -
571 -|**Dimensions (LxHxW)**|225 x 200 x 550mm
572 -|**Weight**|
573 -|**Slots no.**|6
574 -)))
575 -)))
576 -)))
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
BB_programming.labels.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -111.5 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
XWiki.XWikiRights[0]
Levels
... ... @@ -1,1 +1,1 @@
1 -comment
1 +view
XWiki.XWikiRights[1]
Allow/Deny
... ... @@ -1,1 +1,0 @@
1 -Allow
Levels
... ... @@ -1,1 +1,0 @@
1 -comment
Users
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest