[NSRCA-discussion] Need some Futaba S.Bus troubleshooting help

[Jas]

It's usually something simple. Mine wasn't writing/saving when I was doing it my first time lol

Jas iP

> On May 30, 2016, at 12:36 PM, lucky macy via NSRCA-discussion <nsrca-discussion at lists.nsrca.org> wrote:
> 
> disregard.  figured it out.  know how there's two Sbus ports on the receiver?  well, I didn't plug into the right one.  I only recalled reading to use the channel 8 port on the receiver which doubles as an S.Bus port and that is what I did and it didn't work however the dedicated S.Bus2 port along the bottom edge of the RX works perfectly...  :-)
>  
> Subject: Re: [NSRCA-discussion] Need some Futaba S.Bus troubleshooting help
> From: danamaenia at me.com
> Date: Mon, 30 May 2016 11:56:44 -0400
> CC: justanotherflyr at gmail.com
> To: luckymacy at hotmail.com; nsrca-discussion at lists.nsrca.org
> 
> Perhaps describe wiring from Rx to servos, Rx mode, model #s?
> 
> Sent from my iPhone
> 
> On May 30, 2016, at 11:54 AM, lucky macy via NSRCA-discussion <nsrca-discussion at lists.nsrca.org> wrote:
> 
> mine too so I went back through all that and verified it was on the right CH ID and resaved (write command) it anyway, a couple of times.  Even started to grasp at straws and powered off everything and started all over from scratch.  It's a new radio and only the second plane I've put in it and I didn't copy it from something else since the other plane isn't set up to use S.Bus.
>  
> when the servo is connected directly to the transmitter it responds correctly to the rudder input.
>  
> so all 3 servos operate as one would hope when individually connected to the TX but the rudder responds to elevator and nothing else when connected to the receiver.
>  
> Subject: Re: [NSRCA-discussion] Need some Futaba S.Bus troubleshooting help
> From: justanotherflyr at gmail.com
> Date: Mon, 30 May 2016 11:44:05 -0400
> To: luckymacy at hotmail.com; nsrca-discussion at lists.nsrca.org
> 
> My guess is the rudder wasn't set as Ch 4 when you programmed it and saved it.
> 
> Jas iP
> 
> On May 30, 2016, at 11:39 AM, lucky macy via NSRCA-discussion <nsrca-discussion at lists.nsrca.org> wrote:
> 
> Figured this forum is as good as any.
>  
> I have a futaba 18sz.  Airplane set up as 2 ailerons and ailevator ( 2 elevator halves) and 1 rudder.
>  
> The servos were programmed for Ch ID 2 as elevator 1, # 4 rudder and # 7 as elevator 2.
>  
> When the servos are individually in the S.Bus programming mode via plugging the servo in to the back of the transmitter each individual servo works perfectly.
>  
> When I hook them all up to the receiver, the elevator halves work find but the rudder servo is not being commanded by the rudder stick.  Instead, it moves back and forth only when the elevators are moved up and down.  So it's somehow tied to the elevator halves.  I verified in the TX that there is a rudder function and it is to the right stick and it is on channel 4.  I also can not find any type of p-mix at or condition setting that would explain it.  
>  
> And and just for grins when I am on the servo monitor page of the TX, when I operate the elevators it doesn't show that the rudder function is moving too which if it did would really be interesting but at least help to explain what's going on.
>  
> So I'm obviously overlooking something 'obvious' so if anyone has any ideas please chime in!
>  
> Thanks!
> _______________________________________________
> NSRCA-discussion mailing list
> NSRCA-discussion at lists.nsrca.org
> http://lists.nsrca.org/mailman/listinfo/nsrca-discussion
> _______________________________________________
> NSRCA-discussion mailing list
> NSRCA-discussion at lists.nsrca.org
> http://lists.nsrca.org/mailman/listinfo/nsrca-discussion
> _______________________________________________
> NSRCA-discussion mailing list
> NSRCA-discussion at lists.nsrca.org
> http://lists.nsrca.org/mailman/listinfo/nsrca-discussion
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nsrca.org/pipermail/nsrca-discussion/attachments/20160530/75a139c6/attachment.html>