Manual Connect

Manual Connect is the fallback when auto-discovery cannot find your fiscal printer. You pick the driver and transport yourself, enter the connection details, and save the device. The app then registers it with the cloud in the background.

When to use Manual Connect

Use Manual Connect on the Device Discovery screen when one of these is true:

1. Auto-discovery found nothing. The Bluetooth scan returned no paired printers in range, or the network scan found no host responding on the default fiscal ports.
2. The printer is reachable only via a static TCP/IP address the local-network scan cannot reach — typical for off-network deployments, VPN-tunnelled shop floors and port-forwarded back-office printers behind a firewall.
3. You already know the device — driver, transport, host and port — and want to skip the probe entirely.

Open the Manual Connect screen

Open the Devices tab, tap + Add Device, then on the Device Discovery screen tap Manual Connect.

If you are not yet on the Devices tab, see the Devices browser page first.

Fill in the form

The screen has four sections, top to bottom.

Device name

A free-text label, required. The trimmed value appears in the Devices list and on every receipt's device column. Whitespace-only names fail validation.

Example: Back Office Printer.

Driver

A row of chips. Pick the family that matches your hardware:

For the canonical mapping from each driver to its native driver id, default port and baud rate, see Driver registry.

Transport

A second chip row:

• TCP (default)
• Bluetooth
• Serial
• USB

Your choice changes which fields appear in the Connection section below.

Connection

The fields here depend on the transport you picked.

Save the device

After filling in the form, tap Save Device. The app runs through these steps:

Read the device badge

After Save Device closes the screen, the new entry appears in the Devices tab with one of four badges:

The device entry on the Devices browser is your starting point for sending a status command, issuing a receipt, renaming or deleting the device.

Pick the right driver and transport

A few rules of thumb:

• If you have the printer model in front of you, look up its protocol family, default TCP port and baud rate in the Driver registry.
• For most Romanian deployments, Datecs covers the majority of installed AMEFs. Use Daisy for Daisy hardware. Use Tremol for ZFP-family hardware (default port 4999). Use MF/JE for Shtrih-family devices.
• If you do not know the driver and auto-discovery has already failed, start with the manufacturer family (Datecs → the Datecs entry; Tremol → the Tremol entry; Shtrih → MF/JE). Try Custom only after those fail.
• For TCP, enter the printer's static IP and the driver's default port. The screen pre-fills 4999, which is correct for Tremol/ZFP but not for every driver.
• For Bluetooth, pair the printer through Android settings first, then enter the MAC address here.
• For Serial, enter the OS device path.
• For USB, enter the descriptor — but consider Serial instead, since most USB fiscal printers expose a serial profile.

Edit the device later

Once saved, the connection details cannot be edited from Manual Connect. Renaming and unclaiming live on the device's Settings tab in the Devices browser. To change the host, port or address, delete the device and add it again.

Where to next

• Pairing — the auto-discovery flow Manual Connect is the fallback for.
• Devices browser — where the saved device appears, with its badge and detail screen.
• Driver registry — the canonical lookup for every driver's family, default port, default baud rate and native driver.
• Custom protocol — what the Custom driver option targets.
• Sign in to cloud — optional; attaches standalone devices to your organization automatically.