Flarm / Oudie issues

[Nick Kennedy[_3_]]

Hi All
Just got back from 3 weeks of flying in Ephrata and Nephi.

I have random issues with Flarm targets not showing up on my Oudie.

After several years of perfect functionality, Its not working so well now


So this spring I updated my Flarm Firmware, My Flarm net data base and my Oudie to all the latest versions of software.

Flying this year, Often times targets would not show up even though they were 50' away on the ramp, while most targets that did show up came in at very long range, often 10 miles+ out. Sometimes not though and I'd lose targets at 2-3 miles. Or less. Very random performance.

I lost all the targets I.D. which I used to have.

Does anyone know where my problem lies?

In the latest Flarm update?

In the latest Oudie update?

Is it in the Flarmnet data base update?

I checked my Flarm performance in the range analyzer and It came in as very good.
Some others reported they could see my I.D. but not all.

All ADS-S targets came in OK
Any ideas from the Pro's out there?
Anyone experiencing these problems this season?
Where should I start?
Thanks in advance.
Nick

[Dan Marotta]

I had similar problems recently after installing the latest Flarm
update.Â* I eventually went back to the Flarm configuration tool and
redid my Flarm config file.Â* IIRC, I then had to make some manual
changes to the config file and, after reloading that, everything worked
again.Â* It was very tiresome!

On 7/14/2019 10:26 AM, Nick Kennedy wrote:
> Hi All
> Just got back from 3 weeks of flying in Ephrata and Nephi.
>
> I have random issues with Flarm targets not showing up on my Oudie.
>
> After several years of perfect functionality, Its not working so well now
>
>
> So this spring I updated my Flarm Firmware, My Flarm net data base and my Oudie to all the latest versions of software.
>
> Flying this year, Often times targets would not show up even though they were 50' away on the ramp, while most targets that did show up came in at very long range, often 10 miles+ out. Sometimes not though and I'd lose targets at 2-3 miles. Or less. Very random performance.
>
> I lost all the targets I.D. which I used to have.
>
> Does anyone know where my problem lies?
>
> In the latest Flarm update?
>
> In the latest Oudie update?
>
> Is it in the Flarmnet data base update?
>
> I checked my Flarm performance in the range analyzer and It came in as very good.
> Some others reported they could see my I.D. but not all.
>
> All ADS-S targets came in OK
> Any ideas from the Pro's out there?
> Anyone experiencing these problems this season?
> Where should I start?
> Thanks in advance.
> Nick

--
Dan, 5J

[Tim Taylor]

Dan, please provide details of what you did. I have not had Flarm target ID’s on my Oudie since last August. I also can not add gliders to my buddy list.

[Dan Marotta]

Hi Tim,

Go to the Flarm website and use the configuration tool
<https://flarm.com/support/tools-software/flarm-configuration-tool/>.

Log in if you have an account, if not, it might be good to do so. Enter
data applicable to your ship.Â* If I didn't know any better, I used the
defaults.Â* After running the tool, the flarmcfg.txt file was downloaded
automatically.

Place the flarmcfg.txt file in the root of an SD card or USB stick
whichever is applicable to your device.Â* Insert the device and power on
your device.Â* After the configuration is complete, remove the device.Â*
This should at least get you started.Â* I found initially that I got
alerts on my own glider which was very distracting.Â* The fix was, IIRC,
to go back to the default settings in the flarmcfg.txt file.

That should get you started.

Dan





On 7/14/2019 1:16 PM, Tim Taylor wrote:
> Dan, please provide details of what you did. I have not had Flarm target ID’s on my Oudie since last August. I also can not add gliders to my buddy list.

--
Dan, 5J

[Craig Reinholt]

On Sunday, July 14, 2019 at 10:26:56 AM UTC-6, Nick Kennedy wrote:
> Hi All
> Just got back from 3 weeks of flying in Ephrata and Nephi.
>
> I have random issues with Flarm targets not showing up on my Oudie.
>
> After several years of perfect functionality, Its not working so well now
>
>
> So this spring I updated my Flarm Firmware, My Flarm net data base and my Oudie to all the latest versions of software.
>
> Flying this year, Often times targets would not show up even though they were 50' away on the ramp, while most targets that did show up came in at very long range, often 10 miles+ out. Sometimes not though and I'd lose targets at 2-3 miles. Or less. Very random performance.
>
> I lost all the targets I.D. which I used to have.
>
> Does anyone know where my problem lies?
>
> In the latest Flarm update?
>
> In the latest Oudie update?
>
> Is it in the Flarmnet data base update?
>
> I checked my Flarm performance in the range analyzer and It came in as very good.
> Some others reported they could see my I.D. but not all.
>
> All ADS-S targets came in OK
> Any ideas from the Pro's out there?
> Anyone experiencing these problems this season?
> Where should I start?
> Thanks in advance.
> Nick

