PaulusP

Dear Pete, Thanks for your answers. I think I was too much focussed on 1 macro dedicated to 1 button, and this was clearly not correct. When I discovered that 1 button needed to be changed, I only had to program another button and there was no reason at all to delete the macro also. So I will follow your advice and this weekend I will start all over again with creating macro's and than assign the buttons and switches. (if I run into problems I will come back again, but basically I think that I should try myself first to clean the mess I created). Regards, Paul.

Dear Pete, The past few weeks I programmed successfully around 20 buttons in my Airbus cockpit that never worked before (which made me very happy) But than I wanted to change the programming of 1 button (APU start). This is what I deleted: - the relevant button in the buttons list in FSUIPC ini (2=P0,8,CM8:1,0) - the macrofile (macro number eight) in FSUIPC ini - the APU start MCRO file in Flightsim 2004/modules But now I can not add new Mouse macro files anymore! That is, I can add them, but they do not work anymore! Everything is there, new MCRO files, the button programming and the macrofile, but the new added macro's just do not work. Yet, when I press the Tab key (to test while making the Macro) this works. But when I have finished the programming and I assign a button, it just does not work (I pressed reload all buttons also). Than I tested to delete 2 button assignments, while leaving the MCRO files in the modules folder intact, and I could assign again any button to the MCRO files. Existing macro's are still OK, but new macro's just don't work. Probably I deleted too much or too little. Can you give me your advice? Paul.

Dear Peter, Thanks to your new feature "Create mouse macro" in FSUIPC, finally I have been able to make a number of switches and buttons work correctly in my Airbus cockpit! Thank you so much for this really great extension! You are the hero for many cockpitbuilders! Best regards, Paul

