Hi,I am making very good progress with the FSUIPC interface for Level-D's SDK. Overhead, NAV1 and NAV2 are ready and tested. I'm now working on the AFDS. I decided to release the functionality via my FSCONV program. The FSCONV User Manual is almost ready, a preliminary version (2.0) can be downloaded from my website.I expect to make my program available for sharing on Monday evening, March 21st (Spring Time!).Regards,Nicowww.nicokaan.nl

Hi,I have just made available the First public release of my FSCONV program (version 2.01). It offers an FSUIPC interface for the Level-D Simulation 767-300 basic SDK. Currently supported: Overhead, NAV1, NAV2 and the part of the AFDS(reading state vars only). For IOcards users I have also made available all the variable definitions for the extra FSUIPC offsets for Level-D.Goto my website, downloads page.I welcome your comments and/or bug reports.Have Fun!Nicowww.nicokaan.nl

Tnx for sharing your programm with usYour site is an inspiration scourse for all of us and as always your are many steps ahead Hopefully the LVL-D will be fully interfacable soon and we will have some exelent alternative to PMRegards

Hi NicoJust want to express my gratitude for your work on this and your generosity in making all this available to those of us who are not quite up to figuring all this out ourselves. You have inspired my own and many other projects and if ever I can help you out with anything in any way just shout.Thanks Again

Thank you so much for all the time and effort you have put into this project.And most of all, thanks for sharing it with the rest of us.Regards,George DorkofikisAthens, Greecehttp://www.ldsflyingclub.com/lsd1.jpghttp://www.precisionmanuals.com/images/forum/betaimg.jpg

yoss, ian and george,Thank you for the kind words, it's my pleasure!Please try 'every corner' of my program! Find the bugs, if any ;-) ;-)I'm very curious about your findings.As you can see I have taken about 90% of the SDK, the things that are of immediate use. I did not take variables representing the physical position of some switches (like the sby_pow_swith, ext_pow_switch, ... and so on). I did not see any use for it in my sim at this moment in time.If you guys have a specific wish, do not hesitate to mail me. It's now a piece of cake to put an extra variable in.Regards,Nicowww.nicokaan.nl

Hi guys,I have just made available version 2.02. Level-D SDK support now almost complete!Only 3 vars missing, and writing MCP IAS and MCP vspeed. For the latter I await user requirements regarding the specs of the interface..Regards,Nicowww.nicokaan.nl

Hi Nico!Great news! Thank you very much!Concerning Vertical speed, I think an implementation as the default should be ok for everyone. I don't remember how the default works but I think it's using -xxxx to +xxxx.Regards,George DorkofikisAthens, Greecehttp://www.precisionmanuals.com/images/forum/betaimg.jpg

Ok, i'll do that.And what about IAS/Mach?Nicowww.nicokaan.nl

That's a very good question!...Let me think about it how to cooperate with the c/o button...FSBUS is a bit tricky on this. How would IOCards handle it ?George DorkofikisAthens, Greecehttp://www.precisionmanuals.com/images/forum/betaimg.jpg

>Let me think about it how to cooperate with the c/o button...>FSBUS is a bit tricky on this. How would IOCards handle it ?I have studied examples in the IOCards Annex II, Programming and Configuration Manual, a little bit:It looks as if you need two variables in the interface, one for setting IAS (0..400) and one for setting Mach (0..95). In IOcards you can define two logical rotaries that are mapped onto one physical rotarie but take these different variables as input. You can also define two logical displays that are mapped onto one physical display, but one is 'layout' in mach (with a dot) and one in IAS. Depending on the state of the SEL button, IOcards is able to make one logical pair (Rotarie and Display) active... Sound logical heh ;-)I guess I'll take the approach of two variables in the interface ... allright?A problem that still remains to be solved is the state of the SEL button. That's not in the SDK interface, so I guess you remember that state yourself, by keeping track of the button commands you give (by toggling 0x0530 Bit 3)...Nicowww.nicokaan.nl

You still use FSBUS??? How do you do for the overhead?? You have enough inputs and outputs for the overhead from FSBUS??Thanks.Roberto

>You still use FSBUS??? How do you do for the overhead?? You>have enough inputs and outputs for the overhead from FSBUS??I don't use FSBUS, but George does...For FSCONV it does not matter, any system that can work with FSUIPC (IOCards, FSBUS, ... ) can do the trick.Nicowww.nicokaan.nl

I think the question was addressed to me...Yes, I'm still using FSBUS, no overhead head, but it's in the future plans after the FMC.But lately I'm seriously thinking of selling my entire FSBUS setup and switch over to IOCards. From what I read they need less hardware and the software is much more flexible, although harder to configure.I'll wait for the new FSBUS software and I'll decide after I try it.As it stands FSBUS 2.2 has problems that prevent me to fully utilize my current hardware.George DorkofikisAthens, Greecehttp://www.precisionmanuals.com/images/forum/betaimg.jpg

It's the more logical approach and that's what I was going to propose.FSBUS can't do those nice allocations (at least not the current version) so I'll have to figure out another way.I'll send you an email later today what I managed to work in the AFDS section and what doesn't work.Cheers!George DorkofikisAthens, Greecehttp://www.precisionmanuals.com/images/forum/betaimg.jpg