Throttletek Throttle Flight1tech g1000 calibration

[jmg225]

Hi Pete,

i am building a citation Mustang cockpit.  I have Throttleteks Mustang Throttle that has detents for cruise, climb and takeoff.  I'm using flight1techs g1000 student pro. The only way I can get the FADEC to even work is if I set the throttle axis via fsuipc and select "send to fs axis" and select "set throttle 1 axis" and "set throttle 2 axis". The Takeoff and Climb detents work (the n1 values get captured when I place the hardware throttle in the respective detents), but when putting the hardware throttle in the cruise detent, the n1 level does not get captured by the cruise setting and falls way below.  I'm using P3d 4.  If I try to set the axis to calibrate via fsuipc the n1 values dont capture in the software FADEC takeoff, cruise, climb at all.  If I try to just set the axis in P3d using its calibration the fadec settings don't even change between cruise, climb, takeoff on the throttle tape display.  not sure why it wont capture the Cruise FADEC position when in the cruise detent on the throttle especially when the takeoff and climb detents work correctly.  Was wondering if you had any ideas of things I could try  (my fsuipc is registered)   Im thinking it might be a calibration issue   However I have nowhere to calibrate sense it only works by selecting "send to fs axis" and if I select each axis in P3d itself the FADEC doesn't work/capture at all  

Thanks,

John 

[Pete Dowson]

5 minutes ago, jmg225 said:

The only way I can get the FADEC to even work is if I set the throttle axis via fsuipc and select "send to fs axis" and select "set throttle 1 axis" and "set throttle 2 axis".

"Axis throttleN set" I assume you mean?  And, yes, there are a number of aircraft which don't work with the older controls which FSUIPC's "direct" mode uses.

7 minutes ago, jmg225 said:

when putting the hardware throttle in the cruise detent, the n1 level does not get captured by the cruise setting and falls way below.

I presume the value it sets is insufficient. Can you check the actual value being set when you operate the throttle on screen (by mouse or whatever)? Just use the axis event logging option in FSUIPC's Logging Tab -- you can enable the Console log and temporarily run P3D in Windowed mode so you can see the changes in real time, on screen.

Then compare with what is being sent by your controls.

9 minutes ago, jmg225 said:

If I try to set the axis to calibrate via fsuipc the n1 values dont capture in the software FADEC takeoff, cruise, climb at all.

That's because the calibration converts the controls to the older ones, so it's actually the same as the assignment restriction. In order to make it use the newer controls, provided you are using the "no reverse zone" option, set "UseAxisControlsForNRZ=Yes" in the relevant Calibration section of the FSUIPC5 INI file. you can do this whilst P3D is running, then just go to the Calibration tab and select the Reload button.

Note that this only applies to "no reverse zone" mode because the newer controls don't provide a reverse range at all.

If this doesn't work, then, provided you only want specific throttle values to be set, you can use the right-hand side of the assignment, instead of the left, and have zones calibrated there which send specific values, using the same controls but with a specific numerical parameter value for the position. You'd need first to use the logging again to determine what values fit each notch correctly.

Pete

[jmg225]

Hi Pete,

Thank you so much for your quick response.  "UseAxisControlsForNRZ=Yes" solved all the problems. The detents in the hardware throttle now match the software FADEC perfectly.   I have one more question I thought you might have some insight to.  This is kind of hard to explain. I'm building a citation Mustang cockpit.  I have one computer with p3d4 networked to another computer running flight1techs G1000 student pro.  I had ruscool electronics build me a custom 15" mfd for the g1000.  The problem I'm having is getting the soft keys on the mfd to work.  The mfd does not appear as a gaming device, rather it comes with software that allows you to assign a keyboard command (like "SHIFT A") to each soft key button. It then suggests using fsuipc and assigning the keystroke to a function.  I think the problem I'm having is the function I want to happen is not in P3d but in the g1000 software.  The g1000 software also has a file where you can set a keystroke to activate any button.  I'm not sure how to get fsuipc to interact with the g1000 software.  I have the USB from the Mfd connected to the computer with P3d and the mfd software running on that computer.  Ruscool then suggested to run widefs which I'm doing to send the command to the g1000 computer.  So for example I have set the mfd software softkey 1 to "shift A".  I set the g1000 software keyboard.ini file mfd_softkey_1=shift_A.  When I press the actual soft key on the mfd nothing happens however when I literally press shift A on the g1000 computer's keyboard, softkey 1 is activated.  I guess I'm asking is there a way with fsuipc and wide fs to press a button on a controller that has a keyboard command attached to it and have it transmitted to another computer in the network and have that keyboard command executed in general on the networked pc if that makes any sense.  Thanks again for your time. 

[Pete Dowson]

2 hours ago, jmg225 said:

I think the problem I'm having is the function I want to happen is not in P3d but in the g1000 software.  The g1000 software also has a file where you can set a keystroke to activate any button.  I'm not sure how to get fsuipc to interact with the g1000 software.

If you need a keystroke for the G1000 and the MFD can be set to send keystrokes, what would you want to assign in FSUIPC for? Keystroke converted to keystrokes? What's the point of that? Just assign one to the other.

2 hours ago, jmg225 said:

I set the g1000 software keyboard.ini file mfd_softkey_1=shift_A.  When I press the actual soft key on the mfd nothing happens however when I literally press shift A on the g1000 computer's keyboard, softkey 1 is activated.

So, there's something wrong with the MFD sodtware, surely?  Since it was custom build and interfaces to USB, why doesn't it provide standard button presses in any case?

I'm not sure of the relevance of your mention of the network to all this. How are the keystreokes fetting from one to the other in any case?

2 hours ago, jmg225 said:

I guess I'm asking is there a way with fsuipc and wide fs to press a button on a controller that has a keyboard command attached to it and have it transmitted to another computer in the network and have that keyboard command executed in general on the networked pc

Oh, I see! Didn't you refer to the WideFS documentation at all? Look up "KeySend".

Pete

 

[jmg225]

 

[jmg225]

Sorry Pete,

not sure why it posted my last post again.  Thank you for directing me to the KeySend portion of the widefs manual.  I'm having trouble getting it to work.  If you remember I have a hardware PFD with soft keys that output keyboard commands (like ctrl shift A)  I put the keyboard string in the keys page in fsuipc and select "KeySend 1-255" from the function list and enter a number in the parameter field.   On the client computer i have the g1000 software running and in the widefs client.ini file under "user" I add "KeySend1= 65,8" as ctrl shift A is needed to activate the softkey button in the G1000 software.  I'm missing something because it's not working.  If I try each piece separately it works.  If I change the function in fsuipc on the keys page to something like "pause" and press the soft key, p3d does indeed pause.   If on the client computer I press ctrl shift A on the physical keyboard it does indeed activate the soft key in the software.  I can't figure out why the server and client won't work together. 

 

Thanks,

john

[Pete Dowson]

10 hours ago, jmg225 said:

I add "KeySend1= 65,8" as ctrl shift A is needed to activate the softkey button in the G1000 software.  I'm missing something because it's not working.

65,8 represents just 'A', no control or shift. Please look at the list of values for that position. 8 just means the normal key.

Pete