 Ok, this part starts with our P-Nukla kit, which is based on this hardware, it's in the blister distributed from ST, it's very simple way how to play PSM motor and our library. It contains a white board which is a Nukla board with F-302 family. Then it's some power stage, AHM07 with integrated driver and the last one it's some green motor, drone motor and some power adapter. Power adapter, it's not part of the delivery of the first kit, we selected this one because it's easy to play with the bus voltage and it's useful for our hands-on on Thursday. That's about all, we will start with some very fast testing of the hardware, we want to use some binary file, usually we put it to the installation package but we make some small mistake and in Thursday it's not implemented here and on Friday we put it here. I am not sure which version you downloaded, if you haven't inside documentation the binary file, please ask me and I will distribute flash drive with this binary. On this binary it's some testing firmware for this kit, how to use the binary, you have to find it and send to our Nukla board. Our Nukla board contains some parts, in this top part which is cutted through some line, it's ST link, that's debug tool for the downloading and debugging the code inside the micro. This contains also some use art communication, virtual comport and last part it's some virtual driver, like note underscore and the type of DMCU. You have to right click on the binary file, then find send to, in your language could be different and one of the drive it's not F302. Okay, if you have binary file you can right click on the name, use send to and select the note and after that you will see that part of ST link contains LD1 and this let start flashing. It's mean that indicate that program is downloading and our micro is downloaded through the selected firmware. Then short description about the stuff on the kit, we have there some reset button, important part if some code is lost somewhere you can reset it. Then we have blue button, it's user button, it's possible use it in application. Then we have potentiometer, then on the blue board, on the top we have red lead which is possible so use in our application. On the white board, on the nuclear board it's green lead, then in this case we have two possibility to indication lead and how it's about testing firmware. There is some description about button, we will use in this example button for start, stop and acknowledge fault. In some cases our library indicate fault state and we have to acknowledge it. Then we have green lead and we use this lead for the indication that the motor running. And second lead is use it for the two states, fault and fault over. First it's fault now, it's that I don't know you haven't connected power plug and for that reason you will see red lead flashing. Because it's actual fault and it's indicate problem it's now you have to take care about that. You can put it down and there is space on the bottom. Second information it's that fault over it's mean that something happen in past. I have unplugged DC source and I connected, 12 volts it's now on the VBAS but the application have to react on this fault and you have to confirm that condition it's good to start and that's our second indication. You can acknowledge this fault through the pressing blue button. And last one it's potentiometer and potentiometer is use it for speed regulation. Simply regulation with some loop. And that's all about description that there is some chart that we have some way how to control. We can press the start button, potentiometer the application switch to the run state. If you press the stop then you will return back to the idle. If you use workbench for the control then you will go to the run state. And if some fault happen you are unconnect the power plug or you receive different fault. Then you will see the active fault or fault over and through the fault acknowledge you can jump there. Okay we will start with some slide which is in past name hands-on and hardware tool. I like it because describe what is necessary to do and where it's possible find and some additional stuff. It goes through the some objective that you have to find some software, some necessary hardware, describe workflow. It's important part. Okay then we have to find hardware. Today we have PNUCLO kit but if you want you can find different one. Then we can profile through the motor profiler parameter of the motor. Today we will go with different way. Then we can use some workbench and jump to the generate project, our motor control project to some IDE. Today we will use ATOLIC which is ST solution now. We switch from IR to ATOLIC because during the trainings we every time have some problem with the licensing. Because it's not free of charge. We have some temporary license for the training but still it's not work at all. In all cases then it's easy to use our solution which is free of charge for our usage. And it's work fine. It's not issue to use them. Then last step it's about some configuration or testing if it running well and etc. We can use the motor control workbench with some parts of that which is monitor part. And we can play with this application. We have there also KNOP like standard potentiometer. We have there list of faults which can happen. And there is some action button, start, stop motor and etc. And that's the goal for today. Test our application which is coming not from binary but from the workbench. And we will test it. Then some slide about hardware setup. We have there some solution, some power and control board. You can use big evolution board which contains big or small else TFT display for the graphic way. Then you can use motor control connector. Some of boards, big evolution board contains at least one connector, motor control connector. Some of them contains two connectors for the dual motor control. And you can connect it to the big power stages. Second possibility is inverter. It means that some power part and control part is together on one PCB. This one is some bigger one. And last one is some motor control kits which demonstrate like your case. Some nuclear as the control board, power stage and some motor. And we have also big motor control kit which contains big motor, big power stage and etc. That's what you can select. Then reference of boards which is supported directly from today release. And you can find it in release notes of the workbench. And there is some list which control boards it supported. Now it's still changing. We add new and new boards. Then also evolution board, big boards that's ordered by families. And now we have good luck that we are ported to the HALA AHL library and CUBE MX. And now we have also support for L4 and F7 and for the future we have open doors. Then some slide about the inverters with different configurations and etc. And last table it's with boards. This first part it's about some old style but from my point of view good power stages. Big power stage usually fit on the high voltage. Contains also some bridge. You can connect it directly to the mains. Of course be careful that main work on the mains it's danger. And then it's some additional parts. And now we have some additional boards which is new style. And this is not contains conversion from AC to DC. You have to apply DC voltage. From my side it's pity because I cannot demonstrate to customer at all. We have to have power source for that. But if you want to play with the motors then of course you have to buy some DC source and you can use it. That's different range from some watts up to some kilowatts. That's a very huge range. Then software setup. We already use some kit. You can download directly installation from our sites. But to be sure that you have all things what is necessary. We go through the installation package way. And for that you have in one package also a compiler motor profile workbench etc. Then how you can find it. One already touch it through the through the years. Some repository it is located inside documentation or user folder. And second one it's inside the program files. And you can find their workbench folder and motor profile. Again supported IDE link for them. But in the installation package for training it's already atolic part. Then I will go very fast through this. But it's also important because we will use ST link part of the nuclear board. And for that we have to have some drivers and there is some slide with the description. If PC have some problem with the installation how it solve. Then setup of motor parameters. We have a nice view from the version 5.2. We change the face of the workbench and now we have only one graphic picture. With possibility to click on the motor and define the parameter. Click on the power stage and define a parameter of that all is in one part. Then we can define or find the parameters about the motor with the profiler. But for today we will, that's some slide about motor profiler. You have to select board and play with that. Now it's time to use workbench and define motor control project. We can go through the new window, new project. Or and then select application control part, motor part or switch to the inverter. And then at the end select the motor. If it save that. Or for today we will use some predefined example for this pinucleo kit. We have predefined example which is name pinucleo. But it's not in this, it's scrolled in the opposite side. But you can find pinucleo kit with bulk running motor. And it will be task for now. Then you have part with the parameters of control unit and also with power stage. All is configurable some part you can see online. If you change configuration for example from one shunt to three shunt. It will be replaced with one shunt topology. If you cancel for example bus voltage you will see that the link to the micro it's hidden. And it's demonstrated it's not used. Then we have also some kind of application type. It's predefined some startup procedure how to handle startup or another condition. Okay then we have to finalize finware and generate file from the workbench. We will click on some button, generate button and workbench on the background call kupemix. And generate IOC file. That's a project file of the kupemix. And also generate some parameters. Through the compilation you will combine with the additional setup for example with TFT display. What you want to have inside application combine. And through the compiler compile download it to the micro through the ST link. And last step it's tune in real time check if it works well. And then it's possible finalize the application. Then some slide what is the necessary to put inside the motor parameters. Through the compilation we can again in this way generate after that we have to select proper IDE and configuration. And now it's supported F4.27. I think you have it because we put it to the installation package. We will use true studio and there is two possibility about the hard driver selection. That's not mean that in this case when we have we selected AHL library abstract layer. It's not used for the real motor control part. It's used only for the initialization. To be sure that it's in the abstract layer it's possible read it in the fast way. But it's cost some code extra code because it's in the abstract layer. You have seen in just before lunch one table and comparison if you use AHL or low layer after you select true studio low layer. You can click on generate and you will switch to the summer special window which demonstrate which file is generated and etc. At the end you have to open IDE and there is a way if we cannot associate the project file directly to the true studio. You have to go to true studio then open workspace in the true studio. If you open any project true studio ask you about the definition of the workspace. After that true studio save configuration of windows etc. What projects are open etc. That's the location of the workspace. You have to define the proper space and you can open the proper project. After that you have to compile. For that it's dedicated icon or short key with control B. And after build a project compile the project you can download it to the micro. But true studio haven't any simple way how to download it. For that we use jumping to the debug session which is just on the start download the firmware to the micro. And for that you can click on the icon or press F11. And immediately we terminate the debug session and let the application running. And terminate it's possible do by icon like red square or control F2. And that's it. There is some slide how it's working Kale or IR that's quite similar. And last step is go to or switch back to workbench. Open the monitor part which is icon with some dashboard. And then connect to the your application. Usually it's only one communication port. But if you have a computer with some virtual or something else you have to check the proper communication port. Speed it's on the default state 115k. And then you have to connect. Start the communication firmware with the firmware. And then you can use start, fault acknowledge, control the speed with the knob and etc.