Designating Servo

[jnmeade]

I have two physical servos in my airplane. The servo that is physically in the roll system is not being detected by the config system. The servo that is physically in the pitch system is identified and designated as "roll" servo in the calibration process.

This leads me to the conclusion that SkyView counts servos and if only one is identified, SV assumes it is in a wing-leveler function and thus call is a "roll" servo. I understand that if SV finds two servos it differentiates between them by the Calibration procedure, but in this case SV only sees one servo.

Can anyone confirm from documentation reference that if SV sees only one servo it designates it as "roll"? I looked in the current install manual and did not find clarification.

 

[jakej]

Why doesn't it 'see' the Roll Servo' ? Did you do a system Config ? All wiring correct ? I wouldn't spend too much time over what you ask, it's more important to have both working, disconnect the Pitch servo & see what happens.

 

[jnmeade]

My original question is a simple one - how does SV designate the servo name.

You can see by reading my OP that I did a system config and attempted calibration. I didn't include the information about how I tested the servo systems and eliminated all wiring issues (except in the undetected servo itself) because it wasn't germane to my question of how SV names the servos.

It's a straight-forward question and I didn't intend it as an entry into a discussion of troubleshooting the servo system. My error. I should have been more explicit. Thanks for your interest and sorry for any confusion.

 

[Raymo]

I thought it made the determination during calibration, which would make sense.

 

[jnmeade]

I thought it made the determination during calibration, which would make sense.

My understanding is that when there are two or more servos and they work you are correct. Mine is the case of where I have two servos but only one is identified in the config process, and it's the wrong one. Thus my suspicion that if SV sees only one servo it assumes it's a roll (wing-leveler) servo.

Maybe the Dynon rep can offer some clarification. I read the install manual and this situation is not directly addressed or I missed it.

 

[kellym]

My understanding is that when there are two or more servos and they work you are correct. Mine is the case of where I have two servos but only one is identified in the config process, and it's the wrong one. Thus my suspicion that if SV sees only one servo it assumes it's a roll (wing-leveler) servo.

Maybe the Dynon rep can offer some clarification. I read the install manual and this situation is not directly addressed or I missed it.

Your suspicion is more than just likely. I don't believe the system was ever designed to allow a pitch only configuration. The logic is that installing an auto pilot begins with a roll servo. Add a second servo for pitch, a third for yaw. Until you have 2 servos detected, the system is not going to consider anything detected as anything but a roll servo. So you need to solve why the system doesn't see the roll servo. Once you get that solved, you won't have the question, the system will figure out the correct location through the calibration. In fact, I'm pretty certain that in most cases the servos used are identical electronically, and only differ by the mounting hardware and arm connection to the flight controls.

 

[Raymo]

I'm pretty certain that in most cases the servos used are identical electronically

They are identical. Some opt for a higher torque capable servo for pitch. I went for the mid-torque servo for both. I also agree the original question is moot.

 

[jnmeade]

The latest wrinkle is that after at least a dozen configurations and calibrations, for the first time the SV found the pitch servo as the pitch servo For the first time the calibration went right all the way through and resulted in the SV causing the stick and control surface to respond appropriately. Sometime during this testing I disconnected the undetected roll servo. Maybe that is when SF found the pitch servo. In any event, I'm sure I could not reproduce the sequence of events that caused the pitch servo to calibrate correctly but I'm not going to try. Leave sleeping dogs alone. I'm still at the situation of where SV does not detect the roll servo but that is a question for another thread.

 

[Dynon]

So the servo detection/calibration routine is what identifies what servo(s) are installed. For obvious safety reasons, the system doesn't make any assumptions about servo axis designation or direction of travel. When you do the initial 4 corners of travel demonstration, that'll what you're really doing (it's not setting end-points or anything of the like, although it will warn you if it's seeing travel that seems too far for a non-capstan servo).