Receiver Setup, nothing happens

Hey folks,

I originally posted my problem on the wall, but decided to create a discussion topic as a better way to keep the info organized.

Recap - Original Post

I got the Hexa-B kit, have assembled everything according to the manual.  I am at the "setup" step where I am to calibrate my tx/rx channels.

I have a JR 9303 2.4 radio system and am using a Spektrum 7100 receiver (JR and Spektrum are interchangeable as most know).

When my receiver is connected to the Arducopter, it just doesn't react at all.   I have tried when only connected to the USB power from the computer.   I have also tried with my Rx battery connected directly to my receiver (power from the Arducopter is also connected).    

The receiver light will not come on when connected with EITHER power scenario.

Reply from Chris - Use LiPo's for power, through the Power Module - Did this, Light is now on for my bound Rx, but nothing happens in the Radio Calibration screen **ie. Green bars for throttle, roll, yaw, etc...

Reply from Reto - My AR7100 receiver has some higher than standard power requirements.  I was wrong, I am using an AR7000, NOT the 7100, my bad.  **my 7100 is on my 550 sized Standard Heli**

So, here's where I am now:  

1.  Running all power through my LiPo and the Power Module connector.

2.  Receiver was successfully bound / binded to the radio, it is the Spektrum AR7000 and Receiver Light is "steady on".

3.  I have flashed to the latest ArduCopter version, 2.9.1

4.  Successfully "Connect" to the ArduCopter through the Mission Planner

5.  Cannot get any feedback from the "Calibration Screen" "The Green Bars"

Any other ideas?   I'm really stuck here.   I believe I've followed everything in the Manual, step by step.

Thanks,

Xomby

You need to be a member of diydrones to add comments!

Join diydrones

Email me when people reply –

Replies

  • Hey Folks,

    Really, thanks for all the thoughts and discussion around my problem here...   And for that I have an update on a couple of things.

    First, Receiver is now talking through the APM.   I don't know what changed, but here's what I did.

    I bought a new 6 channel receiver just to see if that would make a difference.   I created a brand new 'AIRPLANE' model on my Tx, everything basic, no mixing, no D/R, no expo, etc...

    I forgot to bind my Rx first and had everything connected to the APM, THEN I remembered to "bind" the receiver and did so.  FYI, this is the first time I binded the Rx while connected to the APM.   I was always binding first, then connecting.  (this is what the picture shows in my receiver instructions.

    Well, with the new receiver I now have output registering in the Mission Planner!!  Woohoo!!    For good measure, I changed models on my Tx, put my "old non-working" Rx back and connected it to the APM.   I did the bind process again, while connected to APM and the old non-working receiver worked great!!   So, as far as I can tell, the ONLY thing I did differently is to "Bind the Rx while connected to the APM".  <--maybe I should have done this all along, but honestly dont understand why this would matter.   I don't have to bind a Rx with servos attached, normally, so why is this different.

    So, NOW I've completed the rest of the MP configuration and have arrived at the ESC Calibration step, but new problem...  The ESC's won't respond to the calibration I'm trying to do.

    I am following the steps FOUND HERE. and am using the "Automatic ESC calibration (all at once)" but am not getting distinct single beeps and double beeps after each step.   I have not tried the "Manual ESC calibration (individual)" yet, but will have to try that next.

    Any thoughts on what might be going on?   I am following those (all at once) instructions very carefully.   I am unplugging the USB, I am disconnecting and reconnecting the battery when instructed, but there is no discernable difference in the beeping of the ESC's.

    Thanks,

    Xomby

  • That cables from the receiver to the APM doesn't look correct to me but I could be wrong. The top is the ground.
    Mine is connected with a standard servo cable (3 wire) from each output on the receiver to the inputs on the APM.
    Can you connect at least one or more inputs with a standard servo cable to the inputs on the APM.
    Ground is the outside pin, power than signal.
    Randy
  • Ok, here are some pics of my connections.  I've tried to show everything from the PDB to APM to Rx.

    IMAGE #1:  You will notice a couple of things.  First I did not follow the colors recommended in the guide (I got reversed when I started soldering).  ESC #1 - ORANGE,   #2 - WHITE,   #3 - YELLOW,   #4 - GREEN,    #5 - GRAY,    #6 - BLUE.     Another thing you will notice, I soldered my pins for the ESC connectors to the bottom of the PDB.   I still have the signal wire connected to the correct pin, I believe.   My ESC's all were doing their beeping and chirping as expected.

    3692615809?profile=original

    IMAGE #2:  APM Output from PDB.  #1 - ORANGE,  #2 - WHITE,   #3 - YELLOW,   #4 - GREEN,    #5 - GRAY,    #6 - BLUE.  You can also see the power from PDB connected to the +/- of Output #1 on the APM.    Since I'm using the Power Module option provided by 3DRobotics, I do NOT have the Jumper installed.

    3692615862?profile=original

    IMAGE #3:  APM to Rx.  FYI, I made these patch wires as part of my troubleshooting.  I was using the provided 5 wire harness along with the two wire power connector.  I believe I followed the directions properly and you can trace each connector in the picture, but here is how they are mapped:

    APM_INPUT_1  to  Rx_ALE

    APM_INPUT_2  to  Rx_ELEV

    APM_INPUT_3  to  Rx_THRO

    APM_INPUT_4  to  Rx_RUDD

    APM_INPUT_5  to  Rx_AUX1

    Power from APM is also connected to the BATT connection on my Rx.

    3692615824?profile=original

    Here's what happens...   When connected to USB on computer, all LED's are flashing on the APM, and Rx light is solid (means it is bound to Tx).  However, while attempting to complete the initial setup steps, I am unable to Calibrate my radio inputs.  **GREEN BARS in the Mission Planner Software**

    FYI, same results when I tried to calibrate with the LiPo connected.  As a troubleshooting step, I also tried everything with a dedicated receiver battery connected as well.   Again, no change in the results.  Zero Feedback on the calibration screen of the Mission Planner.

    I hope I've just wired something incorrectly here!!  Really appreciate any help the community can provide!!

    Thanks,

    Xomby

  • Agree, this is a great community.

    I did the servo test and everything with the receiver seems to be working properly

    Also, I see from the manual that the calibration step does not necessarily need the LiPo connected, but I went ahead and tried it that way as a troubleshooting step, and was advised to do so by Chris himself. (See ArduCopter wall posts from the past 24 hours)

    Finally, I will take some pictures so you can see how I have things connected. I am fairly certain that I have the signal posts connected, but it will be great to get another set of eyes or 10 on it.

    Thanks,

    Xomby
  • I will throw in some comments but don't worry, this is a great community. Your problem will be resolved.
    I live in Missouri City. Not too far from you.
    If you connect a servo to an output channel as mentioned above, does the servo actuate.
    If it does then let's see how you have it connected to the APM.
    You don't need lipo power to calibrate.

    Randy
  • jp1

  • I would check a couple of things because it would appear that your APM does not see the output from your receiver, so the questions are:

    1. Is the receiver actually outputing anything,

    2. Is the wiring between the receiver and the APM inputs correct.

     

    Do you have a servo or something that you can attach and test each output on your receiver.  If you confirm that each of the 5 or 6 channels you are wanting to use work then confirm that the signal wire from the receiver is going correctly to the signal pin on the APM and it is not accidently reversed and perhaps going to the ground pin instead.

This reply was deleted.