Radarspotting

Hie there,


Is the very large number of Russian hex codes that my SBs-3 picks up replicated by all the other SBS decoders or peculiar to the BaseStation SBS series?


Their number seems to be on the increase, and unlike other "spurious" codes,as they are allocated to a country, not as easy to lock out.


Regards Mike

Hi Mike

Can you share a sample of the codes?  I assume all without positional data?

This issue was raised on the Mode-S group forum in early March, when several users reported an increase in 'spurious' codes.

I asked the same question as to whether it related to(Kinetic) SBS receivers or was a more general Mode-S problem, most replies were from SBS users but several dongle users reported an increase as well. From the replies it seems to be countrywide but not so apparent in Europe.

My own observations showed an increase from around 3 per day up to 30 or 40 per day, although in the last week or so this seems to have reduced to around 20.

I delete them after each session so I don't have a record of the exact codes but, from memory, they appear to be from (in descending order) Russia; Not Allocated; Germany; France & Serbia, with a smattering of other countries thrown in.

All in all it's become a bit of a chore deleting them each day.

Ian


   

Sorry for slow reply. Attached is the list of "unknown tie-ups" from yesterdays session. The Russian Federation ones are regularly culled by me but are very prolific.


I am using an SBS-3 via Win10 PC using Plane-base for decoding etc.


I have always had a few of these but in last year - 18 months seem to be numerous every day.

[attachment deleted reduce file load]

Thanks Mike.

I'm aware of reports of spurious Mode-S data being generated in China and elsewhere.  Someone  transmitting false data which was always a concern.  Maybe we have a similar situation nearer home?

A bit like spam emails using false sender addresses.  There's always going to be people who like to cause chaos.

Checking my own sqb file, I have a couple of the codes listed.

Thanks for looking Mike.


There are also a few starting 3E ones, which are all German, and end in oo. I wondered if some in this list are just "Birdies" similar to those that can be found on air-band radio.

Re spurious Codes
I observe a varying number of Hex assigned to Russia
often ending with 40,43, 44, 4b, 49, which make me suspicious right away
in the past their last-time end often one second before start-time
but lately no more of that.
I have not checked whether these ModeS happen mainly during workdays
(major mil activity) or also during week end.
re the german-assigned Mil-Block checked and found none of your listed
3E..00 in myne

Thanks Guys,


I try and delete this rubbish about once a week but there is more and more of it. I did wonder if it is peculiar to the Kinetic SBS series or affect every type of system device.


Regards Mike

At intervals I clean out the 'Not Allocated' as well , in one collective SQL-Browser command
but due the 12xxxx are ever repeating , I ignored them and accumulated some 40 different in 3month most coming up and up again , with no real entry in between.

So I wish to delete them enblock like: Delete from Aircraft where ModeS>=12xxxx AND ModeS<=13600;
but that appeared to work only in a pure numerical list

Does anyone know how do it with an alphanumerical in between the rising hex ?
Regards

I normally shutdown Basestation for a short time each evening to check for any 'hidden' changes or corruption &, as part of that process, I delete any spurious codes at that time.
I took the simpler option of marking the Reg' of each one as X in Basestation Reporter as I update the new entries and then run the following SQL command:
DELETE FROM Aircraft WHERE Registration = "X"

I guess if all your other records have an entry in the registration field you could jut run an SQL command to delete any record where the registration field is Null.

Ian

This is fixed by tick box from memory it is TISB
When I get 5 minutes I will look and confirm.

Thanks Chris.

In BaseStation ->Settings ->Data Settings.

Maybe experiment with the Message Filtering check boxes, see attached?

[attachment deleted reduce file load]

I already have the 3 ticks for the ones you mention, I also have a 4th entry in that block, Relay Mode A/C Messages, which is also ticked.

Hi Mike

Have you tried un-checking them?

I posted the place Chris mentioned.  The example may not be relevant.

