ACARS not completing flight due to values lost  gelöst

Moderatoren: Aircraft-Admins, English-Support, FTW-Development, Airport-Admins

Gesperrt

Topic author
Omarza
Beiträge: 66
Registriert: So 2. Sep 2018, 01:36
Wohnort:
Hat sich bedankt: 8 Mal
Danksagung erhalten: 5 Mal

ACARS not completing flight due to values lost  gelöst

#1

Beitrag von Omarza » Sa 3. Nov 2018, 02:06

He Everyone,

I had this problem before but tonight it struck me twice after 2 flights and thus a good 3-4 hours lost in the process. This is not good as one can not fly comfortably and I don't even want to try a 3rd flight...maybe tomorrow as its late here at the moment.

What happens is:
Engine Start: XACARS works fine The OUT Time gets filled in properly on engine start. Also time go to zero on Block and Flight time sets.
Take Off: OFF time gets inserted properly and flight time now updates, flight fuel etc
Landing: ON Time gets updated properly and flight time stops rolling while Block time still keep going
Engine Shutdown: IN Times updates...displays for a fraction of a second and ALL the OUT, OFF, ON and IN times disappear. NOTE the block time and flight times is still there and correct...BUT without the top 4 times OUT, OFF, ON and IN no PIREP gets posted.
In this image below notice the missing OUT, OFF, ON and IN times
Bild

Now on FTW side...all data was fine (BEFORE ENGINE SHUTDOWN) but after ABOVE happened in XACARS all of a sudden it zero's my miles flown in FTW for that flight. You can see FTW clearly show the A/C in the right place on the map (to where it was tracked during flight) and that the a/c is stationary etc.
Bild


Possible suggestion:
If something like this happens...cant FTW detect the landing as ACARS surlely sent that info through...and after a couple of minutes delay while a/c is stationary activate a complete flight in FTW using the last set of data that was correct sent through from XACARS. To determine the last set of correct data received from XACARS one can use a miles flown check...if it all of a sudden goes from a high number to zero or something like that use the previous ACARS data set received with the more correct info...as this ONLY to my knowledge happens on engine shutdown and 99.99 of the flight was tracked and even displayed properly. Thus in this scenario aicraft reloading in cold/dark etc does not work/trigger engines off...not even trying to take-off and land again as the TOP row times (OUT, OFF, ON. IN) all have been lost.

Omarza
Bild

Benutzeravatar

Teddii
Beiträge: 471
Registriert: So 21. Okt 2018, 12:23
Wohnort: EDHK
Hat sich bedankt: 176 Mal
Danksagung erhalten: 80 Mal

ACARS not completing flight due to values lost

#2

Beitrag von Teddii » Sa 3. Nov 2018, 17:20

Hi there!

There is a logfile in the XACARS plugin folder ... it's pretty chatty, so maybe you can find the cause for XACARS reaction there.
Does it only happens with this plane and did it worked before with this plane?

Cheers,
Markus
:arrow: Im FTWiki findest du Antworten auf Oft gestellte Fragen, Videos und Tutorials und das Piloten-Handbuch.
:arrow:
:arrow: Read about ways to translate the FTWiki pages to your language!


Topic author
Omarza
Beiträge: 66
Registriert: So 2. Sep 2018, 01:36
Wohnort:
Hat sich bedankt: 8 Mal
Danksagung erhalten: 5 Mal

ACARS not completing flight due to values lost

#3

Beitrag von Omarza » Sa 3. Nov 2018, 19:26

Hi Markus,

Thanks for the tip of the log file...I did not know about the log file.

The problem occurs every now and then and with various aircraft. However I would say about 95% of the time it works fine. Yesterday was the first time I had it twice in a row however. Yes all the aircraft it happened with is aircraft that I regularly fly in FTW.

When it happens again I will look in the log file as to what happened and it might shed some light on the problem...thanks again for that tip :)

Otto
Bild

Benutzeravatar

Teddii
Beiträge: 471
Registriert: So 21. Okt 2018, 12:23
Wohnort: EDHK
Hat sich bedankt: 176 Mal
Danksagung erhalten: 80 Mal

