Jump to content
The simFlight Network Forums

saabpilot

Members
  • Posts

    27
  • Joined

  • Last visited

Everything posted by saabpilot

  1. Hi again Pete, That answered my question so thanks for the fast answer. MS (FS) has made a weird internal (airfile) MAC% calculation, probably it did not matter at the time of FS9 birth :razz: Now when you are able to "load" FS aircrafts by "stations" it does since you will try to keep as close to 25% MAC for your TOW as possible in a B737 model. The below example is just to show how the MAC% numbers affects the envelope (on the right side). ( DOW = Dry Operating Weight, ZFW = Zero Fuel Weight and TOW is Takeoff Weight ) If out of the envelope - the a/c cannot fly. Bjorn
  2. Hi Pete, I am curious how you calculate MAC % in FSUIPC. When I have a specific load in an OPENSKY B738 TopCat gives me MAC% = 24.27 which is correct and the FSUIPC offset 2EF8 gives 39.7%. The 39.7% is clearly not the correct MAC% as the aircraft would then be totally out of envelope. The fuel and payloads made by TopCat are within the standard B737 loading envelope ( 2EF8 8 CG percent, as a double (FLOAT64). This is the position of the actual CoG as a fraction (%/100) of MAC ) Clearly an error somewhere - either the MAC% calculation vs. Opensky B738 or something else ?? I hope you can give some light on this. Best from Stockholm, Bjorn
  3. OK Thanks Pete. Your old eSound works OK now in FS9 for what I needed it to. LUA seems to be a bit of overkill for this and also I cannot find any primer how to configure LUA and set it up for FS9 in the computer. Best, Bjorn
  4. Hi Pete, I have tried in vain to get the sound file play when Speed brakes are deployed (and not armed). Offset: 0BD4 The dll is in FS9/modules and the sound is in FS9/Sound folder None of the 2 actions below in esound.cfg triggers the sound and I cannot find out why :roll: [Devices] 1=Primary Sound Driver 2=HD Audio rear output [sounds] 1=PMDG_spoiler.wav [Triggers] 1=SPOILERS_POS_LEFT>0&SPOILERS_POS_LEFT<16095,1,1 2=VL0BD4>0,1,1 Best, Bjorn Bjorn Harlin Stockholm, SWEDEN
  5. The new version might have fixed that problem. :D I did not note that you had changed the dll but will install it a.s.a.p. Thanks a lot for the fast respond. Best, Bjorn
  6. After assigning the Rudder and Brake axes in FSUIPC I got one of the two brakes (Axes) written OK into FSUIPC.ini The remaining (0Y) only writes = "0=0Y, 256" in the ini file. :( Then I manually changed the ini file on basis of the X axes values (but with different value = x02) This seems to "stick" in FSUIPC.ini so now I have this: ...... Rudder=-16345,-560,219,16267/8 SlopeRudder=-6 LeftBrake=1497,13619/8 RightBrake=357,13044/8 ...... [Axes] 0=0Y,BR,-15183,-1130,x05006DB0,x02,x09006DB0,x02 1=0X,BR,-15183,-1130,x05006DB0,x01,x09006DB0,x01 I will watch the ini file closely when I make other settings to see if it changes the "Axes" values and will let you know if this happens. Any case, it seems like a small bug somewhere in the axes setting preventing the settings partially from being written into Fsuipc.ini Bjorn
  7. Answer is, I dont know - never needed to calibrate my CH pedals :) However you have a good idea so I will try to assign the brakes in FSUIPC and that might fix the problem. I let you know tomorrow. Why use TSR autobrakes? - Simply because they give you "runway condition" prone brakes - e.g. they simulate wet/snowy/dry runways and they simulate the B737 brake accu correctly. I will buy you a beer at Lelystad if the tip worked :D Best Bjorn www.boeing737sim.se
  8. The TSR autobrake program simulates correctly B737 autobrakes together with PMsystem. Details in the programming is out of my knowledge but I can forward your comments to Thomas Richter who is the author. The FSUIPC.ini does not have the "AXIS" subpart, I am enclosing a copy of my file here below. As I told you, the settings does not stay nor become written to FSUIPC.ini But - all other settings I make e.g. "buttons" writes OK. [JoyNames] AutoAssignLetters=No 0=CH Pro Pedals USB Rudder Pedals 1=CH 3-Axis 10-Button+POV USB Yoke 2=BU0836X Interface [General] History=MY6W6UFL6GW23ECN0YQA9 TCASid=Flight TCASrange=40 TrafficScanPerFrame=10 AxisCalibration=No CentredDialogue=Yes ClearWeatherDynamics=Yes OwnWeatherChanges=No WeatherReadInterval=4 MoveBGLvariables=Yes TimeForSelect=4 MainMenu=&Modules SubMenu=&FSUIPC ... WindSmoothing=Yes AutoTaxiWind=No PropTaxiWind=No TimeSetMode=Partial WhiteMessages=No ThrottleSyncAll=No GraduatedVisibility=Yes LowerVisAltitude=0 UpperVisAltitude=25000 UpperVisibility=6000 GenerateCirrus=Force WindShearSharp=No UpperWindGusts=Yes ExtendMetarMaxVis=Yes DisconnTrimForAP=No ZeroElevForAPAlt=No AutoClearWeather=Yes ExtendTopWind=Yes WindSmoothness=5 SmoothPressure=Yes PressureSmoothness=5 SmoothVisibility=Yes VisibilitySmoothness=2 MaxSurfaceWind=0 WindLimitLevel=200 WindDiscardLevel=400 WindAjustAltitude=No WindAjustAltitudeBy=2000 MinimumVisibility=0 MaximumVisibilityFewClouds=6000 MaximumVisibility=2000 MaximumVisibilityOvercast=2000 MaximumVisibilityRainy=1000 OneCloudLayer=No ThinClouds=No ThinThunderClouds=No CloudThinness=1000 ThunderCloudThinness=10000 CloudTurbulence=Yes CloudIcing=Yes WindTurbulence=No SuppressAllGusts=No ExternalOptionControl=Yes AutoTuneADF=No KeepFS98CloudCover=No ShowPMcontrols=Yes MagicBattery=Yes RudderSpikeRemoval=Yes ElevatorSpikeRemoval=Yes AileronSpikeRemoval=Yes ReversedElevatorTrim=No TrapUserInterrupt=Yes NavFreq50KHz=Yes ClockSync=No SmoothIAS=Yes SetVisUpperAlt=No VisUpperAltLimit=6000 MaxIce=-4 WindSmoothingDelay=0 WindSmoothAirborneOnly=Yes VisSmoothingDelay=0 VisSmoothAirborneOnly=Yes SuppressCloudTurbulence=No SuppressWindTurbulence=No SpoilerIncrement=512 ShortAircraftNameOk=No FixWindows=No FixControlAccel=No StopAutoFuel=No MinIce=-4 LimitWindVariance=No TrafficControlDirect=Yes ShowMultilineWindow=Yes SuppressSingleline=No SuppressMultilineFS=No WeatherReadsFast=No CorrectVSsign=No MouseWheelTrim=No MouseWheelTrimSpeed=1 AxisInterceptIfDirect=No ZapSound=firework UpdatedByVersion=3930 UseProfiles=No [JoystickCalibration] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No FlapsSetControl=0 FlapDetents=No ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=0 RudderTrimControl=0 CowlFlaps1Control=0 CowlFlaps2Control=0 CowlFlaps3Control=0 CowlFlaps4Control=0 MaxSteerSpeed=60 Aileron=-16344,-4840,465,8099/8 SlopeAileron=6 Elevator=-16355,-6823,0,16267/8 SlopeElevator=-2 Rudder=-16383,-5591,-3083,16383/8 SlopeRudder=6 LeftBrake=-16380,16380/16 RightBrake=-16380,16380/16 [buttons] ButtonRepeat=20,10 1=P1,7,C2040,0 2=P1,6,C1001,0 3=U1,6,C1002,0 4=R1,8,C65607,0 5=R1,9,C65615,0 6=P1,0,C1079,0 7=U1,0,C1013,0 8=P1,4,C65829,0 9=P1,5,C65567,0 10=P1,1,C66147,0 11=R1,32,C65735,0 12=R1,34,C65672,0 13=R1,38,C65671,0 14=R1,36,C65734,0 15=U1,1,C65875,0 16=P2,31,C1001,0 17=U2,31,C1002,0 18=P2,2,Cx010031F4,x00 19=P2,1,Cx010031F4,x02 20=P2,6,Cx010031F4,x03 21=P2,5,Cx010031F4,x01 22=P2,0,Cx0D006DB3,x08 23=P2,30,Cx05006DB3,x01 24=U2,30,Cx09006DB3,x01 25=P2,4,Cx05006DB3,x04 26=U2,4,Cx09006DB3,x04 28=P2,3,Cx05006DB3,x02 29=U2,3,Cx09006DB3,x02
  9. Hi again Pete, A picture says more than a thousand words, so I have attached an extract from Thomas Richters manual for TSR Autobrake Pro. This is an add-on fto PMsystems. I am trying (in vain) to get FSUIPC to keep those settings neccessary for the A/B function. Same applies for right brake but with x02 as parameter. Best, Bjorn P.S. The download file name for my FSUIPC (from PM) says FSUIPC 44.53 :)
  10. Hi Pete, Need help. When assigning control sequences to my CH USB Brakes for TSR Autobrake (offset and parameters) FSUIPC do not write those to FSUIPC.ini :( This happened with previous FSUIPC version too as well as the latest one 44.53 I can see FSUIPC reports all joysticks OK. When I run RESCAN and press e.g. left pedal I get the IN/OUT values OK too. Then I tick the "Control Sent" and enter "Offset byte Setbits" and its offset and parameter. Continues with Control to Repeat and "Control Sent" plus "Offset Byte Clrbits" + its offset and Parameter. Finally I press OK and FSUIPC seems to save the settings. But when looking in the ini file no setting is there and it does not show again after a restart of FS and "Reload all Assignments" I have in vain tried this for ½ day :( Do you have any hint what could be wrong? Best, Bjorn
  11. I believe the above will work also for FSX as the offsets should be the same. Why not make a test - takes only 1-2 minutes and if it does not work, then ask.
  12. Great explanation Pete, It worked perfectly! Testid with a button. Have not yet decided if I will assign this to a toggle or button. Many thanks ! Bjorn
  13. Hi Pete, Thanks. As usual a very fast answer from you. I have found the offsets (FS9 Squawkbox3) below at the Squawkbox site, but have no clue how to implement them on a joystick button so I appreciate your kind help with what to write in the FSUIPC.ini (A little computer ilitterate you might say :) ) Best, Bjorn
  14. Hi, Anybody who can give me advice how to toggle Mode C / Standby on the Vatsim/IVAO via a hardware toggle? This is possible via FSUIPC and GoFlight or CP Flight Xponder modules, but I wish dearly to find a stand alone solution. Best Bjorn www.boeing737sim.se
  15. F.y.i. The serial port emulator, GPSout and mappingprogram all works like a charm at any baudrate. Thanks again for your eminent help. Best, Bjorn
  16. I will let you know if I find any problems with this emulator. Best, Bjorn
  17. This one I found works flawlessly - why it can override COM1/COM2 that are sort of standard ports I do not know. I just test runned it since a couple of hours and it do work as advertised :D I run WIN Xp as OP. I have used 4800 bps and will increase the baudrate to get a smoother chart operation, but it is fully usable at 4800 as it is set now. Maybe my wi-fi connection screwed things up with your supplied emulator or something else is wrong or different in our computer setups. Thanks a lot for the very fast answers and directing me the right way with PortMon. That enabled me to track down the problem. Without your advice I would have given up. See you in the Vatsim/IVAO skies :D Best, Bjorn
  18. :D :D :D Success !! The culprit was as I suspected the mixW portemulator that did not connect the ports correctly. I d/l another comport emulator "Virtual Serial Port Driver 6.0" and set it to "Enable strict baudrate emulation" + set up the pair on COM1 and COM2. WideFS now sends to COM1 and FlliteDeck receives on COM2 regardless what "sentences" / baudrate I use. (If I like I can set the driver to use any com port number) The only backlash is the emulator cost = 100 US $ :x vs. yours for free. Maybe I should remove all emulators again and try to set up mixW on COM1+2 ?? Bjorn
  19. Have done that, but still no joy. :evil: Have tested with all combinations of settings sentence/baudrate. However I can see in the PortMon that: 1. FS sends the data to COM4 and also that it uses the "current" sentence setting 2. Flitedeck program scans COM5 for a GPS Flitedeck does not find any data but opens and scans the COM5 port when asked to search for the GPS. Flightdeck is "settable" to any of your sentences and also to any baudrate for "default GPS" or can be configured direct for most if not all flight GPS:es existing. In PortMon you can only see that data from FS goes to COM4 but not that it is "replicated" in COM5 - could it be that the two ports in the pair are not properly interconnected ?? E.g. the program searches an empty COM5 port. Bjorn
  20. Changed to COM4 + COM5 Now it is a faint hope - the warning has changed from "cannot open com port" to "no output detected" :) Tomorrow I will try all supported sentences once again - it is late here now 23:45 LT (Thailand) :D Thanks so far for your very kind help and I will post the results tomorrow. Best, Bjorn
  21. I will make the pair com4-com5 instead and test - might do the trick - i will post the results a.s.a.p.
  22. Hi again Pete, Sorry for the misunderstanding :) I also made a typo - I have actually set COM10 and Com 11 as the pair and set GPSout to transmit to COM10 which I can see it does. But the Jepp FliteDeck says it cannot open the COM11 port ! So something is wrong in FliteDeck or the COM11 port is blocked somehow. Now using your setup for the "sentences" - but since the port is "sort of" unaccessable it does not help much. Best, Bjorn
  23. Hi again, I d/l the PortMon tool and changed the pairs to COM10 and COM11. My old notebook utilizes COM1-COM3 only as far as I can see. Portmon clearly shows me that it gets the data on COM11 now, however no success yet with the map. In Portmon I also can see and verify what "Sentence" is transmitted. I have tried all combinations of Sentence params but would like to try yours for FliteMap - Is Flite Map a Garmin product and if so do you have the product number e.g. something like GPS 215 NMEA 0183, if so I can set up the map as FliteMap and test. Right now when I make the map program search for the Gps on COM11 it says it cannot find any. (Can´t open Com11) The SB3 problem was suddenly solved when I reinstalled your latest FSUIPC :) I tried that before with no success, but now it suddenly works OK. Best, Bjorn P.S. Strangely enough I can not see any port information on the laptops System-Hardware-Device Manager pages as I do on my "stationary" computer?
  24. Hi Pete, Thanks for the promt answer. " am very surprised you can use such port numbers as virtual ports on any PC" As I am not a programmer nor a comm expert it might well be that the pair (COM2 and COM3) I assigned is the culprit. What "pairing" of the com ports do you suggest? As for the SB3 problem I will run it again with 3.75 and attach the log here in a couple of hours. Bjorn
  25. Hi Pete, Two problems. 1. I have installed latest and regged versions in FS9 of FSUIPC, WideServer, and GPSout 2.60 on the FS9 computer and WideClient on an laptop running a GPS enabled flight map program. This can attach to virtually any brand of commercial flight GPS and is capable of scanning all com ports for a GPS signal. (Network is 108 bps Netgear Wi-Fi with only the FS computer and the laptop) Also installed the Virtual Serial Port driver and assigned COM2 and COM3 to those. The GPSout.ini has the lines : Sentences=RMA,RMC,GLL,GGA (for test) Port=WideFS Interval=1000 Speed=9600 PosTo6Decimal=Yes In WideClient.ini I have added last: [GPSout] Port=COM2 Speed=9600 WideFS connects OK with the client, but no data gets to the virtual COM2 port. The virtual port driver is installed per install instructions and shows in Control Panel/System as working OK The map program when running says it cannot open COM2 when I run a built in test that scans all COM ports for GPS. What can be wrong?? 2. Also I cannot get Squawkbox 3 to initiate FSUIPC - a warning about this comes up after FS9 start. I have tried to delete FSUIPC.dll and let SB3 install a "known OK" version (3.50) but get the same error. Best, Bjorn
×
×
  • 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.