PosPrint | Thermal reciept printing using System.Drawing & Wpf | 3D Printing library

Before and after PrintMemoryBitmap, try changing the ILegacyControlObject.BinaryConversion property to Nibble or Decimal and add a process to return it to None.
ILegacyControlObject Interface (POS for .NET v1.12 SDK Documentation)
ILegacyControlObject Properties (POS for .NET v1.12 SDK Documentation)
ILegacyControlObject.BinaryConversion Property (POS for .NET v1.12 SDK Documentation)
BinaryConversion Enumeration (POS for .NET v1.12 SDK Documentation)

An example of how to call it is as follows, which is coded in MainForm.cs of the sample application of POS for.NET SDK.

There are a lot of complications involved in this.

First, as I answered the previous question, if you are using POS for.NET(including OPOS/JavaPOS), don't send the printer's ESC/POS control command directly with the PrintNormal method.

If you want to print a QR code, it may be supported by PrintBarcode method, please check the ADK document of EPSON, and if you can't find it in the ADK document, please contact EPSON support desk.

It is possible to send ESC/POS control commands for the printer according to the UnifiedPOS specification.
A UnifiedPOS POSPrinter escape sequence called "Path through embedded data" (ESC|[*]#E) will send the bytes of data specified in # directly to the printer.
However, it is assumed that the service object supports the feature. Please check with your ADK documentation or support contacts for support availability.

Next, it depends on whether you're using a POS for.NET native service object or an OPOS service object via COM Interop.

When using OPOS service objects, the conversion from Unicode to ANSI code pages is done automatically by the OLE runtime function during the method call, and character codes greater than 127 can be changed by the system code page. Also, if there is a 0x00 in the middle of the data, it will be terminated there and the rest of the data will be ignored.

This is because the parameter of the PrintNormal method are string, not a byte array.

ILegacyControlObject.BinaryConversion property of the service object can be changed to Nibble or Decimal instead of the default value of None.
However, depending on the implementation of COM Interop of POS for.NET, attention may be needed, so it is better to contact the support desk about how to use it.

If you're using a native service object in POS for.NET, it depends on how it's implemented. Again, please check with your ADK documentation or contact support desk for more information.

The reason why letters like F are printed is because the printer is in the initialized state, code page 437.
Look at the letters in the following material at 213 in decimal and 0xD5 in hexadecimal.

Page 0 [PC437: USA, Standard Europe]

Page 19 [PC858: Euro]

The POS for.NET service object internally manages code page settings according to the value of CharacterSet property.

If the application arbitrarily sends initialization commands to the printer, the service object's management information may be inconsistent and the printer may print incorrectly.

If you are using POS for.NET (including OPOS/JavaPOS), you should not use the initialization command (ESC@) or similar commands to change the mode or settings.

In that sense, instead of sending the paper cut also directly the ESC i({ 27, 105 }) command, call the CutPaper method or put the POSPrinter paper cut escape sequence (ESC|P) defined in UnifiedPOS in the print request string.

Please check if the port name setting by Epson.opos.tm.setpos.exe/SetupPOS.exe etc. is correct.

ErrorCodeExtended: 10002 will be below.
It is described in "C:\Program Files (x86)\OPOS\Epson2\Include\epson.h".

"SWD\PRINTENUM{9475957E-9973-435B-AF15-4591F5938233}" is the DevicePath as a standard Windows desktop printer.

EPSON OPOS/OPOS for.NET should not support that mode.

If it is visible on the device manager, it is a usage mistake.

Disconnect the printer, uninstall the printer driver, use the OPOS ADK for.NET, see Appendix-C in the appropriate printer manual, change the hardware settings, and reinstall the device driver (USB serial?) .

Configurattion XML of PosDM settings should be set in the GUI by running the SetupPOS tool of EPSON OPOS for.NET as an administrator instead of the command line.

For details, refer to the SetupPOS User's Reference Manual.

@Dan Neely,

The fundamental problem that you are encountering is that the Brother QL-810W label printer supports ESC/P as opposed to ESC/POS. These are two printer control languages both designed by Epson, but they are not the same. ESC/P is used for page printers and ESC/POS is used for receipt printers. Furthermore, the documentation that you cite states that our ESC/POS implementation supports network and Bluetooth attached printers with no mention of USB connections. The out of band pairing, which is simply a manually authored connector string, will not help in this situation due to the two issues noted above.

The only way to interact with a USB connected printer via Windows.Devices.PointOfService at the time of this response is through our OPOS Bridge implementation which requires the installation of OPOS and a OPOS service object from the hardware vendor. If OPOS is in a working state, we will attempt to communicate with the OPOS Common Controls however Brother does not offer an OPOS service object for this printer today.

In the future we hope to provide support for additional printer control languages and modern driver interfaces that do not require OPOS to access a locally connected printer.

Please use the PointOfService tag when referring to implementations using the Windows.Devices.PointofService API namespace to make it easier for us to find questions on this topic in the future.

Terry Warwick, Microsoft

JavaPOS is not completely device independent software for general purpose.

In order to operate a certain device with JavaPOS, it is necessary for the vendor of the device to provide corresponding JavaPOS control.

If there is no JavaPOS control for the printer you are using, only the jpos.xml file does not work.

If the vendor of the device provides the corresponding JavaPOS control, the description method of jpos.xml should be described in that explanation document.

Please check that the vendor of the printer provides JavaPOS control.

Otherwise, switch to the printer of another vendor that provides JavaPOS control, or print directly using OS's API and printer control sequence, not JavaPOS.

According to the official document, USB connected printers are currently not supported.

Support is currently limited to the Network and Bluetooth device models listed in the tables below. USB connected printers are currently not supported. Please check back for additional support to be added in the future.

For mor info, please see Device support in POS Printer.

As said in the comments, what solved for me is check the versions of fxp/composer-asset-plugin on local and on the server. Updating both solved my problem.

Check version: