1
Technical Support / Re: PAW upgrade and Skydemon
« on: June 27, 2019, 06:54:21 pm »
But - apart from that - it still shows up on SD as a positional target, just like a PAW or ADSB target? (No more bearingless circles?)
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.
Pages: [1] 2
2
Technical Support / PAW upgrade and Skydemon
« on: June 27, 2019, 03:44:22 pm »
Apologies if this has already been asked but with the new update does anyone know how Mode S/3D targets show up on Skydemon? Is it the same as PAW 'Radar' - with an indication of the age of the target - or otherwise? (I tend to only use SD for traffic because of potential overload with 2 screens.)
3
General Discussion / Re: PAW and Gliders
« on: April 08, 2019, 03:17:58 pm »
OK thanks. I was confused on my last flight when Farnborough called out primary glider traffic but I could only see what looks like "normal" - i.e. powered - aircraft on SD. After checking the screenshots more closely I now see the weeniest little G next to the aircraft symbol. Would never spot that in the heat of the moment.
Generally speaking - and I know this is an SD issue not a PAW issue - I find the depiction of other traffic and the little up/down/level symbols next to them too small - and my eyes are supposedly OK according to my last test!
SD also seems to be a bit funny about bearingless traffic - you get the circle but no vertical distance information. For that you need to go to PAW Radar, I think, and/or PAW audio. Another reason for me not to use SD's own new audio, at least until/unless they include that bearingless info too.
Generally speaking - and I know this is an SD issue not a PAW issue - I find the depiction of other traffic and the little up/down/level symbols next to them too small - and my eyes are supposedly OK according to my last test!
SD also seems to be a bit funny about bearingless traffic - you get the circle but no vertical distance information. For that you need to go to PAW Radar, I think, and/or PAW audio. Another reason for me not to use SD's own new audio, at least until/unless they include that bearingless info too.
4
General Discussion / PAW and Gliders
« on: April 08, 2019, 12:49:02 pm »
Can someone tell me how glider traffic is displayed on PAW when using Skydemon? Obviously I'm talking about FLARM/Power FLARM glider traffic picked up via an OGN-R ground station. Does it have a different symbol (like, um, a glider??) or is it identified in any other way?
Also, is there a way of knowing if you're in range of an OGN-R aerial on SD or do you have to go to the PAW Radar page to see it? I saw one aircraft symbol with the word G/STN which presumably stands for Ground Station but then again I might be wrong?!
Also, is there a way of knowing if you're in range of an OGN-R aerial on SD or do you have to go to the PAW Radar page to see it? I saw one aircraft symbol with the word G/STN which presumably stands for Ground Station but then again I might be wrong?!
5
General Discussion / PAW and SkyDemon traffic alert banners
« on: March 10, 2019, 11:17:50 am »
I flew recently using my Pilot Aware linked to SkyDemon as an exercise to see how it all worked together. This is my second flight using PAW + SD and thanks to the help of forumites on here most of the issues I had the first time round have now been resolved. So thank you!
On this second flight I had the new (latest version) SD audio alerts switched off, preferring to use PAW audio alerts since - unlike SD - they also include bearingless traffic.
However, although I was getting the normal SD 'radar' screen on the bottom right of my ipad screen and I could see traffic moving around on the map, this time I never received any traffic banner alerts for positional traffic - even where that traffic was close enough to turn red.
Have I missed something here? By turning off SD voice alerts have I also inadvertently switched off the banner alerts? Or is there some other button that should have been pressed/not pressed??
Any help most gratefully received!
On this second flight I had the new (latest version) SD audio alerts switched off, preferring to use PAW audio alerts since - unlike SD - they also include bearingless traffic.
However, although I was getting the normal SD 'radar' screen on the bottom right of my ipad screen and I could see traffic moving around on the map, this time I never received any traffic banner alerts for positional traffic - even where that traffic was close enough to turn red.
Have I missed something here? By turning off SD voice alerts have I also inadvertently switched off the banner alerts? Or is there some other button that should have been pressed/not pressed??
Any help most gratefully received!
6
Technical Support / Re: Dedicated screen interface
« on: January 17, 2019, 09:13:53 am »
This looks fantastic! Much better than using my iPhone velcroed to the panel to get PAW radar. Plus I like the idea of a second AI as a back up to our G5 for the just-in-case moment.
Any idea when this will be out, available and PAW compatible?
Stodge
Any idea when this will be out, available and PAW compatible?
Stodge
7
General Discussion / Re: first test flight with Rosetta - advice?
« on: January 16, 2019, 09:23:27 am »
OK many thanks for all this. Very useful!
Peter - one thing I would say is that I was in fact getting audio alerts for bearingless, but with no audio vertical separation information. This was clearly not due to traffic 10,000 ft plus above me, but to other traffic in the circuit at Turweston (which we could sometimes see) prompting a whole series of audio alerts/notices/danger warnings without any vertical reference at all. That was the stressful bit. Had there been audio warnings of vertical separation it would have been both much more useful and much easier to manage.
This is why I'm v keen to understand how to ensure I get audio alerts for bearing less contacts with vertical separation, as you say should be the case, the next time I fly.
Could this also be due to being on GDL90 rather than PAW? Or something else I'm doing wrong?
Art any rate I'll get those screenshots overt you on the next flight. Hopefully soon it will all come together!
Cheers and thanks again,
Stephen
Peter - one thing I would say is that I was in fact getting audio alerts for bearingless, but with no audio vertical separation information. This was clearly not due to traffic 10,000 ft plus above me, but to other traffic in the circuit at Turweston (which we could sometimes see) prompting a whole series of audio alerts/notices/danger warnings without any vertical reference at all. That was the stressful bit. Had there been audio warnings of vertical separation it would have been both much more useful and much easier to manage.
This is why I'm v keen to understand how to ensure I get audio alerts for bearing less contacts with vertical separation, as you say should be the case, the next time I fly.
Could this also be due to being on GDL90 rather than PAW? Or something else I'm doing wrong?
Art any rate I'll get those screenshots overt you on the next flight. Hopefully soon it will all come together!
Cheers and thanks again,
Stephen
8
General Discussion / Re: first test flight with Rosetta - advice?
« on: January 15, 2019, 10:34:03 pm »
PS - incidentally, on Ian's config settings, I'm not quite clear why in PAW the vertical separation range for both bearingless and positional contacts is +/- 2000 ft but in SD the vertical display range is +/- 50,000 ft?
Or maybe it doesn't matter what the SD figure is if the target ranges are filtered initially by PAW?
Or maybe it doesn't matter what the SD figure is if the target ranges are filtered initially by PAW?
9
General Discussion / Re: first test flight with Rosetta - advice?
« on: January 15, 2019, 10:28:37 pm »
Thanks so much for all this fantastic support Peter and Ian!
I will try to get the info regarding the transponder from one of my fellow group owners and come back to the forum when I do. (And yes, I am G-MICI). Perhaps there is something in the transponder set up which is causing the problem - not impossible, given it was upgraded to Extended Squitter ADSB-OUT last month.
I'm also sure the business of selecting GDL90 explains why I never got visual warnings on SD for bearingless traffic (but did get them on PAW radar). I'll check when I next fly - hopefully on Saturday - and hopefully this time with Pilot Aware and not GDL90 selected.
However I'm still not clear - does PAW give vertical separation audio alerts as well as visual for bearingless? I think Ian is suggesting this is the case - and that the actual figure is given if the vertical distance is less that 1,000 feet - but can you or somebody confirm this is indeed what is supposed to happen? If so, and even though I had configured PAW for bearingless with Mode C/S Filter at short-range and +/-1000', I never received such an alert, merely the words 'Traffic Notice,' 'Traffic Danger' etc as appropriate - all of which can be quite stressful and not so helpful when things get really busy up there!
When I next fly I will configure everything as suggested and come back on here with the results. I do hope too that this discussion is useful to more than just me - I think this technology is fantastic but I just need to configure everything so that it all works as well as it should!
I will try to get the info regarding the transponder from one of my fellow group owners and come back to the forum when I do. (And yes, I am G-MICI). Perhaps there is something in the transponder set up which is causing the problem - not impossible, given it was upgraded to Extended Squitter ADSB-OUT last month.
I'm also sure the business of selecting GDL90 explains why I never got visual warnings on SD for bearingless traffic (but did get them on PAW radar). I'll check when I next fly - hopefully on Saturday - and hopefully this time with Pilot Aware and not GDL90 selected.
However I'm still not clear - does PAW give vertical separation audio alerts as well as visual for bearingless? I think Ian is suggesting this is the case - and that the actual figure is given if the vertical distance is less that 1,000 feet - but can you or somebody confirm this is indeed what is supposed to happen? If so, and even though I had configured PAW for bearingless with Mode C/S Filter at short-range and +/-1000', I never received such an alert, merely the words 'Traffic Notice,' 'Traffic Danger' etc as appropriate - all of which can be quite stressful and not so helpful when things get really busy up there!
When I next fly I will configure everything as suggested and come back on here with the results. I do hope too that this discussion is useful to more than just me - I think this technology is fantastic but I just need to configure everything so that it all works as well as it should!
10
General Discussion / Re: first test flight with Rosetta - advice?
« on: January 14, 2019, 08:49:18 pm »
PS - forgot to mention I don't have FLARM or SkyEcho. I do have ADSB-OUT linked to my Trig transponder (this was done by my avionics chap at our recent annual) and the GPS info for this comes from the panel GTN 650.
11
General Discussion / Re: first test flight with Rosetta - advice?
« on: January 14, 2019, 08:46:41 pm »
Thanks Peter, Ian and everyone here.
I am attaching a screenshot of my aircraft as a target in SD here, and also the hex code input in SD setup for my aircraft.
I don't have my PAW Rosetta unit here at home (it's in the aircraft at Denham) so I don't know how to access the PAW 192.168.1.1 address without it in order to send screenshots of my home and config pages there. Any suggestions gratefully received!
Two other quickies:
a. Regarding the voice alerts for bearingless traffic in PAW - do they contain the target's vertical distance or not. Am not clear, so don't know if I'm missing something vital here or not.
b. Finally, regarding the non-GPS signal issue in SD when selecting Pilot Aware, I appreciate that this might be because the unit was still referencing my home and not the airfield, but how can that explain why I instantly got a sensible GPS reading when I selected GDL 90 in the SD options?
Would dearly love to fix all this before my next trial run on Saturday!
Stodge aka Stephen
I am attaching a screenshot of my aircraft as a target in SD here, and also the hex code input in SD setup for my aircraft.
I don't have my PAW Rosetta unit here at home (it's in the aircraft at Denham) so I don't know how to access the PAW 192.168.1.1 address without it in order to send screenshots of my home and config pages there. Any suggestions gratefully received!
Two other quickies:
a. Regarding the voice alerts for bearingless traffic in PAW - do they contain the target's vertical distance or not. Am not clear, so don't know if I'm missing something vital here or not.
b. Finally, regarding the non-GPS signal issue in SD when selecting Pilot Aware, I appreciate that this might be because the unit was still referencing my home and not the airfield, but how can that explain why I instantly got a sensible GPS reading when I selected GDL 90 in the SD options?
Would dearly love to fix all this before my next trial run on Saturday!
Stodge aka Stephen
12
General Discussion / Re: first test flight with Rosetta - advice?
« on: January 13, 2019, 11:46:31 pm »
Hi Peter,
Thanks for this.
Regarding the alerts for bearingless traffic, your explanation seems to suggest that the voice alert will ALSO give vertical distance (you write ‘Traffic Alert xxx feet above (etc)') - but that is not the case for my unit. It simply says 'traffic alert' or 'traffic danger' etc - nothing about vertical distance (though there is that warning visual banner in the PAW radar). Am I doing something wrong? Certainly a voice alert giving vertical separation from bearingless would be a huge bonus!
Regarding the self-as-target issue - no, I am getting my own aircraft as an actual target sitting as a red aircraft symbol on top of my yellow aircraft symbol in SD with non-stop visual alerts. The hex code is correctly inputted in PAW, but there is also an option to include it in SD's own aircraft set-up page (along with the reg of course) which I duly did. Should I have? Could this be the source of the problem - i.e. that it should only be inputted in PAW but not SD? Very odd though. Trouble is I can't use PAW in SD unless I fix this somehow!
Best, Stodge
Thanks for this.
Regarding the alerts for bearingless traffic, your explanation seems to suggest that the voice alert will ALSO give vertical distance (you write ‘Traffic Alert xxx feet above (etc)') - but that is not the case for my unit. It simply says 'traffic alert' or 'traffic danger' etc - nothing about vertical distance (though there is that warning visual banner in the PAW radar). Am I doing something wrong? Certainly a voice alert giving vertical separation from bearingless would be a huge bonus!
Regarding the self-as-target issue - no, I am getting my own aircraft as an actual target sitting as a red aircraft symbol on top of my yellow aircraft symbol in SD with non-stop visual alerts. The hex code is correctly inputted in PAW, but there is also an option to include it in SD's own aircraft set-up page (along with the reg of course) which I duly did. Should I have? Could this be the source of the problem - i.e. that it should only be inputted in PAW but not SD? Very odd though. Trouble is I can't use PAW in SD unless I fix this somehow!
Best, Stodge
13
General Discussion / Re: first test flight with Rosetta - advice?
« on: January 13, 2019, 10:25:13 am »
Hi Peter,
Many thanks of this comprehensive response to my questions. (I have to say though that I'm still a little confused about the alerting criteria in bearingless contacts, but I'll leave that one for the moment! Basically, if it's red, get your eyes on stalks.)
One point I did forget to mention: when, before flight, I selected Pilot Aware in Skydemon in 'Third Party Devices' and then clicked Go Flying - again selecting Pilot Aware from the options available - my iPad could not get a GPS signal. I tried with another iPad and had the same situation. Nada. In the end I went back to Third Party Devices and, on a whim, selected GDL 90, then went to Go Flying and did the same. Hey presto - it worked! The GPS signal came in and my PAW was up and running in Skydemon.
This is not supposed to happen like that, right? Do you - or does anyone - have an explanation?
On the HEX code, just to be clear - I was not getting my own return as a target in PAW, just in SD. I checked to see if I'd entered the code incorrectly in SD in my aircraft settings and I hadn't. Given that I'm only getting myself as the target in SD but not PAW I can't understand how this is happening. It would be great to fix it because at the moment I can't use PAW in SD.
On the up, down. level symbols - to me this is not a question of screen brightness because everything else on the screen is normal. It's a question of emphasis in the graphic itself (like making a font bold) so that it stands out clearly. At the moment I think the symbols are too faint, at least for my eyes, which makes me spend more time than I want looking at the screen when I need to be looking outside. Perhaps others have had similar experiences?
Thanks for any help!
Stodge
Many thanks of this comprehensive response to my questions. (I have to say though that I'm still a little confused about the alerting criteria in bearingless contacts, but I'll leave that one for the moment! Basically, if it's red, get your eyes on stalks.)
One point I did forget to mention: when, before flight, I selected Pilot Aware in Skydemon in 'Third Party Devices' and then clicked Go Flying - again selecting Pilot Aware from the options available - my iPad could not get a GPS signal. I tried with another iPad and had the same situation. Nada. In the end I went back to Third Party Devices and, on a whim, selected GDL 90, then went to Go Flying and did the same. Hey presto - it worked! The GPS signal came in and my PAW was up and running in Skydemon.
This is not supposed to happen like that, right? Do you - or does anyone - have an explanation?
On the HEX code, just to be clear - I was not getting my own return as a target in PAW, just in SD. I checked to see if I'd entered the code incorrectly in SD in my aircraft settings and I hadn't. Given that I'm only getting myself as the target in SD but not PAW I can't understand how this is happening. It would be great to fix it because at the moment I can't use PAW in SD.
On the up, down. level symbols - to me this is not a question of screen brightness because everything else on the screen is normal. It's a question of emphasis in the graphic itself (like making a font bold) so that it stands out clearly. At the moment I think the symbols are too faint, at least for my eyes, which makes me spend more time than I want looking at the screen when I need to be looking outside. Perhaps others have had similar experiences?
Thanks for any help!
Stodge
14
General Discussion / Re: first test flight with Rosetta - advice?
« on: January 12, 2019, 12:41:48 pm »
Apologies for my typo but on point 2 it should have read: I had a real issue with the fact that traffic distance in PAW Radar and in audio warning configurations is given in KM and NOT NM.
15
General Discussion / first test flight with Rosetta - advice?
« on: January 12, 2019, 12:37:09 pm »
Many thanks first to those on here who helped me distinguish between the micro SD card and SD card adaptor in my previous post - not entirely obvious to someone who is not tech savvy like myself!
Yesterday I had the opportunity to try out my new rosetta 'in anger' (as it were) in a flight from my home base at Denham to Turweston. The unit was wifi'd to my iPad running SD and my iPhone (5S) running PAW Radar. Settings for bearingless contacts were short range and +/- 1000'.
I have some issues/questions as a result of this first flight which I'd be hugely grateful for help with!
1. Despite the fact that I had bearingless switched on in SD and also enabled (with Mode C/S filter) in PAW, a number of relatively close Mode S/C transponding contacts were not picked up. Talking to Oxford Radar, for instance, there was one near Rugby which was 5kms away and within 500 feet which I confirmed with Oxford was transponding with altitude Nothing was seen on the cockpit display(s) however. Could that be because 'short-range' is actually too short - even at 5kms?
2. I had a real issue with the fact that traffic distance in PAW Radar and in audio warning configurations is given in KM and NM. This makes no sense at all and could be quite confusing just when things get most busy. KM is used typically for visibility. NM is always used for traffic distance on an ATC radar service (and is also used in SD running PAW). With potentially quite a lot of data being displayed in the cockpit, why on earth complicate matters by making it necessary to perform mental calculations as to a target's distance? PLEASE in a software update can we have the display ranges - and audio alert ranges - in NM and not kilometres???
3. Given the bearingless settings I configured in PAW (as above) I could not understand what the criteria were for the different levels of alert (green, amber, red). Are they based on the target's transponding power or vertical distance from my aircraft or both? Does a red 'danger' alert, for instance, depend on the configuration settings? If one chose +/- 50,000', to take an example, would you get a red alert at, say, 1000 feet separation from a target, but if you chose, +/- 500 ft you would only get that red alert at, say, 100 ft? Because I don't know, I also don't know how much to worry - or how high (or low) in the sky to scan.
4. On my iPhone displaying PAW Radar the GS-OGN-1 banner goes slap over the vertical distance selected figure - so I couldn't see what I had selected or therefore change it (please see my attached photo).
5. On the same display an amber alert of traffic has its vertical distance figure almost completely hidden by the graphic of what looks like an aerial. Are these aerials OGN base stations? Is it just coincidence that it happens to be sitting at the centre of my aircraft or is this something else? Perhaps more worryingly, given the relative proximity of the traffic, this was potentially 'challenging' situation since I could not clearly see the vertical distance of the other target.
6. I also think the graphics identifying the up/down/level of other traffic is far too faint and not easily seen. One has to keep remembering that this is a busy cockpit environment, not an office desk, and you need to spend as little time as possible looking at the radar screen!
7. Can someone also actually tell me what GS-OGN 1 actually means? OGN is the Open Glider Network and I believe 1 means 1 base station - but GS? I can't find the answer to that one in any of the manuals.
8. Finally, though this might be a SD question, I kept getting my own transponder as a target even though I had set the HEX correctly both in PAW and on SD in the aircraft edit page. Anyone have an explanation? It got so annoying that I ended up switching it off.
So - these are my questions after my first flight. Have no doubt that PAW is going to be a great boon in time but I need to work through these wiggles first! Perhaps others have had similar issues?
If anyone can supply any answers to the above I will gladly buy him or her a decent drink! I really want to get this right.
Thanks!
Stodge
Yesterday I had the opportunity to try out my new rosetta 'in anger' (as it were) in a flight from my home base at Denham to Turweston. The unit was wifi'd to my iPad running SD and my iPhone (5S) running PAW Radar. Settings for bearingless contacts were short range and +/- 1000'.
I have some issues/questions as a result of this first flight which I'd be hugely grateful for help with!
1. Despite the fact that I had bearingless switched on in SD and also enabled (with Mode C/S filter) in PAW, a number of relatively close Mode S/C transponding contacts were not picked up. Talking to Oxford Radar, for instance, there was one near Rugby which was 5kms away and within 500 feet which I confirmed with Oxford was transponding with altitude Nothing was seen on the cockpit display(s) however. Could that be because 'short-range' is actually too short - even at 5kms?
2. I had a real issue with the fact that traffic distance in PAW Radar and in audio warning configurations is given in KM and NM. This makes no sense at all and could be quite confusing just when things get most busy. KM is used typically for visibility. NM is always used for traffic distance on an ATC radar service (and is also used in SD running PAW). With potentially quite a lot of data being displayed in the cockpit, why on earth complicate matters by making it necessary to perform mental calculations as to a target's distance? PLEASE in a software update can we have the display ranges - and audio alert ranges - in NM and not kilometres???
3. Given the bearingless settings I configured in PAW (as above) I could not understand what the criteria were for the different levels of alert (green, amber, red). Are they based on the target's transponding power or vertical distance from my aircraft or both? Does a red 'danger' alert, for instance, depend on the configuration settings? If one chose +/- 50,000', to take an example, would you get a red alert at, say, 1000 feet separation from a target, but if you chose, +/- 500 ft you would only get that red alert at, say, 100 ft? Because I don't know, I also don't know how much to worry - or how high (or low) in the sky to scan.
4. On my iPhone displaying PAW Radar the GS-OGN-1 banner goes slap over the vertical distance selected figure - so I couldn't see what I had selected or therefore change it (please see my attached photo).
5. On the same display an amber alert of traffic has its vertical distance figure almost completely hidden by the graphic of what looks like an aerial. Are these aerials OGN base stations? Is it just coincidence that it happens to be sitting at the centre of my aircraft or is this something else? Perhaps more worryingly, given the relative proximity of the traffic, this was potentially 'challenging' situation since I could not clearly see the vertical distance of the other target.
6. I also think the graphics identifying the up/down/level of other traffic is far too faint and not easily seen. One has to keep remembering that this is a busy cockpit environment, not an office desk, and you need to spend as little time as possible looking at the radar screen!
7. Can someone also actually tell me what GS-OGN 1 actually means? OGN is the Open Glider Network and I believe 1 means 1 base station - but GS? I can't find the answer to that one in any of the manuals.
8. Finally, though this might be a SD question, I kept getting my own transponder as a target even though I had set the HEX correctly both in PAW and on SD in the aircraft edit page. Anyone have an explanation? It got so annoying that I ended up switching it off.
So - these are my questions after my first flight. Have no doubt that PAW is going to be a great boon in time but I need to work through these wiggles first! Perhaps others have had similar issues?
If anyone can supply any answers to the above I will gladly buy him or her a decent drink! I really want to get this right.
Thanks!
Stodge
Pages: [1] 2