Intro to OPOS - program a device for an OPOS POS

[slopoke54]

All,

I'm going to be creating OPOS drivers for a checkstand scale. The idea is to be able to attach the scale to all/as many as possible existing POS sytems via OPOS.

I have the UnifiedPOS 1.10 doc which has many details. But, for now, I'm just looking to get the highest level grasp of the task.

For example:

Does a checkstand scale programmer write OPOS code just for the scale itself or does the scale programmer have to provide the code that runs on the POS as well?

If the code must be provided for the POS, then there must be multiple versions of the POS code for each POS OS that exists?

A given POS device could have any OS (Windows, Unix...) and then an application program written for it that provides POS functions? Would an OPOS checkstand scale driver be independent of the POS app or would there have to be a separate OPOS driver for every POS app?

As you can see, I'm just looking for the basic 'how is this set up?' kind of view just to get a grasp of the scope.

Any help appreciated...

Glen

 

[FoodtoGo]

Each device should have a driver of the target O/S. These are written to the OPOS standard.

It's like printer laser printer drivers. The Driver handles the unique-ness of the hardware, the application just needs to know where to print.

 

[slopoke54]

Thanks! That's what I thought. So, just to be sure, the vendor of a checkstand scale would have to provide the following to be OPOS compliant:

1. Software/Firmware to run on the checkstand scale device itself.
2. An OS specific (Windows, Linux, etc.) OPOS driver (for each OS desirecd to support) that is available to applications that run on the POS.
3. An installer for each OS/POS to put the drivers on the POS platform.

Are there code examples for both the device itself and the Windows driver (for example) along with POS software that uses the OPOS driver available anywhere?

Thanks for your help,
Glen.

 

[FoodtoGo]

yes, you have it correct. Usually the OPOS driver comes with some way to test the device (similar to the test print in the laser example). Once the driver is tested, the POS software will use it by the device's OPOS name.

Sorry, I've never coded for OPOS. It's a Microsoft driven "Standard" so maybe there's something from them to use.

 

[slopoke54]

Thanks very much!

Glen