Aura Troubleshooting

From Flex Innovations Wiki
Jump to: navigation, search

Aura AFCS Troubleshooting


If you cannot find the answer to your issue, make sure to review the Aura FAQ, manuals, and videos.

Make sure to remove the Propeller and/or safe the engine before making changes to Aura!

Transmitter/Receiver Setup

Issue: I am using a DSM2/DSMX Remote Receiver and it will not bind

The Remote Receiver LED Light is the best diagnostic tool. With the transmitter powered on, the Remote Receiver Link Light (Orange LED) is solid if you are linked/bound. If not, the remote receiver is not bound correctly. Most binding issues result from trying to bind a DSM2 Remote Receiver as a DSMX Remote Receiver.

  1. Make sure your transmitter, receiver and Aura are powered off.
  2. Setup Aura to start the Remote Receiver binding process:
    • For a DSMX Remote, put a bind plug in Aura Port S8
    • For a DSM2 Remote, put a bind plug in Aura Port S1 and S8
  3. Power the remote receiver.
    • Remote receivers are powered by powering the Aura via Battery or USB.
    • Confirm bind mode by observing a fast blinking LED on the remote receiver.
    NOTE: there are some 'Hidden X' remotes out there. They are a DSMX remote in DSM2 packing/labels and were shipped with certain DX8 transmitters and AR8000 receivers. If your DSM2 labeled remote does not enter bind mode with the bind plugs in S1 & S8, try S8 only. If it works, it is actually a DSMX remote (hidden X), and you should label and use it as such.
  4. Binding
    • With the Remote Receiver LED flashing quickly, power on your transmitter in 'BIND' mode per the Transmitter instructions.
    • Binding is complete when the transmitter confirms it and the Remote Receiver LED goes solid orange.
    NOTE: Some SPM systems are picky, and like to be bound at different Tx/Rx distances.... try 2 feet, 6 feet, 10 feet of separation.
  5. After the Remote Receiver Link Light is solid, the transmitter and Remote Receiver are bound. Remove the bind plug to prevent starting the Bind process upon the next Aura power cycle.

Issue: During initial setup, I do not have transmitter control of the aircraft.

  • Make sure the correct wiring connections are made from Aura to your receiver and servos.
  • Make sure Transmitter is ON and Receiver and Aura have Power. Correct as needed.
  • Make sure there are NO bind plugs installed in Aura or Receiver.
  • Make sure your Transmitter and Receiver/Remote Receiver are bound and have the correct LEDs. Consult Radio manufacturer's binding instructions (and Aura binding instructions for DSM2/DSMX Remote Reciever as shown above).
