 I will talk about our new educational and prototyping IOT platform we call catcube. But first of all, there is an outline of this talk, but first of all let's have a look at some kind of advertisement because this is your new point in Czech Republic. This is the place what you have to definitely visit. This is Pilsen, you might know it's through beer or technical or culture heritage and long history. You have to visit Pilsen, so that's the end of the advertisement. This is something about our university, we are a technical university with more than 50 years of tradition. We are a full range university including technical faculties, I'm coming from the Faculty of Electrical Engineering and we are located here, so we are here, we have to go about 500 kilometers west and you are there. Recently we started a project called Smart Campus which is a test pad for IOT technologies and we are hiring for collaborations, so if you are from industry and you have some technology you want to test before deployment, we are open to cooperating with you. So this is also a kind of advertisement, but it's closely related to this talk. This is our campus and we are deploying some technologies, we are providing testing for municipalities before deployment, we are cooperating with industrial partners to provide feedback to them and to test their technologies in the era of the university because under the influence of technically equipped students, hackers etc. It's a great place for testing your hardware ideas, I would say. Now the motivation to be here and to create this kind of thing, we call KitKit. The KitKit Cube has been developed at the department of technologies and measurements of our university because we solve many IOT related projects or projects which has an IOT part and because we decided to publish or to open this hardware projects to be an open hardware project, we want to attract new users and ask for feedback naturally. So this is why I'm here. This is a small hell, how to spell the name of the KitKit because the KitKit is short of department in Czech and it's spelled like this small nice name. So this is why this tricky name is spelled like KitKit. Now the reasons behind the creation of such a project are technical and educational because we are a university we need to paint both eras. As I mentioned, we require to create a point of integration for a number of projects we are working on at our department. So KitKit is a point of integration for hardware and software modules. It enables the deployment to many different environments including low power wire, error networks, point-to-point based networks or no network laboratory validation etc and enables speed up of prototyping phase and test serious deployment. And in the same time if we use it in educational process as a platform bringing to our students a mid-complexity system, hardware both in hardware and software in contrast to for example Arduino when we talk about software which is too simple for technical students and maybe projects like free or at those which are too complicated for one semester course I would say. And because this is designed as an entry point for students to hardware work, we choose to follow industry standards to avoid any confusing by reading documentation and using tools. These are parts of the project currently available at GitHub or on GitHub. This includes hardware, so mainboard, battery board and naturally firmware and documentation. Additionally there are some tools enabling simple demonstration or customization of the server side of the software for example Ravan network. Now let's go into detail. As I mentioned we are targeted on industry standard tools. It's about firmware and also hardware or PCB design. All auditorium at the university, the students are both firmware developers and for example electronic engineers so these two are important for educational process use get cubed for. For firmware we use industry standard tools for STM32 MCUs. These are for example K or 2-3 provided by by STM itself but the situation with PCV or with hardware is a bit complicated because there is a huge incompatibility between tools. If you design something in Altium Designer you cannot open your design files in in KiCad or Eagle. So we decided to open the sample projects for many of these tools but the projects are currently still under review. Then we have industry style documentation. As I said it is to avoid confusion when reading data sheets from Texas Instruments and SD. So our documentation has the same style. We have the platform data sheet, we have application notes to describe some particular cases. We naturally have the readme's but the readme is not the main communication or documentation communication thing we use. As I said the main thing is data sheet application notes and other tools used in the field for example oxygen for documentation etc. This is the typical project life cycle for which get cubed is designed for. The first two phases for the typing and validation is normally phases where development of new project is done. For example you can develop new sensor so you will design a custom board, you will design a firmware driver for this sensor board, you will get a form of validation and then in the next two stages we will just use the infrastructure which is provided by getCube itself. So the first two points are development or validation and the next two points are in fact getCube reconfiguration. This is how hardware looks like. We have a main board which is important and we have some extension boards. We decided to reuse existing standard so we support the so-called micro bus standard which shows to use many ways to use sensor boards developed by microelectronica. We adopted this standard to do our custom socket for getCube socket which is in fact a bigger version of the micro bus socket allowing some placement of bigger mechanical parts in between sockets. Still being very small which allows to deployment of the getCube board into field so you can take tens of development boards itself. These are very small and you can put it into field and provide some rapid validation or infield validation by using their boards in fact. This is the hardware for the platform. This is Murata Type-TBZ which is a system in package including STS-MCU and Semtex radio providing Lora communication capability and relative humidity and temperature sensor. So these two chips or packages are placed on the main board. This allows to use just the main board as a primitive but ready to use basic environmental sensor for for example Lora networks. This is the overview of hardware which is specializing to core drivers, modules and module drivers. Here is another view of the firmware but on the top there is its core which takes care about execution control and configuration, manages configuration and user interface then the getCube core drivers which are required by core and then modules itself they implement the actual functionality of the IoT device. On the right hand side there is some state machine demonstrating the common IoT node lifecycle which is in fact the state machine followed by getCube core during the execution control. The getCube one is a little bit complicated but still the same. Here is demonstrated a killing feature I would say of the getCube platform. These five lines of configuration enable the temperature and humidity sensing by using the getCube main board only in Lora network. So if you will download PCB design files you will manufacture our board and you will take our firmware you enter these few lines of configuration code into the command line interface of getCube. You have a fully operational IoT device providing temperature and relative humidity measurements. Now finally a few use cases this is the environmental sensor in my office this is just out of the box functionality of getCube platform itself and this demonstrates flexibility of getCube for rapid prototyping. It is a textile capacitive sensor developed by my colleagues. There is some depth board for Texas Instruments capacity to digital converter and there behind the smallest part is getCube connected to this depth board it's enclosed in standard box and this was about two or three days of prototyping to get a demonstrator of the textile sensor device. So finally I have here some future work and I would like to ask for feedback or contribution here in this forum. So if you have anything to tell to this list of future work or anything any points to my presentation please let me know now or later. So thank you for your attention. So I think we have a lot of time for questions so if you have any questions currently there is no over-air update functionality in fact it is designed to operate in many different networks for example SIGFOX is a network where getCube itself can be used and there it is quite impossible to provide over-air functionality because of you can transmit few bytes only to the to the touch device. So there is it there it is impossible for a lot of one there is partially possible but yeah well there are lots of limitations it's in many in many white iron networks but there are plans to extend or to integrate for example narrowband connectivity and then there would be some room for over-air updates but currently we don't have this this functionality yeah this is currently under development yeah the the remote configuration is currently under development in fact the developer sits there yeah yeah the security is in fact yeah that is the right question the the security is dependent on first the implemented networks I would say there are well the standard weights standard weights provided by standards we implemented are are implemented also here in in catcube but there is a tricky way in catcube how to compromise this device because it provides the terminal in fact if you have access to the terminal you can do anything so if you have physical access to this device you you can do anything you can naturally omit the the terminal you can exclude it when building when building the device but yeah if you have physical access to this device you you will have the keys for example even if there is no terminal you can you can download your e-prom and then you also can obtain obtain security keys for example there are vulnerabilities but still this is mainly the DEF platform so it's acceptable I think or if your question was targeted to another era like the end devices or also about some framework it's like gathering data out of that yeah we use standard infrastructure as defined by for example laura one standard so everything from the device to the network server is defined by the standard and it follows the standard so it also follows the the security security requirements of the standard so that's it but if you have physical physical access to the device then you have a problem or if the attacker has the physical access to this device you have a problem or if if you have injected server so that's that's true yeah I may ask a very stupid question why you know like like what is the goal of this project which would differentiate it from the symbol yeah for example you mentioned are we or like that yeah yeah we or I tried to explain but maybe maybe the explanation was wrong or or poor there are educational reasons and there are technical reasons the educational reason is to find a mid complexity between the stupid simplicity of Arduino I would say and two complex systems in comparison that was that was the the first thing and the second thing is the reusability of of the parts of this project because as according to best of my knowledge there is no project no open hardware project implementing reusability of both hardware and software modules modules such a way like like this one maybe you know something but yeah I I I did some some some researcher yeah yeah that's true but but if you use Arduino then you know in fact if you use Arduino not and Arduino way you just Arduino puts some um it's not too simple as to use uh at mega itself from from the scratch it's simple to use up mega from scratch then to uh to fight against Arduino idea and etc you know so we started from uh from uh different MCU than than Arduino it's more powerful CPU but uh trying to build a friendly ecosystem well documented ecosystem for students and also for some makers developers etc yeah in fact currently it's the university project but one of four partners uh a company from Pilsen already manufactures this and resells the resells the the dev boards or dev packages for for makers so you can buy it okay thank you thank you for questions