X-Virus-Scanned: clean according to Sophos on Logan.com From: "Finn Lassen" Received: from vms173017pub.verizon.net ([206.46.173.17] verified) by logan.com (CommuniGate Pro SMTP 6.1.5) with ESMTPS id 8015057 for flyrotary@lancaironline.net; Thu, 24 Sep 2015 12:42:12 -0400 Received-SPF: pass receiver=logan.com; client-ip=206.46.173.17; envelope-from=finn.lassen@verizon.net MIME-version: 1.0 Content-type: multipart/alternative; boundary="Boundary_(ID_4wcCzQJyQjFV5PvGqDoUeA)" Received: from [192.168.1.3] ([70.209.33.89]) by vms173017.mailsrvcs.net (Oracle Communications Messaging Server 7.0.5.32.0 64bit (built Jul 16 2014)) with ESMTPA id <0NV6004MXX0WOJ60@vms173017.mailsrvcs.net> for flyrotary@lancaironline.net; Thu, 24 Sep 2015 11:41:26 -0500 (CDT) X-CMAE-Score: 0 X-CMAE-Analysis: v=2.1 cv=btqxfxui c=1 sm=1 tr=0 a=UtoeEz31XFBZTRZpCoAuOw==:117 a=o1OHuDzbAAAA:8 a=oR5dmqMzAAAA:8 a=ff-B7xzCdYMA:10 a=r77TgQKjGQsHNAKrUKIA:9 a=Ia-xEzejAAAA:8 a=7g1VtSJxAAAA:8 a=753VHfGR-QUYCCYff_oA:9 a=pILNOxqGKmIA:10 a=Qa1je4BO31QA:10 a=4PR2P7QzAAAA:8 a=1RYE5310hRlDEdHOmnQA:9 a=lmjbvXc6Ta1dXr_l:21 a=_W_S_7VecoQA:10 Subject: Re: [FlyRotary] Re: OT: Calibrating altimeter and alt encoder To: Rotary motors in aircraft References: Message-id: <560427A7.9010901@verizon.net> Date: Thu, 24 Sep 2015 12:41:11 -0400 User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 In-reply-to: This is a multi-part message in MIME format. --Boundary_(ID_4wcCzQJyQjFV5PvGqDoUeA) Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT On 9/24/2015 11:12 AM, ARGOLDMAN wrote: > Not sure that I understand completely, however the encoded altitude > has nothing to do with your local setting. Yep. I set the Dynon to 29.92. Then the displayed altitude should match what the encoder sends out. Problem is how to accurately (preferably to within 10 feet) calibrate the Dynon. Obviously using nearby METAR reported pressures was not successful. And I'm beginning to think that the instruments that reports pressure to METARs may not be all that accurate -- varies from airport to airport. > all encoders are calibrated to the same calibrations so that when ATC > or whoever reads the reply all of the aircraft that they are looking > at have the same altitude bias independent of errors in setting the > kollsman window in the various aircraft. > Since you have gone into the encoder, there is a possibility that the > alterations that you have done may yield a constant error for ATC > which is worse than not having an altitude report at all. You might > want to have your encoder checked with proper instruments. > Something that comes to mind is that since the encoder and the > altimeter are both run from the static source, that there is a > blockage, kink, water etc that may be influencing the readings. > Good luck in your quest for vertical reading stability > Rich > In a message dated 9/24/2015 8:58:23 A.M. Central Daylight Time, > flyrotary@lancaironline.net writes: > > Off topic, except it's in a 13B Van's RV-3 ;-) > > Again, after flying home from Sun'n'Fun, ATC saw me several > hundred feet > below what I saw on my altimeter. > > Last week I finally got around to removing all the screws that > holds the > fuselage top over the instruments. > > I hooked LEDs across the data lines that run from the altitude > encoder > to the transponder (gray code). > (note that 1 is actually 0 volts -- active low). > > I checked METARs at nearby airports -- CTY, GNV... and I know my > elevation exactly. > That matched what my Dynon D10A and steam altimeter showed. > > I then spent several hours adjusting the high and low pots on the alt > encoder until the codes changed within 10 to 20 feet of the 50 foot > points when applying vacuum to the static system with a syringe. > Can't > get better that that, I though. > > Alas, after replacing the fuselage top and multitude of screws, > yesterday I hopped over to Cross City (CTY) a mere 15 miles away. > I had > to set the altimeter to 0.03 or 0.04 below what their METAR > reported in > order to get altimeter to show their field elevation -- 42 feet. > Basically shows 30 to 50 feet too high altitude if I set the Dynon to > the reported pressure. All that work for nothing! > > Now I'm beginning to suspect that the pressures reported by the > METARs > are not all that precise. > Checking METARS right now at nearby airports, they range from > 29.98 to > 30.02. > > Any suggestions on how to obtain an accurate air pressure reference? > > Finn > > > -- > Homepage: http://www.flyrotary.com/ > Archive and UnSub: > http://mail.lancaironline.net:81/lists/flyrotary/List.html > --Boundary_(ID_4wcCzQJyQjFV5PvGqDoUeA) Content-type: text/html; charset=windows-1252 Content-transfer-encoding: 8BIT
On 9/24/2015 11:12 AM, ARGOLDMAN wrote:
Not sure that I understand completely, however the encoded altitude has nothing to do with your local setting.
Yep. I set the Dynon to 29.92. Then the displayed altitude should match what the encoder sends out.

