Diebold Nixdorf ProBase Store 2 User manual

Brand: Diebold Nixdorf

Model: ProBase Store 2

Type: User manual

User Manual ProBase Store 2.0

JavaPOS™, OPOS, POS for .NET and CPOS

Diebold Nixdorf Public Use

Version 2.3.10

Table of Contents

1. Revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê1

2. Copyright and Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê2

3. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê3

4. General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê4

4.1. Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê4

4.2. Environment at Diebold Nixdorf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê5

4.3. License agreement / rights of use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê5

5. Architecture and interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê6

5.1. Unified Device Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê6

5.2. JavaPOS guideline. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê8

5.3. Product installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê8

5.3.1. Variants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê9

5.3.2. Installation profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê9

5.3.2.1. Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê9

5.3.2.2. Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê10

5.3.3. Default paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê10

5.3.3.1. Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê10

5.3.3.2. Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê11

5.3.4. Special features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê11

5.3.4.1. Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê11

6. Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê12

6.1. Software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê12

6.1.1. Installation requirements for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê12

6.1.1.1. Minimum precondition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê12

6.1.1.2. Additional preconditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê12

6.1.2. Installation requirements for Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê12

6.1.2.1. Minimum precondition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê13

6.2. Runtime requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê13

6.2.1. Runtime requirements Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê13

6.2.1.1. Minimum precondition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê13

6.2.1.2. Additional preconditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê13

6.2.2. Runtime requirements Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê14

6.2.2.1. Minimum precondition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê14

6.2.2.2. Running non-root user. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê14

6.2.3. Driver Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê14

6.2.4. Driver Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê16

6.2.5. Firmware dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê17

6.2.5.1. Note systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê17

6.2.5.2. Coin systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê18

6.2.5.3. Other devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê19

7. Supported peripherals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê21

7.1. Supported operating systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê25

7.1.1. Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê25

7.1.2. Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê25

7.2. Supported Java Runtime Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê25

7.3. Available add-ons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê25

7.3.1. Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê26

7.3.2. Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê26

8. Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê27

8.1. Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê27

8.2. Installation under Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê27

8.2.1. Interactive installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê27

8.2.1.1. Interactive installation Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê27

8.2.2. Silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê34

8.2.3. Unattended installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê34

8.3. Installation under Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê34

8.3.1. Update installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê35

8.3.2. Upgrade installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê35

9. Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê36

9.1. Uninstallation under Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê36

9.1.1. Interactive uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê36

9.1.2. Silent uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê36

9.2. Uninstallation under Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê36

10. Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê38

10.1. JavaPOS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê38

10.1.1. Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê38

10.1.2. Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê38

10.1.3. The JavaPOS Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê39

10.1.3.1. The Configurator Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê40

10.1.3.2. Filtering and Customizing Device Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê41

10.1.3.3. Configuration Properties with Special Meaning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê45

10.1.3.4. Printing the JAR classpath. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê47

10.1.3.5. Forcing a Specific JVM To Be Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê47

10.2. OPOS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê48

10.3. P4DN configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê49

10.4. CPOS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê50

10.5. UDM configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê50

10.5.1. UDM server configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê50

10.5.1.1. Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê50

10.5.1.2. Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê52

10.5.2. UDM client configuration for OPOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê53

10.5.3. UDM client configuration for P4DN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê54

10.5.4. UDM client configuration for CPOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê55

10.5.4.1. Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê56

10.6. DNUT Device Status Correction Mechanism at ProBase RSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê57

10.6.1. Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê57

10.6.2. Integration and Enabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê58

11. Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê59

11.1. Logging during installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê59

11.1.1. Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê59

11.1.2. Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê59

11.2. Logging during uninstallation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê60

11.2.1. Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê60

11.2.2. Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê60

11.3. JavaPOS Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê60

11.3.1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê60

11.3.2. Target Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê60

11.3.3. Logging Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê61

11.3.3.1. Logging Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê61

11.3.3.2. Logger Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê62

11.3.4. Logging Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê64

11.4. JavaPOS Configurator logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê65

11.4.1. Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê65

11.4.2. Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê65

11.5. OPOS logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê66

11.6. P4DN logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê67

11.7. CPOS logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê67

11.8. UDM logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê67

11.8.1. UDM server logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê68

11.8.1.1. Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê68

11.8.1.2. Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê68

11.8.2. UDM client logging - OPOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê69

11.8.3. UDM client logging - P4DN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê69

11.8.4. UDM client logging - CPOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê69

12. Programming Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê71

12.1. JavaPOS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê71

12.2. OPOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê71

12.3. CPOS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê71

12.4. P4DN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê71

13. Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê72

13.1. ProBase/JavaPOS Tool Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê72

13.1.1. Invocation under Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê72

13.1.2. Invocation under Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê72

13.1.3. Toggle JavaPOS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê73

13.1.4. SwingSamples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê73

13.2. Logging Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê74

13.3. JCL Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê75

13.4. OPOS UDM Configuration Updater. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê75

13.5. Test tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê75

13.5.1. SwingSamples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê75

13.5.1.1. Invocation under Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê76

13.5.1.2. Invocation under Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê76

13.5.1.3. The Simple Test mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê77

13.5.1.4. The Extended Test mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê77

13.5.2. Testing via the OPOS Config Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê78

13.5.3. OPOS Sample Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê80

13.5.4. P4DN test tool - Microsoft POS Tester . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê81

13.5.5. PBReport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê81

13.5.5.1. Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê82

13.5.5.2. Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê82

References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê82

Chapter 1. Revision history

Version Date Author Comment / Change

1.0 June 2023 Ragnar

Seedorf

Initial Version for ProBase Store 2

User Manual ProBase Store 2.0

Diebold Nixdorf Public Use 1

Chapter 2. Copyright and Trademarks

Microsoft and Windows are registered trademarks of Microsoft Corporation.

Diebold Nixdorf and BEETLE are registered trademarks of Diebold Nixdorf, Inc.

Linux is a registered trademark of Linus Torvalds.

Red Hat and CentOS are registered trademarks of Red Hat, Inc.

JavaPOS is a trademark of Sun Microsystems, Inc.

Oracle and Java are registered trademarks of Oracle and/or its affiliates.

iButton is a registered trademark of Maxim Integrated

All other company names and trademarks mentioned in this documentation are the property of

their respective owners.

User Manual ProBase Store 2.0

Diebold Nixdorf Public Use 2

Chapter 3. Introduction

ProBase Store 2, the current middle-ware product for retail, is the direct successor to the previous

middle-ware products ProBase Store 1.x which was the direct successor to ProBase Retail 1.x and

ProBase POS 2.x and is therefore the middle-ware product for all current and future Diebold

Nixdorf Retail products.

The content of ProBase Store 2 is very similar to ProBase Store 1 and still largely corresponds to the

combination of the two previous products ProBase POS and ProBase Retail. The UnifiedPOS [1]

interfaces JavaPOS [2], OPOS [3] and P4DN for POS peripherals and JavaPOS for cash recyclers and

security scales are included. Test and configuration tools (such as the JavaPOS Configurator or

SwingSamples). However, ProBase Store 2 does not provide firmware files anymore and the D&S

Platform with the graphical user interface T/SOP now is provided by a separate product installer

(T/SOP Retail).

Following the Diebold Nixdorf JavaPOS guidelines, ProBase Store 2 offers automated integration of

JavaPOS add-ons, automated generation of customizable JavaPOS configurations and separation of

configuration and log files from the installation location of ProBase Store.

This user manual is intended to provide an overview of the functions and tools provided with

ProBase Store 2. Configuration of the individual software layers as well as logging are dealt with

separately.

Supported operating systems, peripherals, and cash recycler as well as requirements regarding the

Java runtime environment, system and device drivers, firmware versions and other software

frameworks are also covered by this manual. However, this information may change slightly for

each ProBase Store version. Therefore, please refer to the release notes of the corresponding

ProBase Store version, as they will provide more up-to-date information in this regard.

[1] UnifiedPOS - https://www.omg.org/retail/unified-pos.htm

[2] JavaPOS - http://www.javapos.org

[3] OPOS - OLE for Retail POS

User Manual ProBase Store 2.0

Diebold Nixdorf Public Use 3

Chapter 4. General information

4.1. Background

The increasing use of Microsoft operating systems on retail market systems as well as the

associated standard OPOS in 1994 had at that time led to the first module-based provision of the

peripheral drivers according to the OPOS standard.

With the emerge of the Java technology to be usable for retail branch solutions and the

introduction of this programming language into the POS application world in 1997, it became

necessary for Diebold Nixdorf to provide the corresponding JavaPOS drivers.

Based on evaluation results on Java, a close cooperation between Diebold Nixdorf and its retail

customers developed in the realization of projects based on Java technology. In the past, JOWE [4]

was the first available software / abstraction layer for controlling retail peripherals from Java

applications under Microsoft Windows operating systems.

At the same time, the standard JavaPOS developed under the proactive cooperation of Diebold

Nixdorf in the relevant committees for this technology approach. On the background of the

progress in the international JavaPOS standardization, the retail market could now also be offered

a pure JavaPOS adapted to the current requirements of the market.

About two years later, the standardization committee decided to meet the requirements for the

synchronization of OPOS and JavaPOS and the standard UnifiedPOS was created. UnifiedPOS is an

acronym for Unified Point of Service (UPOS), which is used to unify the OPOS and JavaPOS

interfaces.

UPOS is not really a driver implementation, but rather an abstract interface definition. The

conversion of the definition into usable code as driver for POS applications is OPOS (as ActiveX or

ATL objects in the Microsoft world) and JavaPOS (as JAR modules in the Java world and thus for

Windows and Linux operating systems).

Since 2002, with the introduction of the .NET Framework on Microsoft Windows operating systems,

there has been another technology for application programming and starting 2003 there were

requests for a further implementation of UPOS for .NET based POS applications. This POS for .NET

(P4DN) implementation of the UPOS standard is based on the .NET technology of the Microsoft

Windows operating systems.

The provision of these three driver stacks, which have all been implemented according to the same

design principles, has led to ProBase POS/ProBase Retail and now to ProBase Store. The peripheral

interfaces JavaPOS, OPOS and P4DN will be delivered with ProBase Store in the future.

As a further interface, Diebold Nixdorf also offers the interface CPOS for applications, which were

developed in the programming language C. This is also an implementation according to the UPOS

standard; here the access takes place via the usual methods in the C programming world.

The basis of ProBase Store is the implementation of the UPOS standard for JavaPOS, which is always

the interface to the peripheral devices. The interfaces OPOS and P4DN are supported with

simultaneous use of the so-called Unified Device Manager (UDM).

User Manual ProBase Store 2.0

Diebold Nixdorf Public Use 4

4.2. Environment at Diebold Nixdorf

ProBase Store 2 can be used on all released DN Retail systems under the ProBase Store 2 approved

operating systems.

The approved operating systems for each DN Retail system can be found within the current

configurator in the DN intranet portal (go to Intranet > Portfolio > Our Portfolio > Services >

Configurator/Price list). In case no access is granted to that site, a Diebold Nixdorf account manager

has to be contacted.

Details about the supported systems and peripherals as well as dependencies regarding driver and

firmware versions can generally be found in in chapter 5 - Specifications as well as the respective

ProBase Store 2 Release Notes.

4.3. License agreement / rights of use

The software ProBase Store 2 is subject to license and usage conditions. The exact wording of the

End User License Agreement can be found in the appendix, chapter [End-User License Agreement -

ProBase Store].

[4] JOWE - Java OPOS Wrapper; no longer supported

User Manual ProBase Store 2.0

Diebold Nixdorf Public Use 5

Chapter 5. Architecture and interfaces

ProBase Store 2 provides the well-known interfaces JavaPOS, OPOS and POS for .NET (P4DN) as well

as CPOS, an interface for C-based applications, for Windows and Linux based operating systems.

These interfaces are all implementations based on the UnifiedPOS specifications with the following

versions:

•JavaPOS 1.13 or higher

•OPOS 1.13

•P4DN 1.14 or 1.12

•CPOS 1.14

The base of ProBase Store is the JavaPOS of Diebold Nixdorf. The interfaces OPOS, CPOS and P4DN

are supported if the UDM is used at the same time.

The interfaces OPOS 1.6 and 1.3, JavaPOS 1.7 and 1.5 as well as RDI and LRDI are not supported by

ProBase Store 2 and cannot be operated in parallel with the interfaces of ProBase Store.

NOTE OPOS and P4DN are reserved for the Windows operating systems, since the basic

technology is only available under Windows.

NOTE

ProBase Store 2 provides the JavaPOS controls based on UnifiedPOS 1.14 and

supports the POS for .NET Framework 1.14 with the functionality specified with

UnifiedPOS 1.13. Optionally the POS for .NET Framework 1.12 with the functionality

specified with UnifiedPOS 1.12 may be used as well.

5.1. Unified Device Manager

The UnifiedPOS standard describes the device interfaces independently to the implementation.

Normally, this is done with a Unified Modeling Language (UML). However, different technologies

and implementations are used in the retail sector, for which some separate appendices have been

added to the UnifiedPOS specification. The most important implementations of the standard are:

•OPOS (since 1994)

•JavaPOS (since 1998)

•POS for .NET (since 2006)

Hardware manufacturers needs to offer all three implementations to support the entire UnifiedPOS

standard. Differences in the implementation technologies and therefore in the methods, properties

and events, as well as differences between Windows and Linux operating systems, can lead to

different behavior of the addressed hardware although the implementations all follow the same

standard. Further requirements of the application developers to support other technologies (for

example in the Linux area further non-Java based API) have not been taken into account yet.

Normally, there is no way to allow an application written in a particular technology to access a

UnifiedPOS device interface written in another technology. This usually requires an adapter or

User Manual ProBase Store 2.0

Diebold Nixdorf Public Use 6

wrapper.

Diebold Nixdorf has developed the Unified Device Manager based on the different implementation

technologies, the different operating system types (Windows and Linux) as well as the different

implementations of the UnifiedPOS standard.

The Unified Device Manager provides a socket-based client-server construct, which uses JavaPOS

for the communication with the hardware and provides all other implementation technologies

according to the UnifiedPOS standard via generic service objects. This approach is also important

for JavaPOS as soon as the UDM client and the UDM server are to be used on different devices (e.g.,

mobile POS).

The following figure shows the UDM architecture as it is provided for Windows.

Figure 1. UDM architecture under Windows

The generic service objects convert the method calls of the application into corresponding JavaPOS

calls, just as the answers from JavaPOS are converted back into the target implementation for the

application. For the application itself, the UDM and the shared JavaPOS are presented transparently.

This results in the following advantages for the customer:

•An identical behavior of the device services under OPOS, JavaPOS, POS for .NET and CPOS

•In the OPOS area, the common controls can be used again

User Manual ProBase Store 2.0

Diebold Nixdorf Public Use 7

•Coexistence of Diebold Nixdorf device services or service objects with those of third-party

manufacturers is possible

•UnifiedPOS remains the standard long-term constant

•A common software stack for POS peripherals, SCO and ACO systems

