Messages

46

Technical Support / Re: Waiting for device

« on: October 13, 2023, 11:50:46 am »

If I connect PAW to the comms audio instead of the tablet I won't then get the airspace and other warnings from Skydemon through the headset which I find quite useful. And if I use the tablet location service instead of PAW on Skydemon then I also don't see the traffic on screen. So I lose both traffic and airspace awareness which is no good.

In which case, as Paul has posted, you either need to to do some fault finding with a different Android device or try the same with iOS.

47

Technical Support / Re: Enabling Traffic on an Advanced Flight Systems EFIS

« on: October 13, 2023, 11:48:59 am »

I was getting incessant "Traffic" alarms coming through on the audio and couldn't seem to be able to turn them off no matter what I changed in the config settings. Will test more.

Where is the audio being generated? In the EFIS or in the PAW? If in the PAW and audio to your intercom then simply adjust the ranges on the PAW Radar screen.

If in the EFIS, then you need to adjust ranges in the EFIS whilst leaving the PAW ones fully open/no limits. If you are desperate, then you can reduce the amount of warnings (by discarding the ones further away) by reducing the limits of reports in the PAW Radar Screen. This is not the correct way to do it, you should leave the Radar screen unlimited and cut back on warning in the EFB/EFIS. I know as I write this that Peter R will be flagging up warnings about doing things the correct way.

Also, on the EFIS, the Aircraft Image was accompanied with an arrow and a couple of sets of 0000s. What are these, and is there a way to remove them from the feed to the EFIS? When I zoom out, they are merged with the aircraft image and when I zoom in as shown in the image they move back and forth in front of the aircraft image. See attached:

Any ideas how to remove?

Is the image the one of your aircraft or other aircraft? If it's of other aircraft then it looks like there is some configuration to be done in your EFIS. Again without the exact model of EFIS it's hard to tell or for others with the same to recognise it and help.

48

Technical Support / Re: Waiting for device

« on: October 10, 2023, 11:25:41 pm »

I've now tried flying with Pingmon firing a ping every second to 192.168.1.1 and it made no difference for me, I still got multiple PAW disconnections 
It always seems to happen at just the wrong time as well, when I most need to know where I am in confined airspace and is very distracting, bordering dangerous.
I can't justify buying a new tablet until I find one that works with PAW so I think I will need to find an alternative to PAW that will work.

Connect the audio out from the PAW to the audio input of your radio or intercom, and get audio alerts for traffic.

Run the tablet using its own location services. Then it will not lose its location when you are transiting airspace. There will be no on screen traffic, but then you have audio alerts.

49

Technical Support / Re: WIFI / unit offline

« on: October 05, 2023, 08:57:43 am »

Can you see any lights either on (red/green) or flickering inside the PAW?

50

Technical Support / Re: Enabling Traffic on an Advanced Flight Systems EFIS

« on: October 05, 2023, 08:56:06 am »

Thank you Steve.

Do you know what the (TBD) after the GDL90 and MAVLINK options mean? The reason I ask is because in the EFIS manual it states that the ADSB settings means the GDL90 protocol. Assuming that to be true then using the one of the three ADSB settings matched with the PAW GDL90 output at a matching speed should work..... but it doesn't.

Andrew.

I think you can ignore the ADS-B settings - you need to set the serial port to do traffic, then within the settings for traffic choose GDL90/NMEA115. Then you need to set the PAW to do GDL90 out, at a baud rate of 115,200 baud.

I've not seen TBD before but which model of Advanced Flight Systems EFIS is it?

In both pictures it looks to me like you are choosing a role for the Serial Port 0, then choosing settings within that role to make it work. So Traffic needs to be green, then within Traffic make your settings as needed.

51

Technical Support / Re: Enabling Traffic on an Advanced Flight Systems EFIS

« on: October 03, 2023, 11:45:59 pm »

At a guess, you would set Traffic/Serial 0 if that's your port 1 to be GDL90/NMEA115K on your EFIS, and then set the Rosetta port driving it to GDL90 in the protocol list and also to the right baud in the speed drop down, which would be 115,200 then be sure to save the changes made.

52

Technical Support / Re: Voltage error message on iphone

« on: September 17, 2023, 06:39:12 pm »

I’m using Rosetta. The following in the USB ports : dongle, GPS, aircrew, and Wi-Fi. The PAW is powered from the 12 volt cigarette lighter using an Anker QC adapter. Even with the voltage error message on the iPhone the radar screen seems to be giving me all the info it’s supposed to and generally works very well

With all due respect, the "it is working so what is the problem?" approach has a slight flaw in the logic.

When the voltage is low, the processor may throttle itself in terms of processing speed/power and whilst things will work, they will not necessarily work how they are meant to.

