On Sunday, June 21, 2020 at 5:09:16 PM UTC-5, wrote:
I have a power core outputing to an Oudie, Butterfly display and SN10b.

I bought all the equipment during the glider purchase, and this is my first experience with all of these devices. I updated all the firmware and software with all the equipment and went flying. The butterfly display seems to be working correctly, however my Oudie was initially providing me sporadic warnings of an aircraft just slightly above and behind me, when there was noone there. I used another glider to confirm they were getting two targets for my ship.

I then used the flarm configuration tool to change the power core to match my transponder hex code and update my name. I now get constant, never ending flarm warnings on my oudie as soon as I start moving.

Also, I loaded on the latest flarmnet to make sure I had all the local ships' contest IDs instead of the hexcode for the targets. My butterfly display does not show the contest IDs but my Oudie does.

I'm at a loss to know what I need to do next. Any help would be appreciated.

I used the following txt file for my configuration:

$PFLAC,S,DEF
$PFLAC,S,ID,A6C7C2
$PFLAC,S,ACFT,1
$PFLAC,S,NMEAOUT1,71
$PFLAC,S,BAUD1,0
$PFLAC,S,NMEAOUT2,71
$PFLAC,S,BAUD2,2
$PFLAC,S,RANGE,65535
$PFLAC,S,VRANGE,500
$PFLAC,S,AUDIOOUT,0
$PFLAC,S,AUDIOVOLUME,100
$PFLAC,S,LOGINT,4
$PFLAC,S,CLEARLOGS
$PFLAC,S,PILOT,David Krautter
$PFLAC,S,GLIDERID,N536LS
$PFLAC,S,GLIDERTYPE,LS6c
$PFLAC,S,COMPCLASS,15m
$PFLAC,S,COMPID,XV
$PFLAC,S,PRIV,0
$PFLAC,S,NOTRACK,0

You must load the FlarmNet file to both the Oudie and the Butterfly display.. I'm guessing based on your problem statement that you missed loading it to the Butterfly. Steps are easy:

Butterfly firmware/FlarmNET update with PF Co
- Copy Butterfly firmware (.BFW) and/or flarmnet (.BFN)
to USB stick.
- Connect stick to Core.
- Switch on system with BF display knob pressed.
- Verify BF display goes into UPDATE MODE with 'WAITING', then 'LOADING'.
- Wait until BF display restarts (can take up to two minutes).


What version of PF firmware are you running? If 7.00 you need to downrev to 6.83 due to a bug in 7.00 that causes the exact problem you describe. If you're already on 6.83 then make sure your ICAO address is the same in both your PF config and your transponder.

Robert