Originally Posted by billpa

mamut, if I understand correctly from your photos, the reason your distance and altitude are not reporting is because you have configured an HDOP accuracy number that is not being reached? I think you just need to make that number larger in the menu (larger number means less accuracy). What do you have it set to now, out of curiosity?

MY BAD!- for your curiosity- 0.9 But I should be able to read on OSD the altitude and distance even if "wrong ones"
"Dual Channel A/D Expander for R/C Data Recorder" can be implemented for reading some other external device (Alpha angle, humidity, magnetic... etc) on Elogger or on OSD?- it would be very useful to develop new sensors
I wish that maybe one day Bill will talk with HappyKilmore to update his PC interface- TV recording/Eagletree PC interface and Google Earth management on the same screen(9'') is a pain ...maybe some day it will be like....

Originally Posted by helichoper

Did you select diversity on the eagle eyes with the little button?

I'm sorry don't have manual with me .lazy me was thinking plug and play :-). Do I have to plug into computer ? I didn't get a USB cable with it

Ok I've looked up the manual on my phone :-)

Originally Posted by catamar

That's what I was saying, but somebody was thinking that maybe now he could have more channels to do some other things. So I asked him how (I think it is not possible)

That has to be me I was not talking about freeing channels on the receiver. The receiver will simply outputs all channels on a single wire. BUT, this will free some inputs on the OSD PRO (as mentionned above). If those inputs could be reprogrammed as outputs, they could be use to extend the number of control surface the OSD PRO can drive, i.e. 1 channel for each aileron. That would allow me (and others) to keep using ailerons as flaperons (both down) which is currently not possible because I had to use a Y cable so the single "ailerons" output of the OSD PRO can drive both ailerongs (going in opposite directions).

Hello,

Why does my throttle percentage indicator start at 18 and goes only up to 75%

Thanks.

Originally Posted by jackheli

Hello,

Why does my throttle percentage indicator start at 18 and goes only up to 75%

Thanks.

Normally you need to calibrate it on Eagle tree PC application.
(mine - on alpha version stick to 100 - I still try to figure it out why maybe I didn't calibrate it correctly)

Originally Posted by jackheli

Hello,

Why does my throttle percentage indicator start at 18 and goes only up to 75%

Thanks.

Originally Posted by mamut

Normally you need to calibrate it on Eagle tree PC application.
(mine - on alpha version stick to 100 - I still try to figure it out why maybe I didn't calibrate it correctly)

You have to calibrate the throttle in the pc application, using the menu item :
Calibration>calibrate throttle.

Throttle range is not calibrated automatically during the senvo analysis wizzard.

Originally Posted by sancho28

That has to be me I was not talking about freeing channels on the receiver. The receiver will simply outputs all channels on a single wire. BUT, this will free some inputs on the OSD PRO (as mentionned above). If those inputs could be reprogrammed as outputs, they could be use to extend the number of control surface the OSD PRO can drive, i.e. 1 channel for each aileron. That would allow me (and others) to keep using ailerons as flaperons (both down) which is currently not possible because I had to use a Y cable so the single "ailerons" output of the OSD PRO can drive both ailerongs (going in opposite directions).

So you're telling me I can do away with all the servo wires coming from the rangelink rx to the OSD board?

Originally Posted by sfakias

You have to calibrate the throttle in the pc application, using the menu item :
Calibration>calibrate throttle.

Throttle range is not calibrated automatically during the senvo analysis wizzard.

Ah... I thought the wizard would do the calibration that's why I stopped looking. Thanks a lot!

Originally Posted by sfakias

You have to calibrate the throttle in the pc application, using the menu item :
Calibration>calibrate throttle.

Throttle range is not calibrated automatically during the senvo analysis wizzard.

I ran the throttle calibration wizard which seemed to go okay. But my OSD still shows 18% to 75%.

When is the calibration setting set on the pc application sent to the OSD?

Originally Posted by jackheli

I ran the throttle calibration wizard which seemed to go okay. But my OSD still shows 18% to 75%.

When is the calibration setting set on the pc application sent to the OSD?

The servo deflections aren't always displaying the figures that you would think they should be.


The question is whether it functions properly.


My throttle never showed from 0 - 100 on servo deflections,

but the values that it shows are constistant, and it works great.

The OSD shows some numbers that have to do with servo positions and these are not in percentage (they are + or - and have values up to several hundredths. The throttle position as a percentage is logged in the e-logger, and can also be displayed live on the pc application.

Am I missing something here?

The calibration setting, I *think* it is sent to the OSD as soon as you finish the calibration procedure. Maybe you have to re-boot your OSD, but I wouldn't think so, since the corrected throttle range is displayed instantly on the pc application, in live mode.

It's would be too bad that with so many configurations we need to get stuck with weird throttle ranges while we are flying... Just saying...

Originally Posted by jackheli

It's would be too bad that with so many configurations we need to get stuck with weird throttle ranges while we are flying... Just saying...

Ya,

That doesn't sound right.



are you trimming your throttle down all of the way when you run your servo analysis wizzard, " for the motor off position?

Originally Posted by Teamsherman

So you're telling me I can do away with all the servo wires coming from the rangelink rx to the OSD board?

Yes, all but one, that will carry the signals for all channels and that has to be connected to the "aileron input" of the OSD PRO (which then becomes the "ppm stream" input...)