Nick,
You might want to do a factory reset. Multiple threads in the past discuss that.
Here is the basic command. I stole this from JS's post a couple of years ago. I've used it successfully in the past. Remove the # sign to activate the command. After the reset, I used the config tool to redo my config file. Works fine(ish) now.

# Original reset line. Clears PowerFlarm, sets all parameters to default values
# $PFLAC,S,DEF

# Complete factory reset. Use once in a one-line config file.
# $PFLAR,99

Craig

[Richard Pfiffner[_2_]]

On Sunday, July 14, 2019 at 2:27:28 PM UTC-7, Craig Reinholt wrote:
> On Sunday, July 14, 2019 at 10:26:56 AM UTC-6, Nick Kennedy wrote:
> > Hi All
> > Just got back from 3 weeks of flying in Ephrata and Nephi.
> >
> > I have random issues with Flarm targets not showing up on my Oudie.
> >
> > After several years of perfect functionality, Its not working so well now
> >
> >
> > So this spring I updated my Flarm Firmware, My Flarm net data base and my Oudie to all the latest versions of software.
> >
> > Flying this year, Often times targets would not show up even though they were 50' away on the ramp, while most targets that did show up came in at very long range, often 10 miles+ out. Sometimes not though and I'd lose targets at 2-3 miles. Or less. Very random performance.
> >
> > I lost all the targets I.D. which I used to have.
> >
> > Does anyone know where my problem lies?
> >
> > In the latest Flarm update?
> >
> > In the latest Oudie update?
> >
> > Is it in the Flarmnet data base update?
> >
> > I checked my Flarm performance in the range analyzer and It came in as very good.
> > Some others reported they could see my I.D. but not all.
> >
> > All ADS-S targets came in OK
> > Any ideas from the Pro's out there?
> > Anyone experiencing these problems this season?
> > Where should I start?
> > Thanks in advance.
> > Nick
>
> Nick,
> You might want to do a factory reset. Multiple threads in the past discuss that.
> Here is the basic command. I stole this from JS's post a couple of years ago. I've used it successfully in the past. Remove the # sign to activate the command. After the reset, I used the config tool to redo my config file. Works fine(ish) now.
>
> # Original reset line. Clears PowerFlarm, sets all parameters to default values
> # $PFLAC,S,DEF
>
> # Complete factory reset. Use once in a one-line config file.
> # $PFLAR,99
>
> Craig

After you do a Complete factory reset. Put the 6.67 firmware and your FLARMCFG file
on a clean USB drive and put in the PowerFlarm.

Richard
www.craggyaero.com

[Nick Kennedy[_3_]]

Craig
The factory reset sounds like a good idea at this point.
I hope that fixes the I.D. problem too.
Should be straightforward.
Richard
Should I put my USB stick in the dishwasher?
You said clean

[zach yama]

I have been having almost the same issue and posted about it a few weeks back. I seem to display all flarm targets but only show their ICAO hexidecimal code, not their ID from the flarmnet database. When I ran XC soar on my Oudie with the propper flarmnet data set active, the targets and IDs were displayed perfectly, leading me to believe this is a problem with the current Oudie firmware. I have reached out to Naviter who has not provided a solution. I will reset my FLARM and post my results here.

[krasw]

It's known Oudie bug, no other possibilities than wait for a fix.

[George Haeh]

Latest Oudie update shows IDs.

Current FlarmNet download page:

LXNAV and Naviter
20190715.fln

Copy to RADAR folder

[Tim Taylor]

On Monday, July 15, 2019 at 9:53:44 AM UTC-6, George Haeh wrote:
> Latest Oudie update shows IDs.
>
> Current FlarmNet download page:
>
> LXNAV and Naviter
> 20190715.fln
>
> Copy to RADAR folder

George,

Please post what version of the SeeYou software you are using. I am using 9.15.01 and could not see Flarm ID's last week.

Tim

[Richard Pfiffner[_2_]]

