Jump to content
The simFlight Network Forums

Thomas321

Members
  • Posts

    49
  • Joined

  • Last visited

Posts posted by Thomas321

  1. Hello Pete,

    I want to assign a Key or a Joystick Button with a Function,

    which sets N1(of both Engines) to a specific Value(maybe 96 Percent).

    Not higher -not lower - 96 Percent - independently of Temp,Pressure,...

    I know about the "TOGA"-Function in FS,but this Function depends on

    Temperature i think.

    I want a FIXED N1-Position with a Keystroke/buttonPress,which the Engines should use as the Target to reach.

    I tried a few Offsets(from the FSUIPC for Programmers.doc),which has something in common with "N1".

    But i don´t get it work,don´t know which Offset to use,and i am not so familiar with this Stuff.

    How can i manage this.

    Thanks for any advice.

    Regards,

    Thomas

  2. Hello Peter,

    I programmed a Button to "TRIM DOWN" ,REPEAT;

    at Button Release: "AP MASTER"

    I press the Button,hold it,and it trims only a little bit;

    if i release the Button the AP engages.

    All normally,exept the REPEATING.

    I created a Log File,this i have enabled:

    IPC Read,IPC Write,Extras,Normal Log File,Debug String

    (hope it fits)

    ********* FSUIPC, Version 3.30 by Pete Dowson *********

    User Name="Thomas "

    User Addr="----"

    FSUIPC Key is provided

    WideFS Key is provided

    [Continuation log requested by user]

    Module base=61000000

    ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E

    WeatherOptions(Orig)=4000360D[4000360D]

    InitDelay: 0 seconds

    WeatherReadInterval=4

    LogOptions=0000001D

    LogExtras=1

    109594 System time = 11:56:13, FS2004 time = 10:26:09 (17:26Z)

    109594 *VIS* SM: Min=0,00, MaxRny=0,00, MaxOvc=0,00, MaxCld=0,00, MaxClr=0,00, Upper=60,00, FT: LwrAlt=6000, UppAlt=25000

    109594 WeatherOptions set, now 4000360D (timer=0)

    112157 AP READOUTS: Flags1=00002103, Flags2=00000000

    116016 AP READOUTS: Flags1=00000000, Flags2=00000000

    127829 AP READOUTS: Flags1=00002103, Flags2=00000000

    135704 AP READOUTS: Flags1=00000000, Flags2=00000000

    140579 C:\Dokumente und Einstellungen\Administrator\Eigene Dateien\Flight Simulator Files\STD.flt

    141079 Clear All Weather requested: external weather discarded

    144516 Flight saved #1 = "Previous flight"

    145938 System time = 11:56:49, FS2004 time = 10:25:03 (17:25Z)

    145938 *** FSUIPC log file being closed

    Memory managed: 3 Allocs, 603 Freed

    ********* FSUIPC Log file closed ****

    here my FSUIPC.ini:

    (Trim Down/AP Master Buttons are RED marked)

    [General]

    History=GLW4NN1YISOLBQC0Q5XHD

    TCASid=Flight

    TCASrange=40

    TrafficScanPerFrame=10

    AxisCalibration=No

    CentredDialogue=No

    ClearWeatherDynamics=Yes

    OwnWeatherChanges=No

    WeatherReadInterval=4

    MoveBGLvariables=Yes

    MainMenu=&Modules

    SubMenu=&FSUIPC ...

    WindSmoothing=Yes

    AutoTaxiWind=No

    WhiteMessages=No

    ThrottleSyncAll=No

    GraduatedVisibility=No

    LowerVisAltitude=6000

    UpperVisAltitude=25000

    UpperVisibility=6000

    GenerateCirrus=Yes

    WindShearSharp=No

    UpperWindGusts=No

    ExtendMetarMaxVis=Yes

    PatchSimApAlt=Yes

    DisconnTrimForAP=No

    AutoClearWeather=Yes

    ExtendTopWind=Yes

    WindSmoothness=5

    SmoothPressure=No

    PressureSmoothness=5

    SmoothVisibility=No

    VisibilitySmoothness=2

    MaxSurfaceWind=0

    WindLimitLevel=200

    WindDiscardLevel=400

    WindAjustAltitude=No

    WindAjustAltitudeBy=2000

    MinimumVisibility=0

    MaximumVisibilityFewClouds=0

    MaximumVisibility=0

    MaximumVisibilityOvercast=0

    MaximumVisibilityRainy=0

    OneCloudLayer=No

    ThinClouds=No

    ThinThunderClouds=No

    CloudThinness=1000

    ThunderCloudThinness=10000

    CloudTurbulence=No

    CloudIcing=No

    WindTurbulence=No

    SuppressAllGusts=No

    ExternalOptionControl=Yes

    AutoTuneADF=No

    KeepFS98CloudCover=No

    ShowPMcontrols=No

    MagicBattery=Yes

    RudderSpikeRemoval=No

    ElevatorSpikeRemoval=No

    AileronSpikeRemoval=No

    ReversedElevatorTrim=No

    TrapUserInterrupt=Yes

    NavFreq50KHz=No

    ClockSync=No

    SmoothIAS=Yes

    SetVisUpperAlt=No

    VisUpperAltLimit=6000

    MaxIce=3

    WindSmoothingDelay=0

    WindSmoothAirborneOnly=No

    VisSmoothingDelay=0

    VisSmoothAirborneOnly=No

    SuppressCloudTurbulence=No

    SuppressWindTurbulence=No

    SpoilerIncrement=512

    ShortAircraftNameOk=No

    FixWindows=No

    FixControlAccel=Yes

    SetStdBaroKey=66,11

    LogWrites=Yes

    LogReads=Yes

    LogExtras=Yes

    [JoystickCalibration]

    FlapsSetControl=0

    ReverserControl=66292

    MaxThrottleForReverser=0

    AileronTrimControl=0

    RudderTrimControl=0

    CowlFlaps1Control=0

    CowlFlaps2Control=0

    CowlFlaps3Control=0

    CowlFlaps4Control=0

    SlopeAileron=0

    SlopeElevator=0

    SlopeRudder=0

    [Keys]

    [buttons]

    0=P0,0,C1006,1

    1=P0,8,C2999,74

    2=P5000,1,C65580,0

    3=P5000,6,C65567,0

    4=P5000,8,C65749,0

    5=P5000,10,K187,8

    6=P5000,12,K189,8

    7=P5000,13,K8,8

    8=P5000,11,K32,8

    9=P5000,4,K83,10

    10=R5000,32,C65734,0

    11=R5000,36,C65735,0

    12=R5000,38,C65671,0

    13=R5000,34,C65672,0

    14=P0,36,C66040,16211

    15=P0,34,C2999,95

    16=P0,1,C2999,93

    17=P0,13,C2999,91

    18=P0,6,C2999,92

    19=P0,19,C2999,94

    20=P0,21,C2999,2

    21=P0,28,C2999,1

    22=P0,20,C2996,71

    23=P0,27,C2996,72

    24=P0,15,C2999,75

    25=P0,7,C2999,77

    26=P0,14,C2999,78

    27=P0,18,C1006,1

    28=P0,4,C1006,2

    29=P0,26,C2999,62

    30=P0,16,C2999,82

    31=P0,24,C1007,2

    32=P0,10,C1007,4

    33=P0,3,C1007,0

    34=P0,30,C2999,83

    35=P0,31,C2999,84

    36=P1,15,C2999,23

    37=P1,29,C2999,22

    38=P2,38,C2999,301

    39=P2,24,C2999,302

    40=P2,31,C2999,303

    41=P2,23,C2999,304

    42=P2,16,C2999,305

    43=P2,2,C2999,306

    44=P2,34,C2999,307

    45=P2,32,C2999,308

    46=P2,36,C2999,309

    47=P2,9,C2999,310

    48=P2,1,C2999,311

    49=P2,15,C2999,314

    50=P2,8,C2999,315

    51=P2,0,C2999,316

    52=P2,22,C65860,0

    53=P2,29,C65861,0

    54=P2,28,C65759,0

    55=P2,21,C65758,0

    56=P2,17,C2999,50

    57=P2,25,C2999,51

    58=P2,3,C2999,52

    59=P2,18,C2999,53

    60=P2,26,C2999,85

    61=P2,19,C2999,86

    62=P2,20,C2999,5

    63=P2,6,C2999,3

    64=P2,13,C2999,4

    65=P2,27,C2996,73

    66=U5000,36,C66415,0

    67=U5000,32,C66415,0

    68=R5000,33,C65856,0

    69=U5000,33,C66415,0

    70=R5000,39,C65854,0

    71=U5000,39,C66415,0

    72=R5000,37,C65855,0

    73=U5000,37,C66415,0

    74=R5000,35,C65857,0

    75=U5000,35,C66415,0

    76=R5000,14,C65607,0

    77=U5000,14,C65580,0 THIS is the Trim Down/AP Button

    [Programs]

    [Monitor]

    Display=9

    and finally my Wideclient.ini from the Client,where the Joystick is connected:

    ; PLEASE SEE WideFS documentation for parameter details

    ; =====================================================

    [Config]

    Port=8002

    Window=16,0,112,780

    Visible=Min

    ServerIPAddr=10.0.0.140

    ButtonScanInterval=20

    ClassInstance=0

    NetworkTiming=5,1

    PollInterval=2000

    ResponseTime=18

    Timeout=12

    TCPcoalesce=No

    UseTCPIP=Yes

    WaitForNewData=500

    ; -----------------------------------------------

    [user]

    Log=Errors+

    Run1=C:\Programme\FS Communicator\FSCom.exe

    Close1=Yes

    AllowShutdown=Yes

    ; ===============================================

    The FSCom.exe was deactivated during testing/logging to Insure it has no Influence.

    Best Regards,

    Thomas

  3. Hello Peter,

    "POV-Views"? I don't list such a control. Can you be more explicit please?

    Yes,of course i meant the PAN-Views! :oops:

    However, there is a "fix" if that's what you really want to do in 2D cockpit mode -- it isn't defaulted because it appears very odd having the cockpit stationary whilst the scenery slides past in front of you. To apply the fix add

    pan_in_cockpit_mode=1

    to the [Controls] section of the FS9.CFG file.

    No, i don´t want to PAN in Cockpit-Mode.

    In Cockpit-Mode all works good for me.

    For example: I assign the Left POV to "PAN Left" ,and

    "Button Release" to "Pan Reset COCKPIT" .

    It works good for me.

    But if i go to the Virtual Cockpit Mode/Spot View and i want to PAN around the Aircraft,the View only make little steps and i have to press the Buttons FAST to pan around the Aircraft.

    The Reason: "Control to repeat while held" has no effect.

    All other Buttons of this Client-Joystick are affected too.

    Independently which Function i select from the FSUIPC-FSControls-Menu.

    The same Problem,if i assign a KEY to a Button.

    NO repeating...

    This Case occurs only with the "Joystick on Client".

    If i use the Joystick on the Server(using FSUIPC-Button Programming-Facility/deactivating the FS-internal Button-assigning) all works normally,all the Buttons repeat.

    Thanks,

    and

    Best Regards,

    Thomas

  4. Hello,

    *FSUIPC 3.30*

    *WideFS 6.23*

    I have a problem with the Joystick Buttons (again).

    The Joystick is on a Client.

    Under the FSUIPC Buttons-Facility\FS Controls , i assign the "POV-Views" to the Coolie-Hat of the Joystick.

    -I think the "Coolie" has 2 Axis,but FSUIPC doesn´t recognize Axis on Clients -yet- .

    maybe in the Future ? :)

    This works,but the Buttons don´t want to REPEAT while i press them.

    I checked "Control to repeat while held",and the entry in the FSUIPC.ini seems correct:

    12=R5000,38,C65671,0

    13=R5000,34,C65672,0

    (only 2 examples for the POVleft,POVright)

    "R" stands for repeat i know...

    Please give me a hint.

    Kind Regards,

    Thomas

  5. Hello again,

    another Problem:

    Now i´ve connected my last PC-the "FlightControlComputer"

    On this PC runs the "FSCommunicator" with its FlyByWire Module from Robert Fischer.Only a Joystick is connected to this PC.

    This PC don´t want to shut down at all wheter using the Hotkey nor the MCDU.

    ONLY WideClient gets closed(and the Application which was started with WideClient).

    entries in WideClient:

    Run1=C:\Programme\FSComm\fscom.exe

    Close1=Yes

    AllowShutdown=Yes

    If I press the Shutdownhotkey on the Server the Application and WideClient shuts down,but the Computer stays fully running.

    If i CLOSE this Application BEFORE I press the Shutdownhotkey,then this PC shuts down completely.

    The Problem: No Keyboard and NO Mouse should be connected to this Computer,so i would not be able to close this Program...

    What can I do?

    Is it bad for the PC to power off without shutting down?

    That would be a solution-but if this is good... :roll:

    Thanks again and

    best regards,

    Thomas

  6. Indeed,with "half running" I mean ,Windows has closed,but the PC don´t

    power off.

    I use all the same 623 Wideclient Versions.

    I see, you have also such Problems with the PCs.

    I also want to do like you, to power off the PCs using a main Power Switch.

    Then all Problems are solved.

    And i *could* live with this solution... :)

    All the Best and thank you very much,

    Thomas

  7. Hi,

    To check that it isn't WideFS or the specific PC, try a different program on that PC, or just close the CDU.EXE first, leaving WideClient running, then use the Shutdown key on the Server.

    If i do so,the other PCs shut down completely,but the MCDU stays "half running"(as described).

    But this MCDU-PC CAN shut down completely,as described before...(if i shut only this MCDU-PC down using the MCDU-Facility)

    Now things have changed(don´t ask me why...):

    If i press the ShutdownHotkey INFLIGHT ,-ALL Clients(exept the MCDU)

    shut down completely.

    The MCDU-PC is half running yet.

    :?

    It seems the only problem is the MCDU-PC...

    here again the Wideclient ini of the MCDU PC(please have a look if all is correct).

    [Config]

    Port=8002

    Window=87,85,812,589

    Visible=Min

    ServerIPAddr=10.0.0.140

    ButtonScanInterval=20

    ClassInstance=0

    NetworkTiming=5,1

    PollInterval=2000

    ResponseTime=18

    Timeout=12

    TCPcoalesce=No

    UseTCPIP=Yes

    WaitForNewData=500

    ; -----------------------------------------------

    [user]

    Log=Errors+

    AllowShutdown=Yes

    RunReady1=C:\MCDU\mcdu.exe

    CloseReady1=Yes

    ActionKeys=Yes

    KeySend1=76,10

    KeySend2=76,12

    It´s not WideFS related,but could you give me advice what there could be configured wrong under Windows that this Problem on the MCDU-PC occurs?

    For a economic Solution i´ll do as far now as follows:

    I shut down the MCDU PC thru the MCDU-Faclility,then i shut down all the other Clients using the Hotkey...

    How do YOU personally handle this?

    Big thanks,

    Thomas

  8. Hello,

    I hope i don´t annoying you with this rather less problem,but it makes me very confusing....

    I have a Problem shutting down my 6 PCs,better said ,ONE of them.

    I want to shut down all my PCs thru the integrated Facility in the

    PM-MCDU.

    That works good,all PCs shut down but the MCDU-PC only gets to the

    Desktop(no Icons), and stays so here until i switch off manually.

    In this case ,the FS (on the Server) is in Flight-Mode(Aircraft at Gate).

    -----------

    But if the FS is in Menu-Mode (where i can create a flight,load a flight,..) and I want to switch off the PCs thru the MCDU,ONLY the MCDU-PC shuts down COMPLETELY,and all the other PCs stay running-,UNTIL i go back in FS to the Flight Mode-then also all the other Clients shut down (automatically)normally .

    That is a bit confusing,and if i make a mistake with this Procedure,I can crouch behind my Cockpit and can search for the PCs,and.... :roll: :)

    The same Problem i also have, using the Shutdownhotkey on the Server:

    If i am in Menu-Mode and press the ShutdownHotKey nothing happens(of course i think bec. WideFS is not serving...?) ,then I load the Flight,and all Clients shut down completely ,EXCEPT the MCDU PC,this one only goes to the desktop(no Icons) and does not shut down completely.

    If i press the ShutdownHotkey INFLIGHT ,-ALL Clients(including the MCDU)

    only shuts down to the blank Desktop (so as would Windows write :"You can switch off your computer now" )

    Here the .ini Files:

    FS-PC (Server):

    ; PLEASE SEE the documentation for parameter details

    ; ==================================================

    [Config]

    Port=8002

    AutoRestart=0

    AutoUpdateTime=13

    MaximumBlock=4096

    NoStoppedRestarts=Yes

    RestartTime=10

    SendTimeout=15

    TCPcoalesce=No

    UseTCPIP=Yes

    ; -----------------------------------------------

    [user]

    Log=Errors+

    ShutdownHotKey=69,11

    ; ===============================================

    [ClientNames]

    1=ECAMS

    2=AD

    3=FMGC

    4=LAPTOP

    5=FCC

    **********************

    a Client:

    ; PLEASE SEE WideFS documentation for parameter details

    ; =====================================================

    [Config]

    Port=8002

    Window=43,44,886,589

    Visible=Min

    ServerIPAddr=10.0.0.140

    ButtonScanInterval=20

    ClassInstance=0

    NetworkTiming=5,1

    PollInterval=2000

    ResponseTime=18

    Timeout=12

    TCPcoalesce=No

    UseTCPIP=Yes

    WaitForNewData=500

    ; -----------------------------------------------

    [user]

    Log=Errors+

    RunReady1=C:\ABGC\abgc.exe

    CloseReady1=Yes

    AllowShutdown=Yes

    ; ===============================================

    ***********************

    and here the MCDU-PC:

    [Config]

    Port=8002

    Window=87,85,812,589

    Visible=Min

    ServerIPAddr=10.0.0.140

    ButtonScanInterval=20

    ClassInstance=0

    NetworkTiming=5,1

    PollInterval=2000

    ResponseTime=18

    Timeout=12

    TCPcoalesce=No

    UseTCPIP=Yes

    WaitForNewData=500

    ; -----------------------------------------------

    [user]

    Log=Errors+

    AllowShutdown=Yes

    RunReady1=C:\MCDU\mcdu.exe

    CloseReady1=Yes

    ActionKeys=Yes

    KeySend1=76,10

    KeySend2=76,12

    ***************************

    under Project Magenta- .ini i configured Topmost=ON for all Applications

    Please give me some Advice,

    best regards,

    Thomas

  9. Hi,

    you wrote:

    No, not axes at present. Only buttons and switches. For flight control axes it isn't a good idea because of the latency (delays involved), but I suppose it could be useful for other axis assignments, like flap setting perhaps. But it isn't a facility high on my list. Sorry.

    I don´t know ,if there are also requests from other users,but now i found out,it would be *very* useful for me,to let FSUIPC recognize also the Axis

    from the Client-connected Joysticks.

    As you said, it would be really useful for the Spoiler/Flap Axis.

    So i would like to ask you ,if you could put this Facility a bit higher on your list... :)

    Many thanks for your attention.

    Kind regards,

    Thomas

  10. Hi Pete,

    I asked, because i use FSComm and the FlyByWire Module already. :)

    FSComm supports only the necessariest Axis (Elevator/Aileron/Throttle).

    But my Sidestick has more Axis then this 3.

    I want to assign the Spoilers/Flaps also.

    Robert Fischer said, maybe FSUIPC could assign the remaining Axis.

    But it isn't a facility high on my list. Sorry.

    if it is on your list,all is good. :D

    best regards,

    Thomas

  11. Hi,

    On the Server there is the FS2004.

    On the Client i have installed the PM-MCDU.

    I want to write to the MCDU-Scratchpad using the FSUIPC Keyboard Interface with Joystick Buttons.

    my Question:

    Is it better to install the Joystick on the Server,and let FSUIPC send

    the Button-Events to the Client-

    -or-

    is it better to install the Joystick on the Client(where the MCDU is installed).

    I think,when i install the Joystick on the Client,the Button Event will be sent to the Server FIRST,and then BACK to the Client.

    One way too much -compared to an Joystick,which is installed on the Server and only needs to send ONE WAY(from Server to CLIENT).

    Am I right?

    What should i do - what is the better way for (Network)-Performance?

    Please give advice to me.

    Best regards,

    Thomas

  12. I must say again,your support is impressive!

    The Example above with the GlassCockpit is not so good.

    Of course it is more realistic,as you said ,to switch the GC ON/OFF depending on the AvionicsMasterSwitch.

    But the PM-MCDU takes no care about whether the AvionicMaster nor the

    BattMaster NOR the FS-Shutdown.

    If i shut down the Avionics/Battery or at all the FS -the MCDU is still running.

    That seems not realistic to me...

    (I think i will contact PM for this)

    But with your new Facility,the MCDU shuts down,when I close FS/and using Hotkey -and

    strarts again,when I run up FS again.

    GREAT!

    many thanks,

    regards,

    Thomas

  13. Hi,

    My opinion is,the Application on the Client(for example- the GlassCockpit) should not running anymore,when i close the Flightsimulator on the Server.

    But the WideClient.exe should stay running.

    If there is no Flightsimulator running than also should be NO GlassCockpit.exe running. I think this would be realistic.

    When i start the FlightSimulator on the Server again and want to make a new Flight,the GlassCockpit WILL start again,so the WideClient.exe is running.-I already know .

    If the WideClient.exe is running, a restart of the Application is no problem,caused by the RunReady-Option.

    ___________________________

    How to do:

    I close the FS9.exe on the Server.

    The WideClient.exe on the Client should stay running,

    but the ABGC.exe should close.

    ___________________________

    with the ShutdownHotkey it

    shuts down the WideClient.exe AND the Application.

    But only the Application should close.

    Big Thanks,

    kind regards,

    Thomas

  14. Hi,

    Sorry, i´ve overseen this options.

    But i don´t check out what to do that the program CLOSES,

    when WideServer is serving no more.

    I tried the Shutdown Hotkey in the Server.ini and the

    "AllowShutdown=App" -Option in the Client.ini.

    That works,WideClient closes and the Application closes too.

    But how can i restart WideClient-or

    better i think-if FS closes,the Application should close too,and when i restart the FS the Application restarts again(depending on the RunReady-Option)

    Please help.

    regards,

    Thomas

  15. Hello,

    Now i have WideFS,because i want to build PM-GlassCockpit with many Clients.

    I have some problems running Programs.

    *FSUIPC 322*

    *WideFS 6221*

    Entering "RunOptions" in the FSUIPC is for LOCAL(i mean programs located on the PC where also FSUIPC is installed)

    Programs only?

    What is the best way to start Programs on the Clients?

    Entering the "Run-Options" in the FSUIPC.INI

    or in the WideServer.ini

    or in the WideClient.ini ?

    If I enter (for example) into the WideServer.ini:

    Run1:\\MCDU\MCDUDemo\MCDUDemo.exe

    it always appears at my FlightSim PC(where i have the WideServer.ini),not on the Client(Name:MCDU)

    I have the MCDUDemo ONLY installed at the Client.

    And if i enter it into the WideClient.ini:

    Run1:\\MCDU\MCDUDemo\MCDUDemo.exe

    ,it runs here of course,but it starts immediately as i run WideClient.exe,so

    I want,that a Program on the Client should wait until the FS on the FS-PC is up and running,and closes,when the FS closes?

    How can I program such a "delay" ,like it can be used for Running Programs under FSUIPC (READY,KILL).?-there it works good

    many thanks

    regards,

    Thomas

  16. Hello,

    "Control" is not 200, as you have added, but 512.

    Now its clearer to me .

    For Ctrl+R i have to ADD 512 to the "R"(82) Value = 594

    And 256 for Shift and 768 for Ctrl+Shift.

    Thanks,it works!

    If you program the buttons in FSUIPC on the FS PC then they apply to PM no matter where its modules are.

    That´s what i wanted to know.

    many thanks.

    with the other Problems i refer to PM.

    Sorry,but i thought controlling PM is a FSUIPC-Issue

    Regards,

    Thomas

    [/code]

  17. Hello Pete,

    Of course I downloaded the new 3.22 release immediately.

    But i have already Problems with the Button Controls.

    we wrote here a few weeks ago about the Buttons-

    and i digged me thru all available Docs,but i still have Questions,

    so please be patient with me :)

    *****************

    FSUIPC 3.22

    ABGC Demo build 221

    MCDU Demo build 136

    1 PC

    **************************

    under FSUIPC->Buttons-

    I press a Joystick Button ,select PMGC KEYS from the Drop-Down Menu and enter (for example) 65 (for O) into the "Parameter".

    Back in FS i must press the Joystickbutton TWICE to activate the Function (in this case-the WX-Radar).

    This "Bug?" refers to all PMGC KEYS.

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

    and i have Problems with Shift/Control Compounds.

    What do I have to enter in the Parameter,if i want -for example- Ctrl+R?

    I´ve tried "282" in the Parameter (2 for Control /82 for "R") -

    but nothing happens.

    If i press CTRL+R on the Keyboard with Windows-Focus on the GlassCockpit-all is normally(the Terrain-Function switches).

    ----------

    You implemented the "PM CDU KEYS" Facility.

    I use the MCDU-Demo on the MSFS-PC,

    I press a Joystick Button,select "PM CDU Keys" and enter 65 (A) in the Parameter.

    Normally an "A" schould appear in the Scratchpad of the MCDU...?

    But this works not.

    Controlling the MCDU this way is a VERY important thing for me.

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

    Are the Facilities "PM GC CONTROLS" , "PM GC KEYS" and "PM CDU KEYS" also available through the Network(with use of WideFS)?

    (without having to manipulate the .ini -Files -(very complicated for me)

    ________

    Thank you.

    regards,

    Thomas

  18. I´ve already built my Hardware-FMC ,it is impossible to

    connect it to the MCDU-PC .

    I meant:

    In the case of more PCs,i cannot plug the FMC to any other Computer,because my FMC is not a stand-alone Device.

    There are 2 SAITEK-Dash2 Controllers.

    The second Controller controls not only the FMC,

    it controls other FS-related Functions too.

    Sorry, i cant better explain-my English is soo good... :oops:

    No, there is no demo. You can't use it in any case with only one PC, so it doesn't matter.

    If i must not, i dont wanna use more than one PC,because i think it is easier to control ,and makes less problem...maybe

    I´ve flown a Payware-A320 for a long time,

    but the configuring of FSUIPC/Magenta is very new to me...

    I will send you a Email for the latest Version.

    Thanks for your great Support!!

    Can i use my existing Registration-Data with this "exclusive"

    Version?

    Regards,

    Thomas

    if you are interesting,visit my Homecockpit-HP

    http://members.aon.at/tomsim/cockpit.htm

  19. Thank you very much for the very fast answer!

    I run the Full GC with the MCDU and the FCU

    (All Demo)

    I must say,that the "MODE DECR"- Function works! -but only for one time

    *?*

    PM is not really designed for single PC use at all.

    I thought so...

    So the best thing would be,to connect more PCs.

    I´ve already built my Hardware-FMC ,it is impossible to

    connect it to the MCDU-PC .

    Is there any Demo of WideFS?

    I thought i don´t need it as i bought Fsuipc ONLY

    :?

    I must study your answers-it is very complex! :D

    What you really need is a facility in FSUIPC, similar to the GC Controls facility, with parameter, to send values to the "CDU Keyboard Interface" offset (see PM's FSUIPC Offsets document on the PM site, offset 5428). I can add that without any problem I think.

    It would be great,i will try it at the new release.

    Thanks you,

    Regards,

    Thomas

  20. Hallo,

    i have also a Problem with assigning Buttons to the PM-Mode/Range Control.

    example:

    I assign a Joystick Button to the Function "Mode ARC".

    All is good,the ND switches to ARC.

    But when i assign the Button to the Function "Mode DECR" or "MODE INCR" -the same with the Range- , it happens NOTHING :shock:

    Another Question:

    Is it possible to control the MCDU through FSUIPC?

    I mean NOT the Function Keys, i mean the A-Z,1-0 Keys.

    I have built a Hardware-MCDU with Joystick-Controllers.

    Assigning the Keys with A-Z,1-0 is no Problem with FSUIPC,

    but how can i assign it to the PM-MCDU?

    At this time i use the HW-MCDU to control the MS-GPS,

    to enter the ICAO-Codes.

    There is no Problem. :)

    The Problem is the Link to the PM-MCDU.

    I must say, i have only one PC,no Network.

    Thanks for any answer

    Greets

    Thomas

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