member of Embedded 4 You www.embrick.de 1 Open Standard Hardware-Bus modular Sensor/Actor Adaption for IoT Frontends
member of Embedded 4 You www.embrick.de 1
Open Standard Hardware-Bus
modular Sensor/Actor Adaption for IoT Frontends
member of Embedded 4 You www.embrick.de 2
Tools for
ModelbasedSoftware
Development
with Series-Code-GenerationModular
I/O-Hardware- open source- driver support- standardization
emBRICK ... an IMACS spin-off
CustomizedEmbedded Solutions
SW-Design
■ Modellerstellung■ Architektur, MMI-Design
System Concepts and Design■ Erfassen von Systemanforderungen■ Beratung bzgl. Realisierung■ Konzept- und Pflichtenhefterstellung
HW-Development
■ Schaltungs-/Layoutentwicklung■ Inbetriebnahme und Prüfung
HW-Production
■ Muster-/Prototypenbau■ Serienproduktion, Service
Implementation
■ Embedded Software■ API, Treiber, Integration
member of Embedded 4 You www.embrick.de 3
Standardization ... the prior Challenge of IoT
wired, direct
wired, LAN
wireless, WPAN
wireless, WLAN
wireless, Mobile
Gateway
Cloud
IoT Single-End-Point
CPUPow
ersu
ply. Radio
Inte
rface Sensor Actor
IoT-Multi-End-Point
CPU
PowerRadio
1
InterfaceSensor
1..3Actor1..4
Gateway
Actor
Radio2
Interface
member of Embedded 4 You www.embrick.de 4
Typical Hardware Characteristics
wide range of node sizes:
Single-End-Point
Multi-End-Point (complex I/O systems)
member of Embedded 4 You www.embrick.de 5
IoT Standardization ... in focus
Current standardization activities considers: wireless coupling radio/CPU modules (e.g. M2.COM) communication protocols and security cloud security ...
member of Embedded 4 You www.embrick.de 6
IoT Standardization ... not in focus
the frontend coupling
is still made proprietary
An unique sensor/actor interface is not a theme.
IoT-Multi-End-Point
CPU
PowerRadio
1
InterfaceSensor
1..3Actor1..4
Gateway
Actor
Radio2
Interface
member of Embedded 4 You www.embrick.de 7
Consequences of missing Standardization ...
many isolated applications for sensor/actor adaption countless of parallel working developers no possibility of cross-system functions (auto configuration)
For customer/user: no freedom of choice no investment protection hesitated investment
Standardization is also necessary here
member of Embedded 4 You www.embrick.de 8
The Solution: brickBUS
brickBUS ? => the bus technology of emBRICKemBRICK ?
member of Embedded 4 You www.embrick.de 9
brickBUS .... Features
extreme simple connection extreme low cost single master, multiple slaves based on SPI (or bit banging) useable with every µC
supports slave power management support auto configuration applicable for industrial purpose open source (modified BSD-License)
member of Embedded 4 You www.embrick.de 10
Frontend for IoT Building Automation Industrial Automation Embedded PLC replacement Rapid Prototyping of Hardware Testing and Measurement
Typical brickBUS Application Areas
Process Controler
Industrial Automat. Automotive / Rail
ConsumerBuilding Automat.IoT
member of Embedded 4 You www.embrick.de 11
brickBUS ... Hardware Topology
I/Os, in form of Modules (bricks), assembled to Module-Strings
Remote-Master + Couplers
Local-Master(examples)
other Strings of bricks (for larger systems)
member of Embedded 4 You www.embrick.de 12
brickBUS ... the Master Interface
member of Embedded 4 You www.embrick.de 13
brickBUS ... the Slave Interface
member of Embedded 4 You www.embrick.de 14
brickBUS ... the Communication Protocol
1. Initialization: get ID, check version, set address2. Running: transfer header, pause, data, pause, ....)
member of Embedded 4 You www.embrick.de 15www.imacs-gmbh.de
Supports: Initialization Identification Error handling: detection, signalizing, correction
Available Stacks (open source, div. µC) Slave Local-Master Remote-Master
brickBUS – Protocol Stacks
member of Embedded 4 You www.embrick.de 16
Native low energy consumption (20 .. 50 mW / Node, active)
Only CPU-Power is neccessary .
Depending on power mode: ▪ Normal▪ Sleep▪ Deep sleep▪ Off
Power Saving
member of Embedded 4 You www.embrick.de 17
BBF# Format, Mounting▪ 1 = FLAT (Patch Board + DIN-Rail)▪ 2 = BOX (DIN-Rail) ▪ 3 = RACK▪ 4 = IoT
BBC# Coupling, electrical▪ 1 = Standard 10 Pin (<1m extension)▪ 2 = 8 wire mid speed (<10m extension)▪ 3 = 2 wire (<10m extension)▪ 11 = High Speed
BBP# Performance▪ 1 = Standard <1 MBit/s, <1m Extension▪ 2 = Low Speed: <100kBit/s▪ 11 = High Speed (planed 25MBit/s)
Categories of brickBUS ... the BB#
member of Embedded 4 You www.embrick.de 18
▪ Actual > 50 I/O-Bricks for different industries
▪ Autarkic host-systems and coupling boards
▪ Starterkits, enclosures und mounting kits
Available „Bricks“
member of Embedded 4 You www.embrick.de 19
all µController, via SPI or bit-banging (Cortex-M, PIC, ...)
x86, Cortex-Ax (IPCs, Raspberry Pi, Beaglebone Black, ...)
with coupler also via LAN, WLAN, CAN, RSxxx, Feldbusse
Available Host Plattforms
member of Embedded 4 You www.embrick.de 20www.imacs-gmbh.de
Driver/Stack for master (PIC, Cortex-M, Cortex-A, x86) Driver/Stack for slaves (PIC, Cortex-M) Starterkits, Toolkits
Available Software
member of Embedded 4 You www.embrick.de 21
div. RTOS, Windows, Linux, Gamma (Middleware) C/C++, UML (eTrice, SiSy, radCASE, Enterprise-Architect) IEC61131 (logi.CAD, CODESYS) …. or own adaptions
Programing Environments
member of Embedded 4 You www.embrick.de 22
Hardware:
emBRICK wireless
emBRICK 2-wire
emBRICK high-speed
Software / Protocol:
safety, fail safe
Services:
Cloud data base with
emBRICK documentation
all meta data
Roadmap
member of Embedded 4 You www.embrick.de 23
The original Intention of brickBUS ...
... was not the IoT(the most µC and the wireless modules also)
it was developed to ... create control systems ... by connecting small (existing) modules (Bricks) together (instead develop each board new)
covering:all sizes, all topology, all performance, all energy reqirements
member of Embedded 4 You www.embrick.de 24
Questions ?Requests ?
Ideas ?Collaboration ?
Talk to us - now!www.embrick.de
Thank you ...
member of Embedded 4 You www.embrick.de 25
Software - Design-Level-Debugging
member of Embedded 4 You www.embrick.de 26
Software - Tools
Main Screen with Structure-View Process- and Module-VisualizationProcess Logging and Record PanelSequencer for Stimulation by external Data (Testing)Design-Level DebuggingIO- and Varaible-Dataview using all MetadataEnergy-/Resource-ConsumptionTarget-User Interfaces