Mike,
I will try that for th 3 mentioned but surely I need the "Relay Mode A/C Messages" ticked if I want Mlat traffic?


Regards Mike

Quote from: Roadrunner on April 05, 2019, 09:07:19 AM
I need the "Relay Mode A/C Messages" ticked if I want Mlat traffic?

Where do you see that option?

As per BaseStation Reference Manual:

Message Filtering:

Ignore Non ADS-B Mode-S Messages: By default BaseStation receives and processes both ADS-B and non-ADS-B Mode-S messages. However, you can turn off the processing of non-ADS-B messages by checking the Ignore Non ADS-B Mode-S Messages checkbox.

Process Mode-S Air to Air Replies:
SBS-3 SBS-1eR SBS-1e, 1090 Puck

Enables forwarding by the SBS or Puck of Mode-S Air-to-Air Surveillance Replies (TCAS Replies). As these contain altitude information, this may enable BaseStation to display the altitude of non-ADS-B but Mode-S equipped aircraft, even when they are outside the coverage of Mode-S radar stations.

Enabling this feature will significantly increase the amount of data transmitted from the SBS or Puck to the PC, and hence the bandwidth required when connecting over a network.

This feature is available currently available only on the SBS-3, 1090 Puck and SBS-1e/eR and will also require a firmware update on the SBS-1e/eR if the firmware build number displayed by the Help >About BaseStation menu is less than 517.

Process TIS-B Messages:
SBS-3 SBS-1eR SBS-1e, 1090 Puck

This enables processing of TIS-B messages by BaseStation. These are similar to ADS-B messages, but are broadcast by radar ground stations, mainly in the USA to relay data about non-ADS-B aircraft, so that aircraft equipped with ADS-B receivers can "see" them.

This feature will require a firmware update on the SBS-1eR or SBS-1e if the firmware build number displayed by the Help > About BaseStation menu is less than 517.

Process ADS-R Messages:
SBS-3 SBS-1eR SBS-1e, 1090 Puck

This enables processing of ADS-R messages by BaseStation. These messages arise because there are two channels used for ADS-B in the USA. These are the 1090 MHz world-wide radar reply channel monitored by BaseStation, and also the 978 MHz UAT channel which uses a different transmission format. Ground stations in the USA are being equipped to re-broadcast data received on one channel as messages on the other channel. This allows differently equipped aircraft to be aware of each other.

This feature will require a firmware update on the SBS-1eR or SBS-1e if the firmware build number displayed by the Help > About BaseStation menu is less than 517.

TIS-B and ADS-R messages are intended to be transmitted from ground to air and normally will be received only if the antenna is within line-of-sight of a ground station.

Relay Mode A/C Messages:
SBS-3, 1090 Puck

This checkbox enables output of Mode A and C data on BaseStation's raw data output over Ethernet (port 30006). BaseStation does not currently use Mode A/C messages itself but they can be used by third party applications connecting to this port. Enabling this option will increase data bandwidth significantly.

Process Non-ICAO Addresses:
SBS-3 SBS-1eR SBS-1e, 1090 Puck

Aircraft or ground vehicles equipped with Mode S radar transponders use 24-bit addresses from a block allocated to each country by ICAO and which are unique to a particular aircraft or vehicle. This is the code that is displayed as a 6-character hexadecimal number by BaseStation. However ADS-B, TIS-B and ADS-R messages that do not originate from Mode S transponders are allowed to use a different set of 24-bit addresses that are not allocated by ICAO and do not have to be unique. This applies for example to certain ground vehicles. TIS-B messages may also use a 24-bit address made up of the 12-bit Mode
A (Squawk) code plus a 12-bit track number allocated by the radar station.

If you enable this feature then BaseStation needs to use special processing for the non-ICAO addresses to avoid incorrect lookup and display of countries, aircraft registrations etc. There is no way for BaseStation to determine the country for a non-ICAO address, and there is no guarantee that such an aircraft or ground vehicle will consistently use the same address.

