Skip to Content
Last modified by robert on 2026/08/12 13:08
From version 118.1
edited by robert
on 2026/08/12 13:06
Change comment: There is no comment for this version
To version 94.2
edited by KB
on 2026/01/19 11:58
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,12 +6,10 @@
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 'Very' Short Period)**
10 +* **SmartSolo BD3C-5 (5 Second Short Period)**
11 +* **SmartSolo IGU 16 1C (5 Hz 'Very' Short Period, single channel)**
12 12  
13 -Visit the [[SmartSolo page>>https://smartsolo.com/igu.html]] for more detail.
14 -
15 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 16  
17 17  (% class="box infomessage" %)
... ... @@ -25,11 +25,10 @@
25 25  
26 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.
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:5Hz_node_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,62 +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. //Don't be lazy. Do it right. //
112 -
113 -[[An example of what not to do.>>image:1786503344572-296.jpg||data-xwiki-image-style-alignment="center" height="341" width="404"]]
114 -
115 -[[North channel PSD of the sensor in the picture above (not good)>>image:1786503812585-338.02.28 PM.png||data-xwiki-image-style-alignment="center" height="244" width="451"]]
116 -
117 -== 3. Node Placement ==
92 +== 2. Node Placement ==
118 118  )))
119 119  
95 +**Protection**: Place nodes inside (landfill) biodegradable bags to minimize cleaning and cross-site soil contamination.
96 +
120 120  **Site Analysis**:
121 121  
122 -* **Take compass measurements away from the sensor as it will affect your measurement. Use a stick or shovel to help align.**
123 -* Take photographs from various angles to document the site setup thoroughly. Have a colleague stand next to it pointing at it.
124 -* 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
125 125  
126 -== 4. GPS Considerations ==
103 +== 3. GPS Considerations ==
127 127  
128 128  (% class="wikigeneratedid" %)
129 -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.
130 130  
131 -== 5. Visibility and Location Marking ==
108 +== 4. Visibility and Location Marking ==
132 132  
133 133  **Flag Placement**: Position a flag, preferably in a bright color (avoid green or yellow), near the instrument to aid in its future location.
134 134  
135 135  **GPS Marking**:
136 136  
137 -* 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.
138 -* 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.
139 139  
140 -== (% 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(%%) ==
141 141  
142 142  * **Charging Duration**: Both types of nodes take approximately 6-8 hours to fully charge from a flat state.
143 143  * **Pre-Deployment Charging**:
144 144  ** Although the nodes hold their charge well, it's beneficial to give them a "top up" charge before deployment.
122 +
145 145  * **Operational Duration**:
146 146  ** 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.
147 147  
148 148  * **Post-Retrieval Charging**:
149 -** After retrieval, charge the instruments to about 50-60% (indicated by ORANGE LED) unless they are to be immediately re-deployed or transported.
150 -* **State of Charge (SoC) for Storage**:
151 -** Maintain a battery charge level of around 50-60% (i.e., ORANGE) for storage.
152 -** This charge level is recommended to prevent battery damage, and should be checked every six months.
153 -** Nodes should //__not be stored at full-charge (GREEN), or 0-charge (RED).__//
154 -** Storage at 0-charge damages lithium batteries**.**
155 -* **SoC for Transport:**
156 -** 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.**
157 157  
158 158  (((
159 -== 7. Data Sharing and Metadata Creation ==
134 +== 6. Data Sharing and Metadata Creation ==
160 160  )))
161 161  
162 162  **GPS Data**:
163 163  
164 -* 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**
165 165  
166 166  **Photo Sharing**:
167 167  
... ... @@ -171,7 +171,7 @@
171 171  
172 172  * 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.
173 173  
174 -== 8. Additional Best Practices ==
149 +== 7. Additional Best Practices ==
175 175  
176 176  * **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.
177 177  
... ... @@ -234,22 +234,20 @@
234 234  (((
235 235  == 2. Disassembling the Node: ==
236 236  
237 -* 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.
238 238  )))
239 239  
240 240  (((
241 241  == 3. Setting Nodes in the Charging Box: ==
242 242  
243 -* Connect to a safe indoor power supply, and turn on (red rocker switch).
244 -* Charging will begin automatically when nodes are inserted in the charging rack.
245 -* 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.
246 246  )))
247 247  
248 248  (((
249 249  == 4. Monitoring the Charging Process: ==
250 250  
251 -* Lights adjacent to the batteries will illuminate, indicating that charging is underway.
252 -* 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.
253 253  )))
254 254  
255 255  (((
... ... @@ -331,7 +331,7 @@
331 331  
332 332  * Once a new project is created, the Data Transfer View panel will display connected nodes with details like series number and data size.
333 333  * If “Prospect not matched” appears, it simply means the new project doesn’t match the original programming project. This is not a concern.
334 -* 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.
335 335  * Completed downloads will appear as new folders in the Downloaded Data panel.
336 336  )))
337 337  1. (((
... ... @@ -338,24 +338,21 @@
338 338  **Exporting Data in Readable Format**:
339 339  
340 340  * Go to the “Tool” menu and select “export seismic data”.
341 -* 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.
342 342  * (% class="box warningmessage" %)
343 343  (((
344 -**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.**
345 345  )))
346 -* 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 -* Set "Remove DC" to "Yes" to centre the data around the zero value
348 -* Set the correct Start Time (UTC) and End Time (UTC) of the project to prevent the unnecessary export of older data
349 -* [[image:Smartsolo harvesting #9 copy.png]]
350 -* Click “prepare” followed by “run” to start reformatting. Monitor this process in the small panel at the bottom left.
351 -* 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]]
352 352  )))
353 353  
354 354  == Smart Solo IGU-16HR Polarity Notice ==
355 355  
356 -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 channel data manually rather than in the SoloLite software or inverting the response metadata.
357 357  
358 -**The BD3C-5 data does not require any sort of polarity inversion.**
328 +**The BD3C-5 data does not require a polarity inversion.**
359 359  
360 360  == 18 Leap Second bug ==
361 361  
... ... @@ -415,8 +415,11 @@
415 415  **Finalizing the Download**:
416 416  
417 417  * After downloading, mark the //"D"// box on your temporary labels to indicate completion.
388 +
389 +
418 418  )))
419 419  
392 +[[image:1706153266647-145.png||data-xwiki-image-style-alignment="center" height="340" width="603"]]
420 420  
421 421  
422 422  
... ... @@ -437,78 +437,23 @@
437 437  
438 438  ----
439 439  
440 -= Instrument Response =
441 -
442 -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]]
443 -
444 -== IGU 16HR-3C ==
445 -
446 - '16HR3C': {'poles':[(-22.211059+22.217768j), (-22.211059-22.217768j)],
447 - 'zeros':[0j, 0j],
448 - 'gain':1,
449 - 'sensitivity': 257019225.55108312}
450 -
451 -[[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"]]
452 -
453 -[[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"]]
454 -
455 -== IGU 16-1C ==
456 -
457 -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.
458 -
459 -[[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"]]
460 -
461 -== BD3C-5 ==
462 -
463 - 'BD3C': {'poles':[(-1720.4+0j), (-1.2+0.9j), (-1.2-0.9j)],
464 - 'zeros':[(14164+0j), (-7162+0j), 0j, 0j],
465 - 'gain':1.69726e-05,
466 - 'sensitivity': 702651512.6046528}
467 -
468 -Above 0.5 Hz, the BD3C-5 response fits well:
469 -
470 -[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:BD3C_Z_huddle.0.5.png]]
471 -
472 -[[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]]
473 -
474 -(% class="wikigeneratedid" %)
475 -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:
476 -
477 -
478 -[[BD3C **0.1 **to 5 Hz bandpass filter>>image:BD3C_Z_huddle.0.1.png]]
479 -
480 -[[BD3C **0.1** to 5 Hz bandpass filter>>image:BD3C_N_huddle.0.1.png]]
481 -
482 -== IGU-16 Horizontal noise & how to avoid ==
483 -
484 -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.
485 -
486 -[[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]]
487 -
488 -(% class="wikigeneratedid" %)
489 -The BD3C-5 nodes do not have this issue:
490 -
491 -[[BD3C-5 test, as above. There is no additional noise on the horizontal channels.>>image:BD3C_psd.png]]
492 -
493 493  = **Cleaning** =
494 494  
495 -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.
415 +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.
496 496  
497 497  = **Weights (for shipping)** =
498 498  
499 499  The weights of bags of nodes, as well as data harvesters and node chargers, are listed below:
500 500  
501 -1 bag + 6*IGU-16HR nodes: 18 kg
421 +1 bag + 6 SP (IGU-16HR) nodes: 18 kg
502 502  
503 -1*IGU-16HR data harvester: 21.5 kg
423 +1 SP (IGU-16HR) data harvester: 21.5 kg
504 504  
505 -1*IGU-16HR charger: 26.3 kg
425 +1 SP (IGU-16HR) charger: 26.3 kg
506 506  
507 -1*BD3C-5 charger (with and without 16 cables): 21 kg / 14.5 kg
427 +1 BB (BD3C-5) charger/data harvester (with and without 16 cables): 21 kg / 14.5 kg
508 508  
509 -1 case + 5*BD3C-5 nodes: 22 kg (aggregate battery weight <5kg, 168Wh)
510 -
511 -1 case + 6*BD3C-5 nodes: 25 kg (aggregate battery weight >5kg, 168Wh)
429 +1 case + 5 BB (BD3C-5) nodes and 6 BB nodes: 22 kg / 25 kg
512 512  )))
513 513  
514 514  (% class="col-xs-12 col-sm-4" %)
... ... @@ -592,8 +592,8 @@
592 592  |**Dimensions (LxHxW)**|558 x 357 x 300mm
593 593  |**Input rating**|100-210V - 50/60Hz
594 594  |**Power**|1000W
595 -|**Weight**|14.5 kg
596 -|**Weight with cables**|21 kg
513 +|**Weight**|14.5kg
514 +|**Weight with cables**|21kg
597 597  )))
598 598  
599 599  (% class="box" id="HSmartSoloBD3C-16PortableBatteryCharger" %)
... ... @@ -605,8 +605,8 @@
605 605  |**Dimensions (LxHxW)**|625 x 500 x 366mm
606 606  |**Input rating**|100-210V - 50/60Hz
607 607  |**Power**|100W
608 -|**Weight**|21.5 - 24 kg
609 -|**Capacity**|16 nodes
526 +|**Weight**|21.5 - 24kg
527 +|**Slots no.**|16
610 610  |**Download Speed**|20MB/sec/slot
611 611  )))
612 612  
... ... @@ -616,11 +616,11 @@
616 616  
617 617  [[image:20250729_124644.jpg]]
618 618  
619 -|**Dimensions (LxHxW)**|625 x 500 x 366 mm
620 -|**Input rating**|100-210V - 50/60 Hz
621 -|**Power**|640 W
622 -|**Weight**|26.3 kg
623 -|**Capacity**|16 nodes
537 +|**Dimensions (LxHxW)**|625 x 500 x 366mm
538 +|**Input rating**|100-210V - 50/60Hz
539 +|**Power**|640W
540 +|**Weight**|26.3kg
541 +|**Slots no.**|16
624 624  )))
625 625  
626 626  (% class="box" %)
... ... @@ -630,9 +630,9 @@
630 630  [[image:20250729_124957.jpg]]
631 631  
632 632  
633 -|**Dimensions (LxHxW)**|590 x 225 x 405 mm
634 -|**Weight**|8.2 kg
635 -|**Capacity**|6 nodes
551 +|**Dimensions (LxHxW)**|590 x 225 x 405mm
552 +|**Weight**|8.2kg
553 +|**Slots no.**|6
636 636  )))
637 637  
638 638  (% class="box" %)
... ... @@ -642,13 +642,9 @@
642 642  [[image:20250729_124502.jpg]]
643 643  
644 644  |**Dimensions (LxHxW)**|230 x 340 x 310mm
645 -|**Weight**|(((
646 -3.6kg (empty)
647 -
648 -18.0kg (full)
563 +|**Weight**|3.6kg
564 +|**Slots no.**|6
649 649  )))
650 -|**Capacity**|6 nodes
651 -)))
652 652  
653 653  (% class="box" %)
654 654  (((
... ... @@ -658,7 +658,7 @@
658 658  
659 659  |**Dimensions (LxHxW)**|225 x 200 x 550mm
660 660  |**Weight**|
661 -|**Capacity**|8 nodes
575 +|**Slots no.**|6
662 662  )))
663 663  )))
664 664  )))
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
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]
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.
Date
... ... @@ -1,1 +1,0 @@
1 -2026-07-09 10:45:51.967