This is POS for.NET service object for calling OPOS version 1.15 controls from POS for.NET.

• 2022-01-22 BugFix:There were unimplemented properties/methods on the following devices.
  • CashChanger
  • CheckScanner
  • FiscalPrinter
  • POSPower
  • POSPrinter
  • Scale
• Migrated to Visual Studio 2022 and .NET Framework 4.8.

In POS for.NET, a mechanism called Legacy COM Interop, called OPOS control, is built inside POS for.NET.
However, this mechanism has the following issues:

• The following additions/changes added in UnifiedPOS version 1.15 are not supported.
  • Added CAT device functions to ElectronicValueReader/Writer device.
  • Added EVRW_ST_CAT to the ServiceType property of ElectronicValueReader/Writer device.
  • Added values to CountryCode and DateType properties of FiscalPrinter device.
• Only 24 of 36 types of device classes defined in UnifiedPOS are supported (in case of v1.14.1)
  Unsupported devices:
  • Belt
  • Bill Acceptor
  • Bill Dispenser
  • Biometrics
  • Coin Acceptor
  • Electronic Journal
  • Electronic Value Reader/Writer
  • Gate
  • Image Scanner
  • Item Dispenser
  • Lights
  • RFID Scanner
• Changing the value of OPOS's BinaryConversion property requires a different conversion process than when calling OPOS directly

In order to solve these problems, i created a service object with the following features:

• An extension DLL for POS for.NET that supports the interfaces and definitions added in UnifiedPOS version 1.15 has been incorporated.
• Supported all 36 types of device classes defined in UnifiedPOS.
• BinaryConversion processing for OPOS was divided into two kinds.
  • In POS for.NET and OPOS, string properties/parameters are passed through without processing anything.
  • Properties/parameters such as byte[] or Bitmap etc. in POS for.NET perform conversion processing according to the value of BinaryConversion.
• When reading the property considered as Enum in POS for.NET, if OPOS notifies the undefined value, it raises PosControlException and notifies it by storing it in the exception's ErrorCodeExtended property.
• Information on the corresponding OPOS device name is defined in the Configuration.xml file of POS for.NET.

To develop and execute this program you need:

• Visual Studio 2022 or Visual Studio Community 2022 version 17.1.0 (development only)
• .NET framework 4.8
• Microsoft Point of Service for .NET v1.14.1 (POS for.NET) : https://www.microsoft.com/en-us/download/details.aspx?id=55758
• OpenPOS.Extension.Ver115 : https://github.com/kunif/OpenPOSExtensionVer115
• Common Control Objects 1.15.000 : https://github.com/kunif/OPOS-CCO
• OPOS service object of target device

To develop/execute this service object, you need the CCO of Common Control Objects 1.15 and the PIA and UnifiedPOS 1.15 support extension DLL for POS for.NET.
If the device vendor's OPOS only installs .ocx for the target device, or if CCO 1.14.001 and earlier versions are not supported, replace them.
Install both CCO and PIA with Install_CCOandPIA.bat of Common Control Objects 1.15.
Please register UnifiedPOS 1.15 Support extension DLL for POS for.NET.

To install on the execution environment, please follow the procedure below.

• Create an appropriate folder and copy OpenPOS.CCO115Interop.dll.
  It is not the root of the drive, and the path name of the folder does not include the blank space and should consist only of alphanumeric characters less equal 0x7E.
  There is less chance of that person having a problem.

• Register with the arbitrary name with the above folder as the value in the ControlAssemblies key of the POS for.NET registry.
  For example "AltCCOInterops"="C:\\POSforNET\\CCOInterop\\"
  However, during development work, it is automatically registered as part of the processing at build time.
  The position of the target key is as follows.

  • 64bitOS: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\POSfor.NET\ControlAssemblies
  • 32bitOS: HKEY_LOCAL_MACHINE\SOFTWARE\POSfor.NET\ControlAssemblies

Create a device entry and set its properties using the posdm.exe program of POS for.NET.

• Create a device entry with the ADDDEVICE command of posdm
  Example usage: posdm ADDDEVICE OposEVRW1 /type:ElectronicValueRW /soname:"OpenPOS 1.15 ElectronicValueRW"

  • The specified device name ("OposEVRW1" in the example) is stored as the value of "HardwarePath"
    Please specify a unique name that does not overlap the name of other POS for.NET or OPOS name.
  • Please append "OpenPOS 1.15 " to the head of /soname: and specify the device class name enclosed in double quotes.
    For example, "OpenPOS 1.15 CashDrawer", "OpenPOS 1.15 POSPrinter", "OpenPOS 1.15 Scanner" etc.

• Set the OPOS device name to be used with the ADDPROPERTY command of posdm
  Example usage: posdm ADDPROPERTY OposDeviceName VenderName_ModelName /type:ElectronicValueRW /soname:"OpenPOS 1.15 ElectronicValueRW" /path:OposEVRW1

  • The property name to be set is "OposDeviceName".
  • Please specify the device name key or logical device name that exists in the OPOS registry for the value to be set ("VenderName_ModelName" in the example).

Target device entry in Configuration.xml after execution example:

