ModeSDeco2 and ModeSMixer2 - console programs for RTLSDR and transcoding

[mlino]

Hi sergsero,

Is there a solution for the issue show in the attached image? I have cleared Firefox's cache but it doesn't work. Version in use is v.20160119.

Regards,

Mlino


[Attachment deleted by Admin to save file space]

[sergsero]

Hi Mlino,

Try this method:
1. Using the menu in header go to page "Flights".
2. In table select any aircraft with coordinates.
3. Move mouse cursor to his icon of earth (right-most) and left click.
4. You will be redirected to page "Map". Probably the Google map will be distorted.
5. Press keys (possibly several times) Control+F5 or Control+Shift+R.

Regards,
sergsero

[mlino]

Hi Mlino,

Try this method:
1. Using the menu in header go to page "Flights".
2. In table select any aircraft with coordinates.
3. Move mouse cursor to his icon of earth (right-most) and left click.
4. You will be redirected to page "Map". Probably the Google map will be distorted.
5. Press keys (possibly several times) Control+F5 or Control+Shift+R.

Regards,
sergsero

Hi sergsero,

The above solution doesn't work in my case. I have pressed the key combination several times but nothing has changed...

Thank you

Mlino

[jmaurin]

ModeSMixer and ModeSDeco are abandoned?

[IanH]

Why do you suggest that?

If current versions work, why would they need updating?

Explain your negative comment!

[IanH]

Is there a solution for the issue show in the attached image? I have cleared Firefox's cache but it doesn't work.

i had the same problem in Chrome. Clearing the cache did not work - I had to go into Chrome advanced settings and clear a lot of old data = "clear browsing data". Then it worked. Don't know the equivalent for Firefox but just clearing the cache does not seem to be enough.

[jmaurin]

Why do you suggest that?

If current versions work, why would they need updating?

Explain your negative comment!

Negative comment? Are you trying to cause mess? It's just a question!
And why I asked this? Simples: some time ago sergsero said that next version would have a lot of features, including the option to edit configuration in WebUI....also, there are some bugs, like that one with negative points if you add multiple......the workaround is to add the same parameter more than one, but still a bug until next version. Also, Sergsero had a health problem, meaning that they couldn't work in this program for a while. This would be more than enought to leave development of modes, since it's closed source.

[IanH]

TL;DR

[AVDB]

Hello,

Now all Google Maps JavaScript API applications require authentication and you must include an API key when loading the API.

This version adds new option: --google-key <arg>
that allows you to specify a Google API key and include it as the value of a key parameter when loading the API.


Intel Windows: modesdeco2_windows_20161010.zip https://drive.google.com/open?id=0B7NYXizl0U6iQlpNUy1DLXhCUGc

I would be grateful for help in testing this option.

/sergsero

modesmixer2_windows_20161009 works like a charm with the new --google-key option but modesdeco2_windows_20161010 gives me this error in spite of installing Microsoft Visual C++ 2015 Redistributable Update 3:

---------------------------
modesdeco2.exe - Ordinal Not Found
---------------------------
The ordinal 4684 could not be located in the dynamic link library C:\Program Files (x86)\Nmap\SSLEAY32.dll.
---------------------------

[spotter.ssol]

Hi sergsero! Hope you're recovering fine.

I have a remote station running dump1090, feeding BEAST to piaware at home. The piaware's MLAT return feed is then pointed to modesmixer on the same system, mixing adbs+mlat data for local view.
This setup was working, but recently I've upgraded piaware (debian package) from version 2 to 3, as required. Now I'm not getting MLAT plots anymore.

Everything still looks absolutely ok:

-FA's user page says ok and connected:

Code Select Expand

Feeder Type: PiAware (Debian Package Add-on) 3.1.0
Multilateration (MLAT): Supported / Enabled (synchronized with 28 nearby receivers)

-piaware's log says ok and connected:

Code Select Expand

Oct 28 22:01:03 ednas piaware[5204]: mlat-client(5257): Beast-format results connection with 127.0.0.1:30104: connection established
Oct 28 22:04:25 ednas piaware[5204]: 22960 msgs recv'd from the ADS-B data program at ***/8080 (243 in last 5m); 22960 msgs sent to FlightAware
Oct 28 22:09:25 ednas piaware[5204]: 23138 msgs recv'd from the ADS-B data program at ***/8080 (178 in last 5m); 23138 msgs sent to FlightAware
Oct 28 22:14:10 ednas piaware[5204]: mlat-client(5257): Receiver status: connected
Oct 28 22:14:10 ednas piaware[5204]: mlat-client(5257): Receiver status: connected
Oct 28 22:14:10 ednas piaware[5204]: mlat-client(5257): Server status: synchronized with 17 nearby receivers
Oct 28 22:14:10 ednas piaware[5204]: mlat-client(5257): Receiver: 37.7 msg/s received 27.2 msg/s processed (72%)
Oct 28 22:14:10 ednas piaware[5204]: mlat-client(5257): Server: 0.1 kB/s from server 0.0kB/s TCP to server 0.4kB/s UDP to server
Oct 28 22:14:10 ednas piaware[5204]: mlat-client(5257): Results: 63.6 positions/minute
Oct 28 22:14:10 ednas piaware[5204]: mlat-client(5257): Aircraft: 2 of 4 Mode S, 7 of 8 ADS-B used


