There's some low level traffic around, from local airports. It's
frequently interrogated, I have a separate ADS-B receiver that also shows
mode s targets, and it shows a lot of stuff buzzing around during the
day. Increasing the altitude limits of course adds more. PCAS target
range can only be increased to 10K meters, so that's a limiting factor in
how much you'll ever see with PF.

Doing more experiments, looks like the defaults aren't good at all for
the FlarmViews that Herb and I are using. In particular the protocol for
the RJ45 and d-sub gets set to 'default', much better results with
version 7. From their description, they ought to default to ver 4.
ADS-B vertical range is set for unlimited, a bizarre choice if you're
actually flying. "Process Mode C Targets" is shut off by default.

Not sure how Herb has his configured, but after setting the protocol to
7, I saw an ADS-B target show up with a plane symbol and a flashing ring,
and got the flashing blue dot when the target was right overhead. So it
seems to be a collision alert. A PCAS target showed up as just a
flashing ring, so it's working as expected now. Max range was about 6
miles in both cases.

These results were with latest firmware on PF and FlarmView, ymmv.

-Dave

On Sat, 07 May 2016 12:07:19 -0700, Darryl Ramm wrote:

So do you have much traffic below ~2,000' AGL where you are? That are
also in SSR interrogator coverage? (although TCAS should fill in as an
interrogator). Why not try setting everything unlimited and see what
happens.

Partial obstructions, local reflections etc. can severely screw with
PCAS's estimation of range. Testing that on the ground may be a waste of
time.

On Saturday, May 7, 2016 at 11:44:51 AM UTC-7, David Kinsell wrote:
Currently using the default flarmcfg.txt file, so 7000 and 600.


Sat, 07 May 2016 10:13:05 -0700, Darryl Ramm wrote:

And what are your PowerFLARM's PCAS range and altitude settings set
to?

On Saturday, May 7, 2016 at 7:11:29 AM UTC-7, David Kinsell wrote:
On Thu, 05 May 2016 11:50:39 -0700, Richard wrote:

On Thursday, May 5, 2016 at 11:17:11 AM UTC-7,
wrote:
Here at Chicago Glider Club we have the dubious distinction of
flying right under the approach path into Midway airport. I have
looked at SouthWest planes coming through from all angles,
including head-on. Flying with a C-mode transponder helps a lot,
Approach will guide the big iron around us although I'm sometimes
wondering about the spacing. My PFlarm will indicate through the
FlarmView display a blue dot around my position that is blinking
ONLY when a SW or bigger commercial plane (equipped with TCAS?)
is coming through. Could there be a connection such that the
transponder when interrogated by a TCAS responds in a way that is
picked up by PFlarm? What else might the blue blinking dot mean?
Please enlighten me.
Herb, J7

that is a mode C or mode S transponder it is non directional and
as it gets closer the circle should get smaller. Blue means it is
above you.

Richard www.craggyaero.com

I've been bench testing 6.06 firmware, and see what I believe Herb
is seeing. A small flashing dot right at current position, but it's
short lived and never gets bigger. It's like the range for mode
c/mode s targets is terrible. I see lots of ADS-B targets at
distances greater than 12 miles, but hardly any mode c/mode s.
Maybe they gave up trying to estimate distance for those targets?