TCAS has algorithms which are dynamic. it also mandates/advise actions.
What i'm talking about is a user controlled option to tell the EC device/data, to reduce it's sensitivity during certain stages of flight.
You can do this already in PaW for example - you set the height and distance and type of traffic you want to know about. My assertion in the circuit is that you want to know about stuff alot closer to you and on take off you probably want to know even less
the reason for postin on here rather than PaW (although I have on their forum too) is a usability one. I can do what i've suggested already through the PaW admin/app. But it'd be more dangerous fiddling with those settings in the take off roll or when doing an OHJ!
the "feature creep" that may be interesting is a two way interaction between SD/EFBs and EC devices. At the moment the EC device broadcasts on UDP and SD/EFBs fairly dumbly (no offence) display the data. That is why they are NOT TCAS devices.
However if the EC device is API enabled, you can allow the EFC to at least control the existing parameters dynamically, with the EC device still be responsible for deciding what data packets to transmit and using it's internal algorithms. The SD wouldn't be doing nay filtering out etc