Fatal Error On transmit after changing new agency Frequency

[Julaibi]

Hello Everyone

I am running Prepar3D v4.4 with VoxATC v7.42 and Active Sky P3D4 on Networking.

Everything is updated using fsaerodata and Navigraph softwares with Cycle 1904

i encounters some issue with one Leg of Flight From OMDB to OBBI when i start my flight everything run smooth from push back all the way to descend once the VoxATC switch me to Bahrain Approach with Frequency which is 119.100 i dial it and transmit i got Fatal Error without respond from the agency after i tried to change the Frequency to Bahrain tower and transmit i hear the tower report message Go a head with no further instructions.

After I disabled VoxATC and enable it still Fatal Error.

I flew the opposite Leg from OBBI to OMDB everything runs Smooth from push back to land and taxi to gate without any issue.

after i flew on different Flight plan still the issue exists.

any idea and Help Please could someone help me to fix this issue.

Thanks



Best Regards

[fsaerodata]

Hello,
this type of error on VoxATC are quite hard to troubleshoot since there is almost no log or trace stored on the application VoxATC itself that can lead to the source of the problem, either the app itself or fsAerodata database.
In the past there were some issues related to VoxATC and FSAD, but related to a conflict with airports that changed the ICAO code.
I'll do some tests with a default system, and let you know,

Regards,

[Julaibi]

Hello Sir

Many Thanks

[Julaibi]

Hello Sir

I did investigation today and I noticed that a flight from OMDB to OBBI with FSaerodata updated to Cycle 1940r1 I got that issue VoxATC with Fatal Errors Disable.

And I fly with same Route without FSaerodata everything was running smooth, so I think the problem came from the STAR Procedure at destination and Approach Frequency Bahrain Approach 119.100.

And you can check that issue sir.


Best Regards

[jabloomf1230]

Hello,
this type of error on VoxATC are quite hard to troubleshoot since there is almost no log or trace stored on the application VoxATC itself that can lead to the source of the problem, either the app itself or fsAerodata database.
In the past there were some issues related to VoxATC and FSAD, but related to a conflict with airports that changed the ICAO code.
I'll do some tests with a default system, and let you know,

Regards,

Jose,

I have been trying to figure this error out also:

https://www.avsim.com/forums/topic/5523 ... nt-3990423

The VOXATC message in the error log indicates (within my limited understanding) that a .NET exception occurred while enumerating the OBBI approaches. One interesting thing that you can check is that if one runs Little NavMap and displays the approaches for OBBI with fsaerodata installed, there is a difference between the sim's database ("Do not use Navigraph database") and the "Use Navigraph for all features" options. The difference is that the built-in LMN Navigraph database has the STARs ending lined up with the final approach path to the runway, whereas the fsaerodata Navigraph version does not:



This might be something specific to how LNM displays approaches or it could be a clue.
Jay

[jabloomf1230]

Jose,

Take a look at the OBBI VORDME approaches. They seem a bit odd. It probably only takes one approach to mess up the entire collection.

Jay

[Julaibi]

Hello

That is the error logs shows the problem

IN 12:59 From :bahrain center: sky dubai two five
ASS state set ASSWaitingAfterHandover bahrain approach
at com.intworkings.voxatc.AircraftStripImpl.SetState(AircraftStripState ass)
at com.intworkings.voxatc.AircraftStripImpl.SetToNextATSU()
at com.intworkings.voxatc.ATSO.AddHandoverStrips()
at com.intworkings.voxatc.ATSO.Run()
at com.intworkings.voxatc.TerminalATSO.Run()
at com.intworkings.voxatc.ATSOWorker.ActiveRun()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

IN 12:59 From :bahrain center:
IN 12:59 From :bahrain center: contact
IN 12:59 From :bahrain center: bahrain approach
IN 12:59 From :bahrain center: one one niner point one
IN 12:59 From :bahrain center:
IN 12:59 From :bahrain center: Terminator

Instructor State set to ISTuning
4044218 Prompt Enabled
4044218 Prompt Text set : one one niner point one sky dubai two five
4044218 Ins Text set : Readback instructions/clearance
VADI key pressed event : 57
RSC Key pressed
RSC PTT Key pressed
15:59:54.7123595 Current Position = 26.3643429892289 51.4198708099095 10436.1738366829
VASound Play 0
Recog :radiomessage : one one niner point one sky dubai two five
IN 12:59 From :sky dubai two five: one one niner point one sky dubai two five
OUT 12:59 one one niner point one sky dubai two five
VADI key released event : 57
IN 12:59 From :sky dubai two five: Terminator

OUT 12:59 Terminator

ASS state set ASSHandedOver bahrain center
at com.intworkings.voxatc.AircraftStripImpl.SetState(AircraftStripState ass)
at com.intworkings.voxatc.ASSWaitingResponse.SetSenderCallsign(Callsign scs)
at com.intworkings.voxatc.RadioMessageImpl.Dispatch(RTOperator op)
at com.intworkings.voxatc.ATSO.Run()
at com.intworkings.voxatc.ATSOARTCC.Run()
at com.intworkings.voxatc.ATSOWorker.ActiveRun()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

4050562 Prompt disabled
4050562 Prompt Text set :
Instructor State set to ISTuning
4050593 Ins Text set : Tune to bahrain approach 119.100
4050609 Prompt disabled
4050609 Prompt Text set :
VADI key pressed event : 42
RSC Key pressed
VADI key pressed event : 5
RSC Key pressed
Instructor key code pressed event : 4
Instructor key code handled : 4
VADI key released event : 5
VADI key released event : 42
IN 13:00 From :Not Set: Terminator

IN 4055655 Frequency Change 119.1
Instructor State set to ISTuning
Instructor State set to ISArrival
4055671 Prompt Enabled
4055687 Prompt Text set : bahrain approach sky dubai two five with you leaving one zero thousand three hundred descending six thousand
4055687 Ins Text set : make contact
VADI key pressed event : 42
RSC Key pressed
VADI key pressed event : 5
RSC Key pressed
Instructor key code pressed event : 4
Instructor key code handled : 4
Instructor menu item selected : 4
VADI key released event : 5
VADI key released event : 42
VADI key pressed event : 57
RSC Key pressed
RSC PTT Key pressed
VASound Play 0
16:00:07.7243001 Current Position = 26.3618241632147 51.4013890987107 10300.8815000545
Recog :radiomessage : bahrain approach sky dubai two five with you leaving one zero thousand three hundred descending six thousand
IN 13:00 From :sky dubai two five: bahrain approach sky dubai two five with you leaving one zero thousand three hundred descending six thousand
OUT 13:00 bahrain approach sky dubai two five with you leaving one zero thousand three hundred descending six thousand
VADI key released event : 57
IN 13:00 From :sky dubai two five: Terminator

OUT 13:00 Terminator

ASS state set ASSAppHandover bahrain approach
at com.intworkings.voxatc.AircraftStripImpl.SetState(AircraftStripState ass)
at com.intworkings.voxatc.ASSWaitingAfterHandover.SetSenderCallsign(Callsign scs)
at com.intworkings.voxatc.RadioMessageImpl.Dispatch(RTOperator op)
at com.intworkings.voxatc.ATSO.HandleIncoming()
at com.intworkings.voxatc.ATSO.Run()
at com.intworkings.voxatc.TerminalATSO.Run()
at com.intworkings.voxatc.ATSOWorker.ActiveRun()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

