Messages

1

Technical Support / Re: Transponder Aerial

« on: January 30, 2020, 08:12:03 am »

Peter, thanks for this. I did have it before on the coaming and have changed the aerial for the centre feed dipole. It was not aesthetically pleasing sticking up in view. I bit the bullet yesterday and located it in the rear fuselage which meant a lot of contortion and bruises. Tested as well and gave a good signal. I also located the PAW aerial as well (centre feed ) about a foot from the 1090 aerial, unable to test that as located in France. The PAW aerial is not so important as most of my flying is in France and I only venture across the channel a couple of times a year. Hopefully it will be OK though.

2

Technical Support / Re: Transponder Aerial

« on: January 29, 2020, 08:16:22 am »

Thanks everyone, My original was a cut down whip aerial and it was impossible to place on the coaming without being in line of sight or being too close to the compass.
I am going to try some experiments this morning with the centre feed dipole and see if I can find somewhere that is going to work.

3

Technical Support / Re: Transponder Aerial

« on: January 28, 2020, 09:59:52 pm »

Thanks for quick response. thought that may be the case!  I do have a centre feed dipole aerial from the shop but no where to locate it easily to keep it vertical (even with its short length) unless its internal to the wood wing and that is a nightmare. A fuel tank and Lycoming would preclude the most obvious location and if placed in the rear fuselage the only accessible spot that is vertical is just below the rear fuel tank. Horizontal would be fine but of course that is really going to limit signal strength. It maybe that ADS-B is strong enough to cope with this on a short range i.e. 20 Nm but I don't know. Adding another external aerial is an option but us Falco chaps are very concerned in adding drag to our fast flying machines.

4

Technical Support / Transponder Aerial

« on: January 28, 2020, 07:21:52 pm »

I might be being a little dense here!
I have had a PAW from nearly the word GO and it has worked fine except the Transponder receiver aerial is located in one of the few vertical positions in the cockpit (its a Falco and everything is curved or has large chunks of metal or fuel tanks in the way to obstruct signals). This results in some blind spots, I also have had for a while a Garrecht VY-01 Transponder with ADS-B output and external aerial linked to an MGL EFIS, again has worked fine.
Question is: Is there any reason why I cannot T a BNC connector into my Transponder aerial and connect to the PAW as well (with of course suitable connectors). I realise the Garrecht outputs a thunk through the aerial but as it also receives and the aerial is external then it may give me a better reception.
I have explored putting the aerial in the wing but this is heading towards the 'too hard tray'.
Have looked through the forum and cannot see this topic having been raised before.

5

Technical Support / Re: Installing 20190621 - SDFormat and Software upgrade

« on: July 20, 2019, 05:02:49 pm »

Pete, Thanks, that is what I guessed, will see what the MGL iEFIS thinks of it.

6

Technical Support / Re: Installing 20190621 - SDFormat and Software upgrade

« on: July 20, 2019, 11:08:24 am »

No problem in formatting or installing to a classic Rasp Pi. However on USB port 1 I have a RS232 converter Port 1 set to Traffic Dynon with a Baud rate of 19200. This interface enabled me to send traffic data to my MGL iEFIS for overlaid traffic data and give me MGL iEFIS traffic audio warnings. There is no such option in this version. Has it been renamed and if so to what??

7

Technical Support / Re: Raspberry Pi Monitor

« on: October 28, 2017, 04:18:00 am »

OK, makes sense. Would it also work with an Ethernet cable between the two RPi’s? Or does that knock out the WiFi from the PAW? It might be more economical to just buy a cheap Android tablet though.

8

Technical Support / Raspberry Pi Monitor

« on: October 23, 2017, 08:52:40 pm »

Raspberry Pi now have a 7” Display that connects directly with the Raspberry Pi Display connector, not the HDMI connector. It uses a fast DSI transfer rate with next to nothing EMI. So question is if this is connected to the PilotAware Pi Display connector can this then be used as a traffic display using the 'Radar' selection. I already have RS232 (via USB) working just fine and also WiFi to SkyDemon but I have some real estate spare on my panel and just having the radar display could be useful. Would it affect what is sent to the RS232 and WiFi?

9

Technical Support / Re: Pilotaware and Weather info

« on: October 19, 2017, 10:05:28 pm »

Any update on this position with UAT, I am very sure that we all do not need yet another WiFi device to be able to transmit to our iPads etc as we can only receive a single WiFi until we get multiplexing on WiFi. I am part of the FASVIG group VE11 that is supposed to be looking at in-cockpit weather. Regrettably most of the group seem to be ex-RAF who are either totally inactive or believe that an entrepreneurial solution is not the way forward. For sure, the CAA to fail to communicate with PilotAware is a total disgrace and does reflect their attitude. I am surprised that SkyDemon are not being proactive with PilotAware on the CAA UAT weather project. Where is the logjam on this, is it political? I cannot believe it can be political as SkyDemon are thankfully innovative and commercially they have everything to gain as well of course PilotAware.

10

General Discussion / Re: Cell connection (3g/4g (Ipad)) and PAW

« on: July 02, 2017, 02:10:08 pm »

I have no problems with PAW WiFi connection to SkyDemon and also a 4G service simultaneously using an iPad

11

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

« on: January 26, 2017, 08:17:55 pm »

Very impressive, I purchased a cheap Android for the radar display as per PAW which I thought was impressive. Just downloaded James's version to it, will use this instead. As for keeping an Android on. You can do this by turning on developer mode. Go to Settings, About, click fairly quickly seven times on Build Number and set to Developer. This gives you a lot more Settings options including being able to keep the screen on when the unit is charging. For an iPad etc you have to be more cunning. Download a tune called Silence on iTunes and play this on repeat!!

12

General Discussion / Re: Traffic on a MGL iEFS

« on: January 19, 2017, 05:26:15 pm »

Well I am glad my original post has born fruit. I shall implement this but have one concern with regard to the ground signal. For RS232 to work correctly a common ground is required I.e. The ground on the PAW should be the same as the ground on the iBox. Technically they will be the same but my PAW is nowhere near the iBox. All my Avionics has a common ground but the PAW is in the rear and plugged into a USB (non noisy Charge4) which is grounded on  the battery ground bus. Any suggestions apart from extra wiring to ensure a good signal would be appreciated.
Carlos, PS where abouts are you in Spain, hoping to be flying around in second half of Feb with two other PAW equipped a/c.

13

Technical Support / Re: The latest version and FLARM

« on: December 11, 2016, 06:14:51 pm »

Peter,

Really do appreciate this and am very sure if the theory evolves into reality then this has to be of benefit to many.
My MGL is away in S.Sfrica having a processor upgrade to give me virtual vision and my Falco is enjoying winter in the S of France so will not get a chance to test for real until February. It is that time of year when winter mods are made. Also built cooling fans into an iPad RAM mount if anyone is interested.

Thanks again.

14

Technical Support / Re: The latest version and FLARM

« on: December 08, 2016, 09:51:24 am »

Peter,

Good question on bearing less targets. If you have an example of RS232 bearing less targets data then I may be able to test this on the MGL simulator and also ask the question at MGL.

15

Technical Support / Re: The latest version and FLARM

« on: December 08, 2016, 08:31:44 am »

Peter,

Thanks for rapid response. PF is Core, currently uses Port 1 for RS232 to MGL and Port 2 for the Air Connect. I will plan to take Port 2 to the PAW which will then give me at least the extra of FLARM info on the iPad. But of course it would be nice to match both sets of data.
So now all I need to think about is taking the Radar Display into the MGL, just needs a PAL output from cheap WiFi enabled browser and direct into 1 of 4 of the Video inputs on the MGL.