I have been using FSACARS with x-plane since I joined the VA and it has worked perfectly after I got it set up correctly.
The brake release times and brake set times are correct in the FSACARS report. When I send the report and check my FREP the pushback time is always the time that I started FSACARS not the brake release time from the report. The arrival time is also not the brake set time. The flight hours are correct.
I do not know if this is the appropriate behavior or not since I am new to the VA.
FSACARS time error
Moderator: Michael Blakely
-
- Screenshot Contest Winner x2
- Posts: 74
- Joined: 12-02-2021 11:42 PM
- Position: HUB Manager KJFK
- Rank: Commander
- Hub: KPHX
- AAV Total Hours: 1244.1
- Current Bid: COMPLETED KORD-KDAL
COMPLETED KDAL-KLAX
COMPLETED KLAX-KMDW
COMPLETED KMDW-KDCA
AA11 KDCA-KMEM
AA11 KMEM-KDAL
AA11 KDAL-KELP
AA11 KELP-KSAN
AA400 KSAN-KELP
CHART KELP-KLAX
FSACARS time error
David "Mike" Roark
AAV2163
AAV2163
- Michael Blakely
- Screenshot Contest Winner x7
- Posts: 3795
- Joined: 07-21-2003 01:14 PM
- Position: CEO
- Rank: Commander
- Hub: KDCA
- Residence: San Diego (North County)
- AAV Total Hours: 3485.5
- Previous VA Hours: 0
- Current Bid: COMPLETED KJFK-KDFW
COMPLETED KDFW-KIAD
COMPLETED KIAD-KDFW
AAL2248 KDFW-KSFO
ASA915 KSFO-KSEA
ASA672 KSEA-KDEN
AAL2771 KDEN-KORD
AAL1918 KORD-KPHX
AAL1945 KPHX-KDFW
AAL2437 KDFW-KLAX - Contact:
Re: FSACARS time error
David,
Since this is a new issue, I went ahead and separated your post from the prior thread and updated the subject to provide differentiating details.
Let me go look at the logs and see what I can find out.
Since this is a new issue, I went ahead and separated your post from the prior thread and updated the subject to provide differentiating details.
Let me go look at the logs and see what I can find out.
Mike
Bid Theme: Back in the USA
Bid Theme: Back in the USA
- Michael Blakely
- Screenshot Contest Winner x7
- Posts: 3795
- Joined: 07-21-2003 01:14 PM
- Position: CEO
- Rank: Commander
- Hub: KDCA
- Residence: San Diego (North County)
- AAV Total Hours: 3485.5
- Previous VA Hours: 0
- Current Bid: COMPLETED KJFK-KDFW
COMPLETED KDFW-KIAD
COMPLETED KIAD-KDFW
AAL2248 KDFW-KSFO
ASA915 KSFO-KSEA
ASA672 KSEA-KDEN
AAL2771 KDEN-KORD
AAL1918 KORD-KPHX
AAL1945 KPHX-KDFW
AAL2437 KDFW-KLAX - Contact:
Re: FSACARS time error
Score 1 for David. He has found a bug in the client. I think I can adapt to this in the website software. Here's what I found out...
First - David - Many pilots (me included) start up FSACARS immediately before pushback. This means as soon as FSACARS is configured, they are releasing parking brakes and pushing back. The result is that the first timestamp available to FSACARS is the same as the "Parking Brake Off" timestamp. If you use the procedure you won't have to manually update your FREPs until I get a fix in place.
Now to the details.
The FSACARS client sends a "Flight Start Time" to the website. I use this in the FREP as the departure time. It seems this is actually the FSACARS start-up time, not the parking brake off time. When I analyzed the logs, I saw some pilots don't set the parking brakes prior to flying, so their logs don't even have a parking brake off entry. FSACARS also sends a flight duration. This is the parking brake off to parking brake on duration. However, if the pilot didn't set the parking brake, then it's the liftoff time to parking brake on duration. I add this duration to the "Flight Start Time" (also the Departure Time) to calculate the Arrival Time. If Departure Time matches parking brake off time, this works. But if there is a delay from Departure Time to parking brake off time, it doesn't work.
I think I can fix this by looking for the Parking Break Off timestamp, and using this for departure time, and if it's not there, default to using the "Flight Start Time" that is always reported.
I've already spent a bunch of my Christmas holiday fixing the multiple FSACARS FREP problem, so I think I'll enjoy the rest of my holiday and fix this one in a couple weeks.
First - David - Many pilots (me included) start up FSACARS immediately before pushback. This means as soon as FSACARS is configured, they are releasing parking brakes and pushing back. The result is that the first timestamp available to FSACARS is the same as the "Parking Brake Off" timestamp. If you use the procedure you won't have to manually update your FREPs until I get a fix in place.
Now to the details.
The FSACARS client sends a "Flight Start Time" to the website. I use this in the FREP as the departure time. It seems this is actually the FSACARS start-up time, not the parking brake off time. When I analyzed the logs, I saw some pilots don't set the parking brakes prior to flying, so their logs don't even have a parking brake off entry. FSACARS also sends a flight duration. This is the parking brake off to parking brake on duration. However, if the pilot didn't set the parking brake, then it's the liftoff time to parking brake on duration. I add this duration to the "Flight Start Time" (also the Departure Time) to calculate the Arrival Time. If Departure Time matches parking brake off time, this works. But if there is a delay from Departure Time to parking brake off time, it doesn't work.
I think I can fix this by looking for the Parking Break Off timestamp, and using this for departure time, and if it's not there, default to using the "Flight Start Time" that is always reported.
I've already spent a bunch of my Christmas holiday fixing the multiple FSACARS FREP problem, so I think I'll enjoy the rest of my holiday and fix this one in a couple weeks.
Mike
Bid Theme: Back in the USA
Bid Theme: Back in the USA
-
- Screenshot Contest Winner x2
- Posts: 74
- Joined: 12-02-2021 11:42 PM
- Position: HUB Manager KJFK
- Rank: Commander
- Hub: KPHX
- AAV Total Hours: 1244.1
- Current Bid: COMPLETED KORD-KDAL
COMPLETED KDAL-KLAX
COMPLETED KLAX-KMDW
COMPLETED KMDW-KDCA
AA11 KDCA-KMEM
AA11 KMEM-KDAL
AA11 KDAL-KELP
AA11 KELP-KSAN
AA400 KSAN-KELP
CHART KELP-KLAX
Re: FSACARS time error
I will do as you do Michael, start FSACARS just before pushback. Thanks for looking into this!
David "Mike" Roark
AAV2163
AAV2163