Hey guys so I am doing a bit of troubleshooting and there are a couple of things that still stump me and am turning here for help.
Attached below are pictures of what I am describing.
1. Running the latest builds of all PM Software and an AIRAC from Navigraph that is maybe 3 cycles old you can see the last leg of the ILS from GATTO to the runway is missing. This happens at all airports, there is a DISCON in the FMC and I cannot figure out why it never connects to the runway. Tried multiple CDU versions and AIRAC cycles that did nothing.
2. Notice the font it seems like it needs to be anti-aliased and is not. It is very Jaggy and I would like to smoothen it up to look better any idea how. Disregard the 777 style Flap indicator I am trying to remove that but all options for "Show flap Indicator" is unchecked and that little bugger is still there. I am waiting to hear back from PM.
3. Notice the ND, see how the NAVAID identifiers seem in a darker black boxed area, and the entire arc ND area seems to be blacker and what appears to be a boarder around the whole display but there is in fact no boarder selected it just shows that way and I don't know why.
4. Lastly the AP / AT P/RST buttons do work. I can click the AP off after disconnecting, and it goes dark but the AT will stay lit and change from flashing to steady and remain on. I can not switch it off at all unless I reactivate AT. Those are controlled by an FDS card I believe as it is an FDS product.
Sorry for the list of questions here guys but I do appreciate any feedback. I have these tickets created at PM but the response time there is slow and I would like to hear from the community here.
Angelo,
Please post your .ini files for the GC and the CDU, they will be listed as GC.ini and CDU.ini in the PM file directories.
John
I will do that when I get back to the simulator.
Angelo. Have you tried the bitmap smoothing button in the menu? To solve your Bitmap smoothing ssues?
Trevor, yeah I have tried that but there is no noticeable difference.
Quote from: blueskydriver on March 16, 2016, 03:01:02 PM
Angelo,
Please post your .ini files for the GC and the CDU, they will be listed as GC.ini and CDU.ini in the PM file directories.
John
Here are the ini's for the Capt, FO, and Upper Eicas displays. Note I changed their names to attach here, in sim they are all in respective folders titled pfd.ini
Hi Angelo,
I haven't had the chance to research your issues yet, but I plan to do it tonight or tomorrow...
John
Hi.
I have read again your issues. I used to use PM until about two years or so ago before I switched to Sim-Avionics, and then most recently to ProSim.
With regards to point number one. I had similar issues with the AIRAC Cycle 1602, waypoints were missing in the approaches, case in point, RNP Approach to Toncontin ( MHTG ), ILS's at KMIA and a few others. I went to the previous one that worked and the problem solved. The latest one, 1603 is back to normal, at least with ProSim, so try grabbing that one and install it. Make sure both CDU and PFD are updated as well as Whazzup if you use it.
In reference to the display issues, there are settings that can be operated from the PFD screen, it seems you tried that to no avail. Now, sometimes, for some obscure reason, you get corrupted files. All the signs that you mention suggest to me that this may have happened. PM uses OpenGL and Windows has to play nice with it. I recall that in more than one occasion I had to use the original installer as if it was a fresh installation and then do the upgrade, it was a pain but it worked. The INI files should be backed up, and then, just copy them on top of the old ones. If you did not modify your INI files, and they worked fine before, they should continue to do so. PM does nor fiddle with the registry, so that is one less headache :).
The A/P reset issue ( I think I gave you a knee jerk recommendation ) to recycle the FD probably wouldn't do a thing :huh:, it may be related to the same issue.
Last but not least, consideration should be given to the possibility that some Windows Updates that are been installed automatically ( Win 7, 8 to 10 anyone ? ), could also be a factor. I am not sure about this, it is just a thought. Stories are circling in the Internet about some programs misbehaving or not working at all after some updates have been installed. The question is which ones. That is beyond the scope of my expertise but I probably would consider it the last option.
:2cw:
Thanks so much guys for the feedback. Jfuenmayor are you saying I should uninstall PM glass cockpit via control panel? Reinstall using our base installer then reapply the latest build release? After that copy back my backed up .ini's?
The AT light was the one that wouldn't extinguish and I would rather avoid having to reset guidance systems, FD and AT on / off just to trick the light. How does one normally see how the light is coded and reads and interprets the commands sent to it by the software?
I actually found out that the 6-pack annunciations, AP AT FMC lights, and Autobrakes are controlled by a program called TSR Boeing 737 NG. If anyone is familiar with that chime in, it is running of a networked PC.
That is right, reinstall the suite with the original installer. I would do it for PmSystems, PFD, CDU and MCP, all from scratch and then the INI files. Remember that the executables are placed in the same folder. If you leave the other files intact it should work, just back them up in case something goes wrong.
From my recollection, PM controls all the systems through their PmSystems software, that is why it should be used with their flight model. Any other model requires deactivation of the panels ( PMDG comes to mind ).
It is my understanding also, that the MCP software controls the A/P and A/T Disconnect functions. The lights in the main panel should blink when any of these is executed, and pressing them should extinguish those lights.The A/P light blinks until the aural warning ceases and then extinguishes itself automatically if you do not press it before . This should be controlled by the AFDS. This feature ( the AFDS ) had not been modeled by PmSystems up until when I was using it. Maybe that software you mention fills the gap.
PmSystems should control the Sixpack annunciators , Autobrake , Recall function as well as the full OHD panel. You should be able to visualized all on the Overhead display of PmSystems. The offsets and their state can also be seen as you move your mouse cursor over the different buttons and lights etc in the OVH panel.
In summary, I would suggest re installing and utilizing AIRAC cycle 1603. Good luck.
joaquin.
Quote from: blueskydriver on March 24, 2016, 09:13:16 AM
Hi Angelo,
I haven't had the chance to research your issues yet, but I plan to do it tonight or tomorrow...
John
Did you get a chance to look at those yet?
Hi Angelo,
I am sorry that I haven't check this yet. Last night I was out in my sim room trying to fix the entire network that is down, even though I went out there to fire the sim up and look at these PM settings. My plan was too have done this sooner for you, but as you likely know the hangar/shed took precedence over everything this past week or so.
The good news is I am going too be inside the next couple of days because of rain days and the fact that the hangar is finished, I will have more time. Therefore, my first priority for today is to get the network going, and then I will look at these settings for you...I promise!
Lastly, would you like call me on my home phone or maybe Skype or Teamspeak? If so, send me a PM and we can exchange info...
John
Quote from: blueskydriver on March 30, 2016, 07:20:24 AM
Hi Angelo,
I am sorry that I haven't check this yet. Last night I was out in my sim room trying to fix the entire network that is down, even though I went out there to fire the sim up and look at these PM settings. My plan was too have done this sooner for you, but as you likely know the hangar/shed took precedence over everything this past week or so.
The good news is I am going too be inside the next couple of days because of rain days and the fact that the hangar is finished, I will have more time. Therefore, my first priority for today is to get the network going, and then I will look at these settings for you...I promise!
Lastly, would you like call me on my home phone or maybe Skype or Teamspeak? If so, send me a PM and we can exchange info...
John
Sent you a PM!
Why is it whenever you really want too help someone, you wind up needing more help for yourself... I was sitting at home 3 hours ago and got intense chest pain, so I called the hospital and they said come into the ER. So, I called Karen at work and she came home too take me in, and now here I sit awaiting lab work and X-Ray results. Years ago I had my left lung collapse and it has not been the same since...
Here is me from 2 mins ago:
I will let you know what happens...
John
I attached a pic of Karen waiting with me.
Oh wow! Well she is smiling so thats a good sing lol! Hey no worries at all you get yourself better! Don't worry about me right now, you get back to a 100% first.
Okay, good news! Karen must've known beforehand, hence her smiles... Turns out my ticker is fine and my airbags are fine as well, but the plurasey is getting worse. It seems I am getting inflammation from the old lung collapse scar tissue, and that is what causes the intense pain. I got referred too go see a specialist for this from the ER, so looks like something can be done.
Currently, I am home now and plan to be up a little bit longer. Likely, will not get too the PM stuff, but tomorrow is another rain day, so I should be inside and plan to fire my sim up too check your settings with mine.
John
Angelo,
Quick questions, why are you using version 513 and not 512? 513 is more like the next version coming out, but in beta and not final stable release, plus there are different letters representing the beta step it is on, like 513d or 513e. Thus, which one of the 513's for all your PM sections (GC, CDU, PMSystems and so on) are you using currently?
You might consider changing to the 512 versions... I am not on 512 yet, but I plan to update; however, I will not update to 513. I never update to a beta...
John
I downloaded MCP 513e, I installed it because I received a new CP Flight MCP, other one was 5 years old and figured since I updated all the other builds, I may as well handle the MCP. I can revert no problem. This day is dragging, I want to get to the sim already. I already notated all the things to run by you so I can keep everything sorted in my head.
Hi Angelo,
I understand it can be very frustrating and I just want too make sure about my setup matching yours, as I am about to update my entire PM setup to match yours. I promised I would help, but part of it is for me to do it right.
In doing so, I read your .txt files as version 513, so if you're using these updated versions that could be causing some of the issues. Would you please tell me what version you upgrading from that were from 5 years ago?
Otherwise, hang in there...
John
It was the CP Flight MCP Pro, it had plastic knobs and dinky FD switches, lighting wasn't as good. The version that ships now is much much nicer. All metal knobs, heavy tactile FD switches, much improved back lighting and button lighting. If the ini says 513, then that is whats in there then. I may have downloaded 513e to read the change log and decided it wasn't beneficial to install based on what it was showing in the log.
EDIT: Im sorry you meant what MCP ver.
The last one that we used before this update was 509.
Tell you what I will wait until you call me at 4:45pm CST too ask you anymore questions, that way I don't make it confusing for you...
John
Angelo,
Hey, I am still updating the PM and the two computers with PFD/ND are locking and PMSystems is not working with InterfaceIT... OMG, talk about problems, now I am having them. I have to connect to the two computers using a keyboard and mouse, as I usually use TightVNC to access them, but that's now locked out...
If you call, I might not be ready just yet, as the PFD/ND is where questions lie.
John
Hi Angelo,
Here is a link for you to take care of the fsplans issue...
https://rhubbarb.wordpress.com/2010/12/09/share-dir-diff-name-win7/
John
Hey Everyone,
Just got done Skpe'ing with Angelo and after a good few hours, we found out some interesting things, as well as resolved some of his PM issues. The great thing he is very knowledgeable and very nice too converse with about the fun "features" of PM.
We all should look forward to hearing more from him, as he will be a great asset to the Cockpit Builders community...
John
Thanks so much John for the kind words! But more so a thank you is in order to you for offering such a helping hand over all this! I learned a lot to say the least. I will be back at today after 5pm so I guess we will reconvene then.
Angelo,
Guess what? I found the right setting to use for the AP disconnect on the yoke. The question is do you have two separate buttons (one for each yoke), you don't need two, but it would be even better if you did.
Here is what you do:
1. Go to FSUIPC and select Buttons Tab, and then press your Capt Yoke AP Button.
2. Once shown in the FSUIPC dialog, use the drop down for the "when the button is pressed" and select PM MCP AP 1L (means left).
3. Do not use any parameters or use the "when button is released" drop down.
4. Exit FSUIPC, be in flight at whatever altitude (say 10000ft) set the ALT Hold, set the SPD at 250kts, set the HDG to whatever you like, and press left CMD, make sure the AP Disconnect Bar is up.
5. Now press your Yoke AP Disconnect Button and you will see that the left CMD will turn off and disconnect the AP.
6. Next, press the left CMD and it will turn the AP back on like you wanted, and just like you have been searching for since 2013 (I saw your post on Pete Dowson's forum).
7. Try it again, the Yoke AP Disconnect Button will work again and again, no MCP AP Disconnect Bar cycling.
8. Here is the really cool part, look at step 5 above...it turns it off right, well instead of reaching up and turning the CMD button back on, you just press the Yoke AP Disconnect button again and the CMD (AP) will come back. In other words, it will cycle it, as well as shut it off.
9. Now, if you setup the Capt's Yoke AP Button like above, all you do for the FO Yoke AP Disconnect Button is choose the PM MCP AP 2C (means center) in the FSUIPC drop down list for "when button is pressed", and nothing else.
10. The final thing is this, the 1L means if the left CMD is used and 2C means if the center CMD is used, but on the B737 it is only left and right CMD buttons (there is no center button); however, like I explained before, Project Magenta is for more then just a B737, so there is an actual 3R (for right) CMD. Although, that seems weird, just trust me when I say 1L is for left CMD and 2C is for right CMD of the B737 MCP...
If you made it this far and get the settings right, you need too test what happens when you are on a approach and locked on the ILS, with both CMD buttons on for an auto-land. I did not make it that far too do a setup test for an auto-land (I am way too tired...it's 6AM CST and I got up yesterday at 8:30am CST...oh yeah!).
My point is, the settings that I used above are correct, but I am not sure if it just shuts of the right CMD button and leaves the left one on during the auto-land sequence, so that you can execute a Go-Around function, that normally is a part of an ILS plate. You know, when you go missed and it says something like...climb to blank feet and blank HDG, then proceed to blank FIX and hold, you can use the AP for that...wait that's so funny, I am telling the ATC guy ATC stuff...rotflol...I must be slap happy!!!
Okay, I am going too bed.
John
For everyone else, if you have questions on using PM, contact Angelo. He has to "Pay It Forward" :idiot: :idiot: :idiot: You will have a lot of fun Skype'ing with him...I did ;D ;D ;D
Nice job guys and thank you for putting the answers here for all to see!
Hahaha that is great! To everyone on this board I must say John is one of the nicest guys I have met in this hobby. The amount of time he spent with me troubleshooting and going out of his way to turn off his fully funtioning ProSim to emulate my PM Setup and stay up way into burning the midnight oil is amazing. Saying Thank You is not enough, he already pinned me to saying when he comes to Southern California I have to show him around lol. I will do that gladly, it is the least I could do! I must say I thought I knew a thing or two about the sim, but what I learned in the past two nights over 17 hours of tweaking is astounding. Just trying to get the darn NetDir to not show any flags when you run "PM FileCheck" PM users you will know what I mean... was a mission and a half but we did it! I just want to say a special Thanks to John and his Wife Karen for letting him help lol! Also Thanks to the great community here, without this place none of this would of happened. Don't you worry about paying it forward! I am a huge believe and will do my best to do so. Just don't ask me about any more damn PM Offsets! If I never have to look for another one after last night it would be too soon! :P
Edit: The yokes each have their own buttons but are wired as such that when either one is pressed it is the same Joy Button ID. So they are the same, program one side, it does the exact same on the other. Same goes for PTT buttons as well.
Okay got a resolution to all issues yay! Positing here for people to see whenever they experience this down the line.
I finally FINALLY heard back from Enrico after pulling my hair out trying to get the AP to disconnect either autopilot A or B and be able to re-engage it without cycling the disengage bar. Up until now all previous discussions about how to do were half measures.
The sure fire way to get the AP to disconnect whether its A or B or Dual Channel AB ILS, is by using the PM K-Codes offset in FSUIPC.
It was not a bit or byte, and it really wasn't even in the documentation. Enrico said to use K100 (Which didn't even exist and offset 04F2) Both wrong.
The real solution was in the FSUIPC dropdown, "PM MCP K-Code" then input the code of K99. This was the final and correct answer. I can now say after over a MONTH I have the AP behaving the way it should PHEW!
The best and happiest solution I found was the weird black boxes and shadowing on the instrumentation of the Nav information on the ND and terrain radar etc.
I needed to reset how the Alpha Channel Layers are drawn, and Pressing ALT+Z a few times resets it and now they look like they are taken straight out of the 737. I am a happy guy to say the least!
Cheers all!