CANABLOX is designed as a modular development system. Instead of building projects with loose jumper wires and breadboards, CANABLOX uses standardized modules, clean I2C connections, baseboards and practical connectors. A project can be assembled from functional blocks such as a controller, RTC, display, ADC, DAC, keypad and I/O expansion modules.
CANABLOX modules are sold separately, so users can build exactly the setup they need. In the past, CANABLOX was also offered in three different kit configurations during Indiegogo campaigns, but those campaign kits were part of the original launch history. The regular CANABLOX system is based on selecting individual modules and combining them into a project.
The Basic Difference
- Individual CANABLOX modules: selected one by one for a specific project, experiment or upgrade
- Project-oriented module selection: a planned group of separately sold CANABLOX modules chosen to work together for a certain application
This is an important difference. CANABLOX is not limited to a fixed box of parts. The strength of the system is that users can combine the modules they actually need.
CANABLOX Is a Modular System, Not a Fixed Kit
CANABLOX should be understood as a modular ecosystem. A user does not have to buy a predefined set of boards. Instead, each project can be built from selected functional blocks.
For example, a simple clock project may need only a controller carrier, an RTC module and a display module. A measurement project may need a controller, an ADC module and a display. A user-interface project may need a keypad, I/O expander and display. More advanced projects can combine many of these functions on a baseboard.
- Choose only the required functions
- Start small and expand later
- Avoid paying for modules that are not needed
- Reuse modules in different projects
- Build clean, repeatable layouts without breadboard wiring
- Combine controller, input, output, sensor and display functions as needed
This makes CANABLOX different from a conventional starter kit. It is not a one-time beginner box. It is a reusable modular development system.
Why the Old Kit Idea Can Be Misleading
The word "kit" can create the wrong expectation. A kit sounds like a fixed package with a fixed list of parts. CANABLOX is more flexible than that.
During the original CANABLOX launch, three different kits were offered through Indiegogo campaigns. Those campaign bundles were useful as introductory packages, but they should not be confused with the current regular product structure.
Today, the better way to think about CANABLOX is this:
- The modules are the product family
- The user selects the modules needed for the project
- The baseboard provides clean physical organization
- I2C cables replace loose jumper wiring
- The system can grow step by step
The result is more flexible than a starter kit because the user is not locked into one predefined combination.
Main Comparison Table
| Feature | Fixed Starter Kit Concept | CANABLOX Modular Selection |
|---|---|---|
| Product structure | One predefined package | Separately sold modules selected as needed |
| Flexibility | Limited to the included parts | Very high because each module is chosen individually |
| Best for | A fixed beginner package | Real projects, experiments, education and expansion |
| Cost control | May include parts not needed for one project | User buys only the functions required |
| Expansion | Additional parts must be added later | Expansion is the normal design principle |
| Learning value | Good if the included modules match the lesson | Excellent because modules can be selected for the exact topic |
| Project readiness | High only for projects matching the kit | High when the correct module combination is selected |
| Main limitation | Fixed selection may not match every project | Requires some planning before ordering |
Advantage of Individual CANABLOX Modules
The biggest advantage of separately sold CANABLOX modules is that the user can build exactly the system required. There is no need to buy a large bundle when only a few functions are needed.
A balanced CANABLOX setup may include:
- Controller carrier for the microcontroller
- Baseboard for clean physical assembly
- Display module for output
- RTC module for timekeeping
- ADC module for analog inputs
- DAC module for analog outputs
- Keypad or input module for user control
- I/O expander for additional digital signals
- Power or adapter modules where needed
But not every project needs all of these. That is exactly why the modular approach matters.
Example: Simple Clock Project
A simple clock project does not require every CANABLOX module. It may only need a small selection:
- Controller carrier
- DS3231 RTC module
- Display module
- Baseboard
- I2C cables
This gives the user a clean clock project without unnecessary analog, DAC or keypad hardware.
Example: Measurement Project
A basic measurement project may use a different module combination:
- Controller carrier
- ADS1115 ADC module
- Display module
- Baseboard
- I2C cables
If the project later needs real-time timestamps, a DS3231 RTC module can be added. If it needs user input, a keypad module can be added. Nothing has to be redesigned from scratch.
Example: User Interface Project
A user-interface project may focus on input and output instead of sensors:
- Controller carrier
- Display module
- Keypad module
- I/O expander module
- Baseboard
This is useful for menu systems, small control panels, test fixtures and learning projects.
Choosing Modules by Function
| Function Needed | Typical CANABLOX Module Type | Purpose |
|---|---|---|
| Microcontroller connection | Controller carrier | Connects a supported controller module to the CANABLOX system |
| Clean assembly | Baseboard | Holds modules in a structured layout |
| Timekeeping | DS3231 RTC module | Adds clock, calendar and timestamp functions |
| Analog measurement | ADS1115 ADC module | Reads analog voltages through an external ADC |
| Analog output | MCP4725 or MCP4728 DAC module | Creates analog control voltages |
| User input | Keypad module | Adds buttons, menu input or numeric entry |
| Digital expansion | MCP23017 I/O expander module | Adds more digital inputs and outputs |
| Display output | CANABLOX display module | Shows numbers, text or project status |
CANABLOX for Learning
CANABLOX is useful for learning because it lets users focus on electronics concepts without fighting loose wiring. Instead of spending most of the time debugging bad breadboard contacts, students and makers can connect modules cleanly and concentrate on the function of the circuit.
| Learning Goal | Useful Module Type | What It Teaches |
|---|---|---|
| I2C communication | RTC, ADC, DAC, display or I/O module | Addresses, libraries and shared bus behavior |
| Time-based projects | DS3231 RTC module | Clock, calendar and timestamp functions |
| Analog measurement | ADS1115 ADC module | Reading analog voltages through an external ADC |
| Analog output | MCP4725 or MCP4728 DAC module | Creating analog control voltages |
| User input | Keypad module | Menu input and button handling |
| Digital expansion | MCP23017 I/O expander module | Adding more digital inputs and outputs |
The user can choose the modules that match the lesson or project. This makes CANABLOX suitable for both beginners and advanced users.
CANABLOX for Education and Workshops
CANABLOX is especially useful in education because it reduces wiring chaos. Teachers and workshop organizers can select a consistent set of modules for a lesson without relying on fragile jumper-wire breadboard setups.
- Less time wasted on jumper-wire mistakes
- Cleaner project layout
- Repeatable exercises
- Modules can be reused across lessons
- Students can focus on code and system behavior
- Projects look more complete and less improvised
For teaching, the module selection can be matched to the subject. A lesson about timekeeping can use RTC modules. A lesson about analog signals can use ADC and DAC modules. A lesson about digital expansion can use I/O expander modules.
CANABLOX for Demonstrations
CANABLOX is also useful for demonstrations. One isolated module may look like a normal breakout board, but several CANABLOX modules connected on a baseboard show the real value of the system.
- Better visual impression
- Clearer explanation of the system
- More project examples can be shown
- Modules can be rearranged to demonstrate flexibility
- Useful for product photos, videos and workshops
The system becomes much easier to understand when customers can see the controller, display, RTC, keypad and other modules working together as one clean assembly.
When Buying Only One Module Makes Sense
Buying only one CANABLOX module makes sense when the project need is already clear. For example, if you only need an extra ADC module, a second display or a keypad, buying the exact module is the better choice.
- You already own CANABLOX modules
- You need to expand an existing setup
- You need one specific function
- You are replacing or duplicating a module
- You are building several copies of the same project
- You know the exact module list required
This is one of the main advantages of the CANABLOX approach. The system does not force every user into the same package.
When a Planned Module Selection Is Better
A user who is completely new to CANABLOX may not know which modules belong together. In that case, it is useful to think in terms of a planned project selection.
For example:
- Clock project: controller carrier, RTC, display, baseboard and cables
- Measurement project: controller carrier, ADC, display, baseboard and cables
- Control project: controller carrier, keypad, I/O expander, display, baseboard and cables
- Analog project: controller carrier, ADC, DAC, display, baseboard and cables
This is not the same as a fixed starter kit. It is a smarter way to choose individual modules for a specific goal.
When Individual Orders Can Become More Expensive
Buying modules one by one gives maximum control, but a new user may end up placing several small orders if the project was not planned carefully.
- First order: controller carrier and one display
- Second order: RTC module
- Third order: ADC module
- Fourth order: keypad or I/O module
- Extra cables or baseboard added later
This does not mean a fixed kit is required. It simply means that users should think about the complete project before choosing modules.
Choosing by User Type
| User Type | Recommended Approach | Reason |
|---|---|---|
| New to CANABLOX | Start with a simple project-oriented module selection | Makes the system easier to understand without buying unnecessary modules |
| Teacher or workshop organizer | Select a consistent set of modules for the lesson | Creates repeatable projects for all participants |
| Existing CANABLOX user | Buy individual modules | Expands the system exactly where needed |
| Customer building one known project | Buy the exact required modules | Only the required functions are needed |
| Maker exploring several ideas | Choose several general-purpose modules | Display, RTC, ADC, DAC, keypad and I/O modules allow many experiments |
| Product developer testing one function | Buy the specific module needed | Targeted testing is more efficient |
Choosing by Project Type
| Project Type | Suggested Module Selection | Reason |
|---|---|---|
| First CANABLOX clock project | Controller carrier, RTC, display, baseboard and cables | A simple and useful first system |
| Adding one extra analog input | ADC module | Only one specific function is needed |
| Building several identical displays | Display modules | Known repeated module requirement |
| Classroom introduction to modular electronics | Same controller, baseboard and selected modules for each student group | Students can build repeatable examples from the same module family |
| Testing one DAC output concept | DAC module and suitable controller setup | No need to buy unrelated modules if only DAC behavior is being tested |
| Learning the CANABLOX ecosystem | Controller, baseboard, display, input and one or more function modules | The system makes more sense when several modules are used together |
Individual Modules as the Foundation
The best way to think about CANABLOX is not "start with a kit, then expand." A better way is:
- Start with a clear project goal
- Select the required controller carrier
- Add the required display, input, sensor or expansion modules
- Use a baseboard for clean assembly if the project benefits from it
- Add more modules later as the project grows
This approach keeps the system flexible and avoids unnecessary parts.
Individual Modules as Expansion
Once the user understands CANABLOX, individual modules become the natural expansion path.
- Add a second display
- Add another ADC module
- Add more I/O expansion
- Add a different controller carrier
- Add a communication module
- Add modules for a specific project
This makes CANABLOX flexible: build the project you need now, then grow in the direction the next project requires.
Common Mistakes
- Assuming CANABLOX is only a starter kit
- Buying only one module and expecting to understand the whole CANABLOX concept
- Buying individual modules without checking whether cables, baseboard or controller carrier are needed
- Forgetting I2C address planning when adding many modules
- Assuming every module is needed for every project
- Trying to compare CANABLOX modules as isolated breakout boards instead of as part of a system
Conclusion
CANABLOX is not defined by a fixed starter kit. The original Indiegogo campaigns included three different kit configurations, but the current CANABLOX system is based on separately sold modules that can be combined as needed.
- Choose individual CANABLOX modules when you know the exact function you need.
- Choose a project-oriented module selection when you are new to CANABLOX or want to build a complete project from the beginning.
- Use a baseboard and I2C cables when you want the cleanest physical setup.
The strength of CANABLOX is flexibility. Users can start with a small project, expand later, reuse modules and build clean electronic systems without breadboard chaos.