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 - PCKnight

Pages: [1]
1
Technical Support / Re: IGrid and phone reception
« on: September 10, 2022, 05:24:43 pm »
Hope these comments help.

I had noticed that I was frequently losing the GSM signal. I assumed that this was just the way it was going to be as I usually fly about 3000 - 3500 feet and the mobile masts are obviously transmitting most of their energy horizontally rather than vertically. I managed to maintain a connection (on iPhone 13) for about 30 - 40 % of the time.

I fly a Jabiru J430 and had been resting the phone on the P2 seat. The P2 seat has the header tank immediately beneath it with 5 litres of Avgas in it. I have no idea of the signal attenuation of Avgas, but I moved the phone to a position in the P1 footwell. In this location the signal is only attenuated by the thickness of the glass fibre fuselage. The result was surprising and encouraging.

I found that on my usual route I was holding the GSM signal almost 100% of the time. almost no drop off, signal was in the green.

Lesson learned is that the GSM signals are already weak for reasons that others have discussed so the position of the phone can be critical for maintaining and getting a good data stream for the IGRID function. I appreciate that this is an aircraft specific comment, but I would suggest that if you are getting GSM drop-off try a different position for your phone to improve reception
Peter

2
I agree. I now know how to get the WiFi connection to work every time.

The iPhone has to be open at the hotspot page. If it is then the PAW will select the iPhone Hotspot automatically and ignore all other Hotspots that may be around. This is when using an iPhone 13 running 15.6.1.

I did find that the network connectivity was a bit poor showing the orange tab but that was probably when at 4000 over rural bits. When it went green extra traffic would spring up and the tab would indicate Atom1 or Atom 2 which I assume is the server it happens to find. I was a bit surprised that I could not maintain a signal for longer as it is a fibreglass aircraft with, presumably, line of sight to the telecom mast.

3
A lot of trials and errors with this. Ipad running SkyDemon, Uavionix ADSB out, Pilot aware rosetta running latest software.

There is no automatic connection to IGrid via the iPhone 13 hotspot. If I look at the list of WiFi hotspots that the Paw is seeing it will include the Uavionix if I have switched it on and  on a good (or bad ) day it picks up the WiFi signal from the HP printer in the ATC Tower. If I switch the iPhone to the hotspot page the iPhone will appear as a hotspot. I can then select it and it appears to be stable as long as the phone is on the hotspot page. I am not sure it will remember everything for next time but I will try it tomorrow and report back. The iPhone being open on the hotspot page seems critical to success
Peter

4
OGN-R PilotAware / ATOM station avoid direct overhead transit.
« on: May 02, 2022, 04:05:30 pm »
My apologies if this has been discussed before.
For the last 12 months I have had an ATOM station installed and it works well. I have noticed that when I am flying I have a tendency to use ATOM stations as waypoints and fly direct from one to another. This also allows me to get a clear result on the Vector software when I am checking the performance of my Pilotaware. However there is a slight downside to this behaviour. When sitting in the garden I have noticed that there seem to be an increase in the number of aircraft transiting overhead the ATOM station. I don't mind but a couple of neighbours have commented on the increase but not yet made the connection with the aerials strapped to the side of our greenhouse..
I have also noticed that this increase in transits will increase the density of aircraft in the vicinity of the ATOM station and could result in a very slight increase in the chance of an airprox which is the very thing the PAW is intended to avoid.
When I was doing IR/IMC training my instructor always recommended that if I was using an VOR or NDB I should fly 0.5 miles to the right of the beacon. That meant there was a good chance of separation and an increased prospect of spotting any aircraft that was flying through the beacon overhead. So unless anyone can see a snag that I have not spotted could I suggest that we all try to fly 0.5 miles right of the ATOM beacon rather than direct through the overhead. (It will also keep my neighbours happy but they won't know why!)
Peter

5
Unfortunately the Apple update to 14.0.1 has no effect on the problem.

As others have found if you connect via Flarm Air connect the PAW will work and show location.

If you then switch back to PilotAware in third party devices the iPad will connect as usual when you select PilotAware from Go Flying. I did not have time to try to see if all the traffic options were function as usual but the radar screen was certainly OK.

So it looks like the origin of the problem is some connectivity glitch between SkyDemon and PAW, whether exacerbated by Mr Apple or not I cannot tell. 

The only other idea I had was to reinstall SkyDemon but that is for later in the day.

Peter

6
I have been having the same issue with SkyDemon in  jabiru J430 (so no bits of metal to interfere with the signal). SkyDemon will still not connect even when a few centimetres from the Rosetta. But iPad will still connect direct to the PAW over 192.168.1.1

There are no other sources of interference as these tests have been outside the aircraft.

Switching off an on again has no effect on  the problem.
Peter

7
Technical Support / SkyDemon Connectivity
« on: September 27, 2020, 06:02:05 pm »
I have a PilotAware Rosetta. It did have the 2019 software but I have successfully updated to the new September 2020 software version.
I use an iPad mini 4 with latest software (14.0). I can log onto the PAW via 192.168.1.1 and everything is working OK. Radar screen works and traffic is being detected.

HOWEVER I cannot connect to the PAW via SkyDemon. I just get the message "connecting to device" and nothing happens. Until a couple of weeks ago it worked perfectly. It would display "Connecting to device", then announce how many satellites it had found and off we went. I have checked the set-up in SkyDemon and everything is as it is meant to be.
The problem occurred first in the 2019 version of the PAW but is exactly the same in the new 2020 version.

I didn't touch or change anything before the problem appeared but there may have been SkyDemon updates or Apple OS updates in between it working and it not working, I'm just not sure on that point.
Advice would be welcome  before I start pushing buttons at random!

Peter

8
General Discussion / Re: Collision Aware
« on: February 06, 2016, 07:51:39 pm »
Thank you. I was beginning to doubt my ability to navigate around the Apple systems. I was only attracted to using the iPad GPS as I thought it would reduced the power requirements by not having a GPS dongle on the Pi.
However as the system has been running for 6 hours on a battery pack this may not be an issue. I will have a go with the NMEA system just to see how it works.
Peter

9
General Discussion / Collision Aware
« on: February 06, 2016, 03:19:31 pm »
I must be missing something. I have looked on iTunes store and on the apple apps store and I cannot find the collisionaware app anywhere.
Can someone please give me a hint as to where to go to find it as I would like to use the iPad GPS rather than the gps dongle in the raspberry pi.
Many thanks
Peter

Pages: [1]