Panel_ID as a condition?

[mtjoeng]

hi

digital aviation cheyenne has 5 main panels MAIN_PANEL .. MAIN_PANEL_ALT4

I would like to share buttons for the WeatherRadar (CoPilot's) with the Trimble (Main), depending on the panel showing

any chance to have the active panel_ID as a button define condition?

thx

mtjoeng

in a state of confusion :shock:

[Pete Dowson]

I would like to share buttons for the WeatherRadar (CoPilot's) with the Trimble (Main), depending on the panel showing

any chance to have the active panel_ID as a button define condition?

Where would I get the active panel ID from?

Without knowing the current panel ID, the only thing you can do is make the button like a toggle switch by using its flag (if it is a regular joystick button) or any spare flag.

Regards

Pete

[mtjoeng]

I've honed my 'condition' problem to the Cheyenne Trimble GPS knob, with an Outer en Inner ring.

This is new to me, and I'm quite lost with Key 'condition'

My VRinsight MCP accepts keystrokes for all its dials and buttons

So this one dial can be pushed also, this I want to use to toggle the output of the dial to the outer or inner ring

so, define dial's turn right, I'll define the key CTRL-TAB-W (87,26)

and use same dial's push, to toggle a flag condition either to point to OuterDial-R macro, or InnerDial-R macro

the dial's push (toggle flag 1005) will be CTRL-TAB-Z (90,26), for virtualbutton 15,16 (4111)

and so, I suppose, things would look something like:

[Keys.Piper PA31T Cheyenne]

..

32=90,26,1005,4111 ; CTRL-TAB-Z=90,26, toggle flag virtualbutton 15,16

33=Wxxx=yyy 87,26,M5:24,0 ; CTRL-TAB-W=87,26 , macro 24 OuterDial-R

34=Wxxx=zzz 87,26,M5:25,0 ; CTRL-TAB-W=87,26 , macro 25 InnerDial-R

and I'm stuck with xxx yyy and zzz

and I've looked at the descriptions of offsets 3210, 2910 and the like, but I'm quite lost

appreciate your pointers what xxx yyy and zzz should read

unless I've missed something, and all above is redundant (oops)

thx

MT

[Pete Dowson]

I've honed my 'condition' problem to the Cheyenne Trimble GPS knob, with an Outer en Inner ring.

This is new to me, and I'm quite lost with Key 'condition'

Me too. What, precisely, do you mean by "key condition"?

so, define dial's turn right, I'll define the key CTRL-TAB-W (87,26)

You aren't using buttons. You aren't trying to do conditional key programming in FSUIPC, are you? Phew!

[Keys.Piper PA31T Cheyenne]

32=90,26,1005,4111 ; CTRL-TAB-Z=90,26, toggle flag virtualbutton 15,16

Well, okay so far. But there's no flag condition key programming facilities in FSUIPC, so there's no way to use that flag if you are only programming keys. All of FSUIPC's flag are aimed at buttons.

The only way, using keys, would be to replace the Flag setting with an Offset Byte ToggleBits using a user-offset like x66C0 and bit 1, say (i.e. 1 as parameter). Then in:

33=Wxxx=yyy 87,26,M5:24,0 ; CTRL-TAB-W=87,26 , macro 24 OuterDial-R

34=Wxxx=zzz 87,26,M5:25,0 ; CTRL-TAB-W=87,26 , macro 25 InnerDial-R

your W parts would be (B not W)

B66C0&1!0 and

B66C0&1=0.

Regards

Pete

[mtjoeng]

errr

32=90,26,x510066C0,x00030001 ;togglebits ctrltabZ

33=B66C0&1!0 87,26,M5:24,0 ;outerL ctrltabW

34=B66C0&1=0 87,26,M5:25,0 ;innerL ctrltabW

like this :?:

mt

[Pete Dowson]

32=90,26,x510066C0,x00030001 ;togglebits ctrltabZ

Err... where on Earth are you getting this stuff?

x5100nnnn is clearly listed as "Offset Byte Cyclic Increment". What do you want to select that for, and then label it incorrectly as "togglebits"? You've even given a limit (3). Why?

Pete

[mtjoeng]

Err... where on Earth are you getting this stuff?

Its the example "FSUIPC4 for Advanced Users.pdf" page 19, and I was wondering what x00030001 was not in Hex :)

not to mention, I figured, x5100 could cycle from 1 to 0 and back :D (and would ask if it could :D )

x5100nnnn is clearly listed as "Offset Byte Cyclic Increment".

saw the list, please bear with the novice. Thought it belonged to the Project Magenta GC Controls specific

What do you want to select that for, and then label it incorrectly as "togglebits"? You've even given a limit (3). Why?

It's the example (of which I can't see the syntax, exactly)

