Datecs

Datecs is a Bulgarian manufacturer with the largest installed base of AMEF hardware in the Romanian and Bulgarian markets. e-bon speaks three Datecs protocol variants — Datecs Extended, Datecs Compact, and Datecs Professional — all in the isl (Information Systems Limited) family. Extended typically covers large-format / professional installs (DP-25, DP-150, DP-500, FP-2000), Compact covers compact and mobile units (FP-700, FP-300, FP-550), and Professional covers FP-1000, FP-3530, and WP-500X. They are the first three entries in the auto-detect probe order because of their installed-base share.

At a glance

Supported transports

All three Datecs protocols accept the standard transport set: TCP/IP over wired Ethernet, Bluetooth, and Serial (RS-232). USB-attached printers are reached through a USB-to-Serial bridge (CDC-ACM or FTDI) and addressed as Serial — there is no native USB transport for AMEF connectivity, on Datecs or on any other protocol in the registry. Wi-Fi is not supported for the AMEF link itself; see the Wi-Fi note in Supported devices.

Connection defaults

The TCP listener on Datecs printers defaults to port 9100, and Serial / Bluetooth links negotiate at 115200 baud. These are the values e-bon will try first when probing or when you accept the suggested defaults during pairing. Override them only when the device has been re-configured locally (uncommon for fiscal hardware) or when the network places the printer behind a port-mapped NAT.

Known quirks / firmware tips

No protocol-specific quirks are documented for the Datecs family at this time — Extended, Compact, and Professional share the ISL command framing and default to the same port and baud, so standard troubleshooting applies. If a Datecs unit pairs but hangs mid-bon fiscal, check the link layer first (Bluetooth signal, switch port, cable) before suspecting the protocol layer; see Troubleshooting for the full checklist.

Pairing flow

Pairing a Datecs printer follows the standard e-bon flow on Android: pick the transport (Bluetooth for mobile setups, Serial for fixed POS, TCP for LAN-attached units), accept the suggested protocol when auto-detect lands on it, and confirm a test print. The full step-by-step is in Pairing your fiscal printer; this page covers only the per-protocol defaults you may be asked about during that flow.

Next steps

• Supported devices — full compatibility matrix and family overview.
• Pairing your fiscal printer — operational pairing flow on Android.
• Troubleshooting — when a paired device goes offline or refuses to print.