GTN 750 in A2A Comanche VC knobs/buttons config request

[fppilot 4,348]

5 minutes ago, BillS511 said:

@fppilot
Are you using the following?
; uses Simulator GPS commands if true.
UseSimGpsCmds = true

It may be on for your 750 but off for the 650.

If I turned it off buttons didn't work. Turned on they worked.

BINGO!   That solved it!  Oh my lord!  Sorry for the time consumed with this.  I'd have never thought something like that was at play!  This one will be remembered, certainly!  Where's my bottle of Scotch!

Edited November 29, 2018 by fppilot

[Indy511 686]

1 minute ago, fppilot said:

BINGO!   That solved it!  Oh my lord!  Sorry for the time consumed with this.  I'd have never thought something like that was at play!  This one will be remembered, certainly!  Where's my bottle of Scotch!

Awesome!
Do you have to double click thou?

[fppilot 4,348]

4 minutes ago, BillS511 said:

Do you have to double click thou?

Yes, on the Home key. And to verify, as Jean-Luc suggested I moved the call to f1vc.xml into an elevated position as the last gauge in [Vcockpit01] and I incremented the gauge number correctly when doing so.  Just fixed the Comanche as well and same there. Double click.

BillS511, so now that I can use the knobs to tune freqs, is there a method with the knobs to xfer a frequency from standby to active?

Thanks so much for helping me hunt this down!

[Indy511 686]

13 minutes ago, fppilot said:

is there a method with the knobs to xfer a frequency from standby to active?

Not sure. I touch the frequencies on the screen.

[fppilot 4,348]

1 hour ago, BillS511 said:

Not sure. I touch the frequencies on the screen.

I'm just laughing at myself over the time spent. The challenge of getting the .xml to work. Then  it wasn't the .xml.  It was a setting.  Then I can now use the tuning knobs...... (drumroll....) and I still have to use the touchscreen to xfer the frequency!  Is that right? If so then who at Garmin thought that up? LOL!

[fppilot 4,348]

If I want to map a single  RXP GTN750_2

Use 0 to map the corresponding device to the RXP GTN #1, use 8 to map to the RXP GTN #2. 

So what do I identify in the table as where I put my finger to represent RXP GTN 750_1?  Is it the top line?  Or is it the bottom line in the table?  Actually, it is neither. Both lines appear to be maybes.  But neither one is. 

Here is an example.  In my A2A 182 Skylane I am using a single gauge and it is rxpGTN_750_2.  So I need an "8" somewhere in that code.  Do I put it in the fourth position (0  0  0  8)? No. To me, a non-programmer, that position appears to be for an rxpGTN_750_1.  That because that position is labeled 751 on the top, and (unit1) on the bottom.  So anything with 2 doesn't seem to fit.
 
3D model       |  652  |  651  |  752  |  751  |
    map to RXP |   #   |   #   |   #   |   #   |
               |(unit2)|(unit1)|(unit2)|(unit1)|

So here is what has had me so confused about this f1vc.xml gauge and how to code line 17.  As a consumer/user and not an .xml programmer, what got in my way  is my understanding of the RXP GPS license agreement.  Say what, you say?  Let me explain. 

With purchase of RXP GTN750 software I got two (2) instruments.  #1 being 750_1; and #2 being a 750_2. Key point here is that either of those two instances can be used as a primary gauge in a panel with two, or either can be used as a sole gauge in a single gauge panel.  Looking at the table I was seeing (unit1) as the first of my two gauges, or the primary, and (unit2) being a second gauge in a panel, or the secondary.  With that way of thinking, either 750_1 or 750_2 could be (unit1) or the primary.  But the top line (752 and 751) did not match that thinking.

3D model       |  652  |  651  |  752  |  751  |
    map to RXP |   #   |   #   |   #   |   #   |
               | 650_1=0 |650_1=0 | 750_1=0 | 750_1=0 |
               | 650_2=8 |650_2=8 | 750_2=8 | 750_2=8 |

Are these correct examples?:
(1) rxpGTN_750_2 in the panel =  0   0   0   8

(1) rxpGTN_750_1 in the panel =  0   0   0   0

(2) rxpGTN_750's in the panel, 750_1 and 750_2  =  0   0   8   0  -or-  0  0  0  8    ???

(1) rxpGTN_750_1 and one rxpGTN_650_2 in the panel = 8  0  0  0

Edited November 30, 2018 by fppilot

[Indy511 686]

2 hours ago, fppilot said:

I'm just laughing at myself over the time spent. The challenge of getting the .xml to work. Then  it wasn't the .xml.  It was a setting.  Then I can now use the tuning knobs...... (drumroll....) and I still have to use the touchscreen to xfer the frequency!  Is that right? If so then who at Garmin thought that up? LOL!

