MLB100 Traffic
Printed From: Avidyne
Category: Avidyne General
Forum Name: SkyTrax Series ADS-B Receivers & Transceivers
Forum Description: Topics on the Avidyne SkyTrax 978 MHz Receivers & Transceivers
URL: http://forums.avidyne.com/forum_posts.asp?TID=846
Printed Date: 23 Nov 2024 at 11:35pm
Software Version: Web Wiz Forums 12.01 - http://www.webwizforums.com
Topic: MLB100 Traffic
Posted By: roltman
Subject: MLB100 Traffic
Date Posted: 16 Oct 2015 at 9:52am
|
Took a 3200nm flight this last week with the MLB100 and traffic turned on. I only saw one target the entire trip (numerous traffic calls by ATC though) with the traffic set to "unrestricted". I'm going to talk to my shop, but I was at 15,000 over Kansas City class B yesterday where I saw the one target and it was shown at my altitude at less than 1nm. I asked ATC and the only traffic there was a airliner on approach at ~3000' or ~12,000' below me. Not 100% sure how the altitude is determined for display. I know the IFDs have proper altitude from the encoder and my AXP340 does too. It has ADS-B out turned on and FAA report came back with a "gold star". The MLB100 was supposed to use the "parroted"AXP340 pressure altitude values. Also sporadically I would get a "Traffic Sensor Fault" message on the IFD540 about every say hour or two and they'd last only a few seconds. I assume it was just a issue with a ground station? I also noted that the traffic data tab looked normal under this fault state until a brief flicker to a "Red X" when unit returned to normal ops. Wondering if it shouldn't be a "Red X" the entire time the IFD540 has a yellow traffic sensor fault? |
Replies:
Posted By: tony
Date Posted: 16 Oct 2015 at 10:03am
| On my airplane when my shop installed my 340, they asked me what frequency my ADSB in was going to be. I told them I was 978. They had to submit some paper work telling the FAA that I need the 1090 rebroadcasted. I have no idea what that paperwork was, but I remember the discussion. |
Posted By: roltman
Date Posted: 16 Oct 2015 at 11:35am
That's a setting on the 340 to broadcast what "In" you have. I have it setup correctly and it was confirmed by the FAA. Spoke with my shop this morning, apparently there's some known ARINC issues and how power's applied. I'll let Avidyne elaborate as I'd be repeating 3rd hand info. The shop also had some questions about how the MLB100 is programmed as they've done a couple now it and it shows traffic correctly with their ground test equipment which throws out some false targets, but I'm not seeing any traffic in flight. |
tony wrote:Posted By: DavidBunin
Date Posted: 16 Oct 2015 at 12:50pm
|
Does your shop have experience with NavWorx installations? In other words they have "done a couple" of NavWorx installations or Avidyne installations? I know that the NavWorx field programming software has that function (traffic simulation mode). I also know that if they used the NavWorx software to program your unit, it will interfere with the Avidyne interface in some way, but I do not know the detail of that interference. The Avidyne units are programmed at the factory. (I don't think there is a field software for them, so what equipment is your shop using to simulate traffic?) A shop that is used to doing NavWorx installations might accidentally de-program an MLB unit if they don't read the Avidyne instructions carefully. David Bunin |
Posted By: roltman
Date Posted: 16 Oct 2015 at 1:39pm
Both. I know they were familiar with the NavWorx and it's console, but they knew not to mess with the Avidyne using the console. The shop purchased some external piece of ADS-B equipment that can transmit UAT/1090 targets and that's what they've used, so they know it kinda works with those targets, but they were concerned there was some piece of programming they were missing (i.e. aircraft ID or hex code, etc.) for it to function correctly. I was just told today the IFDs and the MLB's can't be powered up simultaneously due to some issue with the A429 bus or A735B data. Like the MLB100 falsely putting out incorrect SSMs on the labels and never working correctly after that point (this is my assumption based on the info provided). I'll let Avidyne comment since it is a known issue to them and I'm just putting together 3rd hand info I was told today. |
Posted By: DavidBunin
Date Posted: 16 Oct 2015 at 1:43pm
|
That doesn't sound right to me. They power up together and work just fine in my airplane. David Bunin |
Posted By: roltman
Date Posted: 16 Oct 2015 at 2:09pm
Well I got a notice today from my shop not to b/c of some known software issue which they expect to fix shortly. Again waiting for Avidyne to speak up here. |
Posted By: TogaDriver
Date Posted: 17 Oct 2015 at 2:24pm
|
Another data point: we just installed an MLB100 and, though the traffic test shows good, we are getting zero traffic. The stratus shows lots. We do get weather. Jake or Simpson, could you please help tech support to provide consistent guidance for this problem and let us know what to have our shops do? Thanks. |
Posted By: edanford
Date Posted: 17 Oct 2015 at 3:05pm
|
I just confirmed the same issue with my MLB100 install.. Passes all tests but no traffic displayed. All ifd540 configuration ports look to be set up properly I assume there is missing wiring on install Ed ------------- Ed |
Posted By: MysticCobra
Date Posted: 18 Oct 2015 at 12:21am
That was my experience yesterday on a 2.5 hr flight through a couple of Class B and Cs (was comparing against iFlyGPS / SkyGuardTWX portable setup). At least, that was my experience before the IFD annunciated "traffic sensor fault", there was a *zzzzt*, the smell of electrical smoke, a popped cb, and a dead IFD540. Sigh... At least I had the novelty of an escort of fire trucks from the runway to the FBO!
|
Posted By: TogaDriver
Date Posted: 18 Oct 2015 at 5:02pm
|
I also got a brief Traffic Sensor Fault but no pops or bad smells and my IFDs are still operating. |
Posted By: TogaDriver
Date Posted: 19 Oct 2015 at 7:13pm
|
My shop and I just re-checked all connections and configurations and now believe we have some answers: 1) The MLB100 comes from Avidyne pre-configured with the correct settings. If Avidyne tech-support has your shop Erase EPROM on the MLB100 using the PC configuration console, which they did for mine, your settings will now BE WRONG. and the key setting to get right is on the Initialization->Inputs/GPS Source. This must be set back to MLB100 Aviation Format. 2) The MLB100 needs a GPS input from an IFD 232 serial line, my shop attached the MLB to port 2 but configured port 1 to aviation out. Shop caught the error after confirming the wiring was good, but here comes the fun part: On the IFD(540) if you have both 232 serial ports set to Aviation OUT, port 2 will NOT send out data. It just pegs the output to -5.5 volts. Once he set port 1's 232 serial output to OFF the GPS data on port 2 started flowing. Also, once this was corrected, the MLB100 console saw the lat/long info and let us turn on simulated traffic which showed up on the IFD screens. So, if the MLB does not get valid GPS input, you won't get traffic - real or simulated. AVI-folks: this silent port failure is a bug in the IFD serial software and should be logged if you don't have it so already. Also, you should make sure the MLB100 installation docs call out this behavior to save others time and $. We did not take the time to suss out exactly what combination of port settings disables other ports but I suggest you do this exercise. If only one port can support an output format, the other port output values should change or alert on that settings page as a result. For the record: I have a foot in the EXP world as well and recently installed an ADS600EXP in a friend's RV-12. I'm very well acquainted with NavWorx' products (the MLB100 is an OEM product of theirs) and confirmed the console info directly with NavWorx as we debugged the issue. I hope this provides some help to others with similar issues. My shop communicated the results directly to tech support at Avi so they should be able to recognize this problem in the future and help others who call in. Tomorrow I plan to go fly it and find some REAL traffic, but not too close... :-) |
Posted By: edanford
Date Posted: 19 Oct 2015 at 8:05pm
|
------------- Ed |
Posted By: edanford
Date Posted: 19 Oct 2015 at 8:10pm
|
Two ports not supporting Aviation out sounds like a bug that might be fixable in SW. It would explain my lack of traffic as I have two ports set to RS-232 Aviation out. I would be willing to wait if a SW fix is possible rather than open my panel up again. Simple experiment of turning off the first aviation out RS-232 port will be my next flight experiment Great update. Thanks ------------- Ed |
Posted By: TogaDriver
Date Posted: 19 Oct 2015 at 8:54pm
|
One other suggestion came out of our tech session but I can't remember the source: Assuming the MLB100 has a discrete breaker (it should): Pull this before you start up the IFDs and let them acquire GPS lock. Then turn on the MLB with the breaker. I'm going to try it without this step first and will report my findings. |
Posted By: DavidBunin
Date Posted: 21 Oct 2015 at 8:33am
|
Evolution of ports: Brand-G only allows a data type to be output on a single port. In other words, if port #1 is "Aviation" then port #4 can't also be "Aviation" Avidyne comes out an allows multiple ports to be set to the same data type (I could have "Aviation" on all six ports) but only the first instance actually pumps out data. We have been told that this will be corrected in the "next" software, which in my mind means version 10.2 (not 10.1.1.0). At that time we will be able to have duplicate data outputs. Looking forward to that day. |
Posted By: DavidBunin
Date Posted: 21 Oct 2015 at 9:04am
|
TogaDriver, I learned a little more about the "powering up together" problem last night. Here is what happens: The IFD outputs a test set of coordinates during the power-up self test (what I call the "lawyer screen" when the CDI is active, before you press ENTR for the first time). If you pause there for any length of time, the MLB100 finishes its internal power up sequence, and can process these coordinates from the IFD as real. Then you press ENTR and the Lat/Long data flags. The MLB holds on to the last data it had. At some point, the IFD comes up in a navigating mode and starts outputing your real/actual coordinates. The MLB sees the airplane jump instantly to a location that is hundreds, if not thousands, of miles from where it "knows" it just was, and it ignores that as bad data. So yes, the immediate work-around is to pull the MLB100 circuit breaker and don't power it up until after you're in a normal working mode on the IFD. (Or use the breaker to cycle MLB power after the IFD is up and running.) I think that if you are quick enough on the ENTR button, that you might get the IFD past the test coordinates before the MLB is listening for them, but I don't have a good way to test that theory. My airplane is down for maintenance. If you want to try it, please let us know how it goes. NavWorx is already working on a software update to fix it. (I happened to be there when they duplicated the problem on the bench.) David |
Posted By: roltman
Date Posted: 21 Oct 2015 at 9:39am
TogaDriver, any luck? I have two 550nm legs planned this weekend and would like to help narrow down this problem if at all possible. I was told the power up trick after GPS lock (haven't tried it yet), and the Aviation Out port maybe probably an issue too. However, I have seen ONE traffic target while in flight, and it made absolutely no sense. I tracked it across Kansas from 50nm to the north of my position, and when over KC it was at 7 o'clock < 1nm at my altitude which was at 15,000. ATC had no return, so maybe using David's comment maybe my box thought it was in wrong area of the world? Since I know I'm getting ADS-B Wx in on my #2 unit maybe as David mentioned it's not sending out proper Aviation Out on that port. I don't care if I lose ADS-B Wx since I have a MLB700 on #1 that'll cross feed if ADS-B Wx is turned off on #2. |
Posted By: TogaDriver
Date Posted: 21 Oct 2015 at 10:20am
|
The Toga didn't get tested yesterday. I will try to fly it today but we're pretty sure that disabling one of the aviation out ports will do the trick based on what we saw coming out of port 2 on the scope and the fact that simulated traffic started working immediately after we made that change. And Weather uses a serial in port. Traffic uses a 429 in port. The in and out ports can be set independently so, other possible bugs aside, turning of one aviation out should not affect that. But I do not have an MLB700 so I can't say for sure. Still waiting for Avidyne to respond here. Even a "we will review your report and determine if there is a bug in the IFD serial output code" would be nice. In the meantime, it's back to beta-testing... EDIT: David, I missed your note on the behavior of IFD out ports. I did remember the G limitations when we discovered the issue with IFDs. If this is a known issue, it should be mentioned in the installation docs for the MLB. If nothing else, it will save $ getting billed to Avi for wasted time. ;-) |
Posted By: roltman
Date Posted: 21 Oct 2015 at 11:07am
Thanks. Look forward to a report. As for the ports you are correct; however, I believe the Aviation Out on the serial port is used to tell the MLB100 where you are for the A429 IN traffic data. David, in another thread, mentioned that with MLB100 Wx In forces that same port number to be MLB100 Wx Out in 10.1.0.0 which is not "Aviation Out". Its the thread where AviJake listed the 4 things need for traffic to work in 10.1.0.0 with the MLB100. This was why I was wondering if turning off the MLB100 Wx In and setting that output port to Aviation Out may then fix the traffic issue for me. I honestly haven't been to the plane since my 1600nm trip this last weekend, but will head out there tonight to at least record all my I/O settings. |
Posted By: DavidBunin
Date Posted: 21 Oct 2015 at 4:34pm
|
It may, as long as you don't also have some other port already configured to be "Aviation" data. I didn't think to see if the data appears on the first port that is set to Aviation data (i.e. the first one chronologically when settings are made/saved) or if it's the first port in the list (i.e. port #1) that continues to pump out the "Aviation" data when multiple ports are set for it. It stands to reason (in my mind at least) that either traffic or weather information needs to have some kind of position data in order to display on the right part of the screen. So the fact that MLB100 traffic arrives via ARINC 429 wiring and weather via RS-232 wiring really makes no difference. Looking at the data port selections, and applying a little of my own critical thinking, I would guess that ADS-B Out requires a level of positional/timing precision that is not available in the Aviation dataflow. I see in the manual that "ADS-B (Avi)" is the data used for the AXP340. My guess is that the "ADS-B (Avi)" output is also going to be needed once the MLX200 product comes online. David Bunin |
Posted By: jwjenks
Date Posted: 23 Oct 2015 at 10:32pm
|
Just flew home from my MLB100 installation, and went through the Phila Class B with two heavies in front of me. I'm at 2500' and they were at 4000', both less than 12 miles in front. No traffic displayed on the IFD540. Plus my AXP340 was not broadcasting Mode C pressure Alt. I know I can fix that by disabling the link between IFD and the AXP in configuration table, but didn't feel like turning off the IFD. Yeah they weren't too happy I wasn't broadcasting alt. Yuck!! ------------- JWJ |
Posted By: TogaDriver
Date Posted: 24 Oct 2015 at 4:33pm
|
After flying with only one Aviation out on RS232 port 2, we saw both traffic and weather. There should be no conflict with getting Traffic on 429 and Weather on an RS232 in port. The issue is getting the IFD to output the GPS location to the MLB100 on an RS232 port. We DID, however, see our own ship ghosting us on traffic the whole time. With the old TIS-A that would happen occasionally but it happened the whole flight. One ground I confirmed that both transponder and MLB100 were correctly set to my N number and ICAO number on both devices. My shop said that sometimes that happens with the FAA messing around with their data fusion but I have yet to fly again to see if the problem "goes away". If anyone else has had the own-ship ghost problem with MLB100 please let me if you did something to make it go away. Thanks! Neil
|
Posted By: roltman
Date Posted: 26 Oct 2015 at 10:21am
|
Neil, Do you mind sharing your RS232 configuration. I tried the power cycle this weekend and it did nothing for me. I didn't change my settings since I need to touch base with my shop on what's connected to port #6 on my #2 IFD. IIRC, I had: MLB100 Wx In/Out on port #2 Crossfeed In/Out on port #3 Aviation out on port #6 <-- not sure where this is going |
Posted By: AviSimpson
Date Posted: 26 Oct 2015 at 12:00pm
Tech Support advised me that you should talk to a dealer since they have access to the MLB100 UAT Console and can troubleshoot this issue. ------------- Simpson Bennett Avidyne Corporation Product Manager |
Posted By: Risky52
Date Posted: 29 Oct 2015 at 2:50pm
|
I have been reading alot about how the MLB 100 should be and has been connected, has anyone been airborne and seen any traffic on the IFD? ------------- Wayne T. |
Posted By: roltman
Date Posted: 29 Oct 2015 at 8:23pm
|
Yes. Today I did out to about 30nm. That said I got traffic working after restarting the mlb100 in flight near Philly. Maybe I'm not waiting long enough on ground to delay the turning on the box. Anyway, for next 10-15min, my plane was shown while around Philly, around Dover AFB, that disappeared. I then got a traffic call from ATC @12 o'clock 10nm. It wasn't there on the mlb, but there was one at 6 o'clock. It turned out at that point it was Showing traffic off the nose on my tail. When I made a 30deg turn on an airway the all traffic rotated to stay relative to my nose which is obviously wrong Then near PaxRiver I had a target at my 3, asked ATC and was told that traffic was at my 7. So right now I have altitudes and distances seem correctr, but positions in the thumbnail and map are not correct. |
Posted By: edanford
Date Posted: 29 Oct 2015 at 9:00pm
|
Interesting note on direction issue on thumbnail. I got my MLB100 / IFD540 wiring issues fixed on Tuesday and noticed the same direction issue on thumbnail during flight home from shop Altitude / distance matched my stratus 2 ipad info but the direction was off on thumbnail I had planned to do more tests before I asked about it but your description matched mine exactly ------------- Ed |
Posted By: DavidBunin
Date Posted: 30 Oct 2015 at 8:31am
|
I've been telling pilots to cycle the MLB power after the GPS indication (top right of the IFD screen) turns green. That seems to be working well. I have heard of "quadrant errors" and/or "mirror errors" on other ADS-B systems, but not on the Avidyne products (until now). I think G-brand had an issue for a while with their portable devices. I have not experienced this problem on my airplane. David Bunin |
Posted By: roltman
Date Posted: 30 Oct 2015 at 8:37am
|
I actually thought about what I saw more last night, and I don't think the algorithm that is painting the traffic for the MLB100 (either in that box or the IFD) is using ground track or heading information, instead it assumes the heading or groundtrack to be North at all times. For the traffic I visually saw opposite direction on the same airway 1,000 feet below, it was shown on the IFD at my 6 o'clock position moving to the 12 o'clock position. In other words it was backwards. Well I was on a ~180 heading on that airway (V29 near ENO). Then when I turned from 180 to 226 to V16 over ENO the traffic panned across the map during the turn. Finally near PTX heading 226, I saw traffic on the IFD at 3 o'clock at 10nm. PTX approach said it was military at my 7 o'clock 10nm. Well remove 226deg from 90deg and you'll end up with roughly a 7 o'clock position. So I think the position relative to the nose is correct assuming the aircraft is on a 0deg heading at all times. So if you always fly north I think the traffic position will be displayed correctly otherwise it is wrong. I did try all the various map views on the IFD yesterday and the traffic always stayed relative to the planes nose (i.e. made no difference on traffic display). Finally I have heading information going to my IFD (via HSI Synchro) and normally use the heading up mode. Avidyne or David you have any ideas on this one? |
Posted By: DavidBunin
Date Posted: 30 Oct 2015 at 9:09am
|
That's an interesting theory. One I haven't heard before. I suppose a little for flight data and experimentation would reliably prove (or disprove) its veracity. I will ask some people I know, and see what they say. Again, the issue has not presented itself in my airplane, so I can neither confirm nor dispute the theory. (And I'm down for maintenance right now anyway, so more flight experience is not available to me). David Bunin |
Posted By: roltman
Date Posted: 30 Oct 2015 at 9:39am
|
No problem. Just so everyone can visualize it I put this diagram together. For my N/S case where it's pretty simple to visual, it doesn't answer off-axis uncertainties. The Pax River case does answer all off axis uncertainities. For the Pax River case: Red is what I saw on the IFD map (3 o'clock). Green is what was reported by ATC (7 o'clock) and the true aircraft position. If you then visualize the plane flying north instead of along the airway, the 3 o'clock position would have been correct position relative to the aircraft nose.  |
Posted By: mgrimes
Date Posted: 30 Oct 2015 at 10:33am
I can confirm I am having the exact same issue with our MLB100. Traffic position remains static on the display regardless of which direction the plane is heading. (i.e. always thinks it's on a 360 heading). You can confirm this on the ground by taxiing and turning the plane 360 degrees and noting that the displayed traffic never moves. My avionics shop is in communication with Avidyne and my understanding is that they are diligently working on it. We also have Skywatch on our MFD so we can compare the true aircraft position with an independent traffic source to confirm this is an issue.
|
Posted By: roltman
Date Posted: 30 Oct 2015 at 10:42am
|
Just got a report from my avionics shop this is a known issue to Avidyne. They are working on new software and a SIL will be issued shortly. I was advised to turn traffic off. So my question is it an IFD issue or MLB issue? In other words will the delayed 10.1.1.0 have the fix or some other later fix needed 10.1.2.0? Is there a work around (i.e. take IFD out of heading mode and put it in track mode)? |
Posted By: edanford
Date Posted: 30 Oct 2015 at 2:12pm
|
Thanks Roltman I suspected that something like that was going on Only way it would work would be to fly north always I think IFD540 map mode will not help. I saw the issue in north up map mode ------------- Ed |
Posted By: DavidBunin
Date Posted: 30 Oct 2015 at 2:52pm
|
My sources also confirm that your hunch was correct. This is a recently identified issue, and a software that addresses it has been written, and is in testing now. It is a minor software change in the MLB, so it should have no affect on 10.1.1.0. David Bunin |
Posted By: edanford
Date Posted: 17 Nov 2015 at 1:36pm
|
I heard that there is an upgrade from 4.0.8 (4.0.8.1?) for MLB100 What does it do and when will it be posted? My shop says " any day" for this to be posted for dealers Ed ------------- Ed |
Posted By: DavidBunin
Date Posted: 17 Nov 2015 at 6:57pm
|
In the world of avionics, there is always a next software version. But as far as I know, 4.0.8 is the newest one available today. The next logical number would be 4.0.9 but there aren't even rumors yet (except wherever you heard it). Like any software, there are probably bugs in 4.0.8 but I haven't heard of any yet. David Bunin |
Posted By: ddgates
Date Posted: 18 Nov 2015 at 6:14am
|
David: I had an MLB installed a few months ago. Hooked up weather, but not traffic. My traffic comes from my TAS which I hope will get the -A upgrade during my flying career I assume 4.0.8 is an update. Does 4.0.8 update traffic only or are there other changes, i.e., should I have updating done on my box? Thanks DMG ------------- David Gates |
Posted By: edanford
Date Posted: 18 Nov 2015 at 1:55pm
|
I have got word from tech support that there are some fixes for 4.0.8 that will be posted soon. As a result I will wait a couple of more weeks to fly over to have my MLB100 SW updated. Hope 10.1.1.0 will be out by then too. Just a FYI to anyone out there that has to travel to shop to get this update done. ------------- Ed |
Posted By: DavidBunin
Date Posted: 24 Nov 2015 at 5:34pm
|
David, If you're happy with the performance of your unit as-is, there is no benefit to loading the new software. I only did it because NavWorx asked me to. There aren't any new functions or features in 4.0.8 as far as I know. David |
Posted By: n7ifr
Date Posted: 14 Mar 2016 at 12:24pm
|
David (Bunin): I noticed you updated your MLB and 540 software (4.09 & 10.1.2)... Where can the 10.1.2 be found for download? What - if any - improvements or fixes were in these updates? Thanks. Tom Wolf
|
Posted By: DavidBunin
Date Posted: 14 Mar 2016 at 12:54pm
|
The 10.1.2.0 software for the IFD is on the "Dealers" side of the Avidyne web site. (I found it in the same place that they had put 10.1.1.0.) There were some minor bug fixes that improve the traffic and weather displays, but I don't have a specific list of what changed. I think one of the changes was to the way that the national Naxrad is displayed, but I didn't have a chance to go flying and test it out. Bear in mind that while loading a new navigation database is a pilot action, loading a new operating software is not. Technically this is an appliance alteration, and this action requires a log entry signed by at least an Airframe Mechanic (A&P) or Repair Station (avionics shop). If your mechanic is comfortable supervising your work, then that's between the two of you, but it still has to be his signature in the log entry. David Bunin |
Posted By: jwjenks
Date Posted: 16 Mar 2016 at 8:43am
|
Came home in the rain last week. ATC was good at pointing out the moderate rain but the IFD gave me a much better and wider picture to pick an easier route. ------------- JWJ |
Posted By: DavidBunin
Date Posted: 16 Mar 2016 at 10:49pm
| Hey, that sounds like success! |
Posted By: pitchristian
Date Posted: 18 Apr 2016 at 9:17am
|
Hey Everyone, First post as I am a new Avidyne stack owner. I brought the plane home from the shop a few weeks ago and it turns out my MLB100 and IFD540 combo is not showing traffic at all like others earlier in this thread. I tried the MLB power up after GPS lock with no success so I am pretty sure the shop somehow configured it improperly. My question is what is the latest on this? What directions should the shop follow to remedy the issue? I am taking it back wednesday for them to work on it. Thanks
|
Posted By: flybikeski
Date Posted: 18 Apr 2016 at 11:07am
That MLB thingy needs lots of information. Barometric altitude (possibly to compare with traffic also using baro alt), GPS position RS232 link, a weather RS232 link and a traffic ARINC 429 link. A very helpful thing for your shop to do is to use the UAT RS232 console on a computer to hook into the MLB and it will let you know if it is getting data and ready to go. This will also upload the new version if you haven't yet. Using the console you (they) can turn on a traffic simulator and that will check the IFD to make sure it is receiving the traffic.
|
Posted By: edanford
Date Posted: 19 Apr 2016 at 12:29pm
|
Make sure your ADSB out device is set to UAT in only. My AXP340 was set to 1090 in only and as a result the uplinked traffic data was not complete at all to my MLB100 Once my configuration was corrected on my AXP340 to transmit that my plane was UAT in only , all the traffic appeared on my IFD540. I have not seen that written anywhere but found it out by experience ------------- Ed |
Posted By: ddgates
Date Posted: 19 Apr 2016 at 10:17pm
|
Now that is interesting.
------------- David Gates |
Posted By: dubs
Date Posted: 26 Apr 2016 at 2:56pm
|
OK, after making some changes in the settings, and uploading the DCF file to the IFD440, my avionics shop finally has Traffic displaying on the IFD440 properly, and Wifi working. On my short flight home (10 mins), I confirmed that my iPad was connected to the IFD440 and was able to move a flight plan from the IFD to Foreflight. However, no Traffic, nor Weather, was displayed on Foreflight. Should the IFD440 be feeding Traffic and Weather from the MLB100 to Foreflight? ------------- Baron C55 Tulsa, OK |
Posted By: edanford
Date Posted: 26 Apr 2016 at 3:37pm
|
Not under 10.1.x SW ------------- Ed |
Posted By: AviJake
Date Posted: 26 Apr 2016 at 9:40pm
|
Right. That comes with Release 10.2.0.0. ------------- Steve Jacobson sjacobson@avidyne.com |
Posted By: paulr
Date Posted: 27 Apr 2016 at 10:08am
Not yet. I believe this is planned for the 10.2 software release.
(Edited to remove a bunch of HTML/JS garbage that got pasted in somehow.) " rel="nofollow -
|
Posted By: DavidBunin
Date Posted: 28 Apr 2016 at 4:08pm
| You said a mouthful, paulr! |
Posted By: paulr
Date Posted: 28 Apr 2016 at 4:10pm
Whoa. I wonder how that happened? Let me see if I can fix it...
|
Posted By: DavidBunin
Date Posted: 28 Apr 2016 at 4:20pm
| Your transmission is much clearer on this frequency! |