kwompus21

And as they say - 'there it is'. All works now. As I noted earlier that it was probably something obvious (aka dumb) that I was doing. Yes, I was 'dragging' the .exe file out of its folder - and I have to say I noted the WideClient files populating on my desktop but didn't know what they were - now I do. Also, 'I' created the folder called 'FSUIP' on the P2A as a place hold the WideClient files - that too is on me and I totally get how it confused you. In the end, you have solved my issue and I thank you. You don't get enough credit for the time you take w/ your customers.

Either operator error or a potential issue but I cannot find a WideClient log - I am looking on the P2A computer in the FSUIPC folder that holds the WideClient.ini file and did have the WideClient.exe file, but I pulled it out to reside on my desktop. Would it potentially be sent to a different location or would it be housed on the SIM computer in the Documents folder for FSUIPC. Yes - I opened Navigraph Charts and opened a chart - F12 will works w/ PTT. Note - in order for F12 to work P2A must be connected to the P3D and for that to happen WideClient must be started/connected which tells me WideClient is working (but still can't find the log :)) I am on Widows 10. I can try different function keys. I will refer to your documentation which I believe walks through how to identify the keyboard keys numerically in the Wideclient.INI - or I can just steal what you did 🙂 for F1. Which I believe would look like this: [User]Log=Errors+KeySend1=112,16 ; F1 Press PTT for P2A (or Click F1)KeySend2=112,24 ; F1 Release PTT for P2A (or Release F1)UseSendInput=Yes Edit - I just noted your response in the P2A forum - I probably should have deleted that post now that I have this post - my plan was to resolve the issue and post a link for others to see - I didn't know you responded in the P2A forum and did not mean to have duel active posts. Thank you again so much for your time! Chuck

Thank you for the quick response. Sleep well :) Answers: Yes - I copied is from their manual. ********* WideServer.DLL Log [version 7.076] ********* Blocksize guide = 8192 (double allowed) Date (dmy): 07/12/20, Time 18:37:02.223: Server name is P3D-COMPUTER 15093 Initialising TCP/IP server 15093 Initialising UDP/IP server 16000 Broadcasting service every 1000 mSecs ********* FSUIPC6, Version 6.0.11 (26th November 2020) by Pete & John Dowson ********* Prepar3D.exe version = 4.5.14.34698 Running inside Prepar3D v4 Module base=7FFCC26E0000 Windows 10 Pro 64 Bit reported as Build 19042, Release ID: 2009 (OS 10.0) Reading options from "C:\Users\Chuck\Documents\Prepar3D v4 Add-ons\FSUIPC6\FSUIPC6.ini" Checking the Registrations now ... User Name="Chuck Steinmetz" User Addr="rcsteinmetz32@gmail.com" User WideFS Name="Chuck Steinmetz" User WideFS Addr="chuck.steinmetz@fox6now.com" FSUIPC6 Key is provided WideFS7 Key is provided 16 System time = 07/12/2020 18:31:38 16 FLT UNC path = "\\P3D-COMPUTER\Users\Chuck\Documents\Prepar3D v4 Files\" 32 Using DialogMode 47 FS UNC path = "\\P3D-COMPUTER\Prepar3D v42\" 125 ---------------------- Joystick Device Scan ----------------------- 125 Product= MFG Crosswind V2 125 Manufacturer= MFG 125 Serial Number= MFG500002 125 Vendor=16D0, Product=0A38 (Version 33.1) 172 GUIDs returned for product: VID_16D0&PID_0A38: 172 GUID= {C7FAF5E0-9850-11EA-8001-444553540000} 172 Details: Btns=2, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R4096,U0,V0,X4096,Y4096,Z0 172 Product= FDS-FC1 172 Manufacturer= TEKWorx Limited 172 Vendor=1FD1, Product=03ED (Version 1.35) 172 GUIDs returned for product: VID_1FD1&PID_03ED: 172 GUID= {C7FB6B10-9850-11EA-8003-444553540000} 172 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0 188 Product= AGRONN B737 Yoke V2.2 203 Manufacturer= Microchip Technology Inc. 203 Vendor=04D8, Product=F30F (Version 0.2) 203 GUIDs returned for product: VID_04D8&PID_F30F: 203 GUID= {123C47A0-BA28-11EA-8001-444553540000} 203 Details: Btns=5, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X32767,Y32767,Z0 203 ------------------------------------------------------------------- 219 Device acquired for use: 219 Joystick ID = 2 (Registry okay) 219 2=MFG Crosswind V2 219 2.GUID={C7FAF5E0-9850-11EA-8001-444553540000} 219 Device acquired for use: 219 Joystick ID = 1 (Registry okay) 219 1=FDS-FC1 219 1.GUID={C7FB6B10-9850-11EA-8003-444553540000} 219 Device acquired for use: 219 Joystick ID = 0 (Registry okay) 219 0=AGRONN B737 Yoke V2.2 219 0.GUID={123C47A0-BA28-11EA-8001-444553540000} 219 ------------------------------------------------------------------- 250 Controllers are set to OFF 250 LogOptions=00000000 00000001 250 ------------------------------------------------------------------- 250 SimConnect_Open succeeded: waiting to check version okay 250 Opened separate AI Traffic client okay 18985 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.5.14.34698 (SimConnect: 4.5.0.0) 18985 Initialising SimConnect data requests now 18985 FSUIPC Menu entry added 19000 ... Using Prepar3D with Professional License 19016 \\P3D-COMPUTER\Users\Chuck\Documents\Prepar3D v4 Files\KEGE Ramp2.fxml 19016 \\P3D-COMPUTER\Prepar3D v42\SimObjects\Airplanes\Sim-Avionics 737-800 Winglets\B737-800.air 22969 ### The user object is 'Boeing 737-800 XL Airways Excel' 22969 ### Mode is NORMAL 23891 ### Mode: PAUSE on 69016 Loading Complete ... 69032 ### Mode is NORMAL 69703 User Aircraft ID 2 supplied, now being used 69703 Aircraft loaded: running normally now ... 70282 System time = 07/12/2020 18:32:49, Simulator time = 14:00:01 (21:00Z) 70297 Aircraft="Boeing 737-800 XL Airways Excel" 112032 *** Entered Keys option page *** 113438 *** Exiting Keys option page *** 135360 *** Entered Buttons option page *** 138235 *** Exiting Buttons option page *** 321125 LogOptions changed, now 40000000 00000001 323407 -------------------- Starting everything now ---------------------- 323407 Starting WideServer now ... 323422 ASN active function link set 323422 Ready for ActiveSky WX radar with additional data 323985 Button changed: bRef=0, Joy=0, Btn=0, Pressed 323985 [Buttons] 11=P0,0,C1006,1 323985 FSUIPC Control Action: Ctrl=1006, Param=1 323985 SendKey buffer[0] = 1 324188 Button changed: bRef=0, Joy=0, Btn=0, Released 324188 [Buttons] 12=U0,0,C1006,2 324188 FSUIPC Control Action: Ctrl=1006, Param=2 324188 SendKey buffer[1] = 2 324360 Button changed: bRef=0, Joy=0, Btn=0, Pressed 324360 [Buttons] 11=P0,0,C1006,1 324360 FSUIPC Control Action: Ctrl=1006, Param=1 324360 SendKey buffer[2] = 1 324453 Advanced Weather Interface Enabled 324563 Button changed: bRef=0, Joy=0, Btn=0, Released 324563 [Buttons] 12=U0,0,C1006,2 324563 FSUIPC Control Action: Ctrl=1006, Param=2 324563 SendKey buffer[3] = 2 324750 Button changed: bRef=0, Joy=0, Btn=0, Pressed 324750 [Buttons] 11=P0,0,C1006,1 324750 FSUIPC Control Action: Ctrl=1006, Param=1 324750 SendKey buffer[4] = 1 324922 Button changed: bRef=0, Joy=0, Btn=0, Released 324922 [Buttons] 12=U0,0,C1006,2 324922 FSUIPC Control Action: Ctrl=1006, Param=2 324922 SendKey buffer[5] = 2 325063 Button changed: bRef=0, Joy=0, Btn=0, Pressed 325063 [Buttons] 11=P0,0,C1006,1 325063 FSUIPC Control Action: Ctrl=1006, Param=1 325063 SendKey buffer[6] = 1 325250 Button changed: bRef=0, Joy=0, Btn=0, Released 325250 [Buttons] 12=U0,0,C1006,2 325250 FSUIPC Control Action: Ctrl=1006, Param=2 325250 SendKey buffer[7] = 2 325328 Button changed: bRef=0, Joy=0, Btn=0, Pressed 325328 [Buttons] 11=P0,0,C1006,1 325328 FSUIPC Control Action: Ctrl=1006, Param=1 325328 SendKey buffer[8] = 1 325485 Button changed: bRef=0, Joy=0, Btn=0, Released 325485 [Buttons] 12=U0,0,C1006,2 325485 FSUIPC Control Action: Ctrl=1006, Param=2 325485 SendKey buffer[9] = 2