I'm looking at the Garmin 750 trainer and there is a push button (lower right small knob). It switches between the com frequency and the Nav frequency.

However in the sim the VC small knob doesn't appear to have the push function just turning. The popup small knob has the push function.

 

41 minutes ago, fppilot said:

Are these correct examples?:
(1) rxpGTN_750_2 in the panel =  0   0   0   8

(1) rxpGTN_750_1 in the panel =  0   0   0   0

(2) rxpGTN_750's in the panel, 750_1 and 750_2  =  0   0   8   0  -or-  0  0  0  8    ???

(1) rxpGTN_750_1 and one rxpGTN_650_2 in the panel = 8  0  0  0

As I understand it Jean-Luc states there can only 2 - 8's and 2 - 0's. So the above would not work.

5 hours ago, RXP said:

Use only 2x 8 and 2x 0 in the code.

In the end, you'll find out there is only 2 codes to cover all combinations: either 8800 or 8080.

 

Edited November 30, 2018 by BillS511

[fppilot 4,348]

41 minutes ago, BillS511 said:

As I understand it Jean-Luc states there can only 2 - 8's and 2 - 0's. So the above would not work.

I checked some first before posting.  I am checking more scenarios out now.

0  0  0  0   is what works for a single GTN750_1 in the A2A Skylane 182 and the A2A Comanche
0  0  0  8   is what works for a single GTN750_2 in the same two aircraft

0  0  8  0   is working perfectly in my Turbine Duke v2 with rxpGTN_750_1 as primary and rxpGTN_750_2 as secondary, and  8  8  8  0  works as well. 
0  0  0  8   is working perfectly in the TDV2 with xpGTN_750_2 as primary and rxpGTN_750_1 as secondary, and  8  8  0  8  works as well.

0  8  0  0  is what works in my Milviz Cessna 310R Redux  for a 750_1 as primary and 650_2 as secondary, all in line with the table. I just needed to see it like this to understand it. 

3D model       |  652  |  651  |  752  |  751  |
    map to RXP |   #   |   #   |   #   |   #   |
               | 650_1=0 |650_1=0 | 750_1=0 | 750_1=0 |
               | 650_2=8 |650_2=8 | 750_2=8 | 750_2=8 |

Edited November 30, 2018 by fppilot

[fppilot 4,348]

The table mod below makes it even clearer for me. There are only so many combinations. 

(1) 650 is one.  (2) 650s is another. When you have (2) 650s either one can be primary or secondary.  ex. I can have 650_2 as my primary and 650_1 as my secondary, or of course the other way around.  The same if you have an airplane where you can use (2) 750s.  In fact I just confirmed that with my Turbine Duke v2.  I swapped 750_1 and 750_2 back and forth as primary and secondary.  And I had to adjust the f1vc.xml file by changing from
0   0   8  0  -to-  0  0  0  8.

You can also have combinations of 750s and 650s if you own both and can fit them into an aircraft.  And if you do have one of each, one will be _1 and the other will then need to be _2.  My understanding is that you cannot use two _1s, or for that matter two _2s , even if one was a 750 and the other was a 650. 

The f1vc.xml must reflect what you are doing. So my example of   0  8  0  0 for my Milviz Cessna 310R Redux for a 750_1 as primary and a 650_2 as secondary, would need to change  if I instead decided to use 750_2 as my primary, and 650_1 as secondary.  It would change -to-  0   0   8  0

               |         | Only or |          | Only or |
     3D model  |  650 as |   1st   |  750 as  |   1st   |
               | 2nd GPS |   650   | 2nd GPS  |   750   |
    map to RXP |    #    |    #    |    #     |    #    |
                  |  650_1=0  |  650_1=0   |   750_1=0   |  750_1=0   |
       Value      |  650_2=8  |  650_2=8   |   750_2=8   |  750_2=8   |

 

Edited November 30, 2018 by fppilot

[RXP 2,336]

17 hours ago, RXP said:

The purpose of the "8 8 0 0" is to tell which set of f1 commands (651, 652, 751, 752) gets mapped to which RXP GTN (any GTN #1, any GTN #2).

11 hours ago, fppilot said:

3D model       |  652  |  651  |  752  |  751  |
    map to RXP |   #   |   #   |   #   |   #   |
               |(unit#)|(unit#)|(unit#)|(unit#)|

Let's recap:

• First row (3D model) is the 3D model used in the panel. It could be any of the 4 (these are 3D model embedding f1 gtn commands which are per-device-unit, thus, there are 4 sets of commands). You identify this in looking up which f1 gauges were configured in he panel.cfg
• Middle row is the code telling how to remap from f1 3D model to RXP GTN #.
• Last row (unit #) is the RXP GTN unit # which will receive the command. It could be any of the 2 (these are per-unit). You identify this in determining which RXP gauges you've added.

Examples:

8000 tells to remap any f1 gtn 651 command into any RXP GTN #1 (what matters: it is a #1 RXP GTN, whether a 750 or 650).
8000 tells to remap any f1 gtn 652 command into any RXP GTN #2 (what matters: it is a #2 RXP GTN, whether a 750 or 650).
0800 tells to remap any f1 gtn 651 command into any RXP GTN #2 likewise.
0800 tells to remap any f1 gtn 652 command into any RXP GTN #1 likewise.
0080 tells to remap any f1 gtn 752 command into any RXP GTN #2 likewise.

etc...

Of course, this requires enabling "Use Simulator GPS Commands" because this enables external commands to the RXP GTN (there are also keyboard shortcuts, but they are 'external' to the simulator, whereas 'commands' are internal, i.e. can be fired by any gauge / module / 3D model).

Edited November 30, 2018 by RXP

[RXP 2,336]

14 hours ago, BillS511 said:

However in the sim the VC small knob doesn't appear to have the push function just turning.

I believe the 3D aircraft modeller has decided to hard-code the middle mouse button as the knob push function.

[fppilot 4,348]

 

12 hours ago, fppilot said:

3D model       |  652  |  651  |  752  |  751  |
    map to RXP |   #   |   #   |   #   |   #   |
               |(unit#)|(unit#)|(unit#)|(unit#)|

1 hour ago, RXP said:

8000 tells to remap any f1 gtn 651 command into any RXP GTN #1 (what matters: it is a #1 RXP GTN, whether a 750 or 650).
8000 tells to remap any f1 gtn 652 command into any RXP GTN #2 (what matters: it is a #2 RXP GTN, whether a 750 or 650).
0800 tells to remap any f1 gtn 651 command into any RXP GTN #2 likewise.
0800 tells to remap any f1 gtn 652 command into any RXP GTN #1 likewise.
0080 tells to remap any f1 gtn 752 command into any RXP GTN #2 likewise.

17 hours ago, RXP said:

In the end, you'll find out there is only 2 codes to cover all combinations: either 8800 or 8080.

I spent almost the whole day yesterday sorting this out for myself and I can confirm that those two codes do not cover all of the combinations. Discovered this because I often think outside the box. The potential of the f1vc.xml gauge is more flexible than that use of just those two codes if a user is flexible with how the gauge instances are used.  Personally, I often use either an rxpGTN_750_1 or an rxpGTN_750_2 as a sole GPS in a panel.  In longer range aircraft I use I use the rxpGTN_750_1 and store long range flight plans in rxpGTN_750_1.   For shorter range aircraft, like say the A2A 182 Skylane,  I use the rxpGTN_750_2, and store shorter flight plans there. 

What was giving me headaches was getting f1vc.xml to work for a single rxpGTN_750_2 in the A2A 182 Skylane panel.  Neither 8800 or 8080 work!  The reason is that in my application, the  rxpGTN_750_2 is the first and only 750 in the panel.  So that requires looking at the fourth column of the table and picking a code specific for that position.  Check the Values available in that column and for an rxpGTN_750_2 it requires an 8.

I had to adjust the top row labels in the table one more time for greater clarity.  So here is my table after this latest adjustment:. 

               |         |Only 650 |          |Only 750 |
     3D model  |  650 as | or 1st  |  750 as  | or 1st  |
               | 2nd 650 |   650   | 2nd 750  |   750   |
    map to RXP |    #    |    #    |    #     |    #    |
                  |  650_1=0  |  650_1=0   |   750_1=0   |  750_1=0   |
     Value #      |  650_2=8  |  650_2=8   |   750_2=8   |  750_2=8   |

 

I believe I have proved out this statement.  The columns represent what I show as the top labels of the table.  You go to a column in the table based  on whether a GPS is either the "Only or 1st" of its model, or whether it is the 2nd of its model.  A model is either a 650 or it is a 750.

So for example if a 750 is the only 750 in the panel, then you go to column 4.  If you are using rxpGTN_750_1 then you need a 0 in that fourth column.  0000 works! If you are using a rxpGTN_750_2 as the only 750 in the panel then you need an 8 in that fourth position, 0008 works.  Neither 8800 or 8080 will work for an rxpGTN_750_2 as the only one in the panel.  I have tested and proved this with method.

Solve 1:
Place two RXP GTN 750s in the panel of the RealAir Turbine Duke v2.  One is an rxpGTN_750_1, the other is rxpGTN_750_2.  Which of the two codes in the statement above accomplishes that?  8080 will.  8880 will. 0080 will.  Looking at the bottom two rows of my adjusted table, just match rxpGTN_750_1 to the "Only or 1st 750" or 4th column and see you need a zero in that position in the code. Likewise match up rxpGTN_750_2 to the "750 as the 2nd 750" or 3rd column, and see that you need an 8 for the third position in the code.  0080.

Now stay with me here.....

Solve 2:
If you decide to swap those two 750s around in that panel, with an rxpGTN_750_2 as the 1st and an rxpGTN_750_1 as the 2nd. (again, I do this because of the way I store flight plans). Looking again at my adjusted table you will match up the rxpGTN_750_2 to the "Only or 1st 750" column, and in that, the 4th  position of the code, you would use an 8 because it is rxpGTN_750_2.  Then, since rxpGTN_750_1 is the 2nd 750, it is matched up in the third column and since it is rxpGTN_750_1 it requires a 0 in the third column.  So with the rxpGTN_750_2 as the 1st, and rxpGTN_750_1 as the 2nd, the code is 0008.  I have tested this and confirmed

Solve 3:
Place one GTN 750 as the only 750 into the A2A 182 Skylane. 
Scenerio one: use rxpGTN_750_1.  Looking at the table, match rxpGTN_750_1 to the "Only or 1st 750" column and it requires a 0 in the 4th position. I am trying to recall from all my testing late yesterday, but I believe I found that since it is the only 750 that any code with 0 in the fourth position will work. 
Scenerio two: Use rxpGTN_750_2 instead as the only 750 into the A2A 182 Skylane. The adjusted table shows that matching rxpGTN_750_2 to the "Only or 1st 750" column shows an 8 is required in the fourth position of the code.  So 0008 is what works.  Fully confirmed. 

So 0000 if using rxpGTN_750_1 as the only 750 in a panel, and 0008 if instead using rxpGTN_750_2 as the only 750 in a panel. I tested these two scenarios  thoroughly yesterday, and this also works for the A2A Comanche.

Solve 4:
Place an rxpGTN_750_1 into the panel of the Milviz C310 Redux as the only 750, and also place an rxpGTN_650_2 as the only 650 in that panel.  Matching the rxpGTN_750_1 to column four as "Only or 1st 750" requires a 0 in that fourth position of the code.  Then matching up the rxpGTN_650_2 as the "Only or 1st 650" in the panel takes us to column two of the adjusted table, and since it is rxpGTN_650_2, an 8 is needed in the second position of the code.  So the code is 0800.

If in this scenario you instead use rxpGTN_750_2  -and-  rxpGTN_650_1 in the panel, the code becomes 0008.

The f1vc.xml's readme.txt file should also refer to the "Use Simulator GPS Commands" setting.

 

 

 

[RXP 2,336]

Frank, I thank you for the quite extensive tests. Nonetheless, this doesn't change the basics: the first row is not the RXP model/unit.

In the table, the first row is: "which intended combination of f1 gtn (model+unit#), for which there is a corresponding f1 gauge in the panel.cfg file, the 3D model (the 3D knobs, 3D buttons) is sending the embedded hard-coded custom f1 gtn commands to?".

Once you know/find out which sets of commands a 3D model is supposedly sending, you either put a 0 in its column to route the commands to ANY RXP GTN #1, and you put a 8 to route the commands to ANY RXP GTN #2.

Again, in your case, what matters is not whether you use a GTN_750_1 or GTN_750_2. What matters is what set of commands does the 3D representation of the GTN on the panel was compiled/authored for, and one way to find this out, is looking at what f1 gauges the aircraft vendor as elected to configure in the VCcockpit section of the panel.cfg file.

With the f1 gauges found out, you have a model and unit#. With the combination of f1 gauge (mode+unit#) you get a column. With the column, you choose to redirect the commands to any #1 or #2 RXP unit in putting a 0 or 8 respectively. You then replace the f1 gauges with RXP GTN in the panel.cfg in order to match you choices.

Example: you have 2 GTN in the VC, a 750 and a 650. You inspect the panel.cfg file and conclude it uses a f1 gtn 751 and f1 gtn 651. You want to replace the 750 with a RXP GTN 752, and the 650 with a RXP GTN 651. You get:

f1 751 -> RXP 752
f1 651 -> RXP 651

3D model (f1)  |  652  |  651  |  752  |  751  |
    map to RXP |   x   |   0   |   x   |   8   |
    RXP unit#  |not use|(any#1)|not use|(any#2)|

Your code: x0x8 (with 'x' anything you want, it won't be used).

NB: yes in the case you're not mapping a #1 to a #1 and a #2 to a #2, there are more codes than just the 2 indicated.

It is a very simple system, nothing complex. Just map a source 3D model command set to a RXP unit#.
 

Bonus: why does it have to be like this? Just because some vendors putting 2 GTN on their panels thought it would be better to put 2 unit#1...

Edited November 30, 2018 by RXP
color coded relationships