 Thank you for coming. We would like to present you our idea of an open Linux for space. At the beginning, just let me to show, yeah, at the beginning I have to say that we have prepared for you some environment to comfortably ask questions. So if you scan the QR code, you will be directed to the online application where you can ask questions, which we can review at the end of the presentation. And also we have prepared a few questionnaires for you. So feel free to ask if you would like to. It's to have fun and for us to have some feedback. So who we are? We are mostly from the, let's say, Middle Europe. The most three partners already involved in the Linux for space projects are, we are coming from the Technical University of Liberats and we have partners from Czech Aerospace Research Center and the partners from Czech Experimental Physics Research Center, which is part of the Czech Technical in the Universe. Our partners both have experience in space and above our heads there is a CubeSat already running based on Linux. So how it all hasn't, how it all has started, I think two years or something like this ago, we have started to discuss with some, we have been consulting some European Space Agency project called Mission Hera, if you heard about it. There was a plan and there is already being made a CubeSat, which will go to the Demos and there will be also some measurement and the payload will be driven by the Linux and our professional history is from the automotive, so and we know that there is an automotive Linux, for example. So when we have started to discuss about Linux for space, we have started to do a research. If there is any project like this, like the automotive Linux or any other reference and we found there is none. So we met half a year in last December or November, we have met with our partners, which you can see here and some others on the Czech Space Day or Middle Europe Space Day and again we have asked if there is something and we found there is nothing and something must be done. So that's why we are here. What is our aim? Our aim is to bring the collaborative open-source project, which at the end, our wish, is to have a Yocto-based reference distribution, which will be suitable for the space application and the very special, well-defined use case for space. We would like to bring together all these stakeholders because what we have learned there is many brilliant people working in the space industry, but they are mostly physics or the astrophysics or experience in any other direction, but not so many of them is experience in making Linux. So there is a lot of space for us in this space. And we have already started, we will talk about it later and because space applications are expensive and when I say expensive, I mean horribly expensive, those people those astrophysics used to say, well, this is not expensive because it costs just one million euro. So we have to look for these standards and compliance because there is a lot of restrictions for anything which is leaving the ground and going to the space. So from the beginning, we have started to take carefully in our minds the European Space Agency standards. They are called, they are covered by the European cooperation for space standardization. They have a lot of standards regarding the software development, product development, product management requirements definition and so on. So we have started in February 2002. So you know who we are and if you want and everybody who is looking to us online is involved as well. So please if you want, you can ask us, answer our question why you have come. We are wondering. I was told that people who are online have some latency. So we are waiting for you. Feel free to answer. In a space application, we are used to latencies. It's quite normal. Okay. The bars are still moving. So I'd say next few seconds and we will continue because we have a lot of to say still moving. But I think that we now the results already. Okay. Because it was my idea, but my colleague did all the work. I think for him it's time to start now. Okay. Thank you very much. Now I would like to talk about why we need Linux for space and why we need Linux for space just now. Because space hardware starts to be ready for Linux. That means that right now you can build your own CubeSat more cheaper than before. You can use arm-based components and so on. And if I am now talking about CubeSat, have you ever heard about CubeSat? Do you know what is it? Hands up. Okay. That's great. And who never heard about CubeSat? Okay, so I will explain it. CubeSat is literally a cube device. 10 x 10 x 10 cm cube with devices for measuring. One board controller, EPS, an emergency system controller and another other payloads for measuring. And this CubeSat is able to build much cheaper than several years ago. That means even you can build your custom your own CubeSat. But the problem is with launching. It's still a little bit expensive. So and that's the reason why we are here. Because space is not just for NASA or JAXA. Space is already for us. It's literally open space for us. So and that's the reason why a lot of companies create customized Linux, customized Linux distributions and they head to this distribution. So stable for a long time, make some update, security updates, and so on and so on. And as Linkak mentioned, we both came from automotive industry and we were recognized that same situation was there about 10 years ago. I think, yeah. Because almost every automotive company tries to create custom like embedded Linux and these companies had to sustain them, had to maintain them, make some updates, and so on. And then came on the stage Automotive Great Linux. We came here with similar idea. We want to make one reference distribution of Linux for space. And that's why we are here. Sorry. Of course this, yeah, and this is the CubeSat for this one who doesn't know. Yeah, space is strictly defined as use case. We need to strictly define what could go goes wrong, go wrong in the space. We need to write all all about use case or everything what what could happen there. This system has had to have some requirements before we start to implementation or developing and testing. So at the first phase, I will talk about it later, we need to collect requirements for these systems. And these systems, I mean these requirements have to complain to, shall be complained to space industry standards. Because we are here and we are in Europe. We tries to complain to it ISA standards. But who knows, maybe NASA, JAXA will want to try our Linux for space. So it should be more generic. And now a little bit about history. This is just a selected word, selected words from a journal or article below this table. You can see reference on this article. If you are interested in, you can find this article. It's very interesting, at least for me. So I select four for CubeSat missions. First of them is CubeSat and it was first CubeSat developed in 2003. And the main goal or goal of the mission was to So I forgot the word. To measure low frequency around the ear. And to predict where could LHA happened. Just predict LHAs. Another one, very interesting for me, is Strength One developed by CERNi Space Center launch in 2013. And what is interesting for me is the system on the board. They use Google Nexus One with Android. Hands up and sorry, hands up who has or had Google Nexus One. Okay, thank you. So you can build your over on CubeSat. And last of course Falcon and Elon Musk. Plan, our plan is divided into five missions. First mission already is done, I think, or is still processing. First mission is collecting of requirements. We want to collect the most requirements like experience from our partners, from Czech airspace, research center and others. And that's the reason why we are here, because if you are interested in Linux for space and if you want to help us, it would be grateful if you join us. So the first first phase of this of our plan is requirement collection. The second one, mission, is a requirement definition. Based on the collected requirements, we want to we want to write strictly what does the systems base to be compliant with ISA standards. Third, mission is developing, already developing the Yachter distribution, distribution based on Yachter. And fourth is testing. Testing and making sure that the Linux distribution is really compliant with ISA standards or space industry standards. And five is the biggest one because we are going to space. And this is the next slide for you. What does the space use case? What defines the space use case? What do you think? Please use your phone again. Yeah. Let's wait two more minutes. If you want to support somebody, you can just fill in exactly what I said before. It will make a word cloud for you, but feel free to say anything. And again, welcome to all the people watching us online and feel free to join us. I really like the aliens because the next slide, that's tough. So to participate, you know, there's no one is typing. Yeah, one is typing. I think that this is completely set on our requirements. You can finish your first page, right? So, yeah, free participants are typing. So we will wait. But I think the results of this voting again seem to be... Thank you for all answers. So, and now write answers. And you now know what we have found out. May I? Yeah. What defines the use case? And it's a radiation. A lot of radiation. You were right. That's because we need to think about this because this CubeSat could be shut down immediately when the radiation will push them. So that's the reason why we need to think about radiation. We don't have to. We don't need to be. So what? There could be problems with fire system because fires cannot be opened for a long time and so on. Next one is limited power. We call it a power budget. So we need to think about how much the process, how much processor will take energy from power system. And another one. There is no graphic user interface. Why? Because we don't need it. We don't need a display on the CubeSat. No console interface, line interface because we cannot join them in the space. And so on. Latency asks Lenka to talk about it. And overheating, hard maintenance. I think that the things, the lines, the words you write slide before absolutely fit into this slide. And now I will give a word to Lenka. During our discussions we have found out nearly the same as you have found out here because it's really important that the CubeSat works in extremely dense environment. It's low power, has no user interface and has to be able to survive. So such a, let's say, work definition of use case we have decided to create a set of well-defined requirements which are usable to start to implement anything. And our regular meeting started in February as we told you and on our web page. By the way, the QR code here leads to our web page. You can see the first which we call it 001. If there is any requirement specialist in this room, yes, it's not final yet. I will explain later. But what's important is as we have been talking about the ISA standards to structure the document and from the beginning of the work we use this standard which is called technical requirement specification and which leads you through the requirement collection process. Okay. From the use case, which we have described and you are now familiar with, we will go to the requirements. So for example, from the radiation point of view we have the requirement that the system shall switch off immediately. Okay. What does it mean immediately? You have a few seconds because on the CubeSat or on satellite you have the radiation monitor and it sends you messages and when it sends you switch you off, it means you have to switch off immediately to avoid your memory come on power to the radiation part because otherwise your data will be destroyed. So this is the, let's say the first stuff and from this comes a very, the third one requirement that the file system shall mostly work in regionally. You cannot keep your files in memory. You cannot keep a lot of data for a long time in memory because you will have to remove it from memory quite fastly to any storage and you don't have so much energy for that. Yeah. Again, regarding the reliability which comes from the radiation point of view it's quite typical that you don't have just one Linux there. You have several of them that are typically four. You have, even the physical unit is doubled and on this physical unit you have prepared several instances of Linux in several different memories just to be sure, just to prolong, let's say the life of your CubeSat not towards your money when the radiation comes. So this ends up with quite challenging requirements for booting of the system. It is planned for example to update the firmware but again the firmware update can completely fail down so booting of a system at CubeSat when it's in the sky somewhere is challenging and we had a lot of interesting discussions about it how to do it to fill these requirements. Again, those are just sentences. Those are not requirements. I know it. There are some typical interfaces used in the space world so we named them here just for you to know what's going on there and as we mentioned already there are really horrible power constraints because you have just the sun to give you the energy and in the space world they are working with a term called power budget and it means that you have given amount of energy for each process and the process must not over exceed it. Otherwise the system can collapse and nobody wants to do it wants to have it collapsed. So I thought there would be some other slide. Maybe I removed it. I don't know. Doesn't matter. So what do we have now? We have registered the domain for the project because we think it's really important and you can find something there. First of all there is a registration form. If you will register we will send you a link to the meetings. We didn't want to place the meeting publicly just to avoid any disturbance there. You can find the first version of the requirements. From the engineering point of view there is a lot of work to be done because they have no attributes and a lot of stuff like this. We have started to create a dictionary which we think is also very important and we already have started discussions about how to implement those stuff in Yocto for example. How to be ready for different hardware configuration. Let's say what has to be done in bootloader what has to be done for your kernel etc etc how layers in Yocto should be used how these two features should be used but we haven't published it yet because we haven't finalized it yet. That's something which will come in let's say next month or next year and we have those meetings. Everybody is welcome to join us. Maybe you want to join us so what can you do? You can join the meetings. If you are not interested we are publishing the minutes of meeting online so you can read it there. You can help if you're interested you can help us with the distribution because I know that at this conference it's full of Yocto Specialized developers. You're welcome. We want you. You can use this distribution to be tested on your device or you can provide the hardware. We have agreed with the Czech Aerospace Research Center that their hardware will be one of the first which are to be tested there. Our other plan is at the end of the work just to start the stratosphere balloon which will probably hold something based on Rosbarion's something really light as this so it will be in other reference hardware so feel free to join the penguins going to space. The next community meeting starts I think this is next week at 15 o'clock of the Central European time and you can scan the code to get the invitation. So, now it's up to you. We are really wondering to get your feedback looking for where to get it. The more means I... If you put 10 means I really love the idea if you put just one star it means well... Okay. Not interested at all. I've known it before about 35 people have answered so let's wait for your judgment. I have another question. You can understand what the question is. You don't have to answer but I will be happy if you will answer us. Okay, thank you. Finally, we got this answer so I can go to the last slide. You can ask the questions online. I hope I will see it somewhere... Oh, sorry. Yeah, there are no questions online or you can ask your question directly or give us any comments, feedback, everything is welcome. There are questions already. Okay, so I will go there. Okay. Yeah, the first question about the reference board as I told you we have agreed with our colleagues from National Aerospace Research Centre that they will provide their board for testing and it's a board based on ARM processor which already has been tested in the space application near the surface. Okay, space... CPUs used to be Spark. They are still used. Yeah, the second question, CPUs used to be Spark and sometimes MIPS are these no longer used as much? They are, but there is a slot opening for other hardware as well. Still, if you would like to go, let's say, with MissionHera to the Deimos Moon, you still need to have a hardware which is tested for radiation but there is already existing the ARM, I think it's ARM 7 and it has FPGA core with it together. They used it on a MissionHera to compress the data. It surprised me that I don't know if you know it but they have just, I think, 9 kilobytes per second. They have a lot of data measured there but they need to get down at least two pictures. That's why we think, if you can imagine such an application, the powerful CPUs will appear again more and more. Again, the CubeSats are very often going close to the Earth when the radiation is not so bad and building the CubeSat is really cheap compared to the satellite. You can simply throw them to the space and let them survive for a few months and it's still much more cheaper compared to other stuff. Are you planning to collide with the microchip and their recently awarded NASA contract? There is a big... We didn't plan it yet, maybe in the future. There is a lot of work to be done. I know that there is a lot of activity regarding the RISC-5 also in Europe. We'll see. Is there a typical telemetry protocol being used? Yes, it is. I think it's that mentioned CubeSat protocol. There are a few of them. Some of them are used... Some of them are used at the big satellites and you have to pay to have drivers and so on. Some of them are free, the CubeSat. No? It's free. Our friend told us that I think the space wire... CubeSat is free, that's right. The protocol... You can implement it. But if you want to use... That's right, thank you for correcting me. Linux is too big, yes it is. Too many pointer failure, yes. That's why we agreed that we will join Elisa as well with our use case. Why not to low-level OS such as Zephyr? You know, there is some RTOS at the CubeSat always because I think that... Okay, I don't know if anybody did that. So I will say 99% of CubeSats. The main system is some RTOS and the payloads are based on Linux. This is very important because you still cannot have reliability which is required for the main computer. But again, as there is a lot of complicated software to be running on that, on the CubeSat, for example, as I mentioned the example of the confirmation of the images, those images now are not standard images. It's called a hyperspectral image and it's quite more complicated compared to standard JPEG, let's say, to comprise it. So Linux can find its application in space. It's not just, we can do it, let's do it. It makes sense to have it there. But yes, you're right. The RTOS will still remain there for reliability. Yes, right. Thank you very much. Okay, there is a lot of questions. These were just questions you liked. Yeah, the question regarding the hardware. We would like to provide some reference hardware, but we would like to design the distribution to be open for you to add the hardware. Yes, we will set the rules, what should be done, what should be tested to keep the standards compliance, let's say. How long is the CubeSat expected to be alive? Well, until it dies. But do you know? Two years, yeah, typically. Yeah, okay. So you seem to be really experienced. Come here. And I think, okay, any other questions? You can ask them directly as well or comment it directly. Okay. Yeah, there is a micro. You can use it, it stands here. So I have a question about the testing hardware. So how expensive it is and from which country and by using some media, how could I get that? Sorry, once more. How could I get the test hardware board? You have to buy it. You have to buy it. So how much? I don't know, these are prototypes. They just want to set the checkered space. They have started with the current board, I think, two years ago. And they would like to provide it. And that's, they have testing it. You can ask them. That's why we wanted to add the also Raspberry based example just for everybody who wants to play with that and show his friends that he's running Space Linux in his room to be able to do it. Yeah, I was thinking that the last question of the talk which was asking if we are intended to join in this community could be very different if we were able to know when and how we could get the test hardware that's very important in my point of view. So that was my question and thank you for the answer. We can discuss it. Thank you. Yeah, we can keep it on camera. Okay. So can you easily get this space wire hardware for Raspberry Pi? I don't think so. We have decided to start with the CubeSat. We know that if our mission will grow, grow and grow, we have to, at the end, have the Spiceware and Spice Fiber but at the beginning to keep it doable we would like to implement the CubeSat and be ready for other protocols and hardware. Okay, are there any questions? May I ask our moderator if there are any questions in the online tool? Because people who are watching us online can ask questions as well using that tool. Actually probably there are no questions. So then thank you all.