I had to reload P2A on a new drive due to a crash. Previously I had PTT set up via the SIM computer and it was working. I am now on P3d V4.5 and FSUIPC6. Following the directions in the P2A user manual I set up a button from my Yoke to KEYSEND 1-255 (WideFS) w/ 1 and 2 and 'Select for FS Control' ticked. I inserted the text (pls see below) in the WideClient.ini file under 'Users' on the P2A computer. Then I set the P2A F12 button as the default PTT Hot Key in P2A in the Conifg page. No luck. I have a registered version of both FSUIPC and WideClient. WideClient shows 'connected' and the other functions of P2A work w/ the SIM computer. When I push F12 on my P2A keyboard the PTT button works/illuminates. I'm sure I'm missing something very obvious - any help would be appreciated. The FSUIPC6.ini file has the following code on the SIM computer: [Buttons] PollInterval=25 ButtonRepeat=20,10 1=R0,2,Cx010053F4,x02 -{offset byte set, offset 53F4}- 2=U0,2,Cx010053F4,x00 -{offset byte set, offset 53F4}- 3=R0,3,Cx010053F4,x01 -{offset byte set, offset 53F4}- 4=U0,3,Cx010053F4,x00 -{offset byte set, offset 53F4}- 11=P0,0,C1006,1 -{KEYSEND 1 for WideFS}- 12=U0,0,C1006,2 -{KEYSEND 2 for WideFS}- Here's how it looks in the WideClient.ini on the P2A computer. [User] Log=Errors+ KeySend1=123,16 ; Click F12 KeySend2=123,24 ; Release F12 UseSendInput=Yes Chuck

