V-22 Osprey Project - Tuning and Setup

-

ESC SETUP

I used two Castle Creations Talon 60 ESCs for the V-22 Osprey.  These ESCs are high-quality with an electronic governer designed for RC helicopters.  Other ESCs with this feature are recommended.  Using the CastleLink software and USB dongle, I set the following RPM parameters:

Throttle Setting 2-blade 3-blade
20% 2600 2000
70% 2600 2200
100% 2800 2400

As with any standard airplane or heli it's important to calibrate the ESC endpoints as well.


TILT SERVO SETUP

The HiTec D85MG servos are digital high-torque metal-gear servos that are programmable.  Using the HiTec programmer, I set the 1000us endpoint to the forward flight (0 degree) position and the 2000us endpoint to the hover (90 degree) position, with the 1500us center point in the middle (45 degrees).  The programming of the servo is a bit challenging, as the endpoints set in the programmer coordinate roughly to 900us and 2100us.  It takes a bit of fiddling to get the 1000 and 2000us endpoints spot on.  I used an digital angle meter to set these positions on each wing rotor.


HELICOPTER SWASHPLATE

As with any standard helicopter, it's important that the swashplate be level when the servos are at their neutral position.  There are many tutorials on how to do this, so I won't go into this procedure here.  In addition, the blade pitch must also be set.  This takes quite a bit of back and forth tuning between the radio pitch curve settings, the dRehmFlight VTOL flight controller, and a digital angle meter.  For the full-size Osprey, the rotor blades are curved and have a 45-degree incidence at the root.  I am still using symmetrical "3D" blades that are common with sport RC helicopters.  There are curved, scale versions available, but that's for a later time.  I setup a single pitch curve with the following parameters.  As further testing proceeds, I may alter this depending on forward flight performance.

Pitch Curve Blade Pitch
-100 (1000us) -3 degrees
0 (1500us) 8 degrees
100 (2000us) 20 degrees

It's important that the mechanical linkages be as close as possible so that servo response is balanced across the rotor heads.


FLYING CONTROL SURFACES

As with any airplane, it's important to center the control surfaces.  The settings in dRehmFlight VTOL allow a trim setting to center the servo in forward flight as well as a flaps position when in hover.  With the controller in FF mode, set the parameters so the ailerons are centered along the wing.  Then switch to hover mode and set the parameters so that the flaperons are both extended down the maximum possible while being equal.  You can use a ruler to measure the deflection to ensure they are as close to the same as possible. 

For the elevator, perform the same process with the flight controller trim value to center the elevator and ensure equal throws to each side.



Comments

Post a Comment

Popular posts from this blog

V-22 Osprey Project - Design Changes for v3

-
Image
It's been a busy end of 2021, and as we start 2022 I'm getting closer to building version 3 of the Osprey wing.  The single biggest problem I've faced is the amount of backlash in the direct spur gear drive of the tilt mechanism.  It introduces some nasty instability that, left unchecked, would likely destroy the model in flight. I've investigated other tilt mechanisms, but the one I keep coming back to is the rack and pinion design that Tom Mast uses in his model at Rotormast.  His design uses a high-torque digital servo with a small pinion gear driving a rack attached to the rotor nacelle.  The servo has been modified with an external potentiometer that's driven by a gear on the translation tube to give positional feedback to the servo.  I like this design a lot because 1) It works, and his model is proof, and 2) it requires less torque from the servo and has less backlash. I ordered the pair of modified servos, potentiometer, and rack from Tom's site and star...
Read more

Whereabouts Clock Update

-
Image
After a few months, Life360 has gone the way of Apple and locked down the API I used to get location data from the phones.  This is disappointing, but inevitable. I found on a forum for Home Assistant that the app OwnTracks might be a suitable alternative. It's a neat little app that will trigger the phone to send its location data via MQTT to a server that you specify. I had to rework the code a bit, but the new operation is as follows: OwnTracks on the phone will push location data per its configuration to the MQTT server (Docker container) The Mosquitto (MQTT Broker) container will receive the data and forward the data to its subscribers The MQTTWarn container is a subscriber and translates the received data and adds it to the MariaDB database The Apache web server hosts a Python CGI script that is checked each minute by the Arduino microcontroller.  If the data has changed, the hands are moved to the new location. The only exposed port to the Internet is TCP 1883 for...
Read more

Whereabouts Clock: New Clock Mechanism

-
Image
 When I made the first mechanism of the Whereabouts Clock I utilized sail winch servos to get a motion that was at least 360 degrees.  Most RC servos are limited to about 180 degrees before they hit a physical limit.  I always wanted to create a clock with motors that weren't limited in the number of rotations, such as a stepper motor. However, stepper motors don't retain positional accuracy after a power loss.  The motor drivers only know "left" or "right" and a number of steps.  If the motor is moved, or power is lost, it has no idea where the motors are any longer.  In most control systems using stepper motors there are limit switches that are triggered to "home" the motors to a known position. Also, the Arduino Uno is limited in the number of IO pins.  Most stepper motor control requires at least 4 pins and additional lines for motor enable, micro switches for positioning, etc. A while back I purchased an Arduino Mega and a six-pack of 28BYJ48 ...
Read more