•Harmonized interfaces for applications such as Vynamic™ Checkout, VSS and retail partner

applications

5.2. JavaPOS guideline

By working with the UPOS standard, it turned out that not everything has been standardized or that

there are no guidelines for the implementation. As a result, Diebold Nixdorf, together with selected

partners and customers, developed a JavaPOS guideline ([GL-Lin], [GL-Win]) that includes the

following topics:

•Packaging and delivery of JavaPOS components

•Configuration of the JavaPOS modules to the desired hardware

•Handling additional functions for firmware and device settings

•Handling of additional inventory and statistic data by JavaPOS

•Integration of JavaPOS components from different manufacturers

Focus of this guideline is to simplify the integration of JavaPOS components from different

manufacturers through uniform installation routines. The integration is not done by copying

individual JAR files, but by referencing them. By embedding the JAR files into compliant installers,

they are automatically updateable without manual adaptation.

Starting with ProBase POS 2 and ProBase Store 1, and now also with ProBase Store 2, Diebold

Nixdorf follows this DN JavaPOS guideline.

The biggest differences to the previous architecture, which was implemented in the ProBase POS

1.1 and ProBase Retail 1.2 versions, can be seen in the various installation paths, the folder

structures contained in them and the locations of files and user data such as JAR files, dynamic link

libraries, shared objects, log files and configuration files defined by the policy. The requirements for

the paths to be used correspond to the usual standards of the operating systems (e.g. Linux → LSB)

plus the necessary extensions for using the JavaPOS architecture.

To minimize the integration effort, Diebold Nixdorf provides with the JavaPOS Configurator in

ProBase Store a tool that generates a common system configuration from the individual JavaPOS

components of several manufacturers that follow the JavaPOS guideline directives. Using

application- specific configuration files, this system configuration can be further customized by the

JavaPOS Configurator.

5.3. Product installer

User Manual ProBase Store 2.0

Diebold Nixdorf Public Use 8

5.3.1. Variants

ProBase Store 2 product installer are available as 32-bit and 64-bit versions for Windows and Linux

based operating systems. The installer variants (32 or 64-bit) are based on the process architecture

of the application respectively on the Java Virtual Machine (Java VM) architecture to be used. This

means that e.g. when using a 32-bit application / Java VM on a 64-bit operating system, the 32-bit

ProBase Store installer needs to be used anyway.

The provided product installers follow the naming scheme:

Windows:

•ProBase-Store-MAJOR.MINOR.BUILD-x64.exe

•ProBase-Store-MAJOR.MINOR.BUILD-x86.exe

Example: ProBase-Store-2.0.70-x64.exe

Linux:

•dn-probase-store-MAJOR.MINOR.BUILD-i386.rpm

•dn-probase-store-MAJOR.MINOR.BUILD-x86_x64.rpm

Example: dn-probase-store-2.0.70-x86_64.rpm

For a detailed listing of supported operating systems, see chapter Supported operating systems. The

currently available ProBase Store installer are listed in chapter [Released installer versions].

5.3.2. Installation profiles

5.3.2.1. Windows

The current product installer for Windows operating systems is based on Inno Setup, which offers

the concept of installation profiles and can be used interactively as well as remotely, silent or

unattended.

In case of the ProBase Store installer, a profile is connected to a certain implementation technology,

which allows the programmatic access to peripheral devices. This allows the user to select the

technology that fits the application. The installer ensures that all components for the selected

profile are installed correctly and completely.

If necessary, the user can also make changes to the selection of the components specified by the

preselected profile by further selecting or deselecting components in the Custom Installation

profile. However, the installer cannot perform a consistency check of the components in the

modified profile, so the user must ensure that all required components are installed. Otherwise, the

application may not or may work in a limited way.

The following table shows the currently defined installation profiles:

User Manual ProBase Store 2.0

Diebold Nixdorf Public Use 9

Profile Name Profile Meaning