The voltage alarm is most likely caused by the Aircrew device, if it is powered via its USB port, unplug it and the problem will probably go away.

If you need a data link to the Aircrew device to display traffic, then see if you can power the device directly with 12V in and just use the USB for data input.

There is a 12V input on the back.

I think you'll find elsewhere on this forum that people have been advise against powering Aircrew from a PAW...

Lee can give you precise details about how much throttling affects the PAW, but if you continue to use it whilst throttled you are asking for  other problems to arise at some point.

53

Technical Support / Re: Voltage error message on iphone

« on: September 17, 2023, 04:14:25 pm »

I think the iPhone is a red herring. The PAW just monitors voltage and complains if it is too low.

How does the PilotAware get its power input?  Via an Anker 12V to USB converter, a Charge 2/4 or a power pack, or something else? If a power pack is it low?

If something else then this is very often the problem. There are recommended power sources for a PAW and using other things is often the source of problems.

Is anything plugged into the PAW USB ports other than the GPS, Wifi dongle or the SDR modules? If so, unplug it, as charging something over and above the standard complement of modules is also a known point of failure.

54

Technical Support / Re: No aircraft audio alerts on Skydemon but visible on radar

« on: September 03, 2023, 03:10:42 pm »

It's worth considering that a tiny bit of static, let alone normal radio reception can cause the SkyDemon verbal warnings to stay quiet. I am not sure if this is a SkyDemon thing (I cannot find any reference to muting in the manual) or if it is the radio settings. I have my iPad connected to SkyDemon via Bluetooth, so I do not think it is necessarily anything to do with my radio muting settings. What I do know is my SkyDemon traffic audio is non-existant if there's radio chatter or static.

I'd definitely agree with this if the PAW had been taken into a Microavionics intercom via a 3.5mm jack, as the radio ducks all the other audio inputs. Think it's the same for BT...

55

Technical Support / Re: Waiting for device

« on: September 03, 2023, 01:17:27 pm »

I'll just muddy those waters by saying I have an iPad Mini 4 and not an Android in sight 

But you can still look at received RF power for the Wifi network...

56

Technical Support / Re: No aircraft audio alerts on Skydemon but visible on radar

« on: September 03, 2023, 01:16:14 pm »

This will show if the alerts were generated by the Rosetta. If not, Rosetta settings, if yes, then an SD problem.

Lots of speaker alerts visible on the trace. Closest aircraft was further than I thought at just under 2nm and 300ft below but while initially travelling right to left was then in front of me same direction for a bit before I changed heading. If all the speaker traces are things I was likely to have heard then I didn't. Very odd

I'm looking at SD now and the audio alerts for trafifc are set separately from airspace, obstacle and terrain. So it is possible to have traffic verbal information unticked, hence no traffic info, and yet all the other warnings  working.

YMMV

I can only suggest that you go back to Skydemon, and check the traffic box is ticked and the limits set correctly, and also check the same settings in the PAW, but the PAW less likely as it's recording alerts being made...

57

Technical Support / Re: Waiting for device

« on: August 31, 2023, 10:26:22 pm »

If anyone is concerned about the PAW receiving GPS, they can download the tracklog for the particular flight from the device and upload it to playback.

When scrolling through the tracklog, the number of satellites received at any time will be show IIRC.

58

Technical Support / Re: No aircraft audio alerts on Skydemon but visible on radar

« on: August 31, 2023, 10:42:41 am »

May I suggest extracting the track logs for the flights in question from the PAW Rosetta and uploading them to Aircrew/PAW playback?

You can leave them as not public but then send the resultant link from the upload to Lee, or anyone else you want to share with.

Audio alerts at PAW level will be marked on the trace with a speaker...

https://playback.pilotaware.com/playback/

This will show if the alerts were generated by the Rosetta. If not, Rosetta settings, if yes, then an SD problem.

59

Technical Support / Re: Waiting for device

« on: August 31, 2023, 10:18:59 am »

App details separate. Attachment limits are very small and difficult to comply with...

60

Technical Support / Re: Waiting for device

« on: August 31, 2023, 10:17:35 am »

Running Skydemon on my 'bad' tablet and good phone.
Lots of disconnections on the tablet after 10 to 15 mins, but the phone was rock solid.
I think this more of an Android issue than a hardware problem.
I'll try putting a sim in the tablet to see if its is a network problem? (clutching straws)

The SIM may confuse the issue, as if the table connects to the Internet directly over CGNAT it may not see any of the PAW LAN. It might still connect via Wifi though...

I'd suggest that you load the same Wifi analytics app on both phone and tablet. As an example, VREM Software Wifi Analyzer.

Compare them side by side looking at the same Wifi networks. Any noticeable difference in receive power would point to problems in the RF amp or internal antenna damage?