ddawson

Rob & Dave I could do a module to perform this function. It wouldn't have to be installed in each panel. It would simply go in the FS Modules folder and would load automatically with FS. Doug

FSUIPC will do this now. Have a look in the SDK. Doug Dawson

Pete, Yes it does. It seems to pick up everything. I had to filter out the joystick axes_set commands, as they showed up too. Doug

I am aware of that facility, but up till now I really didn't have a use for it. The use of the keyboard for these things isn't the problem here, it seems it's the way the XML gauges interface to the FS control procedures which seems to be the problem with the acceleration fix. Does your gauge pick up the calls from XML gauges? If so, it could be a solution. Regards, Pete

I am the author of the three gauges noted in your log file. Please ensure that the file 'gaugesound.dll', provided with John's panel, is installed in the main FS folder (not the Modules folder.) All three of those gauges use the file, with dsd_xml_sound.gau calling it almost right away. I suspect your problem has nothing to do with FSUIPC. Regards, Doug Dawson

The file version information is not used by FSUIPC - you may change this value to what ever you like. Keep in mind that when you are entering the registration information there are no spaces in the registration key. It would be entered as: B2AOZMKV9W9Y Also, as far as I recall, you need to specify the file extension (.gau) when you enter the filename and you should not be using quotes. Doug Dawson

Those will do it for you. The one you really need to keep is FSUIPC.KEY, as it contains your registration information. FSUIPC.INI contains any customized settings you have saved - handy to keep, but can be redone. FSUIPC.LOG - you don't need this at all, it is recreated each session. The dll file of course can be copied back into the modules folder at any time. Doug Dawson

I just posted a response to this same question (I presume from you) in the EG forum. Have fun, Doug Dawson

I used this code in my catault gauge. Seemed to work pretty well: FSUIPC_Write(0x3070, 8, &z_acceleration, &Result); FSUIPC_Write(0x3090, 8, &z_speed, &ResultR); FSUIPC_Process(&Result); I had to write both the acceleration and speed values to get it to work, but work it does... Cheers, Doug Dawson

Don't know about something stupid... :twisted: This worked for me: case PANEL_SERVICE_PRE_INITIALIZE: FSUIPC_Open2(FSReq, &Result, Mem, Size); Are you in fact creating a gauge? The readme makes reference to delaying opening the link: "You will probably need to delay opening the link for several seconds after FS starts your module. If it is a gauge you may not have a problem. One way is to simply retry the Open2 each time you are supposed to do something, until it works. The reason for the possible delay is that FSUIPC's interface is not available until everything else in FS is initialised. this can be a few seconds after loading." If you are writing a "stand alone" module, have you tried delaying access to FSUIPC for a few seonds? Doug Dawson

Richard, The easiest way to explain is to illustrate this. Reading from right to left: (0 * 16^0) + (9 * 16^1) + (1 * 16^2) + (2 * 16^3) = 8592 Each digit is multiplied by an ever increase power of 16. The results are added together to give the decimal answer you see. IF you put the digits in a column in a spreadsheet, each digit on a separate row, it becomes quite easy to visualize how to do the converting. Email me if you want any further assitance with that. Regards, Doug

Try changing Call FSUIPC_Read(&H34E, 4, VarPtr(iADFfreq), dwResult) to read Call FSUIPC_Read(&H34C, 2, VarPtr(iADFfreq), dwResult) The ADF freq is at 0x34C and is 16 bits, so your second parameter should only be a 2, not 4. Doug Dawson