JavaPOS Installation

(for all devices)

Installation profile for JavaPOS based

applications.

Note: Installer default profile

OPOS Installation

(for non cash devices)

Installation profile for OPOS based applications.

Forwards OPOS calls to DN’s JavaPOS

implementation using the UDM technology.

POS for .NET Installation

(for non cash devices)

Installation profile for POS for .NET 1.14 based

applications.

Forwards POS for .NET calls to DN’s JavaPOS

implementation using the UDM technology.

CPOS Installation

(for non cash devices)

Installation profile for C based applications.

Forwards C calls to DN’s JavaPOS

implementation using the UDM technology.

Expert Installation Installation profile for customizing the

component selection, preselected by the

previously chosen installation profile.

NOTE It is recommended to use the predefined profiles and to perform a customized

installation only after consultation with the Diebold Nixdorf support team [5]

5.3.2.2. Linux

The current product installer for Linux operating systems bases on the Red Hat Package Manager

(RPM) and does not provide any profiles. All dependencies to other packages will be checked by the

Package Manager and, if possible, automatically resolved.

5.3.3. Default paths

5.3.3.1. Windows

ProBase Store 2 will be installed to C:\Program Files\javapos\ProBase-Store for architecture identical

installations (e.g. 32-bit on 32-bit Windows) and to C:\Program Files (x86)\javapos\ProBase-Store for

architecture-non-identical installations (32-bit on 64-bit Windows) (typically referred to as

<installation directory>.

JavaPOS related user data such as configuration files and log files are stored in subdirectories

under C:\ProgramData\javapos according to the Diebold Nixdorf JavaPOS guidelines [GL-Win]. Non-

JavaPOS related user data is usually stored under subdirectories of C:\ProgramData\Diebold Nixdorf.

In the Windows Start menu, the ProBase Store 2 installer adds all links and subfolders in the

directory Diebold Nixdorf ProBase Store (xx JVM) by default. Here xx is equal to 32-bit or 64-bit,

depending on the ProBase Store installer.

NOTE Windows 10 does not support multiple level of sub folder within the Start menu as

it was known for former Windows releases.

User Manual ProBase Store 2.0

Diebold Nixdorf Public Use 10

5.3.3.2. Linux

On Linux, ProBase Store 2 will be installed in the directory /opt/dn/javapos.

Configuration files are stored in subdirectories under /etc/opt/dn and /etc/opt/javapos, and log files

are stored at /var/log/dn according to the DN JavaPOS guidelines.

5.3.4. Special features

ProBase Store 2 not only consist of UnifiedPOS implementations such as JavaPOS, OPOS and P4DN

or the Unified Device Manager, but also offers a range of tools for diagnosis, configuration, testing

and logging purposes. Further information can be found in the chapter Configuration, Logging, and

Tools.

In the last stages of the setup the product installer runs per default some of these tools to configure

the previously installed components, creates scheduled respectively auto start tasks or sets up

services for these tools.

5.3.4.1. Windows

If the OPOS profile or the OPOS UDM adapter in the Custom Installation profile has been selected,

the product installer will call the OPOS UDM Configuration Updater once and set up a permanent

task for the OPOS UDM Configuration Updater in Windows. By default, this task will be executed at

each system start and user login. Further information can be found in chapter OPOS UDM

Configuration Updater.

NOTE It is recommended to restart the system after the installation, since the final

configuration takes place in the start phase.

[5] GSE; mail to [email protected]

User Manual ProBase Store 2.0

Diebold Nixdorf Public Use 11

Chapter 6. Specifications

6.1. Software requirements

6.1.1. Installation requirements for Windows

The conditions described in this chapter apply to the installation process only. The requirements at

runtime, such as additional system drivers for the devices to be addressed, can be found in chapter

Runtime requirements Windows.

NOTE The installation of ProBase Store 2 requires administrator permissions.

NOTE

ProBase Store 2 as the successor to ProBase Store 1, ProBase POS, and ProBase

Retail, conflicts with these predecessors. They must be uninstalled in advance to a

ProBase Store 2 installation. For more details regarding the migration of an older

DN Middleware product to ProBase Store 2, please refer to the ProBase Store 2

Migration Guide [PBS2-MG].

6.1.1.1. Minimum precondition

The following software must already be installed on the target computer to run the ProBase Store 2

setup successfully:

•Java Virtual Machine (version 8)

For further information, see chapter Supported Java Runtime Environments.

6.1.1.2. Additional preconditions

In case the POS for .NET 1.14 Installation profile (see chapter Installation profiles) or corresponding

POS for .NET components have been selected (see chapter Interactive installation) , ensure that the

following software has already been installed on the target machine:

•Microsoft Point of Service for .NET (version 1.14)

•Microsoft .NET Framework (at least version 4.0)

In case the component POS for .NET 1.12 has been selected (available at installation profile Expert

Installation, see chapter Interactive installation) , ensure that the following software has already

been installed on the target machine:

•Microsoft Point of Service for .NET (version 1.12)

•Microsoft .NET Framework (at least version 2.0 up to 4.0)

6.1.2. Installation requirements for Linux

The conditions described in this chapter apply to the installation process only. The requirements at

runtime, such as additional system drivers for the devices to be addressed, can be found in chapter

User Manual ProBase Store 2.0

Diebold Nixdorf Public Use 12

Runtime requirements Linux.

NOTE The installation of ProBase Store 2 requires administrator permissions.

NOTE

ProBase Store 2, as the successor to ProBase Store 1, ProBase POS and ProBase

Retail, conflicts with these predecessors, which must be uninstalled beforehand. For

more details regarding the migration of an older DN middle-ware product to

ProBase Store 2, please refer to the ProBase Store 2 Migration Guide [PBS2-MG].

6.1.2.1. Minimum precondition

The following software must already be installed on the target computer to run the ProBase Store 2

setup successfully:

•Java Virtual Machine (version 8)

For further information, see chapter Supported Java Runtime Environments.

6.2. Runtime requirements

The conditions described in this chapter only apply to the runtime of ProBase Store 2 components.

The requirements for the installation process can be found in chapter Installation requirements for

Windows and Installation requirements for Linux.

6.2.1. Runtime requirements Windows

6.2.1.1. Minimum precondition

The following software must be installed on the target system to use ProBase Store 2:

•Java Virtual Machine (version 8)

For further information, see chapter Supported Java Runtime Environments.

6.2.1.2. Additional preconditions

In case the POS for .NET 1.14 Installation profile or corresponding POS for .NET components have

been selected during the installation of ProBase Store, the following software has to be installed on

the target machine in order to use the POS for .NET 1.14 API:

•Microsoft Point of Service for .NET (version 1.14)

•Microsoft .NET Framework (at least version 4.0)

In case the POS for .NET 1.12 component has been selected during the installation of ProBase Store,

the following software has to be installed on the target machine in order to use the POS for .NET

1.12 API:

•Microsoft Point of Service for .NET (version 1.12)

•Microsoft .NET Framework (at least version 2.0 up to 4.0)

User Manual ProBase Store 2.0

Diebold Nixdorf Public Use 13

6.2.2. Runtime requirements Linux

6.2.2.1. Minimum precondition

The following software must be installed on the target system to use ProBase Store 2:

•Java Virtual Machine (version 8)

For further information, see chapter Supported Java Runtime Environments.

6.2.2.2. Running non-root user

During installation ProBase Store 2 will create a group with name dndev if it not yet exist and is

setting up permissions and ownership of installed artifacts so that a member of that group is able to

access all required resources and to run provided tools properly.

So a non-root user needs to join group dndev in order to operate devices, e.g. by:

usermod -a -G dndev <user-name>

RS232 device nodes, such as '/dev/ttyS*', are usually owned by group dialout. Hence, a non-root use

needs to join group dialout as well:

usermod -a -G dialout <user-name>

6.2.3. Driver Dependencies

Some devices require additional system driver installed on the target system, which are not part of

this product.

The current release was tested against the following system drivers which are not part of this

product distribution and needs to be installed before any application utilizing this software library

is running.

NOTE

The system drivers are aligned to the bit architecture of the underlying operating

system. Whereas the product is aligned to the bit architecture of the used JRE. This

means, this 32 bit product requires 64 bit drivers on a 64 bit Windows®.

Driver Operating System Affected Devices

probase_fo_usb_drivers_ci

neo_32bit.msi (version

1.4.31)

32 bit of

Windows® 7™

Windows® POSReady 7™

CINEO C6010, C6020,

iButton, Special Electronics

at ACO and kiosk systems

probase_fo_usb_drivers_ci

neo_64bit.msi (version

1.4.31)

64 bit of

Windows® 7™

Windows® POSReady 7™

CINEO C6010, C6020,

iButton, Special Electronics

at ACO and kiosk systems

BNR_USB_Driver_2.1.0.zip Windows® 7™

Windows® POSReady 7™

iCash20

User Manual ProBase Store 2.0

Diebold Nixdorf Public Use 14

Driver Operating System Affected Devices

WN_POSUSB_Driver-

2.50.0.0-44-setup.exe

Windows® 7™

Windows® POSReady 7™

non-HID, non-cash USB

devices

DN_POSUSB_Driver-

3.10.0.0-7-setup.exe

Windows® 7™

Windows® POSReady 7™

Windows® 10™

Note: Windows® 7™ 64-bit and

Windows® POSReady 7™ 64-bit are not

supported yet, especially for iCash45.

non-HID, non-cash USB

devices

CINEO C6010, C6020;

iButton, Special Electronics

at ACO and kiosk systems,

Retail Control Box, Retail

IO Controller, iCash45

DN USB Security Scale

SC500W

DN_CashdrawerSMBus_Dri

ver-1.4.0.0-1-setup.exe

Windows® 7™

Windows® POSReady 7™

Windows® 10 (64 bit only)

cash drawers at BEETLE

/M-III (Kx, Mx, Ox, Rx

Mainboards)

DN_CashdrawerSMBus_Dri

ver-4.0.10.0-01-setup.exe

Windows® 7™

Windows® POSReady 7™

Windows® 10 (64 bit only)

cash drawers at BEETLE

/iPOS+ Advanced, BEETLE

/iPOS+ systems, and

BEETLE A-family A1xxx

systems

Note: This is a different

driver than the previous

one, despite the same

name.

WN_Port_Driver-1.0.0.1-2-

setup.exe

Windows® 7™

Windows® POSReady 7™

Windows® 10 (64 bit only)

cash drawers at BEETLE

/MII+ /SII+ (and older)

systems w/ mainboards G1,

G41, H1, I1, Jx;

mechanical keylock at PS/2

POS keyboard

DN_CDC_Virtual_COM_Port

-1.0.0.0-2-setup.exe

Windows® 7™

Windows® POSReady 7™

Windows® 10 (64 bit only)

iCash30

Driver_Setup.zip

JCM MRX USB Driver

Ver.1.01

Windows® 7™

Windows® POSReady 7™

Note: for Windows 10 no driver is

needed

iCash40 (for FW download

via USB),

iCash60

CP210x Windows Drivers

v6.7.6 9/3/2020

Silicon Labs Virtual COM

Port (VCP) driver

Windows® 7™

Windows® POSReady 7™

iCash65,

CS315KF scale

User Manual ProBase Store 2.0

Diebold Nixdorf Public Use 15

Page is loading ...

Diebold Nixdorf ProBase Store 2 User manual

Diebold Nixdorf ProBase Store 2 User manual

Diebold Nixdorf ProBase Store 2 User manual

Related papers

Other documents