Sort of suggesting, to see if it was anywhere in the ballpark. At least it came to somewhere in that same list :D

this then:

32=90,26,x0D0066C0 ;togglebits ctrltabZ

33=B66C0&1!0 87,26,M5:24,0 ;outerL ctrltabW

34=B66C0&1=0 87,26,M5:25,0 ;innerL ctrltabW

If the above would be better, I even dont quite grasp why

B66C0&1!0

B66C0&1=0

is there. &1=0 is the declaration, and 1!0 is the 'toggle between 1 and 0?

anyway, doesnt work

32=90,26,x0D0066C0 wont toggle, neither

32=90,26,x0E0066C0 (word)

32=90,26,x0F0066C0 (Dword)

the knob sticks to (34=B66C0&1=0 87,26,M5:25,0) InnerKnob

where is this syntax from?

It should all fit into: n=key,shifts,control,parameter , but from this to Cx510066C0,x00030001 or B66C0&1!0 / B66C0&1=0 is rather a big leap.

(I had 6 months of ALGOL (yes, a long time ago) at university, then the usual Pascal with my first computer the the Osborne 1(!) running on CP/M(!), and more recently, of course the amateure (in the good sense) PHP to maintain my website:)

So never the Hex and Offset stuff (in my world (I'm a manager, trained in construction) that's close to Macro Assembly, and I considered that a deadly virus).

It should all be rather basic stuff, perhaps you can suggest what I should read, to get a grasp of these basics, so I can at least get familiar with the syntax. Would really appreciate that.

I could've asked my brother - a mathematician - but unfortunately he has passed away :(

Thx, mt

[Pete Dowson]

Err... where on Earth are you getting this stuff?

Its the example "FSUIPC4 for Advanced Users.pdf" page 19

Yes, but it does say there "Here the value in the Byte at offset 66C0 is cycled from 0–3, and back to 0", zo it isn't the Togglebits control I advised and you commented.

Why not just assign this in the FSUIPC drop down? You don't need to look up stuff in the Advanced User's guide to enter these commands.

not to mention, I figured, x5100 could cycle from 1 to 0 and back :D (and would ask if it could :D )

It can do, but it's a bit pointless.

anyway, doesnt work

32=90,26,x0D0066C0 wont toggle, neither

Because you've not told it which bit(s) to toggle! Please read my original advice on this -- you need a parameter, like 1.

I cannot keep repeating things. Please read more carefully!

Pete

[mtjoeng]

Why not just assign this in the FSUIPC drop down? You don't need to look up stuff in the Advanced User's guide to enter these commands.

40=90,26,x0D0066C0,x01 ;from the dropdown

edited ini:

41=B66C0&1!0 87,26,M5:24,0 ;outerL ctrltabW

42=B66C0&1=0 87,26,M5:25,0 ;innerL ctrltabW

43=B66C0&1!0 86,26,M5:23,0 ;R

44=B66C0&1=0 86,26,M5:26,0 ;R

Works!

toggles now between inner and outer dial

then FSuipc magically rewrites the ini:

41=B66C0&111 87,26,M5:24,0

42=B66C0&1111=x0 87,26,M5:25,0,26,0

43=B66C0&11 86,26,M5:23,0

44=B66C0&1=x0 86,26,M5:26,0

thats fantastic

any documentation about this syntax B66C0&1!0 B66C0&1=0 &1111?

this got me curious now

thx

mt

[Pete Dowson]

then FSuipc magically rewrites the ini:

41=B66C0&111 87,26,M5:24,0

42=B66C0&1111=x0 87,26,M5:25,0,26,0

43=B66C0&11 86,26,M5:23,0

44=B66C0&1=x0 86,26,M5:26,0

Sorry, but there's no way FSUIPC has any code in it whatsoever which "magically" does anything of the sort. Thast looks like corruption of the file. Is your hard disk okay? what version of FSUIPC are you using?

any documentation about this syntax B66C0&1!0 B66C0&1=0 &1111?

There's no such syntax. The normal syntax, as documented, is:

Xxxxx&

where X is the size (like B for Byte, W for Word)

xxxx is the offset

&mask is option masking of value from the offset, with "mask" being the mask

Condition is, for example ! for not equals and = for equals

Value is what you are comparing the result with.

This is in the documentation.

Pete

[mtjoeng]

Sorry, but there's no way FSUIPC has any code in it whatsoever which "magically" does anything of the sort. Thast looks like corruption of the file. Is your hard disk okay? what version of FSUIPC are you using?

well, I have a liitle Heinzelmännchen in my computer, and its running FSuipc hard

added another toggle, between Radar Altitude and Cockpit Altitude (pressure):

6=B66C1&1=0 54,26,M5:55,0

7=B66C1&1=0 55,26,M5:56,0

8=56,26,x0D0066C1,x01

18=B66C1&1!0 55,26,M5:57,0

19=B66C1&1!0 54,26,M5:58,0

and my little Heinzelmännchen changed this now to:

6=B66C1&11111111=x0 54,26,M5:55,0

7=B66C1&11111111=x0 55,26,M5:56,0

8=56,26,x0D0066C1,x01

18=B66C1&11111111 55,26,M5:57,0

19=B66C1&11111111 54,26,M5:58,0

the other inner/outer dial now changed to:

40=90,26,x0D0066C0,x01

41=B66C0&11111111 87,26,M5:24,0

42=B66C0&11111111=x0 87,26,M5:25,0,26,0

43=B66C0&11111111 86,26,M5:23,0

44=B66C0&11111111=x0 86,26,M5:26,0

seems to keep changing with every rewrite (deletes comments also :x ) of the [Keys.Piper PA31T Cheyenne] portion

??

and both work :mrgreen: :mrgreen:

using 4.520

Condition is, for example ! for not equals and = for equals

This is in the documentation.

sorry, missed that

mt

[Pete Dowson]

well, I have a liitle Heinzelmännchen in my computer, and its running FSuipc hard

No idea what a "Heinzelmännchen" is, but I'll try and reproduce this phenomenon when I get the chance.

Not many (if any?) folks use the offset conditions on keypresses. Most all of the fancy stuff is done with buttons.

deletes comments also

I don't think I allow for any comments in the [Keys...] sections in any case. All that fancy stuff was only really ever done for [buttons ...].

Pete

[mtjoeng]

It's the little guy in your garden

wears a red hat, and usually pushes a wheel barrow

wears a beard also, most of the time :D

he's quite friendly actually

takes care of my fsuipc.ini also

I think

Not many (if any?) folks use the offset conditions on keypresses. Most all of the fancy stuff is done with buttons.

More people will have a use for this when more VRinsight MCP's are sold

It's an all-in-one does-any-plane panel, sells for around 330euro 340 GBP 440 USD

have this now for a week or so, works great with the two prop Cheyenne, that has a big radio stack and ILS

and of course addon Jets

Both the Dials and Buttons do Key Presses only (and their simplified version of Mouse Presses) though, bit of a bummer

So needs plenty of - carefully planned - Key Presses. And those dials on the left, I've made - thanks to your fsuipc - to do double functions now :P

thanx

mtjoeng

[Pete Dowson]

It's the little guy in your garden

wears a red hat, and usually pushes a wheel barrow

wears a beard also, most of the time :D

Oh, "garden gnomes". We don't have any! ;-)

Pete

[mtjoeng]

apart that comments will be removed, and might have been part of the problem :(

(it cuts off the line somewhere, and leaves some redundant characters)

after a clean edit, without comments

the 1st Rewrite fsuipc does, is from

7=B66C0&1!0

8=B66C0&1=0

to

7=B66C1&1=x0

8=B66C1&1

then

7=B66C1&11=x0

8=B66C1&1

now

7=B66C0&1111=x0

8=B66C0&1111

(EDIT: seems to consolidate on this one, 1111)

so it adds 1's (trying to correct unexpected code? convert to Hex?)

and I wonder when it runs out of 1's

keeps the toggle working though, also after continues reloads of the ini :D

??

(Edit: perhaps it want the code to be

=B66C0&1111=x0

=B66C0&1111

from the start?)

mt

[Pete Dowson]

(Edit: perhaps it want the code to be

=B66C0&1111=x0

=B66C0&1111

from the start?)

No, they would have quite different meanings when, for example, testing the lights offset (0D0C) in which there are 10 bits used for different lights.

i haven't had time to look into this. If I can reproduce it, I'll fix it. Meanwhile, please be patient. i have a few urgent things to clear up first.

Thanks

Pete

[Pete Dowson]

7=B66C1&1=x0

8=B66C1&1

then

7=B66C1&11=x0

8=B66C1&1

now

7=B66C0&1111=x0

8=B66C0&1111

(EDIT: seems to consolidate on this one, 1111)

Okay. I've at last managed to find time to investigate this. It's a definite bug, and it looks like it has always been there, both in FSUIPC3 and 4 (and FSUIPC's 1 and 2 before them). Seems not many, if any, folks use these facilities! And it applies to Buttons as well as Keys. So it's a good catch indeed! ;-)

It's easy to fix and it will be fixed, along with some other things, in the next updates -- 4.523 and 3.916. I should have them ready and uploaded by tomorrow, or so.

Best Regards

Pete