Pilot controlled lighting / AWOS
Printed From: Avidyne
Category: Avidyne General
Forum Name: IFD 5 Series & IFD 4 Series Touch Screen GPS/NAV/COM
Forum Description: Topics on Avidyne's IFD 5 Series and IFD 4 Series Touch Screen GPS/NAV/COM
URL: http://forums.avidyne.com/forum_posts.asp?TID=740
Printed Date: 24 May 2024 at 4:30am
Software Version: Web Wiz Forums 12.01 - http://www.webwizforums.com
Topic: Pilot controlled lighting / AWOS
Posted By: comancheguy
Subject: Pilot controlled lighting / AWOS
Date Posted: 16 Jul 2015 at 12:44pm
|
I am having some difficulty getting my awos to "talk back". We have a superAwos that responds to 3 clicks with weather and 4 clicks with a radio check. I have to be very precise with my clicks neither too fast or too slow with my 540s. My Narco and my 530 worked with no fuss. Not complaining, but is anyone noticing this? I don't like what it portends for PCL. Ken |
Replies:
Posted By: mfb
Date Posted: 16 Jul 2015 at 1:09pm
|
I had one experience with PCL. I found the same thing - if you clicked too fast the transmitter didn't turn on and it didn't click at all. I was shooting an approach during the day and I'm not sure that I ever did get the approach lights turned on. Mike |
Posted By: edanford
Date Posted: 16 Jul 2015 at 1:42pm
|
I noticed this effect of being very hard to do clicks also on my last flight. I have my IFD540 as primary only so I do have back up methods but it would be bad to discover this on low IFR approach in the dark. I have a PMA450 / IFD540 combination and did not know which part is at issue. Ed ------------- Ed |
Posted By: pburger
Date Posted: 16 Jul 2015 at 1:45pm
|
Interesting. I've noticed a little trouble activating the PCL at my home airport, but I never thought it could be due to my new radio. I have to click very deliberately and very slowly, but not so slow as to miss the 5-second window. Hmmmm...... |
Posted By: Royski
Date Posted: 16 Jul 2015 at 4:25pm
|
comancheguy, that sounds like a problem another 540 owner has reported at our airport (VKX). Personally I manage to trigger the SuperAWOS pretty reliably with the 540 though I have to click more slowly than with my older King radios. I'm not sure if it is an issue only of technique or if there is also a variation in equipment. EDIT: come to think of it, I have a PS Engineering PMA450 and he has the new Avidyne audio panel |
Posted By: Gring
Date Posted: 16 Jul 2015 at 4:28pm
|
I have the same issue with both of my IFD540s. I can get AWOS from my home field 2 out of 10 times I try and as mentioned you have to be very precise. It also appears to affect the PCL, but to a lesser degree. I have spoken with Avidyne about it and they have some additional information on the subject.
To be fair, This appears to affect mostly the Potomac SuperAWOS system which currenly has their certification pulled by the FAA and is not an official weather source any longer. They have a much more sensitive PTT recognition method than the PCL boxes.
|
Posted By: AviJake
Date Posted: 16 Jul 2015 at 4:47pm
|
Agreed. This issue is real. We are working on a root cause --> solution for this. Very quick (<100ms or 1/10th of a second) clicks are not handled optimally in the 540/440. For all the folks who have seen this, are any of you flying 28V aircraft or are you flying a 14V aircraft? ------------- Steve Jacobson sjacobson@avidyne.com |
Posted By: Gring
Date Posted: 16 Jul 2015 at 4:48pm
| 28V |
Posted By: edanford
Date Posted: 16 Jul 2015 at 6:22pm
|
28V ------------- Ed |
Posted By: AviJake
Date Posted: 16 Jul 2015 at 6:27pm
|
Copy ------------- Steve Jacobson sjacobson@avidyne.com |
Posted By: mfb
Date Posted: 16 Jul 2015 at 6:35pm
|
14v Mike |
Posted By: tony
Date Posted: 16 Jul 2015 at 7:21pm
| I had the same issue, thought it was operator error. I'll try it again this weekend. I'm a 14 volt aircraft. |
Posted By: DavidBunin
Date Posted: 16 Jul 2015 at 8:08pm
| I have used the 540 for PCL precisely once so far, and it worked exactly as expected. But maybe I am a slow clicker? I don't like to machine-gun the PTT button. Five seconds is a LONG time. |
Posted By: oskrypuch
Date Posted: 16 Jul 2015 at 8:12pm
14v I normally use my #2 radio (SL30) for ground freq/PCL, had real issues trying to get PCL to work with the 540 when I tried it. * Orest |
AviJake wrote:Posted By: pburger
Date Posted: 16 Jul 2015 at 8:50pm
|
14V Our beacon, lights, and PAPI are all on the same PCL circuit. I use the PCL quite a bit. I had noticed a difference, but thought maybe it was due to an upgrade of the lighting equipment. I'll pay closer attention from now on and report back if I think I have any relevant data.
|
Posted By: MysticCobra
Date Posted: 16 Jul 2015 at 11:20pm
|
I have not tried to trigger PCL with my IFD540 radio, but one of the first things I noticed the first time I tried it out was the apparent delay in opening the transmission channel after pressing the PTT button on the yoke. It seems like there are several 10s of milliseconds delay there...enough that my normal method of near-simo key-the-mic-and-start-talking caused the first bit of my speech to be clipped. I think I've mostly trained myself to key, pause, then speak. But it's clear from this thread that I'm not imagining the behavior. I'd sure like to see that behavior improved. 14V
|
Posted By: comancheguytoo
Date Posted: 17 Jul 2015 at 1:24am
|
14v for me. Have tried PCL at 6 or 7 fields around SoCal. I've been discussing with TJ. One of the hardware guys and he looked at it today and there appears to be a slight delay on the software side, in the range of milliseconds, on each mic press. Lines up with a theory Comancheguy had when we discussed. Only problem is the tower guys at my airport said they could hear my squelch breaks, but still didn't see the PCL equipment respond. They were baffeled. TJ gave me the idea of inverting the timing of the clicks. Instead of qucikon-longoff-quickon-longoff...etc, do longon-quickoff-longon-quickoff...etc I'll try and report back when able. Ken, I should see you at OSH on Sat. am |
Posted By: comancheguy
Date Posted: 26 Jul 2015 at 4:11pm
|
Sorry that I missed you at OSH. 14v for me. Ken
|
Posted By: teeth6
Date Posted: 26 Jul 2015 at 7:53pm
|
Wow, I just noticed this thread. I have a 28 volt aircraft and have a really hard time turning on the PCL at my home airport. I thought there was a problem with the equipment at SFZ and reported it to the airport manager. I never thought it might be an issue with the 540s. So what is the suggestion until this is fixed via software. Click at a certain rate? |
Posted By: AviJake
Date Posted: 26 Jul 2015 at 7:56pm
|
Yes, deliberate "slow" clicking just enough to meet the number of clicks required in the maximum time frame (e.g. 5 clicks in 5 full seconds) is what folks report to be a usable technique. ------------- Steve Jacobson sjacobson@avidyne.com |
Posted By: oskrypuch
Date Posted: 27 Jul 2015 at 9:35am
|
.. With a long push (hold) and a short period for the release. I noticed this last year, but usually use com2 for pcl, so forgot about it. Sorry I didn't report it. * Orest |
Posted By: comancheguytoo
Date Posted: 28 Jul 2015 at 11:12am
|
Just wanted to respond to the methods for work around. I've tried multiple timings now, including the long press short release suggested by support, and also the timing of clicks, spacing them out as long as possible. In my application I've not yet been able to activate lights, and I've tried several airports around the country over the last two weeks. I've had several opportunities to make attempts while towers are still manned. Each location, Dane Cty Madison for instance, reports hearing the clicks, but not seeing the lights come on. They also report that the 'sound' of the clicks are the same when I use my Com 2(SL30) to activate the lights. If I'm understanding what I've been told so far, it sounds as though the working theory is that a timing issue exists between the mic button press and the sql break, making the sql not actually 'break' if you click too fast. Assuming the reports from tower personnel are accurate, it would appear that even when the sql does break, the equipment at various locations still does not detect the sql break.
|