Latest 9H- hexcodes not showing

[keef777]

Hi all
I wonder if anyone else has noticed the problem I'm having and, hopefully, has found a solution?
I have a couple of blue Prosticks hooked up to two laptops, and I have the same problem on each. None of the latest Maltese hexcodes are being picked up and shown on my basestation screen, the only way I can ID the aircraft is FR24 or ADSBx. It affects all hexcodes from 4D2400 onwards, so that includes all the new and rereg Wizz and all new Vistajets.
I've missed a few lately because I now get no warning that they're there unless I happen to be on a flight tracker at the time. As far as I can make out, 9H- is the opnly one affected - so far!
Any ideas please?

[Faramir]

My thought is that Malta has got an extra bit aaded to it's original allocated block to accomodate all the Ryanair movements.
My entry for Malta in Countries.dat is now
Malta=010011010010xxxxxxxxxxxx,12,Malta.bmp
and all planes are decoded fine...

[Anmer]

What are you using to decode the data from the Pro Sticks so that Basestation can use it?

Can you describe your hardware and softwarre setup?

[keef777]

Both laptops are on Win 10 and I'm using Planebase to convert the hexcodes to registrations which then appear in my basestation, but that's not the problem - the hexcodes aren't even being picked up by the Prosticks in the first place. I live 2 miles from Luton, and normally when an aircraft departs it's shown on my basestation, but when one of these 9H- departs there's nothing showing at all, no reg, no hex, they're not even tracking.

[mhm]

My Malta is showing
Malta=01001101001000xx,14,Malta.bmp

Last one that needs updating as its blank is 4D2486 in reporter

[keef777]

Mine picks up everything up to 4D23FF, then nothing after that. I've looked in Basestation Reporter and that confirms it.

[Anmer]

the hexcodes aren't even being picked up by the Prosticks in the first place.

How do you know that?  What you're seeing (or not) are the messages decoded by Planebase.  How is Planebase decoding the data?

Can you describe precisely your setup and let us have some examples of the hex codes you're not "seeing"?

[keef777]

The setup is as I said before and has been unchanged since I bought the Prosticks about 3 years ago, although both laptops are newer. Win 10 running Kinetic Basestation software (v 1.2.4.1884) along with Planebase.

The problem is that the Prosticks aren't picking up the codes in the first place, there's nothing for Planebase to decode. In the last couple of weeks we've had the following, none of which codes appear in Basestation Reporter, which goes straight from 4D23FF to 500057:-
9H-WAD  4D2402
9H-WAJ   4D241F
9H-VVE   4D2449
9H-VCV   4D2486
9H-WBX   4D247B
9H-VIT     4D247F
9H-VCU    4D2480

[Anmer]

The problem is that the Prosticks aren't picking up the codes in the first place,

Sorry to labour this but how do you know the receivers are not picking up these aircraft?

Is Planebase "decoding" the messages?  I can't find a Planebase decoder.  That may be my fault.

What are you using to pass data to Basestation?

Wizz doesn't fly west of Cardiff so I don't pick up many of its aircraft.  But I have lots of hex codes received after 4D23FF.  And I have a ProStick.

My guess it's a software issue not the ProSticks.

[s92driver]

Planebase does not decode the ModeS signals that are being picked up by your Prosticks, you must be using some other software.

I suspect you are actually using ModeSDeco2?  Which will not decode the expanded Maltese allocation if using the default settings.  If you confirm that you are actually using ModeSdeco2 I'll let you know how to correct the situation.


Steve

[keef777]

The hexcodes picked up by the Prostick are decoded by the Planebase program PBLink. This provides the link between Basestation and the Planebase database itself. As soon as a new code is picked up PBLink interrogates Planebase and auitomatically populates Basestaion, including whether or not it is required.
I can't see anywhere I can change the software setup, indeed, I've never had this problem since buying my first SBS-1 at the end of 2006.
The only other thing I've tried was to start a new .sqb file, but that obviously hasn't worked either.

I've just seen another reply which mentions ModeSdeco2, which is indeed what I'm using. I didn't mention this because I thought that was just needed to run the Prostick in the furst place, it seems that I was mistaken.

[Anmer]

Planebase is an external aircraft database.  Its application is "linked" to your local Basestation.sqb file.  The ModeS messages transmited by aircraft don't contain "personalisation" data such as registration, make, type, owner etc.  One has to add this manually to the sqb file or use an app like Planebase,

Basestation was designed to receive decoded and formatted data from a Kinetic SBS or Puck receiver.

The ProSticks do not decode or format the received ModeS messages.  One needs other software to do the decoding, such as ModeSdeco2, as pointed out by s92driver.  That's where the problem lies.  Unfortunately the ModeSdeco2 developer is no longer supporting his applications.

[Keef]

Hi s92driver,

Can I take you up on your offer of how to correct ModeSdeco2 to decode the expanded Maltese allocation please?

Cheers,

Keef

[keef777]

Thanks for clarifying that Anmer, now I understand it a bit better. Hopefully s92driver can come to my rescue.

[s92driver]

Hi Keef,

You will need to edit your ModesDeco config file.  So that is the batch file you use to launch the program, it will end in .bat

Once you find the batch file you will need to open it in a text editor such as Notepad.

Then add the following     --filter-nocountry

Save the file and relaunch ModesDeco.  You will now start processing the new Maltese codes.


Steve