PFC and MCP connection issues

[HBE66]

hi pete :grin:

ive now got 4.645 installed (thaught ill start a new thread for this)

ive updated the ini file with the following, according to the vri pdf:

[VRInsight]

1=COM10, COM50

[VRInsight.FMER]

Lua=JS41_VRIH.lua

DriverReads=YES

DriverWrites=YES

when i now start fsx, the PFC control connection check starts up, and sais:

version of fsuipc module: FSUIPC okay. all options available 4.645

com serial port port connection: none

so i click, change port and COM4 shows up in the dropdown

soo i select COM4 and click retry

it takes a while and then i get "COM4 open okay"

but bellow everything shows a red X

next to "mode control panel (MCP) connection:" i get "No expected result received!"

which is the panel im using

what can this be?

PS: if i change the com10 in the ini to com4, it will show com10 in the dropdown

and i tried loging some com-port action if that might be any help

PFCFSX.log

what i found kind of strange about the fsuipc.log was:

1591 VRI port 1 "COM10" opened

1591 VRI driver port 1 "COM50" failed to open

i presume it is correct if i dont run serialFP2 nor portemulator

[Pete Dowson]

ive updated the ini file with the following, according to the vri pdf:

[VRInsight]

1=COM10, COM50

[VRInsight.FMER]

Lua=JS41_VRIH.lua

DriverReads=YES

DriverWrites=YES

Is this a newly connected VRInsight MCP COmbi you are wanting to use FSUIPC with?

when i now start fsx, the PFC control connection check starts up

Which PFC devices do you have?

and sais:

version of fsuipc module: FSUIPC okay. all options available 4.645

com serial port port connection: none

What COM device did you use to have the PFC device connected ot?

it takes a while and then i get "COM4 open okay"

Any COM port which is available will open. That doesn't mean the right device is there.

but bellow everything shows a red X

next to "mode control panel (MCP) connection:" i get "No expected result received!"

which is the panel im using

Er .. you have a PFC MCP as well as a VRInsight version? Why bother with the VRi one when you hsave the far superior PFC one costing 10 times as much? I don't understand.

and i tried loging some com-port action if that might be any help

PFCFSX.log

All that shows is no PFC COM device on that port.

what i found kind of strange about the fsuipc.log was:

1591 VRI port 1 "COM10" opened

1591 VRI driver port 1 "COM50" failed to open

I'm not that surprised. Why are you using COM50? What happened to COM11 through to COM49? Is it correctly created in your VSPE?

i presume it is correct if i dont run serialFP2 nor portemulator

Pardon? If you don't want to use SerialFP2 you must program everything in the VRI device(s) yourself.

But please answer the other questions first. Why do you even want ot use a VRI MCP when you have the splendid PFC one?

Pete

[HBE66]

lol, it seems i have understood something wrong :grin:

Is this a newly connected VRInsight MCP COmbi you are wanting to use FSUIPC with?

new, but not that new

ive used it on the prior fsuipc version 4.60a

Which PFC devices do you have?

i assume i dont have any PFC device :blink:

its only the vri mcp panel im trying to connect

then i also have some saitek stuff, but that basically works

What COM device did you use to have the PFC device connected ot?

i think this question should be cleared =)

serialfp2 starts with com4 and if thats used its com10

I'm not that surprised. Why are you using COM50? What happened to COM11 through to COM49? Is it correctly created in your VSPE?

does that matter?

i basically thaught ill leave some space between one range and the other

having the actual hardware link bellow 50 and the virtual ports above

Pardon? If you don't want to use SerialFP2 you must program everything in the VRI device(s) yourself.

i basically closed down serialfp2 and vpse because the pfc check wouldnt list any com port

once those 2 applications wherent running, i could refresh and i had a port to choose from

probably ill need to disable the pfc check somehow and carry on as i did with 4.60a

thank you pete

[Pete Dowson]

i assume i dont have any PFC device :blink:

its only the vri mcp panel im trying to connect

But you've installed the PFC driver, PFCFSX.DLL, into the FS Modules folder. Nothing I provide will do that, It's a purely manual process by the user (i.e. you).

i think this question should be cleared =)

serialfp2 starts with com4 and if thats used its com10

Sorry, I don't follow.

i basically thaught ill leave some space between one range and the other

having the actual hardware link bellow 50 and the virtual ports above

If things accept COM ports with such large numbers, I suppose you can do that. You need to be careful though.

i basically closed down serialfp2 and vpse because the pfc check wouldnt list any com port

But the PFC check is done by the PFC driver which is looking for PFC devices.

probably ill need to disable the pfc check somehow and carry on as i did with 4.60a

Perhaps you should simply delete PFCFSX.DLL and its INI and LOG files from your FSX Modules folder. How on Earth did you come to install it in any case?

Pete

[HBE66]

haha, alright im deleting them =)

its probably just me, i saw some additional stuff so i go and install it aswell :grin:

thank you and sorry pete ;)