Jump to content
The simFlight Network Forums

ncngrr

Members
  • Content Count

    10
  • Joined

  • Last visited

Community Reputation

0 Neutral

About ncngrr

  • Rank
    Member

Profile Information

  • Gender
    Male
  • Location
    Colorado, USA
  1. I just deleted/downloaded/installed Mobiflight Connector again. Now my Arduino+Mobiflight recognizes the FSUIPC via WideClient. I added a switch and an LED to my Arduino/Mobiflight Connector breadboard, assigned the parking brake to the switch and the LED as a parking brake indicator (using the FSUIPC offsets). Now that WideFS is talking across the network to my laptop/Arduino, when I flip the switch, I see that the parking brake becomes set in P3D and the indicator LED illuminates. When I turn the switch off, the parking brake is released and the LED goes out. It's a simple first step, but an important one to building my flight sim cockpit! Thank you very much, Pete!
  2. Mobiflight Connector is an app + firmware that is applied over an Arduino Mega 2560 that communicates with FSUIPC and enables flight sim cockpit builders to connect hardware (buttons, LEDs, switches, etc.) to P3D, FSX, etc. With WideClient now "connected", then shall I conclude that everything WideFS is supposed to do is working correctly? Thanks!
  3. Thanks. I verified the WideFS.INI file is in the same folder as the WideFS.EXE file. I changed the workgroup name of the 2nd PC to match that of the P3Dv4 PC. Now when I initiate WideFS, it changed from "waiting for a connection" to "Connected". Now I seem to be unable to open the MobiFlight Connector application. Thanks.
  4. Thank you, Pete, for your assistance! WideServer file on the P3Dv4 PC (running Win 10/64-bit) ********* WideServer.DLL Log [version 7.074] ********* Blocksize guide = 8192 (double allowed) Date (dmy): 17/01/18, Time 15:52:38.401: Server name is DESKTOPFLIGHT1 15437 Initialising TCP/IP server 15437 Initialising UDP/IP server 16016 Broadcasting service every 1000 mSecs ------------------------------ WideClient.INI file on 2nd PC NOT running P3Dv4 (running Win 7/64-bit) ; PLEASE SEE WideFS documentation for parameter details ; ===================================================== [Config] ServerName=DESKTOPFLIGHT1 Protocol=TCP Port=8002 Window=43,44,886,589 Visible=Yes ; ----------------------------------------------- [User] Log=Errors+ ; =============================================== ------------------------------------- WideClient log file on 2nd PC NOT running P3Dv4 (running Win 7/64-bit) ********* WideClient Log [version 6.999z4] Class=FS98MAIN ********* Date (dmy): 17/01/18, Time 17:21:23.491: Client name is SCOTT-PC 469 Attempting to connect now 469 Trying to locate server: Need details from Server Broadcast 469 Failed to connect: waiting to try again 531 LUA: "C:\WideFS Client\Initial.LUA": not found 1469 Attempting to connect now 22485 Trying to locate server: Need details from Server Broadcast
  5. I'm sure I'm not the first one to ask this question, but when I searched the forum for WideFS connection issues, I didn't see anything. 1. I bought/downloaded/installed WideFS from SimMarket to extend my Arduino/Mobiflight I'm wanting to use on a separate PC 2. I installed/registerd both FSUIPC5 and WideFS on my P3Dv4 PC 3. I installed WideFS Client on the separate PC 4. I opened WideFS Client.ini and added the servername=<P3D PC name> and protocol=TCP to it. 5. When I initiate WideClient, a widow opens saying "WideClient FS98 Eliminator - Waiting for a conection" 6 I then open my Mobiflight .mcc file which recognizes the module but does not indicate any connection to FSUIPC I appear to be missing something. Help please. Thanks.
  6. Failsafe, Pete, Thanks for the inputs and thoughts. Being a generally impatient man and not waiting for the cognizant authority, I uninstalled FSX-SE again, deleted all FSX-related files/folders from Steam>SteamApps, deleted all FSX-related files/folders from the registry, and started over. FSUIPC activated fine. ORBX products are installed fine now too. I believe I'm back in business. Thanks much! By the way, I love FSUIPC! Wouldn't fly without it! Scott
  7. Had FSX-Classic (boxed version). Installed FSX-SE (both on computer simultaneously). Downloaded/Installed FSUIPC 4.939. Worked. Liked FSX-SE a lot. Uninstalled FSX-Classic because of some problems with ORBX installation. Uninstalled FSX-SE. Uninstalled FSUIPC. Installed FSX-SE. Initiated FSX-SE. Went flying. Fixed ORBX issues with the following advice from the ORBX Forum --------------------------- @ncngrr. Sometimes there is still a trace of FSX and if that is the case, by default, FSX-SE will be installed in "Co-exist" mode, ie so that it and FSX can be installed on the same PC. This is why the external folders are named FSX-SE instead of FSX. Use your Registry Editor to go to HKEY_CURRENT_USER\Software\Microsoft\Microsoft Games\Flight Simulator - Steam Edition where you will see a Registry Key named Co-existence. You will see that its value is 1. Right click on modify and change this to 0. You can then go to C:\ProgramData\Microsoft\ C:\Users\Your name\AppData\Roaming\Microsoft\ C:\Users\Your name\AppData\Local\Microsoft\ and in each case delete the FSX-SE folder. If you see an FSX folder, delete that also. Then restart FSX-SE and new folders named FSX will be created. Once you have done this, the file structure should match what the installers expect to find for FSX and work correctly. ----------------------------- Installed FSUIPC 4.939. Receive "Cannot edit the DLL.XML file to activate FSUIPC". Install log reads: --------- Installer for FSUIPC4.DLL version 4.939 Looking in registry for FSX install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Parameter"SetupPath" ... >>> OK! FOUND FSX! <<< ... SetupPath=D:\Steam\SteamApps\common\FSX\ Looking in registry for FSX-SE install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0 Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0 Parameter"AppPath" ... >>> OK! FOUND FSX-SE! <<< ... AppPath=D:\Steam\steamapps\common\FSX\ ************ BUT this is the same path as for FSX! Will only install for FSX-SE ************ Looking in registry for Prepar3D v1 install path: HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\LockheedMartin\Prepar3D Parameter"AppPath" ... NOT found! ... Looking in registry for Prepar3D v2 install path: HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v2 Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v2 Parameter"AppPath" ... NOT found! ... =========================================================== INSTALLATION FOR FSX-SE: SetupPath="D:\Steam\steamapps\common\FSX\" Checking version of the FSX-SE EXE: ... Version 10.0.62608.0 (Need at least 10.0.62607.0) Checking compatibility with installed SimConnect: Found SimConnect build 60905 (Original) Found SimConnect build 62608 (Steam) Found SimConnect build 61242 (SP1 May07) Checking if there's already a version of FSUIPC4 installed in: D:\Steam\steamapps\common\FSX\Modules\FSUIPC4.DLL ... Version 4.939 found. FSX-SE Modules folder already exists. Okay -- installed FSUIPC4 into "D:\Steam\steamapps\common\FSX\Modules\FSUIPC4.DLL" Looking for the current user's Application Data path: ... found as "C:\Users\FSXDesktop\AppData\Roaming" Now finding \Microsoft\FSX-SE\FSX_SE.CFG for all users, including this one Looking in "C:\Users\All Users\AppData\Roaming" ... No FSX_SE.CFG there Looking in "C:\Users\Default\AppData\Roaming" ... No FSX_SE.CFG there Looking in "C:\Users\Default User\AppData\Roaming" ... No FSX_SE.CFG there Looking in "C:\Users\FSXDesktop\AppData\Roaming" ... No FSX_SE.CFG there Looking in "C:\Users\Public\AppData\Roaming" ... No FSX_SE.CFG there Cannot edit the DLL.XML file to activate FSUIPC. "Modules\FSUIPC Documents" folder already exists. Now installing additional files into the "Modules\FSUIPC Documents" folder: Installed "FSUIPC4 User Guide.pdf" okay Installed "FSUIPC4 for Advanced Users.pdf" okay Installed "FSUIPC4 History.pdf" okay Installed "List of FSX and P3D controls.pdf" okay Installed "FSUIPC Lua Library.pdf" okay Installed "FSUIPC Lua Plug-Ins.pdf" okay Installed "Lua License.pdf" okay Installed "Lua Plugins for VRInsight Devices.pdf" okay Installed "LuaFileSystem.pdf" okay Installed "Example LUA plugins.zip" okay Installed "ASN WX Radar facilities in FSUIPC4.pdf" okay Installed "Offset Mapping for PMDG 737NGX.pdf" okay Installed "FSUIPC4 Offsets Status.pdf" okay Installed "Profiles in Separate Files.pdf" okay =========================================================== All installer tasks completed. *************** End of Install Log *************** --------------- Any assistance would be greatly appreciated. Thanks. Scott
  8. I decided it was time for me to set up some profiles within FSUIPC to ensure my "joysticks" wouldn't conflict with one another. I created a C172 profile and a Piper Cub profile. In the Piper Cub profile, I told FSUIPC to ignore all of the yoke, throttle quadrant, and TPM axes inputs and then programmed all of the Saitek X52 joystick axes. Likewise, in the C172 profile, I told FSUIPC to ignore all of the throttle quadrant, and X52 inputs and programmed the TPM and yoke axes. Sounds reasonable. When I fired up the C172, everything seemed to work okay. Then, in the Piper Cub, the elevator trim seemed to have a mind of its own (remember, the Piper Cub has no autopilot to explain this), spinning without any input from me. When I was able to seemingly affect some trim change, the Cub's trim rotated "nose down" fashion regardless of the direction I moved the Saitek trim wheel. I changed it in FSUIPC to both normal and reverse modes, but that didn't see to have any impact. At one point in time, I selected "Enable Controllers" from within FSX and when I returned to Free Flight, the "views" within FSX automatically began to cycle at a rather high rate of speed. I enabled FSX control over the controllers in an attempt to regain control of the trim wheel, leaving the remainder of the controls to FSUIPC. When I disabled FSC control over the controllers, the auto-view-cycling ceased. Obviously, something in FSX > Settings > Controls is amiss. Any thoughts? Thanks. Scott Colorado Springs
×
×
  • 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.