-modesmixer's log says ok and connected:

Code Select Expand

2016-10-28 22:01:03.332 INFO inServer(30104) 127.0.0.1:50980 connected
2016-10-28 22:01:05.353 INFO inServer(30104) 127.0.0.1:50980 BEAST data stream detected

-here's some raw data from mlat client and modesmixer taken with tcpdump:

Code Select Expand

1a33ff004d4c41540092e488ad90ad11f01c586e364db11a33ff004d4c41540092e488ad90ad162c1c97fca9c8481a33ff004d4c41540092e488ad99009e2d38440062e953
1a33ff004d4c41540092e48e3890abb14590079cf07fc91a33ff004d4c41540092e48e3890abb5846848a367370e1a33ff004d4c41540092e48e389900f02eb020007871a6
1a33ff004d4c41540092e48a0990b982282de2b7c6f4281a33ff004d4c41540092e48a0990b986633e233dae39111a33ff004d4c41540092e48a09990503ac500400eb9513
1a33ff004d4c41540092e484d690b9b082828d334ad8a41a33ff004d4c41540092e484d690b9b4c49acbcbaf536f1a33ff004d4c41540092e484d699051f95500c0059e614
1a33ff004d4c41540092e488ad90abf1f0fc58a0f0adb81a33ff004d4c41540092e488ad90abf62cf8982dfd75551a33ff004d4c41540092e488ad99009f2d584400ae67e6
1a33ff004d4c41540092e48a0990b98227a1e286f83ac01a33ff004d4c41540092e48a0990b98662b4230d1beb0d1a33ff004d4c41540092e48a09990502ac500400e89fdd

Am I missing something? Is modesmixer compatible with piaware anymore?

[Anmer]

Are you using the correct ports?

https://flightaware.com/adsb/faq

Can I access a streaming ADS-B data feed from FlightFeeder or PiAware? (Back to top) (Edit)

Yes, FlightFeeders and PiAware supports TCP connections to the following ports for data access:

30002 for raw/unparsed messages in AVR format

30003 for parsed messages in BaseStation format

30005 for raw/unparsed messages in Beast binary format

30105 for multilateration results (only) in Beast binary format (for FlightFeeders, the device must be running 7.x or newer software)

30106 for multilateration results (only) in extended BaseStation format (for FlightFeeders, the device must be running 7.x or newer software)


Additionally, the following data input ports are available for PiAware devices:

30104 for injecting raw messages in Beast binary format (messages will be forwarded to PiAware, shown on the local map and forwarded to port 30005 but multilateration results will not be forwarded to PiAware or port 30005)

30004 for injecting raw messages in Beast binary format (identical functionality to port 30104 but exists for backwards compatibility)

[IanH]

See posts here: http://discussions.flightaware.com/ads-b-flight-tracking-f21/any-changes-to-beast-mlat-format-in-piaware-3-t38113.html

Simple answer is that modesmixer2 is NOT compatible with Piaware 3

[spotter.ssol]

See posts here: http://discussions.flightaware.com/ads-b-flight-tracking-f21/any-changes-to-beast-mlat-format-in-piaware-3-t38113.html

Simple answer is that modesmixer2 is NOT compatible with Piaware 3

Thanks IanH! Installed version 2 and everything is OK again.

[sergsero]

Hello,

This version should work with the Google API key. If it's indeed confirmed in tests, it will become the release.

If you want find out what version of Linux is used, then try the console commands:

Code Select Expand

cat /etc/*-release
and

Code Select Expand

cat /proc/version


---
As for the new format of data in return channel in Piaware 3, when mlat-client now returns results as DF 18 TIS-B positions,  I hope to understand what has made Oliver with the Piaware.

Best regards,
sergsero

[IanH]

Good news - looks like modesmixer2 is mostly compatible with Piaware 3 

I had been testing the output of modesmixer2 in PlanePlotter and was combining the data to sbs30006 format - that seems to be the problem.

If I combine the Piaware outputs from port 30005 and 30105 and serve it in Beast format, both ADSB and MLAT data are plotted.

Code Select Expand

modesmixer2.exe --inConnect 192.168.0.179:30005 --inConnect 192.168.0.179:30105 --outServer beast:31005

Serving as sbs10001 to BaseStation also works.

Just the sbsb30006 conversion seems to cause problems.

So returning to the question from spotter.ssol, what is your modesmixer command line?

We should be abler to get it to work with Piaware 3