Lauramks2

FMS 1 on the PFD shows Hukem, the fms controller shows Hukem in pink. I didn't have the ppos showing as it was on another screen not recorded but on the COPILOT MFD showed me that Hukem was straight ahead. One of the tricks I have found going from PSP to SNA is that there is a coastal mountain range just before the approach. Going from Frets which is on the TEC route (Deway frets kayoh8) direct to Hukem takes me near the 5808 ft peak on the coastal range. If you look on the FMS is shows a 4.7 degree dive to Hukem which also gives me the "no vpath" warning. After analyzing my recent flights I realize that the most prudent method would be requesting direct SAGER (IAF). That takes me parallel to the coastal mountains and gives me a longer shot getting lined up on the approach. Doing this also takes me down the valley so I can get down to approach altitudes much easier. Not the shortest route but the most prudent. You may be correct on the false ILS and the 360 degree turns. The day I was flying, I was not on Pilotedge so I could mess around and see what happened. I was intercepting with about 80 degrees cut and as I got near SAGER it started a turn to the right instead of left toward the airport. I thought maybe it was going to take me into holding to line up but it just started a 360. I went around twice just because I wanted to see if it would give me a warning or some indication of what it was doing. I didn't see anything so I went to HDG mode and lined myself up then engaged the autopilot and all was well. If I approach final at greater than 30 degrees, will it turn short, go into a hold, or do nothing? Thanks for your thoughts.

I was setting up for the RNAV Y Rwy 20R at KSNA (John Wayne). As I got close I went used the DIR button to HUKEM (a point on the approach) which was basically straight ahead of me. The PFD showed the magenta line on a heading of 197 (the final approach course) but Hukem was straight ahead of me. I flipped it into heading mode based on the MFD plan view and waited until I got close before manually turning to final and then engaging the autopilot. Attached is a screenshot of the aircraft about 5 miles prior to final intercept. For some reason I have the hardest time with the approaches to KSNA. Is this because HUKEM is not an IAF? I fly into KPSP all the time and intercept at a midpoint on the approach. It seems to work in other areas. This is the only airport where the FMS goes bonkers. I flew the ILS Rwy 20R yesterday and when I intercepted final at SNAKE it started into a right 360. Since I wasn't on Pilotedge, I waited to see what it would do and it just kept flying in circles until I manually intercepted final and stepped to the then waypoint HUKEM.

I had this issue and found that even though I was moving the physical throttle the virtual throttle was not moving out of detent and thus no fuel to engine. That caught me off guard.

Got a left and right oil pressure message on final. OOHHH interesting. Remembered seeing something about postflight oil replenishment. All is good but boss might be upset at trashing two engines. :-)

My research tells me that this message shows up when there is more than 10 knots difference between the airspeed at the pilot side and the copilot side. It is amber and most of the time I have ignored it but sometimes it affects the autopilot and kicks me back to "ROLL" mode. Took me a few approaches to figure out why I was moving off track. Took me longer to realize I needed to hit APR mode again. Now that I have figured out how to compensate, I am wondering if this happens to others. Is it a glitch or is something causing it. I thought it might be ice in the pitot but probe heat was on. It is irritating at worst and doesn't change my flying much but if anyone has some insight, I would appreciate it. If this happened for real, would I switch to a different ADC on the reversionary panel?

This only has happened on that one approach so far. As I fly around I will see if it happens again. I will also try some of the other BFI approaches to see if it is just this airport.

I was flying the 650 v 1.7 and didn't realize it. I switched to the 650 1.8 and flew it again and it still does the same thing. At Lemnn it goes for runway centerline.

Thanks, I probably did just that by jumping in the sim and getting my flight plan into the system trying to make sure my filed flight plan in Pilotedge matched. Thanks for the note. :-)

I was flying the RNAV Y rwy 14R with autopilot engaged. When it got to LEMNN, instead of turning toward COLMT it flew straight and lined up on the extended runway centerline. Approach was normal from there. Why did it do this? The image below shows me past LEMNN headed to the dashed rwy centerline.

what was the fix?

solved. It turns out that I updated the database to IRS 1 but not to 2 or 3. When I updated them all, they synced up. That was interesting because I have updated a number of times before and only updated number 1. Maybe that was enhanced in a recent upgrade?

Jiggle fixed. End of the story was that I had two switches on my CH yoke set for reverse thrust. This is what was causing the jiggle. With lots of planes and lots of settings from different software, it is sometimes hard to find the conflict. I thank you for the help. I learned a lot on the journey.

Tried to send TO speeds and got a message that systems were not in sync. Thought about it for awhile and decided to see what that meant after TO. Turns out the Pilot and CP IRS systems were no longer tied together and that somehow blocks the speeds going to my PFD. Looked all around in the cockpit, manuals and online and never found any way to link them together. One reference was to a menu in the IRS system but in my sim the only control there was to switch between Mag and True reference. Is this something that glitched on startup of the sim and not controlled in the 650? I didn't want to restart so I flew with it and my only issue was I had to manually adjust the copilot system to get the charts I wanted on his MFD. Thoughts?

Big help. Thanks

Thanks for the knowledge. From what you say, it sounds like anything I set up in the bridge should be deselected in xplane so there are no conflicts. Those not selected in the bridge can be set in Xplane. I agree that probably the best is to start clean again. I do have lua scripts for the radios and I did have a script for the autopilot. Then I used some of the profiles for honeycomb so I see how it might be a mix now. (Which is why I'm not sure what "no 8 and 9 levers (T. Reverse)" means.) On the xplane settings for the honeycomb throttle quadrant, the thrust reverse levers are labeled spot 8 and spot 9. I set those for full on thrust reverse when the levers are pulled to the on position. They both perform this action now so the only issue is the jiggle at low n1 which is easy to avoid for now. One new question if I may? Flying into John Wayne today, I found my course on final showed up as 360 instead of 196 degrees. What I found out the hard way was the left selector switch on my honeycomb autopilot when set to CRS does not change the course setting. All the other options work great. I duplicated on my next flight to be sure. I can change the course with the mouse using the knob in the simulator but not using the button on my honeycomb. Xplane doesn't even address that button at all. Can that be assigned in the configurator? My guess is a reset from a clean start may fix all these. Just trying to understand which codes take priority so I can avoid conflicts. You have been a big help. Sometimes it can be frustrating but I am having a ball learning how to integrate all the systems. I am even starting to feel comfortable flying around. Flew KPSP to KSNA and back today on PilotEdge. Thanks.