ChrisPUA320 Posted February 1, 2024 Posted February 1, 2024 (edited) Hi, I figured that the LVars for the V-Speeds (V1,V2,VR) (L:INI_V1, Number), (L:INI_V2, Number) and (L:INI_VR, Number) will stay at "0" even when set in the MCDU. Also the VAR for the FLEX Temperature will always stay at value "40" no matter what is set in the TRP. inbuilds please fix this! Thank you! Edited February 1, 2024 by ChrisPUA320
ChrisPUA320 Posted February 3, 2024 Author Posted February 3, 2024 Thank you for the update. FLEX Temp is now working. But the V-Speeds are still at "0" after 1.0.4...will there be an update on this?
Crabby Posted February 4, 2024 Posted February 4, 2024 On 2/3/2024 at 9:36 AM, ChrisPUA320 said: Thank you for the update. FLEX Temp is now working. But the V-Speeds are still at "0" after 1.0.4...will there be an update on this? Did you enter the Vspeeds on the TO page of the FMC. Mine are working fine and have always worked. V1 and Vr are entered in the TO page. V2 is entered in the speed window on the MCU. Mark "Crabby" Crabtree AAL311 | PHL I7-9700KF | 2070 Super | Honeycomb Alpha/Bravo | MFG Crosswind
ChrisPUA320 Posted February 4, 2024 Author Posted February 4, 2024 (edited) Sure it was entered in the FMC and the V2 is entered as preselected as well but the LVars still stay at „0“ ! In the aircraft it is working fine but if you want to use external devices you can’t because of this issue. did you check the LVars if they do NOT stay at „0“ on your end? Edited February 4, 2024 by ChrisPUA320
ChrisPUA320 Posted February 4, 2024 Author Posted February 4, 2024 @Crabby see my first post on this topic
Deleted Account Posted February 4, 2024 Posted February 4, 2024 Heya! What is the usecase for this? What are you trying to do, that isnt working because these LVARs aren't implemented?
ChrisPUA320 Posted February 4, 2024 Author Posted February 4, 2024 Hi, these Lvars are definitely implemented (see my first post) but they stay at a value if 0 no matter what you insert in the FMC. That is the same like with the Flex value which got fixed in 1.0.4 now.
ChrisPUA320 Posted February 4, 2024 Author Posted February 4, 2024 The Vars are called: (L:INI_V1, Number), (L:INI_V2, Number) and (L:INI_VR, Number
ChrisPUA320 Posted February 4, 2024 Author Posted February 4, 2024 I have several usecases where I would need these values. Besides I have made a complete conversation with the use of AAO which is like FS2crew (but better 😉 ). There is also a takeoff briefing between Cpt and FO where they also talk about the VSpeeds of course. Then I also need them for the callouts during takeoff run etc… rgds chris
Deleted Account Posted February 5, 2024 Posted February 5, 2024 With implemented I mean functional to your needs eg showing the actual number in the LVAR. Obviously I know what V-Speeds are, but I don't understand why you need the LVARs to be functional to your needs. Do you have your own FMC unit?
ChrisPUA320 Posted February 5, 2024 Author Posted February 5, 2024 Thanks for reply. As I described above I have several projects running with AAO (Conversation, FMC, ext hardware etc.) on the A306 where I am dependent on these Vars. They have to be read and used by several scripts.
Recommended Posts