Show Posts

You can view here all posts made by this member. Note that you can only see posts made in areas to which you currently have access.


Messages - exfirepro

Pages: [1] 2 3 ... 155
1
Hi again bladeslapper,

Adding 90degree SMA male to female adaptors between the Rosetta antennas and their connectors certainly appears to be a worthwhile mod to minimise potential antenna damage for a unit that is regularly taken in and out of the aircraft and transported in a bag with other equipment. There will, however, inevitably be some degree of signal degradation due to loss in adding an additional connector, though this should be minimal (usually estimated to be in the region of 1dB per additional connector in each line).

For any of you reading this thread and perhaps concerned that it leaves bladeslapper's GPS hidden under the battery, I recommend that you also read bladeslapper's previous Rosetta modification thread, here...

http://forum.pilotaware.com/index.php/topic,1975.msg21050.html#msg21050

Best Regards

Peter


2
General Discussion / Re: Flightradar24 track error
« on: October 21, 2021, 08:34:22 pm »
Hi Frank,

I have sent you a PM via the message board.

Best Regards
Peter

3
General Discussion / Re: Flightradar24 track error
« on: October 20, 2021, 07:30:25 pm »
Hi Frank,

Thanks for the feedback.

That's one of the things we would have checked / seen from the requested screenshots. FEDE60 is obviously the 'default' Hex ID of your PAW, based on the last 6 digits of the unit's 'MAC' address - and allocated to the PAW automatically during pre-dispatch setup and testing. This, along with other 'default' settings is held in a default profile*, which is normally superseded when you create and save your own 'profile' during initial setup of your unit prior to your first flight. I have no way of checking your initial setup as there are as I say no reports on the database from 4075B1** and the earliest reports from FEDE60 start from 23 April 2021 and continue until 16 October 2021 from ground stations as far apart as Kilkeel, East Fortune and Edinburgh West, and the West and South West of England. The most likely explanation therefore in view of the lack of reports from 4075B1 is that the initial profile was set up and the post install check done, but that profile was either not saved or somehow inadvertently reverted back to the default at some time between the initial setup and 23 April 2021. Whilst historically we have had reports of units reverting to the default profile during updates or licence renewals, this was a bug which was sorted a long time ago, so this is unlikely to be relevant with the current software versions***. I am however aware of at least two recent cases where aircraft which I know personally have been operating on their correct ICAO Hex ID and have mysteriously reverted to the default, but I suspect that these were almost certainly finger-induced errors.

* Profiles are created to allow the unit to be 'swapped' between aircraft with minimal fuss and can be found from a button at the bottom of the PAW Configure Screen. They are created by re-configuring the unit to match each aircraft in which it is likely to be used, then 'Saving' each set of settings as an individual 'Profile'. The desired profile can then be be selected at will prior to flight in a different aircraft.

** With the exception of the single 'ping' from 4075B1 reported by PWShiren on 14th May, which is almost certainly a rogue transmission of some sort.

*** Unless of course you are still running old software - the latest released version is 20201101

Re your Funke Transponder - in view of the numerous recent reports on the database from your PAW transmissions, and the complete lack of reports for ADSB from either Hex ID, it is pretty certain that your transponder is NOT transmitting Mode-S/ES ADS-B, so this obviously needs further investigation. You can find several threads on this subject by searching 'Funke' from the Forum Home Page. Please feel free to come back to us for help if you need it.

Best Regards

Peter

4
General Discussion / Re: Flightradar24 track error
« on: October 19, 2021, 11:11:30 pm »
Hi Frank,

Ditto to the above requests.

I take it you are based at (or near) Newtownards? PilotAware Ground Stations are unfortunately still very thin on the ground in N.I. (only 3 sites at Derry/Londonderry, Tandragee and Kilkeel), so I wouldn't necessarily expect great reports from the Newtownards area.

ATOM Ground Stations are, however, much more common over here on the UK mainland and as you flew from Newtownards direct to Netherthorpe on Sat 16th October, you will have passed a considerable number of them during that flight, yet I can find only one single report for 4075B1 in the PAW database, and that is a single P3i 'ping' at 66Km from PWShireN (near Chepstow) back on the 14th of May, with no record whatever either before or since, and no record whatever of any active ADS-B transmissions (which at much higher power would be more easily received at range). This clearly indicates to me that there is definitely something wrong with your equipment, setup or both.

This could be something as simple as that your PilotAware Licence has expired, but sight of the requested screenshots should help us identify the problem, or at least point us in the right direction as to the likely cause.

Best Regards Meantime
Peter

5
General Discussion / Re: Flightradar24 track error
« on: October 19, 2021, 06:07:26 pm »
Hi Frank,

