Wireless Remote Control

Embed Size (px)

Citation preview

  • 7/28/2019 Wireless Remote Control

    1/7

    Wireless Remote Motor Controller

    ECE 445

    Project Proposal

    Wednesday, February 8th, 2005

    Team Members:Joseph Owusu

    Sara ShahzadMasakatsu Suzuki

    TA: Scott Anderson

    https://courses.ece.uiuc.edu/ece445/cgi-bin/view_project.pl?spring2005_41https://courses.ece.uiuc.edu/ece445/cgi-bin/view_project.pl?spring2005_41
  • 7/28/2019 Wireless Remote Control

    2/7

    I. Introduction

    A. Overview

    We found this project idea and a couple of others on the ECE Power Webpage that

    immediately draw our interest. We decided to go with this project in specific because ofits remote control capabilities, which we figured will be fun to do and also expose us tothe RF field of electrical engineering, which none of us really have worked with before,and thought it would be a good learning opportunity. All of the team members have apower background and therefore, are pretty conversant with the motor controller part.Adding the remote control capability is going to be our biggest challenge, and will pushus out of our comfort zone, thereby helping us to learn more---this is all ECE 445 is aboutanyways. We also found a couple of motor controllers on the market, but they all camewithout remote control and pretty expensive as well. So we figured that if we cansuccessfully build this motor it could be very marketable at low-cost, and could be a goodbasis for a very efficient robot or maybe a wireless car.

    B. ObjectivesThe objective of this project is to design and build a wireless remote motor controllerwhich will come in handy for applications such as golf cart. The user will be able to dothe following operations: start, stop, accelerate and decelerate the motor, by pushing abutton or switch from a distance.

    Benefits

    Inexpensive

    Simple and efficient to use.

    Easy control.

    Features

    Allows adjustable speed control

    Motor will be able to run 150 W continuously, and 250 W for at least one

    minute.

    Requires less power ( power from 12V lead acid battery)

    Remote control capability

  • 7/28/2019 Wireless Remote Control

    3/7

    II. Design

    A. Block Diagram

    B. Block Descriptions:

    1) Power Supply: The power supply will be a 12 V lead acid battery. It will supply thepower to the converter circuit and the control circuit.

    2) User Inputs: The input will be simple buttons/switches that will allow a user toexecute the following operations: start, stop, accelerate, decelerate the motor, and alsopossibly change the motor direction. The input signal will be sent to the controlcircuit through the wireless interface.

    3) Wireless Interface: The interface will receive a signal from the user input and send itto the control circuit. The RF module will send the encoded signal from a transmitterto a receiver. The received signal will be decoded to appropriate signal, and it will befed into the control circuit.

    4) Control: The control circuit will determine the speed and the direction of the motor.One of the received signals received from user inputs will be a control reference. It

  • 7/28/2019 Wireless Remote Control

    4/7

    will be fed into the PWM circuit to generate an appropriate duty ratio that will be sentto the gate drive of the buck converter. The control circuit also will receive adirection/stop command from the user inputs. It will be fed into the H-Bridge circuitin order to allow the motor to stop or change its direction.

    5) H-Bridge: The H-Bridge circuit will enable the motor to choose the direction that itis supposing to be running in and also to come to a complete stop if that is what theuser instructed. H-Bridge circuit will receive signals from the control circuit for theuser defined action.

    6) Buck Converter: The buck converter, or step-down converter, is a switching dc-dcconverter that will produce output voltage lower than the source. It will have an inputvoltage of 12 V from the lead-acid battery and will be designed to output voltagefrom 0 V- 12 V. The output voltage will determine the duty ratio from the controlcircuit and this output voltage of the converter will be interfaced to the motor tocontrol its speed.

    7) Motor: A 12 V permanent magnet dc motor will be supplied by a user. It will beused up to continuous load at 150 W and 250 W for one minute.

    C. Performance Requirements

    Input voltage of 12 Vdc

    Output voltage ranging from 0 V to 12 Vdc, depending on the user specification.

    Motor loads ranging upto continuous 150 W or 250 W for a minute.

    Efficiency greater than 85%.

    Current ripple 5%.

    Voltage ripple less than 2%.

    Wireless control in distances in excess of 300 ft.

  • 7/28/2019 Wireless Remote Control

    5/7

    III. Verification

    A. Testing Procedures

    1) Buck ConverterThe converter performance will be tested with lab generated signal for various duty

    ratios. The testing will ensure that the performance requirement is met. The convertercircuit will be modified to meet the requirement.

    2) ControlA) The PWM circuit will be tested to ensure that it outputs appropriate PWM waveformsfor different control reference. After verifying the PWM waveforms, the converter willbe tested again with the PWM implementation.B) The H-Bridge circuit performance will be tested after it is implemented to the

    converter. It will be tested by observing how converter output responds with differentcontrol signal for the H-bridge circuit.

    3) Wireless InterfaceTo test the RF module, lab generated signal will be sent from receiver and the outputsignal will be observed on an oscilloscope. After ensuring that signal is transmittedsuccessfully, this step will be repeated by sending the encoded signal and observing thedecoded signal.

    4) User InputThe input device will be tested by ensuring that the device inputs generate appropriate

    signals to be sent to wireless interface.

    5) The systemAfter all of the subsystems are tested and verified, the entire system will be tested. Thesystem will be tested for verification of performance requirement. The system will bemodified accordingly.

    B. Tolerance Analysis

    The performance of the buck converter is very crucial for our design. The outputof the converter is suppose to get adjusted in accordance with the user input and hence

    control the speed of the motor. The converter should be tested such that the motor alwaysreceives appropriate amount of power. The efficiency of the converter is also expected tobe pretty high and the duty cycle and the switching frequencies will be vital testingparameters.

  • 7/28/2019 Wireless Remote Control

    6/7

    IV. Cost and schedule:

    A.Labor Costs:

    The formula for labor cost for each person is:

    Ideal hourly salary * actual hours spent * 2.5

    The ideal hourly salary is $30. We each spent 20 hours a week for 10weeks. That gives a

    total labor cost of $ 15,000.

    B.Part Costs:

    PARTS COST

    Transmitter/ Receiver $16.00

    Encoder/Decoder $8.00

    Microcontroller $8.00

    PWM chip $2.00

    Core $15.00

    H-bridge chip $8.00

    MOSFETS $6.00

    Resistors $5.00

    Capacitors $2.00Diodes $3.00

    Switches/Keypad $5.00

    Antenna/coaxial cable $10.00

    Wires $2.00

    Heat sink $15.00

    Total Part Cost $105

    Total cost = Labor Cost + Part Cost = $15,105

  • 7/28/2019 Wireless Remote Control

    7/7

    C. Schedule

    week Masa Joseph Sara2/6 Proposals, ordering

    of parts andassembly of RF

    modules.

    Proposals, orderingof parts andassembly of RF

    modules.

    Calculations anddesign of buckconverter

    2/13 Design of gatedrive and controlcircuits/Testing ofRF modules.

    Testing of RFmodules andPSPICE simulationof converter

    PSPICE simulationof conveter

    2/20 Design review Design review Design review

    2/27 Assembly of control/ PICprogramming

    Assembly ofcontrol/PICprogramming

    Assembly of buckconverter

    3/6 PIC programming PIC programming PIC programming

    3/13 Interfacing user input with RFmodule

    Interfacing userinput with RFmodule

    Interfacing userinput with RFmodule

    3/27 Mock-up Demos Mock-up Demos Mock-up Demos

    4/3 Putting allcomponentstogether

    Putting allcomponentstogether

    Putting allcomponentstogether

    4/10 Testing andtroubleshooting

    Testing andtroubleshooting

    Testing andtroubleshooting

    4/17 Testing andtroubleshooting

    Testing andtroubleshooting

    Testing andtroubleshooting

    4/24 Demo/presentation Demo/presentation Demo/presentation

    5/1 Final paper Final paper Final paper