Problem is how to accurately (preferably to within 10 feet) calibrate the Dynon. Obviously using nearby METAR reported pressures was not successful. And I'm beginning to think that the instruments that reports pressure to METARs may not be all that accurate -- varies from airport to airport.
 
all encoders are calibrated to the same calibrations so that when ATC or whoever reads the reply all of the aircraft that they are looking at have the same altitude bias independent of errors in setting the kollsman window in the various aircraft.
 
Since you have gone into the encoder, there is a possibility that the alterations that you have done may yield a constant error for ATC which is worse than not having an altitude report at all. You might want to have your encoder checked with proper instruments.
 
Something that comes to mind is that since the encoder and the altimeter are both run from the static source, that there is a blockage, kink, water etc that may be influencing the readings.
 
Good luck in your quest for vertical reading stability
 
Rich
 
In a message dated 9/24/2015 8:58:23 A.M. Central Daylight Time, flyrotary@lancaironline.net writes:
Off topic, except it's in a 13B Van's RV-3 ;-)

Again, after flying home from Sun'n'Fun, ATC saw me several hundred feet
below what I saw on my altimeter.

Last week I finally got around to removing all the screws that holds the
fuselage top over the instruments.

I hooked LEDs across the data lines that run from the altitude encoder
to the transponder (gray code).
(note that 1 is actually 0 volts -- active low).

I checked METARs at nearby airports -- CTY, GNV... and I know my
elevation exactly.
That matched what my Dynon D10A and steam altimeter showed.

I then spent several hours adjusting the high and low pots on the alt
encoder until the codes changed within 10 to 20 feet of the 50 foot
points when applying vacuum to the static system with a syringe. Can't
get better that that, I though.

Alas, after replacing the fuselage top and multitude of screws,
yesterday I hopped over to Cross City (CTY) a mere 15 miles away.  I had
to set the altimeter to 0.03 or 0.04 below what their METAR reported in
order to get altimeter to show their field elevation -- 42 feet.
Basically shows 30 to 50 feet too high altitude if I set the Dynon to
the reported pressure. All that work for nothing!

Now I'm beginning to suspect that the pressures reported by the METARs
are not all that precise.
Checking METARS right now at nearby airports, they range from 29.98 to
30.02.

Any suggestions on how to obtain an accurate air pressure reference?

Finn


--
Homepage:  http://www.flyrotary.com/
Archive and UnSub:   http://mail.lancaironline.net:81/lists/flyrotary/List.html

--Boundary_(ID_4wcCzQJyQjFV5PvGqDoUeA)--