Oudie/Flarm alarm from my own ADS-B/Transponder

It was most certainly the aircraft ID.
But now you disabled mode c alerts all together. You may want to turn that back on.

Ramy

On Sunday, May 16, 2021 at 7:58:24 AM UTC-7, wrote:
Thanks to 5Z and Roy B. for their help. I adjusted the FLARM configuration file:
-My config file already had "$PFLAC,S,OWNMODEC,0", but I noticed that I had:
$PFLAC,S,MODEC,1
so I set it to:
$PFLAC,S,MODEC,0
-Per Roy B. I cleaned the FLARM SD chip and put only the latest firmware update and the config file
-I also made some adjustments to the transponder configuration to correct errors found on the PAPR report. One of those was that the aircraft ID was missing the "N". I corrected that in both the transponder and also the FLARM.

I don't know which of these changes fixed the problem, but I tested the system yesterday and I am no longer getting the conflicts.

Thanks again for the help!

Rich L.

On Monday, May 17, 2021 at 11:23:32 AM UTC-5, Ramy wrote:
It was most certainly the aircraft ID.
But now you disabled mode c alerts all together. You may want to turn that back on.

Ramy

I re-enabled mode C yesterday and when flying again got the continuous conflict alerts. In flight I managed to turn the mode C off in the Flarm and the alerts went away. Is there something wrong with my configuration of the FLARM or transponder/ADSB that is causing this? My ADSB set up was just tested and passed, and I just generated a PAPR report for the flight yesterday and it was clean. I updated both my FLARM and Oudie firmware this year, so they should both be up to dare. My FLARM config file is:

################################################## ##################################
# This configuration file must be text only and reside in the top directory of the
# USB stick, SD card or FLARM Tool.
# This configuration file must be named FLARMCFG.TXT
# If you wish to change the settings, you can revisit the online configuration tool
# at any time: https://www.flarm.com
################################################## ##################################
$PFLAC,S,DEF
$PFLAC,S,ID,A4AA4E
$PFLAC,S,ACFT,1
$PFLAC,S,NMEAOUT,71
$PFLAC,S,BAUD,2
$PFLAC,S,RANGE,65535
$PFLAC,S,VRANGE,500
$PFLAC,S,XPDR,2
$PFLAC,S,MODESALT,1
$PFLAC,S,ADSBRANGE,65535
$PFLAC,S,ADSBVRANGE,65535
$PFLAC,S,ADSBWARNINGS,1
$PFLAC,S,PCASRANGE,9260
$PFLAC,S,PCASVRANGE,610
$PFLAC,S,MODEC,1
$PFLAC,S,OWNMODEC,0
$PFLAC,S,PCASCALIBRATION,60
$PFLAC,S,PCASBEEP,1
$PFLAC,S,PCASPFLAU,0
$PFLAC,S,REBROADCASTSERVICES,255
$PFLAC,S,AUDIOOUT,0
$PFLAC,S,AUDIOVOLUME,100
$PFLAC,S,LOGINT,1
$PFLAC,S,PILOT,Livingston/StClair/Bernatz
$PFLAC,S,GLIDERID,N40AF
$PFLAC,S,GLIDERTYPE,LS6a
$PFLAC,S,COMPCLASS,15m
$PFLAC,S,PRIV,0
$PFLAC,S,NOTRACK,0


Rich L.

On Sunday, May 30, 2021 at 7:50:42 AM UTC-7, wrote:
On Monday, May 17, 2021 at 11:23:32 AM UTC-5, Ramy wrote:
It was most certainly the aircraft ID.
But now you disabled mode c alerts all together. You may want to turn that back on.

Ramy
I re-enabled mode C yesterday and when flying again got the continuous conflict alerts. In flight I managed to turn the mode C off in the Flarm and the alerts went away. Is there something wrong with my configuration of the FLARM or transponder/ADSB that is causing this? My ADSB set up was just tested and passed, and I just generated a PAPR report for the flight yesterday and it was clean. I updated both my FLARM and Oudie firmware this year, so they should both be up to dare. My FLARM config file is:

################################################## ##################################
# This configuration file must be text only and reside in the top directory of the
# USB stick, SD card or FLARM Tool.
# This configuration file must be named FLARMCFG.TXT
# If you wish to change the settings, you can revisit the online configuration tool
# at any time: https://www.flarm.com
################################################## ##################################
$PFLAC,S,DEF
$PFLAC,S,ID,A4AA4E
$PFLAC,S,ACFT,1
$PFLAC,S,NMEAOUT,71
$PFLAC,S,BAUD,2
$PFLAC,S,RANGE,65535
$PFLAC,S,VRANGE,500
$PFLAC,S,XPDR,2
$PFLAC,S,MODESALT,1
$PFLAC,S,ADSBRANGE,65535
$PFLAC,S,ADSBVRANGE,65535
$PFLAC,S,ADSBWARNINGS,1
$PFLAC,S,PCASRANGE,9260
$PFLAC,S,PCASVRANGE,610
$PFLAC,S,MODEC,1
$PFLAC,S,OWNMODEC,0
$PFLAC,S,PCASCALIBRATION,60
$PFLAC,S,PCASBEEP,1
$PFLAC,S,PCASPFLAU,0
$PFLAC,S,REBROADCASTSERVICES,255
$PFLAC,S,AUDIOOUT,0
$PFLAC,S,AUDIOVOLUME,100
$PFLAC,S,LOGINT,1
$PFLAC,S,PILOT,Livingston/StClair/Bernatz
$PFLAC,S,GLIDERID,N40AF
$PFLAC,S,GLIDERTYPE,LS6a
$PFLAC,S,COMPCLASS,15m
$PFLAC,S,PRIV,0
$PFLAC,S,NOTRACK,0


Rich L.
Try $PFAC,S,MODESALT,0

Richard,

On Sunday, May 30, 2021 at 4:12:03 PM UTC-4, Richard Pfiffner wrote:
On Sunday, May 30, 2021 at 7:50:42 AM UTC-7, wrote:
On Monday, May 17, 2021 at 11:23:32 AM UTC-5, Ramy wrote:
It was most certainly the aircraft ID.
But now you disabled mode c alerts all together. You may want to turn that back on.

Ramy
I re-enabled mode C yesterday and when flying again got the continuous conflict alerts. In flight I managed to turn the mode C off in the Flarm and the alerts went away. Is there something wrong with my configuration of the FLARM or transponder/ADSB that is causing this? My ADSB set up was just tested and passed, and I just generated a PAPR report for the flight yesterday and it was clean. I updated both my FLARM and Oudie firmware this year, so they should both be up to dare. My FLARM config file is:

$PFLAC,S,ADSBRANGE,65535
$PFLAC,S,ADSBVRANGE,65535

Why are you asking for it to look for every ADS-B target with 65 km horizontally and vertically (215,000')? You might be overwhelming it and this is a symptom.

Many of us depend upon configuration advice provided by the vendors.
I buy my stuff from Paul Remde (Cumulus Soaring).
Does anyone have concerns with how Paul advises to set-up the Flarm?

On Sunday, May 30, 2021 at 9:10:29 PM UTC-5, Guy Acheson wrote:
Many of us depend upon configuration advice provided by the vendors.
I buy my stuff from Paul Remde (Cumulus Soaring).
Does anyone have concerns with how Paul advises to set-up the Flarm?
Guy,

Paul has been very helpful to us on several problems. I set up the FLARM per his instructions, and also the transponder that we bought from him (Trig TT22 with TN72 GPS). Of course I might have missed something...

Rich L.

I agree with Dan about the insane ranges. I recall Paul recommended it only for testing, otherwise you will get alert for every airliner at cruising altitude. However I doubt this is related to the false alarms. Is your mode S ID set correctly in the flarm config?

Ramy

On Monday, May 31, 2021 at 1:56:49 PM UTC-7, wrote:
On Sunday, May 30, 2021 at 9:10:29 PM UTC-5, Guy Acheson wrote:
Many of us depend upon configuration advice provided by the vendors.
I buy my stuff from Paul Remde (Cumulus Soaring).
Does anyone have concerns with how Paul advises to set-up the Flarm?
Guy,

Paul has been very helpful to us on several problems. I set up the FLARM per his instructions, and also the transponder that we bought from him (Trig TT22 with TN72 GPS). Of course I might have missed something...

Rich L.