Abacre Restaurant Point of Sale can work with any OPOS compatible printer, pole and cash drawer.

Note you should make the steps below if you have receipt or kitchen printer, pole or cash drawer. If you have other type printer you may use Windows Driver option from Bill Configuration window.

Supports any OPOS compatible line displays via OPOS service objects provided by the manufacturer. Install the OPOS drivers as per the device manufacturers installation instructions. Magnetic Stripe Reader. Windows provides support for the following magnetic stripe readers from Magtek and IDTech based on their Vendor ID and Product ID (VID/PID). Unified Point of Service (OPOS and JavaPOS) drivers support IBM & Toshiba POS specific peripherals such as 2x20 displays and receipt printers on Windows and Linux. UPOS 1.14.1 was the last to ship a JVM, you are now responsible for supplying your own. UPOS Knowledgebase. UPOS lifecycle &. Drivers, Files & SDK Downloads. Welcome to our download tool. By downloading a driver, you agree to the terms and conditions of the applicable End User License Agreement (EULA) on behalf of yourself and the company you represent.

In general the installation procedure consists of 4 steps:

1. You download and install CCO OPOS drivers. These drivers are used with any device (printer/cash drawer/line display/barcode scanner) of any manufacturer. You may check the latest version of the CCO OPOS driver on official OPOS page: www.monroecs.com/oposccos_current.htm. Click here to start download immediately (direct download link). Note: sometimes POS hardware manufacturer stores CCO OPOS drivers on CD shipped with hardware.

2. You install OPOS drivers from site or CD provided by manufacturer of your POS device (printer, pole, cash drawer).

3. You assign any desired logical device names (LDN) to each device in OPOS configuration utility provided by POS hardware manufacturer.

4. In Abacre Restaurant Point of Sale you assign chosen logical device names (LDN) to devices: bill printers, kitchen and bar printers, pole (line display) and cash drawer.

Read below sample installation procedure for any EPSON OPOS printer.

Download and install CCO OPOS drivers. If you already have the CD disk which normally comes with your Epson printer then skip the first 8 steps, insert your CD into computer, launch the setup of OPOS drivers, then go to step #9.

1. Go to Epson web site: www.epson.com

2. Select your receipt printer model.

3. Click on Drivers link.

4. On the drivers part of the page search for OPOS ADK v2.80E.

5. Download Epson's OPOS ADK for latest version.

6. After all files downloaded, start the main OPOS file (adk280er2.exe)

7. It will propose to specify temp folder. Give temp folder and distribution files will be extracted.

8. Start Setup.exe file. For example, if you specifies temp folder: c: then full path to setup file will be c:OPOSADKV280eOriginaldisk1Setup.exe.

9. Setup process will be started.

10. During installation you may click next for all setup windows.

11. Once installed, SetupPOS application will be started. Close it for now.

12. Install all service packs. During installation of service packs click always Next.

13. Click on Windows start button, then select OPOS folder, then start SetupPOS application

14. In this application you should define your printer, pole, and cash drawer.

15. For example, for defining printer, right-click on POSPrinter devise, and choose Add New Devise command.

16. Select your printer model from drop down box.

17. Select the detailed model. 'P' is for parallel, 'U' is for USB, and serial devices (COM ports) generally have no suffix.

18. In field 'Add New LDN' (Logical Devise Name) set a random name for your printer, for example, you may just call it Printer1.

19. Click Next button and choose how you printer is connected to computer: serial port (COM1 or COM2) or parallel port (LPT).

20. Click finish.

21. Connect printer to computer by cable and stitch printer on.

22. Test how it was installed: right-click on printer and click on CheckHealth Interactive. Normally a window should be displayed

23. Add devises: pole and cash drawer if you have them.

24. Start Abacre Restaurant Point of Sale. Logon as admin.

25. Start menu Configuration - Bill Configuration.

26. Select 'Print using OPOS Driver'.

27. Set Logical Devise Name as you chosen it (for our example it was Printer1).

28. Press Save button and now you may print a test bill.

Note: cash drawer may be connected directly to computer or directly to printer. In second case you should choose the same port. If you want to be sure that cash drawer is correctly connected, in SetupPOS application you may change View from Devise Class View into Port Connection View by using View command from main menu of SetupPOS.

See also:

An Microsoft .NET application wishing to utilize retail devices has at least two available approaches.

Ibm Opos Configuration Utility Driver

OPOS via COM Interop

Microsoft .NET's COM interoperability support allows straightforward integration of the OPOS Common Control Objects into .NET applications. One can directly reference COM objects, and Visual Studio will build the required interoperability layer.

Alternatively, available below are OPOS CCO interoperability assemblies created by the Microsoft TLBIMP utility. All use the 'POS.Devices' namespace, and the class names are consistent with the CCO names. Creating an instance of the class will instantiate the corresponding OPOS CCO, after which time one may call OPOS methods and properties, plus add handlers for events.

