Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 22

Thread: Can anyone help decode these messages?

  1. #11
    Passenger
    Join Date
    Feb 2016
    Posts
    4
    Quote Originally Posted by sysrun View Post
    So, ADS decoding is done - also the Airbus FMS system. Currently trying to make sense of CPDLC - But the ASN.1 decoding is not that easy.
    If you can find a copy of "RTCA DO-219" that document should help you out with CPDLC.

  2. #12
    Passenger
    Join Date
    Apr 2016
    Posts
    4
    Quote Originally Posted by ausmez View Post
    If you can find a copy of "RTCA DO-219" that document should help you out with CPDLC.
    Yeah, looking for it - hard to get...

  3. #13
    Passenger
    Join Date
    Apr 2016
    Posts
    4
    Ok, I managed to write a parser for CPDLC. Not so complicated after I got used to the ASN.1 encoding. I now have decoders for the whole CPDLC chain. Looking forward to get some more logs

    Sent from my SM-N910G using Tapatalk

  4. #14
    Passenger
    Join Date
    Jun 2016
    Posts
    1
    Hello sysrun
    Great to hear that you've managed to create a full prser for CPDLC.
    Is this something you consider making available? Is there any chance to get a copy of this?

  5. #15
    Passenger
    Join Date
    Sep 2017
    Posts
    4
    Hello Sysrun do not know if you are still active on the forum, but am very interested in decoding the cpdlc format , could you share your software on cpdlc as decribed above , sincerely appreciated , Bart Netherlands

  6. #16
    Passenger
    Join Date
    Jun 2015
    Posts
    4
    Just a heads-up for all potentially interested - FANS-1/A CPDLC messages (ie all these which have a type of CR1, CC1, DR1 or AT1) received over VDL mode 2 can be decoded with dumpvdl2 (google: "dumpvdl2 github" to find it, as I am not yet allowed to post links on this forum). Latest version (1.3.1) adds a small utility named decpdlc which can be used for manual decoding of FANS-1/A CPDLC messages received over different media - like plain old ACARS, HFDL or Inmarsat Aero. So if you have any FANS-1/A logs collected with other programs (PC-HFDL, acarsdec, Jaero, etc) you can decode these messages with decpdlc, by supplying their contents on command line or from a file. Search for 'decpdlc' in README.md for more details.

    I plan to separate FANS decoder out from dumpvdl2 codebase into a separate library, so that developers of other software projects could add FANS decoding feature with minimal fuss.

  7. #17
    Passenger
    Join Date
    Sep 2017
    Posts
    4
    Quote Originally Posted by szpajder View Post
    Just a heads-up for all potentially interested - FANS-1/A CPDLC messages (ie all these which have a type of CR1, CC1, DR1 or AT1) received over VDL mode 2 can be decoded with dumpvdl2 (google: "dumpvdl2 github" to find it, as I am not yet allowed to post links on this forum). Latest version (1.3.1) adds a small utility named decpdlc which can be used for manual decoding of FANS-1/A CPDLC messages received over different media - like plain old ACARS, HFDL or Inmarsat Aero. So if you have any FANS-1/A logs collected with other programs (PC-HFDL, acarsdec, Jaero, etc) you can decode these messages with decpdlc, by supplying their contents on command line or from a file. Search for 'decpdlc' in README.md for more details.

    I plan to separate FANS decoder out from dumpvdl2 codebase into a separate library, so that developers of other software projects could add FANS decoding feature with minimal fuss.
    Thanks very much for that effort , really appreciated and will work the manual way for now !
    Good luck with the development !

    regrds

    Bart

  8. #18
    Passenger
    Join Date
    Jun 2015
    Posts
    4
    A couple of examples of ATC uplink messages grabbed from Alphasat 24E L-band 10500 bps channels:

    Code:
    u       /SMACAYA.AT1.A6-EQCE4A4845914C9625C241A5362C4C9640E4B00E8C3
    FANS-1/A CPDLC Message:
    CPDLC Uplink Message:
     Header:
      Msg ID: 9
      Msg Ref: 18
      Timestamp: 08:17:25
     Message data:
      CLIMB TO AND MAINTAIN [altitude]
       Flight level: 330
      CROSS [position] AT [altitude]
       Fix: ARMED
       Flight level: 330
      REPORT LEVEL [altitude]
       Flight level: 330
    
    u       /PIKCPYA.AT1.G-CKNZ22A172DDD11C62C9A738322A003CCF
    FANS-1/A CPDLC Message:
    CPDLC Uplink Message:
     Header:
      Msg ID: 5
      Timestamp: 08:23:11
     Message data:
      AT [time] CONTACT [icaounitname] [frequency]
       Time: 08:35
       Facility Name: EISN
       Facility function: center
       VHF: 135.600 MHz
    
    u       - #MD/AA PIKCPYA.AT1.G-BNLY20A1F92A526A48934D049A6820CE4106AD49F360D48B1104D8B4E9C18F150549E821CF9D1A4D29A821D089321A0873E754830EA20AF26A48414E4419D5E4C396821C59D522D2FE32
    FANS-1/A CPDLC Message:
    CPDLC Uplink Message:
     Header:
      Msg ID: 1
      Timestamp: 08:31:36
     Message data:
      [freetext]
       THIS IS AN AUTOMATED MESSAGE TO CONFIRM CPDLC CONTACT WITH SHANWICK CENTER
    
    u       /SNNCPXA.AT1.G-CKNZA0A2112A41A752A6DD8316C3D98A00F818
    FANS-1/A CPDLC Message:
    CPDLC Uplink Message:
     Header:
      Msg ID: 1
      Timestamp: 08:33:04
     Message data:
      [freetext]
       NRS7016
      SQUAWK [beaconcode]
       Code: 1424
    
    u       /REKCAYA.AT1.TC-LJD24A3749D9A08008C29F127F54F28C3BD
    FANS-1/A CPDLC Message:
    CPDLC Uplink Message:
     Header:
      Msg ID: 9
      Timestamp: 08:55:18
     Message data:
      AT [position] CONTACT [icaounitname] [frequency]
       Latitude:   65 deg north
       Longitude: 000 deg east
       Facility Name: BODO
       Facility function: control
       VHF: 127.725 MHz
    
    u       - #MD/AA MSTEC7X.AT1.D-ABTLA223A3EA41624C90D1B351284A5066CF849699
    FANS-1/A CPDLC Message:
    CPDLC Uplink Message:
     Header:
      Msg ID: 4
      Timestamp: 08:58:15
     Message data:
      [freetext]
       DLH465
      PROCEED DIRECT TO [position]
       Fix: RAMOB

  9. #19
    Passenger
    Join Date
    Sep 2017
    Posts
    4
    Quote Originally Posted by szpajder View Post
    A couple of examples of ATC uplink messages grabbed from Alphasat 24E L-band 10500 bps channels:

    Code:
    u       /SMACAYA.AT1.A6-EQCE4A4845914C9625C241A5362C4C9640E4B00E8C3
    FANS-1/A CPDLC Message:
    CPDLC Uplink Message:
     Header:
      Msg ID: 9
      Msg Ref: 18
      Timestamp: 08:17:25
     Message data:
      CLIMB TO AND MAINTAIN [altitude]
       Flight level: 330
      CROSS [position] AT [altitude]
       Fix: ARMED
       Flight level: 330
      REPORT LEVEL [altitude]
       Flight level: 330
    
    u       /PIKCPYA.AT1.G-CKNZ22A172DDD11C62C9A738322A003CCF
    FANS-1/A CPDLC Message:
    CPDLC Uplink Message:
     Header:
      Msg ID: 5
      Timestamp: 08:23:11
     Message data:
      AT [time] CONTACT [icaounitname] [frequency]
       Time: 08:35
       Facility Name: EISN
       Facility function: center
       VHF: 135.600 MHz
    
    u       - #MD/AA PIKCPYA.AT1.G-BNLY20A1F92A526A48934D049A6820CE4106AD49F360D48B1104D8B4E9C18F150549E821CF9D1A4D29A821D089321A0873E754830EA20AF26A48414E4419D5E4C396821C59D522D2FE32
    FANS-1/A CPDLC Message:
    CPDLC Uplink Message:
     Header:
      Msg ID: 1
      Timestamp: 08:31:36
     Message data:
      [freetext]
       THIS IS AN AUTOMATED MESSAGE TO CONFIRM CPDLC CONTACT WITH SHANWICK CENTER
    
    u       /SNNCPXA.AT1.G-CKNZA0A2112A41A752A6DD8316C3D98A00F818
    FANS-1/A CPDLC Message:
    CPDLC Uplink Message:
     Header:
      Msg ID: 1
      Timestamp: 08:33:04
     Message data:
      [freetext]
       NRS7016
      SQUAWK [beaconcode]
       Code: 1424
    
    u       /REKCAYA.AT1.TC-LJD24A3749D9A08008C29F127F54F28C3BD
    FANS-1/A CPDLC Message:
    CPDLC Uplink Message:
     Header:
      Msg ID: 9
      Timestamp: 08:55:18
     Message data:
      AT [position] CONTACT [icaounitname] [frequency]
       Latitude:   65 deg north
       Longitude: 000 deg east
       Facility Name: BODO
       Facility function: control
       VHF: 127.725 MHz
    
    u       - #MD/AA MSTEC7X.AT1.D-ABTLA223A3EA41624C90D1B351284A5066CF849699
    FANS-1/A CPDLC Message:
    CPDLC Uplink Message:
     Header:
      Msg ID: 4
      Timestamp: 08:58:15
     Message data:
      [freetext]
       DLH465
      PROCEED DIRECT TO [position]
       Fix: RAMOB
    that is more than great ! I a, not completely sure how to get this sorted , but trying to get it working.

  10. #20
    Passenger
    Join Date
    Jun 2015
    Posts
    4
    If you have some FANS logs at hand, then you don't need to read about, compile nor use dumpvdl2. Just get the sources, type "make decpdlc" and in a few minutes you should have a decpdlc binary ready in the current directory.

    Then type, for example:

    Code:
    ./decpdlc u /SMACAYA.AT1.A6-EQCE4A4845914C9625C241A5362C4C9640E4B00E8C3
    and it will spit out the decoded message.

    The first parameter "u" indicates that the following string should be decoded as an uplink message - so you have to know in which direction it has been sent (ground to aircraft or vice versa). Usually it should be pretty straightforward to figure this out from the ACARS log. Or just try "u" and then "d" blindly - it should work this way or another

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •