

Why is it important to drive the rear motor now?
We've not closed the car. We've not connected the front motors. Why are we driving the car at this stage?
- #797
- 23 Feb 2018
We've not closed the car. We've not connected the front motors. Why are we driving the car at this stage?
In this tutorial, we would look at how to connect the front motor of the car to the L298N motor driver. The driver is already connected to the Raspberry Pi or if it is still not connected you should connect it now.
The phone app could do it. The cables are connected. It is time to test if everything works.
The driver is pretty large (compared to other drivers that we could have used). So we should plan on how to position it on the car, where exactly and how to keep it there. Glue might be one solution
We are about to connect the whole car with the lights and motors to the controller. Let's recap to know what is ahead of us, what would the process be and what is the end result of the next couple of sections when at the end we have a car controlled by the phone
While disconnecting the cables it is difficult to get lost. The students just disconnect cables. But when they are connecting them at the end they must have them working. It is easy for them and the whole group to get lost. It has happened a few times. Here are a few things of what you could do if you get lost and something is not working.
Appart from the Inputs there is also one more connection that we must do to have the motor driver properly connected to the controller.
Sometimes, like a lot of times, generally quite often, the SD card will be corrupted in our current setup and you will have to burn the SD Image again on the SD card. It is very important to remove one of the jumpers of the Motor Driver to avoid this.
The car is not moving. The Motor Driver is hot. Here is what to check and how to resolve this.