Help on FS MODULE programming SDK

[f_yunianto]

Hi my name is Yunianto,

I'm currently designing some "hardware panels/interfaces" for FS via FSUIPC. :)

I'd like to write the software (PC side) to be like FSUIPC, which is a "module" to FS2004, so can you help me on the "FS98/2000/2002/2004 Module SDK" ? so I can built my software interface like you did on FSUIPC module. :D

(How did you built the FSUIPC Module ? Can you give me some information on how to program "module" for FS2004?)

I want to write the interface’s software to be a FS-Module and not a separate C or VB etc so when they start the FS the interface’s sofware will start too (like fsuipc) and no need to terminate the interface-software after the fs is closed.

Thank you for your support. :)

I promise to send you hardware samples for my graditude to your great invention "FSUIPC" :D

Regards

F Yunianto

[Pete Dowson]

I'd like to write the software (PC side) to be like FSUIPC, which is a "module" to FS2004, so can you help me on the "FS98/2000/2002/2004 Module SDK" ? so I can built my software interface like you did on FSUIPC module. :D

(How did you built the FSUIPC Module ? Can you give me some information on how to program "module" for FS2004?)

I cannot really help much. There is no offcial documentation. The main thing to realise is that Gauges are also DLL's, and also load and interface in the same way as DLLs. The only real difference is that Gauges are loaded by Panels (by reference in the Panel.CFG files), and unloaded when they are, whilst DLLs in the Modules folder are loaded initially and stay loaded.

I found this out by hacking into existing (FS) DLLs to see how they worked. You need a good disassembler (I recommend IDA) and a reasonable knowledge of Intel assembly code. A good debugger (I use Soft-Ice) is also very handy.

So, you first step is to learn to write a Gauge in C or C++ (the MS SDKs should help there), and when you have that sussed, see how to make it run as a DLL in the Modules folder.

There's another thread here somewhere which did contain a link to a sort of "module builder" kit, but, sorry, I can't find it offhand. It is still here though, I've not deleted anything.

Regards,

Pete

[f_yunianto]

Thank you very much for your help Mr. Dowson :D

The main problem for developer (external program for FS via fsuipc) is to start end close automatically with the FS.

So maybe you could add a function in your next FSUIPC to start external Softwares/programs and kill it when FS is shutting-down. :D

Or maybe just to start them, and the external software could kill itself.

And maybe a separate INI file to list the softwares/programs so external softwares/programs can register itself while installing itself. :wink:

This will help us alot so we can produce better products with less efforts (and time & cost). :wink: :D

And offcourse will boost more product innovations using FSUIPC product, and finally increase FSUIPC selling in the future.

There should be a FSUIPC Developer Conference (Intl) in the near future. :)

Regards,

F Yunianto

[Pete Dowson]

So maybe you could add a function in your next FSUIPC to start external Softwares/programs and kill it when FS is shutting-down. :D

That facility already exists, and has done for a long time now. There is even a utility program kindly provided by Jose Oliveira to edit the FSUIPC.INI file for you (see http://www.schiratti.com/dowson).

Please refer to the Advanced User's guide to FSUIPC, check the section headed "Programs: facilities to load and run additional programs".

Regards,

Pete

[f_yunianto]

Ups.. sorry :D

Thanks then.