On Monday, July 15, 2019 at 9:04:52 AM UTC-7, Tim Taylor wrote:
> On Monday, July 15, 2019 at 9:53:44 AM UTC-6, George Haeh wrote:
> > Latest Oudie update shows IDs.
> >
> > Current FlarmNet download page:
> >
> > LXNAV and Naviter
> > 20190715.fln
> >
> > Copy to RADAR folder
>
> George,
>
> Please post what version of the SeeYou software you are using. I am using 9.15.01 and could not see Flarm ID's last week.
>
> Tim

I also can not see Contest IDs. SeeYou PNA9.15.001 20190715.fln

Bench Testing with two PowerFlarm units and Ultimate running SeeYou PNA 9.15.001.

Richard
www.craggyaero.com

[Ramy[_2_]]

Contest ID not showing is unlikely an issue with the powerflarm but with your display. Since most complaints are about the Oudie I suspect the issue is with the Oudie, or the flarmnet file (wrong format perhaps)?
I don’t have these issues with latest firmwares neither in Xcsoar nor LX9000. The only contest ID not showing is for those which have yet to enter their info on flarmnet (nearly half the pilots apparently find it too challenging).
Reception vary significant between installations, some show up 5 miles while others less than a mile.
If you see someone consistently from more than 5 miles you most likely see their ADSB signal, not flarm signal (the target will look exactly the same in some displays).

Ramy

[George Haeh]

Running 9.15.001

Settings -> Flarm brings up:
Settings - Radar page

Labels Show box is checked.

The IDs were not showing just before the 9.15 upgrade

[Richard Pfiffner[_2_]]

On Tuesday, July 16, 2019 at 8:28:37 AM UTC-7, George Haeh wrote:
> Running 9.15.001
>
> Settings -> Flarm brings up:
> Settings - Radar page
>
> Labels Show box is checked.
>
> The IDs were not showing just before the 9.15 upgrade


Running v9.15.001

20190715.fln in the Radar Folder of Oudie and PNA
I have on both the Oudie and the SeeYou mobile PNA the settings - Radar Page - Labels Show Box Checked.

Still no Contest ID.

Richard
www.craggyaero.com

[[email protected]]

On Tuesday, July 16, 2019 at 3:03:22 AM UTC-4, Ramy wrote:
> Contest ID not showing is unlikely an issue with the powerflarm but with your display. Since most complaints are about the Oudie I suspect the issue is with the Oudie, or the flarmnet file (wrong format perhaps)?
> I don’t have these issues with latest firmwares neither in Xcsoar nor LX9000. The only contest ID not showing is for those which have yet to enter their info on flarmnet (nearly half the pilots apparently find it too challenging).
> Reception vary significant between installations, some show up 5 miles while others less than a mile.
> If you see someone consistently from more than 5 miles you most likely see their ADSB signal, not flarm signal (the target will look exactly the same in some displays).
>
> Ramy

Any tips on how to record the FLARM IDs seen in flight if the contest ID is not available (missing from FlarmNet data)? It's a hassle to write them down by hand, but they are not recorded in the flight log (except perhaps in the encrypted LFLA lines). I wish my glide computer (Tophat) would let me add the ID seen to the data file with one tap, then I can try and add the contest ID to it later.

[George Haeh]

I'm using a slightly older.fln file.

My new Core 1.1 is powered by my Air Glide S which is connected to my Oudie with an NMEA adapter.

$PFLAC,S,NMEAOUT1,81
$PFLAC,S,BAUD1,2
$PFLAC,S,NMEAOUT2,81
$PFLAC,S,BAUD2,2

[[email protected]]

Guys,

thank you very much for this conversation, it helped us pinpoint the problem.

We did have an issue with broken FLN files and when we fixed that we thought that that's "that".

But it turns out that there was another problem with how Power Flarm transmits its ICAO code. We have a new beta version that fixes that. I am very sure that the fix works but it would be incredibly useful if someone who had this problem could test it and report back before we release it:

If you able to test this version please send an email to support at naviter dot com and we'll be glad to give you access to it.

Thanks,
Andrej Kolar
Naviter.com

On Tuesday, July 16, 2019 at 6:12:46 PM UTC+2, Richard Pfiffner wrote:
> On Tuesday, July 16, 2019 at 8:28:37 AM UTC-7, George Haeh wrote:
> > Running 9.15.001
> >
> > Settings -> Flarm brings up:
> > Settings - Radar page
> >
> > Labels Show box is checked.
> >
> > The IDs were not showing just before the 9.15 upgrade
>
>
> Running v9.15.001
>
> 20190715.fln in the Radar Folder of Oudie and PNA
> I have on both the Oudie and the SeeYou mobile PNA the settings - Radar Page - Labels Show Box Checked.
>
> Still no Contest ID.
>
> Richard
> www.craggyaero.com

