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

[Richard Livingston[_2_]]

I recently installed a Trig TT22 transponder in our LS6. Today I got to fly it for the first time and I was getting constant conflict alarms on my Oudie about traffic at (for e.g.) my "6 O'Clock and 35ft above me" The only way I could figure out how to silence these alarms was to set my transponder to "ON" (i.e. no altitude reporting). Naturally my PAPR report showed a failure on both pressure and GPS altitude.

I've been trying to figure out how to configure either the FLARM or the Oudie to ignore my own emissions but so far with no luck. Does anyone out there know how to fix this?

Rich L.

[5Z]

Been there, done that!
You need to tell the FLARM to ignore your own Mode S/ADSB transmissions.
Key items in the config file are, I believe:
# Mode S code
$PFLAC,S,ID,xxxxxx
# configure aircraft type
$PFLAC,S,ACFT,1
# Mode C Filtering 0-Aggressive 1-Normal
$PFLAC,S,OWNMODEC,0


On Thursday, May 13, 2021 at 6:48:10 PM UTC-7, wrote:
> I recently installed a Trig TT22 transponder in our LS6. Today I got to fly it for the first time and I was getting constant conflict alarms on my Oudie about traffic at (for e.g.) my "6 O'Clock and 35ft above me" The only way I could figure out how to silence these alarms was to set my transponder to "ON" (i.e. no altitude reporting). Naturally my PAPR report showed a failure on both pressure and GPS altitude.
>
> I've been trying to figure out how to configure either the FLARM or the Oudie to ignore my own emissions but so far with no luck. Does anyone out there know how to fix this?
>
> Rich L.

[Roy B.]

I had the same problem after I updated my FLARM firmware this year. I made the mistake of using the same memory stick that had last year's update on it. The problem was solved when I reloaded using a formatted stick with only the update on it. I also reloaded my config file from a previously formatted stick.

BUT: For some reason the problem still briefly re emerges when I fly near certain military installations. I don't understand why that happens - and it's only intermittent.
ROY

[Richard Livingston[_2_]]

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.

[Roy B.]

> 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.
>

Rich
You are welcome. If the problem re-emerges intermiently, please let me know. Mine still does it once in a while. Yesterday in a 7.5 hour XC flight I got what I call the "chasing your own tail" alarm about 3 times that stopped when I hit the "dismiss" button. It seems to happen near a large Air Force base and a practice drop zone the AF uses. I have no idea why.
ROY

[Ramy[_2_]]

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.

[Richard Livingston[_2_]]

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.

[Richard Pfiffner[_2_]]

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,

[Dan Daly[_2_]]

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.

[Guy Acheson[_2_]]

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?

[Richard Livingston[_2_]]

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.

[Ramy[_2_]]

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.

[Jonathan St. Cloud]

On Tuesday, June 1, 2021 at 9:35:09 AM UTC-7, Ramy wrote:
> 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.
I am having the same issues: Flarm and transponder see each other as enemies. This is my config file:
$PFLAC,S,DEF
$PFLAC,S,ID,A2CEDC
$PFLAC,S,ACFT,1
$PFLAC,S,NMEAOUT1,41
$PFLAC,S,BAUD1,2
$PFLAC,S,NMEAOUT2,41
$PFLAC,S,BAUD2,2
$PFLAC,S,RANGE,65535
$PFLAC,S,VRANGE,2000
$PFLAC,S,AUDIOOUT,0
$PFLAC,S,AUDIOVOLUME,100
$PFLAC,S,LOGINT,4
$PFLAC,S,PILOT,Jonathan S.
$PFLAC,S,GLIDERID,N280K
$PFLAC,S,GLIDERTYPE,ASG-29Es
$PFLAC,S,COMPCLASS,18 m
$PFLAC,S,COMPID,OK
$PFLAC,S,PRIV,0
$PFLAC,S,NOTRACK,0

[Mark Zivley[_3_]]

Jonathan,

You're missing the lines that state you have a transponder and what type and whether you prefer aggressive or normal filtering.

