Overhead with InterFaceIt

[jeehell]

The same assumption is used. For the middle position, use the same action but with sw up event.

[dcutugno]

The same assumption is used. For the middle position, use the same action but with sw up event.

Ok thanks, now the no smoking work, but the Emer EXT LT is a little strange, first the overhead graphic switch is not in sync with the hardware one and it seems there's a problem there in the logic can you check?

[dcutugno]

Further testing...when i start the software the position of other switches are recognised fine but the EMER EXT LT not...

[dcutugno]

The same assumption is used. For the middle position, use the same action but with sw up event.

Hi, found something... i want a switch to work in reverse order specifically the Overhead Beacon, i want to assign 1st action on SWdown Beacon OFF and in SWup Beacon On when i save it and reopen in ittcreator they are both OFF tried many times but not work...

2) sometimes after a little the led assignment action list become all white and can't select nothing minor issue...you have to restart creator to populate again.

Update 1: also RWY turnoff don't work well

[dcutugno]

The same assumption is used. For the middle position, use the same action but with sw up event.

Hi Jeehell, i think i've found where the problem lies on the 3 position switches we have to talk about the logic of them where can we talk about?

[jeehell]

here seems the good place...
I do not see what are your problems? What was possible in previous IIT version is still possible?

[dcutugno]

here seems the good place...
I do not see what are your problems? What was possible in previous IIT version is still possible?

Ok, i try to explain here but it will be better to have a chat anyway, let's start with the 3 position switches problem (we just try with no smoking OFF-AUTO-ON) here is an example that you can verify first the configuration on ITT:

Switch n.1:
On switch down: OVHD NOSMOKING OFF - assigned action switch down
On switch Up: OVHD NOSMOKING OFF - assigned action switch up

Switch n.2:
On switch down: OVHD NOSMOKING ON - assigned action switch down
On switch Up: OVHD NOSMOKING ON - assigned action switch up

Now my hardware switch is set to OFF if we start the FMGS it perform the first scan of switches and because the last switch with the same function in this case number 2, it put the overhead software switch to AUTO (different than my hardware position) this is why:

IT think scan switch 1 is it down? yes so put it to OFF
then scan switch n.2 is it down? no is up so put to AUTO
here is the bug, after the initial scan you have to make a subroutine for those type of switches where the last assumption is based on a different logic here is an example:
Scan performed so now we need a subroutine to check:
if
switch1 down and switch2 up put it to OFF
or
switch2 down and switch1 up put it to ON
Else
put it to AUTO

So it will get in sync with the first startup either i have to cycle all the switches to sync them correctly.

Hope i was clear any thoughts?

[jeehell]

I see your problem. I will try to add some more logic later on, not much time to work on FDS interface...

JL

[dcutugno]

Hi, have you corrected this?

[jeehell]

not yet..
JL