Hello, people of the internet, my name is Johnny and welcome back to some more Five Nights at Ferney's News. We got a whole bunch of topics to talk about for today, FNA or some of the games in the Fazbearer Fanverse Initiative and some potential info on the release date for Security Breach. But I'm gonna let you know right now, don't get your hopes up, okay, we'll talk about it a bit more when we get to the Security Breach segment of the video. But of course, quickly before we hop into the news double check, make sure you're subscribed. I think it's like 30% of the people who watch me are subscribed, which means 70% of you all are watching and not subscribing, which is just, it makes my little heart sad. And speaking of my heart, FNA4 turned six years old today. That was so ominous. July 23rd, 2015, again six years ago, FNA4 was released. It's insane how fast the time has gone by. Alright, moving on to the actual news topic for today, Funko just decided to randomly release a jumbo lefty plushie out of nowhere. It's coming out in October, but you can pre-order it right now. It's exclusive to EB Games and GameStop and it also looks a bit different from the regular lefty plushie. It looks like the eyes don't pop out, it looks like they're maybe sewn in or something. I personally like it. I already pre-ordered it. 16 inches tall, that's freaking huge. Kind of weird that they made this. Again, it came out of nowhere and also lefty is kind of a strange character to make into a jumbo plushie. I mean, Pizza Sim came out, what, three, four years ago or something? But as we already know, they have been going back to games, you know, FNA6 and FNA3 and make plushies of characters that they haven't before. So maybe, I don't know, hopefully we can see a new wave coming soon after the Curse of Dreadbear in October that has some more phantoms, maybe the withers, maybe some more toys. And speaking of plushies, we kind of have some strange news. It's not confirmation that we're going to get more Sanchez plushies, but they did reply to somebody on Twitter saying, we're contractually not allowed to share what we're working on, but we know you all want some new plush and it's our job to try and do that. So again, not confirmation that we're going to get more Sanchez plushies for FNAF, but who knows, maybe we can see something new from them in the future. I mean, it wasn't too long ago that they got their FNAF license back and they have been re-releasing a lot of products. Right, the plushies, the badge, they all have been re-released, so hopefully new things coming soon. Moving on to the fan games section of the video, I want to start off by talking about fan games at Freddy's before we hop into the Fazbear Fanverse initiative. If you don't know what fan games at Freddy's is, it's basically a huge collection. Think of it like a Nintendo Direct or a State of Play showing off new fan games coming from community members. They have a summer showcase arriving on August the 10th and as you can see, they have a huge roster of games to show off. If you want to stay up to date with what's going on with fan games at Freddy's, I'm going to leave their social link down below. I will be watching it live and I will re-upload my reaction to it on this YouTube channel once I do that on August the 10th. Moving on now to the actual Fanverse initiative games. We have updates on Popgos and Five Nights at Candy's 4, finally. So about two weeks ago, Kane Carter, the creator of Popgos ever getting released a huge freaking devlog detailing what just happened with the game because they made a whole lot of changes to a whole bunch of rooms. It's a pretty long devlog but I'll quickly summarize it. Basically they made the rooms on the cameras larger so that they will fit the actual you know, size of the pizzeria and they'll align with what the rooms look like on the mini map. Here we can see the kitchen as you can see it's now a lot more open and they also had a slight upgrade to the trading coins. Looking at the three versions side by side, you can barely tell the difference. So that's just a quick overview. Again, there's a lot more detail in the devlog itself. So again, it's linked down below. And speaking of the Popgos evergreen cards, a few people actually received in real life versions of the cards themselves that are going to appear in the game. These first couple came from Nova over on Twitter. They're going to be linked down below. And it seems like everybody who received these cards get a total of four, a card from Darko, one from Popgos and one from Balloon Boy. And then they also get a special variant of a different character. For example, Nova got Scarecrow, Stone the Crow, and another person named Gigi Games got Zombie, Blake.  And unfortunately, it seems like they are not going to be merchandise just yet. Hopefully, I don't know, Kane said that he did pitch the idea to Scott and that there is a demand for these cards. So if you show enough support for them, maybe we can get them as official merchandise sometime in the future. Moving on now to Candies 4. It's been a very, very long time since we heard anything from Emile Mako, the creator of FNAC 4 about the game. He posted a quick devlog because it is also the sixth anniversary the other day when he posted this of the original Five Nights at Candies. Why is everything turning so old? Gosh, I feel so old. Anyways, the devlog goes as followed. Update plus sixth anniversary of FNAC. Today marks six years since the first FNAC game released, all the way back in 2015. I never would have imagined that I'd still be working on this series to this day, let alone that people still remember these games. First of all, I want to apologize for the long silence. I haven't been able to really add anything that you could call an update in quite a while, both due to the lack of new work that has been done on FNAC 4 and because I dislike having to share more tidbits of information about the game as a punishment to myself for not having the game finished yet, ha ha. I really want everyone to go into the game as blind as possible when it comes out. Basically, there's been a ton of separate difficulties recently that have impacted me and my workflow. The most notable, of course, being pretty much all of 2020. Even though the Fazbear fanverse became a thing, which was and still is an incredible thing, I've struggled quite a bit with motivational issues on top of the usual bombardment of university work. Due to us students having to work from home, my university had to take quite a long time to adapt to this, which made project work and studying a lot tougher, at least for me. Though I don't want this post to become an entire psychological evaluation, so I just want to state again that FNAC 4 is still happening, even if it is taking longer to complete. I'm also working as hard as I can on the ports and updates for 5 minutes. I can't use remastered 2 and 3. So even if you don't hear from me, know that the wait will be worth it. It's nice to get an update on FNAC 4 and also Emil himself. I really hope that he's not stressing himself too much with all of this work. Of course, life issues get in the way of a lot of things, unfortunately, so I really, really, really, really do hope that Emil is doing well. And like he just said, even if it does take a long time for the game to come out, for us to get another update on the new game, it is nice to know that, you know, he's taking his time making it as perfect as he can, while also trying to, you know, deal with a lot of life issues. Oh, we got a few things to touch upon involving FNAF 8, or it's going to be quite silent for the game, at least for the next couple of months. I did make a whole video about it, so I'm not going to go too in-depth, but basically, Olimix made a whole post about updates coming to the game sometime this fall. A lot of bug fixes, a lot of new game modes, new characters, new animatronics skins, all that good stuff. And in this silence, we're going to get a lot of blasts from the past events. Right now, we are in the Freddy Festival event, as they're calling it, where you can get Black-Eyes Frostbear, Shamrock Freddy, Golden Freddy, Woodland Toy Freddy, VR Toy Freddy, and also Freddy Frostbear. VR Toy Freddy just came into the game as of yesterday, and that is all the updates we have on FNAF AR right now. It's also worth pointing out that their merchandise store has been down officially for one full month. So, I don't know when we're going to see that website go back up again, but I guess we're just going to have to keep waiting. Alright, now let's talk about security breach, because everybody's going bonkers that GameStop has a supposed release date for the video game. I feel like I've talked about this before, so I don't know why I'm needing to talk about it again, but everybody's going, you know, sicko mode, mode bomba, saying, oh my gosh, it's coming out December the 27th. Can I just state how much I really dislike when people get all excited about release dates, even though Scott Norsear will have said anything about a release date, and that they have specifically said that they're not going to keep putting out release dates, because, well, everybody gets hyped up only for them to delay it again. Like, for the love of God, guys, this is literally a placeholder. We've had this exact same talk so many times in the past. In fact, guess what the release date for the game was all the way back last year in 2020? Oh, would you look at that? Release date December 27th, 2019. Hmm, it appears to be the exact same day, guys. I'm getting so sick and tired so fast of everybody hyping everybody up about the release date, and not actually looking into the freaking research. Kane said that this has been up since May on the Irish GameStop site that this screenshot is from, which means that that was posted only a few weeks after Scott delayed the game back in April to later this year. And do you really think that they're going to have an exact release date only a few weeks after delaying the game again? Like, I don't get it. Please, someone explain to me. Why is everybody thinking that this is their release date? Why are people, you know, hyping each other up? This is literally a placeholder. We've had this placeholder for many months now. I just don't get it. So yeah, don't believe this December 27th freaking release date. It's literally a placeholder on GameStop website. They've done this so many times in the past. They have a release date for an upcoming game to be at the very end of the year. It just so happens to be also the time where we could maybe speculate security breach releasing. I just don't get it. Whatever. Let's move on to the final topic. So the final topic isn't really that interesting, but it is nice to know.  It's SkylerLights. Thank you, Scott video.  And Scott left a comment saying this is really amazing. I don't feel like I deserve this. Thank you to everyone who contributed to this. You've really, really made this all worthwhile. I'm not even sure what else to say. I really don't deserve this sort of thing. Thank you. A really sweet comment on a very sweet video. And that is all the news for today. Thank you guys so much for watching. Thank you guys so much for sticking with me through all these years. I know it's a weird thing to say at the end of a random video, but thank you. If you enjoyed it, maybe hit the like button. Maybe subscribe if you haven't already. Got a lot of videos coming out over the next couple of days. If you want to subscribe to see those, that's going to be it. Thank you guys and I'll see you on the flip side. Goodbye.


