new user

[boro]

I have just got flightaware setup and registered and running ok including mlat. The Skyaware map is showing my local traffic but not showing blocked traffic, other than an icon going across the map with no details what it is. I am still running basestation at the moment and I noticed an aircraft which is blocked on commercial tracking sites going over head on the way to Southampton, it was actually VQ-BXH, when I looked at the skyaware map with local traffic it was just showing an icon going across the map but no details of what the aircraft was because it is blocked. Am I missing something here, does blocked aircraft still come up as blocked on the local Skyaware map, which is a pain if it does as I live near EGLF which has a number of blocked business aircraft using it.

[Anmer]

First of all, note that the SkyAware map/list uses FlightAware's server side aircraft database.  In my experience, the database is not great.

I feed FlightAware and use ModeSMixer2 to feed my locally received data and FlightAware's MLAT plots to Basestation which references my updated, local sqb file.
I have no need of FlightAware's inferior database or SkyAware.

[boro]

Hi Anmer, thank you for your reply, ModeSmixer2 looks like the way to go for me, I will have to look up about setting it up, as someone who has used Basestation for many years I have become used to a good reliable database.

[Anmer]

Get back to us if you need help with ModeSMixer2.

[boro]

Ok thanks

[boro]

Hi Anmer, I downloaded modeSmixer2 for windows from the software files and extracted the file in the documents folder, but when I open the folder and click the modesmixer2 application nothing happens, other then a window quickly open and closes, obviously I am not doing something right, couldn't point me in the right directions, thanks.

[Anmer]

I'll reply in detail tomorrow.  Of to bed!

[Anmer]

Morning!

Did you edit the ModeSMixer2 BAT file to point to the IP address of the PiAware feeder and output ports?

Here is my BAT file:

Code Select Expand

@echo off
CMD /c I:\MSM2\modesmixer2.exe --inConnect 192.168.1.136:30005 --inConnect 192.168.1.136:30105 --filter-nocountry --outServer sbs10001:10002
exit

"I:\MSM2" is the folder location for modesmixer2.exe.

I then set the Basestation Data Source to "Network" and the Network address to the IP of the PC running ModeSMixer2 and to use port 10002.

192.168.1.136 is the IP of my RPi running PIAware.

[boro]

Hi Anmer, I am up and running! many thanks for your help, I always do these things with great trepidation as i worry i am going to mess up somewhere!

Presumably when i run basestation i would need to start modemixer first?

As a side issue I have noticed since using the fligthaware dongle my range has increased, I have got an outside aerial which has been up about 14 years and I have noticed over time the range was decreasing, taking aside that the aerial probably needs replacing anyway, it seems the flightaware dongle is more sensitive than the SBS3?

cheers

peter

[Anmer]

Presumably when i run basestation i would need to start modemixer first?

Your presumption is correct.

I found most "dongles" delivered more aircraft and range that the SBS family.  Not a lot but definitely more.