RESOLVED - this was 100% operator error - I neglected to include \radar.bin at the end of the path which results in the Error 5 message. But I learned a heck of a lot about networking along the way. So for anyone else that comes along w/ a similar issue this is what it is supposed to look like - ASNwxRadarPath=\\Avionics\c\Sim-Avionics\WX\radar.bin . Thanks for all the help - stay safe. C.

So after several sessions w/ Microsoft and getting the network set up correctly I tested and was able to write a file to the networked computer. I used PFPX and exported a .pln file as a test file. Also MS tested several .txt files and were able to write to the Simavioncis/WX folder as well. That told MS and me that I have now set up the network correctly. I am still getting an error 5 message so I am reloading the software for FSUIPC and Active Sky for P3Dv4 as we speak. Will report back. Chuck

I re-ran w/ administrator rights and there were no issues. I have a friend who is a network expert - he is going to look into this later this week. I'm pretty sure this is a windows issue - I'll report back when I get it figured out so others can see it. Really appreciated your help. Chuck

The folder does exist - I can see it from the host computer via the network. New error code w/ your suggestion - see below. Error 1314 looks like a known MS Windows code - I'll look in to that today. If you have suggestions it would be appreciated, but this is very much looking like a W10/permission issues: 44531 Error 1314 creating "c:\radar.bin": A required privilege is not held by the client.

FYI - same issue w/ a non-networked drive. Here's line 59250 from the log: 59250 Error 5 creating "C:\Sim-Avionics\WX": Access is denied.

