The UberBlox™ Classification System (UCS)
Note: This section is going to get a little technical, so if you are not interested in this kind of detail, you can skip it for now. You certainly won’t need it to put together our kits as they come with easy instructions.
Here we will give you a brief look into the UberBlox™ Classification System (UCS). Without it, things would turn chaotic very quickly!
The UCS is made up of a hierarchical tree which has four-letter words defining each branch. At level-0 is UBLX, the root of the tree representing the entire UberBlox™ system. This is usually omitted in naming components since it is implied. It is then branched out to level-1 sub-classes that include the “size” sub-classes (e.g. M025 for 25mm-based components), the OTS components (MECM and MECI), AUTO for automation components, and so on.
A level-1 size sub-class such as M025 is then branched out to level-2 sub-classes for all the parts and components that fall under that particular size sub-class. Some examples are:
– NODE for all Nodes
– UBAR for all Bars
– EXTN for all Extenders
– ROTY for rotary components
– LINR for linear components
– ADPT for adapters
– and several others
Each UberBlox™ component is designated as either a Part (UBXP) or an Assembly (UBXA). The name of each part or assembly starts with its designation.
Level-2 sub-classes are then further branched out to include specifics within that particular sub-class, and this process continues until a component is well-defined.
For example, A free-moving rotary hinge sub-assembly with a 180 deg range under M025 size is defined as
There are further sub-classifications that we won’t get into here as it is beyond the scope of this page.
Our goal has been to create a robust and expandable classification system for UberBlox™, and we hope you will find it intuitive and easy to use, allowing you to get to your parts quickly and efficiently to help speed up your design process.
In order to have a standard and easy way of referring to and getting parts to connect and align properly, UberBlox™ uses discrete units of measurement based on the size of a six-sided Node within a particular size sub-class. For example, if a six-sided Node is part of the UberBlox™ M025 sub-class, then one UberBlox-Unit (or ublok, pronounced “U-Blok”) is equal to 25mm, the dimension of one side of that Node.
Bars and other parts that are not cubes can therefore be defined easily in units within their particular size sub-class without having to worry about their physical length in millimeters. For example, under the M025 sub-class, a Bar of 3 ubloks has a length of 3 x 25mm = 75mm, called a M025-UBAR-03-0075 in the UCS.
So as an example, to create a 7x7x7 ublok structure under the M025 sub-class, you connect eight (8) M025-NODE with twelve (12) M025-UBAR-05-0125 (5 ubloks x 25mm = 125mm length). The result is a hollow cubic structure with 175mm sides.
Note that currently UberBlox™ only implements the M025 sub-class, but this could easily expand in the future to include other size sub-classes, as in M020 with 20mm Nodes, or I100 with 1 inch Nodes.
Documentation is under development with much more detailed explanations to give you a solid understanding of the UCS and the way it is structured so that you can start using it to build your UberBlox™ designs and help expand it with new components.