Software Problem when using FSX instead of FS2004

[Snooky]

Hello there,

we recently decided to use FSX instead of FS2004, just because it looks much better.

In FS2004, we used to assign Hardware Buttons to FS Functions, using FSUIPC and FSHWPanel ( http://www.familienvater-cockpit.de/inde/Software ).

FSHWPanel can control an IO-Warrior from Codemercs.

Now we bought FSUIPC4 and tried to make FSHWPanel work with it, but we always get a strange error message we don't understand.

In German, the error is "Fehler bei Bereichsprüfung". In English it's maybe something like "Error while range testing" or "Error testing range".

We google'd and found some people having the same problem, but with many other programs having nothing to do with FS or FSUIPC.

FSHWPanel is written in Delphi.

Maybe someone encountered a similar Error and is able to help us.

Thank you in advance,

Snooky

[Pete Dowson]

In FS2004, we used to assign Hardware Buttons to FS Functions, using FSUIPC and FSHWPanel ( http://www.familienvater-cockpit.de/inde/Software ).

FSHWPanel can control an IO-Warrior from Codemercs. Now we bought FSUIPC4 and tried to make FSHWPanel work with it, but we always get a strange error message we don't understand.

In German, the error is "Fehler bei Bereichsprüfung". In English it's maybe something like "Error while range testing" or "Error testing range".

There's no such error message in FSUIPC. How does this message appear? What is actually producing it -- the add-on program, or FS?

We google'd and found some people having the same problem, but with many other programs having nothing to do with FS or FSUIPC.

FSHWPanel is written in Delphi.

Aha. It could be some incompatibility with an installed Windows or Delphi library then -- though why it would be different with FSX compared to FSX I've no idea.

Maybe someone encountered a similar Error and is able to help us.

It may be a generic range check error in the Delphi program itself. I'm afraid you will need to contact the support for FSHWPanel. Maybe it is something quite simple, like the version number of FS or FSUIPC being out of the range they catered for. I'm sure they will be able to fix it if it is reproducible.

Regards

Pete

[Snooky]

Thank you very much for your answer. We'll try to isolate the procedure or function causing the error.

But, generally spoken, FSUIPC4 is operating the same way FSUIPC does?

This means, the provided functions in your SDK for Delphi have the same name and work the same?

I ask this because functions like FSUIPC_Open are called in FSHWPanel.

The guy who made FSHWPanel wrote this for himself only but provided us the sourcecode. So we can't really expect real support for this program and have to find a solution on our own.

[Pete Dowson]

But, generally spoken, FSUIPC4 is operating the same way FSUIPC does?

Yes. The interface is identical. Version numbers are different, of course. There are a lot of new offsets and some of the old ones do not work, or very occasionally work slightly differently. That is all detailed in the Offsets Status document for FSUIPC4.

This means, the provided functions in your SDK for Delphi have the same name and work the same?

Yes, no difference at all. FSInterrogate itself is a Delphi program, and there are lots more, all still working fine. The interface to FSUIPC has not changed in the 10 years it has been around, and in fact it is identical to that for FS6IPC before it, in FS98.

The guy who made FSHWPanel wrote this for himself only but provided us the sourcecode. So we can't really expect real support for this program and have to find a solution on our own.

Ah, if you have the source code it should be very easy to find the problem and fix it. simply compile it in Debug mode, run it with debugging enabled, and when the failure occurs, see why.

If it is something simple like unexpected version numbers you should be able to find that by inspection of the code. If it might be some other offset value which upsets it, try enabling IPC read and write logging in FSUIPC4's logging tab, see what it does prior to the crash.

Regards

Pete

[Blitz3]

Hi Snooky,

any news in your described problem? I ask, because I just ran in the same error, using FSHW and FSX.

Regards

Blitz3

[dika]

Hi, I still have exact the same trouble with FSX/FSHW. - I already contacted the developer of the FSHW-program. A few years ago he already was very helpful by guide me through th installation of the software FSHWpanel. I also build up a physical switch board and used this already satisfied and succesfully with FS2004. If anyone knows any help - please let me know. greetings