FlightRadar24 ADSB Receiver

[EA1DDO]

Ian, something is not working.   

If I use the modesmixer command as you said, using port 30334:

2018-04-07 21:25:27.761  INFO     ModeSMixer2 v.20170924
2018-04-07 21:25:27.761  INFO     Magnetic declination value was calculated
2018-04-07 21:25:27.777  INFO     inConnect(192.168.1.147:30334) connecting 192.168.1.147:30334
2018-04-07 21:25:27.777  INFO     inConnect(192.168.1.147:30334) connected

In the receiver Status page is saying:
STATUS:

RECEIVER SOFTWARE: ON [stop, display log]
  BS  FEED [30003]: UP, NUM CONNECTED: 0

So I´ve tried port 30003, instead of 30334 and I´ve got this:

2018-04-07 21:22:17.747  INFO     ModeSMixer2 v.20170924
2018-04-07 21:22:17.762  INFO     Magnetic declination value was calculated
2018-04-07 21:22:17.762  INFO     inConnect(192.168.1.147:30003) connecting 192.168.1.147:30003
2018-04-07 21:22:17.762  INFO     inConnect(192.168.1.147:30003) connected
2018-04-07 21:22:19.064  INFO     Coverage area was determined
2018-04-07 21:22:19.064  INFO     Magnetic declination value was calculated

But either case, using the browser I go to 192.168.1.147:8090 and nothing happens. It is not connecting to any page.
Is that correct?
What software can I use to read that output?

Cheers
Maximo

[Anmer]

Helpful post by Khan on FR24 forum:

Skysense can be accessed via IP-of-receiver:8754 while the other receivers directly via IP without the use of any ports.

https://forum.flightradar24.com/threads/11790-New-FR24-receiver-from-Skysense?p=103834&viewfull=1#post103834

[EA1DDO]

Helpful post by Khan on FR24 forum:

Indeed.

Anmer, top man.
Big thank

[IanH]

It is probaly working given the messages you see.

BUt you need to connect to the port on the PC running modesmixer2.

Modesmixer2 is receiving data from the FR24 receiver either on port 30334 or port 30003.

If you are running modesmixer2 on 192.168.1.1 (adjust acordingly), look for the output on 192.168.1.1:8090 (or whatever  port you have defined in --web parameter).

I know this is tricky at first - mulltiple PCs, multiple ports. Eventually it makes sense. 

I've got a Pi sending date to a minimal virtual PC to combine ADSB and MLAT data using modesmixer2 which I display on my desktop PC.

The nice thing about modesmixer2 is that the combined data can also be viewed at the same time on any other PC using a choice of display programs. I could display on BaseStation, GlobeS, Plane Plotter, ADSBScope, ADSBox, ADSBLogger, FlightAirMap all at the same time.

[EA1DDO]

If you are running modesmixer2 on 192.168.1.1 (adjust acordingly), look for the output on 192.168.1.1:8090 (or whatever  port you have defined in --web parameter).

Ian, thanks for that.
My receiver is on 192.168.1.147 and modesmixer is listening port 30003 and output on 8090.

The Basestation software I did set that IP 192.168.1.147 and port 8090.
Type of receiver "Other" (third/last option).

The test page is fine, successfully passed.
But when open the main one... starts to report errors. Every data readed is an error.

Error : EAccessViolation - Access violation at address 00591E38 in module 'BaseStation.exe'. Read of address 0000006C

I've tried running Basestation as Admin, same result.

I guess I am missing something...

Regards, Maximo

Code Select Expand

App: BaseStation
Version: 1.2.4.184

-----------------------------------------------

Occurred : 21:45:05.977 2018/04/10

Error : EAccessViolation - Access violation at address 00591E38 in module 'BaseStation.exe'. Read of address 0000006C

Last Command : UPDATE Sessions SET LocationID = 1 WHERE SessionID = 1

Last Aircraft :

System Status : 0 | 0 | 0 | 0 | 0 | | 0

Previous : O-WriteToDebugMemo | I-WriteToDebugMemo | I-VersionInfoCheckingTimer | O-StatusBarTimer | I-StatusBarTimer | O-ProvisionalAircraftListTimer | I-ProvisionalAircraftListTimer | O-AircraftListTimer | I-AircraftListTimer | O-AircraftListGridTimer | O-AircraftListGrid.UpdateValues | I-AircraftListGrid.UpdateValues | I-AircraftListGridTimer | O-RedrawTimer | I-RedrawTimer | O-DisplayTrackingTimer | I-DisplayTrackingTimer | O-AircraftTimer | O-DispatchDelayedMessages | I-DispatchDelayedMessages | O-CheckStatuses | G-CheckStatuses.GetCurrentPlayTime | I-CheckStatuses | I-AircraftTimer | O-AutoRefreshTimer | I-AutoRefreshTimer | O-WriteToDebugMemo | I-WriteToDebugMemo | I-MainSecondTimerTimer | O-WriteToDebugMemo