[General] ASNwxRadarPath=\\Avionics\c\Sim-Avionics\WX UpdatedByVersion=6010 History=F9NVZHXCM50CVP99C93OM InitDelayDevicesToo=No PMDG737offsets=Auto PMDG747offsets=Auto PMDG777offsets=Auto Annotate=Yes UseSystemTime=No UseMidMouseBtn=Yes MouseWheelMove=No MouseWheelTrim=No MouseWheelTrimSpeed=1 JoystickTimeout=20 RestoreSimcWindows=No FixMachSpeedBug=No AutoScanDevices=Yes DisconnTrimForAP=No ZeroElevForAPAlt=No ThrottleSyncAll=No WhiteMessages=No ShowPMcontrols=No SpoilerIncrement=512 MagicBattery=No RudderSpikeRemoval=No ElevatorSpikeRemoval=No AileronSpikeRemoval=No ReversedElevatorTrim=No ClockSync=No ClockSyncMins=5 ClearWeatherDynamics=No TimeForSelect=4 LoadFlightMenu=No LoadPlanMenu=No PauseAfterCrash=No BrakeReleaseThreshold=75 SaveDataWithFlights=No ZapSound=firework ZapAirRange=1.50 ZapGroundRange=0.25 ZapCylinderAltDiff=0 ShortAircraftNameOk=Substring UseProfiles=Yes EnableMouseLook=No DelayedMouseLookZoom=No WideLuaGlobals=Yes AxesWrongRange=No TCASid=Flight TCASrange=40,3 AxisCalibration=No DirectAxesToCalibs=No ShowMultilineWindow=Yes SuppressSingleline=No SuppressMultilineFS=No AxisIntercepts=No DontResetAxes=No ThreadAffinityMask=x0 LuaAffinityMask=x0 InitDelay=0 GetNearestAirports=Yes LogOptionProtect=Yes TimeForLuaClosing=2 WeatherReadFactor=2 WeatherRewriteSeconds=1 TrafficStallTime=1 InitialStallTime=10 NormalStallTime=1 LuaRerunDelay=66 ComReadLoopTime=20 ControlsListBuild=34698 Console=No ConsoleWindowTopMost=No FSVersionUsed="Lockheed Martin® Prepar3D® v4",4.5.14.34698 SimConnectUsed=4.5.0.0 [Traffic Limiter] AirportPreference=50 PlannedAirportsPreference=50 GroundPreference=50 NearerPreference=50 TargetFrameRate=0 TrafficLimit=0 [JoyNames] AutoAssignLetters=No 0=AGRONN B737 Yoke V2.2 0.GUID={123C47A0-BA28-11EA-8001-444553540000} 1=FDS-FC1 1.GUID={C7FB6B10-9850-11EA-8003-444553540000} 2=MFG Crosswind V2 2.GUID={C7FAF5E0-9850-11EA-8001-444553540000} [JoystickCalibration] RudderBlendLowest=1 AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No FlapsSetControl=0 FlapDetents=No ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=66731 RudderTrimControl=66732 CowlFlaps1Control=66162 CowlFlaps2Control=66163 CowlFlaps3Control=66164 CowlFlaps4Control=66165 SteeringTillerControl=0 MaxSteerSpeed=60 [Axes] PollInterval=10 RangeRepeatRate=10 [Buttons] PollInterval=25 ButtonRepeat=20,10 [AutoSave] Interval=60 Files=10 SaveOnGround=No AutoSaveEnabled=No [GPSout] GPSoutEnabled=No Port=COM1 Speed=4800 Interval=2000 PosTo6Decimal=No SimModeIndicator=No Sentences= [GPSout2] GPSoutEnabled=No Port=<none set> Speed=4800 Interval=2000 PosTo6Decimal=No SimModeIndicator=No Sentences= [WideServer] WideFSenabled=Yes AdvertiseService=1 Port=8002 Port2=9002 [Sounds] Path=C:\Program Files\Lockheed Martin\Prepar3D v4\Sound\ Device1=Primary Sound Driver Device2=Speakers (Realtek High Definition Audio) Device3=Realtek Digital Output (Realtek High Definition Audio) Device4=Optoma 1080P (NVIDIA High Definition Audio) [AutoSaveFilesV4] Next=1

This can't be good: 138750 Error 5 creating "\\Avionics\c\Sim-Avionics\WX": Access is denied. I searched and found this from a previous post of yours - sounds like a permission issue..- "That doesn't stop FSUIPC working, it just means your OpusFSI server program won't load.. Error 5 is a Windows error meaning "Access Denied", so you've got some permissions problem with that folder or file."

