Go Flight

[Bob Reed]

Hi guys. With the advice and help given here by Thomas and Peter, I have this working now. Thanks guys!

[eudoniga]

Hello Peter,
just to let you know that installing the last GF modules, released last july, did the job.
Without a precise reason, I went on thinking that it was enough to keep FSUIPC updated ...
Thanks !

[Peter Dowson]

Hello Peter,
just to let you know that installing the last GF modules, released last july, did the job.

Good! glad that's sorted!

Pete

[eudoniga]

What's the way - if any - to drive the Systems from a GF T8/P8/RP48 by poking directly all PM Offsets (as in sysvars.txt) and not just those of the MCP, CDU and GC listed on the FSUIPC advanced user's guide ?

[Peter Dowson]

What's the way - if any - to drive the Systems from a GF T8/P8/RP48 by poking directly all PM Offsets (as in sysvars.txt) and not just those of the MCP, CDU and GC listed on the FSUIPC advanced user's guide ?

You can set any offset, whether whole Bytes, Words (2-bytes), Dwords (4-bytes) or Doubles (64-bit floating point) using the appropriate "Offset XXXX Set" control. It is documented, and I think there are even examples in the User Guide.

You can clear and set individual bits using a mask as parameter and the "Offset XXXX Setbits" or "Offset XXXX Clrbits" controls.

Regards

Pete

[eudoniga]

What will I say, mr. Dowson ...

THANK YOU for being still SO patient with all those who don't read the docs THOROUGHLY enough !!!

[eudoniga]

... but I don't get to switch on and off the single bits (talking about button programming via FSUIPC user interface).

For setting bytes, I specify the hex code as the first parameter, and then the desired value (0, 1, 2 ...) in the other input box, and it works.

For single bits, I tried using Offset Byte Setbit (or Clrbit or ToggleBit), with the offset hex code (taken from PM sysvar.txt listing) as the first parameter and ... how about the second one (which, I guess, is the one related to the bit to be set/cleared/toggled) ?

Is it a mask that must be input ? In which format ?

This time I previously went to fetch the documentation, but reading top of page 35 of FSUIPC Advanced User Guide wasn't clear enough for a poor, untechnical, soul like mine ... alas !!!

Sorry, mr. Dowson ...

[Thomas Richter]

... but I don't get to switch on and off the single bits (talking about button programming via FSUIPC user interface).

For setting bytes, I specify the hex code as the first parameter, and then the desired value (0, 1, 2 ...) in the other input box, and it works.

For single bits, I tried using Offset Byte Setbit (or Clrbit or ToggleBit), with the offset hex code (taken from PM sysvar.txt listing) as the first parameter and ... how about the second one (which, I guess, is the one related to the bit to be set/cleared/toggled) ?

Is it a mask that must be input ? In which format ?

This time I previously went to fetch the documentation, but reading top of page 35 of FSUIPC Advanced User Guide wasn't clear enough for a poor, untechnical, soul like mine ... alas !!!

Sorry, mr. Dowson ...

Hi

The second number is just the value of the Bit, e.g.
Bit 0 = 1
Bit 1 = 2
Bit 2 = 4
Bit 3 = 8
Bit 4 = 16
Bit 5 = 32
Bit 6 = 64
Bit 7 = 128

So if you read in sysvar.txt
5628 .0 Batt1
5628 .1 Batt2
5678 .4 APUBleed

you use in FSUIPC for Byte SetBit / ClrBit
1/ Batt1
Offset 5628 and value 1

2/ Batt2
Offset 5628 and value 2

3/ APUBleed
Offset 5678 and value 16

[eudoniga]

I get it now !!!

This means that - using the intermediate values - you can set/clear/toggle more than one bit at a time ?

[Thomas Richter]

I get it now !!!

This means that - using the intermediate values - you can set/clear/toggle more than one bit at a time ?

I never tried it, but I would say yes.
I think if you like to switch e.g. Batt1 and Batt2 to ON or OFF at the same time, you use value 3.
But easy try it to see what happens.