NOTE: Some DSM2/DSMX Rx's will 'Link' even if the transmitter has been bound to a different DSM2/DSMX Rx with a different protocol. If you have trouble with a DSM Reciever, perform a fresh bind. Do not fly multiple models from the same 'Tx model memory', as this will increase the chance of this serious issue.
  • Make sure the Aura has a solid Orange LED light. This indicates the Aura has power and the sensor is calibrated.
    • If the Orange Aura LED is blinking, excessive motion was detected at power-up. It is best to cycle power and keep the Aura still during power-up.
    • If the Orange Aura LED is off, check power supply and power connection polarities. Contact support if the problem persists.
  • Make sure Aura also has a solid Green LED light. This indicates a valid radio signal from the Receiver.
    • If the Green Aura LED is not on, the Aura is not receiving a valid signal or is configured incorrectly.
  • If NO Solid Green LED:
    • If using radio Auto-Detect, make sure your radio has a Supported Digital data feed. (The retail Aura 8 supports Spektrum brand DSM2/X Remote Recievers, Spektrum SRXL capable Receivers, Futaba S.Bus/2, Graupner SumD of 8, JR X.Bus Mode B, Jeti Standard UDI12*). Make sure your radio is configured to provide the data.
      • Spektrum and Futaba digital feed capable equipment typically has the feed 'always on'.
      • JR, Graupner, and Jeti typically require special settings (and potentially correct firmware versions). Consult your radio manuals or support.
      • Note: If Auto-detect is enabled, a 'sweeping back and forth' display of Aura's 4 LED's indicates it is searching for a valid signal, and if it persists, it cannot find one. Check the items in this section and provide a proper signal, or use the Aura Config Tool to manually select one if yours is not supported by Auto-Detect.
    • If NOT using radio Auto-Detect, make sure you have configured Aura to read the correct Data feed/type. See the Setup Tab in the Aura Config Tool PC Application. Make sure your radio is configured to provide the data.
      • Spektrum and Futaba digital feed equipment typically has the feed always on.
      • JR, Graupner, and Jeti typically require special settings (and potentially correct firmware versions). Consult your radio manuals or support.
    • Double check that you have the data feed cable connected to the CORRECT PORT and correct polarity. Receiver labeling can be confusing, study it closely and consult the equipment's instructions.
    • Check if Aura has a solid Blue LED light. Blue On is a Failsafe indication. Check Rx/Tx Bind/Re-Bind. Check/Replace cable connecting Aura to Rx/Remote Rx.
    • If using 4 PWM (servo leads) Check the following:
      • Make sure your Rx is Linked (or Bound) to your Tx, and each Rx port needed can drive a normal servo.
      • Make sure ALL of the expected inputs are present. (Typically 4, Receiver Ail, Ele, Rud, CH5 -to- Aura S1, S2, S3, S4). Connection WILL NOT be recognized unless all expected are present.
      • Make sure the polarity is correct. Signal to Signal. Ground to Ground
      • Make sure the settings are correct in the Aura Config Tool (Brand -> PWM -> Servo Ports)
      • Make sure you are Connected, and are Writing your settings to Aura and can Read the same settings back from Aura.
      • Check for correct Aura Power and Sensor (Solid Orange LED) and Valid Radio Source (Solid Green LED)

Issue: I have control, but the sticks are moving the wrong control surfaces.

  • Check that the servos are connected to the correct Aura Ports (S1-S8). You can double check the assignments in the Aura Config Tool -> Servo Ports tab.
  • For Digital Receiver Connections, this is typically caused by having a "non-default" Wing or Tail Type selected in the transmitter. Use a FRESHLY RESET model memory in your transmitter, or reset your wing and tail types to the default type (single Aileron, single Elevator, single Rudder)
  • For more advanced radios, use your monitor to compare your 'channel order' to a blank freshly reset model memory. Make sure the channels are in the same slot/order. Make sure you have not used channel assignments to change from the 'default' on the channels Aura is using, including, but not limited to: Aileron, Elevator, Rudder, and often Ch5/Gear for flight mode, and Ch8/Aux3 for master gain.
  • For PWM Links, check the order of the male to male PWM cables and make sure they are connected to the correct ports at each end.

Issue: I am passing the Transmitter Command Test, but Failing the Aircraft Movement/Sensor Test, or vice-versa.

This is typically caused by: Wrong Sensor Orientation or use of Transmitter Servo Reversing:

  • Check the sensor orientation is correct in the Aura Config Tool. Verify Aura Config Tool -> Setup tab -> Orientation setting matches the Orientation of the Aura in the aircraft. Correct as needed.
  • Check if a transmitter servo reversing setting on Aileron, Elevator, or Rudder, is set to a non-default (reversed) setting. Correct it by setting the transmitter reversing to default/normal, and then use the the "Aura Config Tool-> Servo Ports Tab -> DIRECTION" setting for each affected servo to correct the transmitter command response. Re-run the Transmitter Command and Aircraft Movement (Sensor) checks and pass before attempting flight.

For supported radios, if the Orientation is correct, and the transmitter Reversing for Aileron, Elevator, and Rudder are all set to normal, it is expected to pass the tests (after setting Direction in the Servo Ports tab in the Aura Config Tool).

For radios not specifically supported showing this condition. Reverse the direction for servo reversing on the affected axis (ex. Aileron) in the transmitter, then use the Aura Config Tool -> Servo Port Tab -> Direction setting to make the affected servos respond to the transmitter correctly. Re-run the Transmitter and Sensor checks and pass before attempting flight.

