 Hello! Within this part we will discuss about different inter-task communication techniques which can be used within 3ARTOS operating system. Inter-task communication is an important part of each operating system. We have few possible techniques within 3ARTOS and CMC-SOS which can be used here. And it is extremely important to understand advantages and disadvantages of each of the techniques and sell them properly within your application. The most known and the most powerful one technique is Q. Q allows you to pass the information between the tasks, to pass a bit more information than just on off. So it can be structure, it can be any type of the information, it can be a pointer. The Qs and operations on Qs may block the tasks while they are trying to put something to the Q or get something from the empty Q. So it is important mechanism as well to manipulate on tasks and block them somehow when they are requesting some more information. We will discuss those in the separate section and we will try to demonstrate each advantages and disadvantages of the Qs. The next point, the next technique within inter-task communication are semaphores. Within 3ARTOS and CMC-SOS in fact we've got two types of semaphores widely used. These semaphores which are in fact on off schemes and counting semaphores which can be given and taken a few times more than one. So those are quite good and simple technique to synchronize the tasks and synchronize the task from interrupt for example. Disadvantage is that we do not have the full control on the fact which of the tasks which are waiting for the semaphores will be allowed to take it. It is decided by the scheduler based on the priority of the task and on the time which is spent on waiting for the semaphore. Those issues are not visible within event flags which are quite new mechanism within 3ARTOS and those are allowing us to synchronize the tasks on multiple events or together and we have to our disposal from 8 to 24 bits which can be used for the synchronization of multiple events, multiple tasks. And the important point is that this technique is not available within CMC-SOS API version 1. In version 2 it is present so we can use them as well. We've got again the separate section of this part as well. Then quite interesting one is direct to task notification called as well the event threads that are using the precise communication between the tasks. So one task is sending the combination of the bits to the other tasks. The address is really well known, well identified and it can be used to have much more control on the signal passed between the tasks. On top of those techniques we can put mutexes which are used to guard the short resources. This must be taken and released always in that order by each task that use those resources. So once we take the mutex we should give it back. So it cannot be given back by other tasks. So this is very important point and there is as well the dedicated part on this. So you can follow all of those groups in the next sections which would be built from theoretical part and then would be illustrated by the hands on parts. Thank you for watching this video.