********* FSUIPC6, Version 6.0.10 (19th July 2020) by Pete & John Dowson ********* Prepar3D.exe version = 4.5.14.34698 Running inside Prepar3D v4 Module base=7FFD5A4D0000 Windows 10 Pro 64 Bit reported as Build 19042, Release ID: 2009 (OS 10.0) Reading options from "C:\Users\Chuck\Documents\Prepar3D v4 Add-ons\FSUIPC6\FSUIPC6.ini" Checking the Registrations now ... User Name="Chuck Steinmetz" User Addr=XXXXXXXXX User WideFS Name="Chuck Steinmetz" User WideFS Addr=XXXXXXXXXXX FSUIPC6 Key is provided WideFS7 Key is provided 0 System time = 17/11/2020 17:39:59 16 FLT UNC path = "\\P3D-COMPUTER\Users\Chuck\Documents\Prepar3D v4 Files\" 16 Using DialogMode 47 FS UNC path = "\\P3D-COMPUTER\Lockheed Martin\Prepar3D v4\" 141 ---------------------- Joystick Device Scan ----------------------- 141 Product= MFG Crosswind V2 141 Manufacturer= MFG 141 Serial Number= MFG500002 141 Vendor=16D0, Product=0A38 (Version 33.1) 141 GUIDs returned for product: VID_16D0&PID_0A38: 141 GUID= {C7FAF5E0-9850-11EA-8001-444553540000} 141 Details: Btns=2, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R4096,U0,V0,X4096,Y4096,Z0 141 Product= FDS-FC1 141 Manufacturer= TEKWorx Limited 141 Serial Number= B83329 141 Vendor=1FD1, Product=03ED (Version 1.35) 141 GUIDs returned for product: VID_1FD1&PID_03ED: 141 GUID= {C7FB6B10-9850-11EA-8003-444553540000} 141 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0 172 Product= AGRONN B737 Yoke V2.2 188 Manufacturer= Microchip Technology Inc. 188 Vendor=04D8, Product=F30F (Version 0.2) 188 GUIDs returned for product: VID_04D8&PID_F30F: 188 GUID= {123C47A0-BA28-11EA-8001-444553540000} 188 Details: Btns=5, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X32767,Y32767,Z0 188 ------------------------------------------------------------------- 204 Device acquired for use: 204 Joystick ID = 2 (Registry okay) 204 2=MFG Crosswind V2 204 2.GUID={C7FAF5E0-9850-11EA-8001-444553540000} 204 Device acquired for use: 204 Joystick ID = 1 (Registry okay) 204 1=FDS-FC1 204 1.GUID={C7FB6B10-9850-11EA-8003-444553540000} 204 Device acquired for use: 219 Joystick ID = 0 (Registry okay) 219 0=AGRONN B737 Yoke V2.2 219 0.GUID={123C47A0-BA28-11EA-8001-444553540000} 219 ------------------------------------------------------------------- 250 Controllers are set to OFF 250 LogOptions=00000000 00000001 250 ------------------------------------------------------------------- 250 SimConnect_Open succeeded: waiting to check version okay 250 Opened separate AI Traffic client okay 6313 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.5.14.34698 (SimConnect: 4.5.0.0) 6313 Initialising SimConnect data requests now 6313 FSUIPC Menu entry added 6329 ... Using Prepar3D with Professional License 6360 \\P3D-COMPUTER\AppData\Local\Lockheed Martin\Prepar3D v4\Prepar3D_Default.fxml 6360 \\P3D-COMPUTER\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air 79469 \\P3D-COMPUTER\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\Sim-Avionics 737-800 Winglets\B737-800.air 79485 ### The user object is 'Boeing 737-800 Cyprus Airways' 79485 ### Mode is NORMAL 79844 ### Mode: PAUSE on 103625 Loading Complete ... 103641 ### Mode is NORMAL 104329 User Aircraft ID 2 supplied, now being used 104329 Aircraft loaded: running normally now ... 105016 System time = 17/11/2020 17:41:44, Simulator time = 14:00:01 (19:00Z) 105016 Aircraft="Boeing 737-800 Cyprus Airways" 111047 -------------------- Starting everything now ---------------------- 111047 Starting WideServer now ... 111094 ASN active function link set 111094 Ready for ActiveSky WX radar with additional data 112282 Advanced Weather Interface Enabled 138750 Error 5 creating "\\Avionics\c\Sim-Avionics\WX": Access is denied. 141282 Weather Mode now = Theme

Thank you - and I did w/o success. But I also upgraded Windows on both machines which is not ideal. Thanks!! Chuck

Using Windows 10, FSUIPC 6.0.10, P3D V4.5, and Active Sky for P3Dv4 (ASP4) in Beta. I have my FS and AVIONICS computers networked. My wx engine and FSUIPC are running on the FS computer. I run Simavionics software which is on the AVIONICS computer. This set up worked before w/ Active Sky Next and P3D V3.0, but two factors changed - I updated Windows10 and am now using Active Sky for P3Dv4 (ASP4). I located the fsuipc6.ini file in the Documents folder and added the path ASNwxRadarPath=\\[AVIONICS-PC]\etc under 'General'. I have not been able to get the radar.bin file to appear on the AVIONICS computer. I understand that Windows10 updates can make sharing and permissions a challenge - I'm in the middle of digging into that, but I wanted check here as well that the path I am using (ASNwxRadarPath=) is correct now that I am using Active Sky for P3Dv4 (ASP4). FSUIPC for Advanced Users dated 7/20 notes there is separate documentation for ASN and the ASN Wx Radar document is dated 5/9/14 - just confirming that the path noted on page 1 of this document is still correct w/ the newer version of AS. Pls let me know what more info you may need. Thank you.

Got some help from my friends at Jetline Systems. I had reinstalled V5 and reset Windows w/ no change. We reinstalled FSUIPC and Jetline suggested running 'Delete Generated Files' in the root folder of P3D - that seems to have cleared everything up. Back in action. Thank you all. Chuck

First of all - thank you for taking the time to post the photo - it was very helpful. It appears that the FDS-FC1 is causing the conflict. When I disconnect FDS-FC1 my issue w/ FSUIPC goes away. Per your suggestion I tested (see below) connecting to both Axis 1 (which is the X Axis) and then Axis 7 (which is the dial assignment and the recommended axis) - in both cases there is a conflict w/ FSUIPC. Also, in both cases I re-calibrated in Windows prior to the test. In going over my thread I note the the title is misleading. I explained in my comments, but calling this an issue of not 'recognizing an axis' was misleading. This issue must have more to do w/ a conflict as you note that prevents FSUIPC from seeing the movement of the addon or it is locking up. I'm stumped- any thoughts would be appreciated. Chuck

In this example below - when I push the yoke forward and backwards the In/Out values do not change - they both stay at '0'. I agree that it is showing an assignment (I probably used the wrong word in my depiction of what was going wrong) but trust me - they do not move up or down. It sounds to me that is counter intuitive as they have been assigned, but that's what is happening. I can close FSUIPC and reopen and they do move and I can set up the functions. Yep - not my best move, but that's what I did. Thank you for your time. At this point we can consider this issue closed. Chuck

I used FSUIPC5 for P3D4.5. Will do - thank you. I agree that the numbers don't matter until the assignment is made - I handle that in the Joystick Calibration tab. The way in which I have assigned (for example) the yoke is to move the yoke while on the Axis Assignment tab (the values move accordingly) so FSUIPC knows what I'm trying to assign then tick 'direct to FSUIPC' and assign the yoke to (in this case) the elevator - then I go back and do the same for the ailerons. My issue is when I move the yoke the values do not change - as if it isn't seeing the yoke move. Per your suggestion, I tried as follows: I opened FSUIPC6 - I ticked 'direct to FSUIPC' and assigned to the elevator. The yoke movement was not recognized (when I push the yoke back and forth the values did not change - they remain static). I closed FSUIPC and reopened. This time the the yoke axis movement was recognized by FSUIPC (values do change) but the elevator assignment was not there. I assigned the elevator - closed and reopened and the same elevator assignment was there. In the end, between the other suggestion of calibrating in Windows (which I would need to do each time) and/or if this is a potential fix as long as it stays consistent during flight I'm ok. Great point - but I cleaned up my drives when I installed P3DV5. Thank you very much for your time! Chuck