As the database currently uses a fixed 6-character field for the aircraft address, BaseStation distinguishes non-ICAO addresses by modifying the first character of the displayed hex code as follows:

0 -> G
1 -> H
2 -> J
3 -> K
4 -> M
5 -> N
6 -> P
7 -> Q
8 -> R
9 -> S
A -> T
B -> U
C -> V
D -> W
E -> X
F -> Y

This means that the code does not conflict with the existing ICAO addresses in the database, while still fitting within the 6 character aircraft address field.

For the ModeA/Track number addresses (used by TIS-B only) the last digit is modified instead.

The setting Output Non-ICAO Addresses enables these aircraft to be output to the data port for use by third party applications. Leave this option unchecked if the application cannot handle the modified 6- character codes.

The setting Save Non-ICAO Addresses to DB enables saving of aircraft with these addresses to the database. Again, you can leave this option unchecked if the database is used by a third party application that cannot handle the modified 6-character codes.

Timeouts (Seconds): These parameters dictate how the application responds when it stops receiving messages from an aircraft.

If a preset number of seconds (configured using the Position Lost box) has elapsed since the time the last message was received, the aircraft changes to a state of "position lost", and is shown as yellow (by default) on both the Radar Screen and in the Aircraft List.

If a further period (set by the Signal Lost box) elapses without receiving a message, the aircraft changes to a state of "signal lost" and is removed from the Radar Screen and shown as red in the Aircraft List.

If a further period elapses without receiving a message (configured in the Remove box) then the aircraft is removed from the Aircraft List.

When a final period (set by the Delete box) has elapsed, the aircraft's data is purged completely from memory.

Thanks Mike,


I do send data to PPlotter,  and for a short time more to FR24. I therefore need that option ticked, the others not so sure about


Mike

Hi Mike

I don't see this option?

Relay Mode A/C Messages

Do you?

Yes below the 3 entries that started this discussion. I have an SBS-3 connected to ethernet and feeding my PC

[attachment deleted reduce file load]

Thanks Mike.

What version of BaseStation are you running?  I need to investigate why I don't see that option.

Sorry about the delay in replying but got builders in an electricity on and off all the time.


Software Version : 1.2.4.185
Firmware Version :  SBS3 build 119.


I have a loft aerial. I got 23  Russians again in just the day yesterday (8 hour running period)


Regards Mike

Thanks Mike.

I realised why I wasn't seeiong the same option. I'm not using an SBS-3 or Puck.

Maybe Chris was on the wrong track?

Thanks,


Looks like I will re-check the other 3 options and just live with deleting them regularly. Today, a Saturday I have only had 5 Russians since 7 am to now.


Regards Mike

I had a look at my logged "Russian" modes and extracted just info relating to Mike's supplied list and put the data into excel.

Info for the attached files is:-

00_Russian_Data.zip/xlsx - Is my data extracted to Excel.

01_Russian_Daily_Total.jpg - Shows just the daily total received.

02_Russian_Daily.jpg - Shows daily total broken down by ModeS

03_Russian_Daily_Excluding_445566.jpg - Shows daily total excluding ModeS "445566"

04_Russian_Daily_445566.jpg - Shows daily total of only ModeS "445566"

Inforation releveant to my data is that up to September 2018 I was using an SBS1 connected via USB, after that I have been using an SBS1er connected via ethernet.

The jump up in 445566 reception does seem to coincide with the swap over.

Kelvin

[attachment deleted reduce file load]

Could the jump be due to a higher sensitivity of the SBS-Ie, and even better with the SBS-3?

I guess that's a possibility, but i don't have any comparable data from the SBS-3 to check against.

Mike
I run an SBS 1 on a stand alone pc it has 650 Russian federation
I run an SBS Puck on a pc that's internet connected and it has 795 Russian Federation