Jump to content
The simFlight Network Forums

English Rebel

Members
  • Posts

    205
  • Joined

  • Last visited

Posts posted by English Rebel

  1. Pete

    Sorry I should have mentioned that I was not using actual button information from the INI file  -- just examples -- that's why there are no assignments.  

    I guess I should have written the example as:

     

    45=CP(+J68,B2)J72,B4

    46=J68,B2

    47=J72,B4

     

    I just wanted to get the logic correct.   I was trying to clarify where the button conditional line should be located (as the actual button line entries are done by FSUIPC).  I also should have mentioned that the buttons I am referring to are actually button operated switches and are latching such that they hold there position (DOWN/ON) until they are pressed again (UP/OFF).

    Thanks

    Alan

  2. I'm sorry to be pedantic but I want to make sure I'm doing this correctly.  

     

    Button 68,2 is programmed as the APU master

    Button 72,4 is programmed as the APU Start button.

    Pressing button 72,4 is not supposed to do anything unless button 68,2 has first been pressed and once button 68,2 has been pressed it will allow the function of button 72,4 to take place once it is pressed.  In the real world button 68,2 closes a relay to provide power to button 72,4.

     

    So my button conditional was supposed to be (sorry about leaving in the J and the P):

    n=CP(+68,2)72,4

     

    So with this 

    45=cp(+68,2)72,4

    46=68,2

    47=72,4

     

    Am I correct in saying that:

    Line 45 states that the button assignment on line 47 will not take place (if that button is pressed) unless button 68,2 has been pressed and that if button 68,2 has been pressed then the button assignment on line 47 will take place when it is pressed?

    Thanks for your help on this.

    Alan

  3. At the end of the day you will need a program to interface the pokeys to FSUIPC to get proper encoder acceleration. I am currently working on one for my Learjet MCP at the moment. Its a bit of a slow crawl as I am not the worlds greatest programmer.

    I will let you know when it is done. Might be a while though.

     

    We are working on a solution with Ron Rollo and DonnyRay Jones.  May need some hardware added to the encoder circuits.  At the moment if I set the HDG to the fast option the faster I turn the encoder the heading bug slows down so I think the button presses are being sent by the Pokey card erratically.

  4. Okay so if the 'n' defines the order of execution then the 'n' in n=CP(+j2,b2)j,b does need to have a lower number than that of the 'n' for the actual button entries so it is executed first.

    So for the dependency to work the button section would need to look like this example?

     

    45=cp(+j68,b2)j72,b4

    46=68,2

    47=72,4

     

    Thanks

    Alan

     

    PS Yes I did mean to say at the end of the Buttons section of the INI file not the end of the INI file -- sorry.  

  5. I did a test of the heading bug today.  Using FSUIPC AP Panel HDG INC Fast function I get 180 degrees rotation of the heading bug for 360 rotation of the encoder (One "click of the encoder changes the bug 10 degrees) and for the Normal option I get 1.25 degrees rotation of the bug for 180 degrees rotation of the encoder.  Now there may well be no way to fine tune this in FSUIPC but I'm open to suggestions.

    Thanks

    Alan

  6. I know that in the User Guide I am advised to set the

     AutoAssignLetters=

    to YES so that FSUIPC can keep track of the programming associated with a particular joystick.  My question is does FSUIPC keep track of the programming of the joystick if it's moved not just from one port to another -- but from one PC to another PC both running WideFS on the network?
    Thanks

    Alan

  7. I just installed my Flight Guidance Computer (Autopilot) in my Lear45 sim.  It has encoders for flight level, speed, heading etc., all controlled through a Pokey card.   I can program the functions in FSUIPC from the drop down list in Buttons and Switches as I have programed the Pokey card to send the encoder's left and right turns as such.

    The issue is that I can only select a FAST or SLOW option and when changing the heading for instance, SLOW takes too long and FAST is not accurate enough as it tends to overshoot the desired heading.  When I used to have GoFlight autopilot module this was not an issue as GoFlight software presumably detected how fast I was turning the knob and selected the speed accordingly.  

    I'm sure that someone has somehow managed to fix this -- perhaps using a LUA script to detect how fast the button presses are taking place and selecting the appropriate FSUIPC function -- FAST or SLOW?

    I have no programming experience and have only managed to write a small LUA script that plays a sound when a button is pressed so a more complicated script would be beyond me.

    Any help will be appreciated.

    Thanks

    Alan

  8. Pete

    What I was trying to say (and maybe I wasn't too clear) if I just assign an Increment to the HDG encoder it takes forever to get the needle turned say 180 degrees because of the small incremental movements.   Assigning an Increment fast certainly gets a 180 degree turn of the needle quick but it's impossible to fine tune down to the correct reading as it jumps in too large increments.  Ideally using an Increment when turning the encoder knob slowly but changing to Increment fast when turning it fast but I don't think you can assign both increments to say the CW movement of the encoder.

    So, I read somewhere on your forum about a way to have the incremental movements of the HDG needle small when you are turning the encoder knob slowly and large when you turn it faster.   I cannot find it so was asking if you remember how it was done -- a LUA script perhaps?
    Thanks

    Alan

  9. Pete

    I am getting an FGC (auto pilot) for my Lear 45 that uses encoders connected to a Pokey card for HDG, CRS, ALT etc.   I seem to remember that in Buttons + Switches assignments you have the option for Increment, Decrement, Increment fast, and Decrement fast for all of these function.  However I'm sure you cannot use Increment and Increment fast at the same time for a button assignment to an encoder CW movement.   I seem to remember that there is another way to do this but cannot find it.

    Do you remember what that was -- a LUA script maybe?
    Thanks

    Alan

  10. Sorry to be obtuse but I'm not sure what you are telling me.  I'm not using any code I'm just using the offset and its state.  I'm doing all my entries in Flight Deck Solutions InterfaceIT as all my switches are connected to their interface card.  What I posted in #3 is what options I have in that program.  Also those offsets are read only and 0 is Engine OFF and 1 is Engine ON.

    Thanks

    Alan

  11. I have a light on my electrical panel that indicates a connection between the left and right hand busses (it's a horizontal bar).   This is the correct sequence.

    When neither engine is running the light should be OFF signifying that the two busses are not connected (the emergency battery connects the two).  When the right engine starts the buss connection should close and the light should come ON.  When the left engine starts  the buss connection should open and the light should go OFF.

    To try and achieve this I used offsets 0894 and 092C (combustion flags for the left and right engines).  I used the Value On/Off setting for the right engine I set a value of 1 for On and a value of 0 for Off (so when the engine is off the light is OFF and when the engine is running the light is ON).  For the left engine I used Set value On with a value of 0 to turn off the light OFF when the engine is running?

    For some reason this doesn't see to work correctly.  It's okay for the engines start up sequence as the light comes ON when the right engine starts and goes out when the left engine starts.  However when I shut down the left engine the light comes ON (as it should) but when the right engine shuts down the light stays ON.

    I checked that the combustion flags where working okay by logging the reads. Anyone figure out where I went wrong?
    Thanks

    Alan

  12. Pete

    Does offset 0932 Engine 2 Throttle switchable input set a particular throttle position based on the parameter entered?  What is the format for using it is (Word, Byte etc)?  Are the values -4096 to +16384 for the full range of movement where the negative values are reverse thrust?
    Thanks

    Alan

  13. I am contemplating testing Prepar3d to see if I like it enough to switch from FSX but do not want to reprogram all my switches and re-calibrate my controls.  I have done a search but cannot find a tutorial or any information that tells me what to do except I did see this in one post: 

    if you have an FSX installation already, just copy your FSX Modules folder over to P3D and adapt your DLL.XML file to suit, in the same folder as Prepar3D.CFG.

     

    I'm not sure if this is all I have to do as the FSUIPC.INI file for one has a lot of references to FSX.  If it's a simple as just copying the Modules folder what do I have to do to adapt the DLL.XML file?
    Thanks

    Alan

  14. Pete

    Okay to preserve your sanity let me approach this from another direction.   I deleted the button conditional line (and only the button conditional line) so I can program the APU START button in a different way without being conditional on another button.  So now this is my INI button section:

     

    [buttons]
    ButtonRepeat=20,10
    0=PB,0,Cx0D0073F8,x01
    2=PB,5,Cx050073F8,x20
    4=PB,1,Cx050073F8,x02
    5=PB,14,C66040,16211
    6=UB,1,Cx090073F8,x02
    7=UB,0,Cx090073F8,x01
    8=PB,2,Cx050073F8,x04
    9=UB,2,Cx090073F8,x04
    10=PB,3,Cx050073F8,x08
    11=UB,3,Cx090073F8,x08
    12=PB,4,Cx050073F8,x10
    13=UB,4,Cx090073F8,x10
    14=UB,5,Cx090073F8,x20
    15=PB,13,Cx050073D5,x40
    18=UB,13,Cx090073D5,x40
    19=PB,7,Cx050073F9,x01
    20=UB,7,Cx090073F9,x01
    21=PB,8,Cx050073F9,x02
    22=UB,8,Cx090073F9,x02
    23=PB,9,Cx050073F9,x04
    24=UB,9,Cx090073F9,x04
    25=PB,10,Cx050073F9,x08
    26=UB,10,Cx090073F9,x08
    27=PB,11,Cx050073F9,x10
    28=UB,11,Cx090073F9,x10
    29=PB,12,Cx050073F9,x20
    30=UB,12,Cx090073F9,x20
    31=RB,19,Cx110073FD,x00FF0001
    32=RB,18,Cx210073FD,x00FF0001
    33=RB,23,Cx110073FC,x00FF0001
    34=RB,22,Cx210073FC,x00FF0001
    35=RB,21,Cx210073D2,x00FF0001
    36=RB,20,Cx110073D2,x00FF0001
    37=RB,25,Cx510073D7,x00FF0000
    38=RB,24,Cx610073D7,x000000FF
    39=RB,27,Cx610073D8,x000000FF
    40=RB,26,Cx51000049,x00FF0000
    41=RB,29,C65883,1
    42=RB,28,C65884,1
    70=PB,6,C65821,0
    71=UB,6,C65821,-4096
    75=R72,4,Cx32000C04,x3FFF004B
    76=R72,5,Cx33000C02,x3FFF004B
    77=R72,3,Cx42000000,xC001004B
    78=PC,4,Cx02000BC8,x0000
    80=PC,5,C65820,0
    81=UC,5,C65820,-4096
    82=PC,6,C65821,0
    83=UC,6,C65821,-4096
    84=PC,2,C65983,0
    85=UC,2,C65987,0
    86=PC,3,C65988,0
    87=UC,3,C65992,0
    88=UC,4,Cx02000BC8,x7FFF
    89=R72,6,Cx42000C02,xC001004B
    90=P72,0,C1126,0
    91=U72,0,C66705,0
    93=P69,8,CL3:R,0
    94=U69,8,CL3:K,0
    95=P70,9,CL4:R,0
    96=U70,9,CL4:K,0
    97=P70,10,CL3:R,0
    98=U70,10,CL3:K,0
    99=R64,0,Cx42000BC0,xC001004B
    100=R72,1,Cx32000BC0,x3FFF004B
    101=R72,2,Cx42000BC0,xC001004B
    102=P64,2,CL5:R,0
    103=U64,2,CL5:K,0
    104=P64,3,CL6:R,0
    105=U64,3,CL6:K,0
    106=P64,5,CL5:R,0
    107=U64,5,CL5:K,0
    108=P64,4,CL3:R,0
    109=U64,4,CL3:K,0
    110=R64,7,Cx32000BC0,x3FFF004B
    111=P64,8,C1126,0
    112=CR(-64,8)72,1,Cx32000BC0,x3FFF004B
    113=CR(-64,8)64,0,Cx42000BC0,xC001004B
     
    Switch 72,0 is highlighted in red and shows an action for press and release.  In Buttons + Switches if I press my APU switch it shows up as Joy 72 button 7 and the press action is APU START but is still showing as being conditional and is to be edited in the INI file.  Please let me know where the entry for 72,7 is in my INI file so I can delete it and start over.
    Thanks for your help.
    Alan
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.