Messages

1

Technical Support / Re: Occasional Insanely Loud White Noise

« on: June 07, 2017, 12:24:56 pm »

I've been searching the forum and found a couple of posts that talk of this PSU (or similar). One reported seeing wide band noise but then no further information, others seemed to use with no problem, but of course if it is frequency / load dependent then it may be present, they just haven't seen it.
A couple of threads had people with access to emission testing equipment and said they might test these units, but nothing ever appeared with any results that I can find.
It would be useful to get a definitive answer as these psu modules are physically ideal for box integration.
I would have thought that an eventual natural PAW progression might be to offer a fully packaged, plug and play box for sale and that a working integrated PSU would be needed  for such an item. I suspect that such a box will be needed to provoke mass appeal of PAW to "non tech" pilots.
Thanks Paul for the thread link, this was one I also had found.

2

Technical Support / Re: Occasional Insanely Loud White Noise

« on: June 07, 2017, 11:50:33 am »

Yes I agree that these things are hit and miss.
I did take a spectrum analyser with pick up loop to it before use and didn't see anything particularly significant in the aeronautical band. However as the interference seems to come and go it may well be load dependent so not easy to see.
Yes the Anker USB units are nice but not really easy for integrating into a single box system.
Having said that I have previously de-gutted a similar unit and re packaged the electronics. Seems like this may be the way to go if my interference returns.
Shame, the format of the CPT units was ideal and easy for integrated packaging.

3

Technical Support / Re: Occasional Insanely Loud White Noise

« on: June 07, 2017, 12:57:30 am »

Just to add to this thread, I am aware of at least 2 more aircraft that have had this problem, one of which I am responsible for. The noise was intermittent lasting for several seconds at a time and could not be suppressed with squelch on the Trig comm. It seemed to be frequency dependent (130.425) as changing to alternative frequency (126.4) did not show the problem. (at least in the short time I listened). Back on the ground, when I changed my power wiring to connect the PAW/Flarm to an alternative circuit breaker instead of the "avionics" circuit breaker (mainly so I could easily turn PAW off in flight), to my surprise the problem seemed to have gone away and the comm was working normally. I flew for around again for some 30 minutes with no sign of the noise. However as I remarked earlier it seemed to be frequency dependent so I cannot  say that is was not on other frequencies! I have not had time to further research the effect but will try to listen on some different channels next time I'm at the airfield.
On the other aircraft reported (which I am not directly involved in) the owner tried moving the power to another CB like mine but this did not seem to cure his problem.
We are wondering if it is coming from the 12-5V regulators we are using and he is now going to try a car style USB PSU to see if it makes a difference. On the bench he reported hearing similar noise on a hand held up to 12 inches away with original PSU, but nothing with a car USB PSU. I'm waiting to hear from him if he has made any further tests.
I will add to this thread if and when we learn more but at the moment we are suspicious that it is the PSU chip radiating.
FYI the PSU we are using is a 3A block regulator from e-bay.(DC/DC Converter Regulator 12V Stepdown to 5V 3A 15W Car Power Supply Module. eBay item number:152563993051)

4

General Discussion / Re: outside antenna/s

« on: May 27, 2017, 11:03:07 pm »

As PAW uses same frequency band as FLARM, then FLARM antennas can be used. FYI; LX Avionics do external mount FLARM and ADSB antennas that can be airframe mounted. (with suitable inspector approval)

5

General Discussion / Re: Radar3D - New Pilot Aware traffic display.

« on: January 26, 2017, 09:28:33 pm »

Thanks for info about IOS, I suspect a bunch of us would be prepared to make small contribution each to pay Apple fee if needed ?
Also some of us have Windows phones and tablets, maybe an alternative also ?
great work
Alan

6

General Discussion / Re: Radar3D - New Pilot Aware traffic display.

« on: January 25, 2017, 04:23:31 pm »

Really nice display, congratulations.
A couple of comments;
does it remember last used settings when opening ?
Any chance of iPad (ios) version in future as many of us have iPads for display ?
regards

7

General Discussion / Re: Radar settings

« on: December 08, 2016, 10:03:45 am »

Add my yes please save somehow, just one more thing to adjust when using in present version. I'm not sure it has to be saved on client, would be happy to save on PI and have last used Radar on any/all clients.
regards
Alan

8

General Discussion / Re: case for all the bits and speaker

« on: December 04, 2016, 07:04:47 pm »

I used this box to mount PAW and 12V-5V PSU module. I had 2 RS232/USB cables to interface to FLARM and TRIG via the 9 pin D connector. Audio I fed out with 3.5mm socket. So box takes 12V A/C power in + FLARM info in + GPS data out to TRIG. Antennas use the PAW SMA  + ADSB BNC. Box is 150x100x55 mm

http://spiratronics.com/black-abs-box-150-x-100-x-55-mm.html

9

General Discussion / Radar settings

« on: December 04, 2016, 06:35:34 pm »

I like the radar display, however using on my iPad it seems that "last used settings" are not remembered. If I go to home screen then back to radar it comes up with default range and mode. Similarly when first starting it comes with defaults. Is their any chance/way PAW could remember last used radar settings ?
regards
Alan

10

