Welcome to Radarspotting. Please login or sign up.

May 16, 2025, 10:19:22 PM

Login with username, password and session length

New Members

New Members

You should get an activation email when you join.  If not, please use the Contact option.

String of strange hex codes

Started by Roadrunner, March 21, 2012, 05:38:28 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Roadrunner

Hi there,

I have an SBS3 and this afternoon at approx 14:45/14:46 I received a string of not allocated hex codes with the start and finish times the same. I have had this happen before but this time a large group of the codes all endING in E97 (4DFE97 09FE97 02FE97 017E97 007E97 003E97 001E97 000E97 0DFE97 05FE97) I also had a smaller group 008000 018000 E08000 all at the very same time of 14:45/14:46. In total there were 22 different codes. I have never experienced this many at one time before on any of my SBS1 SBS1e or my new SBS3.

Did anyone else experience this or have any possible explanation for it.

Anmer

Looking at Reporter I too have these and a number of the "E97" records.

E08000
010000
018000
030000

What Data Settings have you got for Message Filtering?
Here to Help.

Roadrunner

Hi Anmer,

As far as I am aware have the standard settings as I have not activated any of the "new" ones in the SBS3. I am switched off at the moment but will check them again in the morning. I have been using the SBS3 for just over 2 months and this is the largest group of "not Allocated" hexes I have ever seen at one time  ???

Mike

Anmer

Same here, none of those Message Filtering boxes are checked.

I suspect bad data wrongly decoded.  Be interesting to hear if anyone received these using an SBS-1?
Here to Help.

Ian K

None of those rec'd here on my SBS-1
Ian

Truetrack

Not on my SBS1 ( I know I am out of (Your) area )
Not even the usual "Russians" which come in pairs often.

Jus these around 12:37
B52520 start/end same sec
one sec later
B5253F start/end same sec
About 10 mins earlier a AWACS popped in NATO13 must have been tactical c/s MAGIC 63
any connection ?
Klaus

mhm

Mike
Colon Cancer Survivor for the Time Being

Tristar500

No strange codes on my SBS1 in Cheshire either.

Ian

boro

I am in Hampshire and the only "odd" one I picked up was 000002 and that came with the call sign XZ 697

Peter

Anmer

Quote from: boro on March 22, 2012, 07:25:14 AM
I am in Hampshire and the only "odd" one I picked up was 000002 and that came with the call sign XZ 697

Was that an SBS-1 or SBS-3 Peter?
Here to Help.

Thermionicmick

I am in the East Midlands and picked them up on my SBS-1 at the same time there was a gaggle of F15's about. One of the unexplained codes had a callsign of Hammr, could the spurious codes be from a dodgey pod on an F15 or even an ECM decoy? :-\

Mick
Mick

Roadrunner

Hi There,

I thought I had sent a message at about 6:30 this morning but cant see it so must have drempt it!.

My settings for the SBS3 in Stand Alone Data are all unticked. However in the Non-Volatile Memory settings for the Process Mode S Ait-to-Air replies, Process TIS-B Messages, Process ADS-R Messages and Relay Mode A/C Messages are all ticked. I dont know if that will cause me to get more unaccountable hex codes or not.

Regards

Mike

Anmer

I dreamt Liverpool were winning 2.0!

I don't have those settings but also got the same codes.
Here to Help.

boro

I'm using SBS1e.

Today I picked up 14 "Russian" at various times between 11.42 & 12.02.
120040 (twice), 120034, 1200A3, 12004C, 12AC37, 1233BA, 123487, 1200AA, 121004, 120042, 12AB71, 12D68A, 1200A2.

Peter

Anmer

Thanks Peter.

The SBS-3 is decoding more messages and I was wondering if the vdata alidation wasn't as good.

Looks like it's not SBS-3 related.
Here to Help.