ACARS not completing flight due to values lost

#4

Beitrag von Teddii » Sa 3. Nov 2018, 19:50

Please, let us know when you find out something new!
:arrow: Im FTWiki findest du Antworten auf Oft gestellte Fragen, Videos und Tutorials und das Piloten-Handbuch.
:arrow:
:arrow: Read about ways to translate the FTWiki pages to your language!


Topic author
Omarza
Beiträge: 66
Registriert: So 2. Sep 2018, 01:36
Wohnort:
Hat sich bedankt: 8 Mal
Danksagung erhalten: 5 Mal

ACARS not completing flight due to values lost

#5

Beitrag von Omarza » Sa 3. Nov 2018, 20:43

I will do that :)
Bild


Topic author
Omarza
Beiträge: 66
Registriert: So 2. Sep 2018, 01:36
Wohnort:
Hat sich bedankt: 8 Mal
Danksagung erhalten: 5 Mal

ACARS not completing flight due to values lost

#6

Beitrag von Omarza » Sa 10. Nov 2018, 20:32

I am just reporting back on that ACARS problem as I got it today again...as I said it doesn't happen often. This time I looked in the log-file and the following error was present...I tried to copy the relevant part from where the flight was ended...and the lines in bold might be where the problem lies?

EDIT: Interesting to note and it might just be coincidence...its roughly the exact same day and time as when the error occured last...Saturday late evening...

At Sat Nov 10 22:04:11 2018 it said it transmitted successfully...but message just after it that no reply was received from the server. Then just after that it states end flight error (probably trigger due to no reply from server) and its aborting. I hope this data can be of any help :) Its right after that error where the ACARS data of the OUT OFF ON IN fields gets cleared although it still keeps and displays the block time, block fuel, flight time, flight fuel etc...(as in image in my first post)

