smithju

Hi Peter, I hope you slept well. I have just e-mailed you my test results. Best Regards, Julian

Pete, I have completed some additional testing, If you wouldnt mind I would like to send the files to you for you to review, what is your e-mail address, i don't know how to add an attachment to this Forum. Regards, Julian[/url]

Peter, How doI use the logging function of EPICIO that you mentioned in your previous post. Julian.

Peter, I have found out by Starting FS Communicator first before FS2002 & the PM software the MCP dosent crash, go figure ! Regards, Julian

Jay, Thanks for the Info. Regards, Julian.

Hi Peter, :D Thanks for the quick response, yes I’m using the on-line Monitor facilities in FSUIPC, a very useful tool. I will send the observation to PM, I just wasn’t sure where to start. I will keep you updated. Regards, Julian :D

Hi Peter, I have made a strange observation while using FSUIPC 3.10 in my setup. Firstly some background information, I have the full PM Boeing software all latest versions, GC 402, MCP 369, CDU 340, WideFs 6.10, FSUIPC 3.10 (registered versions), Epic USB with Epicenter V55 and FS Communicator V1.0.57. I have been experiencing the following problem associated with the PM Offsets 4E2 & 5408 since loading FSUIPC 3.10, the offset size was set to 2 bytes in FS Communicator and had worked happily for many months. After loading FSUIPC V3.10 the MCP crashes with the following message “Runtime error 6 overflow”, FS has to be restarted to clear this problem. After reloading all my software and operating system the problem still occurred, I removed all of my FS Communicator programming and the problem disappeared, I then added the keys back one at a time until the failure occurred, it appeared that the following PM offsets 5408 & 4E2 were causing the problem. I used the FSUIPC Log function to monitor these offsets when FS Communicator is started, the MCP crashes only if the byte size for 5408 is set to 2 bytes, when set to 1 byte all works well, in addition I noticed the value of offset 5409 is the same a 5408 when 2 byte size is used in FS Communicator. I’m no expert but I find it strange that this problem should manifest itself after everything has been running for months, now even when using older versions of FSUIPC the problem occurs therefore I don’t know if FSUIPC I the cause or not, but I thought I would share my experience with you. I have also loaded every version of the MCP I have going back to ver 347 and FSUIPC back to 3.04. I hope this information is useful, keep up the great work you are doing for this hobby of ours. Best Wishes, a very satisfied customer.