Announcement

Collapse
No announcement yet.

Spektrum AR6250 receiver seems to cause 3G unit to fail to initialise

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Spektrum AR6250 receiver seems to cause 3G unit to fail to initialise

    UPDATED:

    Having asked if people have this issue with slow Spektrum receiver connect causing 3G not to initialise - reconnect works fine. I've realised problem I have with 500 3G with AR6250 is due to a problem with the AR6250 receiver power up/failsafe behaviour - which causes 3G unit to fail to boot. The AR6110/6100 I have in 250/450 don't do this, which is why they work fine.

    Seems to be a known 3G issue that if the spektrum receiver is slow to connect the 3G won't initialise, swash doesn't jump and the indicator light flashes red/green/red/green. Unplug/replug battery and it will normally boot up find 2nd time (but I guess quickconnect means rx connects super-fast on 2nd power up) - seems that 'normal' spektrum receivers this is unusual, as they provide servo failsafe positions on power up until radio connects - the AR6250 is different and gives NO SERVO signals at power up, until radio connects.

    AR6250 manual says: Receiver Power Only - When the receiver only is turned on (no transmitter signal is present), all channels have no output signal, to avoid overdriving the servos and linkages.

    AR6110/6100 manual says: Receiver Power Only - In electric aircraft,when the receiver only is turned on (no transmitter signal is present), the throttle channel has no output, to avoid operating or arming the electronic speed control. All other channels hold their last commanded positions set during binding.

    I think I will get an AR7600 receiver for my 500, and use the AR6250 in something else to get round this, I just spoke to Horizon UK, who weren't aware of this, so I've suggested they might want to flag this up, as I can't be the only one looking for a single unit receiver for Align 3G heli.
    Last edited by jamesb72; 09-04-2010, 04:28 PM.

  • #2
    Rebind the TX to the RX and see if that helps

    Jaco
    Jaco

    Outrage Velocity 50 FBL - OS55 - Align DS610, AR7200BX + DS650, MGP, Perfect Regulators Igniter Push Button Glow and Flighttech 8A regulator
    T-Rex 600NSP FBL - OS50 - Align DS620, AR7200BX + DS650, MGP, SwitchGlo and Ely.Q reg
    T-Rex 450SE V2 with CC45 esc
    sigpic Proud owner of 2(Two) EGS!

    Comment


    • #3
      Never had a problem TBH.

      Try running the complete setup again and re-bind your TX to your receiver again also.

      Comment


      • #4
        Not had this on mine yet. Running AR7000 on the 600esp and Ar6200 on the 500.
        Cheers,
        Simon
        --------------------------------------------
        Trex 700N & E
        Futaba 18mz and some planks !!

        x 2

        Comment


        • #5
          Try rebinding again.

          I would rebind anytime i made an adjustment.

          Comment


          • #6
            Its not a rebinding issue, the rx connects fine just takes a while.

            Just compared the AR6250/AR6110 user guides and think I can see what might be causing this.

            AR6250 gives no signal to servo's on power on until connected:
            AR6250 manual says - When the receiver only is turned on (no transmitter signal is present), all channels have no output signal, to avoid overdriving the servos and linkages.

            AR6110/6100 only give no signal to the throttle servo - other servo's get failsafe - I think the 3G wants to see servo signals as part of its boot up:
            AR6110 manual says: Receiver Power Only - In electric aircraft,when the receiver only is turned on (no transmitter signal is present), the throttle channel has no output, to avoid operating or arming the electronic speed control.

            Ooops, seems like the AR6250 receiver may not be a good choice for 3G as its effectively incomatible with 3G startup sequence ;-(

            I've updated first post to show this.
            Last edited by jamesb72; 09-04-2010, 04:24 PM.

            Comment

            Working...
            X