Messages

16

Technical Support / Re: LAA refuse approval to connect Pilotaware to Funke transponder (ADSB out)

« on: January 21, 2021, 10:14:17 am »

Here, here. I wasn't aware of all the work going on in the background, but thanks to all those that put in the effort to achieve this positive and sensible outcome. 

17

Technical Support / Re: LAA refuse approval to connect Pilotaware to Funke transponder (ADSB out)

« on: January 21, 2021, 09:53:12 am »

Yes good news of positive resolution - LAA Engineering have issued this statement via the Flyer Forum (see that forum post to follow the links mentioned):

As you may know it is possible to connect an uncertified GNSS (GPS) receiver to a range of Mode S transponders in LAA aircraft to provide uncertified ADS-B Out, which we’ve been approving since 2015 following the successful NATS trial.

It was recently brought to our attention that CS-STAN Issue 3 CS-SC005a (issued in 2019) requires that the transponder for such installations must be certified to ETSO-C166b, which covers the approval of a transponder to transmit ADS-B Out. LAA technical leaflet TL3.03 and LAA procedures also require that “transponders installed in UK aircraft must be of a type that has undergone an appropriate approval process by either EASA, the CAA or the FAA”. Given the lack of CAA rules on this subject, LAA interpret this requirement as a transponder providing ADS-B out must also be certified to ETSO-C166b. For the majority of ADS-B installations approved so far, this certification requirement was not of concern as most installations used a Mode S transponder that was certified to ETSO-C166b (ETSO certifications can be checked here).

Upon further research, LAA Engineering understands that a change in the wording to CS-STAN CS-SC005a ‘Configuration 3’ will be made with the next revision of CS-STAN which will remove the requirement for ETSO-C166b certification of the transponder. Please see this EASA FAQ here.

LAA Engineering is therefore satisfied that ADS-B Out installations with a transponder that is not certified to ETSO-C166b is satisfactory for ‘uncertified’ applications. The transponder must still be compliant with an appropriate certification for Mode-S operation, installed in accordance with the manufacturer’s instructions, and the ADS-B Out quality indicators must be set to SIL/SDA = 0.

All previously approved ADS-B Out connections are still valid and any LAA/MOD7 or LAA/MOD14 applications that were previously rejected can now be processed normally.

18

Technical Support / Re: LAA refuse approval to connect Pilotaware to Funke transponder (ADSB out)

« on: January 20, 2021, 05:20:24 pm »

Still waiting on a formal response from Funke on their certification. See the relevant thread on the Flyer Forum which has developed a lot of interest and some movement towards a possible resolution.

19

Technical Support / Re: LAA refuse approval to connect Pilotaware to Funke transponder (ADSB out)

« on: January 14, 2021, 12:29:02 pm »

Have only just got this response from LAA so early days, awaiting comment from our avionics engineer who carried out the fit and provided the mod forms. I am amazed that I have not seen this issue come up anywhere else on the forums, there are some technical issue with Funke transponders mostly relating to firmware updates to make the system work, but I have not seen anyone else say that LAA have declined to approve the connection with PAW.

20

Technical Support / LAA refuse approval to connect Pilotaware to Funke transponder (ADSB out)

« on: January 14, 2021, 10:22:58 am »

We have completed a permanent installation of Rosetta Pilotaware including connection to our Funke TRT800A Mode S ES transponder with latest firmware (5.3). Carried out by professional avionics engineer who confirmed ground tests and that ADSB working correctly, set to SIL=0 as non certified GPS from Pilotaware. Sent off the relevant mod forms to LAA earlier this year. Just had the following response saying that they (LAA) won't approve the connection for ADSB out because the TRT range does not comply with the ETSO standard. I have seen nothing on this anywhere, with CAA /LAA and everyone else including Pilotaware encouraging installations of EC units and in particular connections to ES capable transponders for ADSB out as a preferred minimum. Advice?

LAA response to modification forms sent in:

Unfortunately, we can’t approve any ADBS-out connection for the Funke TRT series transponders as they do not possess the appropriate approval. The TRT Series is not approved to ETSO Standard C166B, therefore the ADSB out function can not be approved for use until this certification is sought by the manufacturer. The TRT series is sold as “ADSB Ready” but does not necessarily meet the minimum performance requirements of the ETSO. Unfortunately all transmitting avionics installed in LAA aircraft must hold the relevant approval from the CAA, EASA or FAA.
 
I am sorry this is not the news you wanted to receive. However, you may still use the pilot aware device in your aircraft as standalone electronic conspicuity not connected to that transponder. If you permanently install it you will just need a PMR in your airframe logbook from your inspector.

If this is correct, it throws into serious question why we are being encouraged by all and sundry to spend money on fitting devices which the regulators won't approve. I am struggling to see how this can be right, especially as I have seen nothing on this subject (LAA approval declined) for this elsewhere.

21

General Discussion / Re: Mode S 3D and bearing less overlap?

« on: November 06, 2020, 12:45:10 pm »

Hi Lee,

I have accessed and downloaded some of the recent track files, they seem to be about 4mb each - how do I send them to you?

Martin

22

General Discussion / Re: Mode S 3D and bearing less overlap?

« on: November 04, 2020, 04:44:31 pm »

Lee many thanks for your comprehensive response:

"you can disable Mode-C warnings, but keep Mode-S" - didn't know this, can you point me at the particular setting, that sounds worth exploring.

As regards the track file, PAW is permanent install in the aircraft so I would need to go back out and extract - how do I access the track files and load them onto my iPad or iPhone?

23

General Discussion / Mode S 3D and bearing less overlap?

« on: November 04, 2020, 04:17:27 pm »

So, completed a permanent install of Pilotaware Rosetta into our Jodel at beginning of year, just before first Covid lockdown. Have had limited air trials and with bearing less targets set to 'medium', +/-500ft and 3D switched to on, C/S filter active. PAW is connected by Farnell cable to our Funke transponder with ADSB-out and aircraft hex ID added to both devices. External antennae fitted to metal plate below fuselage with spacing of around 1m between PAW and transponder aerials.

The issue we are seeing is multiple bearing less target reports in quick succession (I believe for the same aircraft). Some of these appear to be transmitting either ADSB or PAW, but we are getting bearing less alerts for the same targets. Could be antenna blanking with the direct target information dropping out, replaced instantly with a bearing less alert, then back to direct target information.

Its very distracting and not helpful to the point that we are considering disabling bearing less all together.

Question - is it possible for an aircraft to transmit both direct ADSB information (say from a Skyecho) and bearingless information simultaneously (say from Mode C transponder)? I am certain this appears to be the case occasionally. I imagine that this would happen if the target flyer had different hex ID in different devices, but assuming that is not the case, could this be due to Mode S 3D multilateral targets falling back or going in and out to bearingless due to blanking or loss of radar interrogation?

Also, the bearingless reports sometimes seem continuous over and over for (apparently) the same target, a continuous running alert report, whereas I thought there would be maybe one report at distant range, then one at closer range, in which case one might expect maybe three alerts over a few minutes.

The direct targets seem to work fine, occasionally disappearing and reappearing.

How is the Mode S 3D multilaterated /bearingless process supposed to work. I would like to think they would be exclusive, i.e. once you had a multilaterated target it would stay that way and not be mirrored by a bearingless report.

We would like to retain bearingless targets for the potentially useful level information, but unless we can eradicate some of the clutter and confusion of alerts, it will have to be disabled in favour of direct target info only. Hopefully, things will improve as more people fit and fly with EC devices following the CAA funding offer.

We have now reset settings to 'ultra short range' to see if things improve.

Thanks.

24

Technical Support / (RESOLVED) Rosetta power + Charge2 USB unit, wifi disconnections

« on: July 26, 2019, 10:16:06 am »

UPDATE - issue RESOLVED with upgrade to Charge2 USB socket. Many thanks to Jeremy Curtis of Harkwood Services for meeting us at Conington to perform the upgrade directly on our Jodel, (swapping our old 2015 early Charge2 box with new internals), entirely free of charge. Flawless customer service from a small company delivering superb quality product. It was great to meet you. Pleased to report that our Rosetta now works perfectly via the updated power socket software and put to great use on our return trip. At one point passing north of Bicester /Brize Norton (we were also receiving a Traffic Service from Brize Radar), we were surrounded by about 5-6 reported contacts, all of whom shown on Skydemon and one of which passed down close to our right hand side which we followed on Skydemon and spotted visually well in advance. We now need to get on with permanent installation so that we can improve antenna positioning and get some more airtime to gain experience with the traffic system and settings. Thanks to both Lee and Jeremy for speedy response getting us up and running.

25

Technical Support / Re: Rosetta power + Charge2 USB unit, wifi disconnections

« on: July 09, 2019, 07:42:54 pm »

Jeremy, brilliant, we’ll be in touch!

26

Technical Support / Re: Rosetta power + Charge2 USB unit, wifi disconnections

« on: July 09, 2019, 05:22:04 pm »

Lee /Jeremy, many thanks for fast response. Yes its a 2015 panel mount, I don’t have the serial number to hand but the original order was dated 2/2/2015 order number RC17267537. Delivered to my home address (then) in Shaftesbury, Dorset, aircraft based at Henstridge. The software update, can that be applied by us on the aircraft or does the unit need to come out to you? We can alternatively fly up to Cambridge /Connington by arrangement to see you at some point. Many thanks again for your help.

27

Technical Support / Re: Rosetta power + Charge2 USB unit, wifi disconnections

« on: July 09, 2019, 04:26:58 pm »

We have updated Rosetta to the latest 2019 software 20190621

28

Technical Support / SOLVED: Rosetta power + Charge2 USB unit, wifi disconnections

« on: July 09, 2019, 04:25:17 pm »

Hi, we are in the initial stage of installation of a brand new Rosetta in our Jodel, with long term view of permanent installation (we have also bought the external antenna kit), but frustratingly have had two abortive attempts to get the unit working in the aircraft. We have a Charge2 USB power supply, installed and working faultlessly for more than 2 years powering a 1A mini iPad and 2A XPS150 GPS sender. The Rosetta works faultlessly with the supplied cable on ground wall socket power and via a car USB socket, but once in the aircraft, fails to connect or loses wifi connection. It looks like a power issue as outlined in many places on this forum. However, we are at a loss to understand it bearing in mind we have the right kit and cabling. Before going to the effort and cost of having all the aircraft wiring and avionics examined, a question about the Charge2 unit.

We have (I believe) a fairly new 18V battery for starting the engine and operating general systems, checking this. We always see low volt light on start up until the (old) generator gets up to speed, and this will come on when all systems drawing power (i.e. switching on electric fuel pump to land). The iPad and GPS plugged into Charge2 work correctly immediately although there is a slight pause after turning on Master switch before the two green lights showing power supplied to the devices appear. On our Rosetta connection, we don't plug in the iPad or the GPS and only the Rosetta is connected. The Charge2 power indicator light shows continuous green -  even though the start up period power on the main supply side may be below 18v (more like 12-14v on the ammeter) until the generator gets going to add juice back into the battery. Does this indicator guarantee that the output side from the USB socket to the Rosetta is at or above the 5.2V that Rosetta needs and is stable, or is there still a possibility that Charge2 output is fluctuating /interrupted? It looks like the Charge2 is not providing the correct or continuous power to Rosetta as the unit works absolutely fine from ground mains power.

Any pointers would be appreciated so that we can investigate further. Don't want to go down the route of portable battery power as we already have a perfectly (we think) usable solid power supply in the aircraft, although the infrastructure behind the Charge2 may need to be inspected.