A typical .NET POS application will include the following in its software stack. Ensure that all of these components are installed, plus registered and/or configured as needed:

• Application. Since the CCOs and and most vendors' Service Objects are 32-bit components, the application's Build Properties must target x86.
  
• OPOS for .NET Assembly. The application references and creates an instance of the assembly's device class. Creating this class causes an instance of the corresponding OPOS Common Control Object to be created. Adding event handlers to this class will hook into the Control Object's events.
  
• OPOS Common Control Objects. The Common Control Object lives for as long as the assembly's device class that created it. (The registered CCO version must be greater or equal to the OPOS for .NET Assembly.)
  
• OPOS Service Object. When the application calls the OPOS for .NET Assembly device class' Open(DeviceName) method, it calls the Control Object's Open method, which looks for the DeviceName in the registry to find and instantiate the appropriate Service Object. (You can manually browse the registry beginning at the key HKLMSOFTWAREOLEforRetailServiceOPOS to find the valid device names.)
  The service object must be acquired from the hardware vendor, and must be installed and configured using instructions from the vendor. Most vendor's configuration utilities offer a test option (which often run the OPOS CheckHealth API). During setup, you should try it to make sure that the Service Object is set up and working with the hardware before adding the additional software layers.

The pre-built assemblies plus a sample application may be foundbelow.

POS for .NET

Microsoft's Point of Service for .NET is currently at version 1.12. Excerpting from its home documentation page, POS for .NET 'is a class library that enables POS developers to apply Microsoft .NET technologies in their products. It provides a simple and consistent interface for.NET Framework applications to interact with POS devices, a set of interfaces and classes created to help Vendors write applications for common devices such as Cash Drawers or Line Displays, and support for Windows Plug and Play functionality.'

To download, searchthis page for 'POS for .NET'. The POS for .NET v1.12 download page states that its supported operating systems are 'Windows Embedded for Point of Service; Windows Server 2003 Service Pack 1; Windows Vista Business; Windows Vista Enterprise; Windows XP Service Pack 2'.

The UnifiedPOS specification contains an appendix that describes the POS for .NET relationship to UnifiedPOS.

OPOS Assemblies for .NET

The complete set of OPOS Assemblies are available in a ZIP file, or they may be installed via the CCO 1.13.003 or 1.14.001 Windows Installer file. A simple test program is also available.

• OPOS for .NET Assemblies 1.14.001
  This ZIP file contains the following:
  • One assembly for each of the OPOS device types. As an example, the filename of the POSPrinter assembly is 'POS.Devices.OPOSPOSPrinter.dll'. In addition, for compatibility with applications built against the 1.12.xxx or 1.13.xxx assemblies, publisher policy assemblys are included for each device type.
  • An assembly containing the OPOS constants.
  • A 'readme' file.
  • Two batch files to assist developers in adding or removing the assemblies from the Global Assembly Cache (GAC), if desired. These must be run in adminstrator mode.
• OPOS for .NET Assemblies 1.13.003
  This ZIP file contains a similar set of files, but for UnifiedPOS 1.13.
• OPOS for .NET Assemblies 1.12.000
  This ZIP file contains a similar set of files, but for UnifiedPOS 1.12.
• POSPrinter1 Application
  This ZIP file contains a C# test application project. It was built against the 1.12.000 OPOS for .NET Assemblies.

Example -- Prepared against the 1.12.000 assemblies and 1.12.000 CCOs.

A screenshot of the POSPrinter1 sample application follows, followed by the NCR Emulator Service Object which was used for this run. (The emulators are not available to the public. You should substitute your own emulators or a vendor's installed and configured device.) The following activities occur while running it:

Ibm Opos Configuration Utility Manager

• Application startup: Instantiate the OPOS POSPrinter assembly's class and wire the StatusUpdateEvents. Display the OPOS Common Control Object's ControlObjectDescription and ControlObjectVersion properties.
• Open: When this button is pressed, the application calls the Open and ClaimDevice methods, and sets the DeviceEnabled property. After opening the device, the application displays the ServiceObjectDescription and ServiceObjectVersion properties.
• Print: When this button is pressed, the application calls the PrintNormal method to print on the receipt station.
• On the emulator, update the Receipt Station's paper status to 'Empty'. A StatusUpdate event is fired; value 24 = PTR_SUE_REC_EMPTY.
• Print when out-of-paper: The print fails with ResultCode 114 = OPOS_E_EXTENDED. (The ResultCodeExtended is not output by this program, but would be 203 = OPOS_EPTR_REC_EMPTY.)

Ibm Opos Configuration Utility Billing

The following screen shots are from Visual Studio 2008, with the POSPrinter1 solution loaded. The Solution Explorer shows the references, including references to the POSPrinter and OPOS Constants assemblies:

The Object Browser shows the classes and interfaces in the OPOSPOSPrinter assembly:

Ibm Opos Configuration Utility Setup

Last updated:2015-02-08