Currently only the following lights (for the Bravo) are programmed:

• Master Warning
• Master Caution
• Engine Fire
• Parking Brake (only shows if you've set it properly  )
• Anti Ice
• Starter Engaged
• APU
• Door

Note 1: The aircraft needs to be electrically powered for the lights to work.
Note 2: Ensure all Yoke switches are in the up position and all on the Bravo are down before loading up for optimum results. I programmed (most) switches to operate in the direction they operate in the sim.

UPDATE 25 JAN 22: Reverser bindings would only work on the Honeycomb Airbus throttle set - updated to work with the original 'Boeing' style throttles. File included if you wish to use your Airbus levers which adds an extra button (ATS Disconnect on lever 2).

Currently, I cannot seem to program TOGA, Max reverse or AP Disc functions as these variables don't seem to work in the HC Configurator. Will update if a fix appears in the future.

Credits to Dendarian (Ian) who has been incredibly helpful!

Challenger 650 Throttle Layout.pdf

Challenger 650 Yoke Layout.pdf

CL650 Alpha-Bravo Configs 25JAN22.rar

Thanks!

CL650-Bravo_Setup.zip

I think the VR experience for a day-one release is fantastic. No issues with flying the plane. My only feedback would be:

1. The ability to communicate with the fuel truck, ramp worker, and use the cell phone inside VR (make the menus similar to the study menus that are usable in VR). This would only apply once inside the cockpit.

2. Several 3-way test rocker switches do not centre in VR. I *think* this might be an X-Plane VR controller limitation and not an issue with the plane.

3. Limit the knob rotation sensitivity (although this is something a user can easily accomplish to their own liking in VR config)

In terms of movement inside the aircraft - for me it's not as huge a deal. Yes, VR hotspots would be appreciated (maybe even just one near the door so that it can be closed without having to leave VR).

Again, just some items to add somewhere on a future to-do list. Nothing mission critical or immersion-breaking. This plane handles great in VR (the HUD is fantastic!) and I am having lots of fun. Thanks again for all of your hard work.

I'm building a python script to integrate Challanger 650 CDU with Winwing PFP 3N. I've got the proper datarefs, specifically CL650/CDU/{cdu_number}/screen/text_lineX and CL650/CDU/{cdu_number}/screen/style_lineX where X is from 0 to 14 representing the line. The text lines are straightforward and represent the text, but the style lines are byte arrays with 24 bytes (same number as columns) which seem to be representing the style/color of each character. 

I can confirm through experimentation that different character colors displayed on CDU have different style_line byte elements. I was hoping there is a documentation around what each byte value or each bit in the byte means so I don't need to reverse engineer it. 

Do you guys think it would be possible to get this published?

Sergey

I want to build a CDU with physical button in my cockpit, and I need to export only the screen. What is the solution?

This is the first prototype of the CDU front panel made of wood using laser cutting

I just upgraded my PC with a Tobii Eyetracker 5

However, as long as the Tobii is active, I cannot walk aorund in the FBO or around the aircraft by using the WASD keys. They don't do anything. Up to now, the only solution I found was to deactive the Tobii Plugin as long as I want to use the WASD keys.

Is there any other solution beside this? It's quite complicated to turn it on and off all the time using the plugin manager 

Thank you in advance for your help!

BR

Thomas

I'm working on integrating Challenger with the winwing PAP3 panel. The PAP3 panel can indicate with speed selector is Kts or Mach, just like on PFD speed tape, but I'm struggling to find a dataref which indicates the mode that's selected. 

Any suggestions?

i was wondering if there is someone who is using Octavi IFR1 with this beatiful plane?

I saw it online and it could be interesting.

Ciao

When I assign a key to this reference through the X-Plane Key assignment, it works.  When I try to assign it to a GoFlight MCP button using the GIT, it doesn't work. If there is anything unique about this dataref, please let me know.  Is the refer you should select assign a joystick button to toggle the AP ENG switch on and off? 

Thanks!

Rich Boll

Wichita, KS

Does anyone here use Spacedesk to create an additional display?

I installed it on an iPad 2 I don't use anymore to have a remote CDU.

It works quite well with the native XP12 737 but not with the CL650. Actually, I can move the CDU to the iPad screen but then it freezes and I can't press anykey.

I don't know if the problem is from the iPad which might be too old, or from the Wifi or even from the CL650 itself.

So if somebody uses Spacedesk succesfully with a similar setup, I'm interested in knowing about your setup.

Few months ago I started to build a FCP for the CL650 using Mobiflight. It is a very simplified version without any LEDs.

Having not as much time as I would like to work on it, it goes slowly. But now, with already some help from Pils, it is almost working 

Unfortunately, I still have a problem with the command "CL650/FP/ap-eng" that doesn't work and I can't find a solution, even by reading some other related topics on thus forum.

So, here is the problem:

All my FCP's buttons and encoders work well except the AP ENG button that is not able to trigger the ap_eng command in the sim.

The sim AP ENG works well by cliking directly on screen or by using a keyboard key, but I can't find a way to make it work by using my FCP AP ENG button.

I tried the following:

1- I assign the CL650/FCP/ap-eng command to the FCP AP ENG button like any other one in Mobiflight >>> It doesn't work

2- I assign another command to FCP AP ENG button (CL650/FCP/hdg_sync for instance) >>> It works, so it doesn't to be a problem with the button itself, nor with the arduino or Mobiflight.

3- I assign the CL650/FCP/ap-eng command to another FCP button >>> It doesn't work

4- I assign a keyboard key to the AP ENG in the sim >>> it works

5- I assign a keyboard key emulation to the FCP AP ENG button and then assign the emulated key to xplane AP ENG >>> Then xplane is able to read it very well when doing the keyboard key assignment in the sim by pressing the FCP button, but when using it, the sim AP ENG is not activated by pressing the FCP button.

6- I assign the same keyboard key emulation to another command >>> it woorks!!!

7- I tried some other combinations without better success for the ap-eng command.

I don't understand why this specific command does not work and I'm out of ideas to try something else.

If you have any idea, I'm all ears...

I know you can open the panel with a command 'CL650/cabin_info/popup' but I was hoping I could select each message to play with a command.

Can anyone guide me to the line in the script that sets that value and tell me what it should read?  I have been using the mouse on the screen to push that button but it is irritating me now. I use that function regularly and like so many computer issues, who knows what electron flew out of line to get that to happen but it would be great to get it back. 

Would it be better just to find and load the original script again rather than track down one little error? 

So far, with @Pils's CL650_xsaitekpanels.ini file, the multipanel was displaying 0s only, instead of the ALT, VSPEED, HDG, COURSE, etc.

I've been digging into it lately, to try and make those displays work, and I managed to find the datarefs. I now got the HDG showing properly, by using abus/CL650/ARINC429/FDCU-1/words/FCC/0/HDG_SEL.

I have also found the following datarefs for ALT and IAS, but the values are in meters for the ALT, and in meters/second for the IAS:

abus/CL650/ARINC429/FDCU-1/words/FCC/0/ALT_SEL
abus/CL650/ARINC429/L-PFD-1/words/FCC/0/IAS_SEL

For the VS value, I've only found datarefs that have values that I cannot decipher, but certainly don't look like 1000, 2000, 2400, etc; the values are not in feet per minute.

I certainly would appreciate someone pointing me in the right direction for finding those datarefs.

Thanks in advance!

There is an issue, and it's either on the Xplane side of things or with the Stream Deck software. When I turn the knob at a "normal" rate, i.e. same as I would turn it in the real aircraft, there is a noticeable lag in movement of the heading bug. It appears to me that the keypresses are sent repeatedly at a fixed rate, which is too slow. As a consequence, the heading bug keeps moving even when I stop rotating the knob, until all the "rotary knob" keypresses have been absorbed by XPlane. A further side effect is that reaction to any presses of the actual keyboard is delayed, again until all the "rotary knob" keypresses have been absorbed by XPlane.

I looked around the StreamDeck SDK documentation, and these made me think that the StreamDeck software, out-of-the-box, sends not only a key-down but also a key-up command for every notch of wheel rotation, which further increases XPlane's workload.

The solution most likely lies in writing a plugin for the StreamDeck software or or for XPlane - both of which are possible, but beyond my abilities - . But just on a hunch, I am posting this here as well, perhaps the HotStart folks have an idea on how else this could be done? (Note: as of this writing, the folks at Elgato have not yet updated the SDK API for the rotary knobs, so a solution might be forthcoming from their side.) 

As is, what I have done is still usable, but you mustn't be in too much of a rush when turning the knobs.

The StreamDeck+ seems almost born for fsim use. The knobs are also have a momentary push function, just like the FCP knobs. So if you push the HDG knob, I have mapped it to sync the heading bug to the current heading - exactly like the real knob. And it gets even better: You can map 2 different actions to a knob push. In the picture, you can see that my leftmost knob is mapped to change the DCP1 range. But if I give it one push, then the mapping changes to PITCH/VS wheel up/down.

Another neat thing is that the StreamDeck + has a touchscreen just above the rotaries, and can detect left and right swipes, allowing me to swipe to a second page of mappings. On my second page, I have a rotary set up for setting the BARO QNH/altimeter setting, with a knob push mapped to toggle between STD and preselected QNH. It's just great!! And on my third page I have the 10th stage bleed buttons mapped,  so it is totally easy to transition from APU to engine bleed source and back. I'll also setup anti-ice controls when I have a chance, and then figure out how to post the mapping profile here - that is also possible. I don't know how many pages of mappings you can have, but I'm at 4 pages so far and it is still offering me the option of adding more.

Final detail: you can download the StreamDeck software even if you don't have the hardware, which allows you to see how easy it is to configure. I am totally impressed with what Elgato have come up with here. And full disclosure, I have no connection to them whatsoever.

Cheers

LC

Log.txt