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

Pages: [1] 2
1
Technical Support / Re: Waiting for device
« on: November 18, 2023, 06:10:33 pm »
It appears that Vic has found the simplest solution to this problem, although I haven't tried it myself yet.  I haven't had any issues when running Pingmon*.

I'm adding this as a postscipt for completeness.

I managed to borrow a Google Pixel phone from a collegue running 'stock' Android 13 and ran it alongside my Samsung Galaxy A7 lite (without Pingmon running)  for about 45 minutes. The Samsung was dropping the connection at random intervals whilst the Google Pixel was rock solid. So it seems that the issue is the customisation(s) that Samsung (and possible other manufacturers) make to the basic Android OS rather than Android itself.

As far as the Samsung goes I suspect it may be the Knox security software as I know from colleagues it causes other issues when used with  work systems

*except the time I hadn't increased the "stop after" interval to 2 hours (I probably ought to set it to never) and the connection dropped as I was nearing my destination

Brooklands

2
Technical Support / Re: Waiting for device
« on: October 07, 2023, 12:11:43 pm »
Colled,

I don't know how pingmon affects battery life on the tablet for certain, but I don't think it has a significant effect - I haven't noticed anything on the flights I've done since I started using it.  I can only guess why it keeps the connection up whereas incoming data doesn't.

@Lee - I've done a test on the ground were I tried setting the PAW to TCP/Flarm and connecting SD using that but I still get dropouts, although they are not as bad as setting the PAW to "All"

Brooklands

3
Technical Support / Re: Waiting for device
« on: September 24, 2023, 10:24:04 am »
Deker, 

Glad to hear that its worked for you as well, I had no isses yesterday on my trip to/from Halfpenny Green with pingmon running.  I'm not sure that the reverse ping would work though: my suspicion is that by forcing the tablet to constantly ping the PAW it stops the connection dropping some how.

@Colled - what make of tablet are you using?  I'm trying to work out if this is purely a  Samsung issue or a more general Android issue.  I'm not running iGrid so that's not causing the problem.  Try installing and running pingmon as this seems tohave 'fixed' the issue for Deker and myself.

I don't think its the lack of internet connection as my Nexus 7 (running Android 6) doesn't drop the connection to the PAW even though it recognises that it doesn't have an internet connection.

Brooklands

4
Technical Support / Re: Waiting for device - A Breakthrough ?
« on: September 18, 2023, 06:44:58 pm »
I think I have found a kludge/work around for the problem (I hesitate to call it a fix).