$PFLAC,S,MODEC,X
$PFLAC,S,OWNMODEC,X
$PFLAC,S,PCASCALIBRATION,30
$PFLAC,S,XPDR,X
$PFLAC,S,MODESALT,X

these are from my file, but since my transponder may be different than yours I've changed the values to an "X" so you'll need to get the correct values based on your setup.

A better recommendation is to go to the Flarm web site and use their configuration tool. It has gotten better than it was.

https://flarm.com/support/tools-software/flarm-configuration-tool/

It's a bit techy, but then you'll end up with a file that should work better than the somewhat limited file you included below.

I would recommend to check the box that says "advanced settings". Just don't adjust the items about baud rates, protocol, or data sentences. Most of the rest makes sense to non EEs.

I would suggest to use the altitude that your transponder is sending out so that your Flarm and the transponder are sending the same altitude info. Maybe others recommend differently. Of course, this assumes that your transponder altitude calibration is accurate.

"Rebroadcast Services" is only for Flarm units in the US which also have the necessary license. If you have a Flarm Fusion or if you paid for the extra license for your core then you'll want to stay with the default value of ADS-R and TIS-B otherwise might as well select "none".

Mark



> I am having the same issues: Flarm and transponder see each other as enemies. This is my config file:
> $PFLAC,S,DEF
> $PFLAC,S,ID,A2CEDC
> $PFLAC,S,ACFT,1
> $PFLAC,S,NMEAOUT1,41
> $PFLAC,S,BAUD1,2
> $PFLAC,S,NMEAOUT2,41
> $PFLAC,S,BAUD2,2
> $PFLAC,S,RANGE,65535
> $PFLAC,S,VRANGE,2000
> $PFLAC,S,AUDIOOUT,0
> $PFLAC,S,AUDIOVOLUME,100
> $PFLAC,S,LOGINT,4
> $PFLAC,S,PILOT,Jonathan S.
> $PFLAC,S,GLIDERID,N280K
> $PFLAC,S,GLIDERTYPE,ASG-29Es
> $PFLAC,S,COMPCLASS,18 m
> $PFLAC,S,COMPID,OK
> $PFLAC,S,PRIV,0
> $PFLAC,S,NOTRACK,0

[Jonathan St. Cloud]

Thank you SO MUCH. I did use the Flarm config tool to make this config file. Will try again. Where do these lines go in the config file? I have a Garrechet mode S transponder. Thanks again!
On Tuesday, June 1, 2021 at 2:30:11 PM UTC-7, wrote:
> Jonathan,
>
> You're missing the lines that state you have a transponder and what type and whether you prefer aggressive or normal filtering.
>
> $PFLAC,S,MODEC,X
> $PFLAC,S,OWNMODEC,X
> $PFLAC,S,PCASCALIBRATION,30
> $PFLAC,S,XPDR,X
> $PFLAC,S,MODESALT,X
>
> these are from my file, but since my transponder may be different than yours I've changed the values to an "X" so you'll need to get the correct values based on your setup.
>
> A better recommendation is to go to the Flarm web site and use their configuration tool. It has gotten better than it was.
>
> https://flarm.com/support/tools-software/flarm-configuration-tool/
>
> It's a bit techy, but then you'll end up with a file that should work better than the somewhat limited file you included below.
>
> I would recommend to check the box that says "advanced settings". Just don't adjust the items about baud rates, protocol, or data sentences. Most of the rest makes sense to non EEs.
>
> I would suggest to use the altitude that your transponder is sending out so that your Flarm and the transponder are sending the same altitude info. Maybe others recommend differently. Of course, this assumes that your transponder altitude calibration is accurate.
>
> "Rebroadcast Services" is only for Flarm units in the US which also have the necessary license. If you have a Flarm Fusion or if you paid for the extra license for your core then you'll want to stay with the default value of ADS-R and TIS-B otherwise might as well select "none".
>
> Mark
> > I am having the same issues: Flarm and transponder see each other as enemies. This is my config file:
> > $PFLAC,S,DEF
> > $PFLAC,S,ID,A2CEDC
> > $PFLAC,S,ACFT,1
> > $PFLAC,S,NMEAOUT1,41
> > $PFLAC,S,BAUD1,2
> > $PFLAC,S,NMEAOUT2,41
> > $PFLAC,S,BAUD2,2
> > $PFLAC,S,RANGE,65535
> > $PFLAC,S,VRANGE,2000
> > $PFLAC,S,AUDIOOUT,0
> > $PFLAC,S,AUDIOVOLUME,100
> > $PFLAC,S,LOGINT,4
> > $PFLAC,S,PILOT,Jonathan S.
> > $PFLAC,S,GLIDERID,N280K
> > $PFLAC,S,GLIDERTYPE,ASG-29Es
> > $PFLAC,S,COMPCLASS,18 m
> > $PFLAC,S,COMPID,OK
> > $PFLAC,S,PRIV,0
> > $PFLAC,S,NOTRACK,0

