Skip to Content
Last modified by robert on 2025/10/29 10:39
From version 60.2
edited by robert
on 2025/07/16 16:08
Change comment: Deleted object
To version 89.1
edited by robert
on 2025/10/28 18:01
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -4,27 +4,48 @@
4 4  (((
5 5  = **Node Types** =
6 6  
7 -ANSIR carry two types of three-channel nodes
7 +ANSIR carry two types of three-channel nodes, and one type of one-channel node:
8 8  
9 9  * **SmartSolo IGU 16HR 3C (5 Hz Short Period)**
10 -* **SmartSolo BD3C-5 (5 Second Broad-Band)**
10 +* **SmartSolo BD3C-5 (5 Second Broadband)**
11 +* **SmartSolo IGU 16 1C (5 Hz Short Period, single channel)**
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 +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.
13 13  
14 -
15 15  ----
16 16  
17 17  = **Programming Defaults** =
18 18  
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.
19 +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.
20 20  
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.
21 +[[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"]]
22 22  
23 +[[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"]]
23 23  
25 +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.
26 +
27 +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.
28 +
29 +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.
30 +
31 +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!**
32 +
33 +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.
34 +
35 +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.
36 +
37 +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.
38 +
39 +Bluetooth (BB nodes only) should be turned OFF to conserve power.
40 +
41 +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).
42 +
43 +{{info}}
44 +**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!
45 +{{/info}}
46 +
24 24  = **Fieldwork Preparation** =
25 25  
26 -(% class="box infomessage" %)
27 -(((
28 28  (% class="box warningmessage" %)
29 29  (((
30 30  **INVEST IN FAST EXTERNAL HARD DRIVES – DO NOT LET THIS BE THE LIMITATION OF DATA HARVESTING**
... ... @@ -33,7 +33,6 @@
33 33  
34 34  **We have had good experience with the 4Tb Samsung T7 Shield drives.**
35 35  )))
36 -)))
37 37  
38 38  == Magnets ==
39 39  
... ... @@ -45,19 +45,26 @@
45 45  
46 46  = **Installation** =
47 47  
48 -== **1. Logbook documentation** ==
68 +(% class="box infomessage" %)
69 +(((
70 +**Field logs are a critical component of fieldwork and this is especially the case for large N nodal deploys. Take notes!**
71 +)))
49 49  
73 +== 1. Logbook documentation ==
74 +
50 50  (((
51 -**Essential Details**: Record the following in a logbook:
76 +**Essential Details** for field logs:
52 52  
53 53  * Station name
54 -* Latitude and longitude
79 +* Latitude, longitude, elevation
55 55  * Names of team members present
56 -* Date and local time of installation
57 -* Serial number (SN) of the sensor
58 -* Detailed notes on the site conditions and setup
81 +* Date and both local & UTC time of installation/removal
82 +* Serial number (SN) of the TOP HALF of the sensor (if a BD3C-5, there is only one serial number)
83 +* 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)
59 59  
60 -== **2. Node Placement** ==
85 +[[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!
86 +
87 +== 2. Node Placement ==
61 61  )))
62 62  
63 63  **Protection**: Place nodes inside (landfill) biodegradable bags to minimize cleaning and cross-site soil contamination.
... ... @@ -65,15 +65,15 @@
65 65  **Site Analysis**:
66 66  
67 67  * **Take compass measurements away from the sensor as it will affect your measurement.**
68 -* Take multiple photographs from various angles to document the site setup thoroughly.
69 -* 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)
95 +* Take photographs from various angles to document the site setup thoroughly.
96 +* Include a detailed site description in your notes
70 70  
71 -== **3. GPS Considerations** ==
98 +== 3. GPS Considerations ==
72 72  
73 73  (% class="wikigeneratedid" %)
74 74  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.
75 75  
76 -== **4. Visibility and Location Marking** ==
103 +== 4. Visibility and Location Marking ==
77 77  
78 78  **Flag Placement**: Position a flag, preferably in a bright color (avoid green or yellow), near the instrument to aid in its future location.
79 79  
... ... @@ -82,7 +82,7 @@
82 82  * Use a GPS device to mark the instrument's exact location.
83 83  * Record this location in both your paper notes and the GPS device.
84 84  
85 -== (% style="color:inherit; font-family:inherit; font-size:max(18px, min(20px, 14.4444px + 0.462963vw))" %)**5. Charge Time, Pre-Deployment & Post-Deployment**(%%) ==
112 +== (% style="color:inherit; font-family:inherit; font-size:max(18px, min(20px, 14.4444px + 0.462963vw))" %)5. Charge Time, Pre-Deployment & Post-Deployment(%%) ==
86 86  
87 87  * **Charging Duration**: Both types of nodes take approximately 6-8 hours to fully charge from a flat state.
88 88  * **Pre-Deployment Charging**:
... ... @@ -96,10 +96,10 @@
96 96  * **Storage and Shipping Charge Level**:
97 97  ** Maintain a battery charge level of around 50-60% (e.g. "orange") for both storage and shipping purposes.
98 98  ** This charge level is recommended to prevent battery damage and is safe for transportation.
99 -** Nodes should not be stored fully charged, and it **they should especially not be stored with 0 charge.**
126 +** Nodes should not be stored fully charged, and **they should especially not be stored with 0 charge as this damages lithium batteries.**
100 100  
101 101  (((
102 -== **6. Data Sharing and Metadata Creation** ==
129 +== 6. Data Sharing and Metadata Creation ==
103 103  )))
104 104  
105 105  **GPS Data**:
... ... @@ -112,9 +112,9 @@
112 112  
113 113  **Metadata File**:
114 114  
115 -* Create and organize metadata according to the [[ANU metadata standard txt file>>attach:example_metadata.txt]].
142 +* 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.
116 116  
117 -== **7. Additional Best Practices** ==
144 +== 7. Additional Best Practices ==
118 118  
119 119  * **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.
120 120  
... ... @@ -169,25 +169,25 @@
169 169  = **Charging Procedure for Seismic Nodes** =
170 170  
171 171  (((
172 -== **1. Preparation for Charging**: ==
199 +== 1. Preparation for Charging: ==
173 173  
174 174  * 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.
175 175  )))
176 176  
177 177  (((
178 -== **2. Disassembling the Node**: ==
205 +== 2. Disassembling the Node: ==
179 179  
180 180  * For the IGU-16HR, remove the battery (bottom half) from the sensor. This is done by unscrewing the spikes counter-clockwise.
181 181  )))
182 182  
183 183  (((
184 -== **3. Setting Nodes in the Charging Box**: ==
211 +== 3. Setting Nodes in the Charging Box: ==
185 185  
186 186  * Place 1-16 IGU-16HR battery components upside-down into the charger, assuring they are oriented properly.
187 187  )))
188 188  
189 189  (((
190 -== **4. Monitoring the Charging Process**: ==
217 +== 4. Monitoring the Charging Process: ==
191 191  
192 192  * 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.
193 193  * 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.
... ... @@ -194,7 +194,7 @@
194 194  )))
195 195  
196 196  (((
197 -== **5. Updating Charge Status**: ==
224 +== 5. Updating Charge Status: ==
198 198  
199 199  * 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.
200 200  * This step is crucial for tracking the charging status of multiple units, especially when handling a large number of nodes.
... ... @@ -205,14 +205,29 @@
205 205  
206 206  
207 207  
208 -[[image:1706153354750-415.png||data-xwiki-image-style-alignment="center" height="317" width="562"]]
235 +{{{
236 + }}}
209 209  
210 210  ----
211 211  
212 212  = **Downloading and Converting Seismic Data to MiniSeed Format** =
213 213  
214 -== **Node Registration and Software Setup** ==
242 +(% class="wikigeneratedid" %)
243 +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]]
215 215  
245 +== Connection tips: ==
246 +
247 +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:
248 +
249 +* Place the node on the harvester gently, then firmly press it down onto the pins.
250 +* 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.
251 +* 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.
252 +* 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!
253 +
254 +
255 +
256 +== Node Registration and Software Setup ==
257 +
216 216  1. (((
217 217  **Registering Nodes in the System**:
218 218  
... ... @@ -229,8 +229,29 @@
229 229  * Ignore the settings for seismic recordings in the subsequent window. Resetting instruments (e.g., sampling rate, gain) requires reprogramming via script.
230 230  )))
231 231  
232 -== **Data Downloading Process** ==
274 +== File structure ==
233 233  
276 +There are essentially three main folders where relevant PROSPECT and PROJECT DATA is stored. Individual projects will be found as subfolders in these.
277 +
278 +=== SOLOLITE ===
279 +
280 +This folder stores SoloLite config files and parameters. Nothing too important stored here, you can always start over and re-create this.
281 +
282 +=== DCCDATA ===
283 +
284 +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.
285 +
286 +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)//
287 +
288 +Then in the SoloLite software, go to tools > Reanalyze Seismic Data
289 +
290 +=== SOLODATA ===
291 +
292 +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.
293 +
294 +
295 +== Data Downloading Process ==
296 +
234 234  1. (((
235 235  **Initiating Data Download**:
236 236  
... ... @@ -247,14 +247,46 @@
247 247  * Click “prepare” followed by “run” to start reformatting. Monitor this process in the small panel at the bottom left.
248 248  * (% class="box warningmessage" %)
249 249  (((
250 -* **Ensure to export data as "COUNTS", not "mV".**
313 +* **Ensure to export data as "COUNTS" (int32), not "mV" (float). This is critical!**
251 251  
252 -* **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).**
315 +* **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.**
253 253  )))
254 254  )))
255 255  
256 -== **Handling Nodes During Download** ==
319 +== Smart Solo Z Polarity bug (SP nodes ONLY!) ==
257 257  
321 +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.**
322 +
323 +== 18 Leap Second bug ==
324 +
325 +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.
326 +
327 +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.
328 +
329 +{{code language="none"}}
330 +<?xml version="1.0" encoding="UTF-8"?>
331 +<config>
332 + <leapsecond>
333 + <interval>
334 + <start_time>2017-01-01#00:00:00</start_time>
335 + <end_time>2999-12-31#23:59:59</end_time>
336 + <second>18</second>
337 + </interval>
338 + <interval>
339 + <start_time>1970-01-01#00:00:00</start_time>
340 + <end_time>2017-01-01#00:00:00</end_time>
341 + <second>17</second>
342 + </interval>
343 + </leapsecond>
344 + <GPS_distance_threshold_degree>
345 + 4e-5
346 + </GPS_distance_threshold_degree>
347 +</config>
348 +{{/code}}
349 +
350 +
351 +== Handling Nodes During Download ==
352 +
258 258  1. (((
259 259  **Monitoring Download Indicators**:
260 260  
... ... @@ -270,6 +270,7 @@
270 270  * **Use fast external hard drives to avoid limitations in data harvesting.**
271 271  
272 272  * **Recommended specifications: USB-C, USB 3.0, and 4+ Tb of space.**
368 +* **The USB type for the harvester is TYPE-A, the typical normal rectangular shape.**
273 273  )))
274 274  )))
275 275  1. (((
... ... @@ -309,7 +309,7 @@
309 309  
310 310  = **Cleaning** =
311 311  
312 -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.
408 +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.
313 313  
314 314  = **Weights (for shipping)** =
315 315  
... ... @@ -347,7 +347,7 @@
347 347  
348 348  |(% style="width:189px" %)**Frequency Band**|(% style="width:221px" %)5 Seconds to 150Hz
349 349  |(% style="width:189px" %)**Sensitivity**|(% style="width:221px" %)200 V/m/s
350 -|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)158 x160mm
446 +|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)Φ158 x160mm(H)
351 351  |(% style="width:189px" %)**Weight**|(% style="width:221px" %)2.8 kg
352 352  |(% style="width:189px" %)**Data Storage**|(% style="width:221px" %)64 Gb
353 353  |(% style="width:189px" %)**Battery**|(% style="width:221px" %)(((
... ... @@ -359,7 +359,7 @@
359 359  
360 360  (% class="box" %)
361 361  (((
362 -= SmartSolo [[IGU-16HR>>url:https://smartsolo.com/cp-3.html]] =
458 += SmartSolo [[IGU-16HR>>url:https://smartsolo.com/cp-3.html]]3C =
363 363  
364 364  [[image:smartsolo node.jpg]]
365 365  
... ... @@ -366,8 +366,8 @@
366 366  [[image:smartsolo node 2.jpg]]
367 367  
368 368  |(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 1652Hz
369 -|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)67.7 V/m/s
370 -|(% style="width:187px" %)**Size (with spike)**|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm
465 +|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)76.7 V/m/s
466 +|(% style="width:187px" %)**Size (with spike)**|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm(H)
371 371  |(% style="width:187px" %)**Weight**|(% style="width:224px" %)2.4 kg
372 372  |(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)64 Gb
373 373  |(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((
... ... @@ -377,6 +377,99 @@
377 377  )))
378 378  )))
379 379  
476 +(% class="box" %)
477 +(((
380 380  
479 +
480 += SmartSolo [[IGU-16>>url:https://smartsolo.com/cp-3.html]]1C =
481 +
482 +
483 +[[image:Screenshot 2025-08-01 161027.png]]
484 +
485 +|(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 413Hz
486 +|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)80 V/m/s
487 +|(% style="width:187px" %)**Size (without spike)**|(% style="width:224px" %)95mm(L) × 103mm(W) × 118mm(H)
488 +|(% style="width:187px" %)**Weight**|(% style="width:224px" %)1.1 kg
489 +|(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)8 Gb
490 +|(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((
491 +Lithium-ion battery contained in equipment (38.48 Wh)
492 +
493 +UN3481 PI967 S2
381 381  )))
382 382  )))
496 +
497 +(% class="box" %)
498 +(((
499 += SmartSolo BD3C-16 Portable Battery Charger =
500 +
501 +[[image:20250729_125049.jpg]]
502 +
503 +|**Dimensions (LxHxW)**|558 x 357 x 300mm
504 +|**Input rating**|100-210V - 50/60Hz
505 +|**Power**|1000W
506 +|**Weight**|14.5kg
507 +|**Weight with cables**|21kg
508 +)))
509 +
510 +(% class="box" id="HSmartSoloBD3C-16PortableBatteryCharger" %)
511 +(((
512 += SmartSolo IGU-16 Portable Data Harvester =
513 +
514 +[[image:20250729_124747.jpg]]
515 +
516 +|**Dimensions (LxHxW)**|625 x 500 x 366mm
517 +|**Input rating**|100-210V - 50/60Hz
518 +|**Power**|100W
519 +|**Weight**|21.5 - 24kg
520 +|**Slots no.**|16
521 +|**Download Speed**|20MB/sec/slot
522 +)))
523 +
524 +(% class="box" %)
525 +(((
526 += SmartSolo IGU-16 Portable Battery Charger =
527 +
528 +[[image:20250729_124644.jpg]]
529 +
530 +|**Dimensions (LxHxW)**|625 x 500 x 366mm
531 +|**Input rating**|100-210V - 50/60Hz
532 +|**Power**|640W
533 +|**Weight**|26.3kg
534 +|**Slots no.**|16
535 +)))
536 +
537 +(% class="box" %)
538 +(((
539 += SmartSolo BD3C-5 Carry Case =
540 +
541 +[[image:20250729_124957.jpg]]
542 +
543 +
544 +|**Dimensions (LxHxW)**|590 x 225 x 405mm
545 +|**Weight**|8.2kg
546 +|**Slots no.**|6
547 +)))
548 +
549 +(% class="box" %)
550 +(((
551 += SmartSolo IGU-16 3C Carry Bag =
552 +
553 +[[image:20250729_124502.jpg]]
554 +
555 +|**Dimensions (LxHxW)**|230 x 340 x 310mm
556 +|**Weight**|3.6kg
557 +|**Slots no.**|6
558 +)))
559 +
560 +(% class="box" %)
561 +(((
562 += SmartSolo IGU-16 1C Carry Bag =
563 +
564 +[[image:20250729_124558.jpg]]
565 +
566 +|**Dimensions (LxHxW)**|225 x 200 x 550mm
567 +|**Weight**|
568 +|**Slots no.**|6
569 +)))
570 +)))
571 +)))
20250729_124502.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.JackD
Size
... ... @@ -1,0 +1,1 @@
1 +318.3 KB
Content
20250729_124558.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.JackD
Size
... ... @@ -1,0 +1,1 @@
1 +376.8 KB
Content
20250729_124644.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.JackD
Size
... ... @@ -1,0 +1,1 @@
1 +528.0 KB
Content
20250729_124747.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.JackD
Size
... ... @@ -1,0 +1,1 @@
1 +488.5 KB
Content
20250729_124957.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.JackD
Size
... ... @@ -1,0 +1,1 @@
1 +532.5 KB
Content
20250729_125049.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.JackD
Size
... ... @@ -1,0 +1,1 @@
1 +457.6 KB
Content
BB_programming.labels.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.robert
Size
... ... @@ -1,0 +1,1 @@
1 +111.5 KB
Content
SP_programming.labels.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.robert
Size
... ... @@ -1,0 +1,1 @@
1 +106.7 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