airtraffic

Author Topic: US domestic enroute CPDLC use started this week  (Read 2522 times)

Offline JetScan1

  • Hero Member
  • *****
  • Posts: 917
US domestic enroute CPDLC use started this week
« on: June 24, 2018, 02:08:48 AM »
(from a recent press release)

"U.S. Domestic En Route CPDLC Validation Starting This Week

June 20, 2018

The Federal Aviation Administration (FAA) begins functional validation of the en route Controller Pilot Data Link Communications (CPDLC) system in domestic U.S. airspace this week, starting with targeted flights in Indianapolis Center (ZID ARTCC).

CPDLC allows air traffic controllers to send data link messages to pilots in domestic en route airspace, with services including climbs, descents, reroutes, and handoffs between ATC sectors. Airlines participating in CPDLC should be training flight crews who are flying on equipped aircraft in anticipation of the nationwide deployment over the next year and a half.

During the initial functional validation phase, a small number of flights will be identified by the FAA for possible participation in CPDLC functional validation. Many of the carriers have stated that the crews for these flights will be check airmen, but some carriers may use line pilots with experience using CPDLC in other airspace areas. In all cases, the crews will be briefed beforehand on the specific procedures to be followed during this initial functional validation.

FAA and airlines plan to expand usage of CPDLC later this summer in the Indianapolis, Kansas City, and Memphis Centers. There will also be broader participation of line crews."

JS



Offline szpajder

  • Newbie
  • *
  • Posts: 42
Re: US domestic enroute CPDLC use started this week
« Reply #1 on: June 24, 2018, 03:44:35 AM »
My guess is that they will be using VHF Data Link mode 2 (VDL-2) to carry CPDLC traffic over land.

If there's anyone interested in this topic in the mentioned area with a spare RTL dongle (or SDRPlay) and a Linux PC (or a Raspberry Pi) it may be worth giving it a try with dumpvdl2 (https://github.com/szpajder/dumpvdl2). The current version of the program can decode CPDLC in both standards being in use today (ie. the new ATN-B1 currently used in EU and the old one FANS-1/A which is encapsulated in ACARS message body). Of course it's best to have a VDL-2 ground station in the reception range, so that ATC clearance messages can be received. Otherwise you will be only seeing responses from aircraft (acknowledgements, WILCOs, UNABLEs and an occasional "REQUEST DIRECT TO <fix>" or "REQUEST CLIMB/DESCEND to FLxxx").

Here are a few examples from EU airspace:

Code: [Select]
[2018-04-11 08:30:33 CEST] [136.975] [-18.4/-48.9 dBFS] [30.5 dB]
2B86F7 (Ground station, On ground) -> 424336 (Aircraft): Command
AVLC type: I sseq: 3 rseq: 0 poll: 0
X.25 Data: grp: 11 chan: 255 sseq: 4 rseq: 5 more: 0
CLNP PDU, compressed header:
COTP Data:
   00 a8 09 83 2c 28 a5 8d 46 7a 10 12 82 54 ab 4e 4c e2 00 59 58 39 00
CPDLC Uplink Message:
 Header:
  Msg ID: 5
  Timestamp: 2018-04-11 06:30:33
  Logical ACK: required
 Message data:
  PROCEED DIRECT TO [position]
   Fix: TUSIN

[2018-04-11 09:51:34 CEST] [136.975] [-28.7/-49.1 dBFS] [20.3 dB]
10920A (Ground station, On ground) -> 4248EF (Aircraft): Command
AVLC type: I sseq: 0 rseq: 7 poll: 0
X.25 Data: grp: 11 chan: 255 sseq: 5 rseq: 4 more: 0
CLNP PDU, compressed header:
COTP Data:
   00 a8 0f a3 30 17 68 65 8d 47 ce 20 1d 62 2d 0a f5 e2 bc 1a 54 ed 41 af 06 0c 38 60 74 bc 82 6e f6 e7 20
CPDLC Uplink Message:
 Header:
  Msg ID: 3
  Timestamp: 2018-04-11 07:51:34
  Logical ACK: required
 Message data:
  CONTACT [unitname] [frequency]
   Unit name: EPWW, WARSZAWAACC, center
   VHF: 134.875 MHz

[2018-04-01 17:53:58 CEST] [136.975] [-26.2/-48.9 dBFS] [22.7 dB]
424368 (Aircraft, Airborne) -> 2A6198 (Ground station): Command
AVLC type: I sseq: 2 rseq: 4 poll: 0
X.25 Data: grp: 11 chan: 255 sseq: 6 rseq: 1 more: 0
CLNP PDU, compressed header:
COTP Data:
   00 a8 08 16 52 d0 cb 18 1f af 21 06 4a a2 11 02 c7 2c 5d 98
