kiek

Hi Pete, I'm sorry for not being very specific. I meant: I call the FSUIPC_read first (with 121 bytes) and directly after that I call the FSUIPC_process function. So the question actually should be: does it make sense (speed wise) to read 128 bytes in order for FSUIPC_process to be more efficient?

Hi Pete, I have to read 121 bytes, 16 times per second, and use this call: FSUIPC_Read(dwoffset, 121, pDest, &Res); Does it make sense to enlarge the size to 128? I mean will the read operation be more efficient with a blocksize of 128?

No thank you Pete, I can wait. Glad you'll fix it.

Hi Pete, I have these lines in FSUIPC4.ini: [Programs] runif1=KILL,READY,C:\Program Files\Aerosoft MCP747\mcp747.exe runif2=KILL,READY,I:\FlightSimming\fsconv\fsconv.exe runif3=KILL,READY,I:\FlightSimming\IOCards\sioc.exe When I kill one of these programs manually, a new instance automatically pops up!?! So the only way to kill these programs is to end FSX... This is different from the behavior I had in FS9.

You can set that path in the Options tab of FSBUILD. For more info about my two pc setup with the same software (and Ground environment Pro) have a look at my website, page preflight

Offset 0x8B1C is for the FO EHSI panel, the Captains side is at offset 0x8B18 .... I have checked this at my side by defining key 'A' for Captains HSI range selector set at 10 nm, and tried that using the keyboard, and it worked well!

Yes, there are 6 in a 767: 10, 20, 40, 80, 160 and 320 nm Sure. (what's normal? ;-) ) The 767 has FULL ILS, FULL VOR, EXP VOR, EXP ILS, MAP and PLAN regards,

Pete, I think you have missed my post, while answering Namron2...

Hi Pete, I had a discussion with namron2 in the Level-D forum, so I can provide some background information. Norm has a rotary switch (6 positions) connected to XKEYS, a kind of keyboard encoder, able to generate a key for each position. This switch is for selecting HSI range in the level-D 767. What he wants, is to give an FSUIPC offset (one provided by FSCONV) a value dependent on the position of the rotary switch. FSCONV has offset 0x8B18 for that (4 bytes long) of which the first 6 bits represent each position of the Level-D rotary switch for the Range. Normally one would not use a keyboard encoder for this, but an interface card of IOCards or FSBUS or EPIC or Phidgets and set these bits in the FSUIPC offset directly. However he insists on trying to accomplish the task with what he has, therefor I recommended a possible way out, like this: "Define separate keys for each range position, say A, B, C, D, E and F (any key-stroke combination will do). Let your XKEYS device generate these keys. In a registered copy of FSUIPC, open the 'Key Presses' tab, Set key 'A', choose as Control sent when keys pressed, Offset Byte Set at offset 0x8B18 and Parameter 1. Repeat that step for the other keys 'B' - 'F': the same Offset Byte Set control at the same offset 0x8B18, but with different Parameters, 2 for B, 4 for C, 8 for D, 16 for E and 32 for F. (Note For the HSI Mode, use the same procedure, but then at offset 0x8B19, with Parameters 1 to 32) " I assume this will work, OK? (although, like I said before, to me this does not seem to be the preferred way of interfacing). Best Regards, Nico Kaan (author of FSCONV)

No, there's just one hub in between. Yes, time out errors ... Well, but I'll buy your advice and stay with TCP. Thanks,

Hi Pete, A few weeks ago I switched from TCP to UDP in my two PC flight simulator. At my non-FS9 PC I run the following programs: ASV6, Squawkbox and Fuel Loader. After switching to UDP ASV6 and Fuel Loader still worked fine but Squawkbox sometimes could not detect FSUIPC, after trying again it most of the times worked ok. However, yesterday I replaced that pc by a much fatser machine (say 5 times faster). What happened: ASV6 keeps working fine but Squawkbox and Fuel Loader can no longer detect FSUIPC... I switched back to TCP and all worked fine... It looks as if there are some timing issues. Are there any parameters I may have missed setting? Your advise would be most welcome. Regards, Nico Kaan

Hi, FSUIPC offers 'generic FS2004' offsets. It's up to the panel developers to support these generic offsets or not. More complex add-ons like the PMDG 747 simulate many more states and controls; these cannot be mapped on the generic FS2004 offsets.... Another complex add-on, the Level-D 767-300, comes with an SDK (a software development kit in the C-language) that gives you access to most of the states and controls. I have made a tool called FSCONV that converts these states and controls to new offsets in FSUIPC. So if you want to build a complete home cockpit you better move to the Level-D ;-) Regards, Nico Kaan http://www.nicokaan.nl

Hi, To my knowledge Hagstrom encoders generate key-strokes, they do not use FSUIPC. Cheap and reliable alternatives that do work with FSUIPC are: OpenCockpits IOcards http://www.opencockpits.com/index.php?newlang=english and FSBUS http://www.fsbus.de/index2.html Nico

Amazing! I know no other cockpit builder that is that far.... Do you have all the hardware installed for all these services?? Note that a Service is there to support your hardware. E.g. It is not of much use to activate the FMC Command service if you do not have the 69 keys installed for the FMC keyboard .... Maybe you should read the manual first.

Hi Robert, ... and Pete is right too... Please read the FSCONV User Manual carefully (55 pages...)

Hi Robert, Thomas is right. FSCONV uses the FSUIPC offset address range 0x8B00 - 0x8BFF for making available all the functions and information that is in the Level-D SDK (they are all Level-D 767-300 spefic). That range was assigned by Pete for use by FSCONV exclusively, just like some other applications have a special range. So there's really no difference in the way HOW you use FSUIPC offsets in Phidgets for the generic FS9 offsets as publiced by Pete in FSUIPC for Programmers .doc, or HOW you use my offsets that are published in the FSCONV User Manual. Any specific FSCONV questions should be addressed to me and not to Pete. Regards, Nico

>I realised I needed WideFS and FSUIPC (tell me I did not make a mistake) Yes you are definitely wrong. You better had spent some more time reading Flightsim Forums. You need a program called WideView http://www.wideview.it/ for that.... FSUIPC is a program that gives you an interface to the FS9 internals. WideFS makes that same interface accessable over a network. They have nothing to do with running copies of FS9 synchronously at separate computers... The documentation is pretty clear about that, even for a non native English reader like me ;-) Regards, Nico

Hi, IOcards from OpenCockpits accesses offsets from FSUIPC, just like other systems such as FSBUS and EPIC. What can you do otherwise.. ;-) It's all written down in manuals in the spanish and in the english language, please search the Opencockpits website for manuals ..

Don't know, but I don't think so. Did not see any example and I'm a regular reader of cockpit builders fora.... Nico

For your information, just to point to a cheap alternative: Packed with the Level-D Boeing 767-300 is an SDK. My freeware program FSCONV makes the SDK functions and data available via FSUIPC offsets. Engine start control is included, amongst various other subsystems. No C-programming skills needed, no expensive PM software needed. Extra logic can easily be add via FSBUS or IOCards. Especially IOCards SIOC is a very powerful tool (and also freeware). Best Regards, Nico Kaan

does not matetr what language you are using: Open FSUIPC LOOP "ENDLESSLY" READ data from FSUIPC; USE data from FSUIPC Sleep for a number of msec (say 50 if you want to sample 20 times/second) END LOOP Nico

read the manuals that are in the SDK...

Does SB3 work with FS2002 as well as FS2004? Regards, Pete YES Nico

Hi Eward, Why are you not using SB3.03? (it's been released half a year ago...)

Hi, It looks as if you have forgotten the FSUIPC_Open(..) command. Now there's no link to FSUIPC, that's why it can't read ... Please read the manual carefully.