[Ramy[_2_]]

The flarm configuration tool should have inserted these lines but unfortunately the tool is confusing. You need to select the option that you have ADSB receiver. All powerflarms have. And also enable the advance mode so you can set the ranges correctly. And then enter the ICAO/mode S code (even if you don’t have mode S transponder).

Ramy

On Wednesday, June 2, 2021 at 6:20:20 AM UTC-7, wrote:
> Thank you SO MUCH. I did use the Flarm config tool to make this config file. Will try again. Where do these lines go in the config file? I have a Garrechet mode S transponder. Thanks again!
> On Tuesday, June 1, 2021 at 2:30:11 PM UTC-7, wrote:
> > Jonathan,
> >
> > You're missing the lines that state you have a transponder and what type and whether you prefer aggressive or normal filtering.
> >
> > $PFLAC,S,MODEC,X
> > $PFLAC,S,OWNMODEC,X
> > $PFLAC,S,PCASCALIBRATION,30
> > $PFLAC,S,XPDR,X
> > $PFLAC,S,MODESALT,X
> >
> > these are from my file, but since my transponder may be different than yours I've changed the values to an "X" so you'll need to get the correct values based on your setup.
> >
> > A better recommendation is to go to the Flarm web site and use their configuration tool. It has gotten better than it was.
> >
> > https://flarm.com/support/tools-software/flarm-configuration-tool/
> >
> > It's a bit techy, but then you'll end up with a file that should work better than the somewhat limited file you included below.
> >
> > I would recommend to check the box that says "advanced settings". Just don't adjust the items about baud rates, protocol, or data sentences. Most of the rest makes sense to non EEs.
> >
> > I would suggest to use the altitude that your transponder is sending out so that your Flarm and the transponder are sending the same altitude info.. Maybe others recommend differently. Of course, this assumes that your transponder altitude calibration is accurate.
> >
> > "Rebroadcast Services" is only for Flarm units in the US which also have the necessary license. If you have a Flarm Fusion or if you paid for the extra license for your core then you'll want to stay with the default value of ADS-R and TIS-B otherwise might as well select "none".
> >
> > Mark
> > > I am having the same issues: Flarm and transponder see each other as enemies. This is my config file:
> > > $PFLAC,S,DEF
> > > $PFLAC,S,ID,A2CEDC
> > > $PFLAC,S,ACFT,1
> > > $PFLAC,S,NMEAOUT1,41
> > > $PFLAC,S,BAUD1,2
> > > $PFLAC,S,NMEAOUT2,41
> > > $PFLAC,S,BAUD2,2
> > > $PFLAC,S,RANGE,65535
> > > $PFLAC,S,VRANGE,2000
> > > $PFLAC,S,AUDIOOUT,0
> > > $PFLAC,S,AUDIOVOLUME,100
> > > $PFLAC,S,LOGINT,4
> > > $PFLAC,S,PILOT,Jonathan S.
> > > $PFLAC,S,GLIDERID,N280K
> > > $PFLAC,S,GLIDERTYPE,ASG-29Es
> > > $PFLAC,S,COMPCLASS,18 m
> > > $PFLAC,S,COMPID,OK
> > > $PFLAC,S,PRIV,0
> > > $PFLAC,S,NOTRACK,0