Jump to content
The simFlight Network Forums

oldJ3pilot

Members
  • Content Count

    79
  • Joined

  • Last visited

Everything posted by oldJ3pilot

  1. It would be nice if I could finally get FSUIPC4 to open Serial FP/M-Panel via the pair established by VSPE. I have followed the instructions precisely: Created a pair--- COM8<=>COM5 after verifying that SerialFP2 is using COM8 (although I believe the documentation says it doesn't matter if it is set to AUTO) Provided the additional info to the VSPE Shortcut--- "C:\Program Files (x86)\Eterlogic.com\Virtual Serial Ports Emulator\VSPEmulator.exe" -minimize -hide_splash C:\ComPair_56.vspe...I have verified the path (more on that later) Added Appropriate lines to FSUIPC4.ini--- [VRInsight] 1=COM8,COM5 [Programs] Run1=READY,close,C:\Program Files(x86)\SerialFP2\SerialFP2.exe To test the for SerialFP2 I programmed a shortcut on my G-15 Keyboard,disabled the two .ini lines in FSUIPC4, launched FSX, and loaded the M-Panel immediately from the shortcut. "C:\Program Files (x86)\SerialFP2\SerialFP2.exe" This is the exact same SC that is in FSUIPC4.ini **The loading of M-Panel always begins with "HOST CONNECTED". After that the process is scrolled across the LED. After enabling the .ini lines in FSUIP, Launch FSX, gets a couple of PC beeps and then the Dialogue box pops up to search the com ports for SerialFP2 (it is never found) Pete: Searched and re-searched..AUTO and each port individually The COM Pair is good and is activating with "ok" I have everything possible set to "Run As Administrator" as for ERROR 267: ERROR 267 FSUIPC cannot open C:\Program Files(x86)\SerialFP2\SerialFP2.exe This is what is so maddening about this problem. EVERYTHING is exactly where the path/s say. The same path works if I disable the FSIUCP4.ini lines. In fact: if I leave the 1=COM6<=>COM5 line the M-Panel LED displays "HOST CONNECTED" but will go no further. I am not asking that you support SerialFP2 or VSPE but to help me find out why FSUIPC4 is unable to execute a program. As the log below shows, Error 267 is keeping FSUIPC4 from doing what it should be able to do. I realize that you have lots of folks looking for help. I also realize that sometimes software can hit a random glitch and fail. If that is the case here, it is something I will just work around. FSUIPC4 is too good an APP to let one problem sour it...and not a serious problem at that. I just hate to give up on ANY problem :? Regards Neal Howard DebugStatus=15 110 System time = 26/09/2010 15:52:29 110 FLT UNC path = "\\NEALSFAST-PC\Documents\Flight Simulator X Files\" 110 FS UNC path = "C:\FSX\" 359 LogOptions=00000000 00000051 359 SimConnect_Open succeeded: waiting to check version okay 437 VRI port 1 "COM8" opened 437 VRI driver port 1 "COM5" also opened 1592 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) 1592 Initialising SimConnect data requests now 1592 FSUIPC Menu entry added 1638 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y 1638 \\NEALSFAST-PC\Documents\Flight Simulator X Files\Cessna-Danville.FLT 1638 C:\FSX\SimObjects\Airplanes\C172\Cessna172SP.AIR 3011 Weather Mode now = Custom 15881 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N 15928 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N 15959 FSUIPC couldn't run: "C:\Program Files(x86)\SerialFP2\SerialFP2.exe" [Error=267]
  2. I might as well give up! I can't even post what I actually did!. The Com pair I created is COM5<=>COM6. The FSUIPC4.ini file reflects the correct , . Frankly, I have been at this so long that my errors are cropping up exponentially....time to give it a rest and come back later. Sorry Pete..hate to waste your time. :oops:
  3. After a complete reinstall of FSX and all my add-ons and hardware I cannot get the VSPE to work with FSUIP to get the MRInsight M-Panel loaded. The panel will load via the start menu or shortcut ok so the problem isn't there. After checking and rechecking my shortcut and .ini entries without finding anything I'm hoping to get the fix here. Prior to the reinstall, and after Pete corrected my syntax in the VSPE shortcut it worked perfectly. Current settings: VPSE Pair......COM5 <===> COM6 (Also tried COM1 <===> COM2 ) FSUIPC4.ini....... [VRInsight] 1=COM5,COM6 [Programs] Run1=READY,CLOSE,C:\Program Files(x86)\SerialFP2\SerialFP2.exe Note that the new driver software uses Program Files(x86) as the main directory instead of VRInsight VSPE shortcut..... "C:\Program Files (x86)\Eterlogic.com\Virtual Serial Ports Emulator\VSPEmulator.exe" -minimize -hide_splash C:\ComPair_56.vspe I have double-checked spelling, and directory trees and cannot find any errors FSUIPC Log.... FSUIPC4 Key is provided WIDEFS7 not user registered, or expired Running inside FSX on Windows 7 (using SimConnect Acc/SP2 Oct07) Module base=61000000 Wind smoothing fix is fully installed DebugStatus=15 78 System time = 24/09/2010 10:58:47 78 FLT UNC path = "\\NEALSFAST-PC\Documents\Flight Simulator X Files\" 78 FS UNC path = "C:\FSX\" 312 LogOptions=00000000 00000051 312 SimConnect_Open succeeded: waiting to check version okay 1046 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N 1514 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) 1514 Initialising SimConnect data requests now 1514 FSUIPC Menu entry added 1560 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y 1560 \\NEALSFAST-PC\Documents\Flight Simulator X Files\Cessna-Danville.FLT 1560 C:\FSX\SimObjects\Airplanes\C172\Cessna172SP.AIR 13807 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N 13916 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N 13931 VRI port 1 "COM5" opened 13931 VRI driver port 1 "COM6" also opened 13931 VRI port 1 "COM5" failed to open 13994 VRI port 1 "COM5" failed to open 14056 VRI port 1 "COM5" failed to open 14119 VRI port 1 "COM5" failed to open 14181 VRI port 1 "COM5" failed to open 14243 VRI port 1 "COM5" failed to open 14306 VRI port 1 "COM5" failed to open 14368 VRI port 1 "COM5" failed to open 14431 VRI port 1 "COM5" failed to open 14493 VRI port 1 "COM5" failed to open 14555 VRI port 1 "COM5" failed to open 14618 VRI port 1 "COM5" failed to open 14680 VRI port 1 "COM5" failed to open 14743 VRI port 1 "COM5" failed to open 14805 VRI port 1 "COM5" failed to open 14867 VRI port 1 "COM5" failed to open 14930 VRI port 1 "COM5" failed to open 14992 VRI port 1 "COM5" failed to open 15055 VRI port 1 "COM5" failed to open 15117 VRI port 1 "COM5" failed to open 15179 VRI port 1 "COM5" failed to open 15242 VRI port 1 "COM5" failed to open MORE OF THE SAME...failed to open lines follow Help me please Master
  4. Last Try after correcting the COM path: ERROR 267 FSUIPC cannot open C:\Program Files(x86)\SerialFP2\SerialFP2.exe
  5. YES, I thought long and hard. After trying to follow your documentation my last attempts probably look random. According to Device Manager, the SerialFP2 is using COM8. My first setting was 1=COM8,COM5...didn't work. Tried 1=COM8,COM6....didn't work. Ditto when I created a pair COM1<===>COM2 My printout of these documents is dog-eared and limp from repeated reference to them. OK Once more unto the breach, dear friends, once more; Or close the COM up with our SERIALFP2 Pete Your responses seem to imply that I am either not too bright or too lazy to do my homework. It is true that I am no longer a fiery youth but I have an earned doctorate in mathematics, taught in a university for 25 years and prior to that was a USAF combat crew navigator. Believe me, I have done a lot of studying and would much rather learn something than request help.
  6. BLESS YOU PETE :!: -May you never need a parachute. :D
  7. I have followed the instructions precisely in Appendix 3 of the manual. Everything works great until step 7>I opened "Properties" of the VSPE shortcut and added the lines as described in "Target": "C:\Program Files (x86)\Eterlogic.com\Virtual Serial Ports Emulator\VSPEmulator.exe -minimize-hide_splash C:\ComPair_1.vspe" It looks like you've missed a space in front of "-hide_splash". How did you "place it on the C drive" if you can't save it? I don't understand, sorry. Saving and placing are the same thing, aren't they? It looks like you are using Vista or Win7 64-bit. I suspect Windows stops you writing things to the C:| root driver, unless you run "as administrator" (a right-click option). Regards Pete
  8. Argggh! I did it again...I did save the file to the C drive without any problem. It is the Shortcut that will not save. It still says the path is invalid. I added the space before -hide and everything was already set to "Run as Admin". Still won't work. Yep, it is Win 7 64 bit, UAC is "OFF". Here it is the shortcut now: C:\Program Files (x86)\Eterlogic.com\Virtual Serial Ports Emulator\VSPEmulator.exe -minimize -hide_splash C:\ComPair_1.vspe" The ComPair_1 file is on the C drive. I put a copy of it on another drive but the result is the same :( "C:\Program Files (x86)\Eterlogic.com\Virtual Serial Ports Emulator\VSPEmulator.exe -minimize -hide_splash D:\ComPair_1.vspe"
  9. I don't have a clue about how to "put it all together", even after reading the fsuipc manual several times. Can someone point me in the right direction? I have a registered version of fsuipc and the 64-bit version of VSPE and am trying to get the VRInsight M-Panel to work with the PMDG Jetstream 41. I originally hoped to get it done with LUA scripts but wasn't successful at that either (Thank goodness for guenseli's "Cold and Dark") Thanks for any help that can be shared with a guy who is definitely in over his head here. Neal Howard an old, old flyboy
  10. Excuse me please, I was not clear Pete. I certainly don't mean for anyone to repeat the same info that I already am struggling with. The M-Panel is working perfectly with every airplane except the JS-41 where it will only operate gear, flaps, and radio freqs. At first I thought that a LUA script would fix it but after reading the VRINSIGHT section of the fsuipc manual I purchased the VSPE which seems the ideal software for interfacing. I will re-read the manual again and start experimenting with settings....at least it wont wreck anything. Sorry again for wasting your time. I'm not as precise as I once was.
  11. oldJ3pilot

    PMDG J41 commands (upd 5th Aug 2010)

    Is there a site for downloading these updated versions? I'm not sure exactly which files I should copy from the forum post. I do not want to risk ruining the great cold and dark file that is presently in my sim. Thanks Neal Howard
  12. oldJ3pilot

    Need Advice about VRINSIGHT panels

    Thanks for the input folks. After some serious measuring I decided that the combo is just a bit to big for my "cockpit". Putting it on top of the Saitek yoke was the only option. With three monitors and all that other junk on the desktop I opted for the M-Panel. It, along with the G15 keyboard and FSUIP options should be more than satisfactory. Oh, and there is still the Saitek Multi panel attached to the yoke (dunno whether it will stay or find another home) Happy flying all.
  13. Most of my flying is done in the RealAir Beechcraft Duke, Flight 1 Pilatus 12, the PDMG Jetstream 41, and (just learning) the Embraer Regional Jets. I already have a registered version of FSUIPC in FSX. Both the VRinsight M-Panel and Combo look good. I lean toward spending the extra for the Combo but would like some advice from some of you more experienced simmers. Am I flying the kind of aircraft that will benefit from them? Most of my sim flights are IFR, following proper procedures via Radar Contact 4, and with a little help from IYP' s Michelle. The JS 41 avionics have almost brought me to my knees so I'm looking for help. No telling how tough the Regional jets will be to learn. My real flying experience, both USAF and Civilian, had none of these new-fangled gadgets. Thanks in advance Neal Howard
×

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.