ATSO exception Enumeration already finished. at System.Collections.ArrayList.ArrayListEnumeratorSimple.get_Current()
at com.intworkings.voxatc.ASSAppHandover.SetupVectoredApproachCircleToLand(Runway rwWithApp, Runway rwForWind)
at com.intworkings.voxatc.ASSAppHandover.SetupCircleToLand()
at com.intworkings.voxatc.ASSAppHandover.MessageEnd()
at com.intworkings.voxatc.RadioMessageImpl.Dispatch(RTOperator op)
at com.intworkings.voxatc.ATSO.HandleIncoming()
at com.intworkings.voxatc.ATSO.Run()
at com.intworkings.voxatc.TerminalATSO.Run()
at com.intworkings.voxatc.ATSOWorker.ActiveRun()
4065171 Ins Text set : FATAL ERROR! disable VoxATC
4065562 Prompt disabled
4065577 Prompt Text set : bahrain approach sky dubai two five with you leaving one zero thousand three hundred descending six thousand
Recog :cockpitmessage : you have comms
Cockpit Recog Result: you have comms
Recog :cockpitmessage : I have comms
Cockpit Recog Result: I have comms
16:00:20.9960688 Current Position = 26.359328252317 51.3829111071102 10168.8516539587

[jabloomf1230]

I think that I figured this out. OBBI has duplicate VOR DME approaches (one for CAT A/B and one for CAT C/D) for both 12L and 30R. Both VOR DME approaches have the same name. Somehow this is causing the error in VOXATC. Without fsaerodata, these approaches are missing. This all makes sense. As VOXATC adds the approaches to its collection, it generates an exception, because the approach type already exists in the collection.

The question becomes, how to fix it. It could be fixed manually by editing OBBI.BGL and deleting the duplicate VOR DME approaches, but that seems a bit tedious, especially if OBBI isn't the only airport where this occurs.

Here's the official AIP entry for OBBI, which is up to date:

http://www.bahrainaims.com/aisjune14/20 ... en-BH.html

EDIT.

I don't think that this is the issue as I checked a couple of other airports that have multiple transitions for VOR DME approaches and they seem okay. There is something about the OBBI approaches that is causing VOXATC problems, but without Tegwyn West's help, we'll probably never figure it out.

[jabloomf1230]

Jose,

I did some more testing on this. I created a new version of OBBI from the fsaerodata stock airport with ADE. The first thing that I noticed was that some time during 2018, the OBBI on-airport VOR ident was changed from BAH to BHR, probably because there is a duplicate VOR with the ident BAH in the UK. I deleted all comms, approaches and used raw (XML) mode in ADE to rename the VOR to BHR. I then added back the approaches from the fsaerodata PROC BGL file to the ADE airport. I added back the AIRAC 1904 comm frequencies. Compiled and re-indexed with VOXATC and guess what? I was able to fly ILS and visual approaches into OBBI with no FATAL ERROR. However, if I requested a VORDME approach, VOXATC gave me vectors to the hold and told me to report at the hold point. But the interesting thing is that it referred to the VOR ident as BAH! As soon as I reached the hold point and reported, VOXATC generated a FATAL ERROR. Here's a link to a zip of the airport files, which I placed in a folder with the highest priority in my scenery library:

https://www.dropbox.com/s/0fp4lk5hos7xz62/OBBI.zip?dl=0

None of this makes any sense to me. The fsaerodata OBBI.bgl file has no reference to anything but the BHR VOR. The Level D 767 folder only refers to Lat-Long coordinates and not the VOR ID. I have no other versions of OBBI installed and I've checked everywhere, not the three ORBX Vector airport folders (since I disabled all of them) or any other potential 3rd party scenery folder. Any thoughts? Where is the reference to VOR BAH coming from? Is VOXATC picking up the VOR ID from the stock airport file APX61220.bgl? Maybe you could change the stock file so that just for OBBI, the VOR ID is changed to BHR and see if that fixes it.

Jay

[fsaerodata]

The BHR navaid is a joint on some nearby airways, and it's used on the FSAD airways database. You can see where it's located selecting it on the Little Navmap app.
I don't understand the point of having a duplicated VOR as long as it's not on the same region; actually FSX/Prepar3D uses the region code to differentiate navaids with same designators.
As said before, without some detailed logs from VoxATC where the errror comes from, it's really hard to figurer oout this kind of generic errors.

Regards,