DEVELOPMENT ISSUE #4,859 - PMDG QOTSII not pushing A/P data throw ACARS. |
Reported by |
Josh Burr (DVA10082)
on 02/02/2017 22:40 ET |
Assigned To |
Luke Kolin (DVA043) |
Issue Status |
Fixed on 03/08/2018 10:31 ET |
Issue Priority |
Medium |
Airlines |
Air France Virtual, Delta Virtual Airlines |
Security |
Public |
Area |
ACARS |
Issue Type |
Enhancement |
Target Version |
2.2 |
Issue Description |
Aside from that, she performed very well and would be cleared for use if it actually passed auto-pilot use information through ACARS for grading. Vince pointed out that the 737 .ini file for PMDG needed to be changed as seen here: https://www.deltava.org/library/b737%20modifying%20pmdg%20ngx%20configuration%20file.pdf
Vince also flew a flight, after following these guidelines for the 747, and filed this PIREP, showing no bubbles with autopilot usage passed on through ACARS. PIREP found here: https://www.deltava.org/pirep.do?id=0x136af6
My PIREP can be found here, same thing, no A/P data (Even though I flew most of the flight by hand, there should still be some white bubbles above FL250: https://www.deltava.org/pirep.do?id=0x136bc5
So question; is there anything we can do to ensure that auto-pilot information is passed through ACARS for grading on check-rides? anything the tech team here might know of? I'm at a loss and have put a hold on clearing the airplane until we can verify that there is either no way at all to present A/P info, or verify that we can send A/P data. Either way, the forum post has been updated here: https://www.deltava.org/thread.do?id=0x20580
See my post at the bottom of that thread. |
25 ISSUE COMMENTS |
Andrew Vane (DVA2887)
02/02/2017 22:59 ET |
Converted Help Desk Issue at http://www.deltava.org/hdissue.do?id=0x2534 |
Luke Kolin (DVA043)
02/03/2017 11:02 ET |
This is almost certainly because FSUIPC does not have integration with the latest PMDG747. I'll reach out to Pete Dowson later today to see if we can get that started.
For ACARS to detect the PMDG 747v2, I'll need to know the name of the aircraft folders (for all variants) as well as the name of the .AIR files. That's really the only thing I need to do at the beginning; from there it's up to Pete to do the integration work and then I just read the offsets. |
Luke Kolin (DVA043)
02/03/2017 14:45 ET |
Does the PMDG 744v2 include any SDK in the install? I'll need that. |
Josh Burr (DVA10082)
02/03/2017 17:58 ET |
-Aircraft folder names (Air file names inside folder)
-PMDG 747-400 (B747-400_GE.air, B747-400_PW.air, B747-400_RR.air)
-PMDG 747-400BCF (B747-400BCF_GE.air, B747-400BCF_PW.air, B747-400BCF_RR.air)
-PMDG 747-400D (B747-400D_GE.air)
-PMDG 747-400ER (B747-400ER_GE.air)
-PMDG 747-400ERF (B747-400ERF_GE.air, B747-400ERF_PW.air)
-PMDG 747-400F (B747-400.air, B747-400F_GE.air, B747-400F_PW.air, B747-400F_RR.air)
-PMDG 747-400M (B747-400M_GE.air, B747-400M_PW.air)
There is an SDK folder located at Computer->Drive->Program Files (x86)->Lockheed Martin->Prepar3D v3->PMDG->PMDG 747 QOTS II->SDK
Would you like an email with the contents of that file attached? |
Luke Kolin (DVA043)
02/04/2017 10:41 ET |
Please send me the contents of the SDK folder.
I should have a beta build "soon"; the question is going to be determining whether we are using v1 or v2. |
Josh Burr (DVA10082)
02/04/2017 20:42 ET |
Sent to you in an email. |
Vincenzo Musumeci (DVA3794)
02/08/2017 08:52 ET |
The goal is to use v2, cause I don't think anyone is using v1 |
Luke Kolin (DVA043)
02/08/2017 12:44 ET |
I don't want to break v1. And fwiw, *I* am still using v1. |
Vincenzo Musumeci (DVA3794)
02/08/2017 20:46 ET |
Good to know.......in the meanwhile we have 4 CRs sitting in the queue with V2..... |
Josh Burr (DVA10082)
02/08/2017 21:11 ET |
So Luke, are we still waiting on Pete, or where do we stand on this? |
Vincenzo Musumeci (DVA3794)
02/09/2017 05:06 ET |
Pete was out yesterday with 4.962 and seems that there is not an integration for PMDG V2 |
Luke Kolin (DVA043)
02/17/2017 11:42 ET |
Please switch to the beta channel; 119b2 includes preliminary PMDG support. It should upgrade to FSUIPC 4.962d. |
Vincenzo Musumeci (DVA3794)
02/20/2017 10:55 ET |
I did switch to the beta channel but it is not clear to me how can switch to a version that is not out yet.
Looking in the Fsuipc download link the latest version is 4.962a |
Luke Kolin (DVA043)
02/21/2017 10:21 ET |
When you restart ACARS, you will be prompted to download the new beta if one is available. |
Luke Kolin (DVA043)
10/15/2017 18:31 ET |
Reopening. Does anyone on this thread have FSInterrogate that comes with FSUIPC? I need someone to check a specific offset. |
Craig Hutchinson (DVA13128)
01/21/2018 17:22 ET |
I just flew a flight with FSUIPC v 5.122, PMDG QOTS II for P3Dv4 v3.00.8466, and ACARS 3.2 (Build 123) on the BETA channel (PIREP: https://www.deltava.org/pirep.do?id=0x147d48) It looks like the A/T info is passing along, but the A/P mode is not. Additionally, the onboard fuel as listed in the Flight Progress session drops out often and its value is replaced by a large negative number, which I think is -2^31. I've attached my ACARS log file; the flight itself runs from about 19:00Z until 21:45Z.
I'd be happy to help troubleshoot however is needed. Thank you! |
Luke Kolin (DVA043)
02/03/2018 10:30 ET |
Build 124 Beta 2 has some additional debug code - could you please switch to the beta track and test. Please ensure that you have a flight number inputted into the FMC prior to connecting ACARS. |
Craig Hutchinson (DVA13128)
02/03/2018 21:44 ET |
I'm running ACARS Beta 124 Beta 2 and will try a test flight on Sunday the 4th. Assuming that you mean the FLT NO field on the RTE page, I'll ensure I've populated that prior to starting the ACARS app. I'll post a link to the PIREP and upload my acars.log file here as well. |
Craig Hutchinson (DVA13128)
02/04/2018 10:32 ET |
I just submitted a PIREP (https://www.deltava.org/pirep.do?id=0x14877e) using FSUIPC v 5.122a, PMDG QOTS II for P3Dv4 3.00.8466 and ACARS 3.2 (Build 124 Beta 2). ACARS did pick up the flight number from the FMC (see attached log). Otherwise, ACARS is showing similar onboard fuel detecting issues as I saw on 21 January as well as not obviously capturing A/P. A/T field shows "MACH" when aircraft A/T is armed, even prior to engine start and regardless of actual A/T mode. A/T field shows blank when cockpit A/T switch to OFF. The follow up comment will attach a timeline of events, A/T & A/P modes, and FMA readings. |
Craig Hutchinson (DVA13128)
02/04/2018 10:41 ET |
Manual timeline for https://www.deltava.org/pirep.do?id=0x14877e that captures significant events related to ACARS, autopilot, auto throttle usage, flight mode annunciations, and periodic fuel states.
I'm happy to continue troubleshooting as needed. Thank you, Craig |
Luke Kolin (DVA043)
02/04/2018 12:03 ET |
I *think* 124 beta 3 (now available) may resolve things. Your callsign is correct, so I think pete's documentation matches reality. I realize I was tweaking some offsets values that I no longer need to, so give this latest version a whirl. I would also check to see if the pax/fuel loading works - PMDG aircraft should have first-class support for this. |
Luke Kolin (DVA043)
02/04/2018 13:05 ET |
Bad flap positions on the PMDG 744v2 are expected. Please do me a favor and type .pitch in the ACARS console for each flap position. It will report what SimConnect is reporting back to ACARS; I can use that to create a custom mapping. That needs to happen for pretty much every payware aircraft. |
Craig Hutchinson (DVA13128)
02/05/2018 02:27 ET |
Flew flight with 124 beta 3 and had consistent accurate fuel state capture throughout flight. Tried pax/fuel loading but I'm not very familiar with ACARS procedures so accept data with skepticism. According to FMC, ZFW = 519.4 with 35+47+272=356 pax at 84.4% load factor; ACARS had 519591 lb ZFW, 83.6% and 373 pax. Adjusted ZFW in ACARS to 519391 and FMC ZFW changed (forgot to record value but it was a few 1000' off ACARS). Did flap test from 05:36:30Z-05:39:50Z; results: Flap 0 = 0, Flap 1 = 4, Flap 5= 19, Flap 10=21, Flap 20=25, Flap 25=27, and Flap 30=30. A/T and A/P work as before: if A/T switch in ARM, ACARS captures as "MACH". ACARS does not capture "A/P" mode. Log file attached. |
Craig Hutchinson (DVA13128)
02/05/2018 02:28 ET |
Pirep for test flight above at: https://www.deltava.org/pirep.do?id=0x148832 |
Craig Hutchinson (DVA13128)
02/10/2018 08:44 ET |
I can confirm in 124 Beta 4 that the flaps are mapped properly: https://www.deltava.org/pirep.do?id=0x148b85 |