
kzuerner
Members-
Posts
48 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Gallery
Downloads
Everything posted by kzuerner
-
Thanks Pete! I will give it a try tomorrow! Regards Klaus
-
Thanks Pete! I was suspecting that I am "on the wrong track". So the only way would be to assign "Trim Down" to two of the "buttons" and "Trim Up" to the other two buttons (as I could identify 4 buttons)? Regards Klaus
-
Hi Pete, after installing FSUIPC 3.556 I dedcided to let all axis be processed by FSUIPC. So I disabled the Joystick in MSFS2004, deleted alle entries in fs9.cfg and got rid of the devices.cfg as you instructed us. I have been able to assign axis allready successfully and I do have the feeling (not enough test-flights yet) that calibrating axis through FSUIPC brings me closer to the feeling of "real flights" (flying real planes also). One "axis" that I also would like to assign is the elevator trim on my GoFlight GF-LGT. But I do not really find out how. Tried several things without success. I do get it as a "button" in FSUIPC but I am not able to get it as an "axis" so I can calibrate it with FSUIPC (Page 6 on Joystick calibration). How would I have to set it right? Regards Klaus
-
Thank you Pete It works as you wrote it! Regards Klaus
-
Hi Pete thanks for your reply. Okay your assumptions are right. I was talking about Project Magenta and I have had 3 PCs before and currently have 2 (one is "kaputt"). Anyway! Your second reply ist the answer to my "challenge". It works if you define the "RunReadyN" parameter in the "KeysendN" line. So my lines in WideClient.ini look like: RunReady1=C:\PM\MCP\MCP.EXE RunReady2=C:\PM\PFD\PFD.EXE RunReady3=C:\PM\PFD2\PFD.EXE CloseReady1=Yes CloseReady2=Yes CloseReady3=Yes KeySend1=34,8,RunReady2,ThunderRT6FormDC,"PFD GLASS COCKPIT" ;Page Down KeySend2=33,8,RunReady2,ThunderRT6FormDC,"PFD GLASS COCKPIT" ;Page Up KeySend10=9,8,RunReady3,ThunderRT6FormDC,"PFD2 GLASS COCKPIT" ;Tab" I found out the the Windowsname now is ThunderRT6FormDC" No changes in PFD.INI necessary. Thank you again Klaus
-
Hi Pete, sorry if that issue was allready raised before. Also I searched I didn't find an answer for me. I had to reinstall my FS2004 from scratch and as I did that I had to connect two screens to one PC which where on two PCs before. On those screens I display PFD/ND on Nr. 1 and EICAS on Nr. 2. This all works well. But I also want to change the display with the keyboard from my "Main-FS-PC". I can do that with WideFS and "Keysend". In principle it works (and I had no problems when I had two PCs for the two monitors). The problem I now have is that some of the "keystrokes" should end up at PFD/ND and others on the EICAS-screen. Now I learned that I have to use different "classnames" to distinquish between the two applications. I tried a lot but I was unable to find out how I could do it. Both applications use the same classname and the same "Windows-Title". In your manual (I think in WideFS) you mention that you can set the classname in the pfd.ini-file. Do you know how?? Or is this a problem for our friends at PM? Thank you for your assistance! Klaus
-
Thank you Pete! I played with "FSInterrogate" and also found some "Offsets" in the GFDisplay documentation. But I admit I was not aware of the documentation from PM. Sorry! Thanks again! Klaus
-
Hi Pete, I have made some progress with programming my GoFlight Modules with FSUIPC and GFDisplay. My problem is that I still do not understand where I can get the right information to set "GFDisplay.ini" correct. I am trying to assign buttons for the PM MCP to a GF-RP48. With FSUIPC it was no problem to assign the correct buttons. But now I want to "illuminate" the lights at the RP48. I found out that you use a "Offset" (X04F0) and a "Bitmap" (eg: M0001 for Autopilot 1). But I could not find out what you set when I press VNAV, LNAV and when I press the buttons on the "ND" (eg.: PM ND VOR Display) etc. The "Control number" in the GFDisplay does not help as I obviously need some "Hex-Value". The documentation for the FSUIPC SDK does not help for PM. Can you give me a hint where and how I find the information I need. Regards Klaus
-
Thanks Pete, I have set the Option "Systemtime" (dont know if I translated it correctly) but as you mentioned allready it does not work. Could you give me a link where to find "FSRealTime". I searched with Google, got a lot of hits but none pointed me to the "source" of that program. Regards Klaus
-
Hi Pete, forgive me if I ask my question in the wrong forum. I normally create flights (eg. from EDDH to LOWK) and save them. When I then use those flights again they use the Date and Time when they where saved. Is there a possibility that my saved flights always use the current Date/Time? Thanks Klaus
-
Thank you Pete for your fast response. I surely believe you should get the "gold-medal" for the best and fastest responses in the flightsimmer forums. So what I want to do is: 1. Assign a function in FS9 (eg. Toggle Battery Master) to a button or switch (however you call it) on the GF-T8. This I do with FSUIPC. In the FSUIPC.ini I find the "Control" (eg.: C66241 for Toggle Battery Master). 2. Now I want the LED above the switch to be lit when the Battery Master switch is "on". If I understand you right I have to look in the FSUIPC SDK to find out which offset is used by the "Battery Master". Thanks for your advice. I will give it a new try. Regards Klaus
-
Hi Pete, I try to use your GFDisplay program and try to "code" the ini-file, with only little success (FSUIPC and WideFS are at the latest release-level). Okay you generously left the programming of a GFT8 to the user because its so simple but ...... Do I understand it right: With FSUIPC i "program" a key (a control) that sets a value somewhere. In GFDisplay I have to "find" that value (offset) write a "condition" and "test" it? But where would I find which "control" sets which "offset"? I also give you just a little example which I did: 14=X3101 S8; Alternator Master 15=X3102 S8; Battery Master 16=X3103 S8; Avionics Master [GFT8.0] L0=C14=1 L0=!C14=0 L1=C15=1 L1=!C15=0 L2=C16=1 L2=!C16=0 It works but did I do it too complicated or correct? Regards Klaus
-
Hi Pete, any news on that new program? Regards Klaus
-
Thanks Pete! I will wait for the new program. I would prefer to use FSUIPC to program the switches etc. as this gives me the ability to have different setups for different planes. Regards Klaus
-
Hi Pete, sorry to disturb, you may have answered that question allready but I could not find the proper answer with the search-function and its allready late in the night.... I managed to program my GF-P8 and GF-RP48 modules with FSUIPC to control my PDMG 737 and PM. When I set one of the Buttons on (e.g. Toggle Nav-Light) through FSUIPC then the little green light (on the GF module) will not be illuminated. Is this correct? Do I have to live with it or did I do something wrong (I just programmed it in the tab "Buttons"). Thank you also for the latest "Debug-Version" but I could not test it yet. But I will report. Regards Klaus
-
I seem to have some problems to attach the log. I try it again. Regards Logs.zip
-
Hi Pete, I have the same experience. I am running FS4K (flying PDMG 737) on one PC and PM GC and MCP on a second PC. I also have on a third PC running PM GC to display EICAS (or how it is called). All by a sudden Wideclient exits on my second PC (running GC and MCP). You will not find it in the tasks. I did not have that problem on my PC running the EICAS. As I could not see any problem in the Client-Log with 6.44 (have not checked the Server-Log) I took your Version 6.442 and hat the same experience. Therfore I send you attached the two logs. Maybe you can trace the problem now. Regards
-
Thank you for that quick reply!! I admit I have not asked PM. So if I understand you right I have not done big mistakes in my ini-files. Why do I get "Errors" in my log. That is interesting to me. Maybe I can just ignore them. This was the complete log of the client. Again thanks!! Regards Klaus
-
Hi Pete I am useing (even) registered Versions of FSUIPC (Version 6.44) and WideFS (Version 6.441). I also use PDMG B737 and PM Glasscockpit. Now I try to "Autostart" my GC which works fine. WideClient starts PM after FS4K is startet. When I shut down FS the PM PFD gets shut down but starts immedeately (?spellt correct??) again. What do I do wrong?? Wideserver.ini: [Config] Port=8002 AutoRestart=0 AutoUpdateTime=13 MaximumBlock=4096 NoStoppedRestarts=Yes RestartTime=10 SendTimeout=15 TCPcoalesce=No ; ----------------------------------------------- [user] Log=Errors+ AutoShutdown=Apps ; =============================================== [ClientNames] 1=HAMBURG17 2=HAMBURG5 3=HAMBURG4 4=PC121 WideClient.ini [Config] Port=8002 Window=43,44,886,589 Visible=No ServerName=192.168.100.16 ButtonScanInterval=20 ClassInstance=0 NetworkTiming=5,1 PollInterval=2000 ResponseTime=18 TCPcoalesce=No UseTCPIP=Yes WaitForNewData=500 ApplicationDelay=0 MaxSendQ=100 WhenMaxSendQ=Recon SendScanTime=10 Priority=3,1,2 ; ----------------------------------------------- [user] Log=Errors+ ;Log=Debug AllowShutdown=AppOnly RunReady1=C:\PM\PFD\PFD.EXE CloseReady1=Yes ActionKeys=Yes KeySend1=34,8;ThunderRT5Form,"PFD" KeySend2=33,8;ThunderRT5Form,"PFD" I also have some interesting messages in the log: ********* WideClient Log [version 6.441] Class=FS98MAIN ********* Date (dmy): 30/12/04, Time 18:57:36.812: Client name is HAMBURG5 47 Attempting to connect now 47 Trying TCP/IP host "192.168.100.16" port 8002 ... 47Okay, IP Address = 192.168.100.16 984 Error on client pre-Connection Select() [Error=10061] Connection refused 984 Ready to try connection again 1047 Attempting to connect now 71422 Connection made okay! 77969 New Client Application: "pfd" (Id=420) 130172 Shutdown request received! 131156 Error on client post-Connection Select() [Error=10053] Software caused connection abort 131219 Attempting to connect now What do I do wrong?? :oops: Regards Klaus Zürner info@hsc-gmbh.de