Hey folkes,Has anyone got the LvlD 767 yet? I assume so, it's been quite here the last few days. Probably everybody is test-flying it!Well... I LOVE IT!And what I love the most is that it comes with the promised SDK to communicate with the panel. And from the brief view I took into it, you can communicate with almost the entire aircraft!!MCP, Overhead, Electrics, Hydralics, you name it!The SDK includes a dll that contains the IPC routines, a C header and a C library with the variables.I really really really hope that Dirk incorporates it into FSBUS as an option. I would love to control the 767 with my hardware. If this happens I will sure throw those 737NG panels away and make new plexi panels for the 767!Even if Dirk won't put it into FSBUS, someone may be able to program a small utility to translate the 767's variables to FSUIPC addresses so that it can be used with FSBUS. I don't know C so I can't program it. If there was a VB sample, maybe I could do it.Any takers?Fly safe,George DorkofikisAthens, Greece

>Even if Dirk won't put it into FSBUS, someone may be able to>program a small utility to translate the 767's variables to>FSUIPC addresses so that it can be used with FSBUS. I don't>know C so I can't program it. If there was a VB sample, maybe>I could do it.Γεια σου Γιώργο. (Greek greeting to George!)Working with C dlls is quite easy with VB (OK, 95% of the time that is). Just pass variable pointers with the "ByRef" keyword and variable values with "ByVal". Data stuctures can be build with the "structure" definition (in VB.Net) or "type" in VB6, while lists are passed by "ByRef"ing the first list member.I don't own the plane so I'm not of much help, but contact me if you need any help.

So the SDK comes with LEVEL D?? Wow If it is so hope someone has already started to make a proggram for FSBUS which it would be great... This could make many cockpits possible in a faster way rather than having to buy non realistic expensive modular software.Roberto

Not only FSBUS... but can it interact with EPICUSB, Phidgets, or any other I/O Bus card. If so PLEASE do let me know

Hi,Yes it's great! I have had a first look at the basic SDK today and it's promising indeed. All the states of the switches and annunciators in the Overhead are there. I will extend my FSCONV program (in C) with some code that regularly reads the state variables from the LVLD 767 sim and translates them into FSUIPC variables (in the Project Magenta range since I'm not using PM). And then the IOCards program from Opencockpits I'm using, will be able to control my leds in my Overhead switches.!!!!Regards Nicowww.nicokaan.nl

Nico that would be great.This way both FSBUS and IOCards will be able to use the PM range FSUIPC offsets immediately.Please confirm if you indeed will do so, so I won't start anything you may have already done.George DorkofikisAthens, Greecehttp://www.precisionmanuals.com/images/forum/betaimg.jpg

Oh my god!!! This is going to be great please keep us informed!! Does it come with the basic software???Thanks.Roberto

Yea sdk comes within the package , but the interfacing software has still to be whritten

So, you mean that your FsConv will run as a Middleware between PIC and Fsuipc? Btw i informed also Dirk about tha SDK and he may do something for FsBus, when he will found time, of course after the new FsBus versions.regardsEddie ArmaosAthens - Greece

>So, you mean that your FsConv will run as a Middleware>between PIC and Fsuipc? Yes (!), I already have that program running, it currently does preprocessing of FSUIPC variables. For instance I compute the fuel config state of PIC 767 (version 1) by reading the amount of fuel in the left and right main tank. If that amount of fuel is too low, I set a flag in a free FSUIPC variable. That flag is read by IOCards and used to light the fuel config led in my Overhead. Of course it could be read by FSBUS as well.But now with the basic SDK of the LVLD, I do not have to read the actual fuel values from FSUIPC, but I can grab the state of the fuel config directly from the LVLD sim and set the same flag in FSUIPC. Much easier and always in sync with the sim!!!You do need a registered FSUIPC for that, because otherwise you are not allowed to write into FSUIPC address space.Regards,Nicowww.nicokaan.nl

That's great news...I only wish there were an NG version of it :(767 is too big an airplane for my kind of flying :(

Hang in there Claudio, maybe somebody will release a 757 patch like they did with the original PIC767.One can always hope.ChuckCYXU

The #### with FSUIPC if you can get it directly from LEVEL D ! Roberto

Hey NicoJust read this post and I can't believe the SDK has the overhead etc included. I'm not into programming at all so I'll be really interested to see what you can do re outputs.....its all too good to be true this LDS767!Also wondering how we can access the dedicated ILS radio for rotary input and display output...have you considered this at all yet?Many Thanks

>>So, you mean that your FsConv will run as a Middleware>>between PIC and Fsuipc? >>Yes (!), I already have that program running, it currently>does preprocessing of FSUIPC variables. For instance I compute>the fuel config state of PIC 767 (version 1) by reading the>amount of fuel in the left and right main tank. If that amount>of fuel is too low, I set a flag in a free FSUIPC variable.>That flag is read by IOCards and used to light the fuel config>led in my Overhead. Of course it could be read by FSBUS as>well.I guess you could do the led checking and other logic with SIOC as well? Just doing a mapping from LSD (well, it seems like drugs for many :)) SDK to some FSUIPC range would make most sense I think. All hardware can use FSUIPC anyway, so doing "fsbus specific" or "IOCARDS specific" stuff sounds like sub-optimal - best would be to have it synced with Peter Dowson to get a dedicated range of offsets like Magenta.. actually, just using the Magenta offset range might be a good idea, since LDS and Magenta are sort of exclusive anyway.//Tuomas