 Hello and welcome on ST Motor Control Workshop dedicated for a new Motor Control Warbench version 5. Why did we decided to make Motor Control Workshop? Firstly we have a new tool version of Motor Control Warbench and secondly there is many many application on the market which requires such solution as you can see on the picture. There are three main points of the workshop. Firstly we will characterize a free-phase BLDC motor. Second point is practical quick and easy development of Motor Control application. And third point is how to move smoothly from Motor Control evaluation to farther development. It means we will teach you how to quickly move from the beginning to the final application. Here is some prerequisities of the Motor Control Workshop. You should have laptop with Windows OS, with admin rights and access to USB port. Then install it our MC package. Third point is USB cable and some hardware Nucleo F303 and XNucleo for Motor application. BLDC motor and power supply. You will see this flowchart during all workshop sessions. We are going to fill all parts from the basic hardware setup to final Motor Control application. Now let's start with hardware getting started. So we will connect all boards together and test our hardware. First lab is test of used hardware with binaries and ST software. And test install it package and related software. It means testing drivers, Motor Control Warbench, install it packages and IDEs. Now let's move to completion and connection of boards. You should have in front of you Nucleo Board for Motor Control application. Nucleo Board with ST SM32 microprocessor motor. In this case it is Jimbal and power supply. On the Nucleo F303 there is also a stealing programmer for programming. Now we have all boards connected and we have to test it with binary file. You can find it in this folder. So it means see users, your username, documents, workshop slash hardware test. You can see here hardware test binary and hardware test Motor Control Warbench project. How to send binary to microprocessor. So you should click, right click on this hardware test binary, send to note F303. It means you will send this binary directly to the microprocessor. If you see blinking the slat on the ST link, it means it is programming the binary to microprocessor correctly. Here is some description what you can see in front of you. So on the ST SM32 Nucleo there is reset button, user button, which we will use for the testing. Green light for indications and potentiometer for speed regulation. Blue button is used for start motor, stop motor and acknowledge a fault if some fault occurs. And let indication of means the software is in middle state, on in run state. Fast flashing it means that fault is active now and slow flashing is, fault is over. It means that fault occurred in the past but now it is only indication that the fault was triggered. And potentiometer for speed regulation. There is description of the testing firmware. Here you can see that the software is in middle state. You can run the motor in two ways. First is by blue button. If you push the button it goes to run state and motor runs. Then you can use potentiometer for speed regulation. And you can go back by the button again. Or you can use motor control war bench monitor. It means that you start the motor from the IDE and it goes to the run. You can use slider in IDE and back to the stop button. If some fault occurs it goes from run to fault. Let indicate that fault is active. And if the fault is over it goes to this state. And you can acknowledge a fault by blue button. Here is another another point. If you press the blue button longer than 3 seconds it will go to pole pair test. And after 25 seconds it goes back to middle state. So it was a binary. And now we will open the project from motor control war bench. So you can found it in the motor control workshop folder. Slash hardware test as we mentioned. Or you can open ST motor control war bench. And click load project. If you open motor control war bench. So now we can see interface and motor control war bench. So first part is a window where you can start a tune motor. And second point you can go to monitor. Which means we will play with the motor. If you are in the monitor first point is to select comport of USB driver. And click to reconnect. If there is a note green note firmware. STMC SDK version something. It means that the board is connected. On the right side there are buttons for playing with motor. So start button stop button. And fault acknowledge and select speed. So you can play with your motor in front of you. And if motor is running and everything works correctly. It is off for this part. And success for this session. At the end of this session there is some notification. As you expect the new versions of tools are coming. It means that IDEs could have different graphic interface in the future. But don't worry functionality and principles remain the same.