Well I took the assembled bunch of goodies flying today, to N.Weald and back and when it worked it worked fine (*), although you could spend too much time watching the screen, luckily there was two of us so one flew and one "tinkered".
I think that you cannot monitor all the time for a conflicting aircraft, you would spend far too much time screen watching and not enough out of the window scanning. It really needs to make use of the audio output on the Pi to alert you to conflicting traffic. You would then wire this into one of the inputs to your intercom system so you get an audible indication which draws your attention to a possible conflict.
I read on another thread the suggestion that all you really need is the type of "pseudo radar" type display like you get on XC-soar because in reality you are not interested in other contacts that are more than say 5km away, so another suggestion, not a radar display, but perhaps filter out, on the Paw, all traffic say >5km (configurable) from present position before sending it to the RunwayHD/Skydemon app for displaying, it makes the navscreen less busy.
* - as I said in the first sentence when it works it works fine, but we were constantly troubled by "loss of flarm" messages on RunwayHD. Looking at the PAW log there seems to be an almost constant repetition of:
listening for connection
listening port 2000
disconnected descriptor=14
pin 6001
connected runwayhd
disconnected descriptor=10
accepted 2000
connected descriptor =15
listening for connection
pin 6001
connected runwayhd
disconnected descriptor=10
accepted 2000
connected descriptor =15
and so on - I have retyped this in order of arrival in the log rather than the reverse way they are displayed as the log is on the Ipad and I am writing this on the lappy.
So would be interested in reasons why this may be happening. Even at home with it all running it does the same/similar with RunwayHD (latest version today), so perhaps there is a difference between the type of input messages expected by RunwayHD and the type actually being sent by the PAW. I see PilotAware is actually named on the Flarm Settings screen now in RunwayHD as one of 4 possible selections. Do other systems use other message formats to display conflicting traffic ?
John