Ev4 Traffic image display
1/I would like to hear others thoughts on the way traffic is depicted in EV4?
In Ev3 the traffic is easily seen and displayed on screen in colour Red and /or Yellow regardless of distance away.
in Ev4 traffic is shown in a very wishywashy grey shadow outline and the eye is not easily attracted to it I find at all!
I had an email conversation with Rob regarding this the other day and he says that it should go from the grey outline to red as the traffic gets closer? This I have found does not happen, or at least does not happen to me! Today I had traffic at 0.5 miles on two occasions and it did not change from the grey shadow outline to red as it got closer at all.It just stayed in the grey shadow outline.
Personally I think this need to be looked at and reviewed.
A separate issue re traffic:-
2/ I am currently using GDL 90 for both Ev3 and Ev4 traffic and have more traffic shown in Ev3 than in Ev4. Sometimes traffic is shown in Ev3 but does not appear at all in Ev4?....Anyone have any idea why?
Ref: I had an email conversation with Rob regarding this the other day and he says that it should go from the grey outline to red as the traffic gets closer? This I have found does not happen, or at least does not happen to me! Today I had traffic at 0.5 miles on two occasions and it did not change from the grey shadow outline to red as it got closer at all.It just stayed in the grey shadow outline.
I believe that Traffic should only change colour if +- 1000ft to you.
With reference your comment about seeing more traffic in EV3 compared to EV4, please check that the filtering settings are the same and that the altitude that EV3 & 4 display for you are matching. I test EC devices at home and set:
Menu>Nav Tools>Settings>GDL 90 Settings>Vertical Proximity to 30000 feet.
EV4: Menu>System>External Devices>Electronic Conspicuity Settings>Traffic Vertical Proximity to 30000Ft.
When I go flying I change it to 3000 feet to "hide" commercial airline traffic which is of no interest.
If the traffic did go to red at >1000ft vertically it would be good!
However it doesn't that is my point. What about horizontally?...at 0.5miles horizontallly it also doesn't show red!...and the time to a potential collision with 0.5miles horizontally at say a conservative 240knot combined closing speed is not that much!
The grey shadow ouline of traffic is what I have a problem with. Ev3 is much clearer .
2/ I have settings in flight EV3 and Ev4 are exactly the same, 2000ft vertically. Ev3 sees more traffic for some reason.
Is your FLARM unit built into the aircraft? If not then suggest you set it up at home and do some testing. I have my PAW at home when not flying and I have had that connected to devices running EV3 & EV4 and am seeing the same commercial (ADS-B) traffic on both devices. Not much GA as the local airport is now closed, but I will run back to back tests again to compare.
I think you/we need to understand what traffic is not appearing on EV4, but is showing on EV3. That may assist.
Are you saying that the traffic at 0.5 miles away is less than 1000 feet above/below you? Do you have any details of that traffic, what time it was and where? Flightradar 24 has the ability to replay traffic. It would be interesting to see if it shows up on there. I have seen traffic 20+ miles away showing red because it is +- 1000 feet to me.
If you can grab comparable screen shots that may help but rule number one, fly the aeroplane. Perhaps you can take a mate with you to assist.
Putting the green/grey plane topic aside, then I would expect both systems to display the same and alert the same and that is what we need to focus on.
I will run some more tests over the weekend but as reported on the other thread, we need to ensure that both EV3 & EV4 are NOT connecting to anything by WiFi other than the same EC device. As has been said, if necessary delete those WiFi connections from your list of networks.
Where are you based? If close by then perhaps we can meet up. I am in Essex.
To explain further re;- Not all traffic protocols being displayed on Ev4.
I have PowerFlarmFusion permanently installed behind the panel in my aircraft connected to top and bottom external antennas.
The above is coupled RJ45 to a Aboba V3+ dedicated traffic display also RS232 coupled to my twin Dynon Skyview screens.
The above system works extremely well and the traffic seen GLD90/Wifi on Ev3 matches more or less what I see on the hardwired displays above, showing Flarm/PowerFlarm, ADSB and Mode S traffic.
I believe Ev4 as I have it currently configured ( SkyEcho set as per Rob's instruction)is only picking up Flarm/PowerFlarm and not ADSB or Mode S which the other displays and Ev3 are showing.
It is not a major problem because I can see lots of traffic on the other displays so it doesn't really matter in the general scheme of things but it would be nice to have Ev4 displaying the same traffic as Ev3.
Thanks for the kind offer of help with this, however I am in Derbyshire.
* Note:- My main concern is the actual Traffic image depiction in Ev4 which as shown at the moment needs improvement in its clarity.
Alan - what version of EV4 are you running - Is it perhaps a version earlier than 4.0.882? please see teh item below from the release notes for Version 4.0.882:
- "FIXED: When using a GDL90 source (SkyEcho2, Stratux etc) for traffic information but using the internal GPS as ownership location then when the GDL90 source internal GPS was inoperative or did not have a fix then received traffic would be displayed at the wrong location."
The location error caused by the bug could be very large, such that the aircraft would usually not be within the visible map area so this could explain the problem you are reporting. Interesting that the bug also links to the "GPS location source" issue you have been discussing on another thread!
Unless you have signed up to continue getting Public Beta versions (an option on the MyEasyVFR pane) you will be on something earlier than .882. However, a bit of good news - we are currently working hard towards a full public release of what will be .899 hopefully in the next week or two if final checks go well!
Running latest version .899.
Ref: I believe Ev4 as I have it currently configured ( SkyEcho set as per Rob's instruction)is only picking up Flarm/PowerFlarm and not ADSB or Mode S which the other displays and Ev3 are showing.
SkyEcho devices do not detect/display Mode S traffic. They did at one stage but as uAvionix could not guarantee the location of a Mode S equipped aircraft (as LAT & LONG are not transmitted), a firmware update removed that functionality.
Do you have a FLARM decode license via EasyVFR? That is required to display FLARM traffic on EV4 when connected to a SkyEcho2 device. However, if EV4 was connected to the FLARM Fusion then you would see FLARM traffic as the decode licence is included with the hardware.
I would be interested to see a screenshot of your Skyecho config page. Is it a SkyEcho 2? Please can you email this to me at [email protected]
If you have a SkyEcho 2 you should also be running:
Wi-Fi version: 0.2.30-SkyEcho
ADS-B Version: 2.6.13
These are the latest firmware releases and ensures that we have matching settings.
Personally, I think you would be best to use your SkyEcho for ADS-B out only and use the FLARM Fusion to receive traffic.
You could have the SkyEcho configured for ADS-B in and connect to that by Wi-Fi only if you had a total FLARM Fusion failure.
I do not need a Flarm de-code licence for PowerFlarmFusion.There is no de-code.
Previously confirmed this with Rob.
I do not have SkyEcho2.
I have PowerFlarmFusion which also has ADSB 'in' and Mode S 'in'.
Rob told me that it would just work by setting up as per SkyEcho2.
I currently see Flarm/PowerFlarm traffic but I believe nothing else, ADSB, etc. wheras Ev3 does.
Apologies, now I understand, you have the FLARM device feeding both EV3 & EV4 with the same vertical proximity values set but you are not seeing the same traffic.
I think this needs some testing with the FLARM Fusion device. I will check with Rob if he has a unit that can be tested with.
That is exactly the issue!