Crossfill error when entering approaches

[FlyingAxx]

Hi there,

While flying with MSFS2024 (store version) and my SWS PC-12 in Alaska I decided to use approach procedures, because of the weather - the first time after installing TDS GTNXi not too long ago. I had the flight plan on the 650Xi and the moving map on the 570Xi. The preselected approach had been just loaded, not activated.
The  flight: PAKK/01 ZUTMU MADTP FANUP THEBS (IAF)  HAREP (FAF) DRIGE JALNO HEGAN (MAP) PAUN/15 --APP HAREP (L15)
I had manually typed in just PAKK to THEBS and finally PAUN before selecting and loading the HAREP LOC15 APP

I'm not sure when it appeared exactly: I saw for a very short time a small (message?) window appearing and disappearing in the middle of the screen and recognised the message indicator flashing. The I found out that the bird obviously didn't follow the predefined course and took over by hand and later by using HDG instead of NAV.

After roughly stabilising the course I first tried to look into the 570Xi, no click spot worked. Then I switched OFF by pulling the related fuse (thanks to SWS implementing this possibility). Now the autopilot accepted again NAV mode. When pushing the fuse again the GTN750Xi booted, but after acknowledging the messages the above described phenomena happened again.

When looking after the message I found CROSSFILL ERROR.

Now I'm not sure whether I did something wrong (ERR in front of the screen ) or if I found a software bug. The behaviour was reproducible, all used software, including W11 is up-to-date.

I've tried it by using an RNAV-approach instead at PAGM/34 and it behaved reproducible no matter when the approach was selected. A "normal" flight in between worked fine, just the way I had used the GTN before.

I'd  catching the little ghostly window.
Where is the log-file?    

EDIT: Made a C172-flight with external TDS, same results.

Help is appreciated.

Thanks,
Alex

[adminOwner2]

Hello Alex,

This sounds to us like a CTD of the PC Trainer when flight planning.

We are not sure what you mean by "570Xi" as there is no such product. There is the GTN 750Xi and the GTN 650 Xi.

We have tried replicating the crash, but we have been unable to. Let's work a bit on this.

Which version of the TDS GTNXi do you have installed?
Which version of the GTNXi PC Trainer are you running inside the TDS?
Which navdata provider/cycle are you running?

Are you able to replicate the crash if you start the TDS GTNXi from the desktop shortcut with MSFS closed?
If so, please help us with a screenshot right before the CTD occurs?

Not to worry, we will do our best to get such issues resolved.

[FlyingAxx]

Hi,
Thanks for your answer.

First: Of course there are the GTN750Xi and the GTN650Xi. I’d been lazy and even didn’t see the typo.
The software:TDS GPS Manager 1.0.1.6 (why it tells me an update is required?)

• Aviation Trainer 3.10.3.0
  
• GTNXi PC Trainer 2042.2.0
  

TDS TDNXi (Pro Upgrade installed for both versions of MSFS)

• MSFS2020
  Executable 1.3.0.5
  Gauge 1.0.22
  
• MSFS2024
  Executable 1.3.0.5
  Gauge 3.0.3
  

Navdata source: Navigraph AIRAC Cycle 2511 rev.3 – no charts

Q: “Are you able to replicate the crash if you start the TDS GTNXi from the desktop shortcut with MSFS closed?”f
No, it only happens with MSFS2024 connected and a couple of seconds after the a/c begins to move. While taxiing it might happen after 30 seconds, during the flight it takes about 5 seconds.

The same is reproducible for me, when using the C172 and using the desktop version of both gauges on a second screen. Unfortunately there is no easy way to recover except maybe switching off the avionic bus (I didn't try it).

The enclosed screenshots are showing the preparation phase till it happened while taxiing along the runway, after taking off after switching to autopilot, while the bird still tries to fly to the left (the AP would work with HDG, but not with NAV), then how it perfectly returns to follow the NAV-mode after pulling the fuse and even during booting the GTN750Xi till its Homepage. Leaving it there works, but about 5 secs after switching to MAP it happens again (this time again the windowed error message).

Remarks the flightplan, including the approach, had been imported from LittleNavMap via your Catalogue function -  only this time. No different result.

You've got screenshots of the first phase till the first crash. If you want I can offer more during the flight phase after toggling the fuse.

Regards,
Alex

---

Now the continuation during the flight. Unfortunately the unlimited space is limited (I even compressed more). However, it was possible rebooting again and again. The only way flying the RNAV later on was leaving the blocked GTN750Xi off.

Regards
Alex

---

The final continuation, showing the error message in the GTN650Xi. That's it.

[adminOwner2]

Hello Alex,

Thank you for the information. We have an idea to try out.

When you set up the flight plan, before the aircraft moves, please access the TDS GTNXi Pro interface from the system tray, access the Navigrpah Charts tab and temporarily change from Navigraph Charts to FliteCharts.

Do you have a Navigraph Charts subscription or did you have one?

[FlyingAxx]

Do you have a Navigraph Charts subscription or did you have none?

I do have just the basic subscription. When flying low and slow I'm often using the SWS Kodiak and there is no need as LittleNavMap (LNM) is fully sufficient. If necessary, e.g. for big irons, lots of AD2 stuff is available that can be shown either on my tablet or my second screen.
However, I'll see whether I can switch from <nothing> to <?>.

If you thing LNM could be the reason - I don't think so as the problem appeared first when I completely typed the plan manually.

Today I had left Alaska and made a trip from TFFJ to TFFF ILS Z-10 Approach and thought for a while that everything works as it should. A couple of mile before VOR PPR, about 25 mins after taking off it happened again.  
I was about to write the message that ILS approaches might be the exception - well they aren't.

At the moment I'm thinking about uninstalling the whole TDS package, but I'm not sure whether a new install would be a clean one. Garmin's software is quite persistent.

First I'll do the check as proposed (as far as possible). And I'll run a second test by using MSFS2020. It's still there while PMDG takes its usual time to adopt.

[FlyingAxx]

Hello Alex,

Thank you for the information. We have an idea to try out.

When you set up the flight plan, before the aircraft moves, please access the TDS GTNXi Pro interface from the system tray, access the Navigrpah Charts tab and temporarily change from Navigraph Charts to FliteCharts.

You apparently nailed it! 
I've just repeated the flight I did this morning, did as you told me - and nothing happened. The bird reached the point where it it tried to fly to somewhere before, but followed its route this time. The vertical path was announced and both gauges remained at their respective task all the time.
Now I'm puzzled in so far as I cannot believe that I'm the only one having no Navigraph chart subscription and didn't even miss Charts at all (LNM can do a lot and its FOSS).
I'll go back now to Alaska (okay, tomorrow) trying another failed flight. I hope that will happen without event as well. Thanks for now.

Edit: I did the second flight right now - success. You've got the right idea. Had it been a matter of not proper reading?

Regards,
Alex

[adminOwner2]

Hello Alex,

Thank you very much for confirming the bug and its fix. Indeed this has been the second bug report, we have addressed this on the TDS side and a proper bug fix will be included in the next TDS GTNXi release, as we take CTDs very seriously.

In the meantime, please enjoy the TDS GTNXi Pro!