Skip to Content
Last modified by robert on 2026/08/12 13:08
From version 119.1
edited by robert
on 2026/08/12 13:08
Change comment: There is no comment for this version
To version 91.1
edited by KB
on 2025/12/04 12:33
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.robert
1 +XWiki.KB
Content
... ... @@ -6,14 +6,12 @@
6 6  
7 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, '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)**
11 +* **SmartSolo IGU 16 1C (5 Hz Short Period, single channel)**
12 12  
13 -Visit the [[SmartSolo page>>https://smartsolo.com/igu.html]] for more detail.
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.
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 17  (% class="box infomessage" %)
18 18  (((
19 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.
... ... @@ -23,13 +23,12 @@
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.
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.
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"]]
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"]]
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!"]]
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"]]
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 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.
... ... @@ -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.
44 +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).
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).
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,22 +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.
69 +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 -= External Power =
77 -
78 -Both the 5Hz IGU-16HR and 5s BD3C-5 can be optionally powered via external battery via either a replacement bottom half (the 5Hz nodes) or a battery cable accessory (BD3C-5) using standard lead acid batteries from 9-36v. We have done preliminary testing at 250 Hz with a 12v battery:
79 -
80 -- BD3C-5: ~~2 days of recording per 1 Ah
81 -
82 -- IGU16-HR 3C:  ~~3.5 days of recording per 1 Ah
83 -
84 -- IGU16-HR 1C: ~~7 days of recording per 1 Ah
85 -
86 -Of course, these can also be fit with a solar panel & charge controller which would then theoretically keep them going indefinitely (limited only by the disk storage, which at 250 Hz could be on the order of 12 months).
87 -
88 88  = **Installation** =
89 89  
90 90  (% class="box infomessage" %)
... ... @@ -106,64 +106,54 @@
106 106  
107 107  [[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!
108 108  
109 -== 2. Burial ==
110 -
111 -**ALL nodes should be buried flush with the ground, no exceptions**. If the node is sticking up the data data quality will be significantly reduced (especially the horizontal channels, see [[below>>https://auspass.edu.au/xwiki/bin/view/Instrumentation/SmartSolo%20Nodes/#HIGU-16Horizontalnoise26howtoavoid]]). It also catches wind, makes them more visible, etc. But mostly it makes the data bad.
112 -
113 -//Don't be lazy. Do it right. //
114 -
115 -[[An example of what not to do.>>image:1786503344572-296.jpg||data-xwiki-image-style-alignment="center" height="341" width="404"]]
116 -
117 -[[North channel PSD of the sensor in the picture above (it is not good)>>image:1786503812585-338.02.28 PM.png||data-xwiki-image-style-alignment="center" height="244" width="451"]]
118 -
119 -== 3. Node Placement ==
92 +== 2. Node Placement ==
120 120  )))
121 121  
95 +**Protection**: Place nodes inside (landfill) biodegradable bags to minimize cleaning and cross-site soil contamination.
96 +
122 122  **Site Analysis**:
123 123  
124 -* **Take compass measurements away from the sensor as it will affect your measurement. Use a stick or shovel to help align.**
125 -* Take photographs from various angles to document the site setup thoroughly. Have a colleague stand next to it pointing at it.
126 -* Include a detailed site description in your notes.
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
127 127  
128 -== 4. GPS Considerations ==
103 +== 3. GPS Considerations ==
129 129  
130 130  (% class="wikigeneratedid" %)
131 -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 (2 cm?) 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.
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.
132 132  
133 -== 5. Visibility and Location Marking ==
108 +== 4. Visibility and Location Marking ==
134 134  
135 135  **Flag Placement**: Position a flag, preferably in a bright color (avoid green or yellow), near the instrument to aid in its future location.
136 136  
137 137  **GPS Marking**:
138 138  
139 -* Use a GPS device to mark the instrument's exact location. Most modern cell phones can get to about a 3m error with their internal GPS also; you can probably also get away with investing a few dollars in a good app that shows error and lets you log markers.
140 -* Also write the GPS down on paper (ie your [[LOG SHEET>>http://auspass.edu.au/field/NODES_blank_fieldlog.pdf]]).
114 +* Use a GPS device to mark the instrument's exact location.
115 +* Record this location in both your paper notes and the GPS device.
141 141  
142 -== (% style="color:inherit; font-family:inherit; font-size:max(18px, min(20px, 14.4444px + 0.462963vw))" %)6. Charge Time, Pre-Deployment & Post-Deployment(%%) ==
117 +== (% style="color:inherit; font-family:inherit; font-size:max(18px, min(20px, 14.4444px + 0.462963vw))" %)5. Charge Time, Pre-Deployment & Post-Deployment(%%) ==
143 143  
144 144  * **Charging Duration**: Both types of nodes take approximately 6-8 hours to fully charge from a flat state.
145 145  * **Pre-Deployment Charging**:
146 146  ** Although the nodes hold their charge well, it's beneficial to give them a "top up" charge before deployment.
122 +
147 147  * **Operational Duration**:
148 148  ** 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.
149 149  
150 150  * **Post-Retrieval Charging**:
151 -** After retrieval, charge the instruments to about 50-60% (indicated by ORANGE LED) unless they are to be immediately re-deployed or transported.
152 -* **State of Charge (SoC) for Storage**:
153 -** Maintain a battery charge level of around 50-60% (i.e., ORANGE) for storage.
154 -** This charge level is recommended to prevent battery damage, and should be checked every six months.
155 -** Nodes should //__not be stored at full-charge (GREEN), or 0-charge (RED).__//
156 -** Storage at 0-charge damages lithium batteries**.**
157 -* **SoC for Transport:**
158 -** Charge levels for transport will be advised by the freighter. The required SoC will depend on volume and transport method (air, land, sea).
127 +** After retrieval, charge the instruments to about 50-60% (indicated as "orange" level) unless they are to be immediately re-deployed.
128 +* **Storage and Shipping Charge Level**:
129 +** Maintain a battery charge level of around 50-60% (e.g. "orange") for both storage and shipping purposes.
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.**
159 159  
160 160  (((
161 -== 7. Data Sharing and Metadata Creation ==
134 +== 6. Data Sharing and Metadata Creation ==
162 162  )))
163 163  
164 164  **GPS Data**:
165 165  
166 -* Ensure you have __carefully documented__ precise lat/lon locations for each station.
139 +* Ensure you have documented precise lat/lon locations for each station and **DOCUMENTED THIS CAREFULLY**
167 167  
168 168  **Photo Sharing**:
169 169  
... ... @@ -173,7 +173,7 @@
173 173  
174 174  * 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.
175 175  
176 -== 8. Additional Best Practices ==
149 +== 7. Additional Best Practices ==
177 177  
178 178  * **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.
179 179  
... ... @@ -236,22 +236,20 @@
236 236  (((
237 237  == 2. Disassembling the Node: ==
238 238  
239 -* For the IGU-16HR, remove the battery section (bottom half) from the sensor by unscrewing the spike section counter-clockwise.
212 +* For the IGU-16HR, remove the battery (bottom half) from the sensor. This is done by unscrewing the spikes counter-clockwise.
240 240  )))
241 241  
242 242  (((
243 243  == 3. Setting Nodes in the Charging Box: ==
244 244  
245 -* Connect to a safe indoor power supply, and turn on (red rocker switch).
246 -* Charging will begin automatically when nodes are inserted in the charging rack.
247 -* Place IGU-16HR battery sections upside-down in the rack, oriented with the terminal connectors.
218 +* Place 1-16 IGU-16HR battery components upside-down into the charger, assuring they are oriented properly.
248 248  )))
249 249  
250 250  (((
251 251  == 4. Monitoring the Charging Process: ==
252 252  
253 -* Lights adjacent to the batteries will illuminate, indicating that charging is underway.
254 -* 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.
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 +* 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.
255 255  )))
256 256  
257 257  (((
... ... @@ -333,7 +333,7 @@
333 333  
334 334  * Once a new project is created, the Data Transfer View panel will display connected nodes with details like series number and data size.
335 335  * If “Prospect not matched” appears, it simply means the new project doesn’t match the original programming project. This is not a concern.
336 -* Select all nodes and right-click to “force download”. This starts the download process.[[image:Smartsolo harvesting #4 copy.png]]
307 +* Select all nodes and right-click to “force download”. This starts the download process.
337 337  * Completed downloads will appear as new folders in the Downloaded Data panel.
338 338  )))
339 339  1. (((
... ... @@ -340,28 +340,23 @@
340 340  **Exporting Data in Readable Format**:
341 341  
342 342  * Go to the “Tool” menu and select “export seismic data”.
343 -* Tailor other parameters to project preference and ensure "Sample Interval" matches the setting used during node reset (note: the standard used by ANU is 4ms, or 250hz)
314 +* Tailor other parameters to personal preference and ensure "Sample Interval" matches the setting used during node reset.
315 +* Click “prepare” followed by “run” to start reformatting. Monitor this process in the small panel at the bottom left.
344 344  * (% class="box warningmessage" %)
345 345  (((
346 -**Ensure export data is set to "COUNTS" (int32), not "mV" (float). This is critical!**
318 +* **Ensure to export data as "COUNTS" (int32), not "mV" (float). This is critical!**
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.**
347 347  )))
348 -* 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.
349 -* Set "Remove DC" to "Yes" to centre the data around the zero value
350 -* Set the correct Start Time (UTC) and End Time (UTC) of the project to prevent the unnecessary export of older data
351 -* [[image:Smartsolo harvesting #9 copy.png]]
352 -* Click “prepare” followed by “run” to start reformatting. Monitor this process in the small panel at the bottom left.
353 -* The data will be exported to the SOLODATA folder. For a windows system, the following file explorer page is where you must navigate to to locate your project folder[[image:Smartsolo harvesting #8 copy.png]]
354 354  )))
355 355  
356 -== Smart Solo IGU-16HR Polarity Notice ==
324 +== Smart Solo Z Polarity bug (SP nodes ONLY!) ==
357 357  
358 -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.
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.**
359 359  
360 -**The BD3C-5 data does not require any sort of polarity inversion.**
361 -
362 362  == 18 Leap Second bug ==
363 363  
364 -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.
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.
365 365  
366 366  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.
367 367  
... ... @@ -417,8 +417,11 @@
417 417  **Finalizing the Download**:
418 418  
419 419  * After downloading, mark the //"D"// box on your temporary labels to indicate completion.
386 +
387 +
420 420  )))
421 421  
390 +[[image:1706153266647-145.png||data-xwiki-image-style-alignment="center" height="340" width="603"]]
422 422  
423 423  
424 424  
... ... @@ -439,78 +439,23 @@
439 439  
440 440  ----
441 441  
442 -= Instrument Response =
443 -
444 -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]]
445 -
446 -== IGU 16HR-3C ==
447 -
448 - '16HR3C': {'poles':[(-22.211059+22.217768j), (-22.211059-22.217768j)],
449 - 'zeros':[0j, 0j],
450 - 'gain':1,
451 - 'sensitivity': 257019225.55108312}
452 -
453 -[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:16HR_Z_huddle.png||alt="IGU16_Z_huddle.png"]]
454 -
455 -[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz bandpass filter>>image:16HR_N_huddle.png||alt="IGU16_N_huddle.png"]]
456 -
457 -== IGU 16-1C ==
458 -
459 -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.
460 -
461 -[[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:16HR1C_Z_huddle.png||alt="IGU16_1C_Z_huddle.png"]]
462 -
463 -== BD3C-5 ==
464 -
465 - 'BD3C': {'poles':[(-1720.4+0j), (-1.2+0.9j), (-1.2-0.9j)],
466 - 'zeros':[(14164+0j), (-7162+0j), 0j, 0j],
467 - 'gain':1.69726e-05,
468 - 'sensitivity': 702651512.6046528}
469 -
470 -Above 0.5 Hz, the BD3C-5 response fits well:
471 -
472 -[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:BD3C_Z_huddle.0.5.png]]
473 -
474 -[[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]]
475 -
476 -(% class="wikigeneratedid" %)
477 -Below the corner frequency (0.2 Hz) the phase response still fares well, but amplitude response may need to be dialed in a bit (it seems a bit high). We are working to try to calibrate this a bit better. In the next two figures the filter is **0.1** to 5 Hz:
478 -
479 -
480 -[[BD3C **0.1 **to 5 Hz bandpass filter>>image:BD3C_Z_huddle.0.1.png]]
481 -
482 -[[BD3C **0.1** to 5 Hz bandpass filter>>image:BD3C_N_huddle.0.1.png]]
483 -
484 -== IGU-16 Horizontal noise & how to avoid ==
485 -
486 -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.
487 -
488 -[[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]]
489 -
490 -(% class="wikigeneratedid" %)
491 -The BD3C-5 nodes do not have this issue:
492 -
493 -[[BD3C-5 test, as above. There is no additional noise on the horizontal channels.>>image:BD3C_psd.png]]
494 -
495 495  = **Cleaning** =
496 496  
497 -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.
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.
498 498  
499 499  = **Weights (for shipping)** =
500 500  
501 501  The weights of bags of nodes, as well as data harvesters and node chargers, are listed below:
502 502  
503 -1 bag + 6*IGU-16HR nodes: 18 kg
419 +1 bag + 6 SP (IGU-16HR) nodes: 18 kg
504 504  
505 -1*IGU-16HR data harvester: 21.5 kg
421 +1 SP (IGU-16HR) data harvester: 21.5 kg
506 506  
507 -1*IGU-16HR charger: 26.3 kg
423 +1 SP (IGU-16HR) charger: 26.3 kg
508 508  
509 -1*BD3C-5 charger (with and without 16 cables): 21 kg / 14.5 kg
425 +1 BB (BD3C-5) charger/data harvester (with and without 16 cables): 21 kg / 14.5 kg
510 510  
511 -1 case + 5*BD3C-5 nodes: 22 kg (aggregate battery weight <5kg, 168Wh)
512 -
513 -1 case + 6*BD3C-5 nodes: 25 kg (aggregate battery weight >5kg, 168Wh)
427 +1 case + 5 BB (BD3C-5) nodes and 6 BB nodes: 22 kg / 25 kg
514 514  )))
515 515  
516 516  (% class="col-xs-12 col-sm-4" %)
... ... @@ -594,8 +594,8 @@
594 594  |**Dimensions (LxHxW)**|558 x 357 x 300mm
595 595  |**Input rating**|100-210V - 50/60Hz
596 596  |**Power**|1000W
597 -|**Weight**|14.5 kg
598 -|**Weight with cables**|21 kg
511 +|**Weight**|14.5kg
512 +|**Weight with cables**|21kg
599 599  )))
600 600  
601 601  (% class="box" id="HSmartSoloBD3C-16PortableBatteryCharger" %)
... ... @@ -607,8 +607,8 @@
607 607  |**Dimensions (LxHxW)**|625 x 500 x 366mm
608 608  |**Input rating**|100-210V - 50/60Hz
609 609  |**Power**|100W
610 -|**Weight**|21.5 - 24 kg
611 -|**Capacity**|16 nodes
524 +|**Weight**|21.5 - 24kg
525 +|**Slots no.**|16
612 612  |**Download Speed**|20MB/sec/slot
613 613  )))
614 614  
... ... @@ -618,11 +618,11 @@
618 618  
619 619  [[image:20250729_124644.jpg]]
620 620  
621 -|**Dimensions (LxHxW)**|625 x 500 x 366 mm
622 -|**Input rating**|100-210V - 50/60 Hz
623 -|**Power**|640 W
624 -|**Weight**|26.3 kg
625 -|**Capacity**|16 nodes
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
626 626  )))
627 627  
628 628  (% class="box" %)
... ... @@ -632,9 +632,9 @@
632 632  [[image:20250729_124957.jpg]]
633 633  
634 634  
635 -|**Dimensions (LxHxW)**|590 x 225 x 405 mm
636 -|**Weight**|8.2 kg
637 -|**Capacity**|6 nodes
549 +|**Dimensions (LxHxW)**|590 x 225 x 405mm
550 +|**Weight**|8.2kg
551 +|**Slots no.**|6
638 638  )))
639 639  
640 640  (% class="box" %)
... ... @@ -644,13 +644,9 @@
644 644  [[image:20250729_124502.jpg]]
645 645  
646 646  |**Dimensions (LxHxW)**|230 x 340 x 310mm
647 -|**Weight**|(((
648 -3.6kg (empty)
649 -
650 -18.0kg (full)
561 +|**Weight**|3.6kg
562 +|**Slots no.**|6
651 651  )))
652 -|**Capacity**|6 nodes
653 -)))
654 654  
655 655  (% class="box" %)
656 656  (((
... ... @@ -660,7 +660,7 @@
660 660  
661 661  |**Dimensions (LxHxW)**|225 x 200 x 550mm
662 662  |**Weight**|
663 -|**Capacity**|8 nodes
573 +|**Slots no.**|6
664 664  )))
665 665  )))
666 666  )))
16HR1C_Z_huddle.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -92.1 KB
Content
16HR_N_huddle.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -88.4 KB
Content
16HR_Z_huddle.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -80.8 KB
Content
1786503344572-296.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -1.4 MB
Content
1786503808210-822.02.28 PM.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -437.8 KB
Content
1786503812585-338.02.28 PM.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -437.8 KB
Content
5Hz_node_programming.labels.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.KB
Size
... ... @@ -1,1 +1,0 @@
1 -109.8 KB
Content
5S_node_programming.labels.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.KB
Size
... ... @@ -1,1 +1,0 @@
1 -114.2 KB
Content
BD3C_N_huddle.0.1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -65.9 KB
Content
BD3C_N_huddle.0.5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -68.4 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 -64.3 KB
Content
BD3C_Z_huddle.0.5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -52.5 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
Smartsolo harvesting #4 copy.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -33.8 KB
Content
Smartsolo harvesting #4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -33.8 KB
Content
Smartsolo harvesting #6 copy.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -33.6 KB
Content
Smartsolo harvesting #8 copy.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -38.3 KB
Content
Smartsolo harvesting #8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -60.0 KB
Content
Smartsolo harvesting #9 copy.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -28.7 KB
Content
XWiki.XWikiComments[0]
Date
... ... @@ -1,1 +1,0 @@
1 -2026-07-09 10:45:51.967
Author
... ... @@ -1,1 +1,0 @@
1 -Mark Goldman
Comment
... ... @@ -1,1 +1,0 @@
1 -I can verify that the default orientation for the SmartSolo 3C nodes is positive values for case motion to the South, West, and downwards. We have co-located nodes with permanent stations and noticed this correlation when comparing waveforms.