I'm asking, will it be better using a MCU?Well if you can make it work without an MCU (micro controller). Then it seems obvious to me and anyone else with a brain, That it's not necessary to use an MCU.
I don't mean to be patronising but your question makes no sense.
a mcu wont do a thing, it dosnt matter what pins you connect it will sit there like a brick.
to explain
a MICRO CONTROLLER (mcu) has to be told what you want it to do by programming it, you cant just buy one stick it in and off you go, for your project you would need to program the chip to do exactly what you want, or get someone to do it for you. would it be worth it????? HMMmmmmmmm i am micro obsessed so i am biased but i would say it's a great project for a micro and you could get it to do all kinds of thingseven down to putting a ultra sonic TX/RX in it so if the copter starts to descend too fast the micro will apply power for a softer landing, actually you could program a beginners mode so the micro helps fly it if you added a accelerometer! so yes on one hand a micro would be great but you dont have to use one
My main problem is that I need to know if:
1. It's possible to connect the receiver to MCU? If so how?
2. What do all the pins on MCU do?
And of course advice on this project
Thank you Sharkbite for the additional information. Your comments are quite useful toward understanding what you want to do.
First, you mention propellers (plural). Are you referring to just the front and rear rotors of a typical helicopter, or does your helicopter have more than one main rotor, such as a quadracopter?
Second, yes, the receiver can be connected to the MCU. In fact, I doubt very much that you want to connect the MCU directly to the RF side. The output from the receiver is a typical pulse-width servo control signal on each channel. (I am assuming your transmitter does not have servo mixing built in.) So, each stick movement will control a single channel. The outputs have 3 wires, one is for ground (usually brown or black), one is for V+ (usually red and almost always the center wire), and one is for signal (usually yellow, orange, or white). From hereon, when I say "connect," I am referring to the signal wire only. Your MCU will, of course, have to share a common ground with the receiver. Those outputs could be combined to a single, serial input to the MCU, but an easier way to begin with might be to connect each signal wire from the receiver (i.e., 4 wires) to a separate pin on the MCU.
The MCU will need to be programmed to adjust its outputs to the mode (car or flight) that it detects. You will need at least 4 pins on the MCU for outputs. I suggest you make a flow chart to help get started. So long as you use 4.8 V (nominal) for the receiver power supply, you will not need any voltage translation between the receiver and MCU.
John
Thanks on your opinion audioguru. I have realized that there is 2.4ghz remote, unfortunately it's a little too expensive for me. It's about 80USD in my place. Furthermore, I'm new to building robots. All I've done is mostly research. I read about micro controllers, servos, ESC's, etcetera...You have an old-fashioned radio system. It operates on a single channel that is at 40.685MHz. Its antenna is long and if anybody else uses that same channel then both of your helicopters will have interference and will crash.
Modern radio control operates at around 2.4GHz. The antennas are very short and there are at least 40 channels that are automatically selected for no interference.
To avoid additional interference, when a model is first used its receiver is "bound" to the transmitter and using a unique "Global Identity" so that only your transmitter will activate the receiver and no other transmitter can even if it uses the same channel.
Of course digital proportional control is used for very fine adjustments of the model.
Most of my RC airplane and helicopter models use 3 gyroscopes to keep them level if wind gusts try to flip them over. Their flights are very stable but acrobats are not affected.
Thanks john, just a simple doubt, does the mc need ac or dc current? What type of mc is easy to program?Thank you Sharkbite for the additional information. Your comments are quite useful toward understanding what you want to do.
First, you mention propellers (plural). Are you referring to just the front and rear rotors of a typical helicopter, or does your helicopter have more than one main rotor, such as a quadracopter?
Second, yes, the receiver can be connected to the MCU. In fact, I doubt very much that you want to connect the MCU directly to the RF side. The output from the receiver is a typical pulse-width servo control signal on each channel. (I am assuming your transmitter does not have servo mixing built in.) So, each stick movement will control a single channel. The outputs have 3 wires, one is for ground (usually brown or black), one is for V+ (usually red and almost always the center wire), and one is for signal (usually yellow, orange, or white). From hereon, when I say "connect," I am referring to the signal wire only. Your MCU will, of course, have to share a common ground with the receiver. Those outputs could be combined to a single, serial input to the MCU, but an easier way to begin with might be to connect each signal wire from the receiver (i.e., 4 wires) to a separate pin on the MCU.
The MCU will need to be programmed to adjust its outputs to the mode (car or flight) that it detects. You will need at least 4 pins on the MCU for outputs. I suggest you make a flow chart to help get started. So long as you use 4.8 V (nominal) for the receiver power supply, you will not need any voltage translation between the receiver and MCU.
John
Does your club use 40.685MHz that Google says is used only in Europe for surface models?As for using 40 MHz instead of 2.4GHz, I would disagree with AG. About half of our club still uses the "older" American frequency of 72 MHz. It makes no difference in how the airplane flies.
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?