July 7, 20214 yr I'm sure it's a dumb question, but... Would it be something that can be fixed by tweaking some aircraft text file, or it needs code to be compiled (hence requiring a new version to be released)?
July 7, 20214 yr Both. The aircraft seems to be configured with GPS overriding NAV/HSI datarefs, this you can disable yourself in the GNS Settings. It might prove to be all that is needed for 90% of the issues you're reporting. But there are additional opportunities to integrate the two better which can only be done in changing the EFIS code itself. For this, we're in contact and assisting already!
July 9, 20214 yr Author Here's some more information. After booting up the SR20 Avidyne on the runway at KGVL, set to fly direct to KAND, and after manipulating the data flow settings on GPS1 which orients the bearing pointer to align with the HSI, the result is what you see here: That looks fine. But as I take off and fly according to the heading bug setting, both the HSI and Bearing pointer ought to follow each other, always pointing at KAND. The HSI works just fine, but as you can see the bearing pointer, once set, does not move. The result after a few minutes flying, and after performing a "direct-to" on the 430, you can see the bearing pointer is not seeking the bearing to the KAND waypoint. I had a couple of minutes this morning and thought I would give you some more information on the problem. Thanks very much for looking at this.
July 9, 20214 yr Thank you for the additional details. We're making progress already and this will be corrected! It is in good hands now.
July 23, 20214 yr Author On 7/9/2021 at 9:40 AM, RXP said: Thank you for the additional details. We're making progress already and this will be corrected! It is in good hands now. When do you think we can expect an update with this fix?
July 23, 20214 yr I don't know when they'll publish their update, but we're also preparing ours in order to provide them additional data they can pick from and display. Unfortunately, we're right now also stuck from releasing this update because of the TG+RXP issue which is also being worked on and being resolved, and I don't want to release 2 updates a few weeks apart. PS: for the TG+RXP issue:https://www.avsim.com/forums/topic/602533-gtn750gns430-xp1155r2-tg-freeze-resolving/?do=findComment&comment=4574441 For this one, those having reported the problem are being handed a TG test build which seems to be working but we don't have enough feedback yet (only 1 reported back so far...). The issue is however not specifically TG or RXP related but rooted deeper in the Windows module loader in a specific context, and we're also investigating this part with the help of a 3rd party in order to make sure we all fully understanding the underlying Windows problem here.
July 23, 20214 yr Author 39 minutes ago, RXP said: I don't know when they'll publish their update, but we're also preparing ours in order to provide them additional data they can pick from and display. Unfortunately, we're right now also stuck from releasing this update because of the TG+RXP issue which is also being worked on and being resolved, and I don't want to release 2 updates a few weeks apart. PS: for the TG+RXP issue:https://www.avsim.com/forums/topic/602533-gtn750gns430-xp1155r2-tg-freeze-resolving/?do=findComment&comment=4574441 For this one, those having reported the problem are being handed a TG test build which seems to be working but we don't have enough feedback yet (only 1 reported back so far...). The issue is however not specifically TG or RXP related but rooted deeper in the Windows module loader in a specific context, and we're also investigating this part with the help of a 3rd party in order to make sure we all fully understanding the underlying Windows problem here. By, "they," do you mean Torquesim? Also, what is 'TG?'
August 16, 20214 yr Author RXP, has Torquesim gotten back with you about the remaining problems involving inability of using the GNS430 CDI button?
August 16, 20214 yr We're in contact and they are working on this. Besides our latest update now includes an additional dataref fms_names (see User's Manual) specifically added thanks to Torquesim feedback!
September 9, 20214 yr Author Jean-Luc, has Torquesim contacted you about the problem with the last RXP update? The Cirrus Entegra, which prior to the update would intercept and follow a vertical glide path, no longer intercepts it. Flies right by the point of interception.
September 9, 20214 yr 5 hours ago, Hank Sullivan said: Jean-Luc, has Torquesim contacted you about the problem with the last RXP update? The Cirrus Entegra, which prior to the update would intercept and follow a vertical glide path, no longer intercepts it. Flies right by the point of interception. Hey Hank, yes I have but haven't heard back yet. @RXP let me know if you need me to re-send the email in case it didn't deliver!
September 13, 20214 yr Author On 9/9/2021 at 2:43 PM, RXP said: @Coop1019 I'm checking this right away. Thank you. RXP, the really important issues with the Avidyne Entegra product in the Torquesim Cirrus SR aircraft appear to be remedied. Now I wonder if I might have you take a look at the workings of the STEC55X autopilot, specifically as it relates to ILS and RNAV WAAS approaches. Essentially, there are additional steps involved in the model which do not exist in the real airplane using this equipment. Anyone using this sim as a trainer would find it confusing noting the differences. And so, I would like to steer you and your people to the following link, which discusses in detail exactly how the STEC55X should work during these approaches. Hopefully someone will be able to create time to look at this. Thanks very much. Love your product! https://genesys-aerosystems.com/sites/default/files/files/Fifty Five X for SR20-22 Avidyne.pdf Edited September 13, 20214 yr by Hank Sullivan
Archived
This topic is now archived and is closed to further replies.