Setting ADF freq to 17XX.X fails

[Daniel Delande]

I am currently writing an application that drives NAV settings. FSUIPC version is 3.201 and FS version is 2004. I have no problem to change frequencies except the ADF one. I change the ADF frequency by reading offsets 0x034C and 0x0356 (these offsets actually reflect FS ADF frequency), modifying them as needed, and writing them back. This works OK except when the frequency I want to write ranges from 1700.0 to 1799.5. I can change and display these frequencies by clicking on the panel, but no way to do it through FSUIPC (but once they are modified manually, I can read the correct values through FSUIPC).

As far as I know, the 'official' range of ADF frequency is 190.0/1799.5 kHz.

I tried several combinations with no success:

- write and process 0x034C, then write and process 0x0356.

- write and process 0x0356, then write and process 0x034C.

- write 0x034C, then write 0x0356, then process.

- write 0x0356, then write 0x034C, then process.

Any suggestion?

Daniel Delande (d147@tiscali.fr)

[Pete Dowson]

Sorry for the delay in replying -- I've been on holiday with no Internet access. I'm just trying to catch up with an enormous backlog now!

This works OK except when the frequency I want to write ranges from 1700.0 to 1799.5. I can change and display these frequencies by clicking on the panel, but no way to do it through FSUIPC (but once they are modified manually, I can read the correct values through FSUIPC).

As far as I know, the 'official' range of ADF frequency is 190.0/1799.5 kHz.

Maybe. but in FS95, 98, 2000 and (as far as I know) 2002 I am fairly sure the supported range was 200.0 to 1699.9 (in increments of 0.1). I submitted a bug report to MS for this years ago. Maybe FS2004 has partly corrected this error ...

... however, evidently not quite!

FSUIPC doesn't actually perform any checking on the values at all. What actually happens when you try to write 1700 + ?

All FSUIPC is doing is using the FS controls:

ADF_HIGHRANGE_SET and

ADF_LOWRANGE_SET

Maybe you can experiment with these in the FSUIPC Keys or Buttons pages?

For ADF2 those don't exist, so FSUIPC uses:

ADF2_COMPLETE_SET

Maybe the equivalent ADF1 version of this works better? Please try things out and let me know. If the newer control works better I can make the change (for FS2004 only) in the next version of FSUIPC.

Regards,

Pete

[Daniel Delande]

Thank you for answering. By the way, you should not be sorry for delay in replying, holidays are legitimate.

What actually happens when you try to write 1700 + ?

I found 2 cases:

1. starting from 1600.0, writing 1700.0 has no visible effect on the panel, readback through FSUIPC shows transiently the written value, then the original value.

2. starting from 0100.0, writing 1700.0 makes the panel display 1100.0.

Please try things out and let me know

Unfortunatly, no valuable result.

Since you had already identified the bug, I think there is not much to do with it, and honestly, I am not sure it is worth spending much effort on the topic. As for me, I'll set wrap-around at 1600.0 and forget supporting higher frequencies.

Thanks again,

Daniel Delande

[Pete Dowson]

Unfortunatly, no valuable result.

But what about ADF2 -- if that accepts the higher values maybe I can make FSUIPC do it too for ADF1?

I'll try things myself next week. This weekend I've a lot of sorting out to do to get myself "back in the groove" so to speak! :-)

Regards,

Pete

[Craig Phillips]

How do you write to FSUIPC in Visual Basic?

[Pete Dowson]

How do you write to FSUIPC in Visual Basic?

Check the VB sections of the SDK. Other than that I can't really help, not knowing VB -- but there are lots of folks here who will help with specific questions, just not a whole tutorial.

Regards,

Pete

[Daniel Delande]

But what about ADF2

I cannot test that, since I have never seen any panel with 2 ADFs, yet.

Regards,

Daniel Delande

[Pete Dowson]

I cannot test that, since I have never seen any panel with 2 ADFs, yet.

I was only thinking of whether it was possible to set 17xx.x to ADF2 and have it "stick" (i.e. read-back correctly). You don't need an actual gauge -- if it sticks then the gauge, if one existed, would have to agree in any case.

:)

No matter, I will check it here and get back to you.

Regards,

Pete