Sat Nov 10 22:04:07 2018: Message: [cycleOnce called.]
Sat Nov 10 22:04:07 2018: FlightState: [STARTED_IN]
Sat Nov 10 22:04:07 2018: Message: [FlightState::Check called.]
Sat Nov 10 22:04:07 2018: Message: [Checking for flight crashed.]
Sat Nov 10 22:04:07 2018: Message: [Checking for flight sim connection.]
Sat Nov 10 22:04:07 2018: Message: [Checking for paused state.]
Sat Nov 10 22:04:07 2018: Message: [Switching state.]
Sat Nov 10 22:04:07 2018: Message: [Called EngineStopped.]
Sat Nov 10 22:04:07 2018: Message: [Number of Engines: [2]]
Sat Nov 10 22:04:07 2018: Message: [Got FuelFlow.]
Sat Nov 10 22:04:07 2018: Message: [Got EngineRunning.]
Sat Nov 10 22:04:07 2018: Message: [0: Running: [0] FF: [0]]
Sat Nov 10 22:04:07 2018: Message: [1: Running: [0] FF: [0]]
Sat Nov 10 22:04:07 2018: Message: [Engines stopped: [1].]
Sat Nov 10 22:04:07 2018: Message: [In ReportPosition.]
Sat Nov 10 22:04:07 2018: Message: [Shall not report position.]
Sat Nov 10 22:04:07 2018: Message: [Currently: IAS:[0] GS: [0] VSpeed: [0] VSpeed_land:[-292].]
Sat Nov 10 22:04:07 2018: Now looking for State.
Sat Nov 10 22:04:07 2018: Calling fillinCurrentData.
Sat Nov 10 22:04:07 2018: prevouttime: [1541872770]
Sat Nov 10 22:04:07 2018: Going to Display ACARS Message.
Sat Nov 10 22:04:07 2018: Returning ACARS Message.
Sat Nov 10 22:04:07 2018: Display ACARS Message done.
Sat Nov 10 22:04:11 2018: ACARS: [MESSAGE [DATA1=XACARS|2.0&DATA2=MESSAGE&DATA3=1541872285&DATA4=[10/10/2018 20:04Z] +++ ACARS Mode: 2 Aircraft Reg: .FFSTS +++ Msg Label: QD Block ID: 01 Msg No: M136A +++ Flight ID: SWN7188 +++ Message: +++ IN 20:04Z /FOB 13504 /RAW 227553 +++ /POS S33 58.171 E18 35.9094 +++ /ALT 160 +++ /HDG 245 +++ /HDT 270 +++ /IAS 0 +++ /WND 00000 /OAT 14 /TAT 0 +++ +++ ] transmitted successfully.]
Sat Nov 10 22:04:12 2018: ACARS: [No answer from server for MESSAGE [DATA1=XACARS|2.0&DATA2=MESSAGE&DATA3=1541872285&DATA4=[10/10/2018 20:04Z] +++ ACARS Mode: 2 Aircraft Reg: .FFSTS +++ Msg Label: QM Block ID: 01 Msg No: M137A +++ Flight ID: SWN7188 +++ Message: +++ BLOCK TIME 01:54 /FUEL 19500 +++ FLIGHT TIME 01:42 /FUEL 17634 +++ FLIGHT DISTANCE 708 +++ +++ transmission.]
Sat Nov 10 22:04:12 2018: ACARS: [ENDFLIGHT returned error: [Invalid Data1] -- Aborting.]

Sat Nov 10 22:04:12 2018: FlightStatusLoop called.
Sat Nov 10 22:04:12 2018: Message: [cycleOnce called.]
Sat Nov 10 22:04:12 2018: FlightState: [FINAL]
Sat Nov 10 22:04:12 2018: Message: [FlightState::Check called.]
Sat Nov 10 22:04:12 2018: Message: [Transitioning to FINAL state.]
Sat Nov 10 22:04:12 2018: Message: [Checking for paused state.]
Sat Nov 10 22:04:12 2018: Message: [Switching state.]
Sat Nov 10 22:04:12 2018: Message: [Removing ACARS object.]
Sat Nov 10 22:04:12 2018: ACARS: [Stopping ACARS.]
Sat Nov 10 22:04:12 2018: ACARS: [Cancelling PIREP.]
Sat Nov 10 22:04:12 2018: ACARS: [Joining Send Thread.]
Sat Nov 10 22:04:12 2018: ACARS: [Joining Flight Info Thread.]
Sat Nov 10 22:04:12 2018: ACARS: [ACARS stopped.]
Sat Nov 10 22:04:12 2018: Message: [Removing FlightState object.]
Sat Nov 10 22:04:12 2018: Message: [Check FlightState failed]
Sat Nov 10 22:04:12 2018: Now looking for State.
Sat Nov 10 22:04:12 2018: Using getConnectFailed.
Sat Nov 10 22:04:12 2018: GetConnectFailed got us: []
Sat Nov 10 22:04:12 2018: Calling fillinCurrentData.
Sat Nov 10 22:04:12 2018: Going to Display ACARS Message.
Sat Nov 10 22:04:12 2018: Returning ACARS Message.
Sat Nov 10 22:04:12 2018: Display ACARS Message done.
Sat Nov 10 22:04:17 2018: FlightStatusLoop called.
Sat Nov 10 22:04:17 2018: Message: [cycleOnce called.]
Sat Nov 10 22:04:17 2018: Now looking for State.
Sat Nov 10 22:04:17 2018: Using getConnectFailed.
Sat Nov 10 22:04:17 2018: GetConnectFailed got us: []
Sat Nov 10 22:04:17 2018: Calling fillinCurrentData.
Sat Nov 10 22:04:17 2018: Going to Display ACARS Message.
Sat Nov 10 22:04:17 2018: Returning ACARS Message.
Sat Nov 10 22:04:17 2018: Display ACARS Message done.
Sat Nov 10 22:04:22 2018: FlightStatusLoop called.
Sat Nov 10 22:04:22 2018: Message: [cycleOnce called.]
Sat Nov 10 22:04:22 2018: Now looking for State.
Sat Nov 10 22:04:22 2018: Using getConnectFailed.
Bild

Gesperrt

Zurück zu „ACARS“

Wer ist online?

Mitglieder in diesem Forum: 0 Mitglieder und 1 Gast