CPDLC Downlink Message:
 Header:
  Msg ID: 3
  Timestamp: 2018-04-01 15:53:57
  Logical ACK: required
 Message data:
  REQUEST [level]
   Flight level: 370
  DUE TO AIRCRAFT PERFORMANCE

@dave, will you be accepting data link feeds anytime soon? :)

"LiveATC - from their keyboards to you" ;)

Offline MIAMIATC

  • Hero Member
  • *****
  • Posts: 726
Re: US domestic enroute CPDLC use started this week
« Reply #2 on: June 24, 2018, 11:40:13 AM »
So it Begins !!!   :-(

Offline JetScan1

  • Hero Member
  • *****
  • Posts: 917
Re: US domestic enroute CPDLC use started this week
« Reply #3 on: June 27, 2018, 07:41:49 AM »
Quote
Here are a few examples from EU airspace:

CONTACT [unitname] [frequency]
   Unit name: EPWW, WARSZAWAACC, center
   VHF: 134.875 MHz

Thanks for the post szpajder, this is the first time I've seen VDL-2 decoded. (please check your PM's).

Quote
@dave, will you be accepting data link feeds anytime soon? "LiveATC - from their keyboards to you"

That would be cool, datalink text files displayed live and archived every 30 minutes. Is this feasible Dave ?

Quote
So it Begins !!!

Yep, might not be so bad though if there was a network of ground stations decoding VDL-2 here on LiveATC.

JS




Offline dave

  • Site Founder
  • Administrator
  • Hero Member
  • *****
  • Posts: 4367
    • LiveATC.net
Re: US domestic enroute CPDLC use started this week
« Reply #4 on: June 27, 2018, 06:37:43 PM »
Some experiments are ongoing and deployment progress is being tracked and monitored. Not much else to say at the moment.

Offline JetScan1

  • Hero Member
  • *****
  • Posts: 917
Re: US domestic enroute CPDLC use started this week
« Reply #5 on: August 22, 2018, 11:11:39 AM »
dave,

Quote
Some experiments are ongoing and deployment progress is being tracked and monitored. Not much else to say at the moment.

Any chance you have a spare HF feed to monitor New York HFDL on 6661 for a test ? Transmit it live and people can decode it themselves. I'm noticing that New York has some occasional CPDLC traffic on this frequency. Not a lot, but there is some, counted around 30 CPDLC messages last night on 6661.

Some examples ...

Using PC-HFDL and decoding CPDLC with decpdlc (thanks to szpajder).

/YQME2YA.AT1.N888FD22036ADD670A7D3A93E70602106ABC
FANS-1/A CPDLC Message:
CPDLC Uplink Message:
 Header:
  Msg ID: 4
  Timestamp: 00:54:43
 Message data:
  CONTACT [icaounitname] [frequency]
   Facility Name: BOSTON
   Facility function: center
   VHF: 133.450 MHz

/YYZE2YA.AT1.N511DN2218B91D6B367CEA94A2C19811D1A0EA43
FANS-1/A CPDLC Message:
CPDLC Uplink Message:
 Header:
  Msg ID: 4
  Timestamp: 06:11:36
 Message data:
  CONTACT [icaounitname] [frequency]
   Facility Name: MONTREAL
   Facility function: center
   VHF: 120.725 MHz

/YQXE2YA.AT1.9V-SKN22139C5DCA6529C8833A9449E004A8E27E
FANS-1/A CPDLC Message:
CPDLC Uplink Message:
 Header:
  Msg ID: 4
  Timestamp: 04:57:49
 Message data:
  AT [time] CONTACT [icaounitname] [frequency]
   Time: 05:12
   Facility Name: SHANRDO
   Facility function: center
   HF: 3446 kHz

/YULE2YA.AT1.N511DN2098DCAA526A48934D049A6820CE4106AD49F360D48B1104D8B4E9C18F150549E821CF9D1A4D29A821D089321A0873E754830EA20AF26A4841367CEA94A2C198821C59D522D2BF81
FANS-1/A CPDLC Message:
CPDLC Uplink Message:
 Header:
  Msg ID: 1
  Timestamp: 06:13:50
 Message data:
  [freetext]
   THIS IS AN AUTOMATED MESSAGE TO CONFIRM CPDLC CONTACT WITH MONTREAL CENTER

/TGUACYA.AT1.N965AM291AEEC972E426C8
FANS-1/A CPDLC Message:
CPDLC Downlink Message:
 Header:
  Msg ID: 18
  Timestamp: 06:46:59
 Message data:
  LEVEL [altitude]
   Flight level: 400

The last one was an Aeromexico flight working Cenemar off the coast of Costa Rica.

Interesting to see the handoffs in the Toronto, Montreal, Edmonton, Moncton, Gander airspace being sent via HFDL that are all well within VHF range.

Or better yet what are the chances you or someone could setup a live SATCOM datalink feed !?

JS