Jump to content
The simFlight Network Forums

Pantu

Members
  • Posts

    31
  • Joined

  • Last visited

Posts posted by Pantu

  1. Hi John,

    thank you very much for prompt reply. Tried your proposed changes, but unfortunately didn´t work.

    I thought that the first line of my script "local Battery_on = {}" would have created a local variable, which could be used for my task and hence the Lvar would exist and be usable by external applications.  That thinking is obviously wrong.

    If however I take a Lvar from a plane for instance, my script works.

    Will have to look for unused Lvars of P3D and try to solve my problem. Don´t know which other way would let me generate Lvars, which could be accessed by Lorbys Axis and ohs.

    Best regards

    Pete

     

     

  2. Hi,

    could someone help me please?

    I´m trying to write the value from an offset into a Lvar using a lua script in FSUIPC 6.

    The task is to monitor an offset, e.g. the battery master switch, and when the value changes, writing the new value into my declarded local variable.

    This would be needed for Lorbys Axis and ohs realizing an interactive voice checklist.

    Axis and ohs only accepts Lvariables, no offsets. SimVars wouldn´t do as I´m using Project Magenta´s Boeing suite. together with P3Dv5.3

    Following script unfortunately won´t do the job:

    ----------------------------------------------------script---------------------------------

    local Battery_on = {}
    function Batteryswitch(offset, val)
                      if value == 1 then
                       ipc.writeLvar("Battery_on", 1)
        else
                       ipc.writeLvar("Battery_on", 0)
        end
    end
    event.offsetmask(0x281C, 1,"UB","Batteryswitch")  --- bit 0

    --------------------------------------------------------------------------------------------

    What am I doing wrong?

    Any help highly appreciated.

    Thanks a lot in advance

  3. Hi,

    could someone help me please?

    I´m trying to write the value from an offset into a Lvar using a lua script in FSUIPC 6.

    The task is to monitor an offset, e.g. the battery master switch, and when the value changes, writing the new value into my declarded local variable.

    This would be needed for Lorbys Axis and ohs realizing an interactive voice checklist.

    Axis and ohs only accepts Lvariables, no offsets. SimVars wouldn´t do as I´m using Project Magenta´s Boeing suite.

    Following script unfortunately won´t do the job:

    ----------------------------------------------------script---------------------------------

    local Battery_on = {}
    function Batteryswitch(offset, val)
                      if value == 1 then
                       ipc.writeLvar("Battery_on", 1)
        else
                       ipc.writeLvar("Battery_on", 0)
        end
    end
    event.offsetmask(0x281C, 1,"UB","Batteryswitch")  --- bit 0

    --------------------------------------------------------------------------------------------

    What am I doing wrong?

    Any help highly appreciated.

    Thanks a lot in advance

  4. Hi Pete,

    I´m planning to migrate from FSX to Prepar3d v 4.1. My question here is to which extend the existing FSUIPC.ini from FSX could be reused straight forward in FSUIPC5, or do i need to set up / program every single button etc. from scratch again?

     

    Thank you very much in advance for shedding some light on this

    Pantu

  5. Sorry, is recognising button presses a problem now? Why? Do you want them ignored?

    Of course not. Sorry wrongly expressed.

    What is "MCP747"? Maybe it isn't connecting to FSUIPC?

    It´s the aerosoft Australia MCP747 autopilot box.

    No. I'm sure you must be misinterpreting something. There's no difference whatsoever between a line manually inserted into the correct section of the INI and one generated by FSUIPC from the options, if indeed they are identical and in the correct section. There cannot possibly be any difference, because that's what FSUIPC reads for its definitions and there is nothing else it can get that information from. See? It's a logical impossibility.

    I don't think the documentation will describe an impossible situation like the one you are describing. I think you should show me the non-working section and the working section. There's something you are not spotting.

    Pete

    Thanks Pete for prompt reply.

    Did check the fsuipc.ini file character by character and eventually found the culprit.

    When I copied the "Buttons" part from the "old" FSUIPC3.ini into the Fsuipc4.ini, I overlooked that there was already an empty "[buttons]" in the FSUIPC4.ini existing. (It´s definitely time to get some better glasses now - before X-mas)

    Empty buttons section erased and voila, the problem is solved.

    Again, thank you very much for your outstanding support and please take my apologies for bothering you with my own stupidity.

    Best regards

    Peter

  6. Hi Pete,

    sofar was using FS9 but now I´d like to switch my homecockpit (B737 Proj.Magenta )to FSX.

    According to the docs one could ease up workload of button assignments by just copying the buttons section from FSUIPC3 to FSUIPC4.

    Sofar so good.

    The problem however is, that FSUIPC4 recognizes the button presses (virtual buttons generated by MCP747). The virtual buttons in MCP747 are mostly all of "Toggle" and some of "Flip Flop" type, (as recommended in the docs) but wouldn´t display the assignments in FSUIPC4 setup page. Hence no reaction on the corresponding parts of project magenta.

    If however I reassign in FSUIPC4 the button with exactly the same function it works.

    Looking into FSUIPC.ini - I can´t find any difference compared to the copied part. It shows exactly the same coding like when it was copied over.

    Does that mean that I´ll have to reassign every single button again?

    Any clue what I´m doing wrong? I´ve read your docs over and over but not getting any clue what´s the culprit.

    Any hint highly appreciated.

    Thanks

    Best rgds

    Peter

  7. Hi Pete,

    I´m using pmsystems (latest build 85) but my fuel levers don´t actually work as supposed.

    The 2 HW switches (eng.1 and2) are connected via FSBus. I defined 2 "virtual buttons" in order to have them recognized in FSUIPC´s button page.

    Then defined for the switches "on" position: mixt. eng1 (2) rich and for the "off" position: mixt. eng1(2) lean.

    So far so good.

    My problem: the switches work nicely(recognized in FSUIPC), but the engines start even the fuel valve switches are in "cutoff" position.

    As soon as I turn the starter switch on the overhead to "Gnd" the light " Start valve open" on the Upper Eicas in PM GC comes on.

    The engine spools up and ignites.

    If i flip the Fuel lever switches to "Run" position the engine continues to run. (OK) Flipping it to "cutoff" the engine shuts down (OK).

    I thought the start valve is driven by the fuel valve switch. How come that the light "start valve open" comes on as soon as the igniter switch is set to GND.

    Do I need to set values for "rich" and "Lean" in FSUIPC?

    Any hint highly appreciated.

    Thanks and best regards

    Peter

  8. Hi Chris,

    the "simple" ones are manufactured by ALPS and KNITTER.

    The latter are less robust (full plastic gear) as the ALPS. The ALPS are fully made from metal and have additionally a centric push button inbuilt.

    Make sure they are not the ones based on phase shift. (The turning direction is contained in the phase shift between the 2 pulses).

    The phase shift based rotaries require a specific interface e.g. named "REDEC" (search the web for REDEC), whereby the rotary switches (special types made by "Knitter switch" and Alps) do not require such interface as, depending on the turning direction, only 1 of the 2 outputs delivers pulses at a time.

    Hence they can directly be connected to a keyboard encoder or FSBus etc.

    Hope this helps

    Best regards

    Peter

  9. Hi Pete,

    I´m loading 747MCP, FSBus router and PM MCP via FSUIPC using following syntax:

    [Programs]

    RunIf1=Ready,Hide,Close,C:\Aerosoft MCP747\mcp747.exe

    RunIf2=Ready,Hide,Close,C:\Programme\FSBUS\FSBUS.exe

    RunIf3=Ready,Hide,Close,C:\MCP\MCP.exe

    Unfortunately the programs are not hidden (minimized) and I have to do it manually to get FS in the fore ground.

    What am I doing wrong?

    Thanks for any hint and best rgds

    Peter

  10. Hi Pete,

    well to switch it on and off in PM is ok, but then the simulated warmup phase is useless for PM ND users.

    Good idea to ask Enrico´s support forum about the missing keys in the CDU, but I´m afraight the support is in hibernation state as I asked some questions days ago but no reply from the support team sofar.

    May be you have an idea what kind of font can be chosen in the CDU ini to improve the readability. Bold is too clumsy and normal becomes rather distorted for some characters when adjusting text and font size thru the display menu.

    Thanks

    Best regards

    Peter

  11. Hi Pete,

    now I have played another couple of hours and found a way to get it working as follows:

    To toggle the WXR button: OFF - WXR - WXR+TURB

    used: Offset word set bits at x6D00 (pushed) value x0003

    Offset word clr bits " (released) value xFFFF

    To incr. Tilt : " " " value x0102

    " " " value xFFFF

    To decr. Tilt : " " " value x0402

    " " " value xFFFF

    That works fine.

    BTW according to the manual (v1.6) there should be keys assigned in PM CDU for tilt etc. They are not there!

    However what seems somewhat strange is, that the radar picture itself does not disappear when switching the radar off. It is still there even the SA_WXR window displays OFF.

    SA_WXR is supposed to export its wheatherfile to the Netdir of PM. All I find there is a file called "pmwx.dat" and another file which is named"xxx.xxx" (no porn file!) :wink: and it contains only xxx. Have you got a clue what it could be?

    Best regards

    Peter

  12. Hi Pete,

    I´m using SA_WXR (v1.2.2) and like to control it via FSUIPC virtual buttons but am a bit puzzled as the instruction from Florian isn´t so clear to me.

    I just don´t know which offset type I should use as the "Offsetwordsetbits"

    doesn´t work for me.

    I used hex address 6D00 with the value 3 (bit 0 and 1 set) but nothing happened.

    Could you just give an example for toggling the OFF - WXR - WXR+TF and for setting the tilt using a rotary switch.

    Thanks a very lot in advance..

    Best regards

    Peter

×
×
  • 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.