Lauramks2

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.

Thrust Reverser setup? Originally I had the no 8 and 9 levers (T. Reverse) set up to "toggle thrust reverse". That didn't work so I set them to "100% reverse" (can't remember the term) when I pull the lever. That works great on both engines. On landing I can pull both levers and get TR activated. It is just engine one that jiggles at idle. I eventually thought I could get around the jiggling by not assigning anything to those two levers but it still jiggled. I even tried turning off the thrust reverse switches but I still get a "REV" indication on engine one. I have perused the log file to see if it would give me clues but nothing so far. Thanks again.

Thanks for your response. I recently posted in this forum a question about how these two programs interact. I have been using the honeycomb profile you posted and that seems to work fairly well. I have seen information that suggests that I set all the xplane controls to "do nothing". What I don't understand is does the configurator override the xplane control settings or does it actually set them up? When I first got the honeycomb quadrant, I went into xplane like I normally would and set up all the buttons and levers there. Then I found out about the configurator. The configurator sets up a profile and bridge in xplane 11. I downloaded a profile and installed it in the bridge. Then I copied the bridge program over to xplane 12. If I have the bridge in the xplane 12, should I just delete my Challenger 650 profile in xplane 12? Or should I keep it and make sure all buttons are "do nothing" so that the configurator profile sets the buttons? Is there reference materials that I can view to better understand the interaction? Can I view the configurator settings to know what your profile sets up for each button? I use the first six programable switches for specific views. Here is where I am at now. I have found that the reverser only jiggles when the n1 is under 32% on the no 1 engine. Engine 2 works great and the reverser works great. If I keep No 1 throttle at 33% I can taxi and takeoff per normal. In flight is just need to be careful not to pull that throttle back too far. That has allowed me to fly the plane. Not ideal but ok. One thing I found on your profile is that if I pull the right throttle below the low detent (as if I pull to cutoff) the engine stops! I had to fly a single engine approach into John Wayne the other day when I noticed I had accidently shut it down on short final. Turned out to be easily accommodated but a bit of a shock. No. 1 engine does not do that. I appreciate your input. It really helps. Laura

I am running a profile from the Honeycomb configurator to set up my Honeycomb throttle quadrant. I have seen some notes that suggest I make sure my "other settings are all on None". If I run my Honeycomb profile, should I go into Xplane 12 and set all those hardware settings to none? Does the profile override the xplane settings? Are the profile settings reflected in the xplane settings? How can I know for sure which settings each button is set to perform? Is there a source document I can refer to on the Honeycomb process and how it affects xplane?

I am having an issue with the left thrust reverse lever. I have downloaded your profile and all looks great except for the thrust reverse. As you see in the video, it jiggles and it keeps me from using engine 1. I have reloaded the 650 but that didn't fix. I have used xplane 12 settings to "do nothing" and that didn't fix. I have deleted the AFC_bridge folder and that didn't fix. It seems a config conflict somewhere. Is there a way to trace the conflict? I think I am using the Boeing profile? Would the Airbus be better? Thoughts? jiggy thrust reverse.mp4

Thanks for the help. I tried to fix by reinstalling the 650 but that didn't fix it. That makes me think it is in the Honeycomb settings or the xplane settings. I will look for a conflict somewhere.

I am using xplane 12? Could that be an issue?

I deleted the AFC bridge from the plugins and it still is jiggy.

jiggy thrust reverse.mp4 here is a video of the issue

I just purchased the Honeycomb Bravo and overall I love the hardware. As I was setting it up I came across some profiles and learned about the "configurator" program. After messing around with that program my throttle 1 hardly moves in conjunction with the hardware throttle and the thrust reverser on one keeps getting stuck on. Visually the thrust reverser lever in the sim is coming on and off all the time (jiggling). I am wondering if the AFC Bridge plugin is in conflict with the XPLANE 12 settings for the throttles. It kind of seems like a physical connection issue but I have tried the other throttles on that #2 station and none make a difference. Anyone have some ideas? Not quite ready to return it if I can fix it.

It's not a biggie once you know. It took some concerned research time to figure out while i was running the checklist trying to get launched. I ended up skipping the check and only later stumbled on the solution. Forces the question of would you enter IFR knowing you couldn't turn on the windshield heat. Thanks for the answer and I am sure it will come out in an update later.

Is it just me or what? If I use my mouse to turn on windshield heat and wing anti-ice I have to move my mouse up to get the switch to go down and vice versa. Is this a known issue?

Pils: Thanks you for all the help. Rose Mode: I ran into this before and I can see I have forgotten what that looks like. I thought I was it in. I am working on setting up the memory functions. Those seem really helpful. I have set the copilot up so that I get the checklist on one, the summary page on 2 and a full screen on 3. That helps as I also like to see the chart on the CP side. I will set my Mem 1 so I get the approach in rose mode. I will watch again and try to figure out why the boost in power on one side. I have flown a number of approaches with SPEED engaged and the needles totally centered all the way down final. That is always joyful. I have battled with the ATS a lot on final. Something I am doing is kicking it off. If I see the speed getting slow, i put the throttles up a bit, disengage the FD and reengage the ATS. All that takes time and destabilizes the approach. I super appreciate the time it takes for your review of the video. It helps a bunch. I am getting more comfortable with this aircraft and the depth of the systems makes it fun to learn.

I like these little AHA moments. Nice to know about the 13% split. One issue I had yesterday was I ran the onboard copilot checklist function. I like how I can click down the checklist and have the copilot work the switches. Twice now, I have gotten to the last part of the landing checklist when the copilot started running the go-around checklist which starts with N1-TO. Suddenly my approach is thrown for a loop and I don't have an easy way to stop the checklist from proceeding. Obviously something I am doing is triggering this so I record the flights to self debrief and figure out what is going on.

Yes, I have a three screen setup and I use the pop up controls to make changes easier but the recording only captures the center screen. FPS on most other aircraft is in the 30's. The challenger eats up a lot of FPS. I have had this computer for a couple of years and it was primed for XP11. Even at this FPS it seems to be realistic to me.