I've completely read all of the information is this thread (many times 😄)

Spoiler

 

I have noticed the "double press" problem but the most irritating thing for me is when I press the DTO button on the 750, it activates the 650 DTO page. Clearly I have something not right in the f1vc files, but I have cut'n'pasted contents from several of the posts in the above thread with the same result.

I was hoping one of the many members here that are far more knowledgeable than me could lend some insight.

Here is the f1vc.xml I currently use - thanks for listening (or reading)

Spoiler

<Gauge Name="f1vc" Version="2.04">

<!-- Reality XP GTN Buttons Bridge -->

<!-- Bridges Reality XP GTN 750/650 Touch with f1 3D bezel -->

<!-- Credits: Reality XP, Sean Moloney and Ryan Butterworth -->

<Element>
  <Select>
    <Value>
        (L:F1GTNMOUSE,bool) 0 !=
        if{

     (L:F1GTNMOUSE, number)  129539 ==  if{
     1 (>K:GPS_DIRECTTO_BUTTON)
     0 (>L:F1GTNMOUSE, number) }

    (L:F1GTNMOUSE, number)  129537 ==  if{
    1 (>K:GPS_MENU_BUTTON)
    0 (>L:F1GTNMOUSE, number) } }

   (L:F1GTNMOUSE,bool) 0 !=
        if{
            (L:F1GTNMOUSE,bool) 0x0001FA01 - sp0
            l0 28 / int sp1 l0 28 % sp0
            <!-- map F1 model to RXP GTN unit -->
            <!-- use: 8 0 8 0 for 652=unit2, 651=unit1, 752=unit2, 751=unit1 -->
            <!-- use: 8 8 0 0 for 652=unit2, 651=unit2, 752=unit1, 751=unit1 -->
              8 8 8 0
              4 l1 case 4 2 l0 1 &amp; ? + sp1
            l0 0 == l0 1 == or if{ l1 (>K:GPS_MENU_BUTTON) }
            l0 2 == l0 3 == or if{ l1 (>K:GPS_DIRECTTO_BUTTON) }                
            l0 4 == l0 10 == or if{ l1 8 &amp; (>K:GPS_BUTTON2) }
            l0 6 == l0 11 == or if{ l1 8 &amp; (>K:GPS_BUTTON3) }
            l0 8 == l0 9 == or if{ l1 (>K:GPS_BUTTON1) }
            l0 12 == l0 18 == or if{ l1 8 &amp; (>K:GPS_GROUP_KNOB_DEC) }
            l0 14 == l0 19 == or if{ l1 8 &amp; (>K:GPS_GROUP_KNOB_INC) }
            l0 20 == l0 26 == or if{ l1 8 &amp; (>K:GPS_PAGE_KNOB_DEC) }
            l0 22 == l0 27 == or if{ l1 8 &amp; (>K:GPS_PAGE_KNOB_INC) }
            l0 24 == l0 25 == or if{ l1 (>K:GPS_CURSOR_BUTTON) }    
            l0 16 == l0 17 == or if{ l1 (>K:GPS_CURSOR_BUTTON) }    
            0 (>L:F1GTNMOUSE,bool)            
        }           
    </Value>      
  </Select>
</Element>
</Gauge>

 

Edited July 17, 20205 yr by RXP

I assume that you have "Use Simulator GPS commands" set for the 750..

If you also have it set for the 650, try deselecting that option.

Thanks Bert - that did it 😄

It also got the HOME button working properly as well.

17 hours ago, DavidP said:

            <!-- map F1 model to RXP GTN unit -->
            <!-- use: 8 0 8 0 for 652=unit2, 651=unit1, 752=unit2, 751=unit1 -->
            <!-- use: 8 8 0 0 for 652=unit2, 651=unit2, 752=unit1, 751=unit1 -->
              8 8 8 0

Hi David,

Please make sure to use one or the other. Although 8880 is not invalid, it might not be what you're looking for. When you're analyzing the possible, these are the remaining 2 combinations.

The reason for these values is because the 'f1' source works as device+unit# pairs (there are 4 possible sources) and the 'rxp' destination works as unit# (there are 2 possible destinations).

Furthermore, is is allowed to use dual #1 with the other, but it is not possible with RXP. Dual GTN setup are always RXP#1+RXP#2 (with RXP being either GTN or GNS by the way).

Therefore, depending on how the aircraft is specifically coded, especially those with dual GTN, you might have to map a source GTN unit#1 to a destination unit#2 and there is no automatic way to know whether the aircraft vendor is using twice a #1 GPS in his aircraft.

Hi Jean-Luc

Thanks for the insight. The 8880 was me experimenting to see what various combination of those numbers do. At the moment I can't really determine what they do! I have a rudimentary knowledge of C++ and VB programming but the xml code has me beat - I have no idea what it means 😄.

Can you give some advice on where to go to try and understand it?

14 hours ago, DavidP said:

Can you give some advice on where to go to try and understand it?

I've tried already explaining in my post above LOL!

I guess I'm not good enough at teaching and I'm glad I'm not working in a school!

Kidding apart, this has nothing to do about programing at all, just configuring.

The 0 is meant for RXP GPS #1 (whichever GPS it is but a unit #1), 8 is meant for RXP GPS #2. These are the 'command modifier' values described in the RXP User's Manual which allow 'redirecting' the same command, say GPS_BUTTON1, to either the unit#1 or unit#2.

Most aircraft will just use "8 0 8 0" because this maps any f1 #1 to any RXP #1 and any f1 #2 to any RXP #2.

Those aircraft for which the vendor decided it would make more sense to offer dual f1 GTN #1 (750#1 + 650#1) - I'm wondering why it is better than 750#1+650#2 but it is just me - you have to redirect one or the other to a RXP #2 for the integration to work. This is where you'd use "8 8 0 0".

 

So Trick Question here.  Is 0 8 0 0 ever valid?  And how about 0 0 0 8?

Hint: Configure a Milviz 310 Redux with one GTN 750 and one GTN 650.  Now if I understand correctly, one of the GTN's must be a _1 and the other a _2.  Is that correct?  So the above combination of one 750 and one 650 would have to be a 750_1 and a 650_2; -or- a 750_2 and a 650_1.  Is that a correct statement?  If so, what code works for a 750_1 and 650_2 combination?   And what code works for a 750_2 and 650_1 combination. 

Spoiler

This is what works in the Milviz Redux for a 750_1 and a 650_2 combination..  "0 8 0 0" 
If I switch to a 750_2 and 650_1 combination I confirmed "0 0 0 8" is the code that works.

In the 310 Redux I do have to press the keys twice, but they work.

 

Edited July 18, 20205 yr by fppilot

Just to be clear, please review the comments:

On 7/16/2020 at 7:57 PM, DavidP said:

            <!-- map F1 model to RXP GTN unit -->
            <!-- use: 8 0 8 0 for 652=unit2, 651=unit1, 752=unit2, 751=unit1 -->
            <!-- use: 8 8 0 0 for 652=unit2, 651=unit2, 752=unit1, 751=unit1 -->

 

• There are 4 distinct sets of commands in the f1 (in the comments: 751,752,651,652)
• There are 2 distinct sets of commands in the RXP (##1,##2)

if you're using "0 0 0 8" this means:

• f1 commands set for 751 are redirected to any RXP #2
• f1 commands sets for any of (652,651,752) are redirected to any RXP #1.

You can represent this as an array too:

  \ from | 652   651  752  751 
to: \          |
           \ --|---------------------
RXP #1   |  0     0    0    x
RXP #2   |  x     x    x    8

Edited July 18, 20205 yr by RXP

In addition: even though the aircraft vendor config tool is mentioning a configuration with a 650 at the top (#1) and 750 at the bottom (#2) it might well be hard coded to use a f1 751 command set... The key is only in what is hard coded in the 3D model regarding the set of f1 commands the aircraft is using for each GTN in the panel.

Edited July 18, 20205 yr by RXP