<ServiceObject Name="OpenPOS 1.15 ElectronicValueRW" Type="ElectronicValueRW">
  <Device HardwarePath="" Enabled="yes" PnP="no" />
  <Device HardwarePath="OposEVRW1" Enabled="yes" PnP="no">
    <Property Name="OposDeviceName" Value="VenderName_ModelName" />
  </Device>
</ServiceObject>

Here is a procedure and an example of calling the device entry created in the usage example of the above setting.

• Add "OpenPOS.Extension.Ver115" to the project reference (found below). "C:\Windows\Microsoft.NET\assembly\GAC_MSIL\OpenPOS.Extension.Ver115\v4.0_1.15.0.0__ad2c9a67c3439201\OpenPOS.Extension.Ver115.dll"
• Add "using OpenPOS.Extension;" to the source code.
• Call PoExplorer's GetDevices method with the device class name and DeviceCompatibilities specified and get the device collection of the corresponding device class
• Search for a DeviceInfo whose ServiceObjectName and HardwarePath match in the acquired device collection and generate an object with the CreateInstance method based on it
• Register event handler
• Call Open method

Example code:

ElectronicValueRW evrwObj1 = null;
PosExplorer explorer = new PosExplorer();
DeviceCollection evrwList = explorer.GetDevices("ElectronicValueRW", DeviceCompatibilities.CompatibilityLevel1);
foreach (DeviceInfo evrwInfo in evrwList)
{
    if (evrwInfo.ServiceObjectName == "OpenPOS 1.15 ElectronicValueRW")
    {
        if (evrwInfo.HardwarePath == "OposEVRW1")
        {
            evrwObj1 = (ElectronicValueRW)explorer.CreateInstance(evrwInfo);
            break;
        }
    }
}
if (evrwObj1 != null)
{
    evrwObj1.DataEvent += evrwObj1_DataEvent;
    evrwObj1.DirestIOEvent += evrwObj1_DirectIOEvent;
    evrwObj1.ErrorEvent += evrwObj1_ErrorEvent;
    evrwObj1.OutputCompleteEvent += evrwObj1_OutputCompleteEvent;
    evrwObj1.StatusUpdateEvent += evrwObj1_StatusUpdateEvent;
    evrwObj1.TransitionEvent += evrwObj1_TransitionEvent;
 
    evrwObj1.Open();
}

Note: The value of the Compatibility property(DeviceCompatibilities) varies from case to case.
In the state listed in DeviceCollection/DeviceInfo, it is "CompatibilityLevel1", and for objects generated by CreateInstance it is "Opos".

• Check whether the interface of OpenPOS.Extension.Ver115 is included and then call the method of UnifoedPOS 1.15.

Example code:

// The object is declared in ElectronicValueRW evrwObj1

try
{
    if (evrwObj1 is IElectronicValueRW115)
    {
        if (((IElectronicValueRW115) evrwObj1).ServiceType115 == ServiceType115.Cat)
        {
            int iSequenceNumber = 9999;
            decimal dAmount = 5000;
            decimal dTaxOthers = 500;
            int iTimeout = 300000;
            try
            {
                ((IElectronicValueRW115) evrwObj1).AuthorizeSales(iSequenceNumber, dAmount, dTaxOthers, iTimeout);
            }
            catch(UPOSException ue)
            {
            }
        }
    }
}
catch(Exception ae)
{
}

Currently known issues are as follows.

• Have not checked the operation using actual OPOS or device.
• In particular, it is unknown whether the conversion of string (OPOS) and Bitmap etc (POS for.NET) of the following property/parameter/return value is correct.
  • BiometricsInformationRecord(BIR) related property/parameter/return value of Biometrics device
  • RawSensorData property of Biometrics device
  • ImageData property of CheckScanner device
  • FrameData property of ImageScanner device
• There are no functions such as acquisition of operation record and information acquisition for troubleshooting.

The following issues were found in POS for.NET during the development process.

• Information is insufficient in Biometrics' BIR defined in POS for.NET.
  It does not contain the following information in the BIR diagram described in the UnifiedPOS specification.
  • Quality
  • Product ID (Owner, Type)
  • Subtype
  • Index Flag
  • Index (UUID)
  • Digital Signature
• Also at BIR, whether it is a issue or not is not clear, but the situation is as follows.
  • The Creation Date/Creation Time is the date and time when the BIR object was created in the POS for.NET service object, not the date and time the device read the information.
    Although it may not be a problem with POS for.NET's own service object, information is rewritten in the case of processing relayed to/from OPOS.

If you want to customize for specific user/vendor specific processing etc, please do it freely.
However, in that case, please change all the following information to make it an independent file so that it can be used concurrently with this service object at the same time.

• File name: OpenPOS.CCO115Interop.dll
• namespace: OpenPOS.CCO115Interop
• GUID: [assembly: Guid("a2226b69-b229-4d9b-95a9-624ea83f9207")]
• Service object name: [ServiceObject(DeviceType.Xxxx, "OpenPOS 1.15 Xxxx",
• Class name: public class OpenPOSXxxx :

Note) "Xxxx" in the above contains the device class name of UnifiedPOS/POS for.NET.

It is good to reduce the amount of work to extract only the device you want to customize and create a new one.

In Addition, if it is good function with versatility, please propose it here.

Licensed under the zlib License.