[[email protected]]

Problem fixed. Thank you Tim Taylor and Richard (Craggy Aero) for confirming this with a live test!

You can download the corrected version here:
http://download.naviter.com/oudie_all/UpdateOudie.exe

or wait until after the weekend, when it becomes available through the Naviter Updater.

Along the way, a new feature was added for all those who will participate in the Pan-American championships - Pressing the Pilot Event button will forward this event also to a Flarm / PowerFlarm if connected.

Have a great weekend!
Andrej Kolar
Naviter.com

On Wednesday, July 24, 2019 at 3:01:49 PM UTC+2, wrote:
> Guys,
>
> thank you very much for this conversation, it helped us pinpoint the problem.
>
> We did have an issue with broken FLN files and when we fixed that we thought that that's "that".
>
> But it turns out that there was another problem with how Power Flarm transmits its ICAO code. We have a new beta version that fixes that. I am very sure that the fix works but it would be incredibly useful if someone who had this problem could test it and report back before we release it:
>
> If you able to test this version please send an email to support at naviter dot com and we'll be glad to give you access to it.
>
> Thanks,
> Andrej Kolar
> Naviter.com
>
> On Tuesday, July 16, 2019 at 6:12:46 PM UTC+2, Richard Pfiffner wrote:
> > On Tuesday, July 16, 2019 at 8:28:37 AM UTC-7, George Haeh wrote:
> > > Running 9.15.001
> > >
> > > Settings -> Flarm brings up:
> > > Settings - Radar page
> > >
> > > Labels Show box is checked.
> > >
> > > The IDs were not showing just before the 9.15 upgrade
> >
> >
> > Running v9.15.001
> >
> > 20190715.fln in the Radar Folder of Oudie and PNA
> > I have on both the Oudie and the SeeYou mobile PNA the settings - Radar Page - Labels Show Box Checked.
> >
> > Still no Contest ID.
> >
> > Richard
> > www.craggyaero.com

[[email protected]]

Please read this about adding buddies when they are not present in FlarmNET file:
https://www.naviter.com/2018/06/oudie-8-comps-with-your-buddies/

The article focuses on OGN buddies, but it works just the same with regular Flarm targets.

Regards,
Andrej Kolar
Naviter.com

On Tuesday, July 16, 2019 at 10:41:12 PM UTC+2, wrote:
> On Tuesday, July 16, 2019 at 3:03:22 AM UTC-4, Ramy wrote:
> > Contest ID not showing is unlikely an issue with the powerflarm but with your display. Since most complaints are about the Oudie I suspect the issue is with the Oudie, or the flarmnet file (wrong format perhaps)?
> > I don’t have these issues with latest firmwares neither in Xcsoar nor LX9000. The only contest ID not showing is for those which have yet to enter their info on flarmnet (nearly half the pilots apparently find it too challenging).
> > Reception vary significant between installations, some show up 5 miles while others less than a mile.
> > If you see someone consistently from more than 5 miles you most likely see their ADSB signal, not flarm signal (the target will look exactly the same in some displays).
> >
> > Ramy
>
> Any tips on how to record the FLARM IDs seen in flight if the contest ID is not available (missing from FlarmNet data)? It's a hassle to write them down by hand, but they are not recorded in the flight log (except perhaps in the encrypted LFLA lines). I wish my glide computer (Tophat) would let me add the ID seen to the data file with one tap, then I can try and add the contest ID to it later.

[Nick Kennedy[_3_]]

Yea Andrej
Thanks for fixing this glitch.
Next week I'm going to pull my plane in the shop and reset my Flarm and reload my confiq and update file, hope it all works.

[Nick Kennedy[_3_]]

Hello
Did anyone apply Naviters Patch fix to there Oudie this weekend and fly with it?

Did it work?

I downloaded it and it came up as a non updated version of the last update.001

[Richard Pfiffner[_2_]]

On Monday, July 29, 2019 at 6:37:35 AM UTC-7, Nick Kennedy wrote:
> Hello
> Did anyone apply Naviters Patch fix to there Oudie this weekend and fly with it?
>
> Did it work?
>
> I downloaded it and it came up as a non updated version of the last update.001

The update on the web is 9.15.001 and it is NOT the update that fixes the problem.

The update will be available in the near future.

I have tested beta v 9.16.001 and it shows the Flarm contest IDs

Richard
www.craggyaero.com