Jump to content
The simFlight Network Forums

Recommended Posts

Posted

Hey,

I would like to get my system time zone to be set to the FS time zone (so that my saitek yoke shows the right local time). I was thinking of making a Visual Basic 2010 program to read the time zone data from FSUIPC and set that value to the system time zone.

I have been programming smaller projects before but nothing with FSUIPC and I think/know that this will be much more complicated than my earlier projects.

So I need some help..

BTW: I'm using FS9

1 Can I use a Visual Studio 2010 Form Application?

2 How to connect the program to FSUIPC? (I have searched through some internet pages and .pdf files, but I could not find a real step-by-step tutorial)

3 What is the basic coding to read the time zone variable from FSUIPC and in what format would this be read?

More questions will follow :)

Roeney

Posted

I would like to get my system time zone to be set to the FS time zone (so that my saitek yoke shows the right local time).

Wouldn't you want Zulu time, rather than Local? Pretty much all aircraft operations (certainly all airliner operations) use Zulu time.

I was thinking of making a Visual Basic 2010 program to read the time zone data from FSUIPC and set that value to the system time zone.

The only "time zone" data there is available is the difference between local and Zulu time. Is that what you mean? Or you could simply read the local time?

For your other questions, assuming you've already referred to the FSUIPC SDK documentation, I would refer you to Paul Henty's .Net interface. There's another thread which may help too,

Connecting My program to Fsuipc to FsX

Regards

Pete

Posted

Well, my thought behind this was that I could see the Zulu time on the panel in FS, and I thought it would be fun to see the local time on the yoke.

And since I use FS TimeSync, I figured that the system time zone had to be adjusted. Both because the FS time is 'slower' and because it would be a circle (FS gets time from system, and system gets time from FS) that may cause some trouble.

And yes, if that's the only time zone data, i would have to calculate the difference.

Maybe it's too much work for such a small thing :P

Posted

And since I use FS TimeSync, I figured that the system time zone had to be adjusted. Both because the FS time is 'slower' and because it would be a circle (FS gets time from system, and system gets time from FS) that may cause some trouble.

Not sure what you mean there. FS maintains both Zulu and Local time, the latter depending where you are flying. Your computer's system time is the time at your computer, not necessarily where you are flying. Any timesync function should be working on Zulu time in any case, and the underlying fixed measure.

And yes, if that's the only time zone data, i would have to calculate the difference.

Sorry, I'm lost again. As I said you can read Zulu time, time offset and Local time, all separately available. Please check the offset lists.

Pete

Posted

Sorry for not being very clear

I think you are right, but I'll try to clarify my thoughts

Ehm, how to say this right..

FS TimeSync sets FS Zulu time to match the system's Zulu time, right?

The system's 'local time' equals the system's Zulu time corrected with time zone.

The FS local time equals the FS Zulu time corrected with the time offset (calculated by FS)

Now if i would set the system Zulu time to the FS local time, the system would correct that with the time zone.

FS TimeSync would then set the FS Zulu time to the system's Zulu time (which is the FS local time), thereby creating a circle.

So I thought it would be easier to have FS TimeSync to match the Zulu times, and my own program to match the Time zone correction (time offset).

I hope it's understandable now :)

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.