Announcement

Collapse
No announcement yet.

ICAO code allocation ranges

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • zkarj
    replied
    Two more have appeared:

    5d849c between 2018/01/15 23:26 - 23:30
    44d310 between 2018/01/17 05:44 - 05:48

    Leave a comment:


  • zkarj
    replied
    Thanks, I've added that in. I'm going through now and purging all of the known dodgy codes (quite a few more had shown up since my original post and were similarly out-of-range of any allocations). I'll see if anything new shows up. I noticed that all of them had shown up on only one occasion each, which is certainly possible for ordinary aircraft (especially non-locals) but does lend weight to the spuriousness of them. I also have 260 minutes' observation of 000000 but that seems like it might be a different thing.

    I'll post back here after a while if anything has (or hasn't) cropped up with --fix in operation. Meanwhile, I have a bunch more codes to research in case they're real. We had a Royal Jordanian G650 over the other day – one of only two aircraft I've captured in the 4xxxxx range. It's amazing what comes into this little place on the bottom of the world.

    Leave a comment:


  • MrMac
    replied
    Like I said, you are not doing any CRC correction. Add --fix , and I think that will remove the faulty decodes.

    /M

    Leave a comment:


  • zkarj
    replied
    I've taken out the modeac, but leaving off interactive makes it spew copious amounts of unreadable (due to speed) output, which I suppose I could pipe to /dev/null. but it seems like more work than just the live readout. Running interactive it's got plenty of headroom on the CPU using only about 15% of one core out of four.

    Leave a comment:


  • Oblivian
    replied
    Shouldn't need modeac, and I'm surprised it's going with interactive. That changes the output to screen priority and not data out relay..

    Sent from my XT1092 using Tapatalk

    Leave a comment:


  • zkarj
    replied
    I'm running it with the following command (lat & lon dumbed down for public consumption):

    ./dump1090 --interactive --net --lat -41.000000 --lon 174.000000 --modeac --mlat --write-json /usr/local/var/dump1090-mut-data

    Leave a comment:


  • MrMac
    replied
    Originally posted by zkarj View Post
    Running dump1090 on macOS.

    I have hundreds of verified correct hits over many days, and for those listed I have multiple hits over successive minutes and then they are not seen again. It seems to me (as a developer and IT professional) that the decoder and software are behaving consistently and the bad data, if that's what it is, is being transmitted that way.
    It's very unlikely anything like that is transmitted. Much more likely that it is a repeated 1-bit decoding error that doesn't get corrected or filtered. I have seen it many times when CRC checking gets turned off by mistake, or too aggressive mode is used for signal detection.

    Post your dump config.

    /M

    Leave a comment:


  • zkarj
    replied
    Receiver as pictured. Running dump1090 on macOS.

    I have hundreds of verified correct hits over many days, and for those listed I have multiple hits over successive minutes and then they are not seen again. It seems to me (as a developer and IT professional) that the decoder and software are behaving consistently and the bad data, if that's what it is, is being transmitted that way.

    IMG_0413.jpg

    Leave a comment:


  • MrMac
    replied
    Looks like CRC checking is off. What type of Rx is this?

    /M

    Leave a comment:


  • zkarj
    replied
    I would need to log more info to see what's going on. These are happening when I'm not around so I am relying on my bespoke script to pull logs from the dump1090 json files.

    Leave a comment:


  • Anmer
    replied
    Do these codes have accompanying flight IDs, altitudes, squawks and positions?

    To me they look "spurious" and are probably not being transmitted by any aircraft

    Leave a comment:


  • zkarj
    replied
    It's been giving me good data from the outset. The two unknown codes were collected within the same period. I also have a signficant number of hits on "000000" but that seems to me to be a reasonable expectation if the code is not present (if that's possible) or not decodable. What I cannot understand is the two codes, over many samples, that do not fall into any allocations as far as I am aware.

    Leave a comment:


  • Beware the rush
    replied
    OK glad you got it working in the end.

    Leave a comment:


  • zkarj
    replied
    78.6% by my calculation. I think it's working fine, in general.

    830492 ae060f VH-VGO 7c6b36 ZK-JSH c812e0 ZK-MTA c81ced ZK-MVO c82315 ZK-NES c81a90 ZK-OJS c81e2c ZK-PLS c82272
    9V-SQJ 76ce2a VH-VGQ 7c6b38 ZK-JWH c8208e ZK-MTC c81cef ZK-MVP c8244b ZK-NET c81a91 ZK-OXA c82081 ZK-PLT c822bb
    9V-SRM 76ce4d VH-VGU 7c6b3c ZK-KAL c81a68 ZK-MTI c81ce6 ZK-MVQ c8244c ZK-NEU c81a92 ZK-OXB c82089 ZK-PLX c82350
    9V-SRQ 76ce51 VH-VGY 7c6b40 ZK-KAZ c81d93 ZK-MTL c81ce9 ZK-MYM c820ae ZK-NEW c81ac0 ZK-OXC c820b6 ZK-PLZ c8229e
    N163JM a0fda7 VH-VQC 7c6c92 ZK-KFH c812a2 ZK-MTZ c81e8b ZK-NEA c818c9 ZK-NEZ c81b24 ZK-OXD c820f4 ZK-PVC c80379
    NZ7122 c87f1e VH-VQU 7c6ca4 ZK-LCA c81cfd ZK-MVA c82009 ZK-NEB c818da ZK-NFA c81bb3 ZK-OXE c8210d ZK-PWL c82473
    NZ7124 c87f20 VH-VZP 7c6de3 ZK-LFT c823d0 ZK-MVB c8200a ZK-NEC c818db ZK-NFB c81c9e ZK-OXF c8216e ZK-SAA c81ac5
    VH-BHR 7c061d VH-YIH 7c7aa7 ZK-LFW c81fcc ZK-MVC c8200b ZK-NED c81958 ZK-NFI c81c9f ZK-OXG c821c1 ZK-SAN c81a1b
    VH-SBI 7c5b4c VH-YIL 7c7aab ZK-MCB c8143f ZK-MVD c820ab ZK-NEE c81959 ZK-OAB c81d8e ZK-OXH c821ee ZK-SAW c8221c
    VH-SBW 7c5b5a VH-YIR 7c7ab1 ZK-MCC c81816 ZK-MVE c821ba ZK-NEF c8195a ZK-OJA c8169d ZK-OXI c8221a ZK-SAY c81ab7
    VH-TQD 7c6273 VH-YIT 7c7ab3 ZK-MCJ c81441 ZK-MVF c821f8 ZK-NEG c8195b ZK-OJB c8169e ZK-OXJ c82268 ZK-SKL c81e79
    VH-TQL 7c627b VH-YIU 7c7ab4 ZK-MCO c81463 ZK-MVG c82284 ZK-NEH c8195c ZK-OJD c816bf ZK-OXK c82269 ZK-TRO c8121e
    VH-VFJ 7c6b0d VH-YIV 7c7ab5 ZK-MCP c81464 ZK-MVH c822ec ZK-NEJ c819dc ZK-OJE c816dc ZK-OXL c822e4 ZK-VMF c821c3
    VH-VFL 7c6b0f VH-YIY 7c7ab8 ZK-MCU c81465 ZK-MVI c822ed ZK-NEK c819dd ZK-OJG c81708 ZK-OXM c8234a ZK-XLF c81681
    VH-VFN 7c6b11 ZK-DRN c8036c ZK-MCW c815e3 ZK-MVJ c82336 ZK-NEM c819de ZK-OJI c8178c ZK-PAK c822e9 ZK-YDZ c82298
    VH-VFX 7c6b1b ZK-FDN c81e82 ZK-MCY c8163c ZK-MVK c82335 ZK-NEO c819df ZK-OJK c81845 ZK-PAQ c822ea ZK-ZQE c81dd7
    VH-VGI 7c6b30 ZK-HKV c82205 ZK-MDF c82368 ZK-MVL c82349 ZK-NEP c819e0 ZK-OJN c818fe ZK-PDM c811de ZK-ZQF c81dd5
    VH-VGJ 7c6b31 ZK-IAG c823e2 ZK-MFT c822df ZK-MVM c82379 ZK-NEQ c81a5a ZK-OJQ c81d9d ZK-PJM c81879 ZK-ZQH c81df5
    VH-VGN 7c6b35 ZK-JAK c82441 ZK-MKG c818fd ZK-MVN c8237a ZK-NER c81a5b ZK-OJR c81e27 ZK-PLK c81bce ZK-ZZA c81e5e

    Leave a comment:


  • Beware the rush
    replied
    Given your NZ location, 90% of your hex codes should be in the C80000 block. If you're not getting C8s then you don't have it set up right.

    Leave a comment:

Working...
X