ADS-C TOOL TO USE DATA FROM HOPPIE

[Koen Meier]

Hi all,
 

Hoppie has the ability to send out a position report via ADS-C. the report is as follows:
REPORT SHT8H 091948 54.87663 -2.89598 27765 334 434 259/31 -39

The contents of this report: station reporting; time; latitude; longitude; altitude; two-speed values; Wind direction/speed and temperature. However, only the first 4 and the last two data entries are useful and these match the basic group and meteorological group.

Now according to the ICAO GOLD document. We have the following available to us:
Periodic based report
Report = <basic group>& any other group

Event based report with the following events
Waypoint change event (WCE)
Report = <Basic group>&<predicted route group>
Level range deviation event (LRDE)
Report = <Basic group>
Lateral deviation event (LDE)
Report = <Basic group>
Vertical rate change event (VRE).
Report = <Basic group>&<earth reference group>

Demand report
Periodic request but immediately
Report = <basic group>
*Note only 1 contract type but the event-based one can have multiple events included

These are the different groups:


Below i have an example of oceanic use with the WCE of the event contract of ADS-C.
From EGGX
To KLM641
Event contract
Waypoint Change Event at RESNO
Waypoint Change Event at 5620N
Waypoint Change Event at 5730N
Waypoint Change Event at 5740N
Waypoint Change Event at 5650N
Waypoint Change Event at JANJO
Report <Basic group>&<predicted route group>
Contract received
Report KLM641; time; N5500.0; W01500.0; 32000 & N5600.0; W02000.0; TIME; 32000 & N5700.0; W03000.0; 32000
Report KLM641; time; N5600.0; W02000.0; 32000 & N5700.0; W03000.0; TIME; 32000 & N5700.0; W04000.0; 32000
Report KLM641; time; N5700.0; W03000.0; 32000 & N5700.0; W04000.0; TIME; 32000 & N5600.0; W05000.0; 32000
Report KLM641; time; N5700.0; W04000.0; 32000 & N5600.0; W05000.0; TIME; 32000 & N5402.0; W05700.0; 32000
Report KLM641; time; N5600.0; W05000.0; 32000 & N5402.0; W05700.0; TIME; 32000 & N4722.4; W06718.2; 32000
Report KLM641; time; N5402.0; W05700.0; 32000 & N4722.4; W06718.2; TIME; 32000 & N4325.5; W07036.8; 32000
Contract ended

RESNO = N5500.0; W01500.0
5620N = N5600.0; W02000.0
5730N = N5700.0; W03000.0
5740N = N5700.0; W04000.0
5650N = N5600.0; W05000.0
JANJO = N5402.0; W05700.0
TAFFY = N4722.4; W06718.2
ENE = N4325.5; W07036.8

Now i am looking at a way that we can use the Hoppie ads-c data in for example euroscope to simulate this system with regards to oceanic ops mainly. I am aware that topsky has Hoppie cpdlc integration which would allow the logon id and station id to be used. Of course, Hoppie also has to be changed to support more than just the periodic contract and there i think some problems lie that are harder to solve. For example, the earth reference group has a true track value and the air reference group has a true heading value. I am not sure if this data can be accessed from the aircraft like the fslabs that currently support it and any user of Hoppie's application. And i am aware that euroscope offers the CPosition class which can store the lat and long values.

Does someone have any directions on where to look next?

kind regards,

Koen Meier

[Ross Carlson]

Just now, Koen Meier 1288732 said:

For example, the earth reference group has a true track value and the air reference group has a true heading value. I am not sure if this data can be accessed from the aircraft like the fslabs that currently support it and any user of hoppie's application.

SimConnect does provide both true and magnetic heading. It also provides GPS true and magnetic track. I have never used the GPS track variables before, so it may be that they are not available or correctly populated in some aircraft, but I imagine it would be a simple change for the aircraft author.

[Koen Meier]

The simconnect variables are pretty useful. One limitation i spotted is that the GPS can only report back the next waypoint and nothing after that. For the rest, the GPS variables are good to know.

[Bernardo Reis]

We tought we could deploy fake mode-S radars in the airspace we want to cover and tell Euroscope that S-mode XPDRs are for example just /J.

This way Euroscope would only show people with /J equipment suffix, correct?