[Solved] Lateral distance setting for traffic alerts
I've jst installed build 604 from scratch as indicated in the release notes. Installation and registration was smooth, a bit surprised that registering was prompted for on selecting the second country. But probably nice to allow free use on a single country without having to maintain two different versions. Good job! Program seems a bit more responsive as well.
With a clean install comes default settings. I didn't see any traffic from my stratux at first as the filter was set for 3000ft default. I set it to 35000ft to see commercial traffic and that worked well. I had my speaker volume quite high when a booming voice warned me of traffic. Had me jumping from my seat! Anyway, that warning was for a plane 30000 above me. Not a real danger.
My request therefor: Separate lateral distance settings for visible traffic and traffic thats actually a threat?
Huhh? Traffic warnings are only given for traffic with 2000ft or less vertical separation. Is the problem reproducable so we can determine wether it is a bug in EasyVFR4 or incomplete data from Stratux or something else?
Hmm.. I might be on to something. It appears to be a combination of factors.
I've lost GPS connection to the Stratus a few times. At that time all detected planes turn orange, and EV4 starts cautioning for all planes regardless of distance or lateral separation. The distance is read relative to the last known position. "Caution, traffic at 5 o'clock, 47 Nautical Miles" for a plane that's both 47 miles away and at 30000ft.
I verified to have good GPS info from my Stratux, and even then it warns for a plane overhead at 15k ft.
Very interesting, I don’t understand why this is happening ????. You have the stratux for a whle; is this something that popped up in the latest version only, or was it in previous versions also? We will do a test with our skyecho2 next week to see if we can replicate this....
I'm noticing several anomalies in the traffic warning systems in the latest software but can't be absolutely sure they were not there previously.
Location (GPS) Source set to "Automatic" and my PilotAware connected, EV4 selects:- "GDL90 Sratux, PilotAware/uavionix SkyEcho (UDP)"
I've heard audio warnings for altitudes above 2000ft as others have remarked and not yet heard any clock directional audio but i suspect that may still be a work in progress. ? Also when using above protocol setting I only get (difficult to spot) Grey aircraft symbols which do not change colour at all with altitude or any other threat level. The text does not change colour either as in other protocols. Contrary to my earlier emails to you I am seeing the same Grey aircraft symbols for the Mode S/3D traffic in this protocol.
I think I must have been using the "PilotAware Flarm Emulated (UDP)" protocol previously as that still only shows the little centre dot but threat aircraft do change colour in that protocol. (I'm not very sure there were so many choices in earlier versions.)
Everything else seems to be coming along nicely. Great work Rob
I had a dig into this Traffic system, its a complex system because every device has its own " curiosities". Specially PAW is difficult to get right with all their different implementations and interpretations over time.
EasyVFR4 fires a warning (change aircraft colour from gray to red or orange, execute a vocal warning) based on two possible alarm systems. One system is controlled by EasyVFR4, the other is controller by the associated device. You can choose which system to use using menu->system->electronic conspicuity settings, the options "Use EasyVFR4 warnings" and "Use Device Warnings" respectively.
The first step in debugging these warning issues is to select only one of these two, so we can narrow down if the alarm is raised by EasyVFR4, or by the device itself.