Hi everyone, Joe for jashbyscasebreaks.com. This is the recap video for 2022 Panini Prison Football Six Box Picker Team number three. There's the list right there. Big thanks to everybody who got into the action. I appreciate it. And here is the recap. Got the Sam Williams, Red Wave, LT, Chris Alavi Silver, Kenny Pickett, Malik Willis, that Nelson Aguileras, the 15. Some nice stuff here. Kenny Pickett Silver, Kenny Pickett Rookie Silver, and the Red Wave autograph of Kenny Pickett and a out of five gold vinyl CD-LAM. Some nice stuff here. We've got more prison football in the store. Check it out, jashbyscasebreaks.com. I'm Joe, I'll see you next time for the next one. Bye bye.


Hello, and welcome to this ST Microelectronics presentation on the basics of stepper motor operation and driving. In this presentation, we will discuss the two most common configurations for stepper motors and the required drive circuit for each. The basic drive sequences, full step, half step, and microstepping, drive topologies for steppers, and typical drive profiles. The basic configuration for the stepper motor has a permanent magnet on its rotor and coils on the stator. A rotating magnetic field is generated by applying alternating positive and negative currents to the stator coils. The most common configuration of a stepper motor in use today is a two-phase bipolar-driven motor. This motor needs an H-bridge to drive each of the two phases. The stepper is a synchronous machine, and the rotational speed is directly controlled by the rate at which the currents in the stator are changed. Stepper motors are well suited for low-torque applications that need precise position control, such as computer peripherals or numerically controlled machine tools. In these applications, steppers have several advantages. Since they have no brushes, they are high-reliability motors, whose life is essentially determined by the life of the bearings or bushings in the motor. The control loop is very cheap since the motor is driven open loop without any position or speed feedback elements. Since the motor is a synchronous machine, speed control is simple, and the motor configuration inherently gives good position control. There are two common configurations for stepper motors. The two-phase bipolar motor and the four-phase unipolar motor. In their simplest form, as shown in the figure, they are a permanent magnet on the rotor and two coils oriented at 90 degrees to each other on the stator. When driven, the current in each of the coils produce a magnetic vector that's summed together, and the permanent magnet on the rotor will align with this magnetic vector. Changing the polarity of the current will change the angle of the magnetic vector and thus generate the rotating magnetic field that will make the motor turn. For the bipolar motor, this is done by sequentially changing the polarity of the current in the two windings. For the unipolar motor, the coil is wound in a center-tapped configuration with the center typically connected to a positive supply voltage. Alternately, connecting the two end connections to ground will change the direction of the resulting magnetic vector. The circuit required to drive each of the configurations are shown here. The bipolar motor needs eight transistors connected in a dual H-bridge configuration to drive the motor, while the unipolar motor needs only four transistors connected to ground to drive the motor. Early applications of stepper motors often used the unipolar configuration since it required fewer transistors to drive and did not require a level shift to drive the upper transistors of an H-bridge. So, if the unipolar motor is much easier to drive, why would you use a bipolar stepper motor? The answer is that for the same motor frame size, a motor that is wound as a bipolar motor will be able to deliver about 40% more torque than the same frame wound as a unipolar motor. Basically, this is because of better usage of the copper in the motor. One of the factors that limit the amount of torque that can be produced is the dissipation in the coil and the maximum allowable temperature in the coil. The dissipation in the coil is proportional to the square of the current in the winding and the coil resistance, and the coil resistance is proportional to the number of turns, N. Torque, however, is proportional to the current times N. When you look at a unipolar motor with N turns in each half of the coil, the dissipation is proportional to I squared times N, and the torque is proportional to I times N. Driving the same coil as a bipolar motor, the current flows through both halves of the coil, so the torque is proportional to I times 2N, and the dissipation is proportional to I squared times 2N. If you set the maximum dissipation to be the same in each unit, you see that for the bipolar motor, you can only drive 70%, actually 1 over the square root of 2 of the current in the unipolar motor. However, that current flows through both halves of the coil and therefore produces 40% more torque. The improvement in performance that can be achieved using the bipolar motor makes it more advantageous than the unipolar motor. Integrated driver ICs have greatly simplified the design for the bipolar motor drive circuits since they integrate both the power transistors and all of the level shifting and gate drive circuitry into one easy to use IC. Typically we find that for low performance applications, for example the paper feed in a desktop inkjet printer, unipolar motors are still commonly used with very simple drive circuits. For higher performance applications, bipolar motors are typically used. Continuing the step sequence in the 1357 order causes the motor to rotate in the forward direction and reversing the order to 7531 will cause the motor to rotate in the reverse direction. This drive sequence is commonly referred to as full step since each change in the current moves the motor one step. For our simple motor that only has one pole pair on the rotor, there are four steps per revolution and one electrical cycle completes one revolution. Real stepper motors of course have many more steps per revolution. One common configuration has 7.5 degree steps which corresponds to 50 steps per revolution for a 12 pole pair motor. Such a motor would require 12 electrical cycles to complete one mechanical revolution. Another common configuration is 1.8 degrees per step with 200 steps per revolution and 25 pole pairs requiring 25 electrical cycles per revolution. Although other configurations are possible, these are the two most common. As we said earlier, the basic configuration of a stepper motor can be thought of as a magnet on the rotor and two coils on the stator oriented at 90 degrees. If we start by energizing both coils with the same magnitude of current, the resulting magnetic vector will be at 45 degrees and the rotator will move to a line with this vector as shown in state 1 on the slide. By reversing the direction of current flow in the first coil, as shown in state 3, the magnetic vector moves 90 degrees and the rotor will follow. Reversing the direction of current in the second coil will then move the rotor to state 5. The same behavior from state 5 to state 7. Continuing the step sequence in the 1, 3, 5, 7 order causes the motor to rotate in the forward direction and reversing the order to 7, 5, 3, 1 will cause the motor to rotate in the reverse direction. This drive sequence is commonly referred to as full step since each change in the current moves the motor one step. For our simple motor that only has one pole pair on the rotor, there are four steps per revolution and one electrical cycle completes one revolution. Real stepper motors of course have many more steps per revolution. One common configuration has 7.5 degree steps which corresponds to 50 steps per revolution for a 12 pole pair motor. Such a motor would require 12 electrical cycles to complete one mechanical revolution. Another common configuration is 1.8 degrees per step with 200 steps per revolution and 25 pole pairs requiring 25 electrical cycles per revolution. Although other configurations are possible, these are the two most common. The idealized current wave form for the two coil currents are square waves shifted 90 degrees in phase. Of course we know that the slope of the current changes will be limited by the inductance and as we will see later can have a dramatic effect on the performance of the motor. If the step sequence is reversed, one of the two current wave forms will be shifted 180 degrees as the motor rotates the reverse direction. You may have observed that only oddly numbered states were used in the previous sequence. One may ask why there are not even numbered states. The answer is that there actually are some states halfway between the full step positions that the motor can easily be driven to. These positions are obtained by simply turning off the current in one coil before turning it on in the opposite direction. States 2, 4, 6 and 8 have current in one winding and no current in the other. Since these positions are halfway between the full step positions, they are referred to as half steps. The drive sequence to operate the motor in half step then has 8 states per electrical cycle. The advantage is that you can easily double the number of steps per revolution, so a 1.8 degree per step motor now gives 0.9 degrees of resolution. An idealized half step sequence of current in the two windings is shown here. The sequence is characterized by the current being positive for 3 steps, 0 for 1 step, negative for 3 steps and 0 for 1 step. The two coil currents are, as in the previous slide, shifted 90 degrees with respect to each other and reversing the sequence would shift one of the two current waveforms by 180 degrees. This simple sequence is generated by switching the currents on or off and controlling the direction of current flow in the coils so that the magnitude of a current when it is on is always the same. If you look at the sequence above, you see that for every other step, the current in one of the two windings is 0. Since the magnitude of the resulting magnetic vector is equal to the vector sum of the vectors generated by the two coils, the magnitude when both coils are energized will be larger by a factor square root of 2 than when only one of the two coils is energized. This variation leads to a ripple in the torque since the torque is proportional to the magnitude of the magnetic vector. It is possible to compensate for the torque ripple by increasing the current in the one winding that is on during the half step so that the magnitude of the magnetic vector is the same as it would be if both of the windings were energized. If we increase the current in the one on coil by the square root of 2, then we will produce the same magnitude of vector when the one coil is on as is produced when the two coils are driven by the same current. The current waveforms shown here have been modified to use this technique to control the current and reduce the torque ripple. As we will see later, this can easily be done with some of the control ICs by simply changing a reference for the motor current. Now that we have discussed the basic drive sequences for stepper motors, we will look at some common driver topologies for steppers. The simplest drive topology is to drive the motor with the rated voltage and simply switch the coils in sequence as we have seen in the full step or half step sequences. The figure here represents such a drive topology. The circuit has been simplified with the single transistor representing one of the transistors of a unipolar drive or the composite of two transistors in the bridge of a bipolar drive. When the phase is energized, the current will increase exponentially until it reaches a value that is equal to the supply voltage divided by the motor resistance, Rc. The time constant of the exponential is L divided by R, which gives rise to the name L over R drive. This drive configuration is very simple, requires no additional components beyond those required to control the current sequence and operates from a single supply voltage. However, it is a relatively low performance in terms of the speed torque profile. One of the reasons the performance is limited is due to the inductive properties of the coils that limit the rate of change of current. If we consider a typical five volts one amp stepper motor, it will have a five ohm resistance. When the coil is energized, the current increases exponentially until it reaches its full value of one amp. As we see in the figure, this can be relatively slow. When we are driving the motor in full step, each time we make a step, the current will reverse direction and the rise time will be limited by the motor inductance. Here we see the step command on the top trace and the corresponding motor phase current in the lower trace. When the step time is longer than the LR time constant of the motor, the current reaches the expected peak value during each step and we get the expected torque produced by the motor. As we increase the speed and the step time decreases, we reach a point where the current just reaches the desired peak during each step. When the step rate is increased further, the motor current may no longer reach the expected value in each step, as we see here. With less time in each step and the current rise limited by the inductance of the motor, we see that the peak current reached during each step is less than the peak value at the slower speed. Increasing the speed a bit more further reduces the peak current. Further increases in speed lead to lower peak currents. When we reach this point, the motor has most likely already stalled if it has any load on it. Since the torque is proportional to the current in the motor, the torque will decrease as the peak current decreases. An earlier slide showed the speed torque curve with a downward slope at increasing speed. This reduction in the peak current at higher speed is one of the contributing factors. As you can easily see from the figures, if the time constant of the current could be decreased, you could expect better performance from the motor. One way to reduce the time constant while maintaining the same peak current is shown here. By placing a resistor in series with the motor winding and increasing the drive voltage, you can achieve the same motor current, however the time constant, which is l over r, is decreased. This drive technique called l over nr was very common in early line printer applications that needed a faster response from the stepper motor. Going back to our example motor, if we increase the supply to 25 volts and add an external 20 ohm resistance, we still get 1 amp current, but the rise time is significantly reduced. Here we compare the typical 5 volt 1 amp motor driven from 5 volts in the l over r configuration and a motor driven in the l over nr configuration using a series resistance equal to four times the motor coil resistance and five times the drive voltage or 25 volts. We see that the rise time is significantly reduced, so we would expect to be able to operate at higher speed. However, the additional dissipation in the added external resistance is not acceptable in today's applications. What is needed is a drive that gives a faster rise time without the dissipation of the l over nr drive. Just as switching regulators have replaced linear regulators for power supplies, switching techniques can be applied to the motor drive as well. When driving a motor we already have a large inductance to work with, so the only additional components needed are the circuit to sense and regulate the current in the motor winding. Common techniques that work well for stepper motors are shown here. In these circuits the comparator senses the coil current by sensing the voltage across the sense resistor and compares it to a reference input. In the fixed frequency implementation when the current exceeds the set value the comparator will reset the flip flop and turn off the transistor allowing the current to decay. The oscillator periodically sets the flip flop causing the cycle to repeat implementing a fixed frequency pulse width modulation or PWM to regulate the peak current. In the constant off-time implementation the comparator triggers a monostable that turns the output off for a fixed period of time each time the peak current of the motor reaches the threshold set by the reference input. Although we commonly refer to this as PWM it is really a fixed off-time frequency modulation since the off-time is fixed and the on-time varies to regulate the current. Both of these currents have been implemented in control ICs for stepper motors. In most applications either technique may be used and there will not be any perceivable difference in the operation of the motor. In some applications particularly when the duty cycle can exceed 50 percent the constant off-time approach offers some advantages in stability of the chopping. Using the chopper controlled current drive to drive the stepper motor allows a very fast current rise and good efficiency in the drive. Comparing the current waveform to the previous example we see a slight improvement in the rise time compared to the L over N R configuration. The example shows the same motor we had earlier operating at five times the rated voltage 25 volts with a chopper current control set to control a peak current of one amp. Obviously there are a lot of advantages to using the chopper drive that improve the performance and give a very good efficiency. The disadvantages of complexity and additional circuitry have mostly been overcome by integrated motor drivers that include all of the control circuits and in many cases also the power transistors on a single monolithic IC. Although some low-end applications are still done using a simple L over R drive and a unipolar motor most applications today use chopper drive with integrated driver ICs to drive bipolar stepper motors. When discussing the drive topologies in the previous section the power stage was simplified to a single transistor in the examples. For a bipolar motor the power stage is actually an H bridge driving each coil and we have some options on how we apply the chopping control to the bridge. The selection made will have an effect on the ripple current and in some cases the performance we get from the motor. We will now look at the chopping modes we can have with an H bridge. The diagram on the left shows the current path during the on time of the PWM. One of the upper transistors and the lower transistor on the opposite side of the bridge are turned on so that current flows through the coil. We know that when we turn off one or both of these transistors the inductive property of the coil will tend to keep the current flowing so the output will fly back so that current flows through the clamp diode or diodes and continues to flow in the coil until it reaches zero or we turn the transistor on again. If we turn off only the lower transistor the current will flow through the upper transistor that is on the coil and the opposite diode on the upper side as shown in the center diagram. This is typically called slow decay mode or phase chopping. Since the rate of change of current in a coil is proportional to the voltage across the coil as given by the equation v equals ldi over dt we know that the current will decay slowly since the voltage across the coil is only the forward diode drop plus the drop across the one transistor. If we turn off both the lower and upper transistors as shown in the figure on the right then the current flows through two diodes the coil and back to the supply. This is typically called fast decay mode or enable chopping. In this case the current will decay much faster since the voltage across the coil is equal to the supply voltage plus the forward drop of the two diodes. In this figure you can see a comparison between fast and slow decay modes of operation. Two things are important to notice first the ripple current is much higher in the fast decay mode second the current decays or decreases much faster in the fast decay mode. For most applications that are operated in full step or half step sequences the slow decay mode is probably a better choice since it gives less ripple in the current. Many times it will also give less dissipation in the driver but this is not always the case. The fast decay has an advantage if the current must decay rapidly which is required in some applications. We have been talking about full step or half step operation. In this case the positioning is limited to the four or eight positions per electrical cycle that are naturally achieved by controlling the phase relationship of the currents without changing the magnitude. For applications that require higher resolution in positioning it is possible to drive a step promoter to positions between the full and half step positions. This is generally referred to as microstepping. Remember that the rotor is a permanent magnet that will attempt to align with the magnetic vector produced by the two coils on the stator. For full step the two coils are energized with equal currents producing a magnetic vector aligned at 45 degrees. For the half step positions only one coil is energized and the magnetic vector is either horizontal or vertical. These two cases are shown in the diagram as the half and full step positions. For microstepping we want to move the rotor to a position between the full step and half step positions. We can align the vector to different positions if we independently control the currents in the two windings. For example if one phase were energized with a current equal to twice the current in the second coil then the magnetic vector would be along an angle of 30 degrees as shown by the third vector in the diagram. In the limit for any angle on the circle the coils could be driven by a current proportional to the sine and cosine of the desired angle. In this way it is theoretically possible to position the rotor at any desired angle. Of course there are some mechanical issues and positioning of the two coils will give a lower limit to what is achievable. We have already seen the current controlled drive circuit where we have the ability to set the coil current by setting the reference voltage. Using the two chopping current controls and setting the reference for each using a DAC it is pretty easy to generate the desired currents in each of the two coils. Here you can see the actual operating waveforms implemented with an L6208 for a microstepping drive. Channels two and three, the green and purple traces, are the output of the DAC for the two coils. Channel four, the magenta trace, shows the current in the winding corresponding to the reference voltage on channel two. Channel one shows the step clock input that controls the phase relationship of the bridge. In this example the sine wave is synthesized using 16 microsteps per step dividing each 90 degrees into 16 5.63 degree microsteps. This implementation uses an 8-bit DAC actually an RC filter on a PWM output from a microcontroller to generate the two reference voltages. As a rule of thumb you need two additional bits in the DAC above the number of microsteps to generate an acceptable sine wave. For the 16 microsteps here a 6-bit DAC would be sufficient. With an 8-bit DAC you could generate an acceptable approximation for the two sine waves for a 64 microstep application. Typically you can achieve 1 16th to 1 32nd microstepping with most motors. How well the motor will follow the microstepping waveform depends on the construction of the motor. This is a good time in the presentation to discuss a couple of anomalies that can occur especially when using the peak detection current controls due to microstepping. In this type of control there are two phenomena that have a significant influence on the current waveform and specifically the ability to control the current so that it matches the desired sinusoidal waveform. These are the minimum current that the circuit can regulate and limitations in the decay rate of the current introduced by the slow decay mode of chopping. The first anomaly that will affect the microstepping drive or the holding current that can be controlled is the minimum current that the chopping drive can regulate. For any peak detect chopping control like the control shown earlier there is a minimum duty cycle that can be achieved due to limitations in the control circuit. The minimum on time may be set by several factors. One factor is the propagation delay through the loop. This includes the delay through the comparator, the propagation delay through the logic, and the turnoff delay time through the base or gate drive circuit and the power transistor. Basically it is the delay from the time the voltage across the sense resistor exceeds the reference voltage at the input to the comparator until the power transistor can be turned off. In some controls like the L297 and L6506 the oscillator basically sets a minimum on time which is the width of the sink pulse that is clocking the RS flip-flop. Some control ICs have a blanking time during which the output of the comparator is ignored. This is done intentionally to mask the switching noise but effectively increase the minimum on time. For a fixed off time control the off time set by the monostable and thus the minimum on time and fixed off time establish a minimum duty cycle. For fixed frequency control the period is set by the oscillator and the minimum on time effectively sets the duty cycle directly. In either case the result is that there is a minimum duty cycle that the control circuit can regulate. In operation the motor current is compared to a reference iREF. In the circuit implementation the current is represented by the voltage across the sense resistor and the reference is really the vREF applied to the comparator. We expect that as we reduce the reference the duty cycle will decrease and the current will also decrease proportionally. Ideally following a linear transfer curve like the dashed blue line. As the reference is decreased the peak current detected will decrease and the output PWM will also reduce until we reach the minimum duty cycle that the circuit can regulate. Below this point a further reduction of the reference will not result in a further reduction in the current. When the reference is decreased further the minimum duty cycle is still applied to the output therefore no more reduction in regulated current is possible. This introduces a non-linearity in the transfer function as shown by the orange line. If a value between zero and the minimum current is commanded the circuit will basically respond with the minimum current. In full step and half step applications this will limit the minimum current that can be delivered if we try to reduce the current to a lower value for a holding torque. In microstepping this means that it is not possible to get zero current simply by setting Vref to zero volts. Of course if we were to use a fast decay the minimum current would be a bit lower. Also there is a discontinuity in the transfer function when the current in the coil transitions from continuous to discontinuous. Looking at microstepping applications it is obvious that we cannot get zero current by simply applying a zero reference. The value of the minimum current may also affect how well we can match the sine wave we are trying to synthesize. Here we have the ideal waveforms for a microstepping drive running at a constant speed. The two phase currents are 90 degrees out of phase and the phase relationship determines the direction of rotation. If we apply the transfer function that we derived in the discussion on minimum current to the desired sine wave current for microstepping we see the effect of minimum current shown here in the orange and green. If the output of the DAC sets current near zero the circuit will respond with the minimum current. To get zero current we can disable the bridge and turn off all of the transistors. Without any drive the current will go to zero so we can get the zero points on our sine wave. Since we can get zero we only have to look at what effect the minimum current will have on the sine wave just before and just after the zero value. Luckily the first microstep after zero and the last one before zero is the largest step that we need to make so if the minimum current is less than the sine of the first microstep there should be no distortion in the sine wave. In the example the minimum current starts to affect the waveform at about 11 degrees so if the first microstep is more than 11 degrees there should be no distortion on the sine caused by the minimum current. In this case we could divide each quarter cycle into eight microsteps of 11.25 degrees each. These are the waveforms we saw earlier operating a stepper motor with one sixteenth microstepping. If you look closely near the zero current points on the current trace you can see a small amount of distortion that may be caused by the minimum current effect. Another anomaly that can affect microstepping is a result of the decay mode that is selected. Earlier we discussed the two different decay modes fast decay and slow decay. In the slow decay mode during the off time the current is recirculating around a path that is one on transistor and one diode or possibly one MOS conducting in the reverse direction. During this time the current decays rather slowly since the voltage across the coil is very small. Remember v equals l di over dt. In a microstepping application we are trying to produce a sine wave drive. However the slow decay rate may limit the ability to follow a fast changing waveform that we have on the downward slope of the sine curve. The green and orange traces represent the current waveform when the decay rate is limited by the slow decay and the inductance of the motor. Since the entire voltage is applied across the motor when energizing the inductance the di dt can be relatively fast. In that case the current can follow the rising slope of the sine wave but the fall time is limited by di dt. This figure shows an actual waveform from operating the l6208 in the slow decay mode using the practice spin system. The di over dt limit of the low decay is limiting the ability to follow the trailing edges of the sine wave. The current waveform looks much better if we change to fast decay. Since the voltage across the coil is larger the rate of change will be greater and you can now follow the desired current waveform. We do see an increase in the ripple current as we expect when changing to fast decay. Of course if the sine wave is slow enough it is possible to follow it well even with slow decay. Ideally we would like the motor to start at full speed and stop on command. However for most applications this is not possible. Think for a moment about how a brushed DC motor responds to an instantaneous step in the input voltage from zero to full voltage. It will naturally accelerate up to full speed and then run at full speed. We need to consider that the equivalent operation is for a stepper motor. For a stepper motor drive the designer must consider the speed torque performance of the motor and guarantee that the motor is always operating under the speed torque curve of the motor. If we exceed the available torque at a given speed the motor will stall and stop. This figure shows a typical speed torque curve that you might find for a stepper motor. Notice the downward slope at higher speeds. Although you might find this curve on a data sheet the real curve has some discontinuities. This is a more realistic speed torque curve. Notice that there are some speeds where the torque seems to drop to zero. This is due to the mechanical resonance points of the motor. A stepper is basically an underdamped machine. Each time it takes a step it overshoots and then settles into the final position. Depending on the damping in the load there may be some operating points that have a mechanical resonance that effectively drops the torque to zero at that speed. The designer must select operating points that are below the speed torque curve or the motor will lose steps and stall. A typical way of operating would be to select a line at around 75% on the torque curve and then be sure you operate on or below that line and did not operate on any of the mechanical resonant points. Obviously the designer must consider the desired operating speed and the available torque. In the diagram the green line may represent the desired operating speed. This may be dictated by a requirement to match a speed or to make a movement within a certain period of time. The available torque for our design point at that speed is shown on the vertical axis. However the torque required to start the motor moving may be much higher than that. The blue line represents the amount of torque needed to overcome the inertia and friction of the system to get the load moving. At this point the maximum speed is much less than the desired speed. Fortunately as the speed increases the load due to the inertia decreases and in most cases less torque is needed to keep the load moving than to accelerate or decelerate it. So as we get the motor moving less torque is typically needed and we can accelerate a bit faster. The simple solution is to create an acceleration and deceleration profile to start and stop the motor. For most applications this can be done with a simple linear ramp for acceleration and deceleration. The starting speed is set by the blue line in the previous slide and the maximum is set by the green line. The blue line in the slide shows a typical move speed profile. For each movement the step time is gradually reduced for each step starting from the time set to overcome the inertia of the load until the desired speed is achieved. The procedure is reversed to decelerate the motor gradually increasing the step time each step. Obviously the calculation for the move must subtract the number of steps it takes to accelerate and decelerate from the total number of steps to move to calculate the number of steps to run at a constant speed. For short moves the motor may not reach the full speed before it needs to start decelerating so the acceleration may have to be truncated as shown by the green line.  The discontinuities at the corners of this acceleration profile correspond to a change in the acceleration or jerk. In applications like moving jars of fluid the jerk may need to be reduced. This can be accomplished by rounding the corners at the top of the movement profile. In this session we have discussed the basics of stepper motor operation and the typical drive configurations for commonly available stepper motors. This block diagram shows a typical stepper motor drive system that implements the drive configuration we have discussed here. The three blocks needed to drive the stepper are the step time and phase generation which is typically done in a microcontroller, the PWM current control and the power bridge. Thank you for your attention. Please visit us at st.com to view the many motor control products and solutions available from ST. For more information please refer to www.st.com slash st motor control. Also you can watch the Power Spin E presentation. Thank you for your attention.


seeing this offense come along and just finding the consistency with them and how much does it have to do with, you know, Tana Hill and then obviously getting that run going? Well, Ryan's done a nice job, clearly, since he's been in there. But the whole offense, we try to make improvements from week to week, even going back to week one, you know, that game, to week to week, whether we won or lost, we just try to make improvements. You're seeing a lot of guys sort of get more comfortable and that's what you want as the season goes on. It's a long season, as we can all tell. I mean, it feels like three different lifetimes ago, you know, week one, but it says we hopefully just keep making progress. You know, like you're just hinting at when there is such a 180 from the two and four to where you are now, it's not just one guy. Right. What are some of the things you've seen maybe across the board that have gotten better since then? There's a lot of things. There's the, the online, I mean, we were shuffling guys in and out because of injuries or whatnot. And just at the tight end position, the receivers, I mean, everybody, they get comfortable. It's like any relationship. The more you're around somebody, the more familiar you are with them. You understand that communications is better. So we're just seeing hopefully continue this growth from week to week. And that's what we've been preaching all year. There's there's a lot of conversations that go go on in between John and drapes and the coaching staff. And it's different from player to player. But you know, I'd let those guys speak for that stuff. Okay. I won't come. I was a fan of him. I thought he was a tough football player that stood in the pocket and, you know, he'd gone through a gamut of injuries and different different systems as well. So but I don't always heard good things about what you thought. Are you seeing that week to week? Or you see more than it's hard to judge when you don't you're seeing some from afar and so you don't really know what they're being asked to do. You know, a lot of times you look at film. There's a lot of assumptions made by other coaches, I think, and I don't want to misquote them. But Bill Beljeck had a really good quote about that. You talk about arguably the greatest coach of all time saying when you're game planning for week to week, you have an idea of what somebody is being asked to do. But you don't know unless you're in those meeting rooms, you can see a similar play. And hey, here's how I teach it.  So they got to be teaching that way. So you don't know until you're in those meeting rooms with a guy and you work with them. But Ryan's done a great job since he's been here. And I can always speak for since Ryan's been with us. And he's done a nice job. How much is it confidence?  When you're on a streak like you are now, how much does confidence kind of feed on itself? Like, we're doing it again, we're going to do it, we've been doing it. Yeah, sure. There's from as you build this thing from week to week, you hope to grow past that stage of Oh, no, I mean, that's the you don't want that mindset at all.  It's not going to be perfect. And that's the beautiful part of this game. It's whether you have the mindset to be like, we're good, whatever they throw at us, like, obviously, you don't want those turnovers to happen or a penalty or a negative play.  We're like, good, here we go. Let's let's move on and then find out figure out what we can do to win this football game. So sure, it grows week to week. But you got to there's a new challenge. And this is gonna be a big challenge for us this Sunday with two games in three weeks against these guys. Do you keep things in the holster this week? Or do you do things that maybe you want to set up something for two weeks from now? Or you really got to put the blinders on it. You know, it's not not an NBA series. You know, when you're going best of seven or something like that, we all it matters is this Sunday, it really does because there's so many things that can happen from this game. And next, if you start doing that, then you may set yourself up for failure on this week. So we just try to focus on today. And then this week, like a lot of players, you know, he's his first year in the NFL. He's getting used to the pro game and what we're asking him to do. He's done a nice job. He just works out it day after day. And so hopefully he continues on that. So again, when he got here, there's always going to be a learning curve with all these guys. And so he's done a really nice job as a rookie. So hopefully he continues to do it. The fact that his big numbers in a few of the last few weeks, and also the snaps, pretty good signs that there's a building trust there for free with him. Yeah, absolutely. All those guys I got to trust all those guys. We put those guys out there, whether it's Khalif or Hollister, Corey, you know, Corey blasting game like during this thing, I got to trust in these guys.  And sometimes he's the primary and sometimes somebody else is. And he's done a nice job making play. How much more fun is it as a coach or maybe how much more juiced does it give you as a coach when things are working like they have of life compared to being in the season where you struck the score points and probably what a lot of my mind doesn't go that way. It's whether you got a fixed mindset, you got a growth mindset. There's ways to look at it. You look at something like it's a disaster. Oh, no, what was me? I'll never look at it like that. I look at it to try to fix a solution see if we can get better. So when certainly there's a comfort level and you're calling plays and things are working, but to look at something as a disaster or catastrophic event, I don't have that mindset. I really don't. How much is the office kind of adopted that just that kind of mindset that you're talking about? How have you seen that we just, you know, I can't speak for these other guys, but just as a whole, we just try to try to be consistent. And I think we all have as a coaching staff and as a players and they'll see through you if you know, you're trying to change week to week and you're trying to be a front runner.  We just try to be consistent and we just try to make improvements because this thing is we got a couple more weeks and we got to get better this week. And that's all we focused on.


