Configuring Diebold Nixdorf Devices for SCO

This topic explains how to configure the Self-Checkout Connector (SCO) to work with Diebold Nixdorf devices in Business Central, including SCO card, terminals, and Device Type setup.

Step 1: Create or Verify Self-Checkout Device Types

SCO terminals must be associated with a Self-Checkout Device Type that defines manufacturer, host, port, and Feature Flags.

  1. Open the Self-Checkout Device Type list in Business Central.
  2. Verify that there is a Device Type for each Diebold terminal to be used.
  3. Each Device Type should include the following fields:
    • Device Type – Unique code for the device type.
    • Description – Descriptive name.
    • Brand – Manufacturer (Diebold Nixdorf).
    • Tender Type Mapping Profile – Optional, if tender type IDs differ.

Step 2: Verify Default Feature Flags

When the RapidStart package is imported and applied, a default DIEBOLDNIXDORF Device Type is created with the following Feature Flags:

  • AgeVerificationLimits → 18,20,40
  • CancelHostName → localhost
  • CancelPortNumber → 17003
  • DiscountText → Discount
  • DisplayPeriodicDiscountDescription → true
  • DisplayTaxInformation → false
  • GrayHairAge → 50
  • MainHostName → localhost
  • MainPortNumber → 17002
  • PosEventsCancelHostName → localhost
  • PosEventsCancelPortNumber → 17005
  • PosEventsHostName → localhost
  • PosEventsPortNumber → 17004
  • UseCustomerOwnBag → false
  • WeighingUnit → kg

Partners can adjust hostnames and ports for each terminal as required. For 1–N installations, create multiple Device Types, one per Diebold terminal.

Required Feature Flags (Communication Endpoints)

SCO communicates with the Diebold TPiSCAN self-checkout application using socket-based channels provided by the IfcIScanConnectorNoOut class. Each Feature Flag defines a hostname and port used for a specific method group.

Feature Flag Description Corresponds to Diebold Parameter
MainHostName Hostname or IP for the main method group. hostNameMain
MainPortNumber Port for the main method group. portNrMain
CancelHostName Hostname or IP used for cancel operations. hostNameCancel
CancelPortNumber Port for cancel operations. portNrCancel
PosEventsHostName Hostname or IP for POS event notifications. hostNamePosEvents
PosEventsPortNumber Port for POS event notifications. portNrPosEvents
PosEventsCancelHostName Hostname or IP for cancel-related event notifications. hostNameCancelPosEvents
PosEventsCancelPortNumber Port for cancel-related event notifications. portNrCancelPosEvents

How the Diebold Integration Works

  1. SCO reads the Feature Flags configured for the Diebold Device Type.
  2. The IfcIScanConnectorNoOut class initializes socket channels using the configured hostnames and ports.
  3. Dedicated receivers are started for inbound method groups (Main and Cancel).
  4. Event streams (PosEvents and CancelPosEvents) are handled by separate channel senders.
  5. Once all sockets are initialized, SCO and Diebold POS exchange commands and events in real time.

After configuring the Feature Flags and restarting SCO, the system should automatically establish a connection with the Diebold POS.

Step 3: Configure the SCO Card

1. Open the Self-Checkout Connector card in Business Central.

2. Configure these fields:

  • Store ID – The store where the Diebold device(s) are located.
  • Hardware Profile – Required; defines EFT and printer devices.
  • Staff ID – Staff with Self-Checkout User = Yes.
  • Terminals Table – Add the terminal(s) that this SCO instance will communicate with:
    • 1–1 installation: Only 1 terminal, must reference a Diebold Device Type.
    • 1–N installation: Multiple terminals allowed, each assigned a Diebold Device Type.

Step 4: Verify Hardware Profiles

Ensure each terminal’s Hardware Profile points to the correct EFT and printer devices in Hardware Station. If the terminal does not have its own Hardware Profile, it inherits the SCO card’s Hardware Profile.

Step 5: Testing Diebold Terminals

  1. Start the SCO connector from the SCO Management Portal.
  2. Check that the terminal(s) are Connected and Online.
  3. Perform a test transaction to verify communication with LS Central.

Notes

  • All terminals associated with a single SCO instance must be Diebold devices.
  • 1–N installations require multiple Device Types and terminals, all Diebold.
  • Feature Flags are maintained in the Device Type, not the SCO card.
  • Ensure hostnames and ports are correctly configured for each terminal.

See Also