Technical Support / Latest PAW audio alerts

« on: December 04, 2016, 01:21:12 pm »

Just downloaded and tried the latest software, Great !!

However a question ? are the audio warning profile box sizes fixed (vert and horiz) ?
I thought I understood at Flyer presentation that the box sizes were user configurable but I can't see any set up input ?

As an aside the radar works fine on my iPad and Win 10 P/C, however my windows phone connects and shows the radar screen but never updates, just shows the initial position frozen. If I manually refresh then it refreshes but resets distance parameters to original defaults. Not a biggy but just to warn any other windows phone users that radar doesn't seem to work correctly.

Minor confusion; the update web page download shows a version of 20161201 but the actual version seems to be 21061124 !

Great effort guys, really becoming a leader and a "must have" for any aircraft. The audio alerts are a great safety step forward.

11

General Discussion / Re: FL*RM Integration - Beta Testers

« on: October 26, 2016, 04:43:15 pm »

16.30 26/10/16
Well, first the good news, Redbox Flarm does O/P $pflaa string when it sees a target.
The problem (which I guess we already knew) is that flarm is very low powered at UHF frequencies and the aircraft flarm antenna polar diagrams (both vertical and horizontal) are horrible on most installations.
Today I borrowed a LX mobile flarm box and took it home. Immediately my redbox started to give $pflaa strings. I then walked a line of sight approx 200 meters to verify it still gave the string with some separation. So far all ok but still no sign of real aircraft.
I then moved my dipole flarm antenna outside the double glazed window and waited. To my delight I finally saw A/C in the circuit at Halton (4Kms). The contacts were very dependent on the source A/C orientation, with A/C facing the contact would be poor unless close, or tail on virtually nothing and contact would disappear. Side on was by far the best. Bearing in mind A/C were typically 1000 ft above me, when facing me the A/C flarm antenna was probably trying to look down through the engine.
To sumarise; it works, best range I saw was 5Kms but indication is very dependent on relative positions vert. and horiz., and orientations. It is likely that the flarm contact in practise will be pretty close before you see him although of course the flarm LED display will still give warning of imminent collision but it will be close !
It will be interesting to compare PAW results which should give better range contact indications because of the higher power. As always antenna positioning is everything for best results.
regards
Alan

12

General Discussion / Re: FL*RM Integration - Beta Testers

« on: October 24, 2016, 10:57:25 pm »

Richard, I'm most intrigued, no I don't see any empty $pflaa strings from my Redbox and I'm surprised I wouldn't have expected any with no contacts.
I do see $pflau strings which are part of the Flarm alarm protocol if I understand correctly.
The plot thickens !
regards
Alan

Alan,
    At home I'm nowhere near any FLARM traffic so testing at home for positive targets is a nonstarter., but looking at the strings in hypeterminal I see the $pflaa strings along side the GPS position strings but no actual traffic to report. Do you get the empty $pflaa strings?
[/quote]

13

General Discussion / Re: FL*RM Integration - Beta Testers

« on: October 24, 2016, 10:14:05 pm »

Richard, Glad it is sorted.
I'm most uneasy about my set up. Today I monitored the data strings coming out of the Redbox looking for the $pflaa string that gives position of other Flarm aircraft. At the same time I monitored flarm aircraft on Open Glider Network to see when anyone come close. Well I'm on the edge of the circuit at Halton and today flarm aircraft were doing circuits so I had several movements varying between 5 Kms and 1 Km from me. ( I could see them visually). To my disappointment I did not see even one $pflaa string coming from the flarm box. Very strange, it is part of flarm protocol surely LX haven't missed it out !
I've sent email to LX asking the question but I'm really puzzled why it doesn't seem to work.  Well Wednesday I guess we will have definitive test, so fingers crossed .
Alan

14

General Discussion / Re: FL*RM Integration - Beta Testers

« on: October 23, 2016, 10:31:39 pm »

Richard, unfortunately I am not using any "supplied" cables, I just have the box and made my own Farnell USB to RJ11 connector cable.
I'm not sure what manual you are looking at but the one I got off the net seems correct;
pin 1 RJ11 (is white in mine) and goes to pin 5 RS232
pin 2 RJ11 is black and goes to pin 3 RS232   (from RJ11 RX) to RS232 Tx
pin 3 RJ11 is red and goes to pin 2 RS232      (from RJ11 Tx) to RS232 Rx

I have 2 different Flarm display leads (from a previous installation) with RJ11 each end and the colour code wires are completely different colours  on each cable so you cannot go by colour you have to visually look and better still ohm meter up to find what pins 1 2 and 3 are connected to on the open end.

I'm not sure what you are actually seeing on the RJ11 to Dsub, but to work it certainly should be wired as a Xover i.e. pin 2 to 3 and pin 3 to 2
hope this helps,
regards
Alan

15

General Discussion / Re: FL*RM Integration - Beta Testers

« on: October 23, 2016, 12:56:06 pm »

OK Ian, it looks like it could be productive for both of us to get together with 2 active Flarms and find out if they really see one another.
I wait your PM, I'm pretty much free anytime.
I have sent e-mail to LX asking them to confirm O/P of LAA string from their box, let's see if they respond
regards
Alan