Jump to content
The simFlight Network Forums

Problems with WideFS6478test.zip


Recommended Posts

Hi Pete,

When running the PM MCP on my wideclient Pc it's starting up and closing again.

See my ini file:

[Config]

UseTCPIP=Yes

ServerIPAddr=192.168.1.3

WaitForNewData=500

NetworkTiming=5,1

Window=32000,32000,160,34

Visible=Yes

ButtonScanInterval=20

ClassInstance=0

PollInterval=2000

Port=8002

ResponseTime=18

TCPcoalesce=No

MaxSendQ=100

ApplicationDelay=2

Priority=3,1,2

OnMaxSendQ=Log

NewSendScanTime=50

; -----------------------------------------------

[user]

Log=ERRORS+

;actionKeys=no

;Keysend1=120,10

;Keysend2=RWoff

; ===============================================

;RUN1="C:\pfd\pfd.EXE"

;RUN2="C:\PMSOUNDS\PMSOUNDS.EXE"

AllowShutdown=apponly

runready1="C:\MCP\MCP.EXE"

runready2="C:\PMSOUNDS\PMSOUNDS.EXE"

runready3="C:\PMsystems\PMSystemsdemo.EXE"

CloseReady1=YES

CloseReady2=YES

CloseReady3=YES

[GPSout]

Port=COM1

Speed=4800

And my log file:

********* WideClient Log [version 6.478] Class=FS98MAIN *********

Date (dmy): 14/08/05, Time 16:57:51.406: Client name is LAPTOP2

172 Opening GPSout port COM1, speed=4800 -- FAILED!

172 Attempting to connect now

187 Connection made okay!

203 C:\MCP\MCP.EXE

266 C:\PMSOUNDS\PMSOUNDS.EXE

422 C:\PMsystems\PMSystemsdemo.EXE

1453 New Client Application: "pmSounds" (Id=992)

5406 New Client Application: "pmSystemsDemo" (Id=3392)

9328 New Client Application: "MCP" (Id=260)

What can cause this

Best regards

JanGeurtsen

Link to comment
Share on other sites

When running the PM MCP on my wideclient Pc it's starting up and closing again.

Sounds like it's license has expired? Otherwise you really need to check with PM support -- I cannot support their programs. Sorry.

In any case I would need more details. The Log you supplied shows nothing because it isn't finished - no errors are shown, nothing really useful is shown, except maybe this:

172 Opening GPSout port COM1, speed=4800 -- FAILED!

which is due to an error in the Beta wideClient -- if you don't add a GPSout section to the INI file it does it for you, but it shouldn't. I have a later version which fixes this, but in your case it shouldn't do any harm in any case as the COM1 port is evidently either already occupied or it doesn't exist.

Does your PM MCP directly connect to anything on a serial port?

Please always close down the relevant programs before showing a log. An unfinished log is not often useful.

Regards,

Pete

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • 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.