🖨️ Hardware: Devices for Your DiKAS POS¶
This page shows which devices work with DiKAS, what to look out for when buying, and how to connect everything — from the receipt printer to the card terminal to the draught system. Each category starts with what you as a restaurant or bar owner need to know; the technical details follow in brief for your technician.
The Basic Principle
DiKAS talks to your devices directly over the local network (TCP/IP) — the printer and card terminal simply sit on the same network as the register. If your POS runs in the cloud, the Hardware Agent (an app on your venue network) takes over card payment and printing locally. The switch happens automatically — you won't notice a thing.
Receipt Printers & Kitchen Printers¶
The receipt printer is the most important device after the register itself: it prints customer receipts, kitchen tickets, and invoices. The good news: DiKAS uses the ESC/POS standard — so practically any common thermal receipt printer works. You don't need to buy a specific model.
Example: Pizzeria Da Mario runs two network receipt printers — one at the counter for customer receipts, one in the kitchen for order tickets. Both are connected to the router via LAN cable, done.
Connection Types¶
You set up a printer under Admin → Settings → Hardware → Printers. There you choose the connection type:
| Connection Type | Who It's For | Input |
|---|---|---|
| IP/Network | Recommended for most businesses | IP address and port, e.g. 192.168.1.100:9100 (raw TCP, default port 9100) |
| Local (USB/COM) | Printer connected directly to the register or appliance | USB 1–4 or COM 1–4 |
| Client Printing | Printing via the POS device itself | — |
| A4 System Printer | Invoices on a regular A4 printer | Via the operating system (CUPS/lpr) |
Network Printer Instead of USB
For businesses with multiple POS stations, network printers are the better choice: every register can reach every printer, no matter where it's located. USB ties the printer to exactly one device.
Step-by-Step Setup (Network Printer)¶
- Connect the printer to the router via LAN cable and switch it on.
- Open Admin → Settings → Hardware → Printers.
- Select "Search for Printers" — DiKAS scans the network and finds the printer automatically.
Alternatively, enter the IP address and port by hand (e.g.
192.168.1.100:9100). - Choose the driver (for most thermal printers: Epson-compatible, see below).
- Trigger a test print — if a receipt comes out, you're done.
Drivers and Options¶
| Setting | Options |
|---|---|
| Driver | Epson NVMode / Epson KeyMode, dot-matrix printer, Star dot-matrix, Mobile 58 mm, "Amount display" (serial customer display, see Customer Display) |
| Receipt Width | Standard 80 mm; 58 mm mobile printers use the dedicated "Mobile 58mm" driver |
| Character Set | Codepage 858 (default — prints umlauts like ä, ö, ü correctly) |
| Cut | Full cut or partial cut, configurable per printer |
| Logo & QR | Logo printing on the receipt, QR code printing (e.g. TSE QR code) |
| Backup Printer | A fallback printer per printer — if one fails, the other steps in |
Built-In Reliability¶
- Printer monitoring: DiKAS monitors paper level, cover status, and online status of the printer.
- Print queue: If a print job fails, DiKAS automatically retries it every 5 seconds — receipts aren't lost just because the paper jams briefly.
- Backup printer: A replacement device can be configured for every printer.
Bluetooth Receipt Printers on the Go
Mobile receipt printers with Bluetooth (RFCOMM/SPP) work via the Android app — handy for the beer garden or the delivery driver. For narrow 58 mm mobile printers, choose the "Mobile 58mm" driver.
How to assign article groups to kitchen printers (food → kitchen, drinks → counter) is covered in Kitchen Printer & Kitchen Display.
Cash Drawer¶
The cash drawer doesn't need its own connection to the register: it plugs into the kick-out port of the receipt printer (RJ11/RJ12 socket — standard on all POS receipt printers). When DiKAS opens the drawer, the signal runs through the printer.
When Does the Drawer Open?¶
You control this in fine detail, depending on your business:
| Level | Setting |
|---|---|
| Per Payment Method | Drawer: Auto (opens only for cash), Always, Never |
| Global | Drawer opening can be disabled entirely |
| Per Workstation | e.g. mobile register without a drawer — disable opening there |
| Per Employee | Drawer opening can be locked for individual employees |
| As a POS Button | Dedicated article type "Open Drawer" — the drawer opens on tap |
Example: At Restaurant Bella Vista, the drawer only opens for cash payment (Auto). The temporary staff have no permission to open the drawer without a booking — only the shift lead has the "Open Drawer" button on their screen.
Card Terminals¶
Card payment is a must these days. DiKAS connects card terminals directly — the amount appears on the terminal automatically, no re-typing, no typos. The terminal is set up under Admin → Settings → Hardware → Card Terminal.
Which Terminals Work?¶
| Terminal Type | What Is It? | Status |
|---|---|---|
| ZVT | The standard protocol used by almost all German card terminals. Connects over the network (TCP/IP). | ✓ Live |
| SoftPOS / Tap-to-Pay (RS2) | Your Android device itself becomes a card reader (NFC) — no extra hardware needed. | ✓ Live |
| Stripe Terminal | Cloud-controlled Stripe card readers; connected via the Reader ID (tmr_…). No hardware agent needed. |
✓ Live |
| SumUp Reader (Air/Solo) | SumUp card reader, connected via the SumUp cloud; paired via code. | ✓ Available |
Example: Da Mario simply keeps using their existing German card terminal — almost all devices from German providers speak ZVT. The mobile waiter at Club Neon, on the other hand, takes payment directly via SoftPOS with the Android phone, with no additional device at all.
Connecting a ZVT Terminal¶
- Connect the terminal to the POS network via LAN cable (same network as the register).
- On the terminal, enable ECR/register connection over TCP/IP (your terminal provider will do this if needed) and note the IP address.
- Open Admin → Settings → Hardware → Card Terminal, select type ZVT.
- Enter the terminal's IP address; the default port is 20007.
- Run a test payment.
Over ZVT, DiKAS controls: payment, void/credit, terminal settlement, receipt reprint, and status query — all from the register.
Who Prints the Card Receipt?¶
The "Terminal has its own printer" option decides:
- On: The terminal prints the card receipt itself (classic standalone device with paper roll).
- Off: DiKAS also prints the card receipt on the POS receipt.
SoftPOS, Stripe, and SumUp readers have no printer of their own — there, the card receipt automatically ends up on the receipt.
Card Refunds: Only With Reference to the Original Payment
With Stripe and SumUp there is no "free-standing" card refund: a refund is only possible with reference to the original payment. Plan your void workflows accordingly — details on handling this are under Payment Methods.
Customer Display & Kitchen Display¶
Both are software at DiKAS, not special hardware: any screen or tablet with a browser will do. You don't buy proprietary hardware — you use what you already have, or a cheap standard tablet.
Customer Display¶
The customer display shows your guests the cart, total, and QR code while ringing up. Between transactions it runs a slideshow — with your own welcome image or video, e.g. your daily menu.
- Set up a second screen or tablet next to the register and open the browser.
- Start pairing in DiKAS — a code appears on the second screen.
- Confirm the code at the register — done, the display is paired.
Alternatives to the browser display:
- Second Android device as an amount display: paired via Bluetooth through the app.
- Classic serial customer display (two-line display): set up as a "printer" with the "Amount display" driver — see Receipt Printers.
Kitchen Display¶
The kitchen display is a browser page with live updates: new orders appear instantly on the screen in the kitchen — no paper chaos. An old tablet or a TV with a browser is enough. DiKAS can additionally, or alternatively, print kitchen tickets on a normal receipt printer.
Everything about setup and operation: Kitchen Printer & Kitchen Display.
Barcode Scanners & NFC Cards¶
Barcode Scanners¶
Any USB or Bluetooth scanner in keyboard mode (keyboard wedge) works instantly — no driver, no configuration. The scanner "types" the barcode like a keyboard, DiKAS recognizes it, and books the article.
- Price-embedded barcodes (e.g. scale labels with a printed-in price) are recognized — the price comes directly from the label.
- Camera scan in the app: delivery drivers can simply scan barcodes with the phone camera — no scanner hardware needed at all.
NFC/RFID: Staff Login and Guest Cards¶
DiKAS uses NFC cards and chips for staff login and for nightclub guest cards (cashless payment in the club, see Disco Turnstile).
| Reader | Connection |
|---|---|
| Phone NFC | Directly via the Android app — no accessory needed |
| USB Reader ACR122U | USB on the register |
| Reader on the DikasArch Appliance | PC/SC or Baltech (serial) |
| Reader in Keyboard Mode | Like a barcode scanner, no driver |
| Staff Key (Addimat Lock) | Via the DikasArch appliance |
Example: At Club Neon, waiters log in at the register with an NFC chip; guests pay with NFC guest cards issued at the turnstile.
Draught Systems¶
A draught system only pours what the register has booked — closing the classic gap between the bar and the register. DiKAS connects directly to the system: the waiter books "2× lager, table 7", and the system releases exactly that pour.
Supported protocols: Gruber, Addimat, Hogatron/WMF — plus a simulator that lets you test the connection without real hardware.
Connection¶
| Variant | Details |
|---|---|
| Serial (COM) | Standard 9600 baud, 8N1; 2400 / 4800 / 19200 also configurable |
| Network (TCP/UDP) | Default port 3010 |
How the Booking Works¶
- The waiter books the drink at the register.
- DiKAS sends PLU + waiter number + table number + quantity to the draught system.
- The system releases the pour. Voids follow the same path.
- Optionally, the system reports its pours back to the register via a return channel — so you can also see what was poured directly at the system.
Options: checksum, automatic reset at end-of-day, automatic retry on transmission errors. The interface shows the live status of the connection and a diagnostic log directly.
Draught System Requires the Local Register
The draught system connects serially or on the local network — it only works with a local register or an on-site DikasArch appliance, not in pure cloud operation.
The step-by-step setup with article assignment can be found under Articles & Printers in Detail.
Cash Machines (Cash Recyclers)¶
A cash machine accepts notes and coins, dispenses change, and makes the register theft-proof — no more open cash balance at the counter.
Supported:
| Device | Connection |
|---|---|
| VNE | HTTP |
| Cashmatic | HTTPS |
| Simulator | For testing without hardware |
The "Coin Levels" menu item at the register always shows the machine's current fill levels.
TSE (Germany Only)¶
Every register in Germany needs a Technische Sicherheitseinrichtung (TSE) (Technical Security Device). With DiKAS you have two options:
| Variant | Hardware Needed? | Who It's For |
|---|---|---|
| fiskaly Cloud TSE | No — account and configuration only | Cloud operation, fastest start |
| Swissbit USB TSE | USB stick on the local POS computer or the appliance | Local operation |
DiKAS sets the PINs of the Swissbit TSE itself — you don't need to initialize anything by hand.
TSE Does Not Run via the Hardware Agent
The TSE is tied to the local register (or runs as a cloud TSE) — it is not addressed via the hardware agent.
Full details on setup, export, and tax audits: TSE.
Disco Turnstile¶
For clubs with a card system, DiKAS controls entry and exit via turnstiles. No specific brand is required: any turnstile controller works, as long as it can send the card ID via HTTP to the Turnstile API (the API key is embedded in the URL). DiKAS responds with open or lock — depending on whether the guest card has been paid.
Alternatives without a turnstile: a self-checkout kiosk at the exit or a mobile exit register.
The complete concept including card issuance and settlement: Disco Turnstile.
Caller ID (Delivery Service)¶
When a regular customer calls, DiKAS automatically opens their customer record — name, address, and recent orders are right there. This saves time and back-and-forth on every call.
This uses the Fritz!Box's caller ID (NCID protocol). Default address: 192.168.178.1, port
1012.
- Enable the Call Monitor on the Fritz!Box (dial the phone code
#96*5*on the connected phone). - Enter the Fritz!Box address in DiKAS (default
192.168.178.1:1012). - Incoming calls now automatically open the matching customer.
Example: At Da Mario's, the phone rings and the POS screen already shows "Weber family, Ahornweg 3, last order: 2× Pizza Diavolo."
What Does DiKAS Run On?¶
| Platform | Use |
|---|---|
| DikasArch Appliance (Mini PC) | Register and hardware agent in one device, boots directly into kiosk mode; also supports eGalax touchscreens |
| Android App | Mobile register, SoftPOS card payment, Bluetooth devices (printer, amount display) |
| Browser | Cloud operation — any modern browser is enough |
| Device Agent (Android Tablet) | Pure hardware bridge without a POS interface |
Hardware in Cloud Operation: The Hardware Agent¶
If your POS runs in the cloud, the card terminal and printer still stay at your venue — the Hardware Agent carries out payments and printing locally. The agent is already built into the DikasArch appliance, the Android app, and the Device Agent; nothing extra needs to be installed.
- Pairing via QR code from Admin → Settings → Hardware → Hardware Agent.
- Multiple devices = failover: if several agents are connected, another one automatically takes over if one device fails.
Full details, including cloud failover in case of a server outage: Hardware Agent.
Next Steps¶
→ Hardware Agent & Cloud Failover — Hardware in cloud operation
→ Kitchen Printer & Kitchen Display — Getting orders to the kitchen
→ TSE — Setting up the Technical Security Device