Printable View
Hi Folks,
today I updated MCP from version 418 to 421A.
My CPflight MCP does work but not the radios. I tried version 420 with the same result. Unfortunatly I don't have vers. 419. Went back to 418 and everything is ok.
Does anybody made same experience ?
Thomas
Mine seems ok with 421a. But I also upgraded the MCP firmware ... might be the difference?
BTW - for those who do upgrade their firmware ... the mode selector on the CPFLIGHT transponder unit now interfaces directly to Squawkbox (SB) for online flying. So set it to TA/RA and you get 'normal' in SB, set to STANDBY = 'Standby' in SB. Very nice! :smile:
I just came from PM's web site and they still show most current B-MCP software to be 420. Where did you find 421a? I am running MCP420 with no problems noted.
Hi All,
I'm running B MCP ver 420 with CP Flight MCP ver 203, EFIS and MPEX board . I have been unable to get MY CP flight EFIS to operate since upgrading to SP1 and MCP ver 420. CP flight MCP starts up just fine however I cant get the EFIS to work at all! So I too am wondering what is going on.
James
Hi James,
it is the power up using PM Systems. try this...
1. Close the PM MCP software, wait until the CP hardware stops.
2. Disconnect the CP hardware powerunit and wait ten seconds.
3. Connect the powerunit again.
4. Restart PM MCP. Check all clients connected.
5. Check both EFIS units for proper function.
On my setup it brougt back all the EFIS functions. Any time the power to the MCT is interupted by using the PM System the problem reaccured.
Build setup:
PM GC 450, MCP 420 latest PM builds, no bete test...
regards from germany
Brian
Brian,
Thank you! That was it. I hope that CPFlight and PMsystems eventually are able to work together again. Have you already posted this to PM and CPFlight? Thanks Again!
Best Regards
James
I have the same problem by usung a cold and dark default flight in fs9 that starts with battery off.
My solution was to set a parameter in the mcp.ini called ignorebatteryoff=on (I'm at work but I'm almost 100% sure of the name) It leaves the cpflight mcp lighted all the time. But I rather have that then cutting the power everytime.
This issue happened to me yesterday for the first time. I'll make the ini change that sas550 suggests (thanks).
But a permanent fix is needed. Has anyone reported it to PM and CPflight?
After struggeling with other mcp issues I found that the ignoreBattery=on fix only works with 421a since there's been a change for this parameter after 420.
Anyone is getting a SERVER DISCONNECTED from SB3 after changing any VHF COMM frequency using MCP 421a and CPFLIGHT radios? This happens with me anytime a need to change the control frequency flying ONLINE....but by the way the TRANSPONDER works with SB3 now.
Yes, I mentioned the transponder feature a few posts earlier. Trouble is whenever we squawk normal it seems to reset the code and we have to put it in again.
Not having any issues with server disconnections when changing com frequencies.
So, my transponder resets too. If i set for example code 4322 and select STBY and then select to TA/RA it resets to code 1200 only in PM GC, but not with cpflight transponder visor, so to solve that i change one digit up or down and then it shows correct again in PM GC (EICAS). This will be solved soon as Enrico release the official update MCP 421, i think so ...
Anyone knows if is possible to make cpflight transponder IDENT button to work with SB3? :roll: