CptBayer

Hi John, I love your support! Fantastic! It is the link software from Java Simulator! But right now I understand the system behind a bit better 🙂 ... greets Klaus

Hi John, sorry for the Dawson, I hadn´t my glasses on my nose yesterday:-p.... I found the the solution myself. The MCDU from Java Simulator has the FSUIPC_WAPID file in the link software folder. In the main FSUIPC folder there is also a FSUIPC_WAPID file needed for the FCU from cpflight. They were different! I tried to use in both folders the same file with the same date and here we go, it´s working 🙂 ! Thanx for your answers! For my understanding what the FSUIPC_WAPID file is good for, I will read the docs... Greets Klaus

Hi Mr.Dawson, my case is maybe a bit strange,but I try to explain my situation and the resulting question. It is about the FBW A 320 and some different hardware products. I´am using the following hardware (with MS 2020): 1. FCU + EFIS from cpflight (needs minimum 7.2.11 but works 100 % with 7.2.14) 2. MCDU from Java Simulator (works maximum with 7.2.10, but not with 7.2.11 - 7.2.14) For me it is not possible to use all the hardware together. Too bad, cause I don´t wanna dispense the one or the other. Now my question, what changed from 7.2.10 to 7.2.11, that the MCDU is not working anymore? I will contact the developer and ask him to update his software/files and i guess he will do it. I only want to understand what the thing is to give some hints to the developer :-). As far as I understand are the hvar one of the important things?! When using the MCDU with 7.2.10 the link software recognizes the buttom press, the needed command will show up in the link software and the command is given to the software MCDU of FBW (by dsuipc and simconenct?!). By using the 7.2.14 the link software recognizes the buttom press but didn,t show the command on the link software and as result nothing happens on the software MCDU of FBW. I hope you could follow my explanation. greets Klaus

Hi, I also want to create a macro file with Hvar for a MCDU. Which tools are the easiest? I have no idea to program macros. Tried to figure out in the web, but didn´t found anything but recording in excel or open office.. got it ... 😛 .... editor file with the extension mcro .... thanx and greets Klaus

Hi John, right. It is easier to go into the aircraft.cfg and take the title as file name of the hvar file... greets Klaus

Hi to all. I found the solution in the forum :-)))). The file name of the hvar file must be the same as in the log file! Via WASM and reload will list all hvar´s and the buttons on the FCU hardware are working... Greets Klaus

Hi to all simmers and developers, I have got a mysterious problem with FSUIPC, hvar files and the FCU hardware (plus EFIS) in comparision with the FBW A 320. I am in contact with Paolo of CPflight and we are troubleshooting together, but for my issue we (better Paolo) did´t find the issue and a suitable solution. The problem described as follows: - loading FS2020 - loading the FBW A 320 - starting and coonnecting FSUIPC (newest version) with WASM - starting FS_com.exe (tool from CPflight) Problem: FSUIPC didn´t load the file A320.hvar which is in the modules folder. The List is blank when selecting "list hvar" via Add-ons and WASM menu. When I press list lvar a long list is shown. The result of this problem is, that the buttons on my EFIS (CSTR, WPT, VOR D, NDB, ARPT and LS) hardware of CPflight did´t work. Only the flight director button FD works?! Strange isn´t it. When I press some buttons on the FBW FCU the green light on the hardware illuminates. Paolo from CPflight told me, that I am with another user are the one and only users with the described problem. For test purpose I load the TBM (also a existing hvar file) and started the hardware. All hvar are listed... Does anyone have a suggestion how to solve this issue? Greets Klaus