In our cockpit ( http://cockpit.punt.nl) we use printed boards to connect hardware buttons to my flightsim and these boards are detected as Joysticks by Windows and FSUIPC. Recently I had to exchange 1 board (nr 5) and after I replaced it, the buttons on boards 5 and 6 did not work properly anymore. Than I found out that the numbers attributed to these joysticks in FSUIPC had been switched. (Remark: in Windows/Gamecontrollers the sequence has NOT changed) Therefore I have three questions: 1. How are the numbers of these joysticks in FSUIPC attributed? 2. Why is it not a logical row? I have 6 joysticks and the numbers in FSUIPC are 0, 1, 2, 4, 5, 6. So number 3 is missing. 3. How can I change those numbers in FSUIPC? I tried to disconnect nr 5 and made a reboot, disconnect nr 6 but no change and than nr 5 + 6, but they still remain switched. Because it took many hours to programme the buttons for those joysticks (my FMC/MCDU), I would like to be able to change the numbers of the joysticks instead of re-doing all my programming. PaulusP

Peter, the problem is solved! Because of your question whether the MJOY joysticks were there in devices.cfg of FS, I checked this file. There were many joysticks mentioned, but no MJOY. So I decided to disconnect and reconnect the MJOY's once again. To my astonishment they were now recognized in both Windows and FS ! So I started up the engines, applied throttle to start taxi and......nothing happened. Than I remembered, having read somewhere in your Forum that you should also set "Joystick sensitivities". And after setting them to maximum, there was the moment of glory: throttles (axis 7 and 8 ) and trim (axis 6) were all working! I do not understand why the throttle and trim joystick axis were recognized this time, but it works, so this topic can be closed. Thanks again for your replies. Paul

Peter, thanks for your quick reply! Actually, I tried to assign the throttles via FSUIPC because they were not recognized in FS 9. I did not understand that, because they are clearly detected by Windows, so why not in FS? :? Could it be posible that FS has a 6 axis maximum also? I have deleted the greater part of the existing joystick and keyboard assignments to prevent conflicts, so at this moment I have deleted all joystick axis for the 4 MJOY's and also the throttle axis of the flightcontrol joystick. When I select "Change assignment" for Joystick axis in FS and when I move the throttle axis of my flight joystick it is detected immediately, but when I move the throttles of the cockpit, there is no detection at all in FS. Note: I will install the upgrade to 3.72 immediately! Paul

Dear Peter, Thanks to your great FSUIPC programme we have been able to make a lot of buttons work in our Airbus A-320 cockpit. But for some reason the throttles and trim do not work . We use so-called MJOY boards (4 of them) to connect our cockpit to the computer. Every MJOY is recognized in Windows as a separate joystick with 8 axes and 32 buttons. In Windows/Gamecontrollers, I select the MJOY for the pedestral. Than I see the 8 axes, and when I move the throttles on the pedestral, they are immediately recognized as axes “Choose” for throttle 1 and “Slide” for throttle 2. If the X and Y –axis are numbers 1 and 2, these will be the axes 7 and 8. (Note: it is a Dutch version of Windows XP; I hope the translation Choose and Slide is correct). However in FSUIPC the throttles are not recognized. First I thought that perhaps they would be recognized as different axes (trim or mixture etc) but I see no movement in FSUIPC whatsoever. I studied the FSUIPC manual, but I could not find a solution. Can you give me advice how to make the throttles work in FSUIC? We use Windows XP Professional (SP2), FS 9 and a registered FSUIPC version 3.71 Paul

Frank, It took some time to come back to this forum, because it was difficult to contact the creater of our Airbus panel and to discuss this with him. As indicated by you, he told me indeed that the solution is to build a key board emulator. However, this means that we will have to rebuild also our MCDU in a Holtek structure. This is an unpleasant setback for us. We are not sure how to continue, but as it is now, our panel will thus never be fully functional. Only the buttons that can be connected through a "FS command" available in FSUIPC will work. Anyway, thanks for your input: at least we now know why other buttons do not work. Paul

Frank, Thanks for searching this forum! I also tried to find a solution for this problem, prior to posting (as recommended :wink: , but you are clearly more experienced since I did not find what you found. And what you found is really interesting! Here is my story: I started FS and than I started to type this message (while FS was reduced to the small tab in the bottom of my screen) and when I pressed the Shift +F9, indeed the APU Master was initialised!! So perhaps I should try to contact the creator of the Airbus 320 panel, to hear whether he can change this. Regarding you other remarks: When I am in FS and I click with my mouse on these buttons (APU and APU start), than the indicator in the panel lights up and after 10 seconds there will be a message in the engine display that says: APU available". Only then it is possible to start up the engines. The buttons are there in my cockpit (they are connected and recognised in FSUIPC), I only need them to be operational. But that will be a software matter. Paul

Frank, thanks for your answer. After reading your reply, I was glad that at least I had programmed the button correctly, but unfortunately my problem is not solved, because it still does not work when I push the button (although the keypress combination is sent correctly). About my panel: it is an Airbus A-320 panel written by a member of our flightsimilatorclub (FSCB= FLight Simulator Club Belgium - http://www.fscb.be) and it is installed like any other commercial FS add-on. I use the panel inside the beautifull IFDG Airbus. The commands "APU master" and "APU start" do not exist in FS 2004, but they exist in the panel. When I make the keypress "Shift + F9" on my keyboard it works perfectly, but when this command is sent through FSUIPC it does not work anymore. Yes, FS2004 and the panel are all on the same computer (to be fully correct the panel gauge is inside "FS2004/aircraft/IFDG A 320/panel" Do you have other suggestions to fix this? Paul

The construction of our Airbus A-320 cockpit is well underway and now we have started to make things really work. Thanks to your wonderful FSUIPC program (we use licensed version 3.71 in FS 2004) many buttons in our overhead panel and pedestral are now functional! There is one problem however: the programming of the buttons only works if we can use a command from the "FS commands" list. But for some buttons, for example "APU Master" or "APU start" there is no corresponding command in the FSUIPC list. Our panel has been programmed so that APU master will start with "Shift + F9" , but when I type this combination in FSUIPC, it does not work. When I press this combination on my keyboard it works perfectly. I have checked FSUIPC-ini file and it says "59=H1,29,K120,9 " I am new into FSUIPC and there is definitely something I overlooked, but can you tell me how to make that button work? Paul

Pete, Thank you for your quick reply! It is Windows XP with SP1 only. I will install the programme and I will come back to report the result. PaulusP

I use actually three different joystick devices. The first two are identical and are microprocessor based MJOY USB circuits designed by Mindaugas Milasauskas. Each of them may be programed with different Name ,Vendor and Product ID number. The first being : Name=MJ16 , VendorID= Hex00 , ProductID= Hex02 The second being : Name=MJ62 , VendorID= Hex00 , ProductID= Hex03 The thirth one is a regular simple Thrustmaster. All three devices are fully functional and do appear in the GAME CONTROLLERS LIST of Windows XP in following order MJ16, MJ62, USB HID (top down). Now we go to the buttons page of the FSUIPC MODULE. Pushing any button of any one joystick is identified by FSUIPC and its number displayed , ALL TOGETHER WITH THE JOYSTICK NUMBER were the button is located. There are no problems with the button numbers. But it appears that , (apart from the fact that you start numbering from zero instead of 1), the identified joystick numbers do NOT CORRESPOND WITH the list sequence in the "game devices list" of Windows. So , MJ62 (2nd) is identified as joystick #0 , MJ16 (1st) as #1 and the thrustmaster (3rd) as #2. If however I unplug the MJ62 (2nd) from the hub and leave the first MJ16 and the thrustmaster (3rd), they will be recognised in the buttons page of FSUIPC as # 1 and # 0 respectively. !!!!! ?????? What is going on ? How can I correct this? PaulusP