washburn_it

I had the same problem with another payware product and I solved this problem taking the original panel off (to avoid "interferences") from the aircraft and implementing the main systems with SIOC. After all we won't need the panel anymore when we have our cockpit, no? Another option may be to replace the panel with a standard FS panel implementing "manually" all the systems that the default panel doesn't support. I usually keep the original panel "on" just the time needed to "study" how to implement an onboard system and then I take it off to test my implementation. I hope this might help too. Regards, Bob

I'm glad it worked (well...I already knew that LOL) Regards, Bob

I tried this and it worked: function ReadAircraftName(): string; var str : string; aName : array[0..255] of Char; dwResult: DWord; begin FSUIPC_Read($3D00, 256, @aName, dwResult); FSUIPC_Process(dwResult); str:= aName; Result:= Trim(str); end; Regards, Bob

I'm not at home so I can't try but have you tried with PCHAR type? Example: var airName: PChar; Regards, Bob

Eheh well... it was a quick "count"...I think 16 may be enough anyway. Let's keep in touch. Bob

Thank you for your quick reply. Well, actually I don't know, at the moment, how many offsets I need since my applications are not yet completed. I was considering a future development to integrate my "glass cockpit instruments" with the interfaces for the cockpit building (FSBUS or IOCards) to permit the user to implement (via SIOC for IOCards or CCC for FSBUS) some functions that are not currently supported by FS2004. I think the "reserved" offsets I need might be 10 (maybe less), anyway I will let you know it when the applications will be finished. Best regards and...enjoy your holidays ! :wink: Bob

Hi, I'm writing some freeware "glass cockpit" application for the "home cockpit building world". Since I would give my applications the chance to interface with IOCards (http://www.opencockpits.com) or FSBUS (http://www.fsbus.de) I wonder if there are some FSUIPC offsets not used by any other application or, generally speaking, if there is a range of offsets that are not used by FS200x so that they can be used for my purpose. With "FS-Interrogate" I verified that there is a "gap" from the offset 0x4001(hex) to 0x527F (hex) that seems to be unused from FS200x. Is that so? Thank you, regards. Bob

I found it...it's strange but it's all due to the firewall (Sygate) !! I don't know which is the interaction between that firewall and FSUIPC or WideFS Server but if I close it, WideFS start working correctly and I don't get that "wrong FSUIPC version" anymore (both from the client computer and server computer). Don't ask me "why" because it's a mistery :shock: Regards, Bob

Thanks Pete for your quick reply...first I will check all of the logs involved with FSUIPC and WideFS...if I can't find anything to explane this behaviour I will send you those files. Regards, Bob

Hi, I have two problems with WideFS (under FS2004 and Windows XP Pro Sp1, FSUIPC ver 3.53 and WideFS 6.51): 1) when I load the Flight1 ATR72 with WideServer active and running I get a message error reporting that some gauges are not working due to the wrong version of FSUIPC...they require FSUIPC v3.41 or above...but the current version of FSUIPC is 3.53. If I remove WideServer.dll from the FS Modules folder, restart FS2004 and reload the Flight1 ATR72 everything works good...why this strange behaviour? 2) I'm developing a "glass cockpit gauge" (torque indicator for a twin turboprop) that reads value of torque through FSUIPC. Everything works good if it runs in the local computer (with FS2004 installed) but if I copy it in a client computer, run WideFS Client and then my glass cockpit gauge it doesn't read any of the FSUIPC offsets. It seems that it isn't connected to the WideFS Server but FS2004 reports 1 client connected (on the main window caption) and Wide Client's state is "connected". My glass cockpit gauge is written with Delphi so I went into debug (in the client computer) of FPCUser (that is the Unit providing the FSUIPC support for Delphi) and I found that when I call the FSUIPC_Open the connection to FSUIPC is refused because it seems it reads a wrong version of FSUIPC. Here follows the part of FSUIPC_Open for Delphi (I think it's similar to the one in C++) where the procedure quits: // Only allow running on FSUIPC 1.998e or later // with correct check pattern $FADE if ((FSUIPC_Version < $19980005) or ((FSUIPC_FS_Version and $FFFF0000) <> $FADE0000)) then begin if fWideFS then dwResult := FSUIPC_ERR_RUNNING else dwResult := FSUIPC_ERR_VERSION; FSUIPC_Close(); Result := FALSE; Exit; end; Why is it recognized a wrong version of FSUIPC if there is the v3.53? Thank you, regards. Bob

Thank you for the answer Pete, I will read the documentation then but I already knew the value range (and its meaning) from FS Interrogate...the aircrafts with which I tried my application was the Cessna 172 and the ATR 42-500....with this last one the "problem" (if we want to consider it a problem) is less evident than in the Cessna probably because, as you said, it has the reverse. Regards, Bob

Hi, I'm developing an external program which permits you to assign up to 8 axis of a joystick (using its circuit for a throttle quadrant) and save the assignement profile for each aircraft, using FSUIPC (3.50) to write directly into the corresponding control in FS2004, bypassing FS2004 assignements. For example if I assign the potentiometer of the X axle to the Engine1 throttle lever then I will write at the offset $088C. All is working but the movement of the throttle lever in the panel aircraft starts moving when the potentiometer is at about 50% of his course. I try to explane: the value of the potentiometer read from the joystick varies from +32768 to -32768 while the value into $088C (according to what is reported from FS-Interrogate) varies from +16384 to -16384 (the formula I used is simply the value read from the axle * 0.5). Then I have just the 50% of the whole course available. I also tried to write into $3AE8 (which can vary from 0 to 1) but the result is the same. How can I do to exploit the whole course? I hope the problem is clear. Regards, Bob