Issue: I am trying to run the Sensor/Aircraft Movement test, but the surfaces don't move, or the movement is too small to verify.

  • Make sure your Flight Mode Switch (Ch5/Gear channel or other channel if it was changed from default) is in the highest gain-gyro active Flight Mode position.
  • Make sure your Master Gain dial (if enabled) is set high (sweep the gain control to different positions and test to verify it is not Reversed.)
  • Use your transmitters 'Monitor/Servo' screen to confirm that the Flight Mode switch is enabled and changing the assigned channel's data correctly as expected. Also check that the Master Gain channel data is moving with the assigned dial (if enabled). Correct as needed.
  • Power on your Tx/Rx/Aura and connect the USB Cable to your Aura and PC. Launch the Aura Config Tool and Connect to your Aura. Go to the Flight Mode Tab in the App. At the top right, toggle the Live Data slider to ON. Move the assigned Flight Mode switch on your transmitter. the Flight Mode screen in the App should change to track the transmitter's Flight Mode switch position (if it does not, check the items above). Set the Flight Mode switch to the position that shows the highest Rate Gain in the Primary Control Mode box on the Flight Mode Tab.
  • Check again for correct control movement and direction.
  • If you have a MASTER GAIN enabled, sweep it and test. Make sure it is Temporarily set to the highest gain setting for the test.
    • If the control surface movement is very small, your gain may be very low.
    • You may want to go to the Control Mode Tab in the app, select the control mode assigned to the flight mode showing the highest gain (ex. Control Mode D or C) (same one reviewed above), and Temporarily adjust the gain on the needed axis to a much higher number in order to make the check more obvious. Then return to previous value.
      • Note 1: The control response is seen WHILE the model is rotating at a rate around an axis.
      • Note 2: Remember that you must Write All to Aura for App changes to take affect.
Tip: "Save As" the model data file to the PC from time to time while changing a portion of the file name (ex. v1, v2, v3). This will allow you to go back to a previous version if you make a mistake, and also let you know which is the most recent file.
There is a Aura Config Tool enabled feature that provides clear feedback to aircraft motion. Connect Aura to the PC with Aura Config Tool Running, and select Quick Actions->Quick Sensor Check and perform the transmitter and sensor test with this enabled. Be sure to cycle the power off and on BEFORE ATTEMPTING FLIGHT.

Flight Performance

Issue: The model Oscillates on one or more axis in flight as the speed gets higher.

  • Reduce speed and switch to a Flight/Control Mode with lower or no gain. Reduce Master Gain if enabled.
  • This is an indication the programmed gain is too high. Reduce the gain on the affected control mode and axis using the Aura Config Tool or by reducing the Master Gain (if enabled).

Issue: My control surfaces move (or 'change trim') when changing Flight Modes

The most common cause of this is the presence of 'non-zero' values in the Subtrim or Trim systems of the transmitter. This 'offset' from stick center will be 'scaled' by Aura when changing an Aura flight mode Dual Rate, and the surfaces will move. The solution is to use the 'Quick Trim' feature (via bind plug in Aura Port S3 -or- via Aura Config Tool->Quick Actions->Quick Trim) to transfer these offsets into Aura, or to apply the offsets manually, either by using the Aura Config Tools Subtrim feature, or by adjusting the linkages manually to remove the transmitter Subtrim/Trim.

It is also possible that the transmitter may not be properly calibrated and sending the wrong data at stick center. Presently the only solution (other than calibrating the Tx correctly) is to use the Live Data in the Aura Config Tool -> Setup -Aura Input Monitor and change the sub-trim inside the Tx to Zero out the Flight Control Stick values at Stick Center.

Issue: I used Quick Trim then used the Config Tool again, and my trim changes are lost.

The Quick Trim features stores the trim changes inside Aura in the 'Sub-trim' memory. These are NOT saved to the Aura Config Tool's PC File automatically. After performing a Quick Trim on your Aura, you must first read from the Aura in the Aura Config Tool then save the settings on to a .acf file your PC. Further editing/changes can then me made on the Config Tool and Saved, and Written to Aura.

Aura Wiki Main