M10 ROAD MAP V1.1 (grammatical and syntactical corrections mostly)
CUBEM10 ROAD MAP V1.1 (M10 for the shake of simplicity)
13/05/20 20.<br>
Some history as a preface.
Despite the fact that we started M10 as a modular PLC system withing a cube of 10x10x10 cm soon realized that in a broader sense, everything is a Programmable Logic Controller. Every microControler Programed Logically to help us in everyday life.
Some history as a preface.
Despite the fact that we started M10 as a modular PLC system within a cube of 10x10x10 cm soon realized that in a broader sense, everything is a Programmable Logic Controller. Every microControler Programed Logically to help us in everyday life.
Many years ago back in 1980 when programming Z80 custom made designs written in assembler for controlling various machinery in reality that was a primitive PLC.
Many years ago back in 1980 when programming Z80 custom made designs written in assembler for controlling various machinery in reality that was a primitive PLC.
...
@@ -16,9 +15,10 @@ PAC is an industrial controller that combines the functionality of a PLC with th
...
@@ -16,9 +15,10 @@ PAC is an industrial controller that combines the functionality of a PLC with th
So M10 idea was born and it does not matter if M10 contains a PLC or a PAC or a custom made C, C++ or Python firmware. M10 likes them all. Because M10 is a controller cube, a container I may say that makes the control job look easy. Any control job.
So M10 idea was born and it does not matter if M10 contains a PLC or a PAC or a custom made C, C++ or Python firmware. M10 likes them all. Because M10 is a controller cube, a container I may say that makes the control job look easy. Any control job.
You may ask what hardware is inside?
You may ask what hardware is inside?
The answer is manythings. Things that haven't cross our mind yet. The hardware inside M10-CUBE may be different as long as the first low of M10-CUBE is not violated
The answer is anything. Things that haven't cross our mind yet. The hardware inside M10CUBE may be different as long as the first low of M10CUBE is not violated
Of course to get an idea of what a M10-CUBE looks like we will introduce you our first M10-CUBE PLC incarnation which at the time of writing ( 05/05/2020) has the following modules ready for fabrication.
But we must start from something we all understand.
To get an idea of what a M10CUBE looks like we will introduce you our first M10CUBE PLC incarnation which at the time of writing ( 05/05/2020) has the following modules ready for fabrication.
1 – CPU module (contains Raspberry Pi 4). All modules share the same 40pin Raspberry bus.
1 – CPU module (contains Raspberry Pi 4). All modules share the same 40pin Raspberry bus.
2 – DIO module. Eight opto isolated 24V inputs plus eight 24V outputs high side transistors.
2 – DIO module. Eight opto isolated 24V inputs plus eight 24V outputs high side transistors.
...
@@ -30,93 +30,78 @@ The team is now preparing
...
@@ -30,93 +30,78 @@ The team is now preparing
- Multi MPU board. STM32, ESP32, ESP8266
- Multi MPU board. STM32, ESP32, ESP8266
- Ideas are keep coming and not necessary all are going to the drawing board but we have fun
- Ideas are keep coming and not necessary all are going to the drawing board but we have fun
Conversation is tacking place in slack M10 workspace www.m10-talk.slack.gr
Conversation is tacking place in slack workspace www.m10cube.slack.gr
If you have skills in electronics, mechanics, in 3D design, in automation engineering or in any way you think you can am braze and contribute to the M10 idea please come and join us.
If you have skills in electronics, mechanics, in 3D design, in automation engineering or in any way you think you like to envolve in the M10CUBE deisgn and contribute please come and join us.
All about M10-CUBE ecosystem must must be open source without any limits.
M10-CUBE ecosystem
All about M10CUBE ecosystem will be open source without any limits.
The design must not violate the rule of M10-CUBE:
M10CUBE ecosystem in detail
- External enclosure (CUBE) maximum dimensions X = 10cm, Y = 10cm, Z = Up to 10cm . Electronics inside must be powered by 24 DC or 220 AC from main supply.
The design must not violate the rule of M10CUBE:
- External enclosure (CUBE) maximum dimensions X = 10cm, Y = 10cm, Z = Up to 10cm. Electronics inside must be powered by 24 DC or 220 AC or POE, or battery.
Some sub rules must also apply but it is to verify that every M10-CUBE incarnation can communicate and stand side by side with the other.
Some sub rules must also apply but it is to verify that every M10CUBE incarnation can communicate and stand side by side with the other.
Directives:
Directives:
-Used materials and modules out of the self if possible.
-Used materials and modules out of the self if possible.
-DIY friendly.
-DIY friendly.
-Think Green and Reuse philosophy
-Think Green and Reuse philosophy
-Z dimension depends on number of modules .
-Z dimension depends on number of UNITS .
-within the CUBE interconnection bus between modules must exist and modules designed for the specific M10CUBE can be interchanged between CUBEs sharing the same bus e.g Rasperry Pi 40 pin.
-All modules belonging to the same M10CUBE type must share the shame mechanical specs for interconnection.
-within the CUBE only interconnection bus between modules must exist and UNITS designed for the specific PACK can be interchanged between CUBEs sharing the same bus.
-M10CUBE can be connected with almost any number of other M10CUBEs by CANBUS, WiFi, Ethernet, LoRaWAN, Bluetooth, or the the upcoming standard by Amazon, Apple, Google, and the ZigBee Alliance
- All UNITS belonging to the same CUBE model must share the shame mechanical specs for interconnection.
-one PACK can be connected with almost any number of other CUBEs by CAN BUS, WiFi, Ethernet
Bluetooth, or the the upcoming standard by Amazon, Apple, Google, and the ZigBee Alliance
-Out of the box as industry dictates CAN BUS is the best candidate and very easy utilized by using readily available software libraries and hardware
-Out of the box as industry dictates CAN BUS is the best candidate and very easy utilized by using readily available software libraries and hardware
Why M10 name?
Why M10 name?
1 - M stand for modular.
-M stand for modular.
-Modular was chosen for obvious reasons.
-Modular was chosen for obvious reasons.
2 - 10 stands for 10cm cube concept and was chosen for various reasons some of them are :
-10 stands for 10cm cube concept and was chosen for various reasons some of them are :
-We have 10 fingers so easy to remember.
-We have 10 fingers so easy to remember.
-10x10x10 as said before is a lot of space to build a DIY PLC (or any controller) though small enough to fit in our home as an automation controller. Connecting more CUBES together with a field-bus like CAN we can spread and distribute a lot of PLC power for any application needed.
-10x10x10 as said before is a lot of space to build a DIY PLC (or any controller) though small enough to fit in our home as an automation controller. Connecting more CUBES together with a field-bus like CAN we can spread and distribute a lot of PLC power for any application needed.
-Friendly dimension to wall mount (Using wall mounting adapters). Can be used next to our wiring junction boxes with acceptable aesthetic (not bulky). With careful artistic 3D design modules can look good even in places where our TV is locating.
-Friendly dimension to wall mount (Using wall mounting adapters). Can be used next to our wiring junction boxes with acceptable aesthetic (not bulky). With careful artistic 3D design modules can look good even in places where our TV is locating.
-Can be Din-Rail mounted Using snap in adapters for use in industrial enclosures
-Can be Din-Rail mounted Using snap in adapters for use in industrial enclosures
M10 concept includes two ideas on one package.
M10 concept includes two ideas on one package.
1 – Abstract (Ideas , Philosophy, Think Green):
1 – Abstract (Ideas , Philosophy, Think Green):
Any technological ideas in the controllers field in an attempt to build an open-source, economical, DIY, Green PLC by incorporating anything done so far in a way that will be modern, good looking industrial design, modular, reusable and more . On this aspect M10 is open and dynamic on the enclosed electronics
Any technological ideas in the controllers field in an attempt to build an open-source, economical, DIY, Green PLC by incorporating anything done so far in a way that will be modern, good looking industrial design, modular, reusable and more . On this aspect M10 is open and dynamic on the enclosed electronics
2 - Material (Framework, Ecosystem, Specifications):
2 - Material (Framework, Ecosystem, Specifications):
That is the real hardware . A container following the M10-CUBE specification. Certain specifications may define the exact hardware but this only applies on a certain type of M10-CUBE
That is the real hardware . A container following the M10CUBE specification. Certain specifications may define the exact hardware but this only applies on a certain type of M10CUBE
To be more specific one can start of building a M10-CUBE PLC using Raspberry Pi 40 pin bus connector. That is the one we choose to try first. Another can start its own M10-CUBE hardware design as long as the m10-CUBE rule is not violated. Of course you are free to do whatever you like and violate M10-CUBE rule but that is not called M10_CUBE. This is only for not loosing track and confuse users. No licensing involved as we decided everything is free and open source.
To be more specific one can start of building a M10CUBE PLC using Raspberry Pi 40 pin bus connector. That is the one we choose to try first. Another can start its own M10CUBE hardware design as long as the M10CUBE rule is not violated. Of course you are free to do whatever you like and violate M10CUBE rule but that is not called M10_CUBE. This is only for not loosing track and confuse users. No licensing involved as we decided everything is free and open source.
That particular M10 -CUBE, lets say M10-CUBE-R will have specific specifications applicable to M10-CUBE-R PLC.
That particular M10 -CUBE, lets say M10CUBE-R will have specific specifications applicable to M10CUBE-R PLC.
All UNITS must be able to communicate and work properly within M10-R PLC
All UNITS must be able to communicate and work properly within M10-R PLC
One can start his own M10-CUBE by not violating the low of M10-CUBE
One can start his own M10CUBE by not violating the low of M10CUBE
Within this limited dimension we must pack as more PLC (electronics) power we can.
Within this limited dimension we must pack as more PLC (electronics) power we can.
5xUNITS of 20mm each on width (z axis) can make a really powerful M10-CUBE PLC.
5xUNITS of 20mm each on width (z axis) can make a really powerful M10CUBE PLC.
CPU can be on one module but that is not limited. Some I/O modules may contain a CPU. In fact there is not strict limit on where the CPU can be located on the system.
CPU can be on one module but that is not limited. Some I/O modules may contain a CPU. In fact there is not strict limit on where the CPU can be located on the system.
A user can build his M10-CUBE PLC and put CPU in any Unit
A user can build his M10CUBE PLC and put CPU in any Unit
Concluding
Concluding
A road map to M10CUBE ecosystem. For the shake of simplicity we call it M10.
1 – M10-CUBE design with external cube dimensions 10x10x10cm
M10 is not reinventing the wheel. Proven technology is used wrapped in an idea to make a reusable micro-controller driven ecosystem. A Green Deal project I may say.
2 - ADD ON BOARDS CASE WIDTH = 17.6 ???
- External dimensions 10x10x10cm.
3 - RASPBERRY PI CASE WIDTH = 29.6 ???
- Raspberry Pi 40 pin bus will be used for the first M10-R PLC. Other CPU boards can be interchangeable with the Raspberry Pi. Next M10CUBE incarnation may use another bus
4 - PCB inside boxes PCB 90x90 mm
- Input modules 24v opto isolated.
5 – RASPI 40 pin bus will be used for the first M10-R PLC. It has a very wide acceptance.
- Output modules 24v high side opto isolated.
6 - Modules interconnection will be done with 2x40 pin connector with long pins
8 - Output card 8 x 24v high side opto isolated. 23017 I2C chip
- Analog IN/OUT modules.
9 - Output card 8 x 24v relay. 23017 I2C chip
- Sensor module for Air quality control.
10 – external clips to the boxes for DIN-RAIL mount
- PSU 24V or 220V, POE, CANBUS and battery backup on the motherboard.
11 - external clips to the boxes for wall mount
- Connection between M10CUBEs Ethernet, WiFi, CANBUS, LoRaWAN.
12 - Analog IN/OUT card
- Add-on module and CPU case 3D printable.
13 – PSU 24 volt can be incorporated on the RASPI motherboard.
- Din-rail and wall mount adapters 3D printable.
14 – POE and battery backup possibility on the RASPI motherboard.
- Add on modules must conform with HAT specification.
15 – 24 volt will come from the I/O connectors externally or somehow from POE
16 - RASPI board can be changed with another CPU board but 40 pin RASPI bus still remains and all interchangeable boards will plug on this 40 pin bus.
Think any Idea that solve controller problems within M10CUBE limitations. Tell us about it or builds it and share it to with the community.
17 – On the M10-CUBE-R we use the raspberry 40 pin bus. So every add on UNIT must considered as HAT and must conform with HAT specification.
Of course anybody can build his own CPU board conforming with M10CUBE CPU standards using any Arduino module (nano, mini, etc)
18 – CPU Unit must have CAN BUS communication so many CUBEs distant apart can easily cooperate and contribute its power to the total system
The design team thinking a multi MPU M10CUBE CPU board containing:
19 – In time M10-CUBES may have different internal buses but CAN BUS must remain the main field bus. In time EtherCAT will be nice to have as a state of art field but.
Think any Idea that solve controller problems within M10-CUBE limitations. Tell us about it or builds it and share it to with the community.
Of course anybody can build his own CPU board conforming with M10-CUBE CPU standards using any Arduino module (nano, mini, etc)
The design team thinking a multi MPU M10-CUBE CPU board containing:
- ESP8266
- ESP8266
- ESP32
- ESP32
- STM32
- STM32
APPLICATIONS for M10-CUBE ecosystem
APPLICATIONS for M10CUBE ecosystem
- PLC controller ever expandable with IEC 61131-3 programming
- PLC controller ever expandable with IEC 61131-3 programming
- Home Automation controller as a Master with, Node-RED, openHAB, Home Assistant, Python etc or as slave device for mains switching, sensor reading, with TASMOTA or any custom hardware
- Home Automation controller as a Master with, Node-RED, openHAB, Home Assistant, Python etc or as slave device for mains switching, sensor reading, with TASMOTA or any custom hardware
- Motor control
- Motor control
...
@@ -128,10 +113,6 @@ APPLICATIONS for M10-CUBE ecosystem
...
@@ -128,10 +113,6 @@ APPLICATIONS for M10-CUBE ecosystem
- Burglar alarm controller
- Burglar alarm controller
- NAS or a set top box for your TV
- NAS or a set top box for your TV
Of course there are limits like everything in life but you can build almost everything. Have the idea and make the board. The new PCB will be will be part of the M10-CUBE family and will be used from everybody.
Of course there are limits like everything in life but you can build almost everything. Have the idea and make the board. The new PCB will be will be part of the M10CUBE family and will be used from everybody.
We like to see and get inspired from any ideas and be happy to contribute.
We like to see and get inspired from any ideas and be happy to contribute.
Naming
- CUBE is the maximum dimension of the M10-CUBE design.
- UNITS (i/o modules) are the bricks for building a CUBE in a modular concept.
