Search results

Well your ADS-B data is being transmitted via your DYNON SV-XPNDR-261 transponder. If you show the correct tail number then your transponder is sending out the correct tail number. In the transponder data stream, Flight ID is not the same as Tail Number and your avionics guy "should" know this...

Don't need to fly for method #2. Find someone with a portable dual band STRATUX/STRATUS receiver and a tablet. ;)

So did it pass the test with the new code, assuming you don't have anything in the flight ID section? 1 - Take a flight around your area and check FlightAware to see what they report as your tail number. 2 - Find a friend that has ADS-B "IN" capability and see what shows up on their display.

New HEX code as in A02F90?

The actual HEX code for N1107R is A02F90 with an OCTAL code of 50027620 so something is definitely wrong with the setup. Try erasing the FLIGHT ID you currently have in your setup and enter HEX Code A02F90 to see if that works. :cool:

If you don't get the beeping alerts you have a configuration/set up issue. Contact DYNON support and they can walk you through setting it up.

Well since stall air speed changes with aircraft weight the old stall warning horn works better for stall avoidance than an airspeed call out. You calibrate the AOA aural alerts so it goes constant just before a stall happens. After a few flight you will know what beep speed gets you your best...

Contact DYNON support for this issue. I had the exact same issue and they had to do a factory update to the EMS module. It has been working perfect since then.

What makes you think having not having continuous software releases means no support? FWIW I prefer not to update a known working system than do a non critical update that might introduce a new problem. That is why, unless there is a critical issue being corrected, I wait until a significant...

Now that ADS-B is required in many US airspaces, the FAA has provided a method to request entry to "rule" airspace under specific situations. FAA ADAPT Tutorial Video :cool:

Sound to me that you have an intermittent cable/antenna connection problem caused by normal airplane vibrations. Check or replace the cable and the connectors. I had the same problem so I replaced my cable/connectors with high grade professionally made RG400 cable. The problem went away. After...

FWIW: I have Trim (Elevator/Aileron), Radio PTT, Fuel Pump, COMM flip-flop, NAV flip-flop, and IDENT on my stick. I don't have electric flaps or that would have on the stick instead of the fuel pump. IOW everything I would need during an instrument departure/approach in actual IMC where I need...

AWESOME!!!! With the numbers you just posted your GPS based independent TAS is within 1Kt of the SkyView displayed TAS. Well within the 3Kt acceptable range and probably just due to rounding up/down the numbers used in the calculations.

This is a very important piece if information I forgot to mention. Unless you are very skilled (or lucky) using wire cutters, scissors or even box cutters to cut the tube almost always results in a leaky fitting. I have this inexpensive plastic tube cutting tool and it works great...

My 2cents... the trim indicator is telling you which way the nose is going, not which way the trim tab is going. IOW: you are trimming nose up or you are trimming nose down.

If your IAS is wrong many of the EFIS calculated values (including Altitude, TAS, Cross Winds and others) may also be wrong. There have been multiple threads about this and similar issue. Here is a link to the latest thread.

Next time you fly do both a "high speed" and "slow speed" test then let us know the results. You are heading in the right direction to make this right. There are too many variables involved so you might not get it "100% perfect" under every condition but as long as you get it to be less than...

Not if the pitot/static system is providing the EFIS with a wrong IAS value. In a modern EFIS, TAS is calculated based on IAS, among other variables, so a wrong IAS will give a wrong TAS. "Garbage in, garbage out."

FWIW my harness came with a thin yellow wire already attached to pin #2, not to be confused with a #2AWG wire. :p

With those "slow speed" numbers your SkyView TAS and GPS calculated TAS are exactly the same (109Kts). TAS error is +14Kts at high speed but 0Kts error at "slow speed". This confirms a static source issue. Now to find the culprit. :cool: