It's the Ant's Drifter. Tail numbers are 25-255, 25-312 and so forth. PF3 doesn't have an "ultralight" call-sign to chose from, so it's numbers (or NATO alphabet) only.

14 minutes ago, d.tsakiris said:

It's the Ant's Drifter. Tail numbers are 25-255, 25-312 and so forth. PF3 doesn't have an "ultralight" call-sign to chose from, so it's numbers (or NATO alphabet) only.

That's the problem.

MCE tries to simulate real world ATC.

Depending on the aircraft and tail registration it detects, call sign can be...

For GA aircraft ( a specific speech grammar tuned for GA callsigns is loaded), and expected callsign is one of these 3

aircraft_type + full_tail_registration

full_tail_registration only.

aircraftTtype + last 3 digits in tail registration.

Let's assume youy're flying a Piper with reg N23MWD. Any of these are acceptavle call signs

Piper November two Three Mike Whiskey Delta

Piper Mike Whiskey Delta

Since only aircraft types expected in PF3 are allowed, by default, anything else is treated like an airliner, and you have to provide an airline name + Flight number

 

Edited April 5, 20188 yr by FS++

2 hours ago, d.tsakiris said:

Announcing pattern turns is hard.

Does that mean that you sometimes succeed with the announcing of the pattern turns? I never did.

My phrases (e.g. "Tower, <callsign> is turning left base to land runway 1") is recognized properly by the speech engine and shows up in the red text, but the appropriate PF3-hotkey is never sent, so Tower never acknowledges that by "report turning final".

As a workaround I created voxkey commands "turning downwind / base / final" with the appropriate hotkeys and that works fine but of course without my callsign and without pressing the PTT-button.

I reported that a long time ago and I am sure it is somewhere on their list. ;-)

 

53 minutes ago, d.tsakiris said:

"ultralight"

I don't think these type of aircraft require radio equipment or need to get in touch with ATC.

You would need a battery to power the radio.

11 hours ago, FS++ said:

Depending on the aircraft and tail registration it detects, call sign can be...

For GA aircraft ( a specific speech grammar tuned for GA callsigns is loaded), and expected callsign is one of these 3

aircraft_type + full_tail_registration

full_tail_registration only.

aircraftTtype + last 3 digits in tail registration.

Let's assume youy're flying a Piper with reg N23MWD. Any of these are acceptavle call signs

Piper November two Three Mike Whiskey Delta

Piper Mike Whiskey Delta

Since only aircraft types expected in PF3 are allowed, by default, anything else is treated like an airliner, and you have to provide an airline name + Flight number

As far as I know, at least in Germany, the call-sign "November 2 3 Mike Whiskey Delta" is also allowed, and I try to use that accordingly. I guess the Drifter has an unusual registration.

11 hours ago, RALF9636 said:

Does that mean that you sometimes succeed with the announcing of the pattern turns? I never did.

My phrases (e.g. "Tower, <callsign> is turning left base to land runway 1") is recognized properly by the speech engine and shows up in the red text, but the appropriate PF3-hotkey is never sent, so Tower never acknowledges that by "report turning final".

I'm not sure, will try to pay attention the next time.

11 hours ago, FS++ said:

I don't think these type of aircraft require radio equipment or need to get in touch with ATC.

You would need a battery to power the radio.

Don't know about requirements in the real world, but the Ant's has a hand-held device mounted in the cockpit.

5 hours ago, d.tsakiris said:

As far as I know, at least in Germany, the call-sign "November 2 3 Mike Whiskey Delta" is also allowed, and I try to use that accordingly. I guess the Drifter has an unusual registration.

I'm not sure, will try to pay attention the next time.

Don't know about requirements in the real world, but the Ant's has a hand-held device mounted in the cockpit.

You can of course use a German registered aircraft (they start with "D" something like "D25255".

The important bit, is that unless the aircraft type is one of the following, MCE would treat it as an airliner.

Cessna, Challenger,Cherokee, Citation, Fairchild, Falcon, Gulfstream, King Air, Learjet, Mooney, Pilatus, Piper, Baron, Beech, Bonanza, aztec, commander, 

katana, Lancair, Galaxy, Phenom

 

 

Roger. How does that then affect speech recognition?

4 hours ago, d.tsakiris said:

Roger. How does that then affect speech recognition?

It does matter, because depending on whether it sees it as an airliner, in which case it would load the ATC speech grammar "vPFEAtc.cfg".

That grammar is optimized to expect call-signs that go like this "Airline_name + up_to_4_digits_flight_nuimber + <one single NATO letter><heavy> (words between brackets are optional)

Examples

Speedbird 143 heavy

Britannia 4056 Alpha

Lufthansa six heavy

KLM five six seven

 

If you're flying GA and try to use a typical GA callsign with the wrong grammar loaded, you could end-up with incomprehensible recognition, as the speech engine will struggle to match what you said to what is expected in the speech grammar submitted by MCE.

In Contrast GA PF3 ATC grammar "vGaPFEAtc.cfg" is optimized to expect call-signs that obey one of these rules

aircraft_type (any listed above) + full_tail_registration

OR

full_tail_registration_only

 

OR

aircraft_type + last 3 digits_or_letters_in_tail_registration

 

 

Get the patch for PF3 MCE integration from this link

Manually replace files as per folder structure

Thanks Gerald. Going to do a lot of VFR / GA flights in the near future, so I hope I will be able to give good feedback!

Oh...any pointers as to what I should pay attention to? What was changed?

1 hour ago, d.tsakiris said:

Oh...any pointers as to what I should pay attention to? What was changed?

It's mostly to address the little imperfections listed at the beginning of this same thread. No major changes

 

On 05/04/2018 at 9:14 PM, RALF9636 said:

Does that mean that you sometimes succeed with the announcing of the pattern turns? I never did.

My phrases (e.g. "Tower, <callsign> is turning left base to land runway 1") is recognized properly by the speech engine and shows up in the red text, but the appropriate PF3-hotkey is never sent, so Tower never acknowledges that by "report turning final".

As a workaround I created voxkey commands "turning downwind / base / final" with the appropriate hotkeys and that works fine but of course without my callsign and without pressing the PTT-button.

I reported that a long time ago and I am sure it is somewhere on their list. ;-)

 

The announcing of the pattern turns does not work for me too, I have no answer from the tower ! To get an answer, I have to type the corresponding key....

Please Gerald, is possible to fix it ?

Thank you and Regards,

On ‎09‎/‎04‎/‎2018 at 1:34 AM, DrumsArt said:

The announcing of the pattern turns does not work for me too, I have no answer from the tower ! To get an answer, I have to type the corresponding key....

Please Gerald, is possible to fix it ?

Thank you and Regards,

OK, will be looked at sometime next week.

Just a suggestion: Maybe, if the call-sign consists of alphanumericals only, MCE could automatically consider it as GA? There are a lot of GA and UL manufacturers out there, can't expect the ATC program to know them all.

Is there a way to tell which grammer configuration MCE is using?

 

28 minutes ago, FS++ said:

OK, will be looked at sometime next week.

That's great, thanks. I just remembered I also struggle a lot to get FSS to open or close my flight plan.