Strange, as there are lots of active PAW ATOM-GRID Ground Stations in and around Lancashire. Unfortunately, Vector doesn't currently report Mode-S due to the extremely high levels of data storage and processing required to do so, however Vector should at least be reporting your PAW P3i transmissions - even if you aren't transmitting Extended Squitter ADS-B.

As Lee has commented, the most likely explanation for a 'jaggy' track on flight reporting websites is poor multilateration (triangulation of position) due to poor reception of Mode-S from your transponder to their Ground Receiving Stations (they certainly DON'T get reports from official Ground Radar!).

If you care to share some details - Aircraft Reg / ICAO, date and time of last flight and points of departure / arrival - I will take a look and try to work out what might be going on.

You can PM me via the details via the message board if you don't want to make the details public.

Best Regards
Peter

6
General Discussion / Re: Bluetooth Adapters - Experiences/Recommendations
« on: October 07, 2021, 05:09:41 pm »
Hi Hil,

Unfortunately I don’t think there is a simple fix for your multiple device / multiple headset scenario.

PilotAware Rosetta already has a built-in Bluetooth Audio option, by virtue of its Raspberry Pi3 Motherboard, which wasn’t available on the PAW Classic (which is based on a Raspberry Pi2). Bluetooth-equipped headsets can therefore (at least in theory) be connected directly to receive the Rosetta’s PilotAware Audio Alerts, but this facility is still in a ‘Beta’ version and has to be configured and setup in the PilotAware Configure Screen to suit each individual headset. Also it doesn’t always retain the previously configured connection, so isn’t therefore ideal and certainly isn’t appropriate for multiple users with their own headsets as it would have to be reconfigured in PilotAware/Configure each time the user / headset changes. It is also not generally possible to connect separate audio sources to a single headset via Bluetooth, but read on...

My solution to the multiple audio sources issue is to use a small audio mixer to combine separate audio feeds hard-wired from my Rosetta and Tablet - in my case to combine the audio warnings from PilotAware and from SkyDemon on my iPad mini, (but it works just the same with a variety of android devices). The combined output from the mixer is hard-wired into my intercom, though I can see no obvious reason why this output couldn’t be fed direct to your headset via a Bluetooth transmitter such as that suggested above by Mariko, though I have to stress that I haven’t actually tried this myself.

The audio mixer I use (also used by several other PAW users) is the ‘Maker hart JUST-MIXER’ - available from Amazon. I have also tried the ‘newer’ Just Mixer 2 from the same company, but personally didn’t find it as effective.

The significant advantage with this setup - apart from being able to boost/balance the audio levels from the different devices is that if the audio alerts become distracting at a critical point in the flight, they can be instantly turned down or muted via the ‘Master’ slider.

I do have a couple of Bluetooth transmitters similar to the one Mariko has suggested somewhere, though I haven’t used them since moving to Rosetta. If I can find them I will try using one to connect the output from the mixer to Headset and see what happens, but I can’t promise how soon I will manage this.

Hope this helps.

Best Regards

Peter

7
Technical Support / Re: Mode C issue
« on: September 29, 2021, 05:41:42 pm »
Hi John,

Thanks for the feedback and good to have my prognosis confirmed. Hopefully all will be good from now, but feel free to get back in touch if you need any further help.

Best Regards
Peter
p.s. I will update the thread title to - ‘Resolved’ to save any confusion.

8
Technical Support / Re: Track File Missing
« on: September 28, 2021, 08:28:50 am »
Hi Gonch,

Thanks for the additional info and apologies for the delay in responding.

All understood on the aircraft and the internal antenna installation. The only comment I would make is that I would suggest moving both antennas a bit further ‘forward’ on the screen to try to reduce obscuration to the rear by the window frames - otherwise that positioning is about as good as you will get from an internal installation.

If you don’t want Bearingless traffic reports then... Yes, you would set Mode CS Select to Disabled - though with the high percentage of pure Mode C and Mode S Aircraft, I would strongly advise you to reconsider using this option. If you decide you DO want warnings for otherwise Bearingless traffic, but don’t want warnings for aircraft you are unlikely to see, I would enable Mode CS (+ Filter as you have a Mode S transponder) and set the reporting Range to Short Range and your altitude filter a bit wider than +/- 500 ft.

Having said all that, there are definitely no P3i reports on the PAW database from your flight on 22/09/21 which supports my hypothesis that your PAW wasn’t transmitting (or at least not outside the aircraft). Even in absence of a track file, transmissions would have been picked up by at least the PWSolent Ground Station. The flight on 24/09/21 shows only 2 P3i ‘pings’ (a few seconds worth of transmission) from your aircraft received by PWSolent at less than 1Km and nothing more.

I managed to get hold of James (the Aircrew Developer) last night and he did a more extensive and in depth search for me from his database, which confirms that although your aircraft has been transmitting Mode S regularly, there are virtually no reports of effective P3i transmissions from the aircraft since early August at least. This would lead me to suspect either a fault with the Rosetta unit itself or (possibly more likely) an issue with the P3i antenna. First thing to check is that you have the correct antenna connected to the correct port on the Rosetta (the P3i antenna is the longer of the two). If this is OK, I would suggest removing the unit and antennas for testing outside the aircraft. To do this, you will require the ‘internal’ P3i antenna from the aircraft plus a ‘standard’ P3i antenna for comparison, or you could return the unit (and antennas) to Ash at PilotAware Support for more extensive testing.

Please keep me posted.

Regards

Peter

p.s. @PaulSS - James sends his apologies, you are correct - the Aircrew website was down for a short while due to an admin error, now sorted out and hopefully all back to normal.


9
Technical Support / Re: Track File Missing
« on: September 25, 2021, 10:14:08 am »
Gonch,

Looking again at the data from 401D1E this morning, it is clear that the number of data ‘pings’ recorded is significantly lower than I would expect to see. I have also tried a ‘Ground Station’ search using the Aircrew Groundstation Track Reporting Tool, but can find no reports for 401D1E for the last 2 dates (1st and 10th August 2021) where data is present on the PAW database - including searching for any EC transmission type from that aircraft. This implies that the aircraft is not running a transponder (please confirm) and again points me towards a lack of effective P3i transmission outside the metal aircraft body.

I will try to speak to James - the Aircrew Developer - to see if he can shed any additional light on my findings.

Best Regards

Peter

10
Technical Support / Re: Track File Missing
« on: September 24, 2021, 11:58:32 pm »
Hi again Gonch,

Thanks for the additional info.

From the screenshot of the PAW Home Screen, I can see no clear evidence as to whether or not your PAW is transmitting, though I must admit I find it difficult to interpret the current Up / Down P3i reports - and from the recorded ‘Uptime’, at the time of the screenshots the unit had obviously only been running for 4 minutes with a 2D rather than a 3D GPS fix - but read on below.

OK, so from what I can see, we have a PAW equipped (metal bodied) PA28, (possibly with a Mode-C or S transponder*) with a significant number of PilotAware P3i only reports* from Ground Stations - between 31st March and 10th August 2021, at varying ranges between 1 and 60 Km (with a few spurious reports from further afield). In the majority of cases the reports are nearer to the shorter end of this range than the longer. This would imply fairly significant limitation of transmission range, especially towards the ground - probably due principaly to obscuration by the aircraft metal bodywork, engine and occupants. In this connection, can you please advise where and in what orientation the PilotAware is mounted. (Photos would be very useful).

* Due to data storage limitations, the database does not currently report data from pure Mode C or Mode S transponders.

From the reports I did find, I would conclude that you operate mainly (but not exclusively) in or around the region of EGHN,  EGHJ and EGHP (and from the data most probably out of EGHN). Is that correct?

Despite the number of Ground Station reports recorded, the PAW Vector Coverage and Range Tool shows no results whatever for your aircraft, though this can be explained by the fact that the Vector reports are based on data from the last 30 days or so only (with the last flight recorded by any PAW Ground Station on 10 August 2021, this explains the lack of any current Vector reports).

Looking at your configuration settings, I can see that you have Mode C/S Settings set to Ultra Short Range and +/- 500 ft (which is extremely tight unless operating primarily from and in the vicinity of a commercial airport), but as you have Mode C/S Select set to ‘Disabled’, this is fairly academic in any case as with this setting NO Mode C or S contacts will be passed to your display screen. I would suggest setting Mode C/S Select to Mode C/S - or Mode C/S + Filter if you are running a transponder, and with the range and vertical reporting distances set much wider - at least until you confirm that such reports are being received.

I would also suggest that you need to open up your receiver range settings in both PAW Configure and your chosen Nav System (which controls ‘Known Position’ reports) to maximise potential for reception of traffic and then try to improve transmission and reception by varying the position of your unit, or trying alternative antennas (such as the PAW Internal Dipole Antennas or better still PAW External Antennas, and analysing the signal reports after each flight using the Vector Range Tool. Screenshots from your Traffic Screen / Nav Display after opening out the Filters will also be of assistance. I am happy to help you with further ongoing analysis of data.

I hope this helps explain what appears to be going on, though it doesn’t of course explain the missing track file(s) - except as I suggested earlier. Please keep in touch.

Best Regards

Peter

Postscript: what was the date and route of the flight(s) you referred to earlier?

11
Technical Support / Re: Track File Missing
« on: September 24, 2021, 09:49:15 am »
Hi Gonch,

If you give me the Reg I’ll take a look on the database.

Regards

Peter

12
Technical Support / Re: Track File Missing
« on: September 22, 2021, 10:34:51 pm »
Hi Gonch,

I would be surprised if the ‘missing’ track files are related to the fact you have carried out multiple flights on the same date - even if the PAW was left running between flights. I regularly fly multiple flights and have never personally noticed any ‘missing’ track files in over 6 years using various iterations of PilotAware - though I DO have direct personal experience of track files missing from at least one other user’s PAW when I was trying to investigate after recent reports of other aircraft ‘latching’ to the user’s aircraft during a couple of flights on two successive days.

The obvious suspicion when no traffic is showing on your traffic screen (but there is definitely traffic about) would be that either your traffic filters are set too tight, or that you have inadvertently chosen ‘Use Location Services’ rather than ‘Use PilotAware’ after selecting ‘Go Flying’ - Easier to do than you might think if you started SD while the aircraft was moving. But in either case a Track File would still (normally) have been created in PilotAware simply by the fact it was running. The fact that no track file appears to be present is of concern. I know Lee has some thoughts as to possible reasons, but I don’t think he has solved the issue definitively yet (or if he has, he hasn’t advised me of his findings). One thing he did say is that it might be possible for him to locate logging details from the flight in the case of a missing track file by interrogating the microSD card direct, provided nothing has been changed on the card (though I think this is a ‘long shot’).

Hopefully Lee will respond when he reads this.

In the meantime, it would help to know which PAW software version you are running and also if you can post a screenshot of your Home and Configure Screen settings (after leaving the unit running out in the clear for long enough to establish a good GPS fix and have a chance of receiving some traffic.

Best Regards

Peter

13
Technical Support / Re: Mode C issue
« on: September 19, 2021, 01:46:00 pm »
Hi John,

You can find the Track files under the ‘Tracks’ tab - which is at the extreme right top of the PAW Screens after accessing via 192.168.1.1. They can be downloaded and you can open them using for example Microsoft Notebook, but most of it will be gobbledegook unless you know what to look for.

If you want to send the unit back for checking, contact Ash via support@pilotaware.com and please report any findings back on here afterwards.

Best Regards

Peter

14
Technical Support / Re: Mode C issue
« on: September 19, 2021, 11:33:29 am »
Hi John,

You still haven't fully clarified what you meant by 'I only get a red warning against mode c', though from the later information, I think we can assume you are referring to the 1090 Status Indicator on the PAW Home Screen - the function of which we have hopefully now clarified.

Thanks for the additional info. Lee has confirmed what I alluded to last night, that although the original Home Screen indicated NO 1090 reception during the period the unit had been running, the later screenshot certainly indicates that your PAW had been receiving some 1090 reports prior to the screenshot being taken, which reduces (though may not completely eliminate) the likelihood of an SDR or antenna fault. I know it sounds simple, but if you haven't already done so, please check the antenna connections and that you have the correct antennas on the correct sockets - the short one on the right when looking at the PAW with the label uppermost - and as Lee has advised try to run the unit for a longer period outside where it has a clear view of the sky. A screenshot(s) of the 'Traffic Screen' from during this test will be helpful to let us see what is going on, as this shows all traffic received - even where it is subsequently filtered by PAW due to your selected PAW filter settings and not sent to the Nav Display.

In this context, I notice from your latest screenshot that you have your reporting filters for Positional Contacts set to 20Km and +/- 2000ft. While this is fairly 'wide', we normally advise users to leave the filters for known position targets* wide open on PAW (which ensures that all data is passed to your Nav System) and use the filters in the NAV system to control what it actually displays - unless of course you are using a Nav System that doesn't include its own Range/Relative Altitude Filters.

* This section only affects known position targets, i.e. ADSB, PAW and re-broadcast Flarm or Mode-S MLAT.

As Lee has advised, the track log from the relevant flight (or extended ground trial) will be conclusive in indicating what traffic your unit has actually received.

Hope this helps.

Best Regards

Peter

15
OGN-R PilotAware / Re: New Stations Added
« on: September 18, 2021, 10:42:02 pm »
Just back from a long (13 hour) day, driving down from Edinburgh with AlanG to install a new PAW ATOM-GRID Ground Station at Athey’s Moor in Northumberland.

Now all up and running and looks like being a very useful site - and extends the ‘Scottish’ coverage a bit further down into the North-East England ‘gap’.

Hopefully we can add a few more sites in due course.

Regards

Peter

Pages: [1] 2 3 ... 155