I was doing some tests on the ground to try and find out what was happening to the WiFi connection between my Samsung Galaxy Tab A7 Lite (SM-T220)and the PAW.  I downloaded an app called PingMon (https://play.google.com/store/apps/details?id=com.mishuto.pingtest&hl=en&gl=US) to monitor the WiFi connection to see if I could see it dropping.  With Pingmon running and Skydemon connected to the PAW in go flying mode I didn't get any dropouts over the hour I ran the test for.

It also worked fine on my flights to and from Fenland on Saturday.

I need to do some more testing to find the optimum settings.  You need to increase the time Pingmon runs before it stops itself (the default is one hour) but  you can set it to not stop until you close the app.

Brooklands




5
Technical Support / Re: Waiting for device
« on: September 09, 2023, 11:57:09 am »
My experience is similar to Deker's - its fine on my old Nexus 7 running Android 6.  The problem only occurs on my Samsung Galaxy Tab 7 running Android 13.

The Samsung tablet used to be OK with my Skyecho 2, but last time out I had issues with it losing the connection to the SE2 as well.

I managed to borrow a a Google Pixel running  Android 13 off a colleague for a test on the ground and didn't see any warnings  on the screen with that over about an hour, but was also expecting audio warning and only found out afterwards the volume had been turned down.

I think its an issue with Android 13,or perhaps just Samsungs implementation of it.

Brooklands

I

6
Since you have a set of Lightspeed Zulus you could try linking them to the tablet via bluetooth rather than use a cable

Brooklands

7
Technical Support / Re: Waiting for device
« on: June 18, 2023, 04:03:14 pm »
An update.

I haven't been able to reproduce the problem where the new tablet kept dropping the connection to the PAW as soon as I told SD to use it.

On the trip to Leicester yesterday I had my old (Android 6) tablet connected to the PAW and my new tablet (Android 13) connected to the Skyecho.  Neither lost the connection.

On the way back I set up the PAW with iGrid, but missed enabling the router setting and the new tablet lost the connection after about 20 minutes but reconnected immediately.

I've done some more tests today at home with the PAW set up with iGrid via my broadband connection but SD is still loosing the connection.  Its ok for about 15 - 20 minutes the I get the connection lost audio message but the table reconnects almost immediately it then goes another 10 -1 15 minutes before dropping again and reconnecting before going into a phase where it constantly drops and re-connects, sometimes immediately and sometimes after a few seconds.  I also re-ran the test with the Skyecho and the connection stayed up until I stopped the test after 40 minutes. 

I've had a look at the two links but I don't have the "Avoid poor connections" option in the Advanced settings and I'd rather not root the device which the others suggestions seem to need.

Brooklands

8
Technical Support / Re: Waiting for device
« on: June 05, 2023, 06:55:06 pm »
I encountered this problem yesterday with my new Samsung Galaxy Tab A7 Lite (SM-T220 model, Android 13) and my PAWClassic with the latest PAW software. 

When I connected the tablet to the PAW wifi it detected that there wasn't an internet connection and asked if I still  wanted to connect which I told it to do.  As soon as I told Skydemon to use pilotware it connected then proceeded to loose the connection and re-connect every couple of minutes.  I'd disabled power saving on the tablet and any other settings that  I thought may affect it.  I tried changing the wifi power settings on the PAW but it made no difference

As the PAW wifi connection was unusable I then tried connecting it to my Skyecho and had no disconnects at all (during a one hour flight) which makes me think that it maybe something in the PAWwifi setup.

I've done some digging today and had a look at the wifi settings on the Skyecho and its got the wifi channel set to auto (and was using channel 11).  I tried setting the PAW to channel 11 and the connection in Skydemon stayed up for about 10 minutes before I got the connection lost message so some improvement.  I'm going to try setting the wifi channel to auto and see what happens. 

I'd like to try changing the mode setting but as I don't know what it does I'm concerned that I may lock myself out of the PAW.

One other thing I noticed was that the tablet seems to run some sort of check on the wifi connection every minute or so

My old Google Nexus 7 (Android 6) had no issues at all so I was able to use that.

Brooklands

9
Technical Support / Re: 1090 Sensitivity
« on: April 10, 2022, 10:51:04 am »
David,

See this post.  I think that's the standard dongle

Brooklands

10
Technical Support / Re: Rosetta stopped working
« on: August 15, 2021, 06:17:01 pm »
That looks to me as though the software hasn't installed properly on the SD card as its failing during the start up.  I think you need to try completely reformatting the card and re-installing PilotAware.  The other possibility is there is a hardware fault on th Pi.

Brooklands

11
Technical Support / Re: Radio interference
« on: May 01, 2021, 11:03:02 am »
Another possibility if nothing else works: I had a similar problem with my PAW (classic, homebuilt).

I was getting noise on the radio which showed up as the radio in receive mode.  After some fault finding I came to the conclusion that it was the old SDR ADSB dongle and replaced it with a new NooElec NESDR Nano 2 which had fixed the problem.  Would be worth borrowing one from somebody else if none of the other suggestions work and see if that helps before ordering a new one.

Brooklands

12
Technical Support / Re: Missing Vector Plot
« on: April 20, 2021, 10:33:37 pm »
Lee,

Both were activeon the 4th.  Flight was 15:30 to 16:30. Looks like the break in capture was responsible for the flight not showingup.

Brooklands

13
Technical Support / Missing Vector Plot
« on: April 18, 2021, 10:04:40 am »
I'm trying different locations of the aerial in the aircraft in an attempt to optinmise the position and improve coverage but I can't find the plot for the flight I did on the 4th April.  I can see the previous flight on the 31st March.  I've got a track file for the flight on the 4th so I know the unit was working. Hex ID is 402bd6.

I've run the track file through the aircrew playback and I can see it was picking up ground stations during the flight

Any suggestions as to why its missing?

Thanks
Brooklands

14
Technical Support / Replacement ADSB dongle
« on: October 25, 2020, 06:11:30 pm »
It looks like the ADSB dongle in my PAW (self built classic) in on the way out.  Is the NooElec NESDR Nano 2+ still the best replacement?  I can't see it on the PilotAware Store(which doesn't surprise me at the moment), but I can find them on Amazon.

Thanks
Brooklands

15
General Discussion / Expired Certificate
« on: June 27, 2020, 01:02:42 pm »
Just in case you weren't aware  ;) the certificate on the main pilot aware website (https://pilotaware.com) expired yesterday (26th).

Brooklands



Pages: [1] 2