Peter - logs attached. I calibrated in Windows and now FSUIPC6 can see the assignment. But every time I close out of P3D and/or restart my computer FSUIPC6 loses the ability to see the yoke (for example). This may speak to an issue w/ my system and/or Windows - but I am not a computer expert. One note, I have used many versions of FSUIPC prior w/o this issue. I'm fine w/ calibrating in Windows each time it is needed as it's a simple process, my concern is if the FSUIPC6 assignment disconnects during a flight and I lose access to the yoke. To know for sure I will have to take it out for a spin :). What do you mean by 'ports'. I will search the forum or if you could expand it would be appreciated. If it's relevant I attached the joyscan log in my first post. Thank you all! Chuck "Edit" - I may be overthinking this - by 'port' do you mean a USB port? If so I'm still a bit confused on your comment. Thanks again. FSUIPC6.ini FSUIPC6.log

I am unable to get FSUIPC6 to recognize the axis movement of my yoke and pedals. When I open FSUIPC6 and go to the Axis Assignment tab, the values flicker between 16383 and 0 (which could mean nothing, but I'm including as I have not seen this behavior before). FSUIPC6 does not respond to movement for the yoke or pedals. I can assign a button from the yoke to FSUIPC6. I have uninstalled FSUIPC6 and reinstalled. I have swapped out the cables and don't see issues w/ the USB ports when I check out the Device Manager. Windows does see the devices and the axis movement as well (which I believe tells me the connection to the computer is OK). I have attached the install log and the Joyscan.csv in case that helps. Thank you. Chuck FSUIPC6.JoyScan.csv InstallFSUIPC6.log

I had to reload P3d V.4 from scratch - then I reset all of my FSUICP settings for my sim. I'm wondering - is there a way to save off all of the settings to load them up back up FSUIPC vs. having to capture the TQ, yoke, pedal, etc one by one. In the end, I don't mind going through the process, but it's time consuming. Just thinking out loud. Thanks. Chuck

First of all, thank you for the time on this. I checked w/ SA and my sense is the manual I was using is out of date. The detents are handled by the SA server. Either way, I learned something more about FSUIPC so that's a good thing. Thank you again, Chuck

Nothing on screen. My understanding is the the Sim Avionics 737 is based on the default airplane. Also, the SA manual pushes us to your manual. I'll reach out to SA as this problem is a first for me I also want to re calibrate so I have 'Rev' selected prior to setting the detentes. I wonder if that might not solve my retracting issue - then I will have one issue resolved. Thank you for the time - I'll report back as to what I find out. Chuck

Correct. I tested the REV option, but did not select prior to calibration - must have missed this note in the manual. I will re-calibrate tonight. I can confirm this to be correct. [JoystickCalibration] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No FlapsSetControl=0 FlapDetents=Yes ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=66731 RudderTrimControl=66732 CowlFlaps1Control=66162 CowlFlaps2Control=66163 CowlFlaps3Control=66164 CowlFlaps4Control=66165 SteeringTillerControl=0 MaxSteerSpeed=60 Aileron=-16384,-512,512,16257 SlopeAileron=-2 Elevator=-16384,-512,512,16045 Rudder=-16384,-512,512,16319 LeftBrake=-16384,0/16 SlopeLeftBrake=-2 RightBrake=-16384,0/16 SlopeRightBrake=-2 Throttle1=-16216,-512,512,16049 Throttle2=-16303,-512,512,16062 Spoilers=-16321,-12569,-12319,16380 Flaps=0,16380 FlapStarts=-16384,-13743,-9485,-5443,-1563,2641,7114,11102,16383 FlapEnds=-16114,-10725,-7437,-2587,1347,4904,9269,13365,16384

Working w/ FSUIPC 5.124. P3d V4.2. Sim avionics software/737 and throttle. I have set up my throttle and all works including the speed brake. I have also set up my flaps as outlined on page 41-43 of the manual. I have a 737-800 and there are total of 9 detentes. After setting up, the flaps will extend to the fist and second detente and also retract. But once I go to the third detente (5 degrees) they will no long retract. Also, if I stop on the third detente it will no longer extend. If I reload the plane the flaps will reset to fully retracted. Note - I can extend flaps to any detente if chosen initially, but after the 3rd detente they no longer retract. I have re calibrated the throttle in Devices page of Windows 7 and to be sure have double checked that I have all control settings removed in P3d. If it is of any help here is an image of FSUIPC showing the #3 detente settings. If there is other information I can post/send that would be of more help just let me know. Thank you. Chuck