Cerppo

I'll push a new version next week.

Nope , not coded. you mean this ? I'll take a look if i can add it easily

Should be Available soon. Edit : https://github.com/landre-cerp/McduDcsBiosBridge/releases/tag/1.1-beta Any feedback / bug report welcome ( please use Issue on github ) I plan to allow Switching ( or choosing at startup ) between Pilot and Copilot , and to have BOTH ! if you own 2 ww cdus ( a PFP7 and a MCDU for example )

Very quick test for the CH-47. No colors / No special font

I like what i'm seeing !!

As this device is not really in the DCS Mood , i suspect "panel" owners already own Winwing combat dedicated devices, which is x100 more immersive i think. But if you own the FCU / EFIS , would you be interested in displaying things on it. EFIS QNH could be useful ( easier to set than often unprecise "clocks" in aircrafts ) FCU VS , Speed , HDG ? ( often on the plane HUD ) I could try to map DcsBios info to this device.

By the way, i can see that you are using the Pfp3n and it confirms that it works on this device too ! ( I was not able to test on this one ) . I'm not sure the "UFC radio report" is that useful on the AH64D, as you have this directly in front of you as a pilot . but leaving the keyboard display alone was "strange" . If you have any / suggestion let me know with direct message. Based on your experience, i added some error handling on config , and log files and this should be the 1.0 ! https://github.com/landre-cerp/McduDcsBiosBridge/releases/tag/1.0

There's some informations in the Readme file https://github.com/landre-cerp/McduDcsBiosBridge i suspect misconfig in the config.json to point to the dcsbios files. Let me know if it helps.

I'm very happy to read this ! Leaving the button mapping to user was a design choice. It's not that long to do and let everyone do it the way they want, feel used to or natural. For the ch47 CDU, i agree ! i counted the lines LSK and RSK , match , i asked the dcsbios team if i could help on making it available but looks like it's not that easy. I'm monitoring it regularly and as soon it's available i'll add it to the project. Again, glad to read that my project helped you. And the physical CDU in the A10C is a real game changer / fun to have.

https://github.com/landre-cerp/McduDcsBiosBridge/releases/tag/1.0-beta

Mcdu-dotnet lib i use was updated by vradar and now handles PFP7 ( and 3N but i cannot test on this one ) . I will release a version later this evening .

I also own a PFP7, so i'm curious to see what Kurisu did to get the PFP3 work, as i would be able to either clone or adapt the mcdu-dotnet lib i used to get the A10C work with the A320 Mcdu. Should come sooner as he updated the Lib to now handle the 777 too !

Bravo !

By the way the answer to the initial question of this thread is YES Unoffically

Lib author told me on Reddit he updated some docs https://github.com/vradarserver/cduhub/tree/main/library/mcdu-dotnet/WinWing/Mcdu

I think it's just a matter of font initialisation sequence. Or font I'd try to make my 777 cdu work now that the a10c -> Mcdu is working , but the lib by default seems to only work for the mcdu airbus. The default lib is searching for a PID ^ VID device that matches productName: WINWING MCDU-32-CAPTAIN vendorId: 0x4098 (16536) Unknown vendor productId: 0xBB36 (47926) The B777 PID is 0xBB37 , so i just changed the PID in the lib code and tried, but nothing was displayed. I also uploaded the font i customised for the A10C ( my 2nd hyptothesis was that the mcdu code refer to a default font name - and they're not the same on mcdu / 777 in the simap pro app. In the process , there's a phase to initialise the device, and as they are physically different i think the mcdu sequence do not work for my b777 . Nothing is displayed So this is the thing to "sort out / sniff " to get something displayed on it ( mcdu lib by default wont work ) - Find the correct initialisation sequence. ( hardest part ) - or just clone the sniffed traffic ? With a customised font it now looks like this

Hi Kurisu. This is exactly how i reversed my Cockpit master cdu 737 ( usbpcap etc. ) Winwing seems to be much more complicated. And i had no clue on what was going on. Now that i see in the C# code Font management, USB data stream , Initialization sequence, etc ... Without knowing the the "protocol" I'm afraid it's not that simple. it seems to use a message / stream usb (i'll look again at my USB complete book fifth edition) By the way since few minutes, i'm testing the v0-alpha of my bridge between DCSbios and the Mcdu ( key binding left to DCS ) , and it's looking good. And i have no code that explains how to communicate with mcdu as i use the mcu-dotnet lib on High level !

Look at the sample section in Library ( https://github.com/vradarserver/cduhub/tree/main ), it's quite clear on how to use the Mcdu object. Pb might be that changing the PID to the PFP3N is not enough to make things work. I tried this very quickly to test my "working code" with a 777 cdu WW ( change ) 0xBB36 pid ( MCDU ) to 0xBB37 ( pid of the 777 ) but nothing showed. My 1st guess is that the "init sequence is different and though do not work on different devices" My code is still a big mess ( wip ) , not organized. But the good news is - it displays pages with a decent char mapping ( and default font of the mcdu i think ). - uses Leds to show Master Caution / NWS / Canopy / Gun Ready Keybindings are to be made in DCS ( which is annoying, but flexible and need no extra code ) . To conclude - I'll share the code ASAP but i'm afraid it won't help you cause it's high level. PS. I agree , there's some black magic in the cdu driving part .

Hi, inspired by the great work of this person https://github.com/vradarserver/cduhub/blob/main/library/mcdu-dotnet/README.md I'm working on something. At the moment, it's a quick and *very* dirty code with hardcoded folder name, etc .. started few hours ago. Based on things i made for the cockpit master CDU737 and DCSFlightPanel. I've not decided yet if i stay in DCSFlightPanels and tries to use this library ( Or the opposite , bring some DCSBios things into a fork of this https://github.com/vradarserver/cduhub/tree/main , dedicated to DCS modules , which my example is coming from ) But it's a good start i think. Tried with A320 Mcdu , but i also can try with the 777 ( think it's just Pid & vid stuff ) .

if it's the same logic as the Cockpitmaster CDU, you need to send data to device, in a specific way to display things on the screen. I reversed it to make mine work with a10c ( and some more modules ) and dcsbios ( in dcsflight panel). ( made a wiki to explain https://github.com/landre-cerp/cdu737-lib/wiki ) Winwing cdu on it's way, i'll give it a try, but the Game peripheral display Tab in the Simapp pro, the possibility to change fonts , and hint on pixel position makes me think it could be really different.

same, that long and this often degraded is quite new (as far as we noticed) . But thanks for the detailed explaination ThGhost !

Thanks ! Is this "normal behaviour" or a way to make it work in the game ?

Hi, we ( our team ) find CBU105 alignment very, very long ( 30+ mins lately) to get ready, and sometimes in fly they became DEG again. ( degraded i suppose ) .Any explanation on this behaviour, besides bug ?