A32NX MCDU Server - Thermal Receipt Printer

Pumpkinking9609 · January 3, 2022, 1:59pm

This is amazing news, thank you so much!

ryane1234 · January 4, 2022, 9:24am

Do you think it’s a quick issue to sort.

ryane1234 · January 4, 2022, 9:39am

Has anybody tried it on the new exp version check if that works.

Vonzeigler · January 4, 2022, 9:49am

The original message mentioned using your phone or ipad for mcdu. How do you get that to work? Would be cool for programming flights.

ryane1234 · January 4, 2022, 10:07am

It’s in the fly by wire release notes. Navigate to fly by wire a320 aircraft folder in the community folder then server then run the mcdu server. It will ask if you want to use a printer select y or n then load up the sim and when you load into an Airport in the aircraft it will display the IP address type that in the phone or tablet and it will appear on the screen.

Pumpkinking9609 · January 4, 2022, 1:52pm

The server works for sure in the exp version. I don’t think they’ve fixed the printer font size issue yet.

ryane1234 · January 4, 2022, 4:30pm

Do you think they will sort the issue quickly or not make it a priority as it currently prints out correctly on a normal printer.

Pumpkinking9609 · January 4, 2022, 8:37pm

You’ll have to ask them!

ConnorMcLeood · January 4, 2022, 9:40pm

problem is already solved and will be implemented with the next dev update

Pumpkinking9609 · January 5, 2022, 6:40pm

I can see this has now been fixed on the GitHub, just unsure what variable to input after the newly added —paper-size argument…?

Pumpkinking9609 · January 5, 2022, 6:43pm

github.com/flybywiresim/a32nx

feat: mcdu server improvements

flybywiresim:master ← tyler58546:mcdu-server-error-handling

opened 08:27PM - 30 Dec 21 UTC

tyler58546

+205 -80

Fixes #6468 ## Summary of Changes * Improved error handling for the MCDU S…erver * "Press any key to continue..." prompt will now appear after an error if no args were passed or if debug mode is enabled * Added a message about opening ports on the firewall * Added `--font-size` and `--paper-size` arguments * Changed printer font for better legibility on thermal printers * Changed default http and websocket ports to 8320 and 8380 * Fixed missing newline on printouts * Fixed scratched color on remote mcdu ### Print Spooler Service not running Now only shows if printing is enabled. ``` > server Would you like to enable printing to a real printer? (y/N): n Starting server... ``` ``` > server Would you like to enable printing to a real printer? (y/N): y Error: Failed to load printers. Make sure the "Print Spooler" Windows service is running. Run with the --debug option to see full error details. See the documentation for more information: https://docs.flybywiresim.com/fbw-a32nx/feature-guides/web-mcdu/#troubleshooting Press any key to continue... ``` The full error details are only shown when debug mode is enabled: ``` > server --debug Would you like to enable printing to a real printer? (y/N): y Error: Failed to load printers. Make sure the "Print Spooler" Windows service is running. Full error details: Error: Command failed: Powershell.exe -Command Get-CimInstance Win32_Printer -Property DeviceID,Name Get-CimInstance : Generic failure At line:1 char:1 + Get-CimInstance Win32_Printer -Property DeviceID,Name + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [Get-CimInstance], CimException + FullyQualifiedErrorId : HRESULT 0x80041001,Microsoft.Management.Infrastructure.CimCmdlets.GetCimInstanceCommand at ChildProcess.exithandler (child_process.js:308:12) at ChildProcess.emit (events.js:314:20) at maybeClose (internal/child_process.js:1022:16) at Process.ChildProcess._handle.onexit (internal/child_process.js:287:5) { killed: false, code: 1, signal: null, cmd: 'Powershell.exe -Command Get-CimInstance Win32_Printer -Property DeviceID,Name', stdout: '', stderr: 'Get-CimInstance : Generic failure \r\n' + 'At line:1 char:1\r\n' + '+ Get-CimInstance Win32_Printer -Property DeviceID,Name\r\n' + '+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\r\n' + ' + CategoryInfo : NotSpecified: (:) [Get-CimInstance], CimException\r\n' + ' + FullyQualifiedErrorId : HRESULT 0x80041001,Microsoft.Management.Infrastructure.CimCmdlets.GetCimInstanceCommand\r\n' + ' \r\n' } See the documentation for more information: https://docs.flybywiresim.com/fbw-a32nx/feature-guides/web-mcdu/#troubleshooting Press any key to continue... ``` ### HTTP port in use ``` > server Would you like to enable printing to a real printer? (y/N): n Starting server... Error: Port 8125 is already in use See the documentation for more information: https://docs.flybywiresim.com/fbw-a32nx/feature-guides/web-mcdu/#occupied-port Press any key to continue... ``` ### Websocket port in Use ``` > server Would you like to enable printing to a real printer? (y/N): n Starting server... Error: Port 8080 is already in use See the documentation for more information: https://docs.flybywiresim.com/fbw-a32nx/feature-guides/web-mcdu/#occupied-port Press any key to continue... ``` ### Firewall message ``` Simulator connected! To control the MCDU from another device on your network, open http://xxx.xxx.xxx.xxx:8125 in your browser. To control the MCDU from this device, open http://localhost:8125 in your browser. Can't connect? You may need to open TCP ports 8320 and 8380 on your firewall. See the documentation for more information: https://docs.flybywiresim.com/fbw-a32nx/feature-guides/web-mcdu/#firewall-configuration ``` ## Screenshots (if necessary) ## References ## Additional context Discord username (if different from GitHub): ## Testing instructions ## How to download the PR for QA Every new commit to this PR will cause a new A32NX artifact to be created, built, and uploaded. 1. Make sure you are signed in to GitHub 1. Click on the **Checks** tab on the PR 1. On the left side, click on the bottom **PR** tab 1. Click on the **A32NX** download link at the bottom of the page

github.com/flybywiresim/a32nx

Physical printing on POS style thermal printers is unreadable

opened 05:06PM - 02 Jan 22 UTC

plhought

Bug

### Aircraft Version Development ### Build info ```json { "built": "2022-0…1-01T15:56:48+00:00", "ref": "master", "sha": "e43e61e317489340a6b11e4960bcb72e72b0e722", "actor": "aguther", "event_name": "manual" } ``` ### Describe the bug Utilizing the new print interface of the MCDU server, when utilizing a widely avialiable and inexpensive POS style thermal printer ("POS-58" type - which is widely re-branded as resold under a number of different brands - TEROW, WAVA, MUNBYN, Zjiang etc etc), the text is very small an unreadable - along with going through about a foot and half of thermal paper before actually attempting to print something. ![20220101_121800](https://user-images.githubusercontent.com/96991444/147883368-08deeb52-caeb-4341-835c-d32404492785.jpg) This is in contrast to a similar function on the FSLabs Airbus, which actually includes pre-built settings to support POS-58 thermal printers, as they are widely utilized by some of their userbase. ### Expected behavior The text would print more in a manner similar to the actual aircraft - which also uses a thermal-printer - although wider. ### Steps to reproduce 1. Have a POS-58 type thermal printer 2. Correctly set up the MCDU Server print option 3. Attempt to print something via the ATSU in the MCDU ### References (optional) ![20220101_121800](https://user-images.githubusercontent.com/96991444/147883396-aec82128-bcc9-4481-a757-54112afb4c93.jpg) ### Additional info (optional) _No response_ ### Discord Username (optional) Patrick#2854

TBHpapa · January 8, 2022, 6:48pm

I’m wondering the same thing. Has anybody been able to get this to work correctly with a C8 paper size thermal printer? This is as far as I get before I become lost.

Pumpkinking9609 · January 8, 2022, 7:17pm

I dont really understand how github and the FBW releases work, but i got a reply on the github page saying we must be patient and it will be added to the next release… not sure what that means? perhaps someone cleverer than me can explain how it all works?

But essentially I think we need to wait and I’ll be added soon.

Watsi01 · January 8, 2022, 7:56pm

It means: the support for your printer is ready to go. It is now being cycled through our QA departement (testing). When they give their ok, we implement it with the following release.