We have Mr. Narang here. He's the founder of Omega Psyche Mobility. So Mr. Narang, you know, the flavor of auto exposure 2023 has been electric. So what are your views on that? Look, I think I'm really excited to be here. Thank you for coming and, you know, all the people out there need to know about electrification, not just electrification, but green energy and sustainability. So I'm excited. We looked at, we've been in this journey for nine years. When we first started, it was even one-tenth of what it is today. And what I see today is a new ecosystem being built. And this is what's going to change India. So again, it's really great to see so many participants, such a big ecosystem. And I think my vision of green energy sustainability across this country. Now, what I would like this to move to rural India, and that's only when we'll really, really get, you know, like I said to you earlier, only when we're involved in this journey, not just now, but again, it's the step in the right direction.


Good day. In this session, we will be providing you with an introductory overview of the AERSHIP project with a focus on our upcoming 2.0 release. My name is Andrew Karanja. I'm a principal system engineer with AT&T and a member of the AERSHIP community with a focus on design and requirements. And my name is Drew Walters. I'm a professional software engineer with AT&T working on their network cloud, as well as a member of the AERSHIP working committee. So let's jump right in. What is AERSHIP? AERSHIP is a collection of loosely coupled but interoperable open source tools that declaratively automate cloud provisioning. AERSHIP consumes a collection of YAML documents that define a site and turns them into a functioning cloud. This includes Kubernetes manifests, bare metal provisioning, network definitions, and more. AERSHIP orchestrates one simple and repeatable workflow for both deployments and updates. This is perhaps one of AERSHIP's strongest features. AERSHIP allows you to consistently and predictably deploy multiple sites substituting the specifics for that site in an automated fashion. The process for updating a site is effectively the same as the initial deployment. You feed AERSHIP a set of YAML documents and it performs the updates. AERSHIP does not require operators to develop their own set of complex orchestration tooling to automate AERSHIP. AERSHIP uses containers as the primary mechanism of delivery and takes full advantage of native Kubernetes resiliency, including health status, pod restarts, restarts, and so on. AERSHIP leverages native Kubernetes security features like RBAC and roll binding. With AERSHIP 2.0, AERSHIP also provides integration with DEX for external authentication and provides tools for secret encryption, decryption, and rotation. While AERSHIP provides out-of-the-box templates that aid in defining a site, it's incredibly flexible and allows operators to deploy any additional software that's required and also supports customizing site definitions as needed. Next, we'll dive into a little history of how AERSHIP got started and where it's headed in the not so distant future. In 2016, the OpenStack Helm project was initiated. Why is this significant? While it's a separate project from AERSHIP that can be considered a companion project, it was the first step in the journey towards being able to deploy and manage all software and hardware in a site via Helm charts. In 2017, the yet-to-be-named AERSHIP project was initiated in collaboration with SKT, Intel, and AT&T. AERSHIP formally launched as an OSF pilot project in 2018 at the Vancouver Summit, and the first release candidate was released in Berlin later that year. The AERSHIP 1.0 GA release was announced at Denver in 2019. In October of 2019, AERSHIP was confirmed as an official OSF project, and today, AERSHIP 1.0 is successfully running 5G workloads in production at AT&T. We did not stop there. Building on the foundation of 1.0, the community has been designing and coding the next generation of AERSHIP. The Alpha version of AERSHIP 2 was released in May of 2020 with beta releasing at the end of last month in September. We are shooting for a general release of version 2.0 at the end of this year or in early 2021. While AERSHIP 1.0 is successfully running workloads in production, we've learned a lot along the way in taking those learnings into consideration when designing AERSHIP 2.0. One big takeaway from 1.0 was the complexity and challenges of updating the AERSHIP components themselves. AERSHIP 2.0 solves for this by introducing the notion of an ephemeral under-cloud control plane, or EUCP. The EUCP is a control plane that is 100% transient. It only exists to run when necessary and removes the need for long-running local components beyond the basic infrastructure. The lack of a local EUCP improves the security posture by reducing the attack surface area of the infrastructure and also by reducing the complexity of the components that need RBAC protecting. When AERSHIP was initially conceived, we created several custom solutions for site provisioning and software management. In the time since AERSHIP 1.0, many best-in-class open-source projects like QBADM, customized cluster API, and helm operator have reached maturity. By leveraging these projects in AERSHIP 2.0, we're able to greatly reduce our development overhead and technical debt. A new AERSHIP component, AERSHIP CTL, provides a consistent interface for these other components and introduces additional features to easily manage the deployment process. A benefit from this approach is the fact that AERSHIP will support a wide array of deployment use cases, including BYO infrastructure, third-party public clouds, virtual machines, and bare metal. This is achieved by utilizing cluster API and its supporting components. Another goal of AERSHIP 2.0 is to reduce the amount of downstream customization of manifests. AERSHIP will provide out-of-the-box type and site templates through Trezermap. Leveraging customized and various replacement catalogs, AERSHIP 2.0 will improve the substitution of site-specific values in a more real-time and automated fashion. This is an improvement over 1.0, where operators were required to download the entire contents of Trezermap, then fork and modify them locally. While we're on the topic of documents, a lesson we learned in AERSHIP 1.0 was that expressing a site as a complete set of document declarations was challenging to manage and mentally digest. In AERSHIP 2.0, we represent lifecycle management as a series of phases that simplify how a Kubernetes cluster is built and subsequently managed. Phases help people deal with a much smaller document set that are granularly scoped to particular objectives. AERSHIP in a pod improves the onboarding experience. It provides a single containerized execution environment, which can be used for CITD, demos, and development purposes. AERSHIP 2.0 also introduces the AERSHIP UI, which will allow operators to visualize and manage document sets, integrate various tooling dashboards, and will integrate with the AERSHIP CTL command line for execution purposes. And on one last note, in early testing with 2.0, we've seen significant improvements in the deployment times that will be compared to AERSHIP 1.0. There are a number of components that make AERSHIP 2.0 possible. At the top, you'll notice we have AERSHIP CTL and AERSHIP UI, two tools that are at the forefront of integrating and orchestrating open infrastructure in AERSHIP 2.0. We took these tools and designed them from the ground up with operators in mind to allow them to easily orchestrate deployments and visualize their infrastructure. These two tools drive the rest of the ones you see on the screen, like the image builder. The image builder is AERSHIP's way of supporting declarative intent for the lifecycle of bare metal hosts. And it does so by producing a reusable ISO or Q-COW image that can be used to deploy hosts for the first time or redeploy them. What this means in practice is that bare metal host upgrades in AERSHIP 2.0 are predictable and efficient, customized. We took customized, which is a widely used tool in the Kubernetes community for customizing YAML documents. And then we developed a model on top of that that allows for deduplicating and representing declarative software intent. AERSHIP CTL understands that model and allows operators to quickly preview and then apply rendered documents. QVADM, Cluster API, Metal 3 with Ironic, and the Flux Helm operator all make managing the lifecycle of AERSHIP 2.0 simple. AERSHIP CTL drives these tools to facilitate bare metal cloud provisioning, make the lifecycle management of Kubernetes easier, and make the lifecycle management of your software easier, all while supporting the tools native document sets. The host config operator is AERSHIP's day 2 host management answer. It allows you to configure things on your host after a site's been deployed without actually the redeploying host using a new image. This can include things like permissions configurations, host package management, or even just executing arbitrary scripts. That and much more is supported by the host config operator. And finally, you'll see TreasureMap. TreasureMap is still an integral part of AERSHIP, even in AERSHIP 2.0. But rather than being a library that's forked and modified as Andrew mentioned earlier, TreasureMap provides a robust set of functions and templates in AERSHIP 2.0. And as an operator, you can inherit for your deployment needs and build on top of. The AERSHIP community strives to keep our project open source, our design transparent, and our community as well as our development process open to all. Here are some changes that we've made over the last few years. We've evaluated the frequency and scope of our community meetings. This includes the IRC meeting, which was recently moved from a weekly meeting to a bi-weekly meeting. This has allowed us to keep our agendas more focused and also get more participants as the meetings don't happen as often. We've established a publicly accessible Slack channel for working in technical committee discussion. Just by joining the Slack channel, members of the community can be a part of the planning process, which typically used to happen over email. We've expanded the purpose and scope of the AERSHIP flight plan meeting. Every Wednesday, the AERSHIP flight plan meeting plans for upcoming milestones by reviewing issues that have been submitted on GitHub to the various projects and then prioritizing them for developers to work on. Now, with the expanded scope, we've been able to include release planning and release tagging. We've also adopted additional collaboration platforms used by Kubernetes, things like GitHub issues that have allowed us to work closer with those projects. You'll notice, though, that we're still using the best in class open-dev tooling, including Garrett and Dool. Thanks for your interest in AERSHIP. We sincerely hope that if you have questions, you will join us in our mailing list. Or we also invite you to our AERSHIP IRC channel, which is hashtag AERSHIP and on free note. And of course, our Slack workspace, AERSHIP.org slash Slack. There you'll find more members of the community who are happy to answer any questions that you have and look at specific use cases. Thank you.


Hello boys and girls, we got a Maserati today. This is the Quatro Porte 2010 Quatro for four and I guess Porte means door, so a four-door Maserati Great name Sounds good So I did rear brakes another while ago to this car and the spark plugs Cleaned the throttle body. It had a check engine light was running rough That actually fixed it just doing spark plugs and cleaning the throttle body had a issue with the locks no not like the wind drivers window and Little things here and there didn't really bother to do any videos on it, but what got me Today the reason why I'm doing this video is because whoever was doing brakes on this car. I Think it was over a year ago or so. This car sits a lot. Keep that in mind so I was doing the rear brakes and You're not gonna believe it well now you are because I just took the front brakes apart But the guy came to me with a grinding noise from the rear and as you can hopefully see these rotors are Brand new as well as the brake pads Now what happened was you know when somebody comes to me and with the brake problem You know and the car has rims You can see right through the rim and you can look at the outside pads and see how much they're they're worn Right, so that's what I did. There was a lot of pad left at least 70% on the outside at least but got on the rack, you know looked on the inside pad and I Could see that the rotor is eaten. It's notes. It's so it's metal on metal action, right? so started taking everything apart and Well, if this was a reaction video Then it would be at first would be like What? Then it would be like Really and then it would be like what tough The inside pad was installed The other way around but that's not it So fix the rear The guy didn't have parts. I was I was supposed to do parking brakes This is a it's got drum brakes and the rotors are drums inside as well So that the parking brakes are inside the rotor so I would have to take it all apart so I put it back together parked it outside and As I was backing it out. I heard more grinding from the front this time But then I thought maybe I looked at the outside rotors. They were rusty. I thought maybe okay It's just from sitting and the rotors are just nasty outside on the outside at least I didn't bother to look on the inside I was in a hurry like I said the guy didn't have enough parts I knew I was gonna bring it in again, but heard the grind parked it whatever Now just just now out of curiosity, you know, I got nothing to do. I put it back on the rack and You know, I'll just show you do you see what I see Alright, so this pad right here is in backwards Yes, so I called the guy and ask him what's going on who did this, you know, so he tells me a little story He did breaks out on the parking lot somewhere whatever for really cheap, you know the guy trying to save money You know, he's got a Maserati. He's trying to save money so the guy comes in he does his front pads whatever from bake pads and And the brakes start squeaking six months later So the guy comes back and regresses the pads and that's probably where When he does this this inner pad is in backwards Look at this rotor. It is eaten away Outside, I mean these these need to be replaced anyways, but How do you do this?  Right? So this is the right way Wrong way right way Wrong way, how do you I mean, how do you make this kind of mistake? You know, and then who's really at fault? What kind of a mechanic was this guy that was working on this car and If you own the Maserati, why are you trying to save money for on your brakes? Have someone do it on the parking lot. These are actually very easy to replace these these bramble Calipers all you do is if you want to just do pads, then you just remove these pins There is no clips or anything like this Little tiny pins over here You have to just knock these out knock one out pull this out then knock out the other Then this pad these pads will slide out before that you can you can put a flat screwdriver in in between the Pad and the rotor and try to press in the pistons You got two on each side. Then if you're gonna replace the rotor, what you got to do is take these these are Ellen I'm guessing 12 maybe I'm guessing right now These two and this whole thing comes out and obviously this little guy here and this whole rotor Will come off and what the hell is this and this not to mention. I mean Seriously, okay guys, that's it for this one. See you soon