# Error on MLAT

**URL:** <https://discussions.flightaware.com/t/error-on-mlat/17462>\
**Category:** ADS-B Flight Tracking\
**Created:** [October 17, 2015, 4:16pm UTC](https://discussions.flightaware.com/t/error-on-mlat/17462 "2015-10-17T16:16:03Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![Foxinthehouse1](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/foxinthehouse1/32/114064_2.png) [@Foxinthehouse1](https://discussions.flightaware.com/u/Foxinthehouse1)\
**Post date:** [October 17, 2015, 4:16pm UTC](https://discussions.flightaware.com/t/error-on-mlat/17462/1 "2015-10-17T16:16:03Z")

</div>

So I started out with setting the -config to feed data to VRS and it worked. Then I saw a thread (Co-Op feeds) and followed the instructions there to feed them MLAT but his killed my local VRS feed so I tried to reset it back so I could see mine own MLAT.

Since then I have not been able to see results on my Default Dump1090 page, sporadic results on my VRS. I have tried every command I have found On the forums with no improvement.

And ever since this started the Log on the ADS-B page repeats this over and over mlat(3904): Beast-format results connection with localhost:30104: [Errno 111] Connection refused

What can I do to fix this. I have very very basic command lien skills but telling me to open up “name here” will not help I just don’t know how to do it. Gotta give me the complete set of instructions.

---

<div class="post-metadata">

**Author:** ![dschaper](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/dschaper/32/59633_2.png) [@dschaper](https://discussions.flightaware.com/u/dschaper)\
**Post date:** [October 17, 2015, 5:34pm UTC](https://discussions.flightaware.com/t/error-on-mlat/17462/2 "2015-10-17T17:34:29Z")

</div>

What version of dump1090 and piaware are you running?

```auto

dump1090 --help 
dump1090-mutability --help
piaware -v

```

---

<div class="post-metadata">

**Author:** ![Foxinthehouse1](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/foxinthehouse1/32/114064_2.png) [@Foxinthehouse1](https://discussions.flightaware.com/u/Foxinthehouse1)\
**Post date:** [October 17, 2015, 6:15pm UTC](https://discussions.flightaware.com/t/error-on-mlat/17462/3 "2015-10-17T18:15:48Z")

</div>

> [@dschaper](#):
>
> What version of dump1090 and piaware are you running?
> 
> ```auto
> 
> dump1090 --help 
> dump1090-mutability --help
> piaware -v
> 
> ```

Both are the most up to date ones as I tried upgrading both to resolve the issue to no avail.

---

<div class="post-metadata">

**Author:** ![elpipila](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/elpipila/32/111945_2.png) [@elpipila](https://discussions.flightaware.com/u/elpipila)\
**Post date:** [October 17, 2015, 6:37pm UTC](https://discussions.flightaware.com/t/error-on-mlat/17462/4 "2015-10-17T18:37:14Z")

</div>

> [@Foxinthehouse1](#):
>
> > [@dschaper](#):
> >
> > What version of dump1090 and piaware are you running?
> > 
> > ```auto
> > 
> > dump1090 --help 
> > dump1090-mutability --help
> > piaware -v
> > 
> > ```
> 
> Both are the most up to date ones as I tried upgrading both to resolve the issue to no avail.

If all else fails, wipe the card and do a clean reinstall.

---

<div class="post-metadata">

**Author:** ![Foxinthehouse1](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/foxinthehouse1/32/114064_2.png) [@Foxinthehouse1](https://discussions.flightaware.com/u/Foxinthehouse1)\
**Post date:** [October 17, 2015, 7:58pm UTC](https://discussions.flightaware.com/t/error-on-mlat/17462/5 "2015-10-17T19:58:55Z")

</div>

> [@elpipila](#):
>
> > [@Foxinthehouse1](#):
> >
> > > [@dschaper](#):
> > >
> > > What version of dump1090 and piaware are you running?
> > > 
> > > ```auto
> > > 
> > > dump1090 --help 
> > > dump1090-mutability --help
> > > piaware -v
> > > 
> > > ```
> 
> Both are the most up to date ones as I tried upgrading both to resolve the issue to no avail.
> 
> If all else fails, wipe the card and do a clean reinstall.

Yeeeaaa, thats is my worst case scenario fix.

---

<div class="post-metadata">

**Author:** ![dschaper](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/dschaper/32/59633_2.png) [@dschaper](https://discussions.flightaware.com/u/dschaper)\
**Post date:** [October 17, 2015, 9:15pm UTC](https://discussions.flightaware.com/t/error-on-mlat/17462/6 "2015-10-17T21:15:30Z")

</div>

> [@Foxinthehouse1](#):
>
> > [@dschaper](#):
> >
> > What version of dump1090 and piaware are you running?
> > 
> > ```auto
> > 
> > dump1090 --help 
> > dump1090-mutability --help
> > piaware -v
> > 
> > ```
> 
> Both are the most up to date ones as I tried upgrading both to resolve the issue to no avail.

Which version of dump1090? (mutability, flightaware?)

And what is the output of

```auto

sudo piaware-config -show

```

---

<div class="post-metadata">

**Author:** ![Foxinthehouse1](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/foxinthehouse1/32/114064_2.png) [@Foxinthehouse1](https://discussions.flightaware.com/u/Foxinthehouse1)\
**Post date:** [October 17, 2015, 9:31pm UTC](https://discussions.flightaware.com/t/error-on-mlat/17462/7 "2015-10-17T21:31:20Z")

</div>

> [@dschaper](#):
>
> > [@Foxinthehouse1](#):
> >
> > > [@dschaper](#):
> > >
> > > What version of dump1090 and piaware are you running?
> > > 
> > > ```auto
> > > 
> > > dump1090 --help 
> > > dump1090-mutability --help
> > > piaware -v
> > > 
> > > ```
> 
> Both are the most up to date ones as I tried upgrading both to resolve the issue to no avail.
> 
> Which version of dump1090? (mutability, flightaware?)
> 
> And what is the output of
> 
> ```auto
> 
> sudo piaware-config -show
> 
> ```

I’ll have to get that tonight. However I rebooted the Piaware about three hours ago via the internet interface on Flightaware and no longer getting errors on that log. I have to verify at home with port changes if it is forwarding malt to VRS or not.

Dump1090 is Flightaware 1.2-3 and piaware is 2.1-3

Config -show displays this,

Mlat 1

mlatResults 1

mlatResultsFormat {beast,connect,localhost:30104 basestation,listen,310003}

---

<div class="post-metadata">

**Author:** ![dschaper](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/dschaper/32/59633_2.png) [@dschaper](https://discussions.flightaware.com/u/dschaper)\
**Post date:** [October 17, 2015, 9:44pm UTC](https://discussions.flightaware.com/t/error-on-mlat/17462/8 "2015-10-17T21:44:10Z")

</div>

> [@Foxinthehouse1](#):
>
> > [@dschaper](#):
> >
> > Which version of dump1090? (mutability, flightaware?)
> > 
> > And what is the output of
> > 
> > ```auto
> > 
> > sudo piaware-config -show
> > 
> > ```
> 
> I’ll have to get that tonight. However I rebooted the Piaware about three hours ago via the internet interface on Flightaware and no longer getting errors on that log. I have to verify at home with port changes if it is forwarding malt to VRS or not.
> 
> Dump1090 is Flightaware 1.2-3 and piaware is 2.1-3
> 
> Config -show displays this,  
> Mlat 1  
> mlatResults 1  
> mlatResultsFormat {beast,connect,localhost:30104 basestation,listen,310003}

If your local VRS is set to port 310003 (I think you may have one too many 0’s) for MLAT then I think you should be set. If you wanted to try the Co-Op VRS in addition to local VRS, the command would be

```auto

sudo piaware-config -mlatResultsFormat "beast,connect,localhost:30104 beast,connect,feed.adsbexchange.com:30005 basestation,listen,310003"
sudo piaware-config -restart

```

If MLAT isn’t working with local VRS, try mgunther’s excellent tutorial: [http://discussions.flightaware.com/ads-b-flight-tracking-f21/vrs-show-both-dump1090-adsb-and-fa-mlat-positions-t36086.html](https://discussions.flightaware.com/t/vrs-show-both-dump1090-adsb-and-fa-mlat-positions/17399)

---

<div class="post-metadata">

**Author:** ![Foxinthehouse1](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/foxinthehouse1/32/114064_2.png) [@Foxinthehouse1](https://discussions.flightaware.com/u/Foxinthehouse1)\
**Post date:** [October 17, 2015, 10:10pm UTC](https://discussions.flightaware.com/t/error-on-mlat/17462/9 "2015-10-17T22:10:21Z")

</div>

> [@dschaper](#):
>
> > [@Foxinthehouse1](#):
> >
> > > [@dschaper](#):
> > >
> > > Which version of dump1090? (mutability, flightaware?)
> > > 
> > > And what is the output of
> > > 
> > > ```auto
> > > 
> > > sudo piaware-config -show
> > > 
> > > ```
> 
> I’ll have to get that tonight. However I rebooted the Piaware about three hours ago via the internet interface on Flightaware and no longer getting errors on that log. I have to verify at home with port changes if it is forwarding malt to VRS or not.
> 
> Dump1090 is Flightaware 1.2-3 and piaware is 2.1-3
> 
> Config -show displays this,  
> Mlat 1  
> mlatResults 1  
> mlatResultsFormat {beast,connect,localhost:30104 basestation,listen,310003}
> 
> If your local VRS is set to port 310003 (I think you may have one too many 0’s) for MLAT then I think you should be set. If you wanted to try the Co-Op VRS in addition to local VRS, the command would be
> 
> ```auto
> 
> sudo piaware-config -mlatResultsFormat "beast,connect,localhost:30104 beast,connect,feed.adsbexchange.com:30005 basestation,listen,310003"
> sudo piaware-config -restart
> 
> ```
> 
> If MLAT isn’t working with local VRS, try mgunther’s excellent tutorial: [http://discussions.flightaware.com/ads-b-flight-tracking-f21/vrs-show-both-dump1090-adsb-and-fa-mlat-positions-t36086.html](https://discussions.flightaware.com/t/vrs-show-both-dump1090-adsb-and-fa-mlat-positions/17399)

Thanks you sir! I did add too many zeros when typing. Will try re doing ports on VRS tonight. Imma learning slowly!

---

<div class="post-metadata">

**Author:** ![dschaper](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/dschaper/32/59633_2.png) [@dschaper](https://discussions.flightaware.com/u/dschaper)\
**Post date:** [October 18, 2015, 7:25pm UTC](https://discussions.flightaware.com/t/error-on-mlat/17462/10 "2015-10-18T19:25:41Z")

</div>

> [@Foxinthehouse1](#):
>
> Thanks you sir! I did add too many zeros when typing. Will try re doing ports on VRS tonight. Imma learning slowly!

Are you back online now?

---

<div class="post-metadata">

**Author:** ![Foxinthehouse1](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/foxinthehouse1/32/114064_2.png) [@Foxinthehouse1](https://discussions.flightaware.com/u/Foxinthehouse1)\
**Post date:** [October 18, 2015, 8:46pm UTC](https://discussions.flightaware.com/t/error-on-mlat/17462/11 "2015-10-18T20:46:06Z")

</div>

> [@dschaper](#):
>
> > [@Foxinthehouse1](#):
> >
> > Thanks you sir! I did add too many zeros when typing. Will try re doing ports on VRS tonight. Imma learning slowly!
> 
> Are you back online now?

Yes far as I can tell. However on my VRS I set the two feeds to merge for one output, but also allow me to select which feed so I could plot ranges. But I am noticing when I select the “merged” feed does not show the combined planes from either feed all the time. I don’t know if this is in my VRS settings (I sat it up following that other thread on doing it)

Here is my Site, you can see from your self. Piaware - MLAT is the combined “merged” feed from the other two.  
[kchapiaware2.ddns.net/](http://kchapiaware2.ddns.net/)

So in conclusion it is working enough to make me happy a little, May buy a new antenna and get more range out of it now. If only I could reach atlanta…

Thanks again!

---

<div class="post-metadata">

**Author:** ![Frazpo](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/frazpo/32/113665_2.png) [@Frazpo](https://discussions.flightaware.com/u/Frazpo)\
**Post date:** [October 18, 2015, 9:22pm UTC](https://discussions.flightaware.com/t/error-on-mlat/17462/12 "2015-10-18T21:22:24Z")

</div>

> [@Foxinthehouse1](#):
>
> > [@dschaper](#):
> >
> > > [@Foxinthehouse1](#):
> > >
> > > Thanks you sir! I did add too many zeros when typing. Will try re doing ports on VRS tonight. Imma learning slowly!
> 
> Are you back online now?
> 
> Yes far as I can tell. However on my VRS I set the two feeds to merge for one output, but also allow me to select which feed so I could plot ranges. But I am noticing when I select the “merged” feed does not show the combined planes from either feed all the time. I don’t know if this is in my VRS settings (I sat it up following that other thread on doing it)
> 
> Here is my Site, you can see from your self. Piaware - MLAT is the combined “merged” feed from the other two.  
> [kchapiaware2.ddns.net/](http://kchapiaware2.ddns.net/)
> 
> So in conclusion it is working enough to make me happy a little, May buy a new antenna and get more range out of it now. If only I could reach atlanta…
> 
> Thanks again!

Mine also behaves in this manner. I don’t think there is anything wrong, I think it is the way VRS is handling the data.  
However, when I am merging my Mlat and ADSB receivers in VRS it will show some as MLAT planes on the page but if I just choose the MLAT receiver to show on the map it will show a bunch more then when the ADSB receiver is merged. Make sense??