Suggestions for 10.3 |
Post Reply | Page <1234 9> |
Author | ||
oskrypuch
Senior Member Joined: 09 Nov 2012 Location: CYFD Status: Offline Points: 3057 |
Post Options
Thanks(0)
|
|
One man's distraction, is another's savior. Many ways to skin a cat. * Orest
Edited by oskrypuch - 30 Jul 2020 at 9:46pm |
||
brou0040
Senior Member Joined: 13 Dec 2012 Location: KIYK Status: Offline Points: 720 |
Post Options
Thanks(0)
|
|
You mean like from an unnecessary alert? :)
|
||
Aerochip
Groupie Joined: 24 Sep 2019 Location: Utah Status: Offline Points: 46 |
Post Options
Thanks(0)
|
|
I agree and why I'd like to see it changed. Fore example, on a GNS430, doing the same button sequence would not end you on the Flightplan page, which this is effectively doing.
|
||
teeth6
Senior Member Joined: 10 Mar 2014 Status: Offline Points: 741 |
Post Options
Thanks(0)
|
|
it would be nice but I believe the reason is you must be on the FMS page to select the waypoint to go direct to. In your example, you were already heading to the waypoint when the vector started so it was already highlighted but it you were going direct to a different waypoint, you’d have to select it on the FMS page and hit direct.
|
||
oskrypuch
Senior Member Joined: 09 Nov 2012 Location: CYFD Status: Offline Points: 3057 |
Post Options
Thanks(0)
|
|
Night time or distraction would be the classic issue on a VFR flight. * Orest
|
||
Aerochip
Groupie Joined: 24 Sep 2019 Location: Utah Status: Offline Points: 46 |
Post Options
Thanks(0)
|
|
Suggestion:
When on MAP page and say I'm on a vector and then want to go back direct to the waypoint that I had previously been tracking to, I would hit Direct, Enter, Enter. Upon doing so, the IFD440 defaults back to the FMS page. I think it is an issue because the FMS page shows a map much like the MAP page, but of course does not show data blocks, traffic, weather, etc. My suggestion would be for it to default back to the MAP page if that is what was previously being used.
|
||
nrproces
Senior Member Joined: 19 Sep 2016 Location: Marion, MT Status: Offline Points: 138 |
Post Options
Thanks(0)
|
|
KBIL when landing to the west, and KCVG when landing on the Center going South, come to mind...
|
||
Sauce
|
||
brou0040
Senior Member Joined: 13 Dec 2012 Location: KIYK Status: Offline Points: 720 |
Post Options
Thanks(0)
|
|
Totally agree, I have it in my checklist to ensure that the FLTA inhibit is disabled as a reminder. I just didn't think the last alert was warranted, there was no need for any urgent actions. KTSP is not a very mountainous airport, its in a pretty big valley. I landed behind a old jet, there is no tight maneuvering required here. It seems like an alert going off here when I told the IFD that this is my destination is an indication that it's a bit too sensitive - or I'm doing something wrong.
|
||
brou0040
Senior Member Joined: 13 Dec 2012 Location: KIYK Status: Offline Points: 720 |
Post Options
Thanks(0)
|
|
I'm not sure how you'd miss a critical FLTA warning if you are on a VFR 3/4 mile base flying the pattern to the destination in your flight plan.
Edited by brou0040 - 30 Jul 2020 at 12:01am |
||
oskrypuch
Senior Member Joined: 09 Nov 2012 Location: CYFD Status: Offline Points: 3057 |
Post Options
Thanks(0)
|
|
I have never seen an FLTA alert on a properly flown IFR approach. Really, by definition there shouldn't be any. But, I have certainly seen alerts when being maneuvered on visual, on occasion. The most obvious one is landing the island airport in Toronto (CYTZ), where once turned on base you encounter the downtown landscape, and alerts go off, PULL UP, etc. But, really, they are appropriate, as I am actually headed right for those obstacles, the CN tower and the rest, the system cannot know (and it would be dangerous to assume) that I will be turning away from these shortly. And, indeed, as soon as I turn final, that stops. If I have passengers, I brief them of the same, it is just treated as a "funny". If that is the kind of alert you are concerned about, and you frequent airports in the midst of terrain, landing not directly off an approach, then having a mute switch might make some sense -- just be doubly sure that it is not off when it shouldn't be. * Orest
Edited by oskrypuch - 29 Jul 2020 at 9:40pm |
||
Bob H
Senior Member Joined: 26 Jan 2018 Location: NH - KMHT Status: Offline Points: 290 |
Post Options
Thanks(0)
|
|
There is some high terrain around both of these airports. At KTSP, if you turned base ¾ nm from the end of the runway (not displaced threshold), you were on the edge of the exclusion zone and pointed right at some very high terrain. The exclusion zone at this VFR airport is most likely a 1 nm radius from the ARP. Seems to me the easy solution is to fly a tighter pattern or throw your disable switch when you are landing at a mountainous airport. For IFR airports where the runway configuration is known, the exclusion zone is 2.0 nm laterally and 4.0 nm off each runway end. I think the warning is appropriate under these conditions.
You’ve got your switch, so you’ve got the option to
silence it anytime you want. Edited by Bob H - 29 Jul 2020 at 9:40pm |
||
Bob
|
||
brou0040
Senior Member Joined: 13 Dec 2012 Location: KIYK Status: Offline Points: 720 |
Post Options
Thanks(0)
|
|
Alerts are a distraction rather than a safety feature if they go off when there is nothing actionable you should do to correct the situation. If you are flying the proper approach, you shouldn't get alerts. If you get terrain alerts every time you land and are doing things correctly, you would get desensitized to the alerts. The reason for the exclusion is because there are airports where you absolutely want the alerts if you aren't planning on landing there, you are too close to terrain, therefore you can't loosen then alerting criteria, but it'll be going off the entire approach if you don't provide the exclusion.
|
||
AviSteve
Admin Group Joined: 12 Feb 2018 Location: Melbourne, FL Status: Offline Points: 2139 |
Post Options
Thanks(0)
|
|
If the aircraft is within the runway exclusion zone, FLTA alerting should be suppressed. It depends on how tight to the runway you flew the pattern, but it's likely that the aircraft was outside the exclusion zone and that's why you got the alert. The TSO for terrain alerting is complicated and there's only so much we can do to eliminate nuisance alerts. Nevertheless, if you want to send us your logs along with the approximate date and time of the event, we can take a look to see if there's some way we can improve the behavior while staying within the TSO requirements. Send me a PM if you're interested.
Edited by AviSteve - 29 Jul 2020 at 1:35pm |
||
Steve Lindsley
Avidyne Engineering |
||
oskrypuch
Senior Member Joined: 09 Nov 2012 Location: CYFD Status: Offline Points: 3057 |
Post Options
Thanks(0)
|
|
Well, I think if you are heading for terrain, it should properly give you a terrain warning. The most likely time for CFIT, is during landing, so not a good time to suppress it. But, whatever works for you. * Orest
|
||
brou0040
Senior Member Joined: 13 Dec 2012 Location: KIYK Status: Offline Points: 720 |
Post Options
Thanks(0)
|
|
As stated, it was a terrain warning (not sure exactly which type, I didn't stop to write it down), I was right base for rwy 11 into KTSP. There is a small hill at the approach end of 11 and mountains further to the north. It does the same thing flying into L05. When flying into these airports, we know we are near the mountains and don't need distracting alerts when flying a standard approach for the airport. Against the wisdom of some vocal posters, I've installed a terrain alerting inhibit switch, and I'm very glad I did - and often suggest it to others. I like to keep the alerting enabled and only inhibit it when it's annoying. This works fine when flying through a pass and you can disable it for a few miles. But in this case, I wasn't expecting it to cause an issue and I had a new passenger with me and the thing started throwing startling unnecessary alerts for no valid reason.
Edited by brou0040 - 28 Jul 2020 at 11:00pm |
||
Bob H
Senior Member Joined: 26 Jan 2018 Location: NH - KMHT Status: Offline Points: 290 |
Post Options
Thanks(0)
|
|
Edited by Bob H - 28 Jul 2020 at 12:36pm |
||
Bob
|
||
brou0040
Senior Member Joined: 13 Dec 2012 Location: KIYK Status: Offline Points: 720 |
Post Options
Thanks(0)
|
|
I'd like to see issues with the terrain alerting when landing at published airports resolved.
It was my understanding that when near an airport, the terrain alerting is disabled, but that isn't the case. Is there a chance that the terrain that is triggering the alert when I'm pointing away from the airport (downwind or base) is beyond those limits even though the airplane is within the limits? I was on base turning final this weekend when that thing went off. Do I have to have a runway selected in the FPL to get it to operate properly?
|
||
nrproces
Senior Member Joined: 19 Sep 2016 Location: Marion, MT Status: Offline Points: 138 |
Post Options
Thanks(0)
|
|
Maybe a "Driftdown" circle based on current winds and terrain?
|
||
Sauce
|
||
Bob H
Senior Member Joined: 26 Jan 2018 Location: NH - KMHT Status: Offline Points: 290 |
Post Options
Thanks(0)
|
|
1. Terrain Awareness 2. Forward Looking Terrain Alerting 3. Terrain Caution Aural 4. Terrain Warning Aural
|
||
Bob
|
||
dmtidler
Senior Member Joined: 12 Feb 2016 Location: USA Status: Offline Points: 616 |
Post Options
Thanks(0)
|
|
The IFD piece of the puzzle looks normal to me; I have no experience with the EX5000 MFD and its integration with the IFD.
|
||
mfuesting
Newbie Joined: 14 Mar 2019 Location: Illinois Status: Offline Points: 11 |
Post Options
Thanks(0)
|
|
A nice new feature would be to make the data label (MSA for this area) which I display on the top of the map, turn red and flash anytime you are below the MSA to draw your attention to the fact that your are below MSA. Thanks!
|
||
Mike L Fuesting
|
||
Jandair
Newbie Joined: 19 Nov 2019 Location: KGPM Status: Offline Points: 16 |
Post Options
Thanks(0)
|
|
Sorry it took a couple of days... I wanted to get a screen capture of what I am seeing in the plane.
The other piece of the puzzle is the EX5000 MFD. I normally look at the trip page to get a big picture view of the entire flight plan. Notice the DTK entries for the last four items on the flight plan. (The ETE and ETA are not shown because I am on the ground.). All of the flight plan information comes from the IFD and my IFD displays look like the ones in your pictures.
So 133 degrees, then 357 degrees, then 131 degrees and finally 311 degrees back to KGPM. The NM are not exact because I am on the ground, but the delta distance for the last four waypoints is 158nm or about an hour from WESAT to KGPM. This reflects in all of the MFD fields including ETE, fuel needed, fuel remaining, etc... So if I enter the waypoints manually, everything looks good on the MFD. Bottom Line - Is this normal for an FMS system or a coding bug? |
||
dmtidler
Senior Member Joined: 12 Feb 2016 Location: USA Status: Offline Points: 616 |
Post Options
Thanks(0)
|
|
I tried this scenario in both an IFD100 as well as the iPad IFD Trainer. The identical results between the IFD100 and iPad IFD Trainer appeared to be normal IFD behavior for this type of arrival. Per the arrival instructions, the IFD adds a "Manual" 130 degree track vectors leg out of WESAT and that track terminates well beyond KGPM. The expectation and note on the arrival is that at some point along that track, ATC is expected to issue radar vectors off the arrival for an approach. I did not see any flight plan legs that return to WESAT after the 130 degree track leg.
While the map view looks like a great deal of extra flying is added, the flight plan legs and track distance doesn't add time or mileage for the vectors leg. The IFD appeared to correctly calculate the distance and time from WESAT to KGPM. In my experience, this appears to be normal FMS behavior for vectors legs. |
||
Jandair
Newbie Joined: 19 Nov 2019 Location: KGPM Status: Offline Points: 16 |
Post Options
Thanks(0)
|
|
Is there a preferred place to report things that seem to be coded wrong? Do they go to Jepp or through Avidyne?
On a recent flight, I loaded a flight plan from KLBB to KGPM then added the the TURKI.WESAT2 arrival into KGPM. The arrival procedure is manual termination with vectors to KGPM. The flight plan (and map view) adds a waypoint after WESAT and beyond KGPM and then a return to WESAT. There are no gaps in route. Added about an hour to the overall flight plan. If I enter each waypoint individually along the route, without the actual arrival, everything maps fine. I was able to duplicate this behavior in the IFD100 app. Is there something I need to add after WESAT to connect directly to KGPM?
|
||
chflyer
Senior Member Joined: 24 Jan 2013 Location: LSZK Status: Offline Points: 1022 |
Post Options
Thanks(0)
|
|
+1 acknowledging that the IFD claims to be GNS-compatible, not GTN-compatible. At this stage, Avidyne should not just be targeting more than GNS compatibility given that the GTN is now adding some features beyond the essential GNS ones. |
||
Vince
|
||
SeanMollet
Newbie Joined: 05 Aug 2019 Location: OverlandPark,KS Status: Offline Points: 25 |
Post Options
Thanks(0)
|
|
Yes! Gfc600 as well, since I’m not eligible for the 500. Too many of those spinny things on my plane.
|
||
Bweb99
Newbie Joined: 05 Jun 2019 Location: Pittsburgh, PA Status: Offline Points: 19 |
Post Options
Thanks(0)
|
|
VNAV Labels compatibility with GFC500
|
||
brou0040
Senior Member Joined: 13 Dec 2012 Location: KIYK Status: Offline Points: 720 |
Post Options
Thanks(1)
|
|
Interesting, sounds like something we have to accept in this case. Thanks for looking into this!
|
||
AviSteve
Admin Group Joined: 12 Feb 2018 Location: Melbourne, FL Status: Offline Points: 2139 |
Post Options
Thanks(0)
|
|
Turns out it's an idiosyncrasy of database coding. One of the coding rules that Jeppesen follows is that when a course reversal hold (HF leg) has a window constraint, only the lower altitude is coded. That one surprised me as well. Perfect example of why it's always good to compare the FMS to the chart...
|
||
Steve Lindsley
Avidyne Engineering |
||
AviSteve
Admin Group Joined: 12 Feb 2018 Location: Melbourne, FL Status: Offline Points: 2139 |
Post Options
Thanks(0)
|
|
It's driven by the database. I looked at the chart and see the window on the hold at CADAB, but the database definitely shows at or above 3900. I'll shoot Jeppesen an email to see if it's a mistake or if it's being driven by some oddball coding rule. Standby...
|
||
Steve Lindsley
Avidyne Engineering |
||
brou0040
Senior Member Joined: 13 Dec 2012 Location: KIYK Status: Offline Points: 720 |
Post Options
Thanks(0)
|
|
Thanks AviSteve, I guess my follow-on question is what drives some window constraints being populated while others aren't? Is that just coming from Jepp? I see JUUSE on the LAX arrival you mentioned say between 8000 and 9000 feet - exactly how I'd expect it, but CADAB for the RNAV 29 at KSBP is not windowed in the IFD, but the plate shows between 3900 and 6000.
|
||
AviSteve
Admin Group Joined: 12 Feb 2018 Location: Melbourne, FL Status: Offline Points: 2139 |
Post Options
Thanks(0)
|
|
Window constraints are already supported. They will be displayed, but cannot be edited. See KLAX RYDRR2 arrival for an example.
|
||
Steve Lindsley
Avidyne Engineering |
||
chflyer
Senior Member Joined: 24 Jan 2013 Location: LSZK Status: Offline Points: 1022 |
Post Options
Thanks(0)
|
|
I have both 540 and 440, and I keep the 440 open on the aux fuel mgmt page. The 440 remembers that on shutdown and always comes up with that page now by default on startup. Might work for the GPS status page too ??
|
||
Vince
|
||
ansond
Senior Member Joined: 12 Nov 2009 Location: Austin, Texas Status: Offline Points: 145 |
Post Options
Thanks(0)
|
|
Another option for 10.3 would be to make the default aux page point to the GPS status page whilst in flight (on ground it could remain pointing to the DB status page)... occasionally, I like double checking my signaling and resolution values and its a pita to have to click over into that page. While I've never had an actual GPS issue, if I did.. I'd want that page to be easily placed for simple recall and checking...
Doug N208LG
|
||
brou0040
Senior Member Joined: 13 Dec 2012 Location: KIYK Status: Offline Points: 720 |
Post Options
Thanks(0)
|
|
I get that each person's ideal NAV tab would be different, but I think the follow-up request to allow a tab of dedicated datablocks is a good feature request, particularly for 440 owners, and allow each user to modify that tab to their preferences. Now if Avidyne were to create an additional datablocks that would replicate an HSI, which might need to be bigger and only fit on that dedicated page (there are already restrictions on which boxes go where based on size), that would also address the earlier feature request.
|
||
brou0040
Senior Member Joined: 13 Dec 2012 Location: KIYK Status: Offline Points: 720 |
Post Options
Thanks(0)
|
|
Feature Request: Between altitude constraint It looks like there is enough real estate on the line when not in "edit" mode, but it's full when selecting the field to edit. I get needing the "before" text since you want the clarity if someone enters a distance other than 0 in the cross field, but it is preventing you from displaying published data even when crossing over and not before the fix. How about not displaying "before" in the edit screen unless someone enters something other than 0. Then, if you need the space in the off chance that someone is doing "before" and "between", let that line scroll off the screen when editing so you have to swipe left/right to get to the fields if you need them. I think there is enough room for it all show up properly once not editing the fields and if you need a little more room, move that entire line left a little to take up all the real estate.
Edited by brou0040 - 05 Jul 2020 at 11:32am |
||
n7ifr
Senior Member Joined: 05 Aug 2013 Location: Scottsdale, Az Status: Offline Points: 470 |
Post Options
Thanks(0)
|
|
[/QUOTE]
I've never tried such a complicated scheme, but here's my postulation... Remote mode just means that the IFD is a node on a different network. You're proposing to have #2 IFD in local mode, thus establishing the network, and having #1 IFD and the IFD100 both connected to that network. Normal cross-syncing should work between both IFDs and IFD100. But, ADS-B in data is not transferred between real IFDs using WiFi. The IFD100 will still just get the ADS-B data from the sensor wired to the IFD to which the IFD100 is connected. Of course, you can just try it. If you do that, report back what you find. I suggest you start a new thread for it, though. Thanks Steve (& Henry on followup ) - Yes a bit overly complicated way to allow the IFD100 to switch between panel IFD's. Not sure of the value, except to experiment to see if by chance: . the two ADSB-types (1090 & 980) might be combined on the IFD100 display . the panel IFD's hard wired data-blocks like Fuel & Frequency info could be accessed... Can't wait for my annual to be done to experiment. Tom W.
|
||
HenryM
Senior Member Joined: 13 Oct 2017 Location: Texas Status: Offline Points: 486 |
Post Options
Thanks(0)
|
|
Then a new feature for the IFD100 would be to allow changing the chassis ID from the app itself, rather than having to go into the settings of the iPad to it.
I understand the IFD100 to really be an additional screen/remote terminal for whatever IFD is is connected to, so it can only work with one device at a time. The chassis ID tells it what device it is connected to. It would be nice to have an easy way to switch between devices from within the app. I guess you'd have to tell it both chassis ID and device type.
Edited by HenryM - 07 Jun 2020 at 8:56am |
||
AviSteve
Admin Group Joined: 12 Feb 2018 Location: Melbourne, FL Status: Offline Points: 2139 |
Post Options
Thanks(0)
|
|
I've never tried such a complicated scheme, but here's my postulation... Remote mode just means that the IFD is a node on a different network. You're proposing to have #2 IFD in local mode, thus establishing the network, and having #1 IFD and the IFD100 both connected to that network. Normal cross-syncing should work between both IFDs and IFD100. But, ADS-B in data is not transferred between real IFDs using WiFi. The IFD100 will still just get the ADS-B data from the sensor wired to the IFD to which the IFD100 is connected. Of course, you can just try it. If you do that, report back what you find. I suggest you start a new thread for it, though. |
||
Steve Lindsley
Avidyne Engineering |
||
Bob H
Senior Member Joined: 26 Jan 2018 Location: NH - KMHT Status: Offline Points: 290 |
Post Options
Thanks(0)
|
|
|
||
Bob
|
||
R0bst3r
Groupie Joined: 27 Jun 2019 Location: Va Status: Offline Points: 44 |
Post Options
Thanks(0)
|
|
I’m aware of the data blocks and zoom mode, but with zoom turned on you can’t get much data on the screen of the 440 and it’s jammed up against a map I really don’t need. So I’m proposing on this screen you could dump the map entirely and have just datablocks.
|
||
n7ifr
Senior Member Joined: 05 Aug 2013 Location: Scottsdale, Az Status: Offline Points: 470 |
Post Options
Thanks(0)
|
|
David - Yes, very interesting ways to maximize traffic display... Recall, the last time you flew with me I could not figure out why my IFD100 was displaying ONLY TAS Trfc-icons. Turns out I had my IFD#1 set to display the Ryan TCAD TAS Trfc. Since then I have both my IFD540's displaying UAT ADSB 980 traffic. Now I understand much better some of the subtleties. When my plane is out of annual in a couple of weeks, I will reconfigure my #1 IFD540: . IFD540-#1 (and Aspens) to display TAS-A . IFD540-#2 to display 980 UAT from Skytrax100 . Transponder set 980 = Yes, 1090 = No so all ADS-R is received by Skytrax100 . iPad (IFD100, FF, & FlyQ) set to display from IFD#2 - all Trfc in UAT format. That way, I can fairly easily switch the iPad between IFD#1 <--> IFD#2 to see how the Apps display Trfc. Ideas? Tom W.
|
||
dmtidler
Senior Member Joined: 12 Feb 2016 Location: USA Status: Offline Points: 616 |
Post Options
Thanks(0)
|
|
I believe Zoom Mode was introduced with IFD software version 10.2.3.1. It is second in the list of options at AUX - SETUP - User Options and described in the latest version of the IFD PG. Zoom Mode is also available on the IFD100.
|
||
oskrypuch
Senior Member Joined: 09 Nov 2012 Location: CYFD Status: Offline Points: 3057 |
Post Options
Thanks(0)
|
|
+1 on BobH's suggestion. Zoom mode? Did I miss a new feature? * Orest
Edited by oskrypuch - 05 Jun 2020 at 1:34pm |
||
dmtidler
Senior Member Joined: 12 Feb 2016 Location: USA Status: Offline Points: 616 |
Post Options
Thanks(0)
|
|
Additionally, the Zoom Mode user option can be used to increase the font size of the datablocks, LSKs, and page tabs. With Zoom Mode, you will not be able to have as many datablocks chosen for display as without Zoom Mode.
|
||
chflyer
Senior Member Joined: 24 Jan 2013 Location: LSZK Status: Offline Points: 1022 |
Post Options
Thanks(0)
|
|
I agree with Bob.
My suggestion to you R0bst3r, is to take the "default nav" information that you want to see and set up your datablocks to show that information where you want it, on a permanent basis.
|
||
Vince
|
||
Bob H
Senior Member Joined: 26 Jan 2018 Location: NH - KMHT Status: Offline Points: 290 |
Post Options
Thanks(1)
|
|
Everything on that Garmin screen is available through customized datablocks on the IFD. There is no need to create a dedicated screen for info that is already available elsewhere. If you are new to the IFD, then give it more time before wanting to revert to what you were familiar with on another navigator. Avidyne's IFD did not become the best GA navigator on the market by copying G or porting over their screens. What's important is that the info is there and it's customizable no less. There have been plenty of suggestions here about doing things the way Garmin did, not because it is better, but because that is what folks were familiar with and their "muscle memory" got in the way. That is not how innovative products get created. If I wanted Garmin, I would have bought Garmin.
|
||
Bob
|
||
R0bst3r
Groupie Joined: 27 Jun 2019 Location: Va Status: Offline Points: 44 |
Post Options
Thanks(0)
|
|
On the IFD-440 would like to see another tab under the map button beside map and svs called default nav. The page would be like the default nav page on the 430/Gtn 650. For me this would be great because I have the IFD100 app running on a second ipad on the map page most of the time, and having the screen of the 440 display course information in large easy to read numbers along with a CDI would be quite handy. This also seems like pilots transitioning from 430's would appreciate this feature as a vast majority that I know seem to use this page quite a bit. |
||
ddgates
Senior Member Joined: 12 Aug 2011 Location: Deer Valley Status: Offline Points: 1100 |
Post Options
Thanks(0)
|
|
We are thinking the same way, Tom. I don't see any real downside if we use discrete SSIDs. May want to use different WiFI channels, and understand there is a way to specify that.
When we started this, there were some communications opportunities. We were told in the past that the only TRFC which would be ported out was ADS-B/Capstone, but the doctrine now is that TAS traffic also ports out. It is interesting to think about that - recall that the TAS unit is sending all the info to do ATAS symbology - but the IFD can't "decrypt" it...can it be set up some way such that FF or FQ can get the TAS data and do full display? I would set up on box on LIO_WiFI and another as a STRATUX AP, seems like opportunities to maximize usefulness.... |
||
David Gates
|
||
n7ifr
Senior Member Joined: 05 Aug 2013 Location: Scottsdale, Az Status: Offline Points: 470 |
Post Options
Thanks(0)
|
|
David - Still a great question, unanswered so far.
So, maybe use IFD#1-WiFi set to "Remote" and IFD#2 WiFi might stream BOTH IFD's WiFi-Streams. This might allow the IFD100 to receive some combo of both of the dual IFD's, allowing for example: . Data-blocks from either IFD540, like Fuel (hard wired to say #2) + Veritas TAS Traffic (hard wired to #1 IFD) and ?? UAT ADSB traffic from #2 IFD540. Maybe Steve will chime in on this one. Tom W.
Edited by n7ifr - 04 Jun 2020 at 7:32pm |
||
Post Reply | Page <1234 9> |
Tweet
|
Forum Jump | Forum Permissions You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |