Flightradar24 Feeder Chat

[w7psk]

New Receiver T-KPAE8
Im currently testing with indoor antenna that I made (Colinnear) and its ready to go outside. Just need to figure the cable routing and the mounting for it. Im using 1/2" PVC to cover the coax. Even with Indoor Im getting up to 75 miles away. Limited to the window line of sight for the longer ranges. Get 20 miles or so through the house

[peterhr]

New Receiver T-KPAE8
Im currently testing with indoor antenna that I made (Colinnear) and its ready to go outside. Just need to figure the cable routing and the mounting for it. Im using 1/2" PVC to cover the coax. Even with Indoor Im getting up to 75 miles away. Limited to the window line of sight for the longer ranges. Get 20 miles or so through the house

Are you close enough to get ground movements from Boeing field?

[w7psk]

Are you close enough to get ground movements from Boeing field?

Sorry, no. Im near Snohomish County Airport (Paine Field) in Everett. KPAE2 gets ground movement there. Even when I get outside I wont as I have a 100Ft hill between me and the airfield. KBFI is about 30 miles south in Seattle.

[w7psk]

Here is my range map for the indoor antenna. Gots to get this out side. Need to find a easy sourced Eave mount to put it on.

Range Map.jpg

Id be interested in finding out whom F-KPAE2 is and see what he is using. His reports are constant all day. KPAE1 and KPAE6 are sporadic. Never see 3,4,5 and 7.

T-MLAT2 seems to be taking over most of the PNW reports though.

Ive only seen 1 or 2 reports from me. Id be interested in what the algorithm is for what gets displayed.

[FR24support]

F-KPAE2 is using our FR24 equipment. "T" are other receivers which do not contribute to MLAT.

T-MLAT are non-positional aircraft plotted using our own receivers. Otherwise they would not appear on any map, except from FAA 5 minute delayed (if available).

[SoCalBrian]

Why can't Radarcape owned by the T- users can't help with MLAT anymore.

That sucks

[peterhr]

Here is my range map for the indoor antenna. Gots to get this out side. Need to find a easy sourced Eave mount to put it on.

[ATTACH=CONFIG]4257[/ATTACH]

Lots of eaves mounts on Ebay, with free postage - but though the masts are cheap, the postage on them is stupid - there most be someone local who sells sectional masts (so you can add a bit to adjust the height)

[FR24support]

Radarcapes can still contribute to MLAT if the customer chooses to enable it. But the vast majority of "T" receivers are not Radarcapes. It was an "overview" response.

[w7psk]

Lots of eaves mounts on Ebay, with free postage - but though the masts are cheap, the postage on them is stupid - there most be someone local who sells sectional masts (so you can add a bit to adjust the height)

Loads of masting around here . Ill look on sleese bay and see. Im loath to use it though.

[w7psk]

F-KPAE2 is using our FR24 equipment. "T" are other receivers which do not contribute to MLAT.

T-MLAT are non-positional aircraft plotted using our own receivers. Otherwise they would not appear on any map, except from FAA 5 minute delayed (if available).

Much thanks

[Ressy]

Radarcapes can still contribute to MLAT if the customer chooses to enable it. But the vast majority of "T" receivers are not Radarcapes. It was an "overview" response.

Curious how you know the data from a T feed is from a privately bought radarcape box? obviously you know the F's are, is there a special code they add?

[peterhr]

Loads of masting around here . Ill look on sleese bay and see. Im loath to use it though.

Here (in the UK) most stuff like that there seems to be where smaller businesses sell stuff without having to pay a big advertising fee or giving amazon a thick slice, not sleezy - just another sales channel.

[paradiselost]

Why can't Radarcape owned by the T- users can't help with MLAT anymore.

That sucks

If you have an F-box look at the box Status page.

FR24 CONNECTION STATUS:
ADS-B: connected, 3 AC tracked
ModeS: disabled

In practicality, the RadarCape (FR24 F-box) can't turn ModeS on or off.....it is just FR24 ignoring ModeS from all T-boxes. ModeS is still functioning as verified by VRS. Comparing the statistics on your FR24 account info with the log produced by VRS will show that FR24 rejects 75% of your data and that 75% is not all ModeS but ads-b also.

Since you are feeding FR24 rejection of ModeS is in their control.

F-KPAE2 is using our FR24 equipment. "T" are other receivers which do not contribute to MLAT.

T-MLAT are non-positional aircraft plotted using our own receivers. Otherwise they would not appear on any map, except from FAA 5 minute delayed (if available).

If you are interested in pseudo-tracking ModeS aircraft other options are available with a different receiver.

Radarcapes can still contribute to MLAT if the customer chooses to enable it. But the vast majority of "T" receivers are not Radarcapes. It was an "overview" response.

The assertion by Support that RadarCape users can enable ModeS is an illusion... it is always ON.

John

F-RPVD1

[F-EGLF1]

If you have an F-box look at the box Status page.

FR24 CONNECTION STATUS:
ADS-B: connected, 3 AC tracked
ModeS: disabled

John

F-RPVD1

John,
Don't know why your F box shows ModeS: disabled, the status page on mine shows

FR24 CONNECTION STATUS:
ADS-B: connected, 102 AC tracked
ModeS: connected, 32 AC tracked

Ben.

Just a thought, is it because you don't have Mlat in your region yet ?

[paradiselost]

John,
Don't know why your F box shows ModeS: disabled, the status page on mine shows

FR24 CONNECTION STATUS:
ADS-B: connected, 102 AC tracked
ModeS: connected, 32 AC tracked

Ben.

Just a thought, is it because you don't have Mlat in your region yet ?

Ben, Europe, Scandinavia, Australia and some parts of the US are the only ones with ModeS connected. Ninety eight percent of the rest of the world will never have MLAT.

The ModeS connected or disabled on the status page is the result of feedback from the FR24 server. It is accepting your data if you are in a MLAT area and if not rejecting it and showing disabled. The F-box produces ModeS output regardless of what the ModeS connected or disabled says.

Overlapping coverage of ModeS is just one part of the FR24 algorithm, the big killer in the rest of the world is latency, time it takes to get to the server. Servers in the cloud are the only solution to overcome latency issues and produce local MLAT. Perhaps the Australia model might work in the rest of the world.

John

F-RPVD1