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 - James Rose

Pages: [1] 2
1
Technical Support / Re: Cannot access PaW
« on: May 03, 2021, 12:08:45 pm »
That QR code is for sharing the WiFi network to other phones. It looks like your phone is connected to PilotAware.

Can you open up the browser, goto 192.168.1.1 and then send a screenshot of what that page looks like?

As Peter said if you don't see the PilotAware homepage on 192.168.1.1 then it's most likely because Android devices do not like connecting to WiFi networks with no internet. You should be able to fix this by:

1) Open the WiFi settings for the PilotAware hotspot
2) Click "forget" so you disconnect from the PilotAware hotspot
3) Reconnect to the PilotAware hotspot, and wait for the "Internet may not be available" message to pop up
4) Click "Keep Wi-Fi" connection
5) Open your browser and go back to 192.168.1.1




Also regarding only seeing HEX on Aircrew:  PilotAware only sends HEX ICAO over USB due to combability for legacy FLARM products - it may be better to power your Aircrew separately and connect Aircrew to PilotAware over WiFi, then you'll get the registrations.

2
Technical Support / Re: Aircrew Playback symbology
« on: March 07, 2021, 10:19:32 pm »
Static is the aircraft type.




The ACSPUMB is the transmission types. If you hover over the letters on the playback it displays:

A = Mode-A
C = Mode-C
S = Mode-S
ES = ADS-B
P = PilotAware
F = FLARM
U = Uplink from ATOM
M = MLAT Uplink from ATOM

So PilotAware was receiving the aircrafts ADS-B transmission, PilotAware transmission and an uplink to its MLAT position (which probarly was discarded as you were receiving it direct). Not sure why it's static, would be good if I could take a look at the track file. The playback tool hooks into some of the PilotAware debugging messages in the .trk file so it could be inaccurate.

3
Technical Support / Re: Ghosting
« on: January 04, 2021, 10:36:27 am »
After looking at the track files from 3rd Jan, the other plane ground station. As you were running PilotAware version 20190621, SkyDemon displayed it as a plane. Latest versions of PilotAware and SkyDemon now show a ground station.

Why the plane was following you on the 4th Nov is a mystery. My guess would be it was also a ground station and some bug with using a 2019 PilotAware release with the latest SkyDemon was causing it to be displayed incorrectly. I believe after you update to the latest PilotAware you shouldn't have any issues.

4
Technical Support / Re: Ghosting
« on: January 03, 2021, 05:31:37 pm »
Hi John,

Could you upload your PilotAware .trk file to http://aircrew.co.uk/playback/ from the 4th of November and send me the link once uploaded?

James

5
Technical Support / Re: Vector shows PAW but not ADS-B signals
« on: December 29, 2020, 01:15:31 pm »
This answers a question I was about to ask, but to wander slightly off thread, how does VECTOR differentiate between ADS-B and CAP1391; aren't they both ADS-B outputs?

The ADS-B packet includes 5 bits for the downlink format (DF). ADS-B is 17 and CAP1391 is 18, the groundstations decode this and store it in the database for VECTOR to query.

6
Technical Support / Re: Vector shows PAW but not ADS-B signals
« on: December 28, 2020, 10:28:04 pm »
Hi Geoffrey

Your flight on the 22/12/2020 you flew within 2 ground stations that were less than 10km away which were:

 - PWUKBIG which doesn't have an ADS-B in
 - PWEverton which does have ADS-B in but its extremely limited (the PilotAware range is 10 times better)

The 360Radar network (which feeds into the ATOM network) saw 285 ADS-B pings, however 360Radar data is not currently used in the beam graphs.
Flightradar24 saw around 40 ADS-B pings.

I am surprised that none of the other PAW groundstations saw your ADS-B, especially when PWEGBT saw your PAW at 60km.

Here are the groundstations which saw your PAW transmissions and your average distance to them.

Code: [Select]
PWEverton    3.5km
PWUKBIG      5.7km
PWUKGRL      10.6km
PWOrwell     14.1km
PWBedford    16.3km
PWOlney      27.4km
PWCambrid    30.0km
PWEGBKE      36.6km
PWEGBT       59.3km

8
General Discussion / Re: Vector analysis - no PAW signal?
« on: December 19, 2020, 08:31:52 pm »
Your PAW HEX code is set to FD6633 while your aircraft HEX is set to 400CBD.

I've attached the vector analysis for your PilotAware (FD6633). I would change your PilotAware HEX-ID from FD6633 it to 400CBD in the PilotAware configuration.

Quote
Insert your unique ICAO code in the Hex-ID field. This will make Rosetta ignore any EC messages from your aircraft. Rosetta will also transmit your aircraft ICAO code to receiving PilotAware units and ATOM GRID ground stations. This allows for better identification and situational awareness.

https://www.pilotaware.com/knowledgebase/configuration

9
How do I go about analysing the logs to quantify the quality of the GNSS data?

If you upload your track file to https://aircrew.co.uk/playback/ (info: https://www.pilotaware.com/knowledgebase/tracks) you can view how many satellites are in view in the top left corner under "Flight Information" for any given part of the flight by dragging the slider along at the bottom. It will also show when you have no GPS lock. Typically you need at least 4 satellites in view for a fix, a good installation will get 10+.










10
General Discussion / Re: Aircrew Traffic Display
« on: August 30, 2020, 06:56:58 pm »
Hi DY691 - did you email the contact@aircrew.co.uk on Friday afternoon? I will get back to you tomorrow.

11
General Discussion / Re: Aircrew Traffic Display
« on: August 04, 2020, 07:41:59 am »
For those of you who use the playback tool - you can now press Press the 'a' key on your keyboard and it will open up the Aircrew traffic display to see what it would be like to fly with Aircrew.

You can zoom in and out with the scroll wheel when hovering over the Aircrew instrument. When in flight the traffic screen would rotate to your heading, however for the demo below I have kept the traffic screen north up as the playback map is also north up.

More information about tracks can be found on the PilotAware site: https://pilotaware.com/knowledge-base/tracks/


https://aircrew.co.uk/playback/20510d


https://aircrew.co.uk/playback/6303c5/


12
General Discussion / Re: Aircrew Traffic Display
« on: July 29, 2020, 10:43:02 pm »


The Aircrew device is now in stock - photo from today checking the internal barometer calibration today at 6,000ft on a device from the latest batch.

http://aircrew.co.uk

13
Technical Support / Re: Feature request: Pause traffic audio
« on: July 26, 2020, 07:35:51 pm »
Any suggestions for how to control this on/off ?
Thx
Lee

Would be great if some of the settings could be set with a http request such as:

192.168.1.1/set/voicealerts/on
192.168.1.1/set/voicealerts/off

Then other devices/apps could easily implement control of PAW settings.

14
General Discussion / Re: Aircrew Traffic Display
« on: January 09, 2020, 02:44:23 pm »
Hi,

Are there any updates on this? Is it now available to order?

Hi Skrswift - there will be an update on the website next week.

A few people were interested in a video of the device in action: https://www.youtube.com/watch?v=dk_nGHQtknM


15
General Discussion / Re: Aircrew Traffic Display
« on: November 22, 2019, 11:40:53 pm »
Hi All,

There are not any devices available to order as I am currently having a serious problem with getting the devices made properly. This is down to me being personally inexperienced with manufacturing. I'm am going to be partnering with another company who I have worked for in the past who has and had experience with this to hopefully get the devices out as soon as possible. I will update the order page as soon as I have more information.

Pages: [1] 2