kiek

and as an example: Yellow,13121,1,1,0,1,0,0,JS64: but 8 OR Green,13120,4,256,0,256,0,0,JS64: but 8 will have the same effect. Cheers!

Hi Pantu, There are several ways that lead to Rome... Indeed a joystick has 32 bits. But you can either reach a bit by: addressing its BYTE boundary and then mask one of the 8 bits in that byte, OR you can address its 32 bits WORD boundary and mask one of the 32 bits in that word! Both ways are valid. I find it easier to address each byte, because then the masks are not bigger the 128. Hope this makes things clear.

Hi Pantu, Your example code is not correct, I'm afraid... You forgot the mask... If you use these lines instead, you will notice that you can program 288 buttons, that will be recognised by FSUIPC! (.. don't blame Pete .. ;-) ) Green,13120,1,1,0,1,0,0,JS64: but 0 Green,13120,1,2,0,2,0,0,JS64: but 1 Green,13120,1,4,0,4,0,0,JS64: but 2 Green,13120,1,8,0,8,0,0,JS64: but 3 Green,13120,1,16,0,16,0,0,JS64: but 4 Green,13120,1,32,0,32,0,0,JS64: but 5 Green,13120,1,64,0,64,0,0,JS64: but 6 Green,13120,1,128,0,128,0,0,JS64: but 7 Green,0,0,0,0,0,0,0, and so on... Regards, Nico Kaan

Hi, I have posted this in the Level-D forum about the same question: =============================================== The Level-D does not support FSUIPC fully! I mean you cannot get all the info from the panel and control switches, rotaries in the panel via the generic FSUIPC FS2004 offsets. Examples: Lights cannot be controlled, Nav1 and Nav2 are not supported... Level-D has taken a new (and better approach): You should interface with the basic-SDK of Level-D (a collection of datatypes and functions in the C-language). But if you want continue to interface via FSUIPC (which is the approach taken by programs for home cockpit buillders such as IOCards, FSBUS and EPIC), and not want to program in C yourself, the good news is: I have made a freeware program that maps the basic-SDK of Level-D to FSUIPC. With this program, called FSCONV, you will have a whole new range of FSUIPC offsets available (for overhead states, NAV1 and NAV2 control, AFDS/MCP control, gear variables, COMM1 with freq tfr switch, ...). More info at my website http://www.nicokaan.nl, page FSCONV ==========================================

Well C (or C++) would be a nice compromise, I would never ever use VB! ;-)

Look into c:\documents and settings\'your username'\application data\microsoft\fs9 there you should find it. Regards,

..hmm.... . I have not experienced that. Think of all the other 20 or more processes that are running under the Windows Operating System... Kill as many you don't need. Furthermore FS9 will always try to use 100% of the CPU. This program is still cpu bound. You better limit the fps to 20.

That's not true. I've always used it on another computer, via WideFS. It is connected that way here at this very moment. Pete Sorry for the confusion Pete, I meant to use MCP747 with Level-D on two different PC's (I am so focussed on Level-D that I cannot imagine any other uses ;-) )

Hi, It's technically impossible (IMHO) to connect the MCP747 to another computer then the one that runs FS9. But why would you?? Everything is available (a Level-D mcp747.exe version packed with the Level-D software) to connect it to the FS9 PC (via a COM port). It runs flawlessly... no impact om fps so why? Regards, Nico Kaan

Hi, Have done some logic symplification. This should do the same: BOOL stillAlive() { char chTime[3]; return ( FSUIPC_Read(0x238, 3, chTime, &DwResult) && FSUIPC_Process(&DwResult)); }

and, by the way, it's a piece of C-code ;-)

Hi, I'm using this function in my FSCONV program. I call it every other minute, works fine! The rationale is that if you're not able to get the Time from FSUIPC, it is no longer running. BOOL stillAlive() { char chTime[3]; return (! ((!FSUIPC_Read(0x238, 3, chTime, &DwResult) || ! FSUIPC_Process(&DwResult)))); }

Hi, For your information: My freeware program FSCONV makes the Level-D SDK available via offsets in FSUIPC. More info at http://www.nicokaan.nl downloads page: FSCONV. Note that you need a registered copy of FSUIPC, otherwise FSCONV will not run. Regards, Nico

Hi, For the second time this week I had problems with WideServer. A few days ago the communication between my two PC's was locked and I noticed this line in my FS2002 screen: "Wideserver: 256 connected..." This evening I had problems with the PTT switch not responding (the AVC window kept saying Transmitting...) and I noticed that the number of Wiseserver connections was increasing with about 1 per second, counting 45, 46, 47, and so on until I closed down FS2002. I powererd down my both computers and started all over again and everything worked fine again. Any ideas what's wrong?? Regards, Nico

Hi, If you can't even afford to buy FSUIPC, don't start with this hobby at all ... my 2 cents...

Hi, With the help of Pete I have solved the problem. In the Aerosoft MCP application (version 1.8a) for switches, it's important to assign the right Switch Type when assigning a function from the predefined and expandable list to a button. For the Virtual Button function, we have added to that list, the corresponding switch type is Toggle. (and not momentary, like I had ) Now it works fine!

Hi, I have connected a push button to the MCP expansion port 4, this morning for test purposes. What I did for Mark's problem: Defined the virtual button 1 (according to Pete) in the variables.txt file that goes with my MCP. Defined the switch position 0 at expansion port 4 to be the Virtual button 1. In FSUIPC, buttons page, I pushed the button and got FSUIPC response with joystick 64, button one, and I programmed it to Keysend 1-255 (widefs) with param 1 on make and Keysend 1-255 (widefs) with param 2 on release. Note that this is equal to my definitions of normal PTT on Joystick 0 button 7. I looked in the fsuipc.ini file and found the button definitions for joystick 64, and saw that they were equal to the definitons for joystick 0 button7. So that looked good. However, it does not work. Strangly enough when I try to reprogram the PTT button in FSUIPC it does not recognize the button anymore, the screen remains grayed. When I exit FS2002 and FSUIPC and start them up again, I get the same picture. Only at the first push at the PTT button, FSUIPC responds with the Keysend definitions, but the second time I want to (re-define)it, it does not respond. This is strange, because for my normal push to talk button on joystick 0 button 7, I get always a respons from FSUIPC. Any ideas Pete what can cause this? Kind Regards, Nico

Hi Mark, Let me try to help and summarize what you have to do, based on the great help you got from Pete: Add 13120,1,1,0,1,0,0,Virtual Button 1 to the definitions file that goes with the MCP software, and attach your PTT button to it using the MCP application software. Then open FSUIPC, choose buttons tab (don't forget that your MCP must be turned on). Push your PTT button and see whether FSUIPC recognises this -virtual- button. If so, add PTT on to the making and PTT off to the release of this button. If not ??? I give up.

Hi, Like I said before, all (including SB) works fine with me..!! No special code needed. Note that I am running SB via WideFS on another PC.

Hi, Just to share this experience: I tried to register my FSUIPC3 software this evening, but in the beginning I did not succeed. My Key was rejected and I got the message that my system was running low on memory... I found out I had a very big FSUIPC log file (13 Mb) with a single (repeated endlessly) message stating that I could not run MCP.exe from this non registered program (something like that) After I had removed the Programs section with the run options from my FSUIPC.INI file, I managed to register and there were no error pop ups. After that, I have downloaded the latest version of the Run Options and added CMStart.exe (from CH products) and MCP.exe